Hello All,
I'm having trouble running multiple jobs which insert records into the same
DB2 UDB for UNIX table? I keep getting:
insert into axu.mon_activity_insert ("STRING") values ('XXXXX')
DB21034E The command was processed as an SQL statement because it was not a
valid Command Line Processor command. During SQL processing it returned:
SQL0911N The current transaction has been rolled back because of a deadlock
or timeout. Reason code "2". SQLSTATE=40001
in one or more of the 5 simultaneous jobs (unix background) that are
performing the inserts. In Oracle I can mult-thread dozens of jobs each
inserting into the same table. What's the deal with DB2 UDB?
I am using the default database configuration parameters:
Interval for checking deadlock (ms) (DLCHKTIME) = 10000
Percent. of lock lists per application (MAXLOCKS) = 10
Lock timeout (sec) (LOCKTIMEOUT) = -1
Max storage for lock list (4KB) (LOCKLIST) = 100
Thanks!
Narayan
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
