Skip to Content
avatar image
Former Member

SAP instance startup problem - MCOD

Hi All,

We have installed two SAP systems with MCOD database concept ie.. ERP and CRM system uses single database.

Installation completed successfully...

Now the problem is If I start ERP system first then CRM system will not come up and happening vice versa.

Please suggest me a solution ASAP .How can I distribute the memory to the two instances ..If the problem is not related to the Memory what are all the other things needs to be checked.

Thanks in advance

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    avatar image
    Former Member
    Dec 20, 2011 at 01:07 PM

    First of all, check via R3trans -d whether you can connect to the database before issuing startsap.

    If R3trans -d doesn't show a returncode 0, then check file trans.log.

    If R3trans -d is ok and the startup of the second instance fails, then look at the developer trace files in the work directory.

    dev_disp and dev_w0 might provide a detailed error message. Maybe the total number of database connections is too limited, or you have not enough RAM, or .... (could be quite a long list of potential problems).

    Regards,

    Mark

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Dec 20, 2011 at 01:28 PM

    Hi Mark,

    Thanks for the quick response...

    R3trans -d is giving return code zero for both systems and we have 28 GB RAM.

    As I mentioned in the thread both systems are starting but one at a time.If I start ERP, I wont be able to start CRM and vice versa.

    This is something related to memory .Can you please help me on this??

    Thanking You,

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Guys,

      Thanks for all your co-operation.

      Solved by changing the memory parameters in /etc/sysctl.conf file.Now both the systems are up and running

      Parameters changed

      kernel.sem

      kernel.msgmni

      Note : Server restart is required after the parameter change