Hi,
We have a few batch processes which are working on partioned tables. Each process is run in 10 jobs which follow the key ranches in the partitions. Now there is one process, which uses also a log-database which contains other keys; most important is the (current) time-stamp. Only inserts take place in these processes.
It seems that this log-table makes the jobs waiting for each other.
What can I do that they don't wait anymore for each other?
- Would it help to lock on row level?
- Does it help to take checkpoints very often? (IMS/BMP) We do it now every 1000 inserts.
- Or is the only way to alter the table and define extra keys like the other tables so that it can be partitioned?
Thanks in advance!
Regards,
Crox
We have a few batch processes which are working on partioned tables. Each process is run in 10 jobs which follow the key ranches in the partitions. Now there is one process, which uses also a log-database which contains other keys; most important is the (current) time-stamp. Only inserts take place in these processes.
It seems that this log-table makes the jobs waiting for each other.
What can I do that they don't wait anymore for each other?
- Would it help to lock on row level?
- Does it help to take checkpoints very often? (IMS/BMP) We do it now every 1000 inserts.
- Or is the only way to alter the table and define extra keys like the other tables so that it can be partitioned?
Thanks in advance!
Regards,
Crox