cancel
Showing results for 
Search instead for 
Did you mean: 

Sudden death of BrTools

Former Member
0 Kudos

Hi all

BrTools (7.10 - 25) stops working, why i dont no... Here is information from the brarchive detail log.

-


Detail log: aebpaqro.svd

-


BR0002I BRARCHIVE 7.10 (25)

BR0006I Start of offline redolog processing: aebpaqro.svd 2009-10-01 17.19.52

BR0484I BRARCHIVE log file: D:\oracle\BU1\saparch\aebpaqro.svd

BR0101I Parameters

Name Value

oracle_sid BU1

oracle_home D:\ORACLE\BU1\102

oracle_profile D:\ORACLE\BU1\102\database\initBU1.ora

sapdata_home D:\oracle\BU1

sap_profile D:\ORACLE\BU1\102\database\initbu1.sap

backup_dev_type disk

archive_copy_dir G:\backup\BU1\brarchive

compress no

disk_copy_cmd rman_set

cpio_disk_flags -pdcu

rman_compress yes

archive_dupl_del only

system_info SAPServiceBU1 SAP380TEST Windows 5.2 Build 3790 Service Pack 2 AMD64

oracle_info BU1 10.2.0.2.0 8192 103 649997898 SAP380TEST WE8DEC AL16UTF16 2050355461

sap_info 700 SAPR3 0002LK0003BU10011E20835594560015Maintenance_ORA

make_info NTAMD64 OCI_10201_SHARE Aug 16 2009

command_line brarchive -u / -jid LOG__20091001171951 -c force -p initbu1.sap -sd

BR0036I The current redolog sequence number 103 of database instance BU1 is not greater than the sequence number 325 of the last saved offline redo log file

BR0031I Probably the redolog sequence number of database instance BU1 was reset

BR0280I BRARCHIVE time stamp: 2009-10-01 17.19.56

BR0008I Offline redolog processing for database instance: BU1

BR0009I BRARCHIVE action ID: aebpaqro

BR0010I BRARCHIVE function ID: svd

BR0048I Archive function: save_delete

BR0011I 110 offline redolog files found for processing, total size 5110.882 MB

BR1397I Files will be compressed by RMAN

BR0130I Backup device type: disk

BR0106I Files will be saved on disk in directory: G:\backup\BU1\brarchive

BR0134I Unattended mode with 'force' active - no operator confirmation allowed

BR0202I Saving init_ora

BR0203I to G:\backup\BU1\brarchive\BU1 ...

BR0202I Saving D:\ORACLE\BU1\102\database\initbu1.sap

BR0203I to G:\backup\BU1\brarchive\BU1 ...

BR0280I BRARCHIVE time stamp: 2009-10-01 17.19.56

BR0198I Profiles saved successfully

BR0202I Saving D:\oracle\BU1\saparch\BU1ARCH1_326_689601689.DBF

BR0203I to G:\backup\BU1\brarchive\BU1ARCH1_326_689601689.DBF.S ...

And her it stops.

The file on the disk is zero byte large.

Oracle has been bounced.

SAP has been bounced.

Server has been bounced.

Write permission has been verified.

Please advise.

Best regards

Mads Hammer

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Mads,

this is probably happening because the database was opened with the resetlogs option. The number of the next log to be really different.

For backup the brbackup will complains agaist this situation.

1 - Rename the log /oracle/DBSID/saparch/archSID.log to oracle/DBSID/saparch/archSID.log.1

2 - Try to make a new backup using brtools.

Regards

former_member204746
Active Contributor
0 Kudos

read SAP note 19914 for a full resolution.

Former Member
0 Kudos

Hi Eric

BRBACKUP is version 7.10 so normally it would deal with this kind automaticaly. Also as the note describes:

"Caution:

-


As of SAP Release 2.2E, BRARCHIVE recognizes automati cally the resetting

of the log sequence nummber, if the database is already open when starting

BRARCHIVE. In this case, the actions described under "Situation B" are not

required."

I have removed all logfiles and started a new backup. Still same issue.

Best regards

Mads Hammer

former_member204746
Active Contributor
0 Kudos

try this:

stopsap

sqlplus / as sysdba

shutdown immediate;

Alter database open resetlogs;

exit

startsap

brarchive

good luck.

Former Member
0 Kudos

Even though brtools should be able to reset the logs, please try the following.

rename the archSID.log to e g archSID.log.old

then create an empty archSID.log and set the same authorization as the "old" one.