I personally feel that more error we come across, more stronger our roots become.
Errors are not gonna ruin the DBA's apettite. Both my pals above forgot the most notable 'ORA-00600 (Internal Error)'. They occur more than the most. :) And of course ORA-01578 (Block Corruption). We don't see them too often, Do we? It is yet another error which can be
very much solved in a corporate environment since they have back-ups even for a mouse-click ;)
Now, This error ORA-00060 (Deadlock) is not too tough to break through. You've got two options:- either rollback and rerun the statement (or) Wait till the statement is issue so that the resources are freed up. And
others are day-to-day alerts (Which can be pretty much ignored) like:
ARCx: Media recovery disabled
This message will be written into the alert.log if the arch process is started with the database being in noarchive log mode.
Ignoring SIGALARM Such a message is written into the alert log when a process that waited for a semaphoreThread 1 cannot allocate new log, sequence 1558 Checkpoint not complete
This error message is written into the alert.log if a checkpoint cannot write all dirty db blocks to the online redo log.
