We and our partners use cookies to Store and/or access information on a device. We and our partners use data for Personalised ads and content, ad and content measurement, audience insights and product development. An example of data being processed may be a unique identifier stored in a cookie. Some of our partners may process your data as a part of their legitimate business interest without asking for consent. To view the purposes they believe they have legitimate interest for, or to object to this data processing use the vendor list link below. The consent submitted will only be used for data processing originating from this website. If you would like to change your settings or withdraw consent at any time, the link to do so is in our privacy policy accessible from our home page..
| Lesson 4 | Informational and task termination messages |
| Objective | Identify 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.
Shutdown messages
Here's an example of what you would see in a database shutdown message.Mon Jun 7 02:50:40 1999 Completed: ALTER DATABASE CLOSE NORMAL Mon Jun 7 02:50:40 1999 ALTER DATABASE DISMOUNT Completed: ALTER DATABASE DISMOUNT
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: /lu4.1-2/tom_log_02.dbf Mon Jun 7 09:55:32 1999 Thread 1 advanced to log sequence 27333 Current log# 3 seq# 27333 mem# 0: /lu1.1-2/tom_log_03.dbf Mon Jun 7 09:58:39 1999 Thread 1 advanced to log sequence 27334 Current log# 1 seq# 27334 mem# 0: /lu3.1-2/tom_log_01.dbf
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 smallNow 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.