This site is currently read-only as we are migrating to Oracle Forums for an improved community experience. You will not be able to initiate activity until January 30th, when you will be able to use this site as normal.

    Forum Stats

  • 3,890,116 Users
  • 2,269,775 Discussions
  • 7,916,823 Comments

Discussions

OIM, One-phase transaction Exception

vegaasen
vegaasen Member Posts: 96
edited Jun 17, 2015 1:30AM in Identity Manager

Hia,

Lately I've noticed that there is a few errors in the logs regarding some JTA stuff. I'm not quite sure what caused these issues, however now they are there :-)

Caused by: org.springframework.transaction.TransactionSystemException: JTA failure on commit; nested exception is javax.transaction.SystemException: One-phase transaction BEA1-0A55CE70E54EFEEF22C1-6F696D4F7065726174696F6E7344425F69616D31 for resource oimOperationsDB_iam1 is in an unknown state.

        at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1044)

        at org.springframework.transaction.support.AbstractPlatformTransactionManager.processCommit(AbstractPlatformTransactionManager.java:732)

        at org.springframework.transaction.support.AbstractPlatformTransactionManager.commit(AbstractPlatformTransactionManager.java:701)

        at org.springframework.transaction.support.TransactionTemplate.execute(TransactionTemplate.java:140)

        at oracle.iam.platform.tx.OIMTransactionManager.execute(OIMTransactionManager.java:22)

        at oracle.iam.catalog.repository.DBRepository.updateCatalogItems(DBRepository.java:4053)

        ... 193 more

Caused by: javax.transaction.SystemException: One-phase transaction BEA1-0A55CE70E54EFEEF22C1-6F696D4F7065726174696F6E7344425F69616D31 for resource oimOperationsDB_iam1 is in an unknown state.

        at weblogic.transaction.internal.XAServerResourceInfo.commit(XAServerResourceInfo.java:698)

        at weblogic.transaction.internal.ServerSCInfo.startCommit(ServerSCInfo.java:555)

        at weblogic.transaction.internal.ServerTransactionImpl.localCommit(ServerTransactionImpl.java:2064)

        at weblogic.transaction.internal.ServerTransactionImpl.globalRetryCommit(ServerTransactionImpl.java:2791)

        at weblogic.transaction.internal.ServerTransactionImpl.globalCommit(ServerTransactionImpl.java:2701)

        at weblogic.transaction.internal.ServerTransactionImpl.internalCommit(ServerTransactionImpl.java:319)

        at weblogic.transaction.internal.ServerTransactionImpl.commit(ServerTransactionImpl.java:267)

        at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:307)

        at weblogic.transaction.internal.TransactionManagerImpl.commit(TransactionManagerImpl.java:301)

        at org.springframework.transaction.jta.JtaTransactionManager.doCommit(JtaTransactionManager.java:1028)

        ... 198 more

Caused by: oracle.jdbc.xa.OracleXAException

        at oracle.jdbc.xa.OracleXAResource.checkError(OracleXAResource.java:1657)

        at oracle.jdbc.xa.client.OracleXAResource.commit(OracleXAResource.java:757)

        at weblogic.jdbc.jta.DataSource.commit(DataSource.java:1110)

        at weblogic.transaction.internal.XAServerResourceInfo.commit(XAServerResourceInfo.java:1434)

        at weblogic.transaction.internal.XAServerResourceInfo.commit(XAServerResourceInfo.java:609)

        ... 207 more

Caused by: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1

ORA-06550: line 1, column 7:

PLS-00306: wrong number or types of arguments in call to 'SYNCRN'

ORA-06550: line 1, column 7:

PL/SQL: Statement ignored

As it seems like, there must be some strange issues with the transaction configuration or something related to the resource/data source oimOperationsDB_iam1.

Has anyone come across this issue before? How did you fix it?

Regards,

Vegard Aasen

Tagged:

Best Answer

  • Dmitry Berezkin
    Dmitry Berezkin Moscow, RussiaMember Posts: 389 Silver Badge
    edited Jun 16, 2015 6:52AM Answer ✓

    It seems like database problem. I found similar one in "Doc ID 1638989.1".

    In your log I see that it is issue in catalog (at oracle.iam.catalog.repository.DBRepository.updateCatalogItems(DBRepository.java:4053)).

    The solution was this: "Apply the database patch #17501296 to the database version 11.2.0.4".

Answers

  • Dmitry Berezkin
    Dmitry Berezkin Moscow, RussiaMember Posts: 389 Silver Badge
    edited Jun 16, 2015 6:52AM Answer ✓

    It seems like database problem. I found similar one in "Doc ID 1638989.1".

    In your log I see that it is issue in catalog (at oracle.iam.catalog.repository.DBRepository.updateCatalogItems(DBRepository.java:4053)).

    The solution was this: "Apply the database patch #17501296 to the database version 11.2.0.4".

  • vegaasen
    vegaasen Member Posts: 96
    edited Jun 17, 2015 1:30AM

    Thanks for the reply! This seems to actually fix the problem, so I guess it was closely related to the oracle database v 11.2.0.4, which is indeed the version we use in all our environments.

    Regards,

    Vegard

This discussion has been closed.