Hi,
I had an issue this morning with my DB2 server running out of space. I was not able to find the root cause but the issue was with a trigger on a table. The trigger was created AFTER UPDATE on TABLE X. It checks the new value and performs some logic. If the logic satisfies, inserts a new row to table Y.
Problem here was the new table Y might already have the same row inserted. If present, the TRIGGER will throw an error due to primary key constraint. So trigger failed. But why would it create the transaction logs every minute and run out of space? After dropping the trigger, the logging stopped. Any help in this is greatly appreciated.
Thanks
Anis GovindaRao
I had an issue this morning with my DB2 server running out of space. I was not able to find the root cause but the issue was with a trigger on a table. The trigger was created AFTER UPDATE on TABLE X. It checks the new value and performs some logic. If the logic satisfies, inserts a new row to table Y.
Problem here was the new table Y might already have the same row inserted. If present, the TRIGGER will throw an error due to primary key constraint. So trigger failed. But why would it create the transaction logs every minute and run out of space? After dropping the trigger, the logging stopped. Any help in this is greatly appreciated.
Thanks
Anis GovindaRao