sap_suse_cluster_connector does not know command gvi

[JPReyes]

Hello,

We are having an issue while setting up the SUSE failover... While

trying to start the cluster it fails when saphascriptco.so call command

"/usr/bin/sap_suse_cluster_connector gvi" with message "unkown

function gvi"

We have the latest sap_suse_cluster_connector version 1.0.0-0.8.1 on

Linux SUSE 11 SP2.

When I check the help "gvi" is not listed as an option"

/usr/bin/sap_suse_cluster_connector --help

/usr/bin/sap_suse_cluster_connector cmd options

  where cmd could be:

  help

  init

  cpa --res RES --act ACT --sta STA

  lsr --out FILE --sid SID --ino INO | --dbhost HOST --dbtype TYPE

  fra --res RES --act ACT [ --nod NODE ]

  lsn --out FILE --res RES

The system is ERP6 EHP6 and I have tried with several Kernels including

721_EXT and 741_EXT

See the logs attached.

sap_suse_cluster_connector.log

---------------------------------------------------

trc file: sap_suse_cluster_connector.log

---------------------------------------------------

Tue Jul 15 12:43:22 2014 : init()

Tue Jul 15 12:43:22 2014 : unkown function gvi

sapstartsrv.log

---------------------------------------------------

trc file: "sapstartsrv.log", trc level: 0, release: "721"

---------------------------------------------------

pid 3295

[Thr 140446778181472] Tue Jul 15 12:43:22 2014

SAP HA Trace: === SAP_HA_InitEx2: SAP UNIX HA Lib 720, patch 600,

changelist 1480835, optu (Mar 8 2014, 00:36:22) ===

SAP HA Trace: profile_params: setting cluster_connector =

"/usr/bin/sap_suse_cluster_connector"

SAP HA Trace: Fire system command /usr/bin/sap_suse_cluster_connector

init ...

SAP HA Trace: cluster_connector_init: Skript returns rc=0

SAP HA Trace: === SAP_HA_GetVersionInfo ===

SAP HA Trace: Fire system command /usr/bin/sap_suse_cluster_connector

gvi ...

SAP HA Trace: SAP_HA_GetVersionInfo: Skript returns rc=25

SAP HA Trace: --- SAP_HA_GetVersionInfo Exit-Code:

SAP_HA_NOT_IMPLEMENTED ---

SAP HA Trace: --- SAP_HA_InitEx2 Exit-Code: SAP_HA_OK ---

HA support limited to interface version 1 by HA product

CCMS agent initialization for instance type SCS: return code 0.

CCMS agent start: return code 0.

Initializing SAPControl Webservice

Starting AutoRestart thread

AutoRestart thread started

SapSSLInit failed => https support disabled

Starting WebService thread

Webservice thread started, listening on port 50013

Trusted http connect via Unix domain socket '/tmp/.sapstream50013'

enabled.

Anyone had the same issue?....

Regards, Juan

[fabian_herschel · Accepted solution]

You can safely ignore the failure. After several ha vendors including SUSE has been certified, SAP decided to enhance the API at sapstartsrv side to support additional scenarios. Together with SAP we decided to introduce a API query command (init_Ext2). This command probes, if a cluster connector is able to answer the question about the supported API level.

All connectors with API level1 are not able to answer this query and may write an error message.

If the Init_Ext2 does not get an answer on the API question it drives the connector in the API1 level, so

after this initial failure everything should be completely ok, because sapstartsrv and its connector library will fallback to API1 mode.

You need a very current SAP kernel o have the script connector library knowing about the init_Ext2 call and than the GVI call should avoided by the

script connector library.  If you already have a current SAP kernel we might need to check with SAP kernel development, if something in the

connector is broken in API1-fallback mode.

Hope this answer that helps.

[JPReyes · Accepted solution]

Hi Fabian,

Appreciate your help, sorry for the delay I was away for the last few days.

I'm doing some tests with the latest kernel available and still having a few issues with the cluster config, but let me document them before I post.

Regards, Juan

[fabian_herschel · Accepted solution]

If the issues are NOT related to the GVI-not-implemented-problem than we should close this thread as solved and you could report your new issues using a new thread. This makes it easier for others to find a thread and a solution.

[fabian_herschel · Accepted solution]

Hi Juan,

chould you check, if my answer from July 17th did answer your question? The thread

is still marked as "not answered" and thus is not that helpful for other users.

Regards

Fabian

[JPReyes · Accepted solution]

Hi Fabian.

Thanks for you answer, It certainly clarified a lot of the questions i had regarding the SUSE cluster connector.

Regards, Juan

[former_member188883]

Hi Juan,

Could you please use sap_suse_cluster_connector based on the version 2 of the sapscriptconnector API 2.

There is a guidelines provided using above connector in the document below.

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d079c1f2-5c6b-2f10-dcbb-a29c20865...

Regards,

Deepak Kori

[JPReyes]

sap_suse_cluster_connector is the latest version y have tried the saphascriptco.so that comes in at lease 3 releases of kernels.

The problem is not the script... the problem is that the script is calling sap_suse_cluster_connector with command gvi and that command is unknown to sap_suse_cluster_connector.

I want to know if there is a later version of sap_suse_cluster_connector or if i'm missing something here.

All the documentation (like the link you sent) list gvi as one of the options, but when i call for sap_suse_cluster_connector help it is not listed.

Regards, Juan

[former_member188883]

H Juan,

Can you try the SAP kernel combination given in SAP note

1693245 - SAP HA Script Connector Library

As per above SAP note

Currently two versions of SAP HA interface are available: Version 1 (available and supported by all currrently certified HA solutions) and Version 2 (under development, released for SAP partners (cluster vendors)

Regards,

Deepak Kori

[JPReyes]

Ok... that's worthy trying... I'm downloading an old kernel to extract the saphascriptco.so (version 1)...  I'll test that.

As far as I can see sap_suse_cluster_connector is having a problem with version 2 of saphascriptco.so

Regards, Juan

[Former Member]

Juan Reyes wrote:

As far as I can see sap_suse_cluster_connector is having a problem with version 2 of saphascriptco.so

From SAP Note 1693245 - SAP HA Script Connector Library already mentioned by for your case:

"

sapstartsrv and SAP HA script connector librray implement the enhanced SAP HA library interface, but vendor scripts have not yet implemented the new interface.

The SAP HA script connector librray reports to sapstartsrv that the new interface was not available. In sapstartsrv.log following lines could appear:

SAP HA Trace: --- SAP_HA_GetVersionInfo Exit-Code: SAP_HA_NOT_IMPLEMENTED ---

HA support limited to interface version 1 by HA product

This is no error, similar to item 2. The HA vendor certifaction was granted for the version 1 interface and is still valid. The new HA functions cannot be used by SAP Start Services.

"

[JPReyes]

Yes... I got that.  😄

[JPReyes]

OK, so I downloaded a kernel that is 2 year old to extract saphascriptco.so and add it to my 721_EXT kernel,  that seems to me working (not without some issues).

Wonder if there is any reason why SUSE has not released a sap_suse_cluster_connector compatible with the saphascriptco.so file that come with the newer kernels?... last update to that file was 2 years ago.

Regards, Juan

[former_member188883]

Hi Juan,

Thanks for sharing your experience with the setup.

As per the note shared above, SAP is progressing with downward compatible approach with newer kernels while other vendors are not keeping pace with SAP's kernel development

Regards,

Deepak Kori

[fabian_herschel]

SAP "surprised" the HA partners with the new calls. And that exactly after the solution where certified in detail with extremely detailed tests.

SAP together with SUSE in the LinuxLab developed than a fallback mode, so the multiple certified

and working HA solutions should NOT be broken. However maybe we need to check exactly your

SAP kernel level, if it already includes this fallback compatability.

SAP HA Trace: === SAP_HA_GetVersionInfo ===

SAP HA Trace: Fire system command /usr/bin/sap_suse_cluster_connector

gvi ...

SAP HA Trace: SAP_HA_GetVersionInfo: Skript returns rc=25

SAP HA Trace: --- SAP_HA_GetVersionInfo Exit-Code:

SAP_HA_NOT_IMPLEMENTED ---

SAP HA Trace: --- SAP_HA_InitEx2 Exit-Code: SAP_HA_OK ---

HA support limited to interface version 1 by HA product

This are the log entries which tells you that in intention the fallback mode to API gets activated.

It's currently a planned fallback, maybe the log entries should be more polite or should not tell

SAP_HA_NOT_IMPLEMENTED.