Download Oracle Streams Advanced Queuing User's Guide and Reference

21
21
Monitoring Oracle Messaging Gateway
This chapter discusses means of monitoring the Oracle Messaging Gateway (MGW)
agent, abnormal situations you may experience, several sources of information about
Messaging Gateway errors and exceptions, and suggested remedies.
This chapter contains these topics:
■
Oracle Messaging Gateway Log Files
■
Monitoring the Oracle Messaging Gateway Agent Status
■
Monitoring Oracle Messaging Gateway Propagation
■
Oracle Messaging Gateway Agent Error Messages
Oracle Messaging Gateway Log Files
Messaging Gateway agent status, history, and errors are recorded in Messaging
Gateway log files. A different log file is created each time the Messaging Gateway
agent is started. You should monitor the log file because any errors, configuration
information read at startup time, or dynamic configuration information is written to
the log.
The format of the log file name for the default agent is:
oramgw-hostname-timestamp-processid.log
The format of the log file name for a named agent is:
oramgw-AGENTNAME-hostname-timestamp-processid.log
By default the Messaging Gateway log file is in ORACLE_HOME/mgw/log. This location
can overridden by the parameter log_directory in the Messaging Gateway
initialization file used by the agent, usually mgw.ora.
This section contains these topics:
■
Sample Oracle Messaging Gateway Log File
■
Interpreting Exception Messages in an Oracle Messaging Gateway Log File
Sample Oracle Messaging Gateway Log File
The following sample log file shows the Messaging Gateway agent starting. The
sample log file shows that a messaging link, a registered foreign queue, a propagation
job, and a schedule associated with the job have been added. The log file shows that
the propagation job has been activated. The last line indicates that the Messaging
Gateway is up and running and ready to propagate messages.
Monitoring Oracle Messaging Gateway 21-1