RMAN-06410: cannot use command when channels are allocated
Cause: An attempt was made to issue a command that can be used only when there are no allocated channels.
Action: Do not use the command, or de-allocate channels and use the command when no channels are allocated.
RMAN-06409: LIKE clause in LIST BACKUP OF ARCHIVELOG is not supported
Cause: LIST BACKUP OF ARCHIVELOG LIKE was used, which is not supported.
Action: Remove LIKE clause from command.
RMAN-06408: recovery catalog upgraded to version string
Cause: This is an informational message issued by the UPGRADE CATALOG command. It indicates the version of the recovery catalog schema to which the recovery catalog was just upgraded. Note that this version number may not reflect the version number of your RMAN executable or target database, because the recovery catalog schema is not changed with each Oracle release.
Action: No action required.
RMAN-06406: deleted archivelog
Cause: This is an informational message.
Action: No action required.
RMAN-06405: database closed
Cause: This is an informational message.
Action: No action required.
RMAN-06404: database dismounted
Cause: This is an informational message.
Action: No action required.
RMAN-06403: could not obtain a fully authorized session
Cause: The most likely cause of this error is that one of the databases to which RMAN had previously connected is not started or has been shut down. Other error messages should identify exactly which database is the problem.
Action: Start the database that is causing the problem.
RMAN-06402: Oracle instance shut down
Cause: This is an informational message.
Action: No action required.
RMAN-06401: database is already started
Cause: A STARTUP command without the FORCE option was issued, but the target database is already started.
Action: Use the FORCE option if you want to restart the database.
RMAN-06400: database opened
Cause: This is an informational message.
Action: No action required.