Keywords

Table-level recovery and renaming

Applied Products

• AnyBackup 6.0.x
• AnyBackup 5.0.x

Symptoms

The Oracle stand-alone database table-level recovery task under Linux environment is initiated on the AnyBackup management console. The task execution fails. The following error message is prompted in the execution output:

Oracle recovery exception. (Error provider: oracleBackup, error value: e050001b, error location: ncOracleRestoreSchedule.cpp: 52)Additional information: The table selected in Oracle table-level recovery: SYS.SCHOOL1 exists in the original production database. For data operation safety, please rename this table in the backup production database. (Error provider: oracleBackup, error value: e0500017, error location: ncOracleDatabaseManager. cpp: 812)

Impact

AnyBackup failed to complete the Oracle database table-level recovery.

Cause

The table selected in Oracle table-level recovery:<table name>still exists in the original production database. For data security, the table cannot be directly overwritten during recovery, resulting in recovery failure.

Resolution

To solve this problem, you need to rename the table in the original database and restore it. The steps are as follows:

Warning: The renaming table is a high-risk operation. Please confirm with the database administrator before executing; Oracle table-level recovery can only be restored to the original machine. Please confirm with the database administrator before performing task recovery.

1. Log in to the Oracle database server on a different machine at the command line, execute the following command, log in to the restored Oracle database and rename the table to be restored

su - oracle

export ORACLE_SID=sid

sqlplus / as sysdba

alter table school1 rename to school1bak;

Note: sid is the database instance name.

2. Restart the recovery task on the AnyBackup management console.

More information

Oracle table-level recovery should ensure that there is no table with the same name in the database, otherwise the recovery will fail. It is recommended to rename or drop related tables in the production database before recovery.