In the Operating user menu you can, among other things, stop an SAP liveCache database (transfer it to the operational state OFFLINE).
If a user is performing administration functions, administration is locked for all other users.
An SAP liveCache database is stopped using the Database Manager with the DBM command db_offline.
Open DBA Cockpit (transaction DBACOCKPIT).
The display options in DBA Cockpit vary depending on which SAP NetWeaver release you are using.
SAP NetWeaver 7.1: Choose .
In the user menu, choose liveCache Assistant (transaction LC10).
Enter the name of the database connection. You can select the name from the list of existing names. You can restrict the search for the required name.
Choose Stop liveCache.
Choose the ABAP Editor (transaction SE38).
Enter the report name RSLVCSTOP.
Create a variant of the report. You must enter data such as the name of the database connection.
You can schedule the report with the variant defined by you for background processing (Define Job (transaction SM36).
All data that is currently in the data cache is saved to the data volumes. This ensures that the SAP liveCache database is in a consistent state.
The SAP liveCache database is transferred to the operational state OFFLINE.
If an error occurs during the stop, you can use the kernel log knldiag (Current Messages) and the current lcinit.log Logs to analyze the cause of the error. You will find an overview of liveCache operating in the DBA Cockpit in the user menu Properties.
The stopping of the SAP liveCache database is also logged in the SysLog of your SAP system (transaction SM21).