468,257 Members | 1,410 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 468,257 developers. It's quick & easy.

Triggers crashing database ?

Hi!

I have one table that tells me what data should be deleted. A procedure goes
over this table and deletes the data. After deleting a row an after delete
trigger is fired and inserts a row in another table, so we know what got
deleted. The problem is that sometimes these trigger crashed the database
and I get this error in db2diag.log:
RETCODE : ZRC=0x8602001A=-2046689254=SQLB_BADD "Bad Database, Can't flush"
DIA8427C The database has been marked as being damaged.

All connections are forced and crash recovery is initiated.
When I recreate that trigger everything is ok.

Any clues ?

Best regards,
Kovi
--
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
| Gregor Kovac | Gr**********@mikropis.si |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| In A World Without Fences Who Needs Gates? |
| Experience Linux. |
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
Mar 28 '06 #1
2 3901
Gregor Kovač wrote:
Hi!

I have one table that tells me what data should be deleted. A procedure
goes over this table and deletes the data. After deleting a row an after
delete trigger is fired and inserts a row in another table, so we know
what got deleted. The problem is that sometimes these trigger crashed the
database and I get this error in db2diag.log:
RETCODE : ZRC=0x8602001A=-2046689254=SQLB_BADD "Bad Database, Can't flush"
DIA8427C The database has been marked as being damaged.

All connections are forced and crash recovery is initiated.
When I recreate that trigger everything is ok.

Any clues ?

Best regards,
Kovi

I just found out that there were three aditional triggers (update, delete,
insert) that were inserting rows in a table with over 22 million rows. Then
I dropped them and everything was ok. Hmm....

Kovi
--
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
| Gregor Kovac | Gr**********@mikropis.si |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| In A World Without Fences Who Needs Gates? |
| Experience Linux. |
-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
Mar 28 '06 #2
Gregor Kovač wrote:
Gregor Kovač wrote:
Hi!

I have one table that tells me what data should be deleted. A procedure
goes over this table and deletes the data. After deleting a row an after
delete trigger is fired and inserts a row in another table, so we know
what got deleted. The problem is that sometimes these trigger crashed the
database and I get this error in db2diag.log:
RETCODE : ZRC=0x8602001A=-2046689254=SQLB_BADD "Bad Database, Can't flush"
DIA8427C The database has been marked as being damaged.

All connections are forced and crash recovery is initiated.
When I recreate that trigger everything is ok.

Any clues ?

Best regards,
Kovi

I just found out that there were three aditional triggers (update, delete,
insert) that were inserting rows in a table with over 22 million rows. Then
I dropped them and everything was ok. Hmm....

Kovi

Kovi,

That doesn't smell right. Please open a PMR so we can get to the bottom
of this.

Cheers
Serge
--
Serge Rielau
DB2 Solutions Development
IBM Toronto Lab
Mar 28 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

reply views Thread by Henry Hank | last post: by
1 post views Thread by jason_s_ford | last post: by
1 post views Thread by tim.pascoe | last post: by
5 posts views Thread by news.cyberlink.ch | last post: by
7 posts views Thread by ajomara | last post: by
debasisdas
reply views Thread by debasisdas | last post: by
4 posts views Thread by --CELKO-- | last post: by
reply views Thread by kermitthefrogpy | last post: by
reply views Thread by zattat | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.