cancel
Showing results for 
Search instead for 
Did you mean: 

SAP HA With Oracle Grid: SAPCTL V6 Error: CRS-0160

Former Member
0 Kudos
141

Hi,

We are intended to provide HA for SAP ASCS on RAC Grid.

Grid is installed, RDBMS is already on RAC, all is good.

We follow the documentation from the SAPCTL archive sapnote 1496927.

This is the command we execute:

sapctl create -sapsid PEK -if eth0 -nm 255.255.255.0 -net 10.0.0.202 -nodes eccdb1,eccdb2 -abapvip 10.0.0.226 -abapmsport 3670 -abapenq ASCS70 -abaprep ERS60 -asinstvip 10.0.0.227 -asinst DVEBMGS10

But, the following error appeared:

CRS-0160: The attribute 'sapcontrol' is not supported in this resource type.

This looks strange, looks like sapctl script is not working well.

Please help.

Thank you

--- Happy New Year! ---

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Hello,

It is really nice to see you resolved this problem.

I am really interested to see what all attributes you had set to resolve this issue.

Thanks in advance.

Regards

Manoj

Former Member
0 Kudos

Hi Manoj,

Have you succeed in this matter also?

Thanks

Former Member
0 Kudos

I need to set the attribute manually for each type error. After that, cluster resources are created successfully.

Former Member
0 Kudos

Sorry,

This is the complete original error.

[root@eccdb1 bin]# sapctl create -sapsid PEK -if eth0 -nm 255.255.255.0 -net 10.0.0.202 -nodes eccdb1,eccdb2 -abapvip 10.0.0.226 -abapmsport 3670 -abapenq ASCS70 -abaprep ERS60 -asinstvip 10.0.0.227 -asinst DVEBMGS10

sapctl version 6.0 Patch 6 Production Copyright 2011 Oracle. All rights reserved

Creating SAP ABAP VIP

Creating SAP ABAP Enqueue resource

CRS-0160: The attribute 'SAPCONTROL' is not supported in this resource type.

CRS-4000: Command Add failed, or completed with errors.

SAP Start Service sap.PEK.ASCS70.startsrv resource creation failed.

After I hardcode some SAPCONTROL to sapcontrol, error is different, it complain that SAPLIBPATH is not supported, so I replaced all SAPCONTROL to sapcontrol, and SAPLIBPATH to saplibpath, then the following message appear:

CRS-0160: The attribute 'sapcontrol' is not supported in this resource type.

Thanks

Former Member
0 Kudos

This is the command that generate the error:

/usr/bin/crsctl add resource sap.PEK.ASCS70.startsrv -type sap.startsrv.type -attr "ACTION_SCRIPT=/usr/sap/sapctl/bin/crssapactions.pl,PLACEMENT=restricted,SERVER_POOLS=SAP_SP_PEK, SAPLIBPATH=/usr/sap/PEK/ASCS70/exe,SAPCONTROL=/usr/sap/PEK/ASCS70/exe/sapcontrol, START_DEPENDENCIES='hard(ora.acfs.pek.acfs,sap.PEK.abapvip)pullup(ora.acfs.pek.acfs,sap.PEK.abapvip)attraction(sap.PEK.ERS60.abaprep)', STOP_DEPENDENCIES='hard(ora.acfs.pek.acfs)', CHECK_INTERVAL=60,RESTART_ATTEMPTS=0"

Thanks

Former Member
0 Kudos

This is becoming strange.

I had ensure that sap.startsrv.type has SAPCONTROL attribute, using the following command:

[root@eccdb1 log]# !1083

crsctl modify type sap.startsrv.type -attr "ATTRIBUTE=ACTION_SCRIPT,TYPE=string,DEFAULT_VALUE=/usr/sap/sapctl/bin/crssapactions.pl, ATTRIBUTE=SAPLIBPATH,TYPE=string,DEFAULT_VALUE=UNKNOWN, ATTRIBUTE=SAPCONTROL,TYPE=string,DEFAULT_VALUE=UNKNOWN, ATTRIBUTE=CHECK_INTERVAL,TYPE=int,DEFAULT_VALUE=60, ATTRIBUTE=SCRIPT_TIMEOUT,TYPE=int,DEFAULT_VALUE=600"

The command above is accepted by grid gracefully, but same error still happen.

/usr/bin/crsctl add resource sap.PEK.ASCS70.startsrv -type sap.startsrv.type -attr "ACTION_SCRIPT=/usr/sap/sapctl/bin/crssapactions.pl,PLACEMENT=restricted,SERVER_POOLS=SAP_SP_PEK,SAPLIBPATH=/usr/sap/PEK/ASCS70/exe,SAPCONTROL='/usr/sap/PEK/ASCS70/exe/sapcontrol', START_DEPENDENCIES='hard(ora.acfs.pek.acfs,sap.PEK.abapvip)pullup(ora.acfs.pek.acfs,sap.PEK.abapvip)attraction(sap.PEK.ERS60.abaprep)', STOP_DEPENDENCIES='hard(ora.acfs.pek.acfs)', CHECK_INTERVAL=60,RESTART_ATTEMPTS=0"

CRS-0160: The attribute 'SAPCONTROL' is not supported in this resource type.

CRS-4000: Command Add failed, or completed with errors.

Is this a bug?

Former Member
0 Kudos

Waw, it's getting really weird.

The following command is success:

/usr/bin/crsctl add type sap.startsrv.type -basetype cluster_resource -attr "ATTRIBUTE=ACTION_SCRIPT,TYPE=string,DEFAULT_VALUE=/usr/sap/sapctl/bin/crssapactions.pl, ATTRIBUTE=SAPLIBPATH,TYPE=STRING,DEFAULT_VALUE=UNKNOWN, ATTRIBUTE=SAPCONTROL,TYPE=STRING,DEFAULT_VALUE=UNKNOWN, ATTRIBUTE=CHECK_INTERVAL,TYPE=int,DEFAULT_VALUE=60, ATTRIBUTE=SCRIPT_TIMEOUT,TYPE=int,DEFAULT_VALUE=600"

But check on the resource type, no SAPCONTROL, no SAPLIBPATH.

[root@eccdb1 ~]# crsctl status type sap.startsrv.type -f | grep ATTR

ATTRIBUTE=ACL

ATTRIBUTE=ACTION_FAILURE_TEMPLATE

ATTRIBUTE=ACTION_SCRIPT

ATTRIBUTE=ACTIVE_PLACEMENT

ATTRIBUTE=AGENT_FILENAME

ATTRIBUTE=AUTO_START

ATTRIBUTE=BASE_TYPE

ATTRIBUTE=CARDINALITY

ATTRIBUTE=CARDINALITY_ID

ATTRIBUTE=CHECK_INTERVAL

ATTRIBUTE=CREATION_SEED

ATTRIBUTE=DEFAULT_TEMPLATE

ATTRIBUTE=DEGREE

ATTRIBUTE=DEGREE_ID

ATTRIBUTE=DESCRIPTION

ATTRIBUTE=ENABLED

ATTRIBUTE=FAILOVER_DELAY

ATTRIBUTE=FAILURE_COUNT

ATTRIBUTE=FAILURE_HISTORY

ATTRIBUTE=FAILURE_INTERVAL

ATTRIBUTE=FAILURE_THRESHOLD

ATTRIBUTE=HOSTING_MEMBERS

ATTRIBUTE=ID

ATTRIBUTE=INCARNATION

ATTRIBUTE=INTERNAL_STATE

ATTRIBUTE=LAST_FAULT

ATTRIBUTE=LAST_RESTART

ATTRIBUTE=LAST_SERVER

ATTRIBUTE=LAST_STATE_CHANGE

ATTRIBUTE=LOAD

ATTRIBUTE=LOGGING_LEVEL

ATTRIBUTE=NAME

ATTRIBUTE=NOT_RESTARTING_TEMPLATE

ATTRIBUTE=OFFLINE_CHECK_INTERVAL

ATTRIBUTE=PLACEMENT

ATTRIBUTE=PROFILE_CHANGE_TEMPLATE

ATTRIBUTE=RESTART_ATTEMPTS

ATTRIBUTE=RESTART_COUNT

ATTRIBUTE=SCRIPT_TIMEOUT

ATTRIBUTE=SERVER_POOLS

ATTRIBUTE=START_DEPENDENCIES

ATTRIBUTE=START_TIMEOUT

ATTRIBUTE=STATE

ATTRIBUTE=STATE_CHANGE_TEMPLATE

ATTRIBUTE=STATE_CHANGE_VERS

ATTRIBUTE=STATE_DETAILS

ATTRIBUTE=STOP_DEPENDENCIES

ATTRIBUTE=STOP_TIMEOUT

ATTRIBUTE=TARGET

ATTRIBUTE=TYPE

ATTRIBUTE=TYPE_ACL

ATTRIBUTE=TYPE_NAME

ATTRIBUTE=UPTIME_THRESHOLD

This weird.

Former Member
0 Kudos

This problem is solved.