on 04-08-2011 5:14 PM
Hi Experts
We have PI system in cluster environment.
Issue is N1 Node (CI) does not move to N2 node (DB) in case of any failover. However N2 Node (DB) is moving perfectly from N1 to N2 and vice a versa.
There is no problem with SAP SID IP, SAP SID Netname, SAP SID SAPMNT and Drive movement to N2 node. But when we try to bring online SCS or ASCS service in N2 node it get fail and all resources move to N1 node automatically. I found that SAP Note 1043592 but it did not resolve the issue. We are trying hard to troubleshoot this issue. However we have raised a message to SAP and waiting for there response.
OS: Windows 64 bit SP2
Database: SQL Server 2005
N1 Node (CI)
N2 Node (DB)
If anyone has experienced this issue, please help us.
Thanks
Ajit
Also please check the developer trace files for errors (if the groups gets failed back to Node 1 then these will be the .old files).
I have seen issues previously where the ports required for the SAP instance have been used by other processes - you will see this in the developer trace files if this is the problem.
If this is the issue then you can use netstat -o together with the Task Manager to find the Windows process that is holding the port.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
Check sap services in scs and ascs are they starting ok.
It might be version of sapstartsrv.exe is corrupt.
Copy sapstartsrv.exe and sapstartsrv.exe.new from the CT_RUN directory overwrite version in the kernel
folder for scs and ascs
Then try to bring online scs and ascs.
regards,
John Feely
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
80 | |
24 | |
11 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.