SBYN_AUDIT
This table maintains a log of each instance in which any of the master index database tables are accessed through the EDM. This includes each time a record appears on a search results page, a comparison page, the View/Edit page, and so on. This log is only maintained if the EDM is configured for it. This table can grow very large over time and might require periodic archiving. The differences in data types between Oracle and SQL Server are noted in Table 10. The Oracle type is on the first line, and the SQL Server type is on the second.
Table 10 SBYN_AUDIT Table Description|
Column Name |
Data Type |
Description |
|---|---|---|
|
VARCHAR2(20) Varchar(20) |
The unique identification code for the audit record. This column cannot be null. |
|
|
VARCHAR2(20) Varchar(20) |
The name of the parent object as defined in the Object Definition file. |
|
|
VARCHAR2(15) Varchar(15) |
The EUID whose information was accessed during an EDM transaction. |
|
|
VARCHAR2(15) Varchar(15) |
The second EUID whose information was accessed during an EDM transaction. A second EUID appears when viewing information about merge and unmerge transactions, comparisons, and so on. |
|
|
VARCHAR2(32) Varchar(32) |
The type of transaction that caused the audit record to be written. This column cannot be null. |
|
|
VARCHAR2(120) Varchar(120) |
A brief description of the transaction that caused the audit record to be written. |
|
|
DATE datetime |
The date the transaction that created the audit record was performed. This column cannot be null. |
|
|
VARCHAR2(20) Varchar(20) |
The user ID of the person who performed the transaction that caused the audit log. This column cannot be null. |
- © 2010, Oracle Corporation and/or its affiliates