Category: Howto

December 4

My presentation of 2nd of December during the UKOUG Conference… So what was in it? Mainly appetizers of how some useful things work and a little bit high level concepts. I demonstrated, I hope, new ways, with (some) foundations coming from XML DB functionality. How to interface with the outside world, for example, by directly saving and selecting from multiple XML files, on disk, from your database or getting or pushing data from/to the internet, like RSS data, getting data for your Google Maps API or easily setting up a SOAP web service.

So among others:

  • How to enable, disable the Protocol Server and to see its Status
  • Overview of the Protocol Server configuration file xdbconfig.xml, Its contents and meaning
  • Memory structures that effect the shared server and therefore also the Protocol Server
  • Protocol HTTP API’s like the PL/SQL Gateway, DBURI (oradb) and Native Database Web Services (orawsv)
  • An overview how the Native Database Web Services works + DEMO
  • An overview how the DBURI servlet works + DEMO
  • An overview of URITypes of  HTTPUriType and XDBUriType’s + DEMO’s
  • The possibilties of combining BFILENAME and XML, like selecting and save files directly from disk
  • An overview of Repository Event’s, how it works demonstrated via a simple DEMO
November 17
November 13

I am currently busy trying to lock down (secure wise) APEX, which is, to say the least, very hard… Anyway one of my tricks from the old days (the days you couldn’t lock an account / database schema), was to lock an user account via the following alternative use of the ALTER USER statement

ALTER USER {username} IDENTIFIED BY VALUES ' {String} '

of course nowadays you can use the more complete syntax

ALTER USER {username} IDENTIFIED BY VALUES ' {String} ' ACCOUNT LOCK

Most of the time this method is used to reset the password to its original value.

I noticed in my (secured) Oracle 11g EE database version that passwords are not shown anymore via DBA_USERS