Decoding Siebel 8.x Audit Trail Data With Scripting
(Doc ID 796113.1)
Last updated on JULY 04, 2023
Applies to:
Siebel Audit Trail - Version 8.0 [20405] to 17.0 [IP2017] [Release V8 to V17]Siebel Tools - Version 8.0 [20405] to 17.0 [IP2017] [Release V8 to V17]
Information in this document applies to any platform.
NOTE: This document has been superseded by Siebel Bookshelf.
The contents of this note are now located in this Bookshelf section:
Bookshelf 8.1 > Siebel Applications Administration Guide > Audit Trail > Decoding the Audit Log File.
Details
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Purpose |
| Scope |
| Details |
| Additional Notes |
| Is it possible to generate decoded audit events that have a unique row ID? |
| Why does the function getAuditRowId() throw an exception if it finds more than one audit data record? |
| References |