What to do about the ever growing files on Oracle application server as: - default-web-access.log - server.log and more.. These files are not logrotated (OAS < 10.1.3 ) and cannot always be deleted or renamed manually on a 'normal' way, and it must be scripted to avoid extraordinary large log-files. Quite annoying, until Frits Hoogland pointed me to a standard Linux-functionality, 'logrotate'.
Apex, version 3.2.1.00.10, on a 10.2.0.3-database is working fine for some time. Then, while clicking the 'application builder' home-page, we got the 'page not found'-error in the browser. Logging of Apache shows: mod_plsql: /pls/apex_schd/f HTTP-404 ORA-03113: end-of-file on communication channel\n mod_plsql: Unable to reset state for mode 0: Err 3114 url=>/pls/apex_schd/f
Why is it that java is crossing my path so much now and then... After a restore of a database on another node, including renaming him/her, java classes were invalid. Trying to create / replace them, errors popped up: ORA-29516: Aurora assertion failure: Assertion failure at eox.c:317 Uncaught exception Root of all Java exceptions: java.lang.NullPointerException
Consider this, you've got no DataGuard at your disposal. Single node, relying on your RMAN-backup on disk, which is fortunately copied to tape. Now your complete node is burning down. What's is left is your RMAN-backup. In a bad scenario you'll have to restore this to another node.
It is considered a skill every DBA should have, cloning / duplicating a database with RMAN. My own basic checklist through an example: Cloning of the DEVDB on the node LARRIE to node ELLISON, new database name DEVDBNEW