RelationalDBDesign RelationalDBDesign 

Alert Log   «Prev  Next»
Lesson 4Informational and task termination messages
ObjectiveIdentify specific informational and task termination messages.

Informational and Task Termination Messages

In this lesson, you'll see examples of messages that fit into the category of information and task termination messages. As you just learned, these messages report on the status of the database, but are not necessarily critical to monitor, nor do they indicate serious problems.

Startup messages

View the code below to see an example of a database startup message.
Database Startup Message
Database Startup Message
These messages show all of the non-default start-up parameters and the starting of the Oracle background processes.

Shutdown messages

Here's an example of what you would see in a database shutdown message.
Mon Jun  7 02:50:40 1999
Mon Jun  7 02:50:40 1999

Redo log switches

These messages show the date and time of the redo log switch, the thread number of the new log file, and the disk location of the current redo log file.
Mon Jun  7 09:52:04 1999
Thread 1 advanced to log sequence 27332
Current log# 2 seq# 27332 mem# 0:
Mon Jun  7 09:55:32 1999
Thread 1 advanced to log sequence 27333
Current log# 3 seq# 27333 mem# 0:
Mon Jun  7 09:58:39 1999
Thread 1 advanced to log sequence 27334
Current log# 1 seq# 27334 mem# 0:

Failure to extend a rollback segment message

This is a task termination message. In this case, the rollback segments have filled, aborting the transaction. (This is also sometimes classified as a severe error - you'll read more about it in the next lesson.)

Snapshot too old message

This is another task termination message. This indicates that a long-running UPDATE or INSERT has exhausted the rollback segments.
ORA-01555: snapshot too old:
rollback segment number 3 with name "R02" too small
Now take a look at the messages to which you will pay very close attention. The messages in the next lesson all indicate severe conditions that you will need to remedy.