Skip to Content
avatar image
Former Member

Issue in Client Import

We are performing client import from our Production system to Development system, but stuck while import TR due to Lock Overflow in Development system, we have already increased the number of locks till memory support but still issue not solved.

is there any way to solve this issue ?

Number of Locks Configured - 48946666(2K)

Our System

OS - Windows Server Standard 2008 R2 (Physical Memory Support 32 GB)

Database - ASE Sybase 15.7

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Dec 21, 2017 at 09:11 AM

    Hi Ritesh,

    From your use of terminology it sounds like this is a SAP Buisness Suite system in which case I will let one of my colleagues advise you on this but if you are running a standalone ASE then please reply with as much information as you can and I will try and advise you.


    Add comment
    10|10000 characters needed characters exceeded

  • Dec 21, 2017 at 09:55 AM

    Hello Ritesh,

    Andy is right. This is a SAP on ASE question and the correct tag you should use is "SAP ASE ERP Enablement". Choosing the right tag is important as it exposes the question to the right people from the start.

    Coming back to the question, you should analyse the ASE log along with a sp_monitorconfig 'all' output run in isql. If they indicate a shortage of locks in ASE, you can check the following KBA if it helps:

    If there is no errors in ASE, then you should investigate the issue from the Client import angle.

    Hope this helps



    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      I checked in ASE Log File, shows error ASE has run out of LOCKS, increased locks but not work

      follow SAP Note - 1884542 - [ASE Error SQL1204] ASE has run out of LOCKS

  • Dec 22, 2017 at 09:21 AM

    Hello Ritesh,

    Almost 50 millons for number of locks is a very high value indeed. Which is the sizing of your source SID database ? (you should be able to see that from DBACockpit). The ASE 15.7 SP level should be ideally >= SP137.
    Along with KBA provided here, you may have a look on this SAP Note which has a link to the Best Practices Guide (page 33 - "3.5.4 Troubleshooting Data Import"). Also have a look on explanation from page 30.

    Best regards,

    Add comment
    10|10000 characters needed characters exceeded

    • Greetings Ritesh,

      I realize I didn't specify the SAP Note for the Best Practices Guide, here is it: SAP Note 1680803, the complete import recommendations start at page 25 (chapter "3.5 Import"). Please read it carefully.

      Also for analysis purpose it would be interesting to check whether the out of locks message (Msg 1204) is returned always on the same table import / import phase.

      Best regards,