Author Topic: ORA-06512 and ORA-04088 error ?  (Read 111 times)

0 Members and 1 Guest are viewing this topic.

Offline CyborgRepublic

  • Full Member
  • *
  • Posts: 207
  • Karma: +0/-0
    • View Profile
ORA-06512 and ORA-04088 error ?
« on: March 29, 2010, 12:49:53 PM »
I have created a trigger not to let records with certain fields null
to be inserted into the table:
IF :new.RUL_CODE is null or
:new.FES_UINS_CODE is null or
:new.FES_UIO_CALOCC is null then
RAISE_APPLICATION_ERROR(-20000,'Record is not saved. Check course
record and try to save again.');
end if;

The trigger is set to fire before insert.

The trigger does the trick preventing the record to go into the table,
but besides my error message it shows also ORA-06512 and ORA-04088
errors, which I’d prefer my users not to see. I found numerous
opinions that these messages are OK. One of the answers in this ng:
“It's normal situation. Your trigger raise application error.
You need define exception entry for this error in block where you
enter INSERT statement.
With best regards, Lisa”

How to define exception entry? How to hide ORA-06512 and ORA-04088
error messages?

Thank you for your help.

Techronnati | where technology never sleeps

ORA-06512 and ORA-04088 error ?
« on: March 29, 2010, 12:49:53 PM »

Mountain View


Related Topics

  Subject / Started by Replies Last post
0 Replies
Last post November 06, 2008, 11:39:48 PM
by Corps
1 Replies
Last post November 19, 2008, 07:04:47 AM
by Corps
0 Replies
Last post November 24, 2008, 07:13:56 AM
by h2obubbler
1 Replies
Last post April 06, 2010, 10:58:19 PM
by TDelight
2 Replies
Last post June 06, 2017, 02:54:11 AM
by nomadic

Posting Disclaimer: Any individual may post a message in this forum and may do so anonymously. Therefore, the sole author is exclusively and entirely responsible for all opinions in that message. They do not represent the official opinions of Techronnati, its administrators or moderators or the Techronnati Management. Techronnati is merely acting as an impartial conduit for constitutionally protected free speech and is not responsible and will not be held liable for the content of such messages. All images and service logos are trademarks of their respective owners.