Category: RDBMS

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

October 19
October 18

Driven by a post from Lewis about “OSDM: Rerverse Engineer A Schema“, I dared my luck to play with Oracle SQL Developer Data Modeler (OSDM), trying to see if it understands the XML database realm off doing things. It doesn’t understands it…at least, yet.  I used the early adopter release 1.5.1 (build 518).

I wonder if it is reasonable that I am disappointed; In the long run the “XDB” schema that I used to reverse engineer isn’t relational but (at least) object-relational. Most of the object relational issues, OSDM understands, but not the theory behind XMLType tables. I tried it multiple times, in the end, even the “secondary tables” and “spatial properties” option you can check during the reverse enginering option.