DB2 load - lock with force
Posted: Tue Nov 22, 2011 11:50 am
We have a job that is pulling from Teradata and writing directly to target tables on DB2. Sometimes it is failing with a lock timeout. DBAs have confirmed that it is not a deadlock scenario. We think it could be a user lock on the table that prevents our load.
The DB2 load utility has an option called 'lock with force' that will force off other locks so that the loader can achieve the locks that it requires. We have load scripts that take advantage of this.
Our DataStage job is using the DB2 Enterprise stage which does not have an explicit option for this. Does anyone know what the default behavior is? Does the Ent stage use lock with force or not? Is there a way to override that behavior? Some hidden or undocumented APT variable?
Thanks!
ps.. This is related to Failed DB2 load - Failed opening fifo
The DB2 load utility has an option called 'lock with force' that will force off other locks so that the loader can achieve the locks that it requires. We have load scripts that take advantage of this.
Our DataStage job is using the DB2 Enterprise stage which does not have an explicit option for this. Does anyone know what the default behavior is? Does the Ent stage use lock with force or not? Is there a way to override that behavior? Some hidden or undocumented APT variable?
Thanks!
ps.. This is related to Failed DB2 load - Failed opening fifo