Restore Troubleshooting - SAP Oracle iDataAgent

The following section provides information on some of the troubleshooting scenarios related to restore:

Table of Contents

Restore fails with permissions issue

Symptom

The restore fails due to issues accessing the SnapProtect registry, log files and base directories.

The RMAN restore fails because it cannot load the CommVault SBT Media Management library.

The SAP backint restore fails because the symbolic links are configured and correctly pointing to the SnapProtect backint.

Resolution

Run the Database Readiness Check.

Restore of large number of files fails for RMAN and BACKINT

Symptom

SAP Note (1647272 P.12) advises that if the SAP Oracle database has BR*Tools version 7.20(28)-7.20(31), restoring a large number of files (greater than 100) fails, when you are using the RMAN interface, and runs slowly when you are using the BACKINT interface. This is due to the chunking feature, where a large number of files are not processed at one time, but in groups of 100. This feature was introduced in patch 7.20(28) and existed till patch 7.20(31). It was disabled in patch 7.20(32).

Resolution

Upgrading to BR*Tools 7.20(32) (or later) or to BR*Tools 7.40(4) solves this issue.

Before running a restore, disable the SAP feature causing the failure by setting the following SAP special parameters in init<DBSID>.sap.

_rman_grp_cnt = 9999

_util_grp_cnt = 9999

After modifying the parameters, re-run the restore job.

Restore fails with character set name issue

Symptom

The restore fails due to mismatch of character set at the source location where RMAN is run and target database location.

Resolution

This is an Oracle issue. Please contact Oracle support for more information.

Restore completed with warnings

Restore jobs from SAP for Oracle iDataAgent will be displayed as "Completed with Warnings" in the Job History in the following cases:
  • When the database restore succeeds but it fails when recovering the database or opening the database.

BRRESTORE Can Cause Movement and Logging to Stop in Windows Configuration

Symptom

On Windows Configurations, when you launch BRRESTORE from the CommCell Console, or the command line interface, the following issue occurs.

There is no further movement in restore Command after lines- BR0229I Calling backup utility with function 'restore'...

There is no further logging for the SnapProtect logs on the client side.

Example

[brrestore -d util_file -b2 SAP_XXXX_XXXX -m G:\oracle\CER\saparch\archCER.log -c force -u / ]
brrestore Log:[
BR0401I BRRESTORE 7.20 (34)
BR0405I Start of file restore: reoxjbwp.rsf 2014-10-07 10.57.43
BR0484I BRRESTORE log file: G:\oracle\CER\sapbackup\reoxxlkm.rsf
BR0280I BRRESTORE time stamp: 2014-10-07 10.57.44
BR0407I Restore of database: CER
BR0408I BRRESTORE action ID: reoxxlkm
BR0409I BRRESTORE function ID: rsf
BR0415I File for restore using backup utility ID SAP_XXXX_XXXX: G:\oracle\CER\saparch\archCER.log
BR0416I 1 file found to restore, size 0.000 MB
BR0421I Restore device type: util_file
BR0134I Unattended mode with 'force' active - no operator confirmation allowed
BR0100W Internal error for 'stop_file' at location BrStopCheck-1
BR0280I BRRESTORE time stamp: 2013-09-07 10.44.44
BR0229I Calling backup utility with function 'restore'...

Resolution

Disable the User Account Control (UAC) for the Windows user and resubmit the restore.

SAP Oracle ComnmCell Console Restores May Fail with the Wrong RMAN Syntax Construction in the Case of Multiple Database Resets

Symptom

The SAP Oracle CommCell Console restore may fail due to an RMAN syntax error when there are multiple database resets.

Example

run { allocate channel dsk device type disk;
run { allocate channel sbt_1 device type 'SBT_TAPE' parms
'SBT_LIBRARY=/opt/dbserve20/simpana/Base/libobk.so,BLKSIZE=1048576,ENV=(CV_mmsApiVsn=2,ThreadCommandLine=SAPRESTORE
1182598 1182598 -p 2 -jt 1182598:2:1 saporavm3 -vm Instance001 -cn saporavm3 -rcp 0 -rcp 0 -rcp 0)';
restore archivelog from sequence 3 until sequence 4 thread 1 from tag aeouuxih force;
restore archivelog from sequence 5 until sequence 5 thread 1 from tag aeouuzek force;
restore archivelog from sequence 10 until sequence 11 thread 1 from tag aeouvarw force;
release channel dsk;release channel sbt_1; }
exit;

Resolution

Upgrade to BRTools 7.40 patch level 12.

Restore fails when there are multiple subclients for data only and log only backups

Symptom

When there are multiple subclients for a database and one subclient is for data only backups and the other for log only backups, a data and log restore may fail if a user selects a backup job that contains only data. The restore job error is:

[Failing Restores as the log summary file information could not be found. Try restores from the command line.]::Client [sde-sap1] Application [ClSapAgent] Message Id [301989971] RCID [0] ReservationId [0]. Level [0] flags [0] id [0] overwrite [0] append [0] CustId[0]

Resolution

Perform a point-in-time restore for the backup cycle where the data and logs are available. For more information, see Restoring the Database to a Point-in-Time.

SAPOR0014: Restore of Data and Log Backups May Fail when Using a Copy Precedence

Symptom

If you browse the data and log backups by using a copy precedence, the restore fails when the data backup and log backup have different storage policies with different copy precedence values. The error is similar to the following:

Error Code: [18:72] Description: No log sequence number ranges were found. Source: dbtestlinux6, Process: ClSapAgent

Resolution

Ensure that the data and log backups are present on the same copy precedence for their respective storage policies.

Use a command line restore to perform one of the following restores:

  • Select and restore the data only backup by provide the data storage policy copy precedence value
  • Select and restore the log only backup by provide the log storage policy copy precedence value

Oracle Errors

If you receive an Oracle error during a SAP Oracle restore 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.

Recovering data associated with deleted clients and storage policies

Symptom

In a disaster recovery scenario, use the following procedure to recover data associated with the following entities:

  • Deleted storage policy
  • Deleted client, agent, backup set or instance

Before You Begin

This procedure can be performed when the following are available:

  • You have a Disaster Recovery Backup that contains information on the entity that you are trying to restore. For example, if you wish to recover a storage policy (and the data associated with the storage policy) that was accidentally deleted, you must have a copy of the disaster recovery backup that was performed before deleting the storage policy.
  • Media containing the data you wish to recover is available and not overwritten.
  • If a CommCell Migration license was available in the CommServe when the disaster recovery backup was performed, no additional licenses are required. If not, obtain the following licenses:
    • IP Address Change license
    • CommCell Migration license

    See License Administration for more details.

  • A standby computer, which is used temporarily to build a CommServe.
Recovering Deleted Data
  1. Locate the latest Disaster Recovery Backup that contains the information on the entity (storage policy, client, agent, backup set or instance) you are trying to restore.
    • Check the Phase 1 destination for the DR Set or use Restore by Jobs for CommServe DR Data to restore the data.
    • If the job was pruned and you know the media containing the Disaster Recovery Backup, you can move the media in the Overwrite Protect Media Pool. See Accessing Aged Data for more information. You can then restore the appropriate DR Set associated with the job as described in Restore by Jobs for CommServe DR Data.
    • If the job is pruned and you do not know the media containing the Disaster Recovery Backup, you can do one of the following:
      • If you regularly run and have copies of the Data on Media and Aging Forecast report, you can check them to see if the appropriate media is available.
      • If you do not have an appropriate report, and know the media that contains the DR Backup, catalog the media using Media Explorer. Once the cataloging process is completed, details of the data available in the media are displayed.
  2. On a standby computer, install the CommServe software. For more information on installing the CommServe, see Install the CommServe.
  3. Restore the CommServe database using the CommServe Disaster Recovery Tool from the Disaster Recovery Backup described in Step 1. (See CommServe Disaster Recovery Tool for step-by-step instructions.)
  4. Verify and ensure that the NetApp Client Event Manager NetApp Communications Service (EvMgrS) is running.
  5. If you did not have a CommCell Migration license available in the CommServe when the disaster recovery backup was performed, apply the IP Address Change license and the CommCell Migration license on the standby CommServe. See Activate Licenses for step-by-step instructions.
  6. Export the data associated with the affected clients from the standby CommServe as described in Export Data from the Source CommCell.

    When you start the Command Line Interface to capture data, use the name of the standby CommServe in the -commcell argument.

  7. Import the exported data to the main CommServe as described in Import Data on the Destination CommCell.

    This brings back the entity in the CommServe database and the entity is visible in the CommCell Browser. (Press F5 to refresh the CommCell Browser if the entity is not displayed after a successful merge.)

  8. You can now browse and restore the data from the appropriate entity.

    As a precaution, mark media (tape media) associated with the source CommCell as READ ONLY before performing a data recovery operation in the destination CommCell.