4000-4999 |
RMAN-04000
|
memory allocation failure
Cause:A memory allocation request could not be satisified.
Action:
Increase the amount of memory available to RMAN. |
RMAN-04001
|
heap initialization failure
Cause:This message should be accompanied by other error
message(s) indicating the cause of the error.
Action:
Check the accompanying errors. |
RMAN-04002
|
ocipi failed, ORA-string
Cause:OCI process level initialization failed.
Action:
This error should not normally occur. |
RMAN-04003
|
ociinit failed
Cause:The call to OCIEnvInit failed.
Action:
This error should not normally happen. Contact Oracle Customer Support. |
RMAN-04004
|
error from recovery catalog database: string
Cause:Oracle error signaled by catalog database. This message
should be accompanied by other error message(s) indicating the cause of the
error.
Action:
Check the accompanying errors. |
RMAN-04005
|
error from target database: string
Cause:Oracle error signaled by target database. This message
should be accompanied by other error message(s) indicating the cause of the
error.
Action:
Check the accompanying errors. |
RMAN-04006
|
error from auxiliary database: string
Cause:Oracle error signaled by auxiliary database. This message
should be accompanied by other error message(s) indicating the cause of the
error.
Action:
Check the accompanying errors. |
RMAN-04007
|
WARNING from recovery catalog database: string
Cause:Non fatal Oracle error signaled by catalog database. This
message should be accompanied by other error message(s) indicating the cause of
the error.
Action:
Check the accompanying errors. |
RMAN-04008
|
WARNING from target database: string
Cause:Non fatal Oracle error signaled by target database. This
message should be accompanied by other error message(s) indicating the cause of
the error.
Action:
Check the accompanying errors. |
RMAN-04009
|
WARNING from auxiliary database: string
Cause:Non fatal Oracle error signaled by auxiliary database. This
message should be accompanied by other error message(s) indicating the cause of
the error.
Action:
Check the accompanying errors. |
RMAN-04010
|
target database Password:
Cause:No password was provided for the target database.
Action:
Provide target database password. |
RMAN-04011
|
recovery catalog database Password:
Cause:No password was provided for the recovery catalog database.
Action:
Provide recovery catalog database password. |
RMAN-04012
|
auxiliary database Password:
Cause:No password was provided for the auxiliary database.
Action:
Provide auxiliary database password. |
RMAN-04013
|
must connect before startup
Cause:A STARTUP command was attempted before connecting to the
database.
Action:
Connect to database before attempting STARTUP command. |
RMAN-04014
|
startup failed: string
Cause:The database failed to startup.
Action:
The cause of the failure is included in the error message. Correct the cause of
the failure and retry the startup command. |
RMAN-04015
|
error setting target database character set to string
Cause:An error was received while setting the session character
set in the target database.
Action:
This error should not normally happen. Contact Oracle Customer Support. |
RMAN-04016
|
could not get OCI error handle
Cause:An error was received while initializing the OCI layer.
Action:
This error should not normally happen. Contact Oracle Customer Support. |
RMAN-04017
|
startup error description: string
Cause:of failure.
Action:
No action is required. |
RMAN-04020
|
target database name "string" does not match channel's name:
"string"
Cause:The CONNECT clause in the ALLOCATE command has resulted in
a connection to a database which is not the same as the one used to connect to
the target database.
Action:
Verify that the CONNECT string connects to the same database as the one
specified in the TARGET connection for the CONNECT command. |
RMAN-04021
|
target database DBID string does not match channel's DBID
string
Cause:The CONNECT clause in the ALLOCATE command has resulted in
a connection to a database which is not the same as the one used to connect to
the target database.
Action:
Verify that the CONNECT string connects to the same database as the one
specified in the TARGET connection for the CONNECT command. |
RMAN-04022
|
target database mount id string does not match channel's mount
id string
Cause:The CONNECT clause in the ALLOCATE command has resulted in
a connection to a database which is not the same as the one used to connect to
the target database.
Action:
Verify that the CONNECT string connects to the same database as the one
specified in the TARGET connection for the CONNECT command. |
RMAN-04024
|
starting Oracle instance without parameter file for retrival of
spfile
Cause:The instance could not be started because no default
parameter file (either PFILE or SPFILE) could be found. The instance will be
started in restricted mode with default parameters.
Action:
None - this is an informational message. |
RMAN-04025
|
unable to generate a temporary file
Cause:Creation of a temporary file failed. If could be that the
system does not have enough resources (disk space, memory or similar).
Action:
Verify and free some system resources memory and try again. |
RMAN-04026
|
unable to open a temporary file: "string"
Cause:Opening of a temporary file failed. If could be that the
system does not have enough resources (disk space, memory or similar).
Action:
Verify and free some system resources memory and try again. |
RMAN-04027
|
unable to write to a temporary file: "string"
Cause:Writing to a temporary file failed. If could be that the
system does not have enough resources (disk space, memory or similar).
Action:
Verify and free some system resources memory and try again. |
RMAN-04031
|
initialization parameters used for automatic instance: string
Cause:This is an informational message only.
Action:
No action is required. |
RMAN-04032
|
using contents of file string
Cause:The specified file was included as part of the auxiliary
database parameter file. This is an informational message.
Action:
No action is required. |
RMAN-04033
|
cannot open auxiliary parameter file string
Cause:An auxiliary parameter file was specified with SET
AUXILIARY INSTANCE PARAMETER FILE command but the specified file cannot be
found.
Action:
Set the parameter file to an existen file or retry the command without setting
AUXILIARY INSTANCE PARAMETER FILE. |
