Dear community,
Is it possible that a newly added column in a partitioned table can create deadlock ?
We look at our app code, we are 99% sure we partition our data correctly.
And our DBA says
"each block has some free space...may be newly added column consumed leftover space"
"and since INI_TRANS value is 1...per block...since less free space is available(due to new col addition)...we are unable to put more tnxs"
How does INI_TRANS affect number of parallel update and possibly cause deadlock ?
What the DBA shares below regarding the deadlock
---------Blocker(s)-------- ---------Waiter(s)---------
process session holds waits process session holds waits
2404 6309 X 2407 6502 S
2407 6502 X 2405 6372 S
2405 6372 X 1409 4103 S
1409 4103 X 2404 6309 S
Rows waited on:
Session 6309: obj - rowid = 0033DA34 - AAM9o0ACfAAOH6cAAA
(dictionary objn - 3398196, file - 159, block - 3702428, slot - 0)
Session 6502: obj - rowid = 0033D9B0 - AAM9mwACfAAOJaXAAA
(dictionary objn - 3398064, file - 159, block - 3708567, slot - 0)
Session 6372: obj - rowid = 0033D9B0 - AAM9mwACfAAOJhzAAA
(dictionary objn - 3398064, file - 159, block - 3709043, slot - 0)
Session 4103: obj - rowid = 0033DDD0 - AAM93QACfAAOLC5AAA
(dictionary objn - 3399120, file - 159, block - 3715257, slot - 0)