oracle.panama.messaging.transport.impl.InternalTransportException

transport internal exception: java.sql.SQLException: ORA-02291: integrity constraint (WIRELESS.TRANS_MESSAGE_SID_FK) violated - parent key not found ORA-06512: at "WIRELESS.TRANSPORT", line 362 ORA-06512: at "WIRELESS.TRANSPORT", line 704 ORA-06512: at line 1at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137)

Samebug tips0

We couldn't find tips for this exception.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web3

  • via Unknown by 445084,
  • Stack trace

    • oracle.panama.messaging.transport.impl.InternalTransportException: transport internal exception: java.sql.SQLException: ORA-02291: integrity constraint (WIRELESS.TRANS_MESSAGE_SID_FK) violated - parent key not found ORA-06512: at "WIRELESS.TRANSPORT", line 362 ORA-06512: at "WIRELESS.TRANSPORT", line 704 ORA-06512: at line 1at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:137) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:304) at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:271) at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:625) at oracle.jdbc.driver.T4CCallableStatement.doOall8(T4CCallableStatement.java:180) at oracle.jdbc.driver.T4CCallableStatement.execute_for_rows(T4CCallableStatement.java:790) at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1109) at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2901) at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:2992) at oracle.jdbc.driver.OracleCallableStatement.execute(OracleCallableStatement.java:4124) at oracle.panama.messaging.transport.impl.DBStorage.enqueueSendingMessage(DBStorage.java:620) at oracle.panama.messaging.transport.impl.SendingBilling.send(SendingBilling.java:125)

    Write tip

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

    Users with the same issue

    We couldn't find other users who have seen this exception.