Advanced Queuing - Oracle

Working with Messaging Gateway
cannot be altered when Messaging Gateway is running. Entering a value of NULL
does not alter the maximum memory attribute.
The following example, when executed with the Messaging Gateway agent
running, updates the maximum number of connections to 3. The maximum
memory is unchanged.
SQL> exec dbms_mgwadm.alter_agent(3, NULL)
Startup and Shutdown
After Messaging Gateway is installed and configured, start it as follows:
SQL> exec dbms_mgwadm.startup
You can determine the status of the Messaging Gateway agent by using the MGW_
GATEWAY view and by monitoring the log file. Refer to "Monitoring the Messaging
Gateway Log File" on page 18-26.
Monitor the Messaging Gateway agent using the MGW_GATEWAY view as follows:
SQL> select * from mgw_gateway;
AGENT_STATUS AGENT_PING AGENT_JOB AGENT_USER AGENT_DATABASE LAST_ERRO
--------------------------------------------------------------------------
RUNNING REACHABLE 213 MGWAGENT
(Continued) LAST_ERR LAST_ERROR_MSG MAX_CONNECTIONS MAX_MEMORY
-----------------------------------------------------
3 64
When Messaging Gateway has completed initialization, the AGENT_STATUS
column shows the value RUNNING and the AGENT_PING column shows the value
REACHABLE.
The first column, AGENT_STATUS, shows the status of the gateway agent. This
column has the following possible values: NOT_STARTED, START_SCHEDULED,
INITIALIZING, STARTING, RUNNING, and SHUTTING_DOWN. The second column,
AGENT_PING, pings the Messaging Gateway agent. Its value is either REACHABLE
or UNREACHABLE. The columns LAST_ERROR_MSG, LAST_ERROR_DATE, and
LAST_ERROR_TIME give valuable information if an error in starting or running the
Messaging Gateway agent occurs.
See Also: Oracle9i Supplied PL/SQL Packages and Types Reference,
DBMS_MGWADM, for database view information
18-14 Oracle9i Application Developer’s Guide - Advanced Queuing