Unsolved

This post is more than 5 years old

2 Posts

3352

August 21st, 2009 02:00

SAP backup (Oracle) using the NetWorker module

Hello all!

I have some issues with a SAP backup on Oracle using the NetWorker module.
It fails and points to some log file like(/oracle/PR3/saparch/aebhejum.svd):

=== START LOG ===

BR0002I BRARCHIVE 7.00 (42)
BR0006I Start of offline redo log processing: aebhejum.svd 2009-08-21 06.03.52
BR0484I BRARCHIVE log file: /oracle/PR3/saparch/aebhejum.svd
BR0477I Oracle pfile /oracle/PR3/102_64/dbs/initPR3.ora created from spfile /oracle/PR3/102_64/dbs/spfilePR3.ora

BR0101I Parameters

Name Value

oracle_sid PR3
oracle_home /oracle/PR3/102_64
oracle_profile /oracle/PR3/102_64/dbs/initPR3.ora
sapdata_home /oracle/PR3
sap_profile /oracle/PR3/102_64/dbs/initPR3.sap
backup_dev_type util_file
util_par_file /oracle/PR3/102_64/dbs/initPR3arch.utl
archive_dupl_del only
system_info orapr3/orapr3 sapdb AIX 3 5 0002D8DAD300
oracle_info PR3 10.2.0.4.0 8192 19761 975534864 sapdb WE8DEC UTF8
sap_info 700 SAPPR3 PR3 E1488100137 R3_ORA 0020200921
make_info rs6000_64 OCI_102 Jul 4 2009
command_line brarchive -c force -u / -d util_file -r initPR3arch.utl

BR0017W Offline redo log file '/oracle/PR3/oraarch/PR3arch1_14953_555675517.dbf' not found
BR0017W Offline redo log file '/oracle/PR3/oraarch/PR3arch1_14954_555675517.dbf' not found
BR0017W Offline redo log file '/oracle/PR3/oraarch/PR3arch1_14955_555675517.dbf' not found
BR0017W Offline redo log file '/oracle/PR3/oraarch/PR3arch1_14956_555675517.dbf' not found
*** SKIPPED ***
BR0017W Offline redo log file '/oracle/PR3/oraarch/PR3arch1_18621_555675517.dbf' not found
BR0017W Offline redo log file '/oracle/PR3/oraarch/PR3arch1_18622_555675517.dbf' not found
BR0017W Offline redo log file '/oracle/PR3/oraarch/PR3arch1_18623_555675517.dbf' not found

BR0280I BRARCHIVE time stamp: 2009-08-21 06.03.53
BR0008I Offline redo log processing for database instance: PR3
BR0009I BRARCHIVE action ID: aebhejum
BR0010I BRARCHIVE function ID: svd
BR0048I Archive function: save_delete
BR0011I 1137 offline redo log files found for processing, total size 51771.732 MB
BR0130I Backup device type: util_file
BR0109I Files will be saved by backup utility
BR0134I Unattended mode with 'force' active - no operator confirmation allowed

BR0280I BRARCHIVE time stamp: 2009-08-21 06.03.53
BR0229I Calling backup utility with function 'backup'...

BR0280I BRARCHIVE time stamp: 2009-08-21 06.03.53
BR0279E Return code from 'backint -u PR3 -f backup -i /oracle/PR3/saparch/.aebhejum.lst -t file -p /oracle/PR3/102_64/dbs/initPR3arch.utl -c': 2

BR0232E 0 of 1137 files saved by backup utility
BR0280I BRARCHIVE time stamp: 2009-08-21 06.03.53
BR0231E Backup utility call failed

BR0016I 0 offline redo log files processed, total size 0.000 MB

BR0007I End of offline redo log processing: aebhejum.svd 2009-08-21 06.03.53
BR0280I BRARCHIVE time stamp: 2009-08-21 06.03.53
BR0005I BRARCHIVE terminated with errors

=== END LOG ===

We tried to communicate with SAP support, but they said:

***
You are receiving the errors after the following message:
BR0229I Calling backup utility...

And then you get the following :
BR0231E Backup utility call failed

Brbackup transfers the responsibility for any data handling to the
Backint external backup tool. Any errors in this section point to
problems with this backup utility. So, we kindly ask you to contact
your external backup tool vendor concerning this issue since errors in
this area belong to their field of responsibility.
***


Could anybody tell where is the problem may be?

Thanks!

56 Posts

August 24th, 2009 01:00

You can try to find the cause from /nsr/applogs/arch_backintPR3.log. It's more detailed than brarchive log files. T´here is also backintPR3.log for online backups.

I think the most propable reason for this failure is this:

You have over 1000 files and over 50GB to backup. Check out your util file for this parameter: "ss_group_by_fs". If value is "yes" your backup will not succeed. This is because networker will create a list of files to backup and if the list is too long backup will fail. This is somekind of overflow thing. When this parameter is set "yes", NW will create only one huge saveset.

You have to comment "ss_group_by_fs" or set it "no". Then NW will use "savesets" value defined in util file. If your "savesets" value is for example "20" NW will split your 50GB of archive logs to 20 pieces and backup will succeed.

"ss_group_by_fs" will usually work fine except just this one little drawback.

2 Intern

 • 

14.3K Posts

September 4th, 2009 04:00

Check the backint log first. ss_group_by_fs might an issue with archive log backup if you have too many of them, but not with database backup. Does the backup of DB run?

2 Intern

 • 

14.3K Posts

September 4th, 2009 04:00

(duplicate)
No Events found!

Top