SAP Content Server 6.40 MaxDB 7.8 DB-Connect failed

[Former Member]

Hi specialists, gurus ...,

I installed a Content Server 6.40 (newest patch) on SuSE SLES 11 SP1 with a MaxDB 7.8 (64 Bit, newest build) and apache 2.2.24. Apache server seems to work fine but a http-request (serverinfo) within the browser returns:

serverType="SAP HTTP Content Server";serverVendorId="SAP AG";serverStatus="running";serverDate="2013-03-21";serverTime="10:41:32";startUpDate="2013-03-21";startUpTime="10:41:24";lastAccessDate="2013-03-21";lastAccessTime="10:41:24";

contRep="ZKOWLWAREH";contRepStatus="offline";contRepStatusDescription="SQLConnect failed, [SAP AG][LIBSQLOD SO][MaxDB] Unable to connect to data source;-709 CONNECT: (cannot create communication semaphore), Error Code: -709";

contRep="ZOFFCONT";contRepStatus="offline";contRepStatusDescription="SQLConnect failed, [SAP AG][LIBSQLOD SO][MaxDB] Unable to connect to data source;-709 CONNECT: (cannot create communication semaphore), Error Code: -709";

The following notes I followed up: 1353266, 1571193, 735598, 822239, 1022330, 1619726,1466917 ....

The modules on apache side is loaded: LoadModule sapcs_module  modules/mod_sapcs22.so

The cs.conf looks like this:

[ContentServer]

TraceLevel=debug

AdminSecurity=0

AdminSecurityGroup=sapsys

ContRepRoot=/usr/sap/cs/cs2cs/contrep

ContentStorageHost=localhost

ContentStorageName=CS2

StorageDriver=SAPDBStorage

PSEDir=/usr/sap/cs/cs2cs/security

driver=SAP MaxDB CS2

Also soft links with libsqlod.so to the libraries didn't help.

I am out of ideas now.

Any other ideas?

Thanks in advance.

Ralph

[former_member188883]

Hi Ralph,

Is the MaxDB database up and running .Please check this.

Regards,

Deepak Kori

[Former Member]

Hi Deepak,

sure, the DB is running.

Regards,

Ralph

[former_member188883]

Hi Ralph,

Please check the SAP Note No. 1727986.

What SAP kernel version do you have on your system?

Post output of "sdbregview -l" command, run it on application server.

Also found some relevant information from SAP note 1353266

1. 3. UNIX/Linux

If you entered the path for SQLDBC, that is, <INDEP_PROG_PATH>/lib[/lib64] (for example, /sapdb/programs/lib) *manually* in the environment of the user <sid>adm and/or sqd<sid> for one of the variables LD_LIBRARY_PATH, SHLIB_PATH, or LIBPATH when using SAP Kernel 640_EX2, remove this entry and install the DBENV files (.dbenv) that are provided with SAP Note 1066891 instead.
Otherwise, in the environment variables mentioned above, this *old* path for SQLDBC will lead to the following database connection error in the dev traces and/or the file trans.log (during the connection test using R3trans -d) because the SQLDBC of the legacy installation is used instead of the new SQLDBC of the isolated client installation CL_<SAPSID> after you upgrade to MaxDB Version 7.8:
  ERROR => Connect to database failed, rc = -10709
  (Connection failed (RTE:cannot create communication semaphore))

Hope this helps.

Regards,

Depak Kori

[Former Member]

Hi Deepak,

thanks for suggestion, but I already found this note and it is implemented.

Actually the environment variable LD_LIBRARY_PATH is set to

by the scripts.

Please keep in mind that is not a ABAP kernel. The content server modules for apache contain the path to the ODBC libraries. They use the library path variable, but they are searching for libsqlod.so, not for libsdbodbc.so. It seems, that the modules don't know the 7.8 library path structure. may be the use ./lib64 subfolder instead of ./lib in a 64 bit enviroment.

Regards,

Ralph

[former_member188883]

Hi Ralph,

So is the problem resolved now.

In such a case you may close this thread.

Regards,

Deepak Kori

[Former Member]

Hi Deepak,

the problem is not solved.

Regards,

Ralph Breier

[former_member188883]

Hi Ralph,

Could you share the current state of the issue.

Regards,

Deepak Kori

[Former Member]

Hi Deepak,

the state is the same as at 23th march. I already opened a support case/message (276615 / 2013) at 27th march in marketplace, but there is no reaction from SAP side until now.

Regards,

Ralph Breier