The problem of offline full backup using DB13

[Former Member]

We have installed a new ECC6.0 for oracle in HP-UNIX.

But when I did a offline full backup using DB13,the backup finished in

1 sec.

In the log there is no any action.

I can finish the offline full backup using Brtools on OS.

Why I can not do the offline full backup using DB13?

Job name Status Scheduled start

Actual start End Time

DBA:FULLOFF+LOG_____@222826/2000 Completed 06.03.2007 22:29:11

06.03.2007 22:29:11 06.03.2007 22:29:13

Job log

Job started

Step 001 started (program RSDBAJOB, variant &0000000000000, user ID SYSADM)

Execute logical command BRBACKUP On host sapdev

参数:-u / -jid FLGOF20070306222826 -c force -t offline_force -m full -p initDEV.sap -a -c force -p initDE

V.sap -cds

Job finished

I have see the notes 988038 ,but I can't find the sp--SAPKB70011 in the SAP Market Web.

How can I solve this problem?

[Former Member]

I have imported the SP11 of basis into my system.

But the problem is not sloved yet.

Who can help me?

Thanks!

Ryan

[andreas_herzog]

sp--SAPKB70011 in the SAP Market Web:

-> sapnote 988.038 -> scroll down to "Highest Implemented Support Package" -> clikc on the package "SAPKB70011" -> a new window opens (takes some time!) -> "download to pc" or "add to download basket"

OR

enter SAPNet -> Alias: PATCHES -> Support Packages and Patches -> SAP Application Components -> SAP ERP -> SAP ERP 2005 -> Entry by Component -> SAP ECC Server -> Basis Support Package 11 for 7.00 (released march, 5th)

GreetZ, AH

[Former Member]

Hi,

Follow what Andreas has adviced or take a shortcut as follows :

Go to Support Packages and Patches in service.sap.com/patches and in the search string put SAPKB700* and search.

Normally i do this if the patch no is known to me to save time.

Regards

[Former Member]

Hi Ryan,

Why don't you try to run it from the command line.

As <sid>adm, run brbackup and the options you find at the job log (-u / -c force -t offline_force -m full -p initDEV.sap -a -c force -p initDEV.sap -cds), except the JobID (-jid).

Maybe it will show more info about the error.

You can try also, execute it as ora<sid> and look what happens.

Best Regards,

JC Llanes.