cancel
Showing results for 
Search instead for 
Did you mean: 

Bug in Oracle-grid/sapctl setup .. manually it works

Former Member
0 Kudos

I want to protect the standalone enqueue server with Oracle cluster (11.2.0.2).

Somehow the connection between crs and sapctl does not work properly - funny enough, the manual invocation of crssapactions.pl is successful (see below) .

[root@rac11a ~]# crsctl status res -t
sap.QRC.ERS71.startsrv
      1        OFFLINE OFFLINE
sap.QRC.SCS51.javaenq
      1        OFFLINE OFFLINE
sap.QRC.SCS51.startsrv
      1        ONLINE  UNKNOWN      rac11a
sap.QRC.javavip
      1        ONLINE  ONLINE       rac11a

When I want to start the sapstartsrv with crs, an error occurs

[root@rac11a ~]# crsctl start res sap.QRC.SCS51.startsrv -n rac11a
CRS-2679: Attempting to clean 'sap.QRC.SCS51.startsrv' on 'rac11a'
CRS-2680: Clean of 'sap.QRC.SCS51.startsrv' on 'rac11a' failed
CRS-4000: Command Start failed, or completed with errors.

This is the log:

[tail oracle/LOCAL/GRID/11202/log/
rac11a/agent/crsd/sap_startsrv_type_qrcadm/sap_startsrv_type_qrcadm.log:

2012-02-18 11:34:48.166: [    AGFW][1169709376] Preparing CLEAN command for: sap.QRC.SCS51.startsrv 1 1
2012-02-18 11:34:48.166: [    AGFW][1169709376] sap.QRC.SCS51.startsrv 1 1 state changed from: UNKNOWN to: CLEANING
2012-02-18 11:34:48.168: [    AGFW][1148729664] Executing command: clean for resource: sap.QRC.SCS51.startsrv 1 1
2012-02-18 11:34:48.170: [    AGFW][1148729664] Entering script entry point...
2012-02-18 11:34:48.170: [sap.QRC.SCS51.startsrv][1148729664] [clean] Executing action script: /usr/sap/sapctl/bin/crssapactions.pl[clean]
2012-02-18 11:34:48.169: [CRSTIMER][1190689088] Timer Thread Starting.
2012-02-18 11:34:48.243: [    AGFW][1148729664] Command: clean for resource: sap.QRC.SCS51.startsrv 1 1 completed with invalid status: 206
2012-02-18 11:34:48.244: [    AGFW][1159219520] Executing command: check for resource: sap.QRC.SCS51.startsrv 1 1
2012-02-18 11:34:48.244: [    AGFW][1159219520] Entering script entry point...
2012-02-18 11:34:48.245: [sap.QRC.SCS51.startsrv][1159219520] [check] Executing action script: /usr/sap/sapctl/bin/crssapactions.pl[check]
2012-02-18 11:34:48.249: [    AGFW][1169709376] Agent sending reply for: RESOURCE_CLEAN[sap.QRC.SCS51.startsrv 1 1] ID 4100:3734
*2012-02-18 11:34:48.301: [    AGFW][1159219520] Received unknown resource status code: 206*
2012-02-18 11:34:48.301: [    AGFW][1159219520] check for resource: sap.QRC.SCS51.startsrv 1 1 completed with status: UNKNOWN
2012-02-18 11:34:48.303: [    AGFW][1169709376] sap.QRC.SCS51.startsrv 1 1 state changed from: CLEANING to: UNKNOWN

A manual invocation of crssapactions.pl (as I assume it's invoked by crs) works successfully (check,stop and start):

[root@rac11a ~]# export _CRS_CRS_HOME=/oracle/LOCAL/GRID/11202
[root@rac11a ~]# export _CRS_SAPCONTROL=/sapmnt/QRC/exe/sapcontrol
[root@rac11a ~]# export _CRS_SAPLIBPATH=/sapmnt/QRC/exe
[root@rac11a ~]# export _CRS_NAME=sap.QRC.SCS51.startsrv
[root@rac11a ~]# /usr/sap/sapctl/bin/crssapactions.pl check
Sat Feb 18 11:41:37 2012| CHHECK sapstarsrv SCS51 begin
Sat Feb 18 11:41:37 2012| Suchmuster: START_SCS51 QRC_SCS51
Sat Feb 18 11:41:37 2012| Executing /sapmnt/QRC/exe/cleanipc 51 remove
Sat Feb 18 11:41:37 2012| Deleting named pipe /tmp/.sapstream55113
Sat Feb 18 11:41:37 2012| Action exiting, RC=1

This is how the crs resource was defined:

crsctl add resource sap.QRC.SCS51.startsrv -type sap.startsrv.type 
-attr "ACTION_SCRIPT=/usr/sap/sapctl/bin/crssapactions.pl, 
PLACEMENT=restricted, SERVER_POOLS=SAP_SP_QRC, SAPLIBPATH=, SAPCONTROL=/usr/sap/QRC/SYS/exe/run/sapcontrol,
START_DEPENDENCIES='hard(sap.QRC.javavip) pullup(sap.QRC.javavip) attraction(sap.QRC.ERS71.javarep)', 
CHECK_INTERVAL=60,RESTART_ATTEMPTS=0"

Where's the bug....?

Edited by: lholifeld on Feb 18, 2012 9:09 PM

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi,

Have you resolved this issue, If yes please let me know the solution as we are facing the same issue after upgrading the sapctl from version 4.0 to 6.0.

Regards,

Koushal Solanki