LIVECACHE ADMINISTRATION PDF

Archiving Backup Files Only necessary for log backups on data carriers of the File type. Scheduling an Interactive Log Liveecache. Name of the Database Connection. Tasks on Demand Perform the tasks in the table below when the corresponding events occur. Operating system commands Database Manager. Recommendation We recommend that you activate the automatic log backup.

Author:Milkree Vurisar
Country:Laos
Language:English (Spanish)
Genre:Business
Published (Last):19 May 2016
Pages:269
PDF File Size:15.7 Mb
ePub File Size:3.26 Mb
ISBN:318-7-46391-893-3
Downloads:21631
Price:Free* [*Free Regsitration Required]
Uploader:Akinojora



The database tool XCONS database console is used to display the operating system resources used by the database system, the distribution of database sessions among threads and the status of active database sessions.

XCONS is a command line tool. It can be used on all operating systems supported by the database system. We recommend that you only use XCONS in productive systems for analysis if you have a thorough knowledge of database and operating systems. How can I display task states? Which task states are available and what do they mean? The task state indicates whether a task is currently active and what action it is currently executing.

The names of some task states were changed as of Version 7. The new names appear in parentheses after each task state. There are special Vsuspend wait statuses, each of which is displayed under its own name. The number entry in brackets after a task status describes a wait situation that the relevant task is experiencing. In addition, the result does not display all possible wait situations; instead, it displays only those that have occurred in the system since the database was restarted.

An exclamation mark after the task status indicates that this task was canceled either by the application for example, due to a termination of the work process or by a kill or cancel command from the database console.

It is not uncommon for a task to have this status for a long time. The disconnect does not take place until the transaction that was cancelled is rolled back. A shared lock is set on the root page. The task waiting on the exclusive lock is not woken until the shared lock on the root is released.

Once the shared lock is approved, separators are used to determine the leaf where the searched record should reside. If the number PageNo of the page is fixed, a shared lock on the leaf is requested and a read access is performed for the lock in the data cache.

This access may be delayed due to a collision with an exclusive leaf lock. The subsequent access on the relevant leaf is executed with an exclusive lock, which may collide with another shared lock at leaf level. If you cannot carry out the change operation locally on the current leaf, a lock escalation takes place: in this case, the exclusive lock on the leaf and the shared lock on the root is released.

An exclusive lock on the root is requested so that the previously identified cross-leaf operation can be executed. If the root page was already changed previously by another operation, it is written explicitly by the delete process to prevent the next savepoint from having to wait for completion of the delete operation. TableRootExcl: A task attempts to set an exclusive lock on the root page of a table and has to wait because of a lock collision.

TableNodeShare: A task attempts to set a shared lock on a page at index level greater than 1 or at leaf level of a table and has to wait because of a lock collision. TableNodeExcl: A task attempts to set an exclusive lock on a page at index level greater than 1 or at leaf level of a table and has to wait because of a lock collision.

TableLvl1Share: A task attempts to set a shared lock on a page at index level equal to 1 or at leaf level of a table and must wait because of a lock collision.

TableLvl1Excl: A task attempts to set an exclusive lock on a page at index level equal to 1 of a table and has to wait because of a lock collision.

InvRootExcl: A task attempts to set an exclusive lock on the root page of an index and has to wait because of a lock collision. InvNodeShare: A task tries to set a shared lock on a page index or leaf level of an index and has to wait because of a lock conflict. InvNodeExcl: A task tries to set an exclusive lock on a page index or leaf level of an index and has to wait because of a lock conflict.

Wait statuses on page chains that contain object data:ObjRootShare: A task attempts to set a shared lock on the root page of a page chain of an object and has to wait because of a lock collision. ObjRootExcl: A task attempts to set an exclusive lock on the root page of a page chain of an object and has to wait because of a lock collision. ObjNodeShare: A task attempts to set a shared lock on a page of a page chain of an object and has to wait because of a lock collision.

ObjNodeExcl: A task attempts to set an exclusive lock on a page of a page chain of an object and has to wait because of a lock collision. Wait statuses on page chains that contain undo data:The database system writes undo log entries before images for transactions that change data in the database to undo log files page chains in the data area.

The undo log entries enable a transaction rollback or consistent views for example, in SAP liveCache. UndoRootShare: A task attempts to set a shared lock on the root page of an undo page chain and has to wait because of a lock collision. UndoRootExcl: A task attempts to set an exclusive lock on the root page of an undo page chain and has to wait because of a lock collision.

UndoNodeShare: A task attempts to set a shared lock on a page of an undo page chain and has to wait because of a lock collision.

UndoNodeExcl: A task attempts to set an exclusive lock on a page of an undo page chain and has to wait because of a lock collision. Wait statuses on page chains that contain history data:History files contain references to the terminated transactions belonging to the undo log files. At each savepoint, the database system writes the updated history files page chains to the data area. For performance reasons, several history files are always open in parallel.

As of Version 7. Once the garbage collectors have deleted the data that requires deletion, they also delete the relevant undo log files. This relieves the user task of the delete operation of the undo log files. Collisions may occur on the history files between the user task and garbage collectors. HistRootShare: A task attempts to set a shared lock on the root page of a history page chain and has to wait because of a lock collision. HistRootExcl: A task attempts to set an exclusive lock on the root page of a history page chain and has to wait because of a lock collision.

HistNodeShare: A task attempts to set a shared lock on a page of a history page chain and has to wait because of a lock collision. HistNodeExcl: A task attempts to set an exclusive lock on a page of a history page chain and has to wait because of a lock collision.

DC OvFlow: The data cache is used intensively at this time and cannot accept new data. The data cache can only start accepting data again when pages from the data cache have been written again to the volumes.

The data area cannot accept any more pages. The database hangs. To resolve the problem, add a new data volume. The log queues can only start accepting redo log entries again when the log writer has written data from the log queues to the log area. Database operation stops because no more log entries can be written to the log volume. To solve this problem, you must save the log area.

Adding a log volume does not help in this situation. Competing accesses are synchronized using special semaphores regions, reader-writer locks. Can I debug individual tasks? The files are cyclically synchronized. In the case of a database crash, the current content of the memory segments is synchronized with the memory mapped segments. SAP Support can evaluate them using a post-mortem console. Storage volume: The memory space depends on the memory that the runtime allocates internal structures.

Number of files: As of 7. Where can I find more information on the subject of the runtime environment?

LAE MTR4 PDF

LiveCache Administration

.

CRESTRON GLS-ODT-C-1000 PDF

LIVECACHE ADMINISTRATION PDF

.

HISTORY OF KUMARI KANDAM PDF

MaxDB Administration – Runtime Environment – SAP liveCache

.

Related Articles