User Guide

SAP AG November 2002
2. All the transactions that were still open at the time of the savepoint are determined using
the transaction list.
3. The transactions are processed in the way described in Restart or Recovery [Page
49].
See also:
Restartability [Page
38]
Example: Restart [Page
52]
ROLLBACK
In a ROLLBACK, all the changes made by a transaction [Page 152] or a subtransaction [See
SAP DB Library] on the database instance [Page 132] are reversed.
• Changes closed with a COMMIT [Page
129] can no longer be reversed with a
ROLLBACK.
• As a result of a ROLLBACK, a new transaction is implicitly opened.
In normal database operation, the database system performs the required ROLLBACK
actions independently. However, ROLLBACK can also be explicitly requested using
appropriate SQL statements.
In a restart, the system checks which transactions were terminated or closed with
a ROLLBACK statement. These actions are reversed.
Run Directory
The run directory is created when a new database instance [Page 132] is installed by the
database system (database parameter RUNDIRECTORY [Page 88]). The run directory is
used to store log files in which all actions and errors are logged. All the relative path names
relate to the run directory of the database instance.
See also:
SAP DB Directories [Page
77]
SAP DB Document Server
SAP DB Document Server is a database instance type [Page 132] of the SAP DB database
system.
In today’s information landscape, a large amount of data must be processed that does not
have the typical format of a relational database, but is “unstructured” (such as videos, XML
documents). SAP DB Document Server was developed on the basis of the SAP DB OLTP
[Page 149] relational database system to ensure that as much of this unstructured data as
possible can be processed outside the OLTP database. This improves the performance of the
SAP DB OLTP database.
One application example is the SAP Content Server.
User Manual: SAP DB 147