A QSA parameter controls whether the “all columns” posting method or ROWID posting indexes are used for tables without selective indexes that contain LOBs, LONGs, XMLTypes, or user-defined datatypes (object types, REFs, and VARRAYs).
The parameter is called ALLOW_LONG_WO_UNIQUE and is specified in the VALUE column of the QUEST_EXEC_PARAMETER table:
By default, ALLOW_LONG_WO_UNIQUE parameter is set to NO. It can be changed while the agent is running and the database is online. It should only be changed to YES if you are certain that rows can be identified uniquely based on columns that do not contain LOBs, LONGs, XMLTypes, and user-defined datatypes (object types, REFs, and VARRAYs).
Collection trigger has failed (20777)
Trigger Oracle error is - 103
Error msg: Failed LW collector trigger
To post live transactions to reorganized copy tables, QSA uses a PL/SQL stored procedure and Oracle Call Interface (OCI) calls:
When a table contains a LONG column, changes to non-LONG columns are posted first with the stored procedure. Any changes needed for the LONG column are posted afterward with OCI calls.
Each execution of the stored procedure is called a “posting session”. If OCI calls are executed after the stored procedure is run, they are considered to be part of the posting session.
Both the stored procedure and OCI calls retrieve transactions in chronological order (oldest transactions first).
Note The reason OCI calls are used for LONG columns is to ensure that data of any size is successfully posted. LONG values larger than 32,760 bytes are not supported for PL/SQL. If a PL/SQL stored procedure were used to post a non-supported LONG value, data would be truncated.
© 2023 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Nutzungsbedingungen Datenschutz Cookie Preference Center