cancel
Showing results for 
Search instead for 
Did you mean: 

URGENT Locking Issue when reloading

Former Member
0 Kudos

Hello,

I keep trying to reload a DSO and keep getting a lock error. I have ensured all lockes are deleted and then started the load. I then log out of the box. It will fail at different times saying it is locked by me. i am on SP12.

Thanks,

Edited by: MG on Dec 20, 2007 2:55 PM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

At what point are you getting the error?

During InfoPkg schedule or during DTP execution.

Also what is the type of update: Full or Delta

Former Member
0 Kudos

OK so we are getting the issue with a DTP. WE loaded a delta and now are running fulls to repair some data. The data is in the PSA already and wsa loaded prior to the delta. The load completed I had an issue with, but I don't know why. It locked about 60% of the time. I have looked at all possible locks and jobs before I start and there is none. Then I start the load. It will run from anywhere to 1-4hrs and then it fails saying it was locked by me.

Answers (2)

Answers (2)

Former Member
0 Kudos

ODS Locks can occur due to following reasons -

During loading

you are not permitted to

· delete the contents of the ODS object

· Archive data

you are permitted to

· delete data request by request

· delete data selectively

· activate data

During activation

you are not permitted to

· delete the contents of the ODS object

· delete data request by request

· delete data selectively

· delete master data

· archive data

· reactivate data

· Update data to other data targets

During the deletion of individual requests

you are not permitted to

· delete the contents of the ODS object

· start deleting more requests

· delete data selectively

· activate data

· archive data

· Update data to other data targets

During the selective deletion of data

you are not permitted to

· delete the contents of the ODS object

· delete data request by request

· start deleting more data selectively

· activate data

· archive data

· Update data to other data targets

Check job and process overview in the tcodes below and kill it before reloading it.

SM37, SM66, SM50/51.

Hope it Helps

Chetan

@CP..

Former Member
0 Kudos

Check in SM 58 - if IDOCS are pending ..if they are..thn they are trying to again creaqte processes and thus lockin might be happening....

clear all IDOCS..kill the jobs and then try relaoding..

What locks are you getting anyways?

--S@A