In the Operating user menu you can, among other things, stop an SAP liveCache database (transfer it to operational state OFFLINE).
Note
If a user is performing administration functions, administration is locked for all other users.
The stopping of an SAP liveCache database is performed using the Database Manager with the DBM command db_offline.
In accordance with the authorization concept, the user was assigned one of the roles SAP_BC_LVC_OPERATOR, SAP_BC_LVC_ADMINISTRATOR or SAP_BC_LVC_SUPERUSER.
Open the DBA Cockpit (transaction DBACOCKPIT) and 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
.Choose
.Choose Stop liveCache.
Choose ABAP Editor (transaction SE38).
Enter the report name RSLVCSTOP.
Create a variant of the report. You must enter the name of the database connection, among other things.
You can schedule the report with the variant defined by you for background processing (Define Job (transaction SM36) Scheduling Background Jobs).
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 OFFLINE operational state.
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.
The stopping of the SAP liveCache database is also logged in the SysLog of your SAP system (transaction SM21).