Archive Backup failed from DB13

[Former Member]

Hi,

we are getting archive backup failed. Backup is scheduled in DB13 & after triggering, following logs are given below.

BR0010I BRARCHIVE function ID: cds

BR0048I Archive function: copy_delete_save

BR0011I 479 offline redolog files found for processing, total size 49345.710 MB

BR0112I Files will not be compressed

BR0130I Backup device type: rman_util

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

BR0280I BRARCHIVE time stamp: 2015-08-19 11.14.28

BR0541I Starting offline redolog backup using RMAN...

BR0278E Command output of 'SHELL=/bin/sh /oracle/PRO/112_64/bin/rman nocatalog':

ld.so.1: rman: fatal: relocation error: file /oracle/PRO/11204/bin/rman: symbol kgnfsgsvr11_: referenced symbol not found

BR0280I BRARCHIVE time stamp: 2015-08-19 11.14.28

BR0279E Return code from 'SHELL=/bin/sh /oracle/PRO/112_64/bin/rman nocatalog': 137

BR0522E 0 of 479 files / save sets processed by RMAN

BR0536E RMAN call for database instance PRO failed

BR0200I BR_TRACE: location BrRmanCall-56, commands for RMAN in: /oracle/PRO/saparch/.aerfcyei.cmd

@/oracle/PRO/saparch/..aerfcyei..cmd

host '/usr/sap/PRO/SYS/exe/run/brtools -f delete /oracle/PRO/saparch/..aerfcyei..cmd';

run { allocate channel sbt_1 device type 'SBT_TAPE'

parms 'BLKSIZE=524288 ENV=(NB_ORA_POLICY=RMAN-1905-GRP-prodb-PRO-L, NB_ORA_SERV=reuxgbus010-c, NB_ORA_CLIENT=sapprodb-b, NB_ORA_SCHED=Default-Application-Backup)';

allocate channel sbt_2 device type 'SBT_TAPE'

parms 'BLKSIZE=524288 ENV=(NB_ORA_POLICY=RMAN-1905-GRP-prodb-PRO-L, NB_ORA_SERV=reuxgbus010-c, NB_ORA_CLIENT=sapprodb-b, NB_ORA_SCHED=Default-Application-Backup)';

allocate channel sbt_3 device type 'SBT_TAPE'

parms 'BLKSIZE=524288 ENV=(NB_ORA_POLICY=RMAN-1905-GRP-prodb-PRO-L, NB_ORA_SERV=reuxgbus010-c, NB_ORA_CLIENT=sapprodb-b, NB_ORA_SCHED=Default-Application-Backup)';

allocate channel sbt_4 device type 'SBT_TAPE'

parms 'BLKSIZE=524288 ENV=(NB_ORA_POLICY=RMAN-1905-GRP-prodb-PRO-L, NB_ORA_SERV=reuxgbus010-c, NB_ORA_CLIENT=sapprodb-b, NB_ORA_SCHED=Default-Application-Backup)';

backup tag aerfcyei format 'PRO_aerfcyei.%s_%p' filesperset 10 check logical

archivelog from sequence 636125 until sequence 636603 thread 1;

release channel sbt_1;

release channel sbt_2;

release channel sbt_3;

release channel sbt_4; }

list backup of archivelog from sequence 636125 until sequence 636603 thread 1 tag aerfcyei;

exit;

BR0280I BRARCHIVE time stamp: 2015-08-19 11.14.28

BR0543E Offline redolog backup using RMAN failed

BR0016I 0 offline redolog files processed, total size 0.000 MB

BR0007I End of offline redolog processing: aerfcyei.cds 2015-08-19 11.14.28

BR0280I BRARCHIVE time stamp: 2015-08-19 11.14.28

BR0005I BRARCHIVE terminated with errors

Please suggest me how to resolve this?

Thanks

Abhijit

[JamesZ]

Hi Abhijit,

I suppose you tested for both user sidadm and orasid.

In that case, is there a standby alone gateway installed in the database host? If there is gateway user in the database host, please test via three users, sidadm, orasid and gateway use for command:

/oracle/PRO/112_64/bin/rman nocatalog

Then let us know the result.

Best regards,
James

[Former Member]

Hi James,

As we taken the archive backup from command line successfully but when it's triggering by scheduling or manually from DB13 from sap Gui, it's failed.

So we here what need to check?

Thanks

Abhijit 

[former_member224542]

Hi Abhijit,

When you ran rman archive backup via command line, I assume you used orasid? If yes, then that could be the issue. DB13 uses sidadm (you can verify that the created logfile in /oracle/SID/saparch is owned by sidadm), therefore, please check if sidadm environment is sufficient to execute oracle functions such as rman.

Regards,

Glenn

[Former Member]

Abhijeet,

I see below error,

BR0278E Command output of 'SHELL=/bin/sh /oracle/PRO/112_64/bin/rman nocatalog':

ld.so.1: rman: fatal: relocation error: file /oracle/PRO/11204/bin/rman: symbol kgnfsgsvr11_: referenced symbol not found

BR0280I BRARCHIVE time stamp: 2015-08-19 11.14.28

BR0279E Return code from 'SHELL=/bin/sh /oracle/PRO/112_64/bin/rman nocatalog': 137

Return code 137 mean the job was killed because it exceeded the time limit.

Looks like the job waited for some time to write in the disk but unfortunately disk was not available due to some reason.

Can you check the error in this perspective.

regards,

Rv

[Former Member]

Hi Rv,

Thanks for the response in this regards & we will check from our side.

Thanks

Abhijit

[JamesZ]

Hi Abhijit,

The problem does seem to be related to environment variable setting. Can you please check if the command which was triggered in db13 can be executed from os level? Please try two times for both sidadm and orasid users.

Then let me know the result.

Best regards,

James

[Former Member]

Hi James,

It was working while we are triggering the backup from os level in command line but it fails if run from db13. we have checked it from os level that is performing well.

Regards

Abhijit