ORA-32800 internal error string
-
Cause: An unexpected error condition occurred.
-
Action: Contact Oracle Support Services.
ORA-32801 invalid value string for string
-
Cause: An invalid value was given for a parameter.
-
Action: Specify a valid value for the parameter.
ORA-32802 value for string must be string
-
Cause: An invalid value was given for a parameter.
-
Action: Specify the value as indicated by the message.
ORA-32803 value for string cannot be altered
-
Cause: An attempt was made to alter a value that cannot be altered.
-
Action: Retry the operation without altering the indicated value.
ORA-32804 invalid value string, string should have form string
-
Cause: A value specified for a parameter has the incorrect form.
-
Action: Specify a string of the correct form.
ORA-32805 identifier for string too long, maximum length is string characters
-
Cause: An identifier string exceeded the maximum allowed length.
-
Action: Specify a string whose length is less than the maximum.
ORA-32806 value for string is too long, maximum length is string
-
Cause: A value exceeded it's maximum allowed length.
-
Action: Specify a value whose length is less than the maximum.
ORA-32807 message system link string already exists
-
Cause: A message system link of the specified name already exists.
-
Action: Specify a different name.
ORA-32808 message system link string does not exist
-
Cause: A message system link of the specified name does not exist.
-
Action: Specify a message system link name that already exists.
ORA-32809 foreign queue string is already registered
-
Cause: The foreign queue has already been registered for this message system link (NAME@MSGLINK).
-
Action: Specify a different name that is not being used for this message system link.
ORA-32810 foreign queue string is not registered
-
Cause: The foreign queue (NAME@MSGLINK) has not been registered for this message system link.
-
Action: Specify the name of a registered foreign queue.
ORA-32811 subscriber string already exists
-
Cause: The specified subscriber identifier already exists.
-
Action: Specify a different identifier.
ORA-32812 subscriber string does not exist
-
Cause: The specified subscriber identifier does not exist.
-
Action: Specify a subscriber identifier that already exists.
ORA-32813 propagation schedule string already exists
-
Cause: The specified propagation schedule identifier already exists.
-
Action: Specify a different identifier.
ORA-32814 propagation schedule string does not exist
-
Cause: The specified propagation schedule identifier does not exist.
-
Action: Specify a schedule identifier that already exists.
ORA-32815 message system link string is referenced by a foreign queue
-
Cause: An attempt was made to remove a message system link currently referenced by one or more registered foreign queues.
-
Action: Unregister all foreign queues using this message system link and retry the operation.
ORA-32816 foreign queue string is referenced by a subscriber or schedule
-
Cause: An attempt was made to unregister a foreign queue currently referenced by one or more subscribers or propagation schedules.
-
Action: Remove all subscribers and propagation schedules using this foreign queue and retry the operation.
ORA-32817 message system link string is not configured with a log queue for string
-
Cause: An attempt was made to add a propagation
subscriber but the message system link was not configured with a log
queue for the indicated propagation type.
-
Action: Alter the message system link to configure the link with a log queue for this propagation type.
ORA-32818 AQ queue string does not exist
-
Cause: An operation was attempted where the specified AQ queue does not exist.
-
Action: Specify the name of an AQ queue that already exists.
ORA-32819 AQ queue string must be a normal queue
-
Cause: An operation was attempted where the specified AQ queue exists but is not a normal queue.
-
Action: Specify the name of an AQ queue which was created as a normal queue (NORMAL_QUEUE).
ORA-32820 subscriber queue and exception queue must use same message system link
-
Cause: An operation for INBOUND propagation was
attempted where the specified subscriber queue and exception queue
reference different message system links.
-
Action: Specify an exception queue that is a registered foreign queue of the same message system link as the subscriber queue.
ORA-32821 subscriber queue and exception queue must have same payload type
-
Cause: An operation for OUTBOUND propagation was
attempted where the AQ queues used for the subscriber queue and
exception queue have different payload types.
-
Action: Specify an exception queue that has the same payload type as the subscriber queue.
ORA-32822 subscriber string is marked for removal
-
Cause: An administration operation for a subscriber
was attempted which is marked for removal. If attempting to remove a
subscriber, then the Messaging Gateway agent is not running or is
running but unable to remove the subscriber at this time.
-
Action: Do not issue propagation administration
commands for a subscriber for which removal is pending. Wait for the
subscriber to be removed by the agent or issue REMOVE_SUBSCRIBER with
the FORCE option to force the subscriber to be removed.
ORA-32823 subscriber exists for queue string and destination string
-
Cause: An attempt was made to create a propagation subscriber when one already exists for the specified queue and destination pair.
-
Action: Specify a different queue and destination pair, or remove the subscriber using that pair and retry the operation.
ORA-32824 schedule exists for source string and destination string
-
Cause: An attempt was made to create a propagation schedule when one already exists for the specified source and destination pair.
-
Action: Specify a different source and destination pair, or remove the schedule using that pair and retry the operation.
ORA-32825 Messaging Gateway agent has not been started
-
Cause: An attempt was made to shut down Messaging Gateway agent when it is not started.
-
Action: No action required.
ORA-32826 Messaging Gateway agent has already been started
-
Cause: An attempt was made to start Messaging Gateway agent when it is already started.
-
Action: No action required.
ORA-32827 Messaging Gateway agent must be shut down
-
Cause: An operation was attempted that requires the Messaging Gateway agent to be shut down.
-
Action: Issue SHUTDOWN, wait for MGW_GATEWAY view to
show NOT_STARTED status, and retry the operation. CLEANUP_GATEWAY may
need to be issued to reset the gateway state if the agent fails to shut
down after a reasonable amount of time.
ORA-32828 Messaging Gateway agent must be running
-
Cause: An operation was attempted that requires the Messaging Gateway agent to be started and responsive.
-
Action: Issue STARTUP, wait for MGW_GATEWAY view to show RUNNING status, and retry the operation.
ORA-32829 Messaging Gateway agent cannot be shut down while it is starting
-
Cause: An attempt was made to shut down Messaging Gateway agent when it is in the process of starting and initializing.
-
Action: Wait for MGW_GATEWAY view to show RUNNING
status and retry the operation. CLEANUP_GATEWAY may need to be issued to
reset the gateway state if the gateway fails to start after a
reasonable amount of time.
ORA-32830 result code string returned by Messaging Gateway agent
-
Cause: Messaging Gateway agent terminated abnormally due to an unexpected error.
-
Action: Review the Messaging Gateway log file for
further information regarding the problem. Resolve the problem and start
the Messaging Gateway agent. Contact Oracle Support Services if the
problem is unable to be resolved.
ORA-32831 timed out trying to acquire administration lock
-
Cause: A timeout occurred when attempting an
administration operation. An attempt was made to perform an
administration operation while Messaging Gateway agent is starting and
initializing, or two administration operations were attempted at the
same time.
-
Action: Retry the operation. If Messaging Gateway agent is starting, then wait for MGW_GATEWAY view to show RUNNING status.
ORA-32832 failure string trying to acquire administration lock
-
Cause: An unexpected error occurred trying to acquire administration lock.
-
Action: Retry the operation. Contact Oracle Support Services if the error persists.
ORA-32833 failure string trying to release administration lock
-
Cause: An unexpected error occurred trying to release administration lock.
-
Action: Contact Oracle Support Services if the error persists.
ORA-32834 Messaging Gateway agent user has not been set
-
Cause: Messaging Gateway agent user has not been configured.
-
Action: Create a database user having role MGW_AGENT_ROLE and issue DB_CONNECT_INFO to configure an agent user.
ORA-32835 database user string does not exist
-
Cause: The specified database user does not currently exist.
-
Action: Create the user and grant all necessary privileges and roles.
ORA-32836 database user string must be granted role string
-
Cause: The specified database user does not have a required role.
-
Action: Grant the user the indicated role.
ORA-32837 invalid configuration state string
-
Cause: Unexpected configuration state.
-
Action: Remove and re-create the configured
entities. Contact Oracle Support Services if the problem is unable to be
identified or resolved.
ORA-32838 exceeded maximum number of properties
-
Cause: An attempt was made to alter a property list where the number of properties in the resulting list exceeds the maximum allowed.
-
Action: Order the elements of the alter list differently so the number of elements in the resulting list is less than the maximum.
ORA-32839 property string is reserved, names with MGWPROP$_ prefix are not valid
-
Cause: An attempt was made to specify a reserved name for a property name.
-
Action: Use a non-reserved name.
ORA-32840 property name cannot be NULL
-
Cause: An attempt was made to use NULL for a property name.
-
Action: Specify a non-NULL name.
ORA-32841 invalid value for property string
-
Cause: An attempt was made to specify an invalid value for a property.
-
Action: Specify a valid property value.
|
Copyright © 1996, 2002 Oracle Corporation. All Rights Reserved. |
|
No comments:
Post a Comment