Regarding DBMS_ERRLOG.CREATE_ERROR_LOG

Question

Hi ,
I wanted to create one error table using existing packag DBMS_ERRLOG.
BEGIN
DBMS_ERRLOG.CREATE_ERROR_LOG('MG_TR_COMPANY_DESK');
END;
The above snipped is giving error:
[Error] Script lines: 1-4 --------------------------ORA-44002: invalid object name
ORA-06512: at "SYS.DBMS_ASSERT", line 283
ORA-06512: at "SYS.DBMS_ERRLOG", line 112
ORA-06512: at line 2
What could be the issue?

Answer 1

gulamoh wrote:
Hi,
Let me first tell you what iam trying to do:
1)     create table MG_TR_COMPANY_DESK as (select * from TR_COMPANY_DESK where 1=2);
TR_COMPANY_DESK is the existing table.
2) BEGIN
DBMS_ERRLOG.CREATE_ERROR_LOG('MG_TR_COMPANY_DESK');
END;
3) alter table MG_TR_COMPANY_DESK add constraint MG_TR_COMPANY_DESK_PK primary key(companyid);
Compay id is not unique in TR_Company_desk
4) insert /*+ APPEND */ into MG_TR_COMPANY_DESK
select * from TR_COMPANY_DESK
LOG ERRORS
REJECT LIMIT UNLIMITED;
Ideally above should happen and the the records which have violated the Unique constraint should go to err$_mg_tr_company_desk table..Correct
But I am getting the error
ORA-00001: unique constraint (CFDG_OWNER.MG_TR_COMPANY_DESK_PK) violated
Whats wrong I am doing?Ahh. see that is a different now. :)
As Peter has suggested, you can not use LOG ERRORS with direct path insert to catch unique constraint violation.
That is what is happening exactly in you case. The TR_COMPANY_DESK is having duplicate
records and a direct path insert is failing due to constraint violation. What happens when you change direct-path to conventional insert ?
Your DBMS_ERRLOG.CREATE_ERROR_LOG is not necessarily failing.
You can see that by checking whether ERR$_MG_TR_COMPANY_DESK table exists.
Edited by: user503699 on Jan 18, 2010 5:28 PM