Forums | Aggregator | Books | Industry News | Firefox Plugins | Social | Links

Comments

DML Error Logging in Oracle 10g Database Release 2 - Use this new feature to capture errors and allow DML operations to complete successfully.



venki said...

i tried the qureies its giving me the error...

LOG ERRORS INTO err$_dest ('INSERT') REJECT LIMIT UNLIMITED
*
ERROR at line 4:
ORA-00933: SQL command not properly ended

same log errors......error for this syntax...

can u please help me..............

Tim... said...

Hi.

Please don't ask technical questions in the comments section. They should be asked in the forum. This is for comments about the article contents.

The code provided works fine for me when using Oracle 10g Release 2 (10.2.0).

Cheers

Tim...

d kari said...

is this dml logging work on remote tables like

INSERT INTO dest@remote
SELECT *
FROM source
LOG ERRORS INTO err$_dest@remote ('INSERT') REJECT LIMIT UNLIMITED;

joemcglynn said...

thanks for concise and complete explanation of how the LOG ERRORS feature works. This was the sole url I could find which provides quality online documentation on this feature !.

SHAHID said...

wonderfull and very helpfull articla.
if you could write another artical for advance level.

tanks

kk said...

A very good article indeed. This is very helpful.

Razvan said...

I have a problem when using in a select statement the decode function
ORA-38908: internal error occurred during DML Error Logging
ORA-24328: illegal attribute value
Pls help

Tim... said...

Questions in forum. Says so in the big red letters above the box you typed into. :)

Cheers

Tim...

elayer said...

I think, thats an awfull exception logging method from oracle.

You have to change your statements in order to get the exception logging working. This ist not in all situations possible in praxis!

DB2 has an exception logging where you don't have to change your DML-Statements. This is usefull!

daniel said...

First of all, thank's for the article, Tim. It's very useful as always.

Second, RE elayer. I agree i would be much more convenient if the feature worked without code change. On the other hand I don't thin this was intended to get employed in PROD. In test it makes sense.

Tim... said...

Daniel: Not sure why you think it is not a production feature. I think it is very much so!

Cheers

Tim...

DO NOT ask technical questions here! They will be deleted!

These comments should relate to the contents of a specific article. Constructive criticism is good. Advertising and offensive comments are bad and will be deleted!

Add your comments here.
Name
Comment
(max 400 chars - plain text)