Saturday 5 May 2012

ORA-27374: insufficient privileges on event source queue

ORA-27374: insufficient privileges on event source queue

Cause: The job owner had insufficient privileges on the event source queue that was specified for the job.

Action: The job owner has to have dequeue privileges on event source queue or he has to have manage queue or dequeue any queue system privileges. Make sure one of these privileges is granted.

ORA-27373: unknown or illegal event source queue

ORA-27373: unknown or illegal event source queue

Cause: The source queue specified for the event based job or event based schedule was either not found or was of the wrong type.

Action: Check if the queue exists. If it does make sure it is a multiple consumer queue and it is a post 8.1 compatible queue. Single consumer queues and old-style queues cannot be used as event source queues.

ORA-27372: length of action and arguments exceeds platform limit string

ORA-27372: length of action and arguments exceeds platform limit string

Cause: The total length of the job or program action and the arguments exceeds the platform limit specified.

Action: Reduce the total length by specifying fewer and or or shorter arguments

ORA-27371: jobs of type EXECUTABLE are not supported on this platform

ORA-27371: jobs of type EXECUTABLE are not supported on this platform

Cause: The user tried to create a job or program of type EXECUTABLE on a platform where such jobs are not supported.

Action: Switch to a different platform or create a different type of job or program.

ORA-27370: job slave failed to launch a job of type EXECUTABLE

ORA-27370: job slave failed to launch a job of type EXECUTABLE

Cause: The scheduler ran into an error when the job slave tried to start a job of type EXECUTABLE. The rest of the error stack will provide more detailed information on what the exact problem was.

Action: Correct the problem specified in the error stack and reschedule the job.

ORA-27369: job of type EXECUTABLE failed with exit code: string

ORA-27369: job of type EXECUTABLE failed with exit code: string

Cause: A problem was encountered while running a job of type EXECUTABLE. The cause of the actual problem is identified by the exit code.

Action: Correct the cause of the exit code and reschedule the job.

ORA-27367: program string.string associated with this job is disabled

ORA-27367: program string.string associated with this job is disabled

Cause: An attempt was made to run a job whose program has been disabled.

Action: Reenable the program before running the job.

ORA-27366: job string.string is not running

ORA-27366: job string.string is not running

Cause: An attempt was made to stop a job that was not running.

Action: Verify the status of the job. If the job is running but this message is still being returned, contact Oracle support.

ORA-27365: job has been notified to stop, but failed to do so immediately

ORA-27365: job has been notified to stop, but failed to do so immediately

Cause: The job specified in the stop_job command cannot be stopped immediately(because it is rolling back or blocked on a network operation), but it has been notified to stop. This means it will be stopped as soon as possible after its current uninterruptable operation is done.

Action: No action is required for the job to be stopped, but calling stop_job with force (if you have the privilege) may cause the job to be stopped sooner.

ORA-27303: additional information: string

ORA-27303: additional information: string

Cause: OS system call error

Action: contact Oracle Support

ORA-27302: failure occurred at: string

ORA-27302: failure occurred at: string

Cause: OS system call error

Action: contact Oracle Support

ORA-27301: OS failure message: string

ORA-27301: OS failure message: string

Cause: OS system call error

Action: contact Oracle Support

ORA-27300: OS system dependent operation:string failed with status: string

ORA-27300: OS system dependent operation:string failed with status: string

Cause: OS system call error

Action: contact Oracle Support

ORA-27250: OS system call failure

ORA-27250: OS system call failure

Cause: OS system call failed

Action: check errno and contact Oracle support

ORA-27230: OS system call failure

ORA-27230: OS system call failure

Cause: OS system call failed

Action: check errno and contact Oracle support

ORA-27216: skgfgsmcs: sbtinfo2 returned a malformed response

ORA-27216: skgfgsmcs: sbtinfo2 returned a malformed response

Cause: The media management software returned a malformed response during an sbtinfo2() call.

Action: Contact the media management vendor.

ORA-27215: skgfgsmcs: sbtinfo2 returned unknown file

ORA-27215: skgfgsmcs: sbtinfo2 returned unknown file

Cause: During an sbtinfo2() call, the media management software returned information about an unknown backup file.

Action: Contact the media management vendor.

ORA-27214: skgfrsfe: file search failed

ORA-27214: skgfrsfe: file search failed

Cause: The FindNextFile function returned unxpected error.

Action: Check errors on the error stack for an explanation why the search for files could not be successfully executed.

ORA-27213: failed to unload Media Management Library

ORA-27213: failed to unload Media Management Library

Cause: dlclose for media library returned error. See Additional Additional information for error code.

Action: contact Oracle Support.

ORA-27212: some entrypoints in Media Management Library are missing

ORA-27212: some entrypoints in Media Management Library are missing

Cause: media library does not have one of the following entrypoints : sbtinfo, sbtread, sbtwrite, sbtremove, sbtopen, sbtclose, sbtinit

Action: Retry the command with proper media library.

ORA-27211: Failed to load Media Management Library

ORA-27211: Failed to load Media Management Library

Cause: User-supplied SBT_LIBRARY or libobk.so could not be loaded. Call to dlopen for media library returned error. See Additional information for error code.

Action: Retry the command with proper media library. Or re-install Media management module for Oracle.

ORA-27210: syntax error in device PARMS

ORA-27210: syntax error in device PARMS

Cause: User-supplied PARMS value has incorrect syntax.

Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn

ORA-27209: syntax error in device PARMS - unknown keyword or missing =

ORA-27209: syntax error in device PARMS - unknown keyword or missing =

Cause: User-supplied PARMS value has incorrect syntax. The server expected to find ENV or BLKSIZE, but found an unknown keyword.

Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn

ORA-27208: syntax error in device PARMS - environment variable value missing

ORA-27208: syntax error in device PARMS - environment variable value missing

Cause: User-supplied PARMS value has incorrect syntax.

Action: Retry the command with correct syntax: ENV=(var1=val1,var2=val2,..)

ORA-27207: syntax error in device PARMS - parentheses mismatch or missing

ORA-27207: syntax error in device PARMS - parentheses mismatch or missing

Cause: User-supplied PARMS value has incorrect syntax.

Action: Retry the command with correct syntax: ENV=(..) BLKSIZE=nnnn

ORA-27206: requested file not found in media management catalog

ORA-27206: requested file not found in media management catalog

Cause: A backup file used in a recovery manager catalog maintenance command was not found in the media management catalog.

Action: Retry the command with a different file.

ORA-27205: skgfpcn: sbtpccancel returned error

ORA-27205: skgfpcn: sbtpccancel returned error

Cause: sbtpccancel returned an error. This happens during a proxy restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27204: skgfpqr: sbtpcqueryrestore returned error

ORA-27204: skgfpqr: sbtpcqueryrestore returned error

Cause: sbtpcqueryrestore returned an error. This happens during a proxy restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27203: skgfpqb: sbtpcquerybackup returned error

ORA-27203: skgfpqb: sbtpcquerybackup returned error

Cause: sbtpcquerybackup returned an error. This happens during a proxy backup.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27202: skgfpen: sbtpcend returned error

ORA-27202: skgfpen: sbtpcend returned error

Cause: sbtpcend returned an error. This happens during a proxy backup or restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27201: skgfpcm: sbtpccommit returned error

ORA-27201: skgfpcm: sbtpccommit returned error

Cause: sbtpccommit returned an error. This happens during a proxy backup or restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27200: skgfpgo: sbtpcstart returned error

ORA-27200: skgfpgo: sbtpcstart returned error

Cause: sbtpcstart returned an error. This happens during a proxy backup or restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27199: skgfpst: sbtpcstatus returned error

ORA-27199: skgfpst: sbtpcstatus returned error

Cause: sbtpcstatus returned an error. This happens during a proxy backup or restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27198: skgfpvl: sbtpcvalidate returned error

ORA-27198: skgfpvl: sbtpcvalidate returned error

Cause: sbtpcvalidate returned an error. This happens during a proxy backup or restore.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27197: skgfprs: sbtpcrestore returned error

ORA-27197: skgfprs: sbtpcrestore returned error

Cause: sbtpcrestore returned an error. This happens when a proxy restore is begun.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27196: skgfpbk: sbtpcbackup returned error

ORA-27196: skgfpbk: sbtpcbackup returned error

Cause: sbtpcbackup returned an error. This happens when a proxy backup is begun.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27195: proxy copy not supported

ORA-27195: proxy copy not supported

Cause: An attempt was made to do a proxy backup or restore, but the media management software installed with Oracle does not support proxy copy.

Action: Re-run the backup in non-proxy mode, or contact the media management vendor if the software is supposed to support proxy copy.

ORA-27194: skgfdvcmd: sbtcommand returned error

ORA-27194: skgfdvcmd: sbtcommand returned error

Cause: sbtcommand returned an error. This happens when an rman SEND command is issued.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27193: sbtinfo2 did not return volume label

ORA-27193: sbtinfo2 did not return volume label

Cause: sbtinfo2 did not return the volume label information for the backup file that was just created.

Action: This is an internal error in the media management product. Contact the media management vendor.

ORA-27192: skgfcls: sbtclose2 returned error - failed to close file

ORA-27192: skgfcls: sbtclose2 returned error - failed to close file

Cause: sbtclose2 returned an error. This happens while closing a backup file during a backup or restore operation.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27191: sbtinfo2 returned error

ORA-27191: sbtinfo2 returned error

Cause: sbtinfo2 returned an error. This happens while retrieving backup file information from the media manager s catalog.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27190: skgfrd: sbtread2 returned error

ORA-27190: skgfrd: sbtread2 returned error

Cause: sbtread returned an error. This happens while reading a backup file during a restore operation.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27166: tried to join current thread

ORA-27166: tried to join current thread

Cause: A thread in the program tried to join itself.

Action: This is an internal error; contact Oracle support.

ORA-27165: tried to join thread that does not exist

ORA-27165: tried to join thread that does not exist

Cause: The program tried to join a thread that does not exist.

Action: This is an internal error; contact Oracle support.

ORA-27164: tried to join detached thread

ORA-27164: tried to join detached thread

Cause: The program tried to join a detached thread.

Action: This is an internal error; contact Oracle support.

ORA-27163: out of memory

ORA-27163: out of memory

Cause: The program ran out of memory when allocating a temporary data structure.

Action: Increase the amount of memory on the system.

ORA-27162: thread creation failed

ORA-27162: thread creation failed

Cause: The program was unable to create a thread.

Action: Check errno and contact Oracle support.

ORA-27161: request for Oracle binary information failed

ORA-27161: request for Oracle binary information failed

Cause: The program was unable to get information about the Oracle binary.

Action: Check for additional errors and contact Oracle support.

ORA-27160: process requested to perform operation

ORA-27160: process requested to perform operation

Cause: The current process was requested to perform an operation by another process.

Action: This is used internally; no action is required.

ORA-27159: failure setting process scheduling priority

ORA-27159: failure setting process scheduling priority

Cause: Oracle was unable to set the scheduling priority desired.

Action: Consult the Oracle Administrator s Guide.

ORA-27158: process control failure

ORA-27158: process control failure

Cause: Oracle was unable to set the specified process control.

Action: Consult the Oracle Administrator s Guide.

ORA-27157: OS post or wait facility removed

ORA-27157: OS post or wait facility removed

Cause: the post or wait facility for which the calling process is awaiting

Action: check errno and contact Oracle Support

ORA-27156: request for process information failed

ORA-27156: request for process information failed

Cause: internal error

Action: contact Oracle Support

ORA-27155: could not execute file

ORA-27155: could not execute file

Cause: OS system call failed

Action: check errno and contact Oracle Support

ORA-27154: post or wait create failed

ORA-27154: post or wait create failed

Cause: internal error, multiple post or wait creates attempted simultaneously

Action: check errno and contact Oracle Support

ORA-27153: wait operation failed

ORA-27153: wait operation failed

Cause: OS system called failed

Action: check errno contact Oracle Support

ORA-27152: attempt to post process failed

ORA-27152: attempt to post process failed

Cause: OS system call failed

Action: check errno and contact Oracle Support

ORA-27151: buffer not large enough to hold process ID string

ORA-27151: buffer not large enough to hold process ID string

Cause: internal error

Action: contact Oracle Support

ORA-27150: attempt to notify process of pending oradebug call failed

ORA-27150: attempt to notify process of pending oradebug call failed

Cause: OS system call

Action: check errno contact Oracle Support

ORA-27149: assignment out of range

ORA-27149: assignment out of range

Cause: internal error, requested conversion too large for type

Action: contact Oracle Support