Backup | Restore |
The following section provides information on troubleshooting backups.
Increase in sbtio.log file size |
Sometimes, jobs fail due to increase in the size of sbtio.log file in the $UDUMP directory. To resolve this, set the size limit for thesbtio.log file using the sMAXORASBTIOLOGFILESIZE registry key. Once the specified size limit is reached, the sbtio.log file gets pruned automatically. |
Command Line Backup Failures |
|
Sometimes, the third party command line jobs may hang when you perform
large backups and restores. This happens since ClOraControlAgent updates the job manager for every 100MB data transfer and this causes the thread failure for large backups/ restores after transferring some of the data. The following exception will be seen in the clOraControlAgent.log: 5710030 304 02/22
03:47:23 608119 OraAgentBase::NotifyCommServeJobContinue() - m_jobObject->setUnCompBytesToAdd(105119744)
... You can set
sBYTESDIFFMBS registry key <value> in MBs in OracleAgent/.properties. |
|
Offline backups fails when using lights out script |
|
Time Out Failures | The default time for resources to allocate streams during RMAN command line backups is 86400 seconds (i.e., 24 hours). If a backup fails due to a timeout being reached, you can configure the sALLOCATESTREAMSECS registry key to increase the waiting time period. |
Backup Failures |
|
Backup Fails on Red Hat Enterprise Linux 4 with oracle version 10.1.0.5 32Bit |
Issue:The backup may fail with the following error on Red Hat Enterprise Linux 4 with oracle version 10.1.0.5 32Bit as there is a known oracle issue with libunwind.so.3 file: channel ch1: starting
piece 1 at Jul 12 2013 16:46:08 Resolution:Upgrade your oracle version from 10.1.x to 10.2 to avoid the backup failure on Red Hat Enterprise Linux 4. |
Database block corruption | Oracle backups fail with the following error: LISTING 2: r_20030520213618.log RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on d1 channel at 05/20/2003 21:36:26 ORA-19566: exceeded limit of 0 corrupt blocks for file /u01/app/Oracle/oradata/MRP/sales_data_01.dbf Make sure that the maximum value for database block corruptions is set for the backup. It is recommended that you set this value to match the number of corrupted database blocks identified by RMAN for the database file being backed up. |
Backups fail intermittently on Linux clients | On Linux clients, if the libobk.so
library fails to load, the backups may fail. As a workaround, do the following steps:
This will ensure that the libobk.so library is loaded so that backups for Oracle on Linux can run successfully. |
Backup fails on Windows Clients | Make sure that the Oracle user is part of administrator
group. If the user is not part of administrator group, assign group permissions
for the user as follows:
|
Log backups failure |
|
Backup fails on Linux clients because of UNKNOWN Instance Status |
Backups may fail on Linux clients if the Oracle instance status is shown
as UNKNOWN on CommCell Console.
To resolve this issue, make sure the nproc value in /etc/security/limits.d/90-nproc.conf file is greater than 1024. |
Shared Memory Error |
Issue:
The backup failed because the shared memory on the HP-UX PA-RISC client has not been configured per operational guidelines. Resolution:Add the DisableIPC_GLOBAL file in the /apps/simpana/Base directory on the client where the backup failed.
|
If you are experiencing performance issues during backup, you can troubleshoot them by enabling logging of performance details in the log files. These performance counters contain information that help in resolving the performance related issues during backups.
Registry Key | Location | Supported Values |
sORASBTPERFSTAT |
|
Y or Yes to enable. |
The following performance counters will be printed in the log files:
Total Oracle I/O Time |
Time spent per SBT thread for reading the data from disk. |
Total MA I/O Time |
Time spent during data transfer to MediaAgent i.e., data read from the network buffer and written to the disk. |
You can track the progress of the job from the Job Controller window of the CommCell Console.
For example, if backup job is using 10 streams, make sure to backup at least 200 GB of data. If you are performing backups using 5 streams, make sure to backup at least 100 GB of data. |
If the Total Oracle I/O Time value is more than the Total MA I/O Time value then perform the following to improve performance:
If the Total Oracle I/O Time value is lesser than the Total MA I/O Time value then perform the following to improve performance:
Backup jobs from Oracle iDataAgent will be displayed as "Completed w/ one or more errors" in the Job History in the following cases:
If you receive an Oracle error during an Oracle backup operation, we recommend that you follow procedures published by Oracle Corporation on resolving the specific error. We also advise you to consult with your on-site Oracle database administrator, as needed.