Problems with cascade deletes ?

We are using NT Workgroup 7.3.3 and occasionnaly find ourselves with orphan records
in a table that is linked to its parent with a FK using a delete cascade.
All we do is delete some records in a few tables and let Oracle delete the corresponding records in the child tables. And it's only one or two child table per parent, not more than one generation down.
I can't say that our app is perfect but still I can't figure out how Oracle would permit the presence of these orphans after our delete operation. We do not update any PKs.
It does not happen all the time, and of course when I trace it it does not. But we still have that situation in all the schemas where the operation is done.
Would anyone know of a way for that situation to happen either because of an Oracle bug or a misuse of FK in our part. The only bizzare hint that we have is that the child table having orphan records is the only one where the parent PK column is generated from a sequence instead of character like the others.

Thanks for all the help ! !

Serge Beaulé, DBA
Informission Group Inc.
serge.beaule_at_informission.ca Received on Fri May 22 1998 - 12:49:25 CDT