Skip to Content
0
Oct 18, 2016 at 01:30 PM

ASE has run out of LOCKS

1086 Views

Hi,

The following problem. I have a some tables with >200 million entries, during a client copy I have excluded these tables to export/import them via R3trans, with Oracle the best way to finish the client copy quickly and export/import the tables also in a faster way.

So, I exported the tables with the command to delete the existed entries first before the new entry will be imported. But that fact brings Sybase everytime to the error message "run out of LOCKS".

I shutdown SAP to give ASE all the memory the hardware has, but to get over 200 million locks, I need much more memory than the hardware has. The same is, if I want to delete the table entries with "delete from", it runs out of locks.

So can somebody tell me, whats the different to Oracle and why I need that size of locks to delete that amount of entries? Truncate is possibly the best way, or via SE14 drop and create the table again, but unfortunately I have to delete the entries for a special client!

Thanks for any help!

Best regards,

Tobias