Job Aborts with Unique Constraint Message

This forum contains ProfileStage posts and now focuses at newer versions Infosphere Information Analyzer.

Moderators: chulett, rschirm

Post Reply
dsusr
Premium Member
Premium Member
Posts: 104
Joined: Sat Sep 03, 2005 11:30 pm

Job Aborts with Unique Constraint Message

Post by dsusr »

Hi,

We are trying to do the profiling on the source files and are finding that jobs for few files are getting aborted. We tried to do the analysis for each column seperately for those files and found that only for some specific columns the jobs are getting aborted.

The Profile Stage Error files just contain the message

'Unable To Continue. contact Technical Support.'


Below is the log details present in 'ColumnAnalysis_YYYYMMDD_3.log.orch'



---------- 6/19 7:28:52 -- ELAPSED: 1.200 min wall, 50.550 sec cpu ----------
Completed running OSH script to sort/build distribution.

---------- 6/19 7:28:52 -- ELAPSED: 1.200 min wall, 50.570 sec cpu ----------
main::WriteDistributionRow: *** Request for Diagnostic Info at ColumnAnalysis.pl line 7885. ***
Name of Table : ColumnDistribution
Last Return Status: 0
---------- Array of Error Messages ----------
Hash2Sql::InsertPKey: Problem encountered during DBI/EXECUTE:
------- DBI Result Information -------
Return Code : <not defined>
SQL State : '23000'
Error Number: '-1'
-- Error text --
[DataDirect][ODBC Oracle Wire Protocol driver][Oracle]ORA-00001: unique constraint (PSDB.PK_COLUMNDISTRIBUTION) violated (SQL-23000)(DBD: st_execue/SQLExecute err=-1)

-------------- SQL Statement --------------
INSERT INTO COLUMNDISTRIBUTION (
DATEFORMATID,
DOMAINVALUE,
COUNTOFVALUES,
DATATYPE,
COLUMNANALYSISID
)
VALUES (?, ?, ?, ?, ? )

------------ Placeholder Values ------------
1. '0'
2. '23203120414D414E4E20434F555254'
3. '1'
4. 'Char'
5. '2261'

----------- Placeholder Datatypes -----------
Listed by #DEFINE values:
1. '-8'
2. '-9'
3. ''
4. '-9'
5. ''

--------------- Stack Trace:
Stack level: 1 (relative to lowest level)
Caller package: main
Caller filename: ColumnAnalysis.pl
Caller line #: 7886
Subroutine called: InternalLog::AddLogStackTrace

Stack level: 2 (relative to lowest level)
Caller package: main
Caller filename: ColumnAnalysis.pl
Caller line #: 1867
Subroutine called: main::WriteDistributionRow

Stack level: 3 (relative to lowest level)
Caller package: main
Caller filename: ColumnAnalysis.pl
Caller line #: 1591
Subroutine called: main::ProcessColumnDistribution

Stack level: 4 (relative to lowest level)
Caller package: main
Caller filename: ColumnAnalysis.pl
Caller line #: 3929
Subroutine called: main::AnalyzeOneColumn

Stack level: 5 (relative to lowest level)
Caller package: main
Caller filename: ColumnAnalysis.pl
Caller line #: 994
Subroutine called: main::ProcessWorkQueueOfColumnNames

Stack level: 6 (relative to lowest level)
Caller package: main
Caller filename: ColumnAnalysis.pl
Caller line #: 905
Subroutine called: main::ColumnAnalysisForOneTable

---------- 6/19 7:28:52 -- ELAPSED: 1.200 min wall, 50.570 sec cpu ----------
Transaction rollback succeeded for fatal error.

-------------------------------------------------------------------------------------


Can someone please suggest me some steps to rectify this problem.

Regards,
dsusr
pk7
Participant
Posts: 44
Joined: Fri Aug 03, 2007 8:35 am
Location: Kansas CIty

Post by pk7 »

dsusr,

I responded to your query on the IBM developworks site.

pk7
Post Reply