[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference utrop1::linkworks_v3

Title:	LinkWorks V3.0 Notes Conference
Notice:	LNX_APO = APO issues, LINKWORKS_V3 = V3.0 issues
Moderator:	tacklr.apd.dec.com::TACK_Lm::TACK_L

Created:	Tue Jun 28 1994
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	2269
Total number of notes:	8338

2168.0. "ORA-00001: unique constraint (OPS$OMDBA,EREIGBUCHIX) violated" by KERNEL::SIMPSONR (fred) Mon Mar 24 1997 16:31

UNIX V3.2G   LINKWORKS 3.07

I have a customer who is having problems with out-going mail. Basically it
happens when users are sending mail. The mail processes at no time go down and
if they retry sending the mail it can work fine. This is a list of the errors
and the effects so far:

Error on screen                                          Outgoing mail sent Y/N
ORA-00001: unique constraint (OPS$OMDBA,EREIGBUCHIX) violated        Y
ORA-00001: unique constraint (OPS$OMDBA,AUSGANGBUCHIX) violated      N
ORA-00001: unique constraint (OPS$OMDBA,OBJEKTIX) violated           N

The following errors were found in /usr/op/cell/users/ER-11-97, they occurred
when a user was opening mail:

SQL-Error
---------
ORA-00001: unique constraint (OPS$OMDBA,EREIGBUCHIX) violated

  in function:   OMxEreigBuchIns
dynamic function trace:
  ==>OMxUserListSelClose==>OMxTableNextId==>OMxTransactionInit
  ==>OMTransactInit==>InitTransactions==>OMTransactInit
  ==>OMxTransactionInit==>OMxEreigBuchIns==>OMxLogin==>DBConnected
  ==>OMxLogin==>OMxEreigBuchIns==>OMTableLock==>OMTransactFunction
  ==>OMTableLock==>OMxEreigBuchIns==>DB_write_datetime
  ==>OMxEreigBuchIns==>DB_write_datetime==>OMxEreigBuchIns
version:3.0.7
 built for OS: DEC OSF/1 V3.0
 built for RDBMS: ORACLE7 Server Release 7.1.3.2.1
 running on OS: OSF1 V3.2 62 alpha
time: Fri Mar 21 15:40:06 1997
user: omuser
=========================================================================
SQL-Error
---------
ORA-00001: unique constraint (OPS$OMDBA,EREIGBUCHIX) violated

  in function:   OMxEreigBuchIns
dynamic function trace:
  ==>OMxUserListSelClose==>OMxTableNextId==>OMxTransactionInit
  ==>OMTransactInit==>InitTransactions==>OMTransactInit
  ==>OMxTransactionInit==>OMxEreigBuchIns==>OMxLogin==>DBConnected
  ==>OMxLogin==>OMxEreigBuchIns==>OMTableLock==>OMTransactFunction
  ==>OMTableLock==>OMxEreigBuchIns==>DB_write_datetime
  ==>OMxEreigBuchIns==>DB_write_datetime==>OMxEreigBuchIns
version:3.0.7
 built for OS: DEC OSF/1 V3.0
 built for RDBMS: ORACLE7 Server Release 7.1.3.2.1
 running on OS: OSF1 V3.2 62 alpha
time: Fri Mar 21 15:40:06 1997
user: omuser
=========================================================================
SQL-Error
---------
ORA-00001: unique constraint (OPS$OMDBA,OBJEKTIX) violated

  in function:   OMxObjektIns
dynamic function trace:
  ==>OMxTransactionInit==>OMTransactInit==>InitTransactions
  ==>OMTransactInit==>OMxTransactionInit==>OMxObjektIns==>OMxLogin
  ==>DBConnected==>OMxLogin==>OMxObjektIns==>OMTableLock
  ==>OMTransactFunction==>OMTableLock==>OMxObjektIns
  ==>DB_write_datetime==>OMxObjektIns==>DB_write_datetime
  ==>OMxObjektIns==>DB_write_datetime==>OMxObjektIns
version:3.0.7
 built for OS: DEC OSF/1 V3.0
 built for RDBMS: ORACLE7 Server Release 7.1.3.2.1
 running on OS: OSF1 V3.2 62 alpha
time: Fri Mar 21 15:42:04 1997
user: omuser


Any ideas?
Regards,
Richard Simpson.

T.R Title User Personal
Name Date Lines

2168.1 Duplicate object id ? Rebuild index ? BACHUS::dbc624.bro.dec.com::POPPE Thu Mar 27 1997 14:06 26

T.R	Title	User	Personal Name	Date	Lines
2168.1	Duplicate object id ? Rebuild index ?	BACHUS::dbc624.bro.dec.com::POPPE		`Thu Mar 27 1997 14:06`	26
	Hi Richard, As far as I know, unique contraint on oracle means that in the concerned table, one of the fields should only contain unique values, and now has a duplicated value. Apparently in the indexes of the objekt table (2 objects with the same obj_id ?) This means trouble in the database. I was told the following: >when you stop and restart oracle, the rdbms could swith the unique >constraint, meaning it will allow you to have duplicates in that >field. Then you don't get these messages anymore, and your >application (LinkWorks in this case) should run again. But .... >it means that you can get more duplicates in the database without >knowing it. You have to run specific sql scripts to get that >duplicate out of the table, and set the field back to unique. Maybe it could be solved by just rebuilding the indexes ? I would try (after taking backups) to run instcell upgrade, it will rebuild the indexes. You could of course check the situation of the table by "select obj_id, name from objekt order by 1" to get an overview, but the list could be rather long. First count your objects ("select count (*) from objekt"). Regards, Marc

Hi Richard,

As far as I know, unique contraint on oracle means that in the
concerned table, one of the fields should only contain unique 
values, and now has a duplicated value.  Apparently in the indexes
of the objekt table (2 objects with the same obj_id ?)
This means trouble in the database.  
I was told the following:
>when you stop and restart oracle, the rdbms could swith the unique
>constraint, meaning it will allow you to have duplicates in that
>field.  Then you don't get these messages anymore, and your 
>application (LinkWorks in this case) should run again.  But ....
>it means that you can get more duplicates in the database without
>knowing it.  You have to run specific sql scripts to get that 
>duplicate out of the table, and set the field back to unique.

Maybe it could be solved by just rebuilding the indexes ?
I would try (after taking backups) to run instcell upgrade, it will
rebuild the indexes.  You could of course check the situation of the
table by "select obj_id, name from objekt order by 1" to get an 
overview, but the list could be rather long.  First count your objects
("select count (*) from objekt").

Regards,
Marc