Kbase P112414: What are save key events and how to enable/disable them?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
31/01/2011 |
|
Status: Verified
GOAL:
What is the enablekeyevents command ?
GOAL:
How does the enablekeyevents works ?
GOAL:
What is the disablekeyevents command ?
GOAL:
How does the disablekeyevents works ?
GOAL:
How to save key event in the database?
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.1x
OpenEdge 10.2x
FIX:
The OpenEdge 10.1x database has an option to truncate the database log file online. When this operation is executed, some important events may be lost. You can enable Save Key Events on a database so that some of these events from the database can be logged to the database as well as to the log file.
By enabling this option the DBA and Technical Support will have access to deleted messages from key events despite the truncation of the database log file.
There are approximately 200 messages that are included as key events in 10.1X and 10.2X.
Defining key events:
Key events in the history of your database include starting the database, changing the structure of the database, executing certain utilities, and encountering errors. When a key event occurs, details of the event are written to your database log file. When you enable your database to save key events, the information written to the log file is also copied into the _KeyEvt table in the database. The details of key events provide insight into critical moments in the history of your database.
Having the details of key events preserved is useful in the diagnosis of issues, either independently, or with the assistance of Progress technical support. Saving key events in the _KeyEvt table ensures that vital information is not lost when your log file is truncated or deleted. It also provides quick access to information that is otherwise embedded within your log file, possibly in the middle of millions of log file entries.
To enable key events logging use the following command :
proutil dbname -C enablekeyevents
When you enable your database to save key events, an additional database process is created to handle the responsibility. This background database process periodically scans your database log file, creating records of the key events in the _KeyEvt table. When successfully started, the key event process writes messages to your log file similar to the following:
[2006/04/06@10:52:58.578-0400] P-6450 T-1 I KEVTRDR 5: (13658) Starting the Save Key Events daemon.
[2006/04/06@10:52:58.578-0400] P-6450 T-1 I KEVTRDR 5: (2518) Started.
Disabling your database from saving key events can be done at any time, even when the database is online. Issue the following command to disable the save key event storage:
To disable key events logging use the following command:
proutil dbname -C disablekeyevents
For a list of all the events logged to the key events table please see the documentation.