cancel
Showing results for 
Search instead for 
Did you mean: 

Long running local client copy

Former Member
0 Kudos

Hi,

After new installation SAP R/3 4.7 enterprise, i defined local client copy from 000 as back ground job.This bk.job running was running more than 15 hours.

So i decided to cancel the active job,it did't respond.

I shutdown the sapmmc and when i restarted the console

disp+work process not starting.

Is it because i used SAP_ALL for local clientcopy???

What is the way out now ?????

Can any one help me , please???

regards,

sreepathi

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Sreepathi,

I too feel there can be an archive stuck error.

If yours is a unix OS,execute df -k /oracle/SID/orarch and see if this is 100% full.

If so move the contents to another location.

And because you interrupted the client copy delete the client at OS level .

To delete a client XXX, you have to create a command file "delXXX" with following entries

Clientremove

Client = XXX

Select *

Place the command file in /usr/sap/trans/bin

$ cd /usr/sap/trans/bin

$ R3trans –w <log file name> -u 1 <command file name >

e.g $ R3trans -w delXXX.log -u 1 delXXX

To check the progress...

$ tail -f delXXX

Reorg the database post client delete .

Once you are able to login in to SAP start the client copy afresh.

There is no problem with selecting SAP_ALL profile for a local client copy.

Regards,

Bapujee Naidu

Former Member
0 Kudos

Hi Sreepathi,

maybe an archiver stuck on the database?

Regards,

Pascal