Constraint voilation-AD error

Can anybody tell me what this error mean?
Unable to set user info: 'SetInfo(): 0X8007202F: , 000020B5: AtrErr: DSID-03152392, #2:
0: 000020B5: DSID-03152392, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 200f4 (homeMDB)
1: 000020B5: DSID-03152392, problem 1005 (CONSTRAINT_ATT_TYPE), data 0, Att 200ab (homeMTA)
, A constraint violation occurred.
Thanks.

Can anybody tell me what this error mean?
Unable to set user info: 'SetInfo(): 0X8007202F: ,
000020B5: AtrErr: DSID-03152392, #2:
0: 000020B5: DSID-03152392, problem 1005
5 (CONSTRAINT_ATT_TYPE), data 0, Att 200f4 (homeMDB)
1: 000020B5: DSID-03152392, problem 1005
5 (CONSTRAINT_ATT_TYPE), data 0, Att 200ab (homeMTA)
, A constraint violation occurred.
Thanks.Your homeMDB and homeMTA values are being evaluated and validated in AD and are not correct - check with your Exchange Admins (especially if you have a clustered Exchange environments - your AD login server, the location that the MTA is running on and the server your MDB is stored on may all be different from each other

Similar Messages

Constraint voilation issue.

Hi All,
I am having 2 tables A and table b. table A has a fk constraint in table B (note table A and table B are not master detail)
When I add data to Table A i am programmatically auto generating data for Table B and commiting the data in the same transaction.
However when i do this i get the below error.
Constraint "FK_IFW_SRV_RGR" is violated during post operation "Insert" using SQL statement
How do i commit the data of table B first and then table A in one transaction?
Or is there a better way to handle this ?
Thanks
Ajay

Can you mention which technology using.There is no any sign of JDev-ADF in your post, looking as a candidate for Database Forum.
However, I assume that child record is not referencing to parent record that's y constraint violation is coming.
Insert your Parent record then commit child record.

An approach to processing "constraint violation" oracle errors.

Hello,
We are using Toplink to map our classes to the tables. What would be the best way in the framework to map "constraint violation" sql exceptions to readable error messages sent back to the users?
Say, we need to insert new Member record. The Member table has 10 foreign keys for lookup tables such as member_type, member_level, etc...The straight forward approach is to check all the FKs using queries before inserting the Member record and generate corresponding error messages if any of the FKs fails.
Is there a more generic and ellegant approach for this?
thank you

This is something that is generally left up to the application. Many approach this by issuing the insert and getting the exception then. Others do as you described.

Catching unique constraint voilation at the VO level

I have a Result table which is used as Result table/ for updation/ for insertion of new row.
The underlying db table on which the Eo and consequently VO are based has a unique constraint which I want to catch and throw a suitable exception when the user is trying to update or insert using the result table which in my case is an advanced table. I am unable to figure out at what place I need to put the check. Though I am trying to handle the said condition before calling the getTransaction().commit(), I guess the DB is throwing the error even earlier which I presume is at the point of insertion into the Db which I guess happens at the EO setAttribute Level. So is it right to put the check at the setters in the EO???
Kindly provide feedback as how to overcome this problem

GFMIS.PK_ELTRADERID
ON (lct.trader = exl.trader)Your ON clause should be work on the same column of your PK, that should be enough to avoid the unique constraint violation.
Nicolas.

(Error) ORA-00001: unique constraint (WHSE_DBA.PK_DELPHI_TRANS_FACT) violat

I have a stored proc which runs every night. The stored proc is giving a unique constraint violation.
(Error) ORA-00001: unique constraint (WHSE_DBA.PK_DELPHI_TRANS_FACT) violated.
Any idea about how to debug this.

I want to create an error table on the stored proc shown below. I know I have to add something in the exceptions. Can anyone give me the commands and where to add it.
CREATE OR REPLACE PROCEDURE WHSE_DBA.DM_LD_DELPHI_TRANS_FACT
IS
-- VARIABLE DECLARATIONS
LAST_LOAD_DATE                   DATE;
INSERTCOUNT                 NUMBER:=0;
-- LOGGING VARIABLES AND CONSTANTS
TARGETTABLE                 CONSTANT VARCHAR2(20):='DELPHI_TRANS_FACT';
MSGUNKNOWNERR               CONSTANT VARCHAR2(20):='Error';
NBRIGNOREERR                CONSTANT NUMBER:=12541;
DEFDATE                     CONSTANT DATE:='01-OCT-2006';
ERRDESCRIPTION              VARCHAR2(255);
V_DELPHI_TRANS_TOTAL           NUMBER;
V_DELPHI_TRANS_FACT_TOTAL   NUMBER;
BEGIN
-- LOOK UP LAST LOADED RECORD
SELECT NVL(MAX(SNAPSHOT_DATE),DEFDATE)
INTO LAST_LOAD_DATE
FROM DELPHI_TRANS_FACT;
-- * LOAD ALL DIMENSION TABLES
-- BUDGET_YR_DIMENSION
INSERT INTO BUDGET_YR_DIMENSION (BUDGET_YEAR, SNAPSHOT_DATE)
(SELECT DISTINCT BUD_YR, SYSDATE
FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM BUDGET_YR_DIMENSION
WHERE BUDGET_YEAR=OUTER.BUD_YR));
-- EFF_DATE_DIMENSION
INSERT INTO EFF_DATE_DIMENSION (PAID_FIS_YEAR, PAID_QTR, EFFECTIVE_DATE, SNAPSHOT_DATE)
(SELECT DISTINCT CVT_DATE_TO_FISCAL_YEAR(EFF_DT), PD_QTR, EFF_DT, SYSDATE
FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM EFF_DATE_DIMENSION
WHERE EFFECTIVE_DATE=OUTER.EFF_DT));
-- PROC_DATE_DIMENSION
INSERT INTO PROC_DATE_DIMENSION (PROCESS_DATE, SNAPSHOT_DATE)
(SELECT DISTINCT PROC_DT, SYSDATE
FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM PROC_DATE_DIMENSION
WHERE PROCESS_DATE=OUTER.PROC_DT));
-- ORG_DIMENSION
INSERT INTO ORG_DIMENSION (ORG,COST_CTR,SNAPSHOT_DATE)
(SELECT DISTINCT ORG, CC_CD, SYSDATE
FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM ORG_DIMENSION
WHERE ORG=OUTER.ORG));
-- BPAC DIMENSION
INSERT INTO BPAC_DIMENSION (BPAC, AFC_CD, PE_CODE, SNAPSHOT_DATE)
(SELECT DISTINCT BPAC, AFC_CD, PE, SYSDATE
FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM BPAC_DIMENSION
WHERE BPAC=OUTER.BPAC));
-- FUND DIMENSION
INSERT INTO FUND_DIMENSION (FUND,APPROP_CD,LIM_CD,SNAPSHOT_DATE)
(SELECT DISTINCT FUND, APPROP_CD, APPLIM_CD, SYSDATE
FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM FUND_DIMENSION
WHERE FUND=OUTER.FUND));
-- OBJ_CD_DIMENSION
INSERT INTO OBJ_CD_DIMENSION (OBJ_CD,SNAPSHOT_DATE)
(SELECT DISTINCT OC_CD, SYSDATE
FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM OBJ_CD_DIMENSION
WHERE OBJ_CD=OUTER.OC_CD));
-- GLA DIMENSION
INSERT INTO GLA_DIMENSION (GLA_CD,SNAPSHOT_DATE)
(SELECT DISTINCT GLA, SYSDATE FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM GLA_DIMENSION
WHERE GLA_CD=OUTER.GLA));
-- PROJECT_TASK_DIMENSION
INSERT INTO PROJECT_TASK_DIMENSION (PROJECT_NO,TASK_NO,SNAPSHOT_DATE)
(SELECT DISTINCT PROJ_NBR, TASK_NBR, SYSDATE FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM PROJECT_TASK_DIMENSION
WHERE PROJECT_NO=OUTER.PROJ_NBR
AND TASK_NO=OUTER.TASK_NBR));
-- TRANS_DESC_DIMENSION
INSERT INTO TRANS_DESC_DIMENSION (DESCRIPTION,SNAPSHOT_DATE)
(SELECT DISTINCT DESCR, SYSDATE FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM TRANS_DESC_DIMENSION
WHERE DESCRIPTION=OUTER.DESCR
AND OUTER.DESCR IS NOT NULL));
-- SUPPLIER_DIMENSION
INSERT INTO SUPPLIER_DIMENSION (SUPPLIER_NAME, SNAPSHOT_DATE)
(SELECT DISTINCT VENDOR_NAME, SYSDATE FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM SUPPLIER_DIMENSION
WHERE SUPPLIER_NAME=OUTER.VENDOR_NAME));
-- DELPHI_INV_DIMENSION
INSERT INTO DELPHI_INV_DIMENSION (INVOICE_NO, SNAPSHOT_DATE)
(SELECT DISTINCT INV_NO, SYSDATE FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM DELPHI_INV_DIMENSION
WHERE INVOICE_NO=OUTER.INV_NO));
-- DELPHI_PO_DIMENSION
INSERT INTO DELPHI_PO_DIMENSION (PO_NO, SNAPSHOT_DATE)
(SELECT DISTINCT PO_NO, SYSDATE FROM DELPHI_TRANS OUTER
WHERE NOT EXISTS
(SELECT 1
FROM DELPHI_PO_DIMENSION
WHERE PO_NO=OUTER.PO_NO));
-- TEMPORARILY DISABLE KEY FOR FASTER LOADING
DB_MISC.PRO_EXE_DDL('ALTER TABLE DELPHI_TRANS_FACT DISABLE CONSTRAINT PK_DELPH_TRANS_FACT');
    -- MOVE DATA INTO TABLE
     INSERT INTO DELPHI_TRANS_FACT (BPAC_KEY, ORG_KEY, FUND_KEY, OBJ_CD_KEY, GLA_KEY,
     EFF_DATE_KEY, PROC_DATE_KEY, PROJECT_TASK_KEY, BUDGET_YR_KEY, DELPHI_TRANS_DESC_KEY,
     BALANCE, COMMIT_AMT, UDO_AMT, AEU_AMT, AEP_AMT, OBLIGATION_AMT, SNAPSHOT_DATE,
     SUPPLIER_KEY, DELPHI_INV_KEY, DELPHI_PO_KEY)
     (SELECT BPAC_KEY, ORG_KEY, FUND_KEY, OBJ_CD_KEY, GLA_KEY, EFF_DATE_KEY, PROC_DATE_KEY,
     PROJECT_TASK_KEY, BUDGET_YR_KEY, TRANS_DESC_KEY, SUM(BAL), SUM(COMMIT_AMT), SUM(UDO_AMT),
     SUM(AEU_AMT), SUM(AEP_AMT), SUM(OBLIGATION_AMT), MAX(SYSDATE), SUPPLIER_KEY, DELPHI_INV_KEY,
     DELPHI_PO_KEY
     FROM BPAC_DIMENSION, ORG_DIMENSION, FUND_DIMENSION, OBJ_CD_DIMENSION, GLA_DIMENSION,
    EFF_DATE_DIMENSION, PROC_DATE_DIMENSION, PROJECT_TASK_DIMENSION, BUDGET_YR_DIMENSION,
     TRANS_DESC_DIMENSION, DELPHI_TRANS,     SUPPLIER_DIMENSION, DELPHI_INV_DIMENSION, DELPHI_PO_DIMENSION
     WHERE DELPHI_TRANS.SNAPSHOT_DATE>LAST_LOAD_DATE
     -- JOIN WITH BPAC_DIMENSION
    AND DELPHI_TRANS.BPAC=BPAC_DIMENSION.BPAC
     -- JOIN WITH ORG_DIMENSION
     AND DELPHI_TRANS.ORG = ORG_DIMENSION.ORG
     -- JOIN WITH FUND_DIMENSION
     AND DELPHI_TRANS.FUND = FUND_DIMENSION.FUND
     -- JOIN WITH OBJ_CD_DIMENSION
     AND DELPHI_TRANS.OC_CD=OBJ_CD_DIMENSION.OBJ_CD
     -- JOIN WITH GLA_DIMENSION
     AND DELPHI_TRANS.GLA=GLA_DIMENSION.GLA_CD
     -- JOIN WITH EFF_DATE_DIMENSION
     AND DELPHI_TRANS.EFF_DT=EFF_DATE_DIMENSION.EFFECTIVE_DATE
     -- JOIN WITH PROC_DATE_DIMENSION
     AND DELPHI_TRANS.PROC_DT=PROC_DATE_DIMENSION.PROCESS_DATE
     -- JOIN WITH PROJECT_TASK_DIMENSION
     AND (DELPHI_TRANS.PROJ_NBR=PROJECT_TASK_DIMENSION.PROJECT_NO
     AND DELPHI_TRANS.TASK_NBR=PROJECT_TASK_DIMENSION.TASK_NO)
     -- JOIN WITH BUDGET_YR_DIMENSION
     AND DELPHI_TRANS.BUD_YR=BUDGET_YR_DIMENSION.BUDGET_YEAR
     -- JOIN WITH TRANS_DESC_DIMENSION
     AND DELPHI_TRANS.DESCR=TRANS_DESC_DIMENSION.DESCRIPTION
     -- JOIN WITH SUPPLIER_DIMENSION
     AND DELPHI_TRANS.VENDOR_NAME=SUPPLIER_DIMENSION.SUPPLIER_NAME
     -- JOIN WITH DELPHI_PO_DIMENSION
     AND DELPHI_TRANS.PO_NO=DELPHI_PO_DIMENSION.PO_NO
     -- JOIN WITH DELPHI_INV_DIMENSION
     AND DELPHI_TRANS.INV_NO=DELPHI_INV_DIMENSION.INVOICE_NO
     GROUP BY BPAC_KEY, ORG_KEY, FUND_KEY, OBJ_CD_KEY, GLA_KEY, EFF_DATE_KEY, PROC_DATE_KEY,
     PROJECT_TASK_KEY, BUDGET_YR_KEY,TRANS_DESC_KEY, SUPPLIER_KEY, DELPHI_INV_KEY, DELPHI_PO_KEY);
-- COUNT AFFECTED RECORDS
INSERTCOUNT:=0+SQL%ROWCOUNT;
-- RE-ENABLE KEY CONSTRAINT
DB_MISC.PRO_EXE_DDL('ALTER TABLE DELPHI_TRANS_FACT ENABLE VALIDATE CONSTRAINT PK_DELPH_TRANS_FACT');
-- STORE RESULTS OF OPERATION
IF INSERTCOUNT>0 THEN
DB_MISC.LOGFAILURE_EX('none', 'none', INSERTCOUNT||' new records loaded successfully.', TARGETTABLE, 'DM_LD_DELPHI_TRANS_FACT', FALSE);
END IF;
--- COMPARE BALANCE TOTAL FROM DELPHI_TRANS TABLE AND DELPHI_TRANS_FACT TABLE
SELECT SUM(BAL) INTO V_DELPHI_TRANS_TOTAL
FROM DELPHI_TRANS ;
SELECT SUM(BALANCE) INTO V_DELPHI_TRANS_FACT_TOTAL
FROM DELPHI_TRANS_FACT ;
VALIDATE_LOAD(V_DELPHI_TRANS_TOTAL,V_DELPHI_TRANS_FACT_TOTAL);
-- EXCEPTION HANDLING ROUTINES * * * * * * * * * * * * * * * * * * * * * *
EXCEPTION
    WHEN OTHERS THEN
      ROLLBACK;
      IF SQLCODE!=NBRIGNOREERR THEN
        ERRDESCRIPTION:=SQLERRM;
        -- CALL ROUTINE TO PROCESS ERROR
        DB_MISC.LOGFAILURE_EX('none', 'none', ERRDESCRIPTION, TARGETTABLE, 'DM_LD_DELPHI_TRANS_FACT', TRUE);
        COMMIT;
      END IF;
-- END EXCEPTION HANDLING ROUTINES * * * * * * * * * * * * * * * * * * * * * *
END

DML ERROR LOGGING - how to log 1 constraint violation on record

Hi there
We are using DML error logging to log records which violate constraints into an error table.
The problem is when a record violates > 1 constraint it logs the record but details only 1 constraint violation - is there a way to get it to record all constraint violations on an individual record.
Many Thanks

In the Netherlands several years ago a framework called CDM RuleFrame was introduced that did just this. Their main thought was that it is desirable to collect all error messages from one transaction and display them all at the end of the transaction.
[url http://www.dulcian.com/papers/ODTUG/2001/BR%20Symposium%202001/Boyd_BR.htm]Here is an article that explains the concept.
In short: it involves coding every single business rule as a database trigger using transaction management of CDM RuleFrame.
I would not recommend it however, because I think [url http://rwijk.blogspot.com/2007/09/database-triggers-are-evil.html]database triggers are evil. However, it may appeal to first time users of an application.
Hope this helps.
Regards,
Rob.
Message was edited by:
Rob van Wijk
But if cannot be "turned on" by some switch: you have to design your system this way. So the short answer to your question is: no, it is not possible.

ADF-BC:Customize Error Messages for Database Constraint Violations

Hai all
I have an apploication using JDEV 10.1.3.3 and ADF BC.
In my applcation I'm overriding the default error messages on violation of constraints by using a custom message bundle .
I did all the things specified in Oracle® ADF Developer's Guide
Chapter 25.8 Customizing Business Components Error Messages .
IT is working fine
My problem is along with the userdefined custom messge in the bundle
another default message is showing which is nothing meaningful to the
end user.
For Ex: for an Uniqiue constraint the following error message comes
Error
1 .The Usercode should be unique!!!
2 .ORA-00001: unique constraint (MYDB.USERCODEUNIQUE) violated
ORA-06512: at line 1
The first line is defined by me.the second one is added automatically.
I want to prevent showing the error no 2 for all DB constraint violations
Is there any method to do it.I think I'm missing someting
Please help me.This is very annoying to the end user.
Thanks
Ans

Hi,
guess you know about this
http://download-uk.oracle.com/docs/html/B25947_01/bcadvgen008.htm#sthref2393
So have a look here
http://download-uk.oracle.com/docs/html/B25947_01/web_val008.htm
The code for this is from SRDemo and allows you to suppress messages from JSF display
Frank

OWB Update/Insert throwing unique constraint ..

Hello Al,
I am currently facing issue when it is supposed to update/Insert the records in OWB10gR2.
Also there are no duplicates in the source data while doing this.
Any help is appreceated.
Thanks,
Suresh
Edited by: user8745316 on Jul 27, 2010 12:58 AM

Hi Nawneet,
Thanks for the reply.
My issue is something like this , there were duplicates from the source and we deleted them but still it gives this error @ Unique constraint voilated errror.
I also can understand that as we have same matching records by key columns from source and target which should ideally be doing the update and if non matching should be inserting which is not happening now.
can you please suggest me the issue.
Thanks for your help.
Suresh

Handle Oracle Error from Oracle Forms

Actually I have a form with all types of validation and Id will be auto-generated by forms.
Now if any oracle error occures after pre-insert, auto-generated number will generate but record is not saving.
I want to handle this oracle error in my form and nullify the auto-generated ID forcefully.
Edited by: Sudipto Nag on Sep 16, 2008 12:07 PM

The way we handle database error generally is this:
You should in any case have a NOT NULL constraint on the database column. In the ON-ERROR trigger, we then check for the dbms_error_code value to see, what error message the database returned, after checking for Forms returning the general trigger exception 40735. For example, to trap a NOT NULL constraint voilation, you would do something like this.
if error_code= 40735 then --Forms error code = "Trigger raised unhandled exception".
if dbms_error_code in (-1400, -1407) then --mandatory not null column missing
    --do something, like alerting the user
elsif dbms_error_code in (<other DBMS error codes goes here>) then
    --do something else
end if;
end if;I believe this is what you are looking for. Hope it helps.
Regards,
Jacob

Primary Key Constraint

dear members,
I have a tables named orders and part. Both of them contain common column named partnum. The column partnum in the table orders contains duplicates. I tried to add a primary key constraint to that column partnum but sql*plus gave me an error unique constraint voilation.
The reason for the error was because of duplicates in the column partnum but if i want to assign a column as a primary key and suppose it contains duplicates then how can i do that ? I cannot alter my table orders data, in this case how should i proceed further!!!

You cannot use a single column with duplicates or null values as a primary key. It's that simple.
If a given single column has duplicates values its not a possible candidate for a primary key. It has to be an unique value.
I'm not fully sure here but kinda feels like your table "orders" has information about all orders (purchase, sell, whatever) related with "parts". So, this way if its possible that orders has duplicates because you have several orders on the same "part". I think "part" has a primary key on "partnum". If there's a need for a pk in "orders" maybe you have an additional column, let's call it "ordernum".

Error while upgrading Oracle SOA 10.1.3.3 to 10.1.3.5

Hi,
Iam trying to upgrade Oracle SOA ver.10.1.3.3 to 10.1.3.5 on a windows server.The following steps were followed.
1. SOA was stopped. Back up of the SOA folder was taken.
2. SOA uses the default Olite database. Connected to the BPEL schema and run the upgrade_10133_10135_olite.sql script.
It errored out in the upgrade process of 10.1.3.3 to 10.1.3.4.
The esb schema upgrade script executed without error. Have any one faced similar issue? or aware of the reason? Please help me out. Thanks in advance.
The following is the log:
SQL> @E:\Downloads\Installables\p8626084_101350_WINNT\Disk1\install\soa_schema_upgrade\bpel\scripts\upgrade_10133_10135_olite.sql
SQL> SET FEEDBACK 1
SQL> SET NUMWIDTH 10
SQL> SET LINESIZE 80
SQL> SET TRIMSPOOL ON
SQL> SET TAB OFF
SQL> SET PAGESIZE 100
SQL> @@upgrade_10133_10134_olite.sql
SQL> Rem
SQL> Rem $Header: bpel/everest/src/modules/server/database/scripts/upgrade_10133_10134_olite.sql /st_pcbpel_10.1.3.1/11 2009/06/03 00:37:24 nverma Exp $
SQL> Rem
SQL> Rem upgrade_10133_10134_olite.sql
SQL> Rem
SQL> Rem Copyright (c) 2008, 2009, Oracle and/or its affiliates.
SQL> Rem All rights reserved.
SQL> Rem
SQL> Rem NAME
SQL> Rem upgrade_10133_10134_olite.sql - <one-line expansion of the name>
SQL> Rem
SQL> Rem DESCRIPTION
SQL> Rem This script can be used to upgrade orabpel schema on olite database from 10.1.3.3.0 to 10.1.3.4.0
SQL> Rem
SQL> Rem NOTES
SQL> Rem This script can be used to upgrade orabpel schema on olite database from 10.1.3.3.0 to 10.1.3.4.0
SQL> Rem
SQL> Rem MODIFIED (MM/DD/YY)
SQL> Rem nverma 04/27/09 - Backport nverma_bug-8463393 from
SQL> Rem nverma 04/14/09 - Backport nverma_bug-7171739 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem ramisra 06/05/08 -
SQL> Rem ralmuell 03/28/08 - Sensor schema change for 6819678
SQL> Rem ramisra 03/17/08 - Backport ramisra_bug-6845586 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem atam 03/06/08 - update version
SQL> Rem nverma 01/29/08 - Upgrade script (10.1.3.3.0 to 10.1.3.4.0) for orabpel schema on olite
SQL> Rem database.
SQL> Rem nverma 01/29/08 - Created
SQL> Rem
SQL> SET ECHO ON
SQL> SET FEEDBACK 1
SQL> SET NUMWIDTH 10
SQL> SET LINESIZE 80
SQL> SET TRIMSPOOL ON
SQL> SET TAB OFF
SQL> SET PAGESIZE 100
SQL> ALTER TABLE DLV_MESSAGE MODIFY (CONV_ID VARCHAR2(256))
Table altered
SQL> ALTER TABLE DLV_SUBSCRIPTION DROP CONSTRAINT DS_PK
Table altered
SQL> ALTER TABLE DLV_SUBSCRIPTION MODIFY (CONV_ID VARCHAR2(256))
Table altered
SQL> ALTER TABLE DLV_SUBSCRIPTION ADD CONSTRAINT DS_PK PRIMARY KEY(CONV_ID, SUBSCRIBER_ID)
Table altered
SQL> ALTER TABLE INVOKE_MESSAGE MODIFY (CONV_ID VARCHAR2(256))
Internal Error:thinExecute: Result Communication Failed
SQL> ALTER TABLE INVOKE_MESSAGE MODIFY (MASTER_CONV_ID VARCHAR2(256))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE NATIVE_CORRELATION MODIFY (CONVERSATION_ID VARCHAR2(1000))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE NATIVE_CORRELATION MODIFY (NATIVE_CORRELATION_ID VARCHAR2(1000))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE CUBE_INSTANCE MODIFY (CONVERSATION_ID VARCHAR2(256))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE TASK MODIFY (CONVERSATION_ID VARCHAR2(256))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE WORK_ITEM MODIFY (CUSTOM_ID VARCHAR2(256))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE DLV_SUBSCRIPTION DROP CONSTRAINT DS_PK
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE DLV_SUBSCRIPTION MODIFY (SUBSCRIBER_ID VARCHAR2(256))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE DLV_SUBSCRIPTION ADD CONSTRAINT DS_PK PRIMARY KEY(CONV_ID, SUBSCRIBER_ID)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE DLV_MESSAGE MODIFY (RES_SUBSCRIBER VARCHAR2(256))
Internal Error:AllocStatement: Request Communication Failed
SQL> CREATE INDEX DDMR_DOCKEY ON DOCUMENT_DLV_MSG_REF(DOCKEY)
Internal Error:AllocStatement: Request Communication Failed
SQL> CREATE INDEX CI_CUSTOM4 ON CUBE_INSTANCE (MODIFY_DATE)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE WFUserTaskViewGrant ADD ( granteeType VARCHAR2(20), applicationContext VARCHAR2(200) )
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table cube_instance add ( at_count_id integer, at_event_id integer, at_detail_id integer )
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values add error_message_temp clob
Internal Error:AllocStatement: Request Communication Failed
SQL> update activity_sensor_values set error_message_temp=error_message
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values drop column error_message
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values add error_message clob
Internal Error:AllocStatement: Request Communication Failed
SQL> update activity_sensor_values set error_message=error_message_temp
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values drop column error_message_temp
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values drop column error_message_temp
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table fault_sensor_values drop primary key
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table variable_sensor_values drop primary key
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values drop primary key cascade
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values add constraint activity_sensor_pk primary key(id, process_instance_id)
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table variable_sensor_values add constraint variable_sensor_pk primary key(id, process_instance_id)
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table variable_sensor_values add constraint variable_sensor_fk1 foreign key(activity_sensor_id, process_instance_id) references activity_sensor_values(id, process_instance_id)
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table fault_sensor_values add constraint fault_sensor_pk primary key(id, process_instance_id)
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table activity_sensor_values modify constraint activity_sensor_pk enable
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table variable_sensor_values modify constraint variable_sensor_pk enable
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table variable_sensor_values modify constraint variable_sensor_fk1 enable
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table fault_sensor_values modify constraint fault_sensor_pk enable
Internal Error:AllocStatement: Request Communication Failed
SQL> drop index activity_sensor_values_indx
Internal Error:AllocStatement: Request Communication Failed
SQL> create index activity_sensor_values_indx on activity_sensor_values(process_instance_id, sensor_name, action_name)
Internal Error:AllocStatement: Request Communication Failed
SQL> update version set guid = '10.1.3.4.0'
Internal Error:AllocStatement: Request Communication Failed
SQL> update version_server set guid = '10.1.3.4.0'
Internal Error:AllocStatement: Request Communication Failed
SQL> COMMIT
Internal Error:AllocStatement: Request Communication Failed
SQL> @@upgrade_10134_10135_olite.sql
SQL> Rem Copyright (c) 2008, 2009, Oracle and/or its affiliates.
SQL> Rem All rights reserved.
SQL> Rem
SQL> Rem NAME
SQL> Rem
SQL> Rem DESCRIPTION
SQL> Rem
SQL> Rem NOTES
SQL> Rem <other useful comments, qualifications, etc.>
SQL> Rem
SQL> Rem MODIFIED (MM/DD/YY)
SQL> Rem vnanjund 07/09/09 - Backport vnanjund_bug-8655721 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem mchinnan 07/07/09 - Backport mchinnan_bug-8636836 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem vnanjund 07/06/09 - olite fix
SQL> Rem mchmiele 07/02/09 - Backport mchmiele_bug-8613538 from
SQL> Rem mchmiele 07/01/09 - Backport mchmiele_bug-8613538 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem mchmiele 06/30/09 - Migrating processes with correlation sets
SQL> Rem mchmiele 06/30/09 - Backport mchmiele_bug-8613538 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem mchmiele 06/29/09 - Olite resource tables
SQL> Rem mchmiele 06/29/09 - Backport mchmiele_bug-8613538 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem ramisra 05/11/09 - Backport ramisra_bug-8498498 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem nverma 04/27/09 - Backport nverma_bug-8463393 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem mnanal 03/09/09 - Backport mnanal_bug-7286083 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem mnanal 02/10/09 - RFI bug 7022475
SQL> Rem ramisra 01/02/09 - Backport ramisra_bug-7577303 from
SQL> Rem st_pcbpel_10.1.3.1
SQL> Rem ramisra 09/17/08 - Created
SQL> Rem
SQL> SET ECHO ON
SQL> SET FEEDBACK 1
SQL> SET NUMWIDTH 10
SQL> SET LINESIZE 80
SQL> SET TRIMSPOOL ON
SQL> SET TAB OFF
SQL> SET PAGESIZE 100
SQL> -- Update version
SQL> --
SQL> update version set guid = '10.1.3.5.0' where dbtype = 'olite'
Internal Error:AllocStatement: Request Communication Failed
SQL> commit
Internal Error:AllocStatement: Request Communication Failed
SQL> CREATE table temp_attachment ( key varchar2( 50 ), bin blob )
Internal Error:AllocStatement: Request Communication Failed
SQL> INSERT into temp_attachment (key,bin) SELECT key, bin FROM attachment
Internal Error:AllocStatement: Request Communication Failed
SQL> DROP table attachment
Internal Error:AllocStatement: Request Communication Failed
SQL> CREATE table attachment ( key varchar2( 50 ), content_type varchar2( 50 ), bin blob, constraint att_pk primary key( key ) )
Internal Error:AllocStatement: Request Communication Failed
SQL> INSERT into attachment (key,bin) SELECT key, bin FROM temp_attachment
Internal Error:AllocStatement: Request Communication Failed
SQL> DROP table temp_attachment
Internal Error:AllocStatement: Request Communication Failed
SQL> DELETE FROM WFRoutingSlip rs WHERE NOT EXISTS (SELECT 1 FROM WFTask t WHERE t.taskid = rs.taskid)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE WFRoutingSlip ADD CONSTRAINT RoutingSlipTaskConstraint FOREIGN KEY (taskId) REFERENCES WFTask (taskId) ON DELETE CASCADE
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE process_descriptor ADD (last_change_time NUMBER(38))
Internal Error:AllocStatement: Request Communication Failed
SQL> UPDATE process_descriptor SET last_change_time=(SELECT (SYSDATE - TO_DATE('01-01-1970','DD-MM-YYYY')) * (24*60*60*1000) FROM DUAL)
Internal Error:AllocStatement: Request Communication Failed
SQL> create index WFTaskTaskGroupId_I on WFTask(taskGroupId)
Internal Error:AllocStatement: Request Communication Failed
SQL> create index WFTaskWorkflowPattern_I on WFTask(workflowPattern)
Internal Error:AllocStatement: Request Communication Failed
SQL> DELETE FROM domain_properties WHERE prop_id IN ( 'dspMinThreads' , 'dspMaxThreads', 'dspInvokeAllocFactor' )
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE dlv_subscription ADD ( partner_link VARCHAR2(256) )
Internal Error:AllocStatement: Request Communication Failed
SQL> UPDATE VERSION SET guid = '10.1.3.5.0'
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table WFTaskTimer add key varchar(100)
Internal Error:AllocStatement: Request Communication Failed
SQL> alter table WFAttachment modify (encoding varchar(100))
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE dlv_subscription DROP CONSTRAINT ds_pk
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE dlv_subscription ADD CONSTRAINT ds_pk PRIMARY KEY (subscriber_id)
Internal Error:AllocStatement: Request Communication Failed
SQL> DROP INDEX ds_conversation
Internal Error:AllocStatement: Request Communication Failed
SQL> CREATE INDEX ds_conversation ON dlv_subscription( conv_id )
Internal Error:AllocStatement: Request Communication Failed
SQL> DROP INDEX ds_operation
Internal Error:AllocStatement: Request Communication Failed
SQL> CREATE INDEX ds_operation ON dlv_subscription( process_id, operation_name )
Internal Error:AllocStatement: Request Communication Failed
SQL> drop table cx_resource
Internal Error:AllocStatement: Request Communication Failed
SQL> create table cx_resource ( id integer, pid integer, name varchar(64), kind char(1), modify_date timestamp default sysdate, constraint cx_resource_pk primary key( id ), constraint cx_resource_no_dups_pk unique (pid,name) )
Internal Error:AllocStatement: Request Communication Failed
SQL> create index cx_resource_name_idx on cx_resource (name)
Internal Error:AllocStatement: Request Communication Failed
SQL> create index cx_resource_pid_idx on cx_resource (pid)
Internal Error:AllocStatement: Request Communication Failed
SQL> drop table cx_content
Internal Error:AllocStatement: Request Communication Failed
SQL> create table cx_content ( id integer, /* id of the resource content, pointing to Resource.id */ content blob, /* the content as a blob */ constraint cx_content_pk primary key( id ) )
Internal Error:AllocStatement: Request Communication Failed
SQL> -- Add debugger tables
SQL> --
SQL> @@debugger_olite.ddl
E:\Downloads\Installables\p8626084_101350_WINNT\Disk1\install\soa_schema_upgrade\bpel\scripts\debugger_olite.ddl (The system cannot find the file specified)
SQL> ALTER TABLE work_item ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE dlv_subscription ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE ci_indexes ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE wi_exception ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE wi_fault ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE document_ci_ref ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE audit_trail ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE audit_details ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE cube_scope ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE attachment ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE attachment_ref ADD (ci_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE document_dlv_msg_ref ADD (dlv_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> ALTER TABLE xml_document ADD (doc_partition_date TIMESTAMP)
Internal Error:AllocStatement: Request Communication Failed
SQL> create or replace view admin_list_cx as select ci.cikey, domain_ref as ci_domain_ref, process_id, revision_tag, creation_date ci_creation_date, creator ci_creator, modify_date ci_modify_date, modifier ci_modifier, state ci_state, priority ci_priority, title, status, stage, conversation_id, metadata, root_id, parent_id, test_run_id, index_1, index_2, index_3, index_4, index_5, index_6, ci.test_run_id from cube_instance ci, ci_indexes cx where ci.cikey = cx.cikey (+)
Internal Error:AllocStatement: Request Communication Failed
SQL> COMMIT
Internal Error:AllocStatement: Request Communication Failed

Hi,
IF ORACLE DATABASE HAS ALREADY HAS ORABPEL AND ORAESB USERS, I don't know password.:
My remarks. If you upgrade a SOA suite to a higher version, you always need to known the passwords of the Oracle dehydration store (orabpel/orawsm/oraesb). If you do not know that, call your DBA. Otherwise try: the same password as the user name or try 'welcome1'. You could also force to change the password via the system user; alter user <user> identified by <password>;
IS IT A GOOD IDEA TO UPGRADE Oracle SOA 10.1.3.1.0 to Oracle SOA 10.1.3.4.0?
Yes! 10.1.3.4 is the succeeder of 10.1.3.3, in the beginning of next year 10.1.3.5 (with WLS 10.3) will come out. Note if you use 10.1.3.4 download also the latest patchset from metalink.
Marc
http://oroasoa.blogspot.com

Error while saving Employee Billrates through OAF page

Dear All,
I am facing the below mentioned error while saving Employee Bill rates for any project through OAF interface. I have tried saving the same through FORMS interface and its getting saved. The Unique constraint on the error log is on the table PA_EMP_BILL_RATE_OVERRIDES and the column is EMP_BILL_RATE_OVERRIDE_ID and we have a sequence for generating Unique id. The sequence used is PA_EMP_BILL_RATE_OVERRIDES_S.
Please note that the error only fires on insertion of new record in the table PA_EMP_BILL_RATE_OVERRIDES, on updation error doesn't fire.
The Constraint definition on the table is :
create unique index PA.PA_EMP_BILL_RATE_OVERRIDES_U2 on PA.PA_EMP_BILL_RATE_OVERRIDES (EMP_BILL_RATE_OVERRIDE_ID)
ERROR : java.sql.SQLException: ORA-00001: unique constraint (PA.PA_EMP_BILL_RATE_OVERRIDES_U2) violated

Dear All,
I am facing the below mentioned error while saving Employee Bill rates for any project through OAF interface. I have tried saving the same through FORMS interface and its getting saved. The Unique constraint on the error log is on the table PA_EMP_BILL_RATE_OVERRIDES and the column is EMP_BILL_RATE_OVERRIDE_ID and we have a sequence for generating Unique id. The sequence used is PA_EMP_BILL_RATE_OVERRIDES_S.
Please note that the error only fires on insertion of new record in the table PA_EMP_BILL_RATE_OVERRIDES, on updation error doesn't fire.
The Constraint definition on the table is :
create unique index PA.PA_EMP_BILL_RATE_OVERRIDES_U2 on PA.PA_EMP_BILL_RATE_OVERRIDES (EMP_BILL_RATE_OVERRIDE_ID)
ERROR : java.sql.SQLException: ORA-00001: unique constraint (PA.PA_EMP_BILL_RATE_OVERRIDES_U2) violated

EXPDP error - ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOA

Greetings All,
Oracle 11g (11.2.0.0) on Windows 2008 R2
I am getting the error below during a schema export of just 1 particular schema. Other schema expdp’s don’t encounter this problem.
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/REF_CONSTRAINT
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA [REF_CONSTRAINT:"CM_MASTER"."PPY_PEN_FK"]
ORA-04063: package body "XDB.DBMS_XDBUTIL_INT" has errors
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 8165
----- PL/SQL Call Stack -----
object      line object
handle    number name
000000047B38A000     18990 package body SYS.KUPW$WORKER
000000047B38A000      8192 package body SYS.KUPW$WORKER
000000047B38A000      2823 package body SYS.KUPW$WORKER
000000047B38A000      8847 package body SYS.KUPW$WORKER
000000047B38A000      1649 package body SYS.KUPW$WORKER
000000047A576CD0         2 anonymous block
Job "CM_MASTER"."EXP_CM_MASTER" stopped due to fatal error at 17:11:30I have deleted the identified constraint, but then errors out again on another constraint.
I have found a tentative resolution for the ORA-39126 error (delete database stats, then gather database stats) but have not done so yet.
I have tried deleting the statistics for just the schema (cm_master), and then re-gathered stats for the same schema. Still get the error.
I am concerned about the ORA-04063: package body “XDB.DBMS_XDBUTIL_INT” has errors.
I have unlocked and set new password for the XDB user, but am not able to logon as XDB to re-compile the package body in question.
We had some maintenance applied over the weekend that “revoked execute from public” on the following packages:
dbms_datapump
dbms_crypto
dbms_crypto_toolkit
dbms_java_test
dbms_random
dbms_sql
utl_file
utl_http
utl_mail
utl_smtp
utl_tcpThe user performing the export with the problem (cm_master) was then granted execute back on the following packages:
dbms_datapump
dbms_crypto
dbms_random
dbms_sql
utl_file
utl_http
utl_mail
(not: dbms_crypto_toolkit, dbms_java_test, utl_smtp, utl_tcp,)Other schemas were granted execute on the following packages and are NOT having expdp problems:
dbms_datapump
dbms_sql
utl_file
utl_http
utl_mail
(not: dbms_crypto, dbms_crypto_toolkit, dbms_random, utl_smtp, utl_tcp )I don't think the public revokes are causing this error because the "Other schemas" do not have this error and were not specifically granted back all of the public revokes that cm_master received back.
I appreciate any suggestions.
Thanks for your time,
Bob
Edited by: Snyds on Jun 5, 2012 10:03 AM

rjamya,
I checked dba_registry, all 18 rows returned are VALID.
I attempted to compile the package body identified in the error messages:
ORA-04063: package body "XDB.DBMS_XDBUTIL_INT" has errorswith
alter package xdb.dbms_xdbutil_int compile body;I got thje following results
Error starting at line 60 in command:
alter package xdb.dbms_xdbutil_int compile body
Error report:
SQL Command: package XDB.DBMS_XDBUTIL_INT
Failed: ORA-24344: success with compilation error
24344. 00000 - "success with compilation error"
*Cause:    A sql/plsql compilation error occurred.
*Action:   Return OCI_SUCCESS_WITH_INFO along with the error code
package XDB.DBMS_XDBUTIL_INT altered.Any other suggestions regarding how to resolve errors in the XDB.DBMS_ packages?
I also tried granting CM_MASTER execute on the packages that I revoked execute to PUBLIC on, with no effect.
I tried “exclude=REF_CONSTRAINT” on the export, the problem seemed to move to the next section:
Estimate in progress using BLOCKS method...
Processing object type SCHEMA_EXPORT/TABLE/TABLE_DATA
Total estimation using BLOCKS method: 96.31 MB
Processing object type SCHEMA_EXPORT/USER
Processing object type SCHEMA_EXPORT/SYSTEM_GRANT
Processing object type SCHEMA_EXPORT/ROLE_GRANT
Processing object type SCHEMA_EXPORT/DEFAULT_ROLE
Processing object type SCHEMA_EXPORT/PRE_SCHEMA/PROCACT_SCHEMA
Processing object type SCHEMA_EXPORT/DB_LINK
Processing object type SCHEMA_EXPORT/SEQUENCE/SEQUENCE
Processing object type SCHEMA_EXPORT/TABLE/TABLE
Processing object type SCHEMA_EXPORT/TABLE/GRANT/OWNER_GRANT/OBJECT_GRANT
Processing object type SCHEMA_EXPORT/TABLE/INDEX/INDEX
Processing object type SCHEMA_EXPORT/TABLE/CONSTRAINT/CONSTRAINT
Processing object type SCHEMA_EXPORT/TABLE/COMMENT
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/FUNCTION
Processing object type SCHEMA_EXPORT/PACKAGE/COMPILE_PACKAGE/PACKAGE_SPEC/ALTER_PACKAGE_SPEC
Processing object type SCHEMA_EXPORT/FUNCTION/ALTER_FUNCTION
Processing object type SCHEMA_EXPORT/VIEW/VIEW
Processing object type SCHEMA_EXPORT/PACKAGE/PACKAGE_BODY
ORA-39126: Worker unexpected fatal error in KUPW$WORKER.UNLOAD_METADATA [PACKAGE_BODY:"CM_MASTER"."SR_MAINTENANCE"]
ORA-04063: package body "XDB.DBMS_XDBUTIL_INT" has errors
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95
ORA-06512: at "SYS.KUPW$WORKER", line 8165
----- PL/SQL Call Stack -----
object      line object
handle    number name
000000047B38A000     18990 package body SYS.KUPW$WORKER
000000047B38A000      8192 package body SYS.KUPW$WORKER
000000047B38A000      2823 package body SYS.KUPW$WORKER
000000047B38A000      8847 package body SYS.KUPW$WORKER
000000047B38A000      1649 package body SYS.KUPW$WORKER
000000047A576CD0         2 anonymous block
Job "CM_MASTER"."EXP_CM_MASTER" stopped due to fatal error at 19:36:23I tried the suggestion from my Google-ing, drop database statistics, then gather database statistics. No effect, same error.
I also tried granting CM_MASTER execute on the packages that I revoked execute to PUBLIC on, with no effect.
Again what seems odd is that I can export other schemas without errors.
Any other suggestions, please.
Thanks,
Bob
Edited by: Snyds on Jun 5, 2012 12:04 PM

DML Error Logging Tables?

How can I use DML Error Logging Tables with OWB10gR2 (in tab-definition and mappings)?
btw: what really is a shadow-table?

Hi,
What you can do to solve this is to add a Pre-mapping to your mapping which calls a procedure that alters the constraint on the target table in which you use the "EXCEPTIONS INTO <error_table> " clause.
like:
PROCEDURE "ENABLE_CONSTR_WITH_EXCEPTIONS"("P_TABLE" IN VARCHAR2, "P_CONSTRAINT" IN VARCHAR2) IS
v_table            varchar2(30) := p_table;
v_constraint          varchar2(30) := p_constraint;
v_command           varchar2(200);
e_CannotValidate      exception;
PRAGMA EXCEPTION_INIT(e_CannotValidate, -2437);
-- main body
BEGIN
/* Enable Constraint and write error into exception table */
BEGIN
    v_command := 'ALTER TABLE ' || v_table || ' ENABLE CONSTRAINT '|| v_constraint ||' EXCEPTIONS INTO exceptions';
    execute immediate (v_command);
    commit;
END;
    EXCEPTION
        WHEN e_CannotValidate THEN
           -- In my case when Unique Constraints are violated I will delete the duplicates.
           DELETE_DUPLICATES(v_table, v_constraint);
        WHEN OTHERS THEN
            NULL; -- enter any exception code here
END;
-- End of ENABLE_CONSTR_WITH_EXCEPTIONS;Greetz,
Ilona Tielke

Error Logging Clause & Alternatives

Users want data from an external source validated, and any nonconformities logged. I had hoped to do this via constraints and the error logging clause, and cooked up an example to try things out:
SQL> alter table emp add constraint emp_ck_sal check(sal between 1 and 5000) enable;
Table altered.
SQL> select constraint_name, constraint_type from user_constraints where table_name = 'EMP';
CONSTRAINT_NAME                C
EMP_CK_SAL                     C
PK_EMP                         P
FK_DEPTNO                      R
SQL> exec dbms_errlog.create_error_log('emp', 'bad_emp');
PL/SQL procedure successfully completed.
SQL> insert into emp (empno, ename, job, mgr, hiredate, sal, deptno)
2 select 8001, 'AZIZ', 'CLERK', 7782, sysdate, 1000, 10 from dual
3 union
4 select 8002, 'NG', 'CLERK', 7782, sysdate, 0, 10 from dual
5 union
6 select 8003, 'ASFAW', 'CLERK', 8000, sysdate, 8000, 50 from dual
7 log errors into bad_emp
8 reject limit unlimited;
1 row created.
SQL> select * from emp;
EMPNO ENAME      JOB              MGR HIREDATE      SAL       COMM DEPTNO
   7369 SMITH      CLERK           7902 17-DEC-80     800                 20
   7499 ALLEN      SALESMAN        7698 20-FEB-81    1600        300      30
   7521 WARD       SALESMAN        7698 22-FEB-81    1250        500      30
   7566 JONES      MANAGER         7839 02-APR-81    2975                 20
   7654 MARTIN     SALESMAN        7698 28-SEP-81    1250       1400      30
   7698 BLAKE      MANAGER         7839 01-MAY-81    2850                 30
   7782 CLARK      MANAGER         7839 09-JUN-81    2450                 10
   7788 SCOTT      ANALYST         7566 19-APR-87    3000                 20
   7839 KING       PRESIDENT            17-NOV-81    5000                 10
   7844 TURNER     SALESMAN        7698 08-SEP-81    1500          0      30
   7876 ADAMS      CLERK           7788 23-MAY-87    1100                 20
   7900 JAMES      CLERK           7698 03-DEC-81     950                 30
   7902 FORD       ANALYST         7566 03-DEC-81    3000                 20
   7934 MILLER     CLERK           7782 23-JAN-82    1300                 10
   8000 MOORE      MANAGER         7839 22-MAY-06    3600                 40
   8001 AZIZ       CLERK           7782 31-AUG-06    1000                 10
16 rows selected.
SQL> select ora_err_number$, ora_err_mesg$, empno empnox, ename enamex, sal salx, deptno deptnox
from bad_emp;
ORA_ERR_NUMBER$ ORA_ERR_MESG$                EMPNOX ENAMEX     SALX   DEPTNOX
           2290 ORA-02290: check constraint 8002   NG         0      10
                (SCOTT.EMP_CK_SAL) violated
           2290 ORA-02290: check constraint 8003   ASFAW      8000   50
                (SCOTT.EMP_CK_SAL) violatedGreat. "Clean! Modern! Rapid!" as Mr Mori said. However, there's a problem. Employee 8003 ASFAW actually violates 2 constraints: the reported EMP_CK_SAL check constraint for having a salary out of range, and the FK_DEPTNO foreign key constraint because dept 50 doesn't exist - which isn't reported. The users want all the violations reported at once so that only one fix operation is required. I don't think I'm going to do that via the error logging clause? Anything I've missed?
So - any ideas on how to avoid the 3000 line package of row-by-row processing with 7 levels of nested IFs I keep finding predecessors and associates have employed to do this kind of thing?

Hello
I would say that unless you can convince your users that they are going to have to accept that for some rows, they are going to have to correct more than one error, in more than one run, you will end up re-inventing the wheel - infact you will be creating a caterpillar track, capable of navigating pretty much any terrain roughly as quick as an actual caterpillar.
Realistically though, what percentage of data is going to require users to re-import the same row twice? Is the quality of the source data very poor?
One potential solution would be to use views on the source data that identify rows violating any given constraint:
SQL> CREATE TABLE dt_test_dept (id number primary key)
2 /
Table created.
SQL>
SQL> insert into dt_test_dept values(1)
2 /
1 row created.
SQL>
SQL> CREATE TABLE dt_test_emp (id number primary key, deptid number, sal number)
2 /
Table created.
SQL>
SQL> alter table dt_test_emp add constraint emp_dept_fk foreign key (deptid) references dt_test_dept
2 /
Table altered.
SQL> alter table dt_test_emp add constraint emp_ck_sal check(sal between 1 and 5000) enable
2 /
Table altered.
SQL>
SQL> CREATE TABLE dt_test_emp_src(id number, deptid number, sal number)
2 /
Table created.
SQL> insert into dt_test_emp_src VALUES(2, 100,500)
2 /
1 row created.
SQL> insert into dt_test_emp_src VALUES(3, 1,5001)
2 /
1 row created.
SQL> insert into dt_test_emp_src VALUES(4, 100,5001)
2 /
1 row created.
SQL> insert into dt_test_emp_src VALUES(5, 1,5000)
2 /
1 row created.
SQL>
SQL> CREATE VIEW dt_test_emp_bad_fk
2 AS
3 SELECT
4     'No matching department' err_text,
5     id,
6     deptid,
7     sal
8 FROM
9     dt_test_emp_src
10 WHERE
11     NOT EXISTS(     SELECT
12                             NULL
13                     FROM
14                             dt_test_dept
15                     WHERE
16                             dt_test_dept.id = dt_test_emp_src.deptid
17             )
18 /
View created.
SQL> CREATE VIEW dt_test_emp_bad_sal
2 AS
3 SELECT
4     'Salary invalid' err_text,
5     id,
6     deptid,
7     sal
8 FROM
9     dt_test_emp_src
10 WHERE
11     sal NOT BETWEEN 1 AND 5000
12 /
View created.
SQL>
SQL> CREATE VIEW dt_test_emp_bad
2 AS
3 SELECT
4     *
5 FROM
6     dt_test_emp_bad_fk
7 UNION ALL
8 SELECT
9     *
10 FROM
11     dt_test_emp_bad_sal
12 /
View created.
SQL> select * from dt_test_emp_bad
2 /
ERR_TEXT                       ID     DEPTID        SAL
No matching department          2        100        500
No matching department          4        100       5001
Salary invalid                  3          1       5001
Salary invalid                  4        100       5001
SQL> select * from dt_test_emp_bad order by id, err_text
2 /
ERR_TEXT                       ID     DEPTID        SAL
No matching department          2        100        500
Salary invalid                  3          1       5001
No matching department          4        100       5001
Salary invalid                  4        100       5001That way you can pre-emptively idetify the rows that will fail and not even attempt to insert them. It does of course mean one view or select statement per constraint but that's the price I guess.
HTH
David
And it should mean much less code to maintain...
Message was edited by:
david_tyler

Constraint voilation-AD error

Similar Messages

Maybe you are looking for