SAP Content Server 6.40 MaxDB 7.8 DB-Connect failed

[Former Member]

Hi specialtists, gurus ...

I installed a Content Server 6.40 (with newest patch) with a MaxDB 7.8 (newest build) on SuSE SLES 11 SP1 64 bit with a compiled apache 2.2.24. The apache server seems to work fine, but a servinfo request in 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, 619726, 822239, 1022330, 698915, 1710193, 664384 and much more ....

The cs module is loaded by apache: 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

Even soft links didn' help.

I'm out of ideas now.

Can anybody help?

Thanks.

Ralph

[Former Member]

It is clear that CS can't connect to the DB. Firstly make sure that MaxDB is running. Can you check that MaxDB is actually listening on localhost? Does it help if you change localhost to the hostname of the server? Try switching on trace (FullTrace = 1) and see what is logged in cs_trace.txt.

If you stil can't locate the problem, see if the problem is with the environment variables. See SAP note 1727986 for details.

https://service.sap.com/sap/support/notes/1727986

[Former Member]

HI Samuli,

thank you for suggestion.

on Linux I cannot set FullTrace. I already find this note, but the sripts set LD_LIBRARY_PATH to:

declare -x LD_LIBRARY_PATH="/sapdb/programs/lib"

After MaxDB installation via sapinst the directory of LD_LIBRARY_PATH contains only this files:

dbcs2:cs2cs> ls -al /sapdb/programs/lib

total 13088

dr-xr-xr-x  2 sdb  sdba       4096 2013-03-21 10:54 .

dr-xr-xr-x 10 root sapinst    4096 2013-03-21 11:29 ..

-r-xr-xr-x  1 sdb  sdba    8836524 2013-03-01 15:59 libicudata.so.34

-r-xr-xr-x  1 sdb  sdba    1502580 2013-03-01 15:59 libicui18n.so.34

-r-xr-xr-x  1 sdb  sdba    1421704 2013-03-01 15:59 libicuuc.so.34

-r-xr-xr-x  1 sdb  sdba    1595641 2013-03-01 16:24 libsapni.so

In older MaxDB versions the library libsqlsqd.so remained in this directory. In version 7.8 they are located now in /sapdb/<SID>/db/lib. Additionaly the library names are changed to libsdbodbc.so. This new names are not implemented in die mod_sapcs* modules. A grep on these files get only matches, if I search with libsqlod and no matches. if search with libsdbodbc.

I got a successfull connect to DB with isql and a configuration with .odbc.ini (also over localhost)

[SAPMaxDBCS2]

ServerDB=CS2

ServerNode=localhost

Driver=/sapdb/CS2/db/lib/libsdbodbc.so

It seems that the cs modules for apache don't know about these changes.

Regargs,

Ralph

[Former Member]

In order to switch on trace, add the following line to your [ContentServer] section:

FullTrace=1

See SAP note 329473 for details.

https://service.sap.com/sap/support/notes/329473

The DBENV.SH from SAP note 1727986  will correctly set the LD_LIBRARY_PATH environment variable to point to the location of newer MaxDB versions. Just execute the script and see the value of the environment variable after execution, it should point to your MaxDB location. Make sure the environment variable SAPSYSTEMNAME is also set.

[Former Member]

Hi Samuli,

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

Parameter FullTrace is not available for Unix.

Actually the environment variable LD_LIBRARY_PATH is set to

by the scripts.

The content server modules for apache contain the path to the ODBC libraries. I "grep"ed them with LD_LIBRARY_PATH and saw that 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. and they use ./lib64 subfolder instead of ./lib in a 64 bit/MaxDB 7.8 environment.

Regards,

Ralph

[Former Member]

The attachment is not visible.

I actually think that you might be correct. The last supported MaxDB version for 64-bit SLES11 in the Content Server 6.40 context is 7.7. MaxDB 7.8 is only supported on Windows and AIX. To add to that there is an interresting bit of information in SAP note 1619726:

Note the following: Currently (August 2011), ODBC versions higher than 7.6 on UNIX are not yet used in the content server environment.

https://service.sap.com/sap/support/notes/1619726