This is a guest post by David Clement, a veteran database engineer, a coworker and a friend of mine. You can find him online at davidclement.org.
Here is an interesting feature that’s worth knowing about because of the potential for strange bugs. When you run a SQL script in the Unix shell, if you use a user-defined exception, you have to take care to prevent failure and success from returning the same result.
The following code snippet shows a normal way to return an error code to the Unix shell from a SQL script. I saved this as return_error_code.sql:
3 Comments | Filed in Oracle, Tips | Tags: gotcha, linux, pl/sql, shell, sql, unixHere is an example of how you would use event-based scheduling to create an Oracle Scheduler job that has to run after the successful completion of another job.
4 Comments | Filed in Oracle | Tags: dbms_scheduler, eventSomething I discovered recently is that the DEFAULT profile for Oracle 11g sets the PASSWORD_LIFE_TIME to 180 instead of UNLIMTED by default. Applications will encounter an “ORA-28002: the password will expire within X days” error message if you keep the default value.
To change the PASSWORD_LIFE_TIME, you:
ALTER PROFILE default LIMIT password_life_time UNLIMITED;
Read more about 11g new security related features here.
1 Comment | Filed in Links, Oracle, Tips | Tags: 11g, gotcha, password, Security