Does Audit Trail Work on CLOB Column Types?
(Doc ID 1676716.1)
Last updated on JANUARY 24, 2020
Applies to:Siebel CRM - Version 184.108.40.206  and later
Information in this document applies to any platform.
Customer is migrating Siebel 220.127.116.11 (Public Sector) from MS SQL Server to Oracle Exadata. Customer enabled audit on delete event of 'Case' entity. Note Case (S_NOTE_CASE) has a NOTE long column and its child entity of Case. On MS SQL Server Platform, the NOTE column is created as VARCHAR(MAX), whereas on the Oracle Exadata platform, it is created as a CLOB column.
When the record from Case entity is removed from the UI, Audit works fine without any errors on the MS SQL Platform. On the Oracle Exadata, the Delete is successful, but 'Auditing' fails with an error thrown in the UI.
As per the Tech Note, Audit on Long columns is not allowed.
Delete Fails On Business Component With Errors (ORA-01723) (ORA-06550) (SBL-DAT-00236) (ORA-00932) (SBL-DBC-00111) <Document 1538399.1>
Since customer is migrating from MS SQL Server to Oracle Exadata, Customer is going to lose crucial functionality.
At Business layer it is defined as DTYPE_TEXT with 4095 length. We checked the maximum length of data in the production for this column. Maximum is approximately 1200 characters.
What options does the customer have? Is it possible to convert the Physical type to Varchar 1999, since the max length is under 2000 characters?
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