Lynn Pettis (10/21/2010)
Okay, we think we solved the problem, but don't ask me why; especially since we couldn't rebreak it.Using Oracle's SQL Developer stored procedures and functions are by default compiled for debug.
When we were esearching this problem, we were getting the problem with a duplicate entry being created where one shouldn't, logicaly thinking. Well, this morning we recompliled all the stored procedures and functions in Dev without debug. Problem fixed. Recompiled the stored procedures and functions for debug, still fixed! What?? It didn't break? WT%!?!.
Went into Test, problem existed there. Compiled all procedures and functions without debug, problem fixed.
If anyone with Oracle experience can explain this, I'm all ears and willing to learn something new.
Can't explain it but, as a rule of thumbs the closer you are to the database the better - if in doubt apply ddl and compile code via sqlplus.
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.