110 PACKETSIZE= LIBNAME Option Chapter 9
Syntax
OR_UPD_NOWHERE= YES | NO
Syntax Description
YES
specifies that SAS does not use an additional WHERE clause to determine whether
each row has changed since it was read. Instead, SAS uses the SERIALIZABLE
isolation level (available with Oracle 7.3 and above) for update locking. If a row
changes after the serializable transaction starts, the update on that row fails.
NO
specifies that SAS uses an additional WHERE clause to determine whether each row
has changed since it was read. If a row has changed since being read, the update fails.
Details
Use this option when updating rows without locking
(UPDATE_LOCK_TYPE=NOLOCK).
By default (OR_UPD_NOWHERE=YES), updates are performed in serializable
transactions. This enables you to avoid extra WHERE clause processing and potential
WHERE clause floating point precision problems.
ORACLE_73_OR_ABOVE is an alias for this option.
Note: Due to the published Oracle bug 440366, sometimes an update on a row fails
even if the row has not changed. Oracle offers the following solution: When creating a
table, increase the number of INITRANS to at least 3 for the table.
See Also
To apply this option to an individual data set or a view descriptor, see the data set
option “OR_UPD_NOWHERE= Data Set Option” on page 198
PACKETSIZE= LIBNAME Option
Enables you to specify the packet size for SYBASE to use
Valid in: the SAS/ACCESS LIBNAME statement
DBMS support: SYBASE
Default value: current server setting
Syntax
PACKETSIZE=numeric-value
