Wednesday, 18 April 2012

ORA-24088: AQ Agent string does not exist

ORA-24088: AQ Agent string does not exist

Cause: This AQ Agent does not exist

Action: Specify a valid AQ agent. Check the DBA_AQ_AGENTS view for a list of valid aq agents

ORA-24087: Invalid database user string

ORA-24087: Invalid database user string

Cause: An invalid database username was specified

Action: Specify a valid database user

ORA-24086: cannot create a 8.0 compatible string queue

ORA-24086: cannot create a 8.0 compatible string queue

Cause: An attempt was made to create a 8.0 compatible queue table and enable a feature that is supported only on 8.1 style queue tables

Action: This feature is not supported

ORA-24085: operation failed, queue string is invalid

ORA-24085: operation failed, queue string is invalid

Cause: An attempt was made to enqueue, dequeue or administer a queue which is invalid. This could have occured because the payload type of the queue s queue table was dropped.

Action: Drop the queue table setting the force option to true.

ORA-24084: DBLINK name in address field of agent string is not unique within the first 24 bytes

ORA-24084: DBLINK name in address field of agent string is not unique within the first 24 bytes

Cause: Advanced Queuing requires that the agent s dblink name should be unique within the first 24 bytes (for 8.0 compatible queuetables)

Action: Specify a dblink name that is unique within the first 24 bytes or migrate to 8.1 compatible queuetables where this restriction is not there.

ORA-24083: cannot specify remote subscribers for string QUEUE string

ORA-24083: cannot specify remote subscribers for string QUEUE string

Cause: An add_subscriber call with a non-null address field was issued on a queue which does not support remote subscribers. Remote subscribers are not supported for NON_PERSISTENT QUEUES.

Action: Specify a null address field and retry the call.

ORA-24082: propagation may still be happening for the schedule for QUEUE string and DESTINATION string

ORA-24082: propagation may still be happening for the schedule for QUEUE string and DESTINATION string

Cause: The snapshot process executing the propagation schedule did not respond to the disable propagation command.

Action: Make sure that the job for the propagation schedule has been ended.