Oracle Error Messages: 06/05/12

Tuesday, 5 June 2012

ORA-32840: property name cannot be NULL

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-32839: property string is reserved, names with MGWPROP$_ prefix are not valid

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-32838: exceeded maximum number of properties

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-32837: invalid configuration state string

ORA-32837: invalid configuration state string

Cause: The specified configuration state is invalid.

Action: Remove and re-create the configured entities. Contact Oracle Support Services if the problem cannot be identified or resolved.

ORA-32836: database user string must be granted role string

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-32835: database user string does not exist

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-32834: Messaging Gateway agent user has not been set

ORA-32834: Messaging Gateway agent user has not been set

Cause: A 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-32833: failure string trying to release administration lock

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-32832: failure string trying to acquire administration lock

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-32831: timed out trying to acquire administration lock

ORA-32831: timed out trying to acquire administration lock

Cause: A timeout occurred when attempting an administration operation. Either an administration operation was attempted while the Messaging Gateway agent was starting and initializing, or two administration operations were attempted at the same time.

Action: Retry the operation. If the Messaging Gateway agent is starting, wait for MGW_GATEWAY view to show a RUNNING status and retry the operation.

ORA-32830: result code string returned by Messaging Gateway agent

ORA-32830: result code string returned by Messaging Gateway agent

Cause: The 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 cannot be resolved.

ORA-32829: Messaging Gateway agent cannot be shut down while it is starting

ORA-32829: Messaging Gateway agent cannot be shut down while it is starting

Cause: An attempt was made to shut down the Messaging Gateway agent when it is in the process of starting and initializing.

Action: Wait for MGW_GATEWAY view to show a RUNNING status and retry the operation. CLEANUP_GATEWAY may need to be issued to reset the gateway state if the agent fails to start after a reasonable time period.

ORA-32828: Messaging Gateway agent must be running

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 a RUNNING status, and retry the operation.

ORA-32827: Messaging Gateway agent must be shut down

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 a 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 time period.

ORA-32826: Messaging Gateway agent has already been started

ORA-32826: Messaging Gateway agent has already been started

Cause: An attempt was made to start the Messaging Gateway agent when it is already started.

Action: No action required.

ORA-32825: Messaging Gateway agent has not been started

ORA-32825: Messaging Gateway agent has not been started

Cause: An attempt was made to shut down the Messaging Gateway agent when it is not started.

Action: No action required.

ORA-32824: schedule exists for source string and destination string

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-32823: subscriber exists for queue string and destination string

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-32822: subscriber string is marked for removal

ORA-32822: subscriber string is marked for removal

Cause: An administration operation was attempted for a subscriber which is marked for removal. If attempting to remove a subscriber, 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-32821: subscriber queue and exception queue must have same payload type

ORA-32821: subscriber queue and exception queue must have same payload type

Cause: An operation was attempted for OUTBOUND propagation 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-32820: subscriber queue and exception queue must use same message system link

ORA-32820: subscriber queue and exception queue must use same message system link

Cause: An operation was attempted for INBOUND propagation 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-32819: AQ queue string must be a normal queue

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-32818: AQ queue string does not exist

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 existing AQ queue.

ORA-32817: message system link string is not configured with a log queue for string

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-32816: foreign queue string is referenced by a subscriber or schedule

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-32815: message system link string is referenced by a foreign queue

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-32814: propagation schedule string does not exist

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-32813: propagation schedule string already exists

ORA-32813: propagation schedule string already exists

Cause: The specified propagation schedule identifer already exists.

Action: Specify a different identifier.

ORA-32812: subscriber string does not exist

ORA-32812: subscriber string does not exist

Cause: The specified subscriber identifier does not exist.

Action: Specify an existing subscriber identifier.

ORA-32811: subscriber string already exists

ORA-32811: subscriber string already exists

Cause: The specified subscriber identifier already exists.

Action: Specify a different identifier.

ORA-32810: foreign queue string is not registered

ORA-32810: foreign queue string is not registered

Cause: The foreign queue (NAMEMSGLINK) has not been registered for this message system link.

Action: Specify the name of a registered foreign queue.

ORA-32809: foreign queue string is already registered

ORA-32809: foreign queue string is already registered

Cause: The foreign queue has already been registered for this message system link (NAMEMSGLINK).

Action: Specify a different name that is not being used for this message system link.

ORA-32808: message system link string does not exist

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-32807: message system link string already exists

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-32806: value for string is too long, maximum length is string

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 allowed length.

ORA-32805: identifier for string too long, maximum length is string characters

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 allowed length.

ORA-32804: invalid value string, string should have form string

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-32803: value for string cannot be altered

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-32802: value for string must be string

ORA-32802: value for string must be string

Cause: An invalid value was specified for a parameter.

Action: Specify the value as indicated by the message.

ORA-32801: invalid value string for string

ORA-32801: invalid value string for string

Cause: An invalid value was specified for a parameter.

Action: Specify a valid value for the parameter.

ORA-32800: internal error string

ORA-32800: internal error string

Cause: An unexpected error occurred.

Action: Contact Oracle Support Services.

ORA-32775: cannot change size attributes of read only tablespace string

ORA-32775: cannot change size attributes of read only tablespace string

Cause: An attempt was made to change size attributes of a tablespace that is read only.

Action: Change the tablespace to read or write and retry the operation.

ORA-32774: more than one file was specified for bigfile tablespace string

ORA-32774: more than one file was specified for bigfile tablespace string

Cause: More than one datafile or tempfile was specified in CREATE TABLESPACE command for a bigfile tablespace.

Action: Change command to contain only one file or create a smallfile tablespace instead.

ORA-32773: operation not supported for smallfile tablespace string

ORA-32773: operation not supported for smallfile tablespace string

Cause: An attempt was made to perform an operation which is supported only for bigfile tablespaces, e.g. resize tablespace.

Action: Use the appropriate clause of the ALTER DATABASE DATAFILE command instead.

ORA-32772: BIGFILE is invalid option for this type of tablespace

ORA-32772: BIGFILE is invalid option for this type of tablespace

Cause: An attempt was made to create a bigfile tablespace that is dictionary managed or locally managed with manual segment-space management.

Action: Either change the tablespace type to locally managed with automatic segment-space management, or create a SMALLFILE tablespace instead.

ORA-32771: cannot add file to bigfile tablespace

ORA-32771: cannot add file to bigfile tablespace

Cause: An attempt was made to add the second file to a bigfile tablespace.

Action: Do not use this command with bigfile tablespace.

ORA-32767: No server connection for this operation

ORA-32767: No server connection for this operation

Cause: The client side sql or plsql function operation requires a connection to the server, but currently no client or server connection existed.

Action: Establish a client or server connection.

ORA-32766: instr with negative offset: use varchar semantics on LOBs

ORA-32766: instr with negative offset: use varchar semantics on LOBs

Cause: The current varchar behavior is different. e.g. instr( abcd , cd , -2, 1) returns 3, whereas instr(to_clob( abcd ), cd , -2, 1) returns 0, (i.e. no match), because the reverse search starts from offset -2, which points to c and moving backward, i.e. d is ignored. This is symmetric to instr( dcba , dc ,2,1), which returns 0.

Action: ORACLE uses the same varchar semantics on LOBs (instr). Using the same example, instr(to_clob( abcd ), cd , -2, 1) will return 3 as in the varchar case.

ORA-32763: Turn off N-Pass Temp LOB cleanup

ORA-32763: Turn off N-Pass Temp LOB cleanup

Cause: None

Action: Facilitate debugging and testing or or or or or or or or or or or or or or or or or or or or or or or or or or or or SQL function on LOBs Error numbers 32766 to 32770 are reserved for SQL function on LOBs or or or or or or or or or or or or or or or or or or or or or or or or or or or or