Skip to Content
author's profile photo Former Member
Former Member

Issues with DB/CI and DI @ different levels

SAP gurus - Hi

Recently migrated my AIX servers (from 5.3 to 6.1) for the CI and DI instances and ran into issues -

Here is the order of events..

1- First migrated the DI instance, applications started alright, active in SAP

2- Then I migrated the inactive node of the CI HACMP cluster - no impact to service

3- Then I did the fail-over from to migrate the other HACMP node, at this point after the cluster failover (the CI is also at AIX 6.1 now), the DI instance is not showing active in SAP GUI anymore, although the SAP is running on both CI and DI at the OS level.

4- We tried to stop/start just the DI, that didn't work

5- Then we stopped/started both DI and CI in the correct order (CI first then DI), still not good

6- Finally rebooted the DI server, started SAP after reboot and then it showed up

Luckily this was in the test environment, I have to progress the change to Production and I cannot imagine having to reboot the Prod DI instances, that is a big no no.

Does this ring a bell? anyone, anybody seen this before? or know what might have caused the app servers to disappear from SAP? anything we can do proactively to avoid this situation? or avoid reboot post-actively? 😊

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • Posted on Dec 13, 2011 at 03:29 AM

    I'm not sure what you mean by "DI instance is not showing active in SAP GUI anymore", how did you see that ?

    What error you captured in screen for fail logon ?

    Is this issue reproduciable after migration completed to 6.1 ?

    For improper instance stop/start, dev_* trace files / sapstart/stderr logs are the one the look at as well to find out the reason.



    Add a comment
    10|10000 characters needed characters exceeded

  • Posted on Dec 13, 2011 at 05:50 AM


    In you cluster environment, DI and CI are the standalone engines while ASCS and DB services are part of cluster services.

    Hence when you perform failover , HACMP script should take care of starting DI after shifting the resources to takeover node.

    HACMP script needs to be tweaked to incorporate these changes.

    Hope this helps.


    Deepak Kori

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.