ORA-29314: tablespace string is not OFFLINE FOR RECOVER nor READ ONLY

ORA-29314: tablespace string is not OFFLINE FOR RECOVER nor READ ONLY

Cause: Tablespace clean SCN is either 0 or invalid.

Action: ALTER the tablespace OFFLINE FOR RECOVER.

ORA-29313: tablespace string cannot be imported twice

ORA-29313: tablespace string cannot be imported twice

Cause: This is an internal error.

Action: Contact your database administrator.

ORA-29312: changes by release string cannot be used by release string, type: string

ORA-29312: changes by release string cannot be used by release string, type: string

Cause: A point-in-time tablespace was chosen to perform the recovery, but the current database is not compatible with the database that was used to create the point-in-time tablespace.

Action: Choose a point-in-time and retry the operation.

ORA-29311: export dump file was not generated by this database, string does not match

ORA-29311: export dump file was not generated by this database, string does not match

Cause: The export dump files were imported to an incorrect database.

Action: Open the correct production database and try the import again.

ORA-29310: database is not open, or opened as a clone

ORA-29310: database is not open, or opened as a clone

Cause: Either the database was not open, or an attempt was made to open it as a cloned database.

Action: Open the production database instead.

ORA-29309: export dump file was generated by different version of DBMS_PITR package

ORA-29309: export dump file was generated by different version of DBMS_PITR package

Cause: The version of DBMS_PITR is different from the version of the cloned database.

Action: Load the version of DBMS_PITR which matches the version of the cloned database.

ORA-29308: view TS_PITR_CHECK failure

ORA-29308: view TS_PITR_CHECK failure

Cause: Some objects which crossed the boundary of the recovery set were not allowed in the tabelspace point-in-time recovery.

Action: Query TS_PITR_CHECK and resolve the boundary crossing objects.