AP TB PERFORMANCE
Hi All,
While executing the AP TB rebuild the XLA_TB_WORK_UNITS will have both PROCESSING and UNPROCESSED rows. And the UNPROCESSED rows will be reducing and finally no rows will be available in this table.
This is happening quite fine with my TEST Instance whereas in PROD, due to previous rebuilds concurrent requests had been cancelled and whenever a new rebuild command executed all the unprocessed begin to process.
My query is how to avoid all these UNPROCESSED rows and only the freshly defined DEFINITION_CODE to be executed, so that the time taken was rebuild would be minimal.
While executing the AP TB rebuild the XLA_TB_WORK_UNITS will have both PROCESSING and UNPROCESSED rows. And the UNPROCESSED rows will be reducing and finally no rows will be available in this table.
This is happening quite fine with my TEST Instance whereas in PROD, due to previous rebuilds concurrent requests had been cancelled and whenever a new rebuild command executed all the unprocessed begin to process.
My query is how to avoid all these UNPROCESSED rows and only the freshly defined DEFINITION_CODE to be executed, so that the time taken was rebuild would be minimal.
Tagged:
1