Troubleshooting: Oracle Database Servers
Creation Date: July 29, 2009
Revision Date: October 02, 2015
Product: DS‑Client
Summary
This article provides information for troubleshooting Oracle database backup sets.
RMAN reports file corruptions during backup
Problem
DS-Client backup of Oracle server fails with the following RMAN error:
ORA-19566: Exceeded Limit Of 0 Corrupt Blocks From Backup
More information
For more information, refer to the Oracle documentation: Metalink document #457422.1
Oracle restore fails
Problem
DS-Client restore of Oracle server fails with the following error:
ORA-01152: File %s was not restored from a sufficiently old backup
More information
For more information, refer to the Oracle documentation: Metalink document #243264.1 (Creating a Database From an Existing Database Fails with an ORA-01152 on Alter Database Open Resetlogs)
Oracle backup reports error ORA-12154
Problem
DS-Client backup of Oracle server reports the following error:
ORA-12154: TNS: Could not resolve the connect identifier specified
More information
This occurs if the Oracle Database Service Name has changed since this backup set was created. When you define an Oracle backup set, each backup item contains the Service Name as part of the path (e.g. an Oracle DB with the Service Name “orcl” might have backup items “orcl\SYSTEM” or “orcl\*”). If the Service Name is changed, DS-Client will fail to connect to the Oracle database with the ORA-12154 error.
Resolution
This is not likely to occur often (or at all), but in the event such a change is made, you must migrate the backup set to change the <oracle_service_name>\item_name from the old Oracle Service Name to the new one.
To migrate the backup set:
1. Right-click the Oracle backup set and select Migrate.... The Migrate Backup Set wizard appears.
2. Select the computer to backup. In this situation, this will be the same machine as the original backup set.
3. When you click Next, you are prompted to enter the Oracle Database credentials.
• Adjust the backup set’s database credentials to use the new service name.
4. Follow the rest of the Wizard screens to re-specify the backup set items and complete the migration. Once migration is complete, try backing up again to verify you do not get the ORA-12154 error.
Another alternative is you can create an entirely new backup set and stop using the old one.
Oracle 12c Known Issues (Linux & Windows)
The following are known issues that are specific to Oracle version 12c running on either Windows or Linux.
For Oracle version 12c, you may not see the PDB$SEED item in the New Backup Set Wizard because the parameter EXCLUDE_SEED_CDB_VIEW is set to TRUE.
• To enable view and selection of this item, set this parameter’s value to FALSE. Enter the SQL*Plus command line and type the following:
SQL> alter system set ‘EXCLUDE_SEED_CDB_VIEW’ = FALSE scope=both;
• When restoring the whole CDB with controlfile, you must remove all the autobackup controlfiles under the directory “autobackup”. (If the flash_recovery_area is configured, the “autobackup” directory is in the “flash_recovery_area”.)
• Remove any old controlfiles and old archived logs.
• If you need to restore only the PDB$SEED from an Oracle 12 backup, you must close it on the target first with the following SQL*Plus command lines:
Alter session set “_oracle_script”=TRUE;
Alter pluggable database PDB$SEED close immediate instances=all;
Oracle 12c Known Issues (Windows)
The following are known issues that are specific to Windows Oracle version 12c.
• The Oracle owner must be a member of the Windows Administrators group.
• The user who performs the Oracle 12C installation is the ‘Oracle owner’. Make sure this user is a member of the Windows Administrators group.
• If the Oracle owner is not a member of the Windows Administrators group, any backup will fail when DS-Client tries to back up the Controlfile.
• Backup of the SYSTEM tablespace fails because the RMAN setting for the Controlfile Autobackup parameter is OFF.
• Change the setting to ON with the following command:
RMAN> configure controlfile autobackup ON;
Oracle 12c Known Issues (Linux)
The following are known issues that are specific to Linux Oracle version 12c.
Problem: DS-Client using DS-PIPE fails to back up the controlfile
• By default, threaded execution is OFF on the Oracle server.
• If threaded execution is enabled on the Oracle server, DS-Client using DS-PIPE will fail to back up the controlfile.
Workaround 1
Create the backup set using any other protocol than DS-PIPE. You can use Local File System, NFS, or UNIX-SSH.
Workaround 2
When threaded execution is enabled, backup processes from DS-Client using DS-PIPE need to go through a listener that has been specifically configured in the listener.ora file.
You probably do not want to change the default listener configuration, therefore you can:
• Create a new listener (e.g. LISTENER2) in the listener.ora file and set the following configuration line for it:
DEDICATED_THROUGH_BROKER_LISTENER2=OFF
• Create a new Oracle service name in the tnsnames.ora file and configure it to use this new listener (port).
• Use this service name when you create the Oracle backup set and enter the database credentials.