master database only
syslogshold contains information about each database’s oldest active transaction (if any) and the Replication Server truncation point (if any) for the transaction log, but it is not a normal table. Rather, it is built dynamically when queried by a user. No updates to syslogshold are allowed.
The columns for syslogshold are:
Name |
Datatype |
Description |
---|---|---|
dbid |
smallint |
Database ID. |
reserved |
int |
Unused. |
spid |
smallint |
Server process ID of the user that owns the oldest active transaction (always 0 for Replication Server). |
int for cluster environments |
||
page |
unsigned int |
Starting page number of active portion in syslogs defined by oldest transaction (or the truncation page in syslogs for Replication Server). |
xactid |
binary(6) |
ID of the oldest active transaction (always 0x000000 for Replication Server). |
masterxactid |
binary(6) |
ID of the transaction’s master transaction (if any) for multidatabase transactions; otherwise 0x000000 (always 0x000000 for Replication Server). |
starttime |
datetime |
Date and time the transaction started (or when the truncation point was set for Replication Server). |
name |
char(67) |
Name of the oldest active transaction. It is the name defined with begin transaction, “$user_transaction” if no value is specified with begin transaction, or “$chained_transaction” for implicit transactions started by the ANSI chained mode. Internal transactions started by Adaptive Server have names that begin with the dollar sign ($) and are named for the operation, or are named “$replication_truncation_point” for Replication Server. |
xloid |
int null |
Lock ownership ID based on spid if the owner is a task, or on xdes if the owner is a transaction. |
Because of this change in the datatypes for the Cluster Edition, Sybase strongly recommends that you archive and truncate audit tables before you upgrade. This reduces the likelihood of a failed upgrade because of insufficient space in the sybsecurity database.