12000-12999 |
RMAN-12000
|
execution layer initialization failed
Cause: This message should be accompanied by other error
message(s) indicating the cause of the error.
Action:
Check the accompanying errors. |
RMAN-12001
|
could not open channel string
Cause: An ALLOCATE CHANNEL command could not be processed.
Action:
This message should be accompanied by other error message(s) indicating the
cause of the error. |
RMAN-12005
|
error during channel cleanup
Cause: This message should be accompanied by other error
message(s) indicating the cause of the error.
Action:
Check the accompanying errors. |
RMAN-12007
|
cannot allocate more than number channels
Cause: The maximum number of RMAN channels has been exceeded.
Note that one channel is reserved for RMAN.
Action:
Allocate fewer channels. Contact Oracle if you have a need for more channels in
a single job. |
RMAN-12008
|
could not locate backup piece string
Cause: There was at least 1 backup set that could not be accessed
by any of the allocated channels.
Action:
Allocate additional channels on other nodes of the cluster. |
RMAN-12009
|
command aborted because some backup pieces could not be located
Cause: Same as 7008.
Action:
Refer to 7008. |
RMAN-12010
|
automatic channel allocation initialization failed
Cause: This message should be accompanied by other error
message(s) indicating the cause of the error.
Action:
Check the accompanying errors. |
RMAN-12011
|
multiple records for default device type found in catalog
Cause: configuration for default device type not consistent.
Action:
re-run CONFIGURE DEFAULT DEVICE TYPE command to set device type. |
RMAN-12012
|
multiple records for string parallelism found in catalog
Cause: configuration for device parallelism is not consistent.
Action:
re-run CONFIGURE PARALLELISM command for device to set parallelism. |
RMAN-12013
|
multiple records for string channel number found in catalog
Cause: configuration for the channel is not consistent.
Action:
re-run CONFIGURE CHANNEL command to configure this channel. |
RMAN-12014
|
multiple records for default channel configuration for string
found in catalog
Cause: configuration for the channel is not consistent.
Action:
re-run CONFIGURE CHANNEL command to configure the channel. |
RMAN-12015
|
configuration for string channel number is ignored
Cause: This is an informational message only. Parallelism for the
device is less than associated channel number.
Action:
To use this configuration increase parallelism for this device. To clear this
configuration use CONFIGURE CHANNEL... CLEAR command. |
RMAN-12016
|
using channel string
Cause: This is an informational message only.
Action:
No action is required. |
RMAN-12017
|
could not locate pieces of backupset key string
Cause: No copies of the specified backupset key can be accessed
on any of the allocated channels.
Action:
Allocate additional channels on other nodes of the cluster, or, if the backup
pieces have been deleted, use the CROSSCHECK BACKUP command to correct the
recovery catalog entries. |
RMAN-12018
|
channel string disabled, job failed on it will be run on
another channel
Cause: This is an informational message displayed whenever a
retriable error occurs for the job and there are channels available to run this
step.
Action:
No action is required. |
RMAN-12019
|
continuing other job steps, job failed will not be re-run
Cause: This is an informational message displayed whenever there
is a non-retriable error occured for the job.
Action:
No action is required. |
RMAN-12020
|
error on step filtered for normal output string
Cause: This message is added when stacking errors for failed jobs
after channel failover was performed. It will be filtered from normal output.
Action:
No action is required. |
