SAP Content Server
This page provides information about SAP MaxDB used as SAP Content Server for Knowledge Warehouse systems.
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).
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.
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.
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.
Find all user password information in note 2120775.
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.
Then file CS_Trace.txt is written. In this file you'll find e.g. connect errors.
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.
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.
Then files sqltrace[PID].pct are created in the working directory of the web server (on Microsoft Windows this is windows\system32).
Before executing a CHECK DATA WITH UPDATE in operational state ADMIN, read note 852168.
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.