SAS/ACCESS 9.2 for Relational Databases: Reference, Fourth Edition

356 ORHINTS= Data Set Option 4 Chapter 11By default (OR_UPD_NOWHERE=YES), updates are performed in serializabletransactions so that you can avoid problems with extra WHERE clause processing andpotential WHERE clause floating-point precision.Specify OR_UPD_NOWHERE=NO for compatibility when you are updating a SAS 6view descriptor.Note: Due to the published Oracle bug 440366, sometimes an update on a row failseven if the row has not changed. Oracle offers this solution: When you create a table,increase the number of INITRANS to at least 3 for the table. 4ExampleIn this example, you create a small Oracle table, TEST, and then update the TESTtable once by using the default setting (OR_UPD_NOWHERE=YES) and once byspecifying OR_UPD_NOWHERE=NO.libname oralib oracle user=testuser pw=testpass update_lock_type=no;data oralib.test;c1=1;c2=2;c3=3;run;options sastrace=",,,d" sastraceloc=saslog;proc sql;update oralib.test set c2=22;update oralib.test(or_upd_nowhere=no) set c2=222;quit;This code uses the SASTRACE= and SASTRACELOC= system options to send theoutput to the SAS log.See AlsoTo assign this option to a group of relational DBMS tables or views, see the“OR_UPD_NOWHERE= LIBNAME Option” on page 163.“Locking in the Oracle Interface” on page 728“SASTRACE= System Option” on page 408“SASTRACELOC= System Option” on page 419“UPDATE_LOCK_TYPE= Data Set Option” on page 397ORHINTS= Data Set OptionSpecifies Oracle hints to pass to Oracle from a SAS statement or SQL procedure.Default value: noneValid in: DATA and PROC steps (when accessing DBMS data using SAS/ACCESSsoftware)DBMS support: Oracle