"ORA-00001: unique constraint violated" after A-MQ failover

Solution Verified - Updated -

Issue

  • In an Oracle RAC environment, a warning stating that a unique constraint has been violated is seen in the log file after a failover:
java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (BrokerName.SYS_C0083242) violated
       at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:439)[60:ojdbc6:0]
       at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:395)[60:ojdbc6:0]
       at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:802)[60:ojdbc6:0]
       at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:436)[60:ojdbc6:0]
       at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:186)[60:ojdbc6:0]
       at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:521)[60:ojdbc6:0]
       at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:205)[60:ojdbc6:0]
       at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1008)[60:ojdbc6:0]
       at oracle.jdbc.driver.OraclePreparedStatement.executeForRowsWithTimeout(OraclePreparedStatement.java:9870)[60:ojdbc6:0]
       at oracle.jdbc.driver.OraclePreparedStatement.executeBatch(OraclePreparedStatement.java:9974)[60:ojdbc6:0]
       at oracle.jdbc.driver.OracleStatementWrapper.executeBatch(OracleStatementWrapper.java:213)[60:ojdbc6:0]
  • We have a JDBC master-slave configuration for our AMQ 6.1 message broker. We see that the master suddenly went down and has thrown the error relating to unique constraint.

Environment

  • Jboss A-MQ
    • 6.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.