RMAN-06201: Key Thrd Seq S Completion time Name
Cause: See RMAN-06203.
Action: No action required.
Category Archives: RMAN Database Error Messages
RMAN-06200: List of Archived Log Copies
RMAN-06200: List of Archived Log Copies
Cause: See RMAN-06203.
Action: No action required.
RMAN-06196: Oracle instance started
RMAN-06196: Oracle instance started
Cause: A STARTUP command completed successfully. This is an informational message.
Action: No action required.
RMAN-06195: auxiliary database not started
RMAN-06195: auxiliary database not started
Cause: A command was issued that requires the auxiliary database instance be started.
Action: Issue a STARTUP AUXILIARY command.
RMAN-06194: target database instance not started
RMAN-06194: target database instance not started
Cause: A command was issued that requires the target database instance be started.
Action: Issue a STARTUP command to start the instance.
RMAN-06193: connected to target database (not started)
RMAN-06193: connected to target database (not started)
Cause: The database must be started before any other RMAN commands are issued. This is an informational message.
Action: No action required.
RMAN-06192: maximum value for piecesize or setsize must be between 1 Kb and 2048 Gb
RMAN-06192: maximum value for piecesize or setsize must be between 1 Kb and 2048 Gb
Cause: Input size for maxpiecesize or maxsetsize was out of range.
Action: Specify a valid size and retry the command.
RMAN-06191: PL/SQL package string.string version string in string database is too new
RMAN-06191: PL/SQL package string.string version string in string database is too new
Cause: RMAN detected an incompatible version of the specified package.
Action: Use a newer version of Recovery Manager. Message 6439 indicates the minimum required version of Recovery Manager.
RMAN-06190: PL/SQL package string.string version string in string database is not current
RMAN-06190: PL/SQL package string.string version string in string database is not current
Cause: RMAN detected an old version of the specified package. RMAN will execute in backwards-compatible mode.
Action: No action is required, but certain features and bug fixes may not be available when RMAN runs in backwards-compatible mode. If the database is RCVCAT, then you can use the UPGRADE CATALOG command to upgrade the recovery catalog to the most current version. If the database is TARGET or AUXILIARY, then you must either upgrade the specified database or use an older version of RMAN. The files that must be run to upgrade the target or auxiliary database are DBMSRMAN.SQL and PRVTRMAN.PLB.
RMAN-06189: current DBID number does not match target mounted database (number)
RMAN-06189: current DBID number does not match target mounted database (number)
Cause: SET DBID was used to set a DBID that does not match the DBID of the database to which RMAN is connected.
Action: If the current operation is a restore to copy the database, do not mount the database. Otherwise, avoid using the SET DBID command, or restart RMAN.