This is a bug in version 4.1.9 and it's fixed from version 4.3.0beta and beyond.

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

  • SSHR error on 12.1.1 vision linux RHEL 5
    via by Baal666bobo,
    via by 708463,
  • error during check printing
    via by afzal,
  • eBS Behaviour became slow
    via by cheesewizz,
  • MyBatis Error Calling Oracle Function
    via Stack Overflow by greyfox
  • Ghost index calling oracle function
    via Stack Overflow by Alvaro Gomez
  • Failed Data Load - SIL
    via by Edwin-ACE,
    • java.sql.SQLException: ORA-24067: exceeded maximum number of subscrib ers for queue APPLSYS.FND_CP_GSM_OPP_AQ ORA-06512: at "APPS.FND_CP_OPP_IPC", line 85 ORA-06512: at line 1at oracle.jdbc.driver.SQLStateMapping.newSQLException( at oracle.jdbc.driver.DatabaseError.newSQLException( at oracle.jdbc.driver.DatabaseError.throwSqlException( at oracle.jdbc.driver.T4CTTIoer.processError( at oracle.jdbc.driver.T4CTTIoer.processError( at oracle.jdbc.driver.T4C8Oall.receive( at oracle.jdbc.driver.T4CCallableStatement.doOall8( at oracle.jdbc.driver.T4CCallableStatement.executeForRows( at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout( at oracle.jdbc.driver.OraclePreparedStatement.executeInternal( at oracle.jdbc.driver.OraclePreparedStatement.execute( at oracle.jdbc.driver.OracleCallableStatement.execute( at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute( at oracle.apps.fnd.cp.opp.OPPAQMonitor.initAQ( at oracle.apps.fnd.cp.opp.OPPAQMonitor.init( at oracle.apps.fnd.cp.opp.OPPAQMonitor.initialize( at oracle.apps.fnd.cp.opp.OPPServiceThread.init( at

    Users with the same issue

    11 times, last one,
    2 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    Unknown visitor1 times, last one,
    15 more bugmates