10000-10999 |
RMAN-10000
|
error parsing target database connect string "string"
Cause: An invalid target connect string was supplied.
Action:
Specify a valid connect string and re-run the job. |
RMAN-10001
|
error parsing recovery catalog connect string "string"
Cause: An invalid recovery catalog connect string was supplied.
Action:
Specify a valid connect string and re-run the job. |
RMAN-10002
|
ORACLE error : string
Cause: The specified Oracle error was received. This message
should be accompanied by other error message(s) indicating the cause of the
error.
Action:
Check the accompanying errors. |
RMAN-10003
|
unable to connect to target database
Cause: Recovery manager was unable to connect to the target
database. This message should be accompanied by other error message(s)
indicating the cause of the error.
Action:
Ensure that that the target database is started, and that the connect string is
valid. |
RMAN-10004
|
unable to connect to recovery catalog
Cause: Recovery manager was unable to connect to the recovery
catalog
Action:
Ensure that that the recovery catalog is started, and that the connect string
is valid. This message should be accompanied by other error message(s)
indicating the cause of the error. |
RMAN-10005
|
error opening cursor
Cause: An error was received while trying to open a cursor. This
message should be accompanied by other error message(s) indicating the cause of
the error.
Action:
If the associated Oracle error message indicates a condition that can be
corrected, do so, otherwise contact Oracle. |
RMAN-10006
|
error running SQL statement : string
Cause: An error message was received while running the SQL
statement shown.
Action:
If the associated Oracle error message indicates a condition that can be
corrected, do so, otherwise contact Oracle. |
RMAN-10007
|
error closing cursor
Cause: An error was received while trying to close a cursor. This
message should be accompanied by other error message(s) indicating the cause of
the error.
Action:
If the associated Oracle error message indicates a condition that can be
corrected, do so, otherwise contact Oracle. |
RMAN-10008
|
could not create channel context
Cause: An error was received while trying create a channel
context. This message should be accompanied by other error message(s)
indicating the cause of the error.
Action:
If the associated Oracle error message indicates a condition that can be
corrected, do so, otherwise contact Oracle. |
RMAN-10009
|
error logging off of Oracle
Cause: An error was received while disconnecting from Oracle.
This message should be accompanied by other error message(s) indicating the
cause of the error.
Action:
This is an informational message only. |
RMAN-10010
|
error while checking for RPC completion
Cause: Recovery Manager's channel context had an error while
checking to see if a remote procedure call had completed. This message should
be accompanied by other error message(s) indicating the cause of the error.
Action:
If other error messages indicate a condition that can be corrected, do so,
otherwise contact Oracle. |
RMAN-10011
|
synchronization error while polling for rpc number,
action=string
Cause: Recovery Manager could not synchronize properly with a
remote procedure call.
Action:
This is an internal error that should not be issued. Contact Oracle Support. |
RMAN-10012
|
KGU error : string
Cause: An error occurred while initializing the KGU subsystem
Action:
This is an internal error that should not be issued. Contact Oracle Support. |
RMAN-10013
|
error initializing PL/SQL
Cause: An error occurred while initializing the PL/SQL subsystem.
Action:
This is an internal error that should not be issued. Contact Oracle Support. |
RMAN-10014
|
PL/SQL error number on line number column number : string
Cause: PL/SQL error
Action:
The text of this message will be issued by the PL/SQL subsystem. See the PL/SQL
error message manual. |
RMAN-10015
|
error compiling PL/SQL program
Cause: An error occurred while compiling a PL/SQL program.
Action:
This is an internal error that should not be issued. Contact Oracle Support. |
RMAN-10018
|
error cleaning up channel context
Cause: An error was received during inter-step cleanup of a
channel context.
Action:
This is an internal error that should not be issued. Contact Oracle Support. |
RMAN-10020
|
error initializing Recovery Manager execution layer
Cause: An error was received while initializing the Recovery
Manager execution layer in preparation for running a job. This message should
be accompanied by other error message(s) indicating the cause of the error.
Action:
If other error messages indicate a condition that can be corrected, do so,
otherwise contact Oracle. |
RMAN-10022
|
error in system-dependant sleep routine
Cause: An error was received while waiting for a remote RPC to
complete. The error occurred in the system-dependant sleep routine.
Action:
This is an internal error that should not be issued. Contact Oracle Support. |
RMAN-10023
|
RPC attempted to unrecognized package
Cause: The Recovery Manager internal RPC router received a
package name that it could not understand.
Action:
This is an internal error that should not be issued. Contact Oracle Support. |
RMAN-10024
|
error setting up for rpc polling
Cause: The Recovery Manager could not create the RPC polling
context which is required to test for RPC completion. This message should be
accompanied by other error message(s) indicating the cause of the error.
Action:
If other error messages indicate a condition that can be corrected, do so,
otherwise contact Oracle. |
RMAN-10025
|
connection is already registered for events
Cause: The Recovery Manager could not enable the target database
connection to test for RPC completion.
Action:
This is an internal error that should not be issued. Contact Oracle Support. |
RMAN-10026
|
network error number-number occurred registering connection
Cause: An network error occurred while attempting to register the
target database connection to test for RPC completion.
Action:
This is an internal error that should not be issued. The message numbers are
issued by the Sql*Net layer. Contact Oracle Support. |
RMAN-10027
|
could not locate network layer context
Cause: Recovery Manager could not locate a necessary context area
while attempting to register the target database connection to test for RPC
completion.
Action:
This is an internal error that should not be issued. Contact Oracle Support. |
RMAN-10028
|
network error number-number occurred during remote RPC
Cause: An network error occurred while waiting for a remote RPC
to complete.
Action:
This is an internal error that should not be issued. The message numbers are
issued by the Sql*Net layer. Contact Oracle Support. |
RMAN-10029
|
unexpected return code number from PL/SQL execution
Cause: PL/SQL returned an unexpected return code while executing
one channel program.
Action:
This is an internal error that should not be issued. Contact Oracle Support. |
RMAN-10030
|
RPC call appears to have failed to start on channel string
Cause: An RPC to a target database instance was issued, but was
not observed to start within 5 timeouts.
Action:
This error is probably accompanied by other error messages giving the precise
cause of the failure. |
RMAN-10031
|
RPC Error : ORA-number occurred during call to string.string
Cause: An RPC to the target database or recovery catalog database
encountered an error.
Action:
This error is accompanied with the error message from the server where the
error occurred. |
RMAN-10032
|
unhandled exception during execution of job step number :
string
Cause: An unhandled PL/SQL execption occurred during a job step.
Action:
This error is accompanied by the error messages describing the exception. |
RMAN-10033
|
error during compilation of job step number : string
Cause: PL/SQL detected a problem during the compilation of a job
step
Action:
This error message is accompanied by the error messages describing. |
RMAN-10034
|
unhandled exception during execution of job step number, error
unknown
Cause: PL/SQL detected an unhandled exception during execution of
a job step, but no further information available
Action:
none. |
RMAN-10035
|
exception raised in RPC : string
Cause: A call to a remote package resulted in an exception.
Action:
The exception should indicate what went wrong. |
RMAN-10036
|
RPC call ok on channel string
Cause: This is just an informational message. It should be
preceeded by message 10030.
Action:
No action is required. |
RMAN-10037
|
RPC anomaly detected on channel string, upinblt=number
Cause: This is an debugging message and can be ignored.
Action:
No action is required. |
RMAN-10038
|
database session for channel string terminated unexpectedly
Cause: The database connection for the specified channel no
longer exists. Either the session was terminated by some external means or the
channel terminated because of an internal error.
Action:
Check for an oracle trace file for detailed information on why the session
terminated. |
RMAN-10039
|
error encountered while polling for RPC completion on channel
string
Cause: This error should be accompanied by other errors giving
the cause of the polling error.
Action:
Check the accompanying errors. |
RMAN-10040
|
asynchronous support not detected, RMAN will run synchronously
Cause: The database connection does not support asynchronous
operation, so RMAN will not multi-task work among multiple channels. Multiple
channels can still be allocated, but they will not run work concurrently.
Action:
Use a connection type that supports asynchronous operations. |
RMAN-10041
|
Could not re-create polling channel context following failure.
Cause: The RPC polling context, which is required to test for RPC
completion, failed and Recovery Manager could not re-create this channel. This
message should be accompanied by other error messages indicating the cause of
the error.
Action:
If other error messages indicate a condition that can be corrected, do so,
otherwise contact Oracle. |
