Consultor Eletrônico



Kbase P165884: OEManagement Trending errors with an integrity constraint violation
Autor   Progress Software Corporation - Progress
Acesso   Público
Publicação   9/23/2010
Status: Verified

SYMPTOM(s):

An SQL Exception occurred during an insert into the trend database. SQLState: 23000

Trending becomes unavailable.

Numerous error messages in the admserv.log file.

* Alert! Alert Name: FathomTrendingUnavailable, Resource Name: coli550.Fathom, Severity: 3, Message: Fathom cannot reach the trend database at jdbc:datadirect:openedge://localhost:50140;databasename=fathom. Check the log file for more information. (9892)

Problem with trend data, see admserv.log on trend machine: (9640)

message: [DataDirect][OpenEdge JDBC Driver][OpenEdge] Integrity constraint violation:uniqueness constraint violation (7518)

Trending user disconnecting from trend database with uniqueness contraint violation error

Fathom is not trending Memory information.

FACT(s) (Environment):

Trend Database has been migrated from OpenEdge Management 10.2A/3.2A or earlier
All Supported Operating Systems
OpenEdge Management 3.2x

CAUSE:

Using a trend db from or created under 10.1C. The older trend databases had a uniqueness constraint on the sample_ID value for the db_actbuf table. 10.2B version of the trend database does not. This was done to accommodate the secondary/alternate buffer pool.
The Insert error in the admserv.log will be followed by a very long string of inserts. The duplicate entry will look something like:
INSERT INTO PUB.Db_ActBuf ( ActBuf_LogicReads,ActBuf_OSWrites,ActBuf_Flushed,ActBuf_Deferred,ActBuf_LogicWrites,ActBuf_OSReads,
Sample_ID) values (29502.0,32.0,0.0,33.0,51.0,124.0,550172 );
INSERT INTO PUB.Db_ActBuf ( ActBuf_LogicReads,ActBuf_OSWrites,ActBuf_Flushed,ActBuf_Deferred,ActBuf_LogicWrites,ActBuf_OSReads,
Sample_ID) values (29502.0,32.0,0.0,33.0,51.0,124.0,550172 );

FIX:

Archive your old trend database and start with a restore of the fathom.bak provided with 10.2B. This copy of the trend database does not have a uniqueness constraint on the sample_ID field.