DB2 or Hash Lookup Problem?
Posted: Thu Jun 26, 2003 6:47 am
Dear all,
We are using DS 6, with DB2 7.2 both on AIX.
One of our job design is to read from a table, lookup the key values from a hash file, if the keys already in the hash use the value from the hash, if not found write new value to the hash and use the value (from the hash and/or the new value) to another table.
The lookup process is using a LookupRoutine.
The thing is, we are developing the jobs in a development Project (DSS_D) and development database (STGDB), and the job works perfectly.
But when we move the job to test project (DSS_T) and using test db (STGTS), the job lookup process didn't work, and the we always get the duplicate key error because the job keep writing the same key to the next table.
Both DSS_T and DSS_D, as well as STGDB and STGTS are in the same AIX machine, but STGDB in stginst1 instance, and STGTS in tstinst1 instance.
During development we make stginst1 as the main DB2 instance for DS, but since we found this problem in test environment, we change tstinst1 as the main DB2 instance for DS.
If we run the job in DSS_T or DSS_D using the same data and using STGDB, the job works perfectly. But if we run in DSS_T or DSS_D using STGTS the job always failed.
We already make the configuration of both instances and both databases to be exactly the same, but the same problem still happen.
Can anyone help me? Because I have no idea what's wrong, and I don't know what else to do. [V]
Please help me [:(] [:(] [:(]
Regards
ND
We are using DS 6, with DB2 7.2 both on AIX.
One of our job design is to read from a table, lookup the key values from a hash file, if the keys already in the hash use the value from the hash, if not found write new value to the hash and use the value (from the hash and/or the new value) to another table.
The lookup process is using a LookupRoutine.
The thing is, we are developing the jobs in a development Project (DSS_D) and development database (STGDB), and the job works perfectly.
But when we move the job to test project (DSS_T) and using test db (STGTS), the job lookup process didn't work, and the we always get the duplicate key error because the job keep writing the same key to the next table.
Both DSS_T and DSS_D, as well as STGDB and STGTS are in the same AIX machine, but STGDB in stginst1 instance, and STGTS in tstinst1 instance.
During development we make stginst1 as the main DB2 instance for DS, but since we found this problem in test environment, we change tstinst1 as the main DB2 instance for DS.
If we run the job in DSS_T or DSS_D using the same data and using STGDB, the job works perfectly. But if we run in DSS_T or DSS_D using STGTS the job always failed.
We already make the configuration of both instances and both databases to be exactly the same, but the same problem still happen.
Can anyone help me? Because I have no idea what's wrong, and I don't know what else to do. [V]
Please help me [:(] [:(] [:(]
Regards
ND