Neoview Control Query Default (CQD) Reference Guide (R2.5)

NOT_ATOMIC_FAILURE_LIMIT
Transaction control and lockingCategory
Specifies the maximum number of nonfatal errors that are allowed during a single non
atomic rowset insert statement. If the number of non fatal errors exceeds this value then
the execution of insert statement terminates in an error and the transaction is rolled back.
Description
‘30’ through ‘32000’
The default value is ‘32000’. Prior to R2.3 the default value was SYSTEM which meant
that there was no limit on the number of non-fatal errors. The setting SYSTEM is no longer
valid.
Values
Use when the user does not wish to proceed with the rowset insert statement because the
number of errors exceeds a certain value. If the data is expected to be of good quality and
the presence of a large number of nonfatal errors is a cause for concern, then this default
can be set to a value lower than the default and each occurrence of a large number of
nonfatal errors are treated as an error.
Usage
Not applicableProduction usage
Has the effect of disabling the not atomic inserts feature if the data is dirty and the default
has been specified to a low value. But can have a positive impact if bad data is an exception,
by causing execution of the insert statement to stop before it tries to insert more rows in a
large rowset that are likely to fail insertion.
Impact
AnyLevel
Not applicableConflicts/Synergies
Not applicableAddressing the real
problem
Neoview Release 1.0Introduced in release
Not applicableDeprecated in release
OPI_ERROR73_RETRIES
Transaction control and lockingCategory
The error 73 retry count for online populate index (OPI) is overridden by this CQD. After
all the online processing for OPI is complete, it tries to avoid rollback, if it finds some
operation (such as a utility) has a DDL lock (error 73's) by retrying. This is different than
the ONCOMMITERROR retries.
Description
Integer
The default value is Retry 10 times (about 20 minutes).
Values
Used to change the retries for when a populate index operation encounters locks. You
should not increase the retry count, and instead reduce it, on a busy system.
Usage
Not applicableProduction usage
Can extend the OPI elapsed time due to the retries, still without success.Impact
QueryLevel
Not applicableConflicts/Synergies
Not applicableAddressing the real
problem
Neoview Release 1.0Introduced in release
Not applicableDeprecated in release
NOT_ATOMIC_FAILURE_LIMIT 51