Freitag, 29. Oktober 2010

Oracle joke

Sometimes it's really funny to read logfiles (and yes, some sarcasm helps a lot!)
my todays joke is this one:



ALTER DATABASE ENABLE BLOCK CHANGE TRACKING
Fri Oct 29 11:28:04 2010
Block change tracking file is current.
Fri Oct 29 11:28:30 2010
Starting background process CTWR
Fri Oct 29 11:28:30 2010
CTWR started with pid=58, OS id=9457
Fri Oct 29 11:28:55 2010
ORA-1013 signalled during: ALTER DATABASE ENABLE BLOCK CHANGE TRACKING...
Stopping background process CTWR
Fri Oct 29 11:29:26 2010
Background process CTWR not dead after 30 seconds
Killing background process CTWR
Fri Oct 29 11:29:26 2010
PMON (ospid: 4322): terminating the instance due to error 487
Fri Oct 29 11:29:26 2010
ORA-1092 : opitsk aborting process
Fri Oct 29 11:29:26 2010

What was going here?

  • Someone tried to enable Block Change Tracking.

  • The process CTWR started.

  • (for some reason) the DBA hit ^C before the operation finished.

  • The instance tried to stop the CTWR.

  • CTWR did not stop within 30 seconds - therefore the instance tried to kill it.

  • PMON found CTWR dead (ORA-487 "CTWR process terminated with error"), considered this a critical issue and terminated the instance. (ORA-1092 "ORACLE instance terminated. Disconnection forced")



For me this is one if these bugs which are not worth investigating.
Kommentar veröffentlichen