on 10-04-2010 1:28 PM
hello
I have the following configuration :
os : sles 10 sp2
db : RAC - oracle 10.2.0.4
sap: SAP ECC 6.0
I wanted to do an update to kernel sap , from Kernel release 700 lvl 221 to Kernel release 700 lvl 254.
But after I put sap kernel 254 i noticed the replication process from crs died minutes after start .
From what I saw in the log crs this process died in unknown circumstances and try to restart and after several attempts service stopped .
Crs log says :
[CRSRES][1424156992]0In stateChanged, sap.PRD.ERS04.0.abap.rep target is ONLINE
[CRSRES][1424156992]0sap.PRD.ERS04.0.abap.rep on nod2 went OFFLINE unexpectedly
[CRSRES][1424156992]0StopResource: setting CLI values
[CRSRES][1424156992]0Attempting to stop `sap.PRD.ERS04.0.abap.rep` on member `nod2`
[CRSRES][1424156992]0Stop of `sap.PRD.ERS04.0.abap.rep` on member `nod2` succeeded.
[CRSRES][1424156992]0sap.PRD.ERS04.0.abap.rep RESTART_COUNT=0 RESTART_ATTEMPTS=2
[CRSRES][1424156992]0Restarting sap.PRD.ERS04.0.abap.rep on nod2
[CRSRES][1424156992]0startRunnable: setting CLI values
[CRSRES][1424156992]0Attempting to start `sap.PRD.ERS04.0.abap.rep` on member `nod2`
[CRSRES][1424156992]0Start of `sap.PRD.ERS04.0.abap.rep` on member `nod2` succeeded.
[CRSRES][1424156992]0Successfully restarted sap.PRD.ERS04.0.abap.rep on nod2, RESTART_COUNT=1
[CRSRES][1424156992]0sap.PRD.ERS04.0.abap.rep Updated LAST_RESTART time in ocr
[CRSAPP][1424156992]0CheckResource error for sap.PRD.ERS04.0.abap.rep error code = 1
[CRSRES][1424156992]0In stateChanged, sap.PRD.ERS04.0.abap.rep target is ONLINE
[CRSRES][1424156992]0sap.PRD.ERS04.0.abap.rep on nod2 went OFFLINE unexpectedly
[CRSRES][1424156992]0StopResource: setting CLI values
[CRSRES][1424156992]0Attempting to stop `sap.PRD.ERS04.0.abap.rep` on member `nod2`
[CRSRES][1424156992]0Stop of `sap.PRD.ERS04.0.abap.rep` on member `nod2` succeeded.
[CRSRES][1424156992]0sap.PRD.ERS04.0.abap.rep RESTART_COUNT=1 RESTART_ATTEMPTS=2
[CRSRES][1424156992]0sap.PRD.ERS04.0.abap.rep Uptime does not exceed uptime_threshold
[CRSRES][1424156992]0Restarting sap.PRD.ERS04.0.abap.rep on nod2
[CRSRES][1424156992]0startRunnable: setting CLI values
[CRSRES][1424156992]0Attempting to start `sap.PRD.ERS04.0.abap.rep` on member `nod2`
[CRSRES][1424156992]0Start of `sap.PRD.ERS04.0.abap.rep` on member `nod2` succeeded.
[CRSRES][1424156992]0Successfully restarted sap.PRD.ERS04.0.abap.rep on nod2, RESTART_COUNT=2
[CRSRES][1424156992]0sap.PRD.ERS04.0.abap.rep Updated LAST_RESTART time in ocr
[CRSRES][1424156992]0sap.PRD.ERS04.0.abap.rep target set to OFFLINE before stop action
I tried to restart the process , restart crs and restart the server without any success .
When I came up with the old version of SAP kernel problem gone .
I made a comparison access rights between the old and the new kerner and i found nothing special .
To avoid human error or copy i rebuilt the whole process started digging kernel update but the result was the same .
Can you help me solve this problem? Thanks
Make sure your crs_stat file is not replaced with new file. crs_stat and few other files will be having entries for cluster settings.
Thanks,
Venkat.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Check this note may help you Note:1453114
Regards
Uday
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You have to check the dev_en* files in the work directory of the ERS instance. One thing that might be wrong is that you were still using an older version of the binaries there (be aware of sapcpe and global and local kernel's).
Best is to manually check for these entries, just to make sure:
patchno 254
As you put the old kernel back and everything works again, an error on the crs layer is rather unlikely.
Cheers Michael
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
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.