Skip to end of metadata
Go to start of metadata

SAP Content Server

This page provides information about SAP MaxDB used as SAP Content Server for Knowledge Warehouse systems.


Availability
Log mode
Backup and Recovery
Upgrade
Changing the password of user SAPR3 resp. SAP<SID>
Traces
Check Data
Further information


Availability

SAP Content Server is available for Microsoft Windows and Unix/Linux. Released SAP MaxDB versions can be found in PAM. See also note 1983930 Availability of SAP Content Server 650.

back to top

Log mode

The SAP Content Server should not run with log mode AUTO OVERWRITE (in earlier versions called DEMO). Only the Cache Server instances are allowed to run with this log mode.
Please check note 599445 if you need to temporarily activate the AUTO OVERWRITE mode (e.g. for an Upgrade).

back to top

Backup and Recovery

Backup strategies for SAP Content Server can be found in note 319332. This note also contains information about recovery. However, this is actually the same as for a SAP MaxDB OLTP database. In case of problems please read General backup and recovery problems
Concerning the consistency between the SAP Content Server based on SAP MaxDB and the connected SAP System you need to ask the application developer.

back to top

Upgrade

Note 498036 lists the notes which need to be concidered for a SAP MaxDB upgrade. In case of an upgrade it is important to register the ODBC driver correctly. Therefore please pay attention to note 301352. Note 698915 describes how a new ODBC driver can be installed.

back to top

Changing the password of user SAPR3 resp. SAP<SID>

Notes 661852 and 212394 describe how the password of the SAP user can be changed for a SAP Content Server.
As of version 7.5 the ODBC driver does not convert the user/password information into upper case automatically anymore. If the new password should contain lower case characters, you need to specify the password in double quotes when you execute the ALTER PASSWORD statement.

Example:

ALTER PASSWORD sap TO "Example_1".

Find all user password information in note 2120775.

back to top

Traces

For a SAP Content Server there are two traces (in addition to the SAP MaxDB database trace). Both traces can be activated by changing file ContentServer.ini. This file is described in detail in note 329473.

SAP Content Server Trace

To activate the Content Server Trace you need to add row FullTrace=1 in section [ContentServer] of file ContentServer.ini.

Example:

[ContentServer]
KeepConnection=0
AdminSecurity=1
LogRequests=1
ResponseTrace=1
Log404Response=1
MaxTransferBlockSize=4096
FullTrace=1

Then file CS_Trace.txt is written. In this file you'll find e.g. connect errors.

Example:

000011408 Err 2003-09-05/13:45:47 CreateTab ContentStorage, connect error SQLConnect failed, Specified driver could not be loaded due to system error 126 (LiveCache)., Error Code: 160

In this example the connection to the SAP Content Server failed because of Microsoft Windows system error 126. The error text of this system error can be determined using XSYSRC.

Example:

C:\sdb\programs\bin>xsysrc 126
Errortext for errorcode 126:
'The specified module could not be found.'

Precompiler Trace

To activate the Precompiler trace for a SAP Content Server you need to add parameter sqltrace=1 to the [contRep-<RepositoryName>] section in file ContentServer.ini.

Example:

[contRep-YCP1]
ContentStorageHost=tti62
ContentStorageName=YCP1
Storage=ContentStorage.dll
Security=1
ContRepDescription=Contentrepository
driver=LiveCache
ResponseTrace=1
DefaultDocProt=
Log404Response=1
sqltrace=1

Then files sqltrace[PID].pct are created in the working directory of the web server (on Microsoft Windows this is windows\system32).

back to top

Check Data

Before executing a CHECK DATA WITH UPDATE in operational state ADMIN, read note 852168.

back to top

Further information

Originally the component for messages and notes for SAP Content Server was called KM-KW-CDB. You might find some notes still on this component. Current notes can be found on component BC-DB-SDB. The application component is called BC-SRV-KPR-CS.

back to top

Relevant SAP Notes

1619726 FAQ SAP Content Server

212394 DBM, DBA and Domain User initial password
301352 ODBC driver is not registered 
319332 Content Server backup strategies 
329473 Description of file ContentServer.INI 
498036 Overview installing SAPMaxDB/liveCache versions
661852 Setting the DB password for content servers 
698915 Importing a SAP DB ODBC driver 
852168 Do not execute VERIFY/CHECK DATA in the ADMIN (COLD) status