Forum Stats

  • 3,836,791 Users
  • 2,262,191 Discussions
  • 7,900,111 Comments

Discussions

Admin server running into issues in SOA.

1007055
1007055 Member Posts: 8
edited Jul 24, 2013 6:06PM in SOA Suite Discusssions

Hi All,

Can anyone help me.

I have recently  installed Oracle SOA suite on Linux box. While I was running the Admin Server I am running into Some issues. Though Admin Server is running fine but all that I am running out of memory because of the Logs. Can anyone help me find the issue and solve. I can do some other arrangements to save memory. IF you could help me for any issue I would be so happy. One more thing SOA suite installed on Admin server instead soa_server1 or soa_server2. I still need to SOA-infra setup onto soa_server1 or soa_server2(on different remote machines) [if this info could help also.]

This issue is repeating every 5 secs.

<Jul 16, 2013 5:35:21 PM EDT> <Error> <oracle.soa.mediator.common.listener> <BEA-000000> <DBLocker caught exception while retrieving locked messages. Will retry retrieval after 2 seconds

Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.6.0) (Build 111018)): oracle.toplink.exceptions.DatabaseException

Internal Exception: java.sql.SQLSyntaxErrorException: ORA-00904: "TENANT_ID": invalid identifier

Error Code: 904

Call: SELECT CASE_ID, CONTAINER_ID, DUMMY1, MSG_ID, COMPONENT_DN, OPERATION, CREATION_DATE, PRIORITY, COMPONENT_STATUS, QNAME_LOCAL_PART, CASE_INFO, QNAME_NAMESPACE, LOCK_TIME, SOURCE_URI, TENANT_ID, INSTANCE_CREATED, IS_EVENT, STATUS FROM MEDIATOR_DEFERRED_MESSAGE WHERE (((STATUS = ?) AND (LOCK_TIME = ?)) AND (CONTAINER_ID = ?))

        bind => [1, 2013-07-16 17:23:12.814, A8424220EE5D11E2BF9C6D1C72885086]

Query: ReadAllQuery(oracle.tip.mediator.common.persistence.MediatorDeferredMessage)

        at oracle.toplink.exceptions.DatabaseException.sqlException(DatabaseException.java:305)

        at oracle.toplink.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:614)

        at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:468)

        at oracle.toplink.threetier.ServerSession.executeCall(ServerSession.java:447)

        at oracle.toplink.internal.sessions.IsolatedClientSession.executeCall(IsolatedClientSession.java:117)

        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:193)

        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:179)

        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeSelectCall(DatasourceCallQueryMechanism.java:250)

        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.selectAllRows(DatasourceCallQueryMechanism.java:583)

        at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectAllRowsFromTable(ExpressionQueryMechanism.java:2500)

        at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectAllRows(ExpressionQueryMechanism.java:2458)

        at oracle.toplink.queryframework.ReadAllQuery.executeObjectLevelReadQuery(ReadAllQuery.java:467)

        at oracle.toplink.queryframework.ObjectLevelReadQuery.executeDatabaseQuery(ObjectLevelReadQuery.java:874)

        at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:679)

        at oracle.toplink.queryframework.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:835)

        at oracle.toplink.queryframework.ReadAllQuery.execute(ReadAllQuery.java:445)

        at oracle.toplink.internal.sessions.AbstractSession.internalExecuteQuery(AbstractSession.java:2265)

        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1079)

        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1063)

        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1037)

        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1009)

        at oracle.tip.mediator.dispatch.db.DBAccess.getMessageFromDB(DBAccess.java:800)

        at oracle.tip.mediator.dispatch.db.DBAccess.getDeferredMessages(DBAccess.java:821)

        at oracle.tip.mediator.dispatch.db.DeferredDBLocker.getLockedMessages(DeferredDBLocker.java:153)

        at oracle.tip.mediator.common.listener.DBLocker.getLockedMessages(DBLocker.java:173)

        at oracle.tip.mediator.common.listener.DBLocker.run(DBLocker.java:93)

        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)

        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)

        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)

Caused By: java.sql.SQLSyntaxErrorException: ORA-00904: "TENANT_ID": invalid identifier

        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)

        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)

        at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)

        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)

        at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)

        at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:548)

        at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:217)

        at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:947)

        at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1283)

        at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1441)

        at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3769)

        at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3823)

        at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1671)

        at weblogic.jdbc.wrapper.PreparedStatement.executeQuery(PreparedStatement.java:135)

        at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeSelect(DatabaseAccessor.java:814)

        at oracle.toplink.internal.databaseaccess.DatabaseAccessor.basicExecuteCall(DatabaseAccessor.java:540)

        at oracle.toplink.internal.databaseaccess.DatabaseAccessor.executeCall(DatabaseAccessor.java:468)

        at oracle.toplink.threetier.ServerSession.executeCall(ServerSession.java:447)

        at oracle.toplink.internal.sessions.IsolatedClientSession.executeCall(IsolatedClientSession.java:117)

        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:193)

        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeCall(DatasourceCallQueryMechanism.java:179)

        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.executeSelectCall(DatasourceCallQueryMechanism.java:250)

        at oracle.toplink.internal.queryframework.DatasourceCallQueryMechanism.selectAllRows(DatasourceCallQueryMechanism.java:583)

        at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectAllRowsFromTable(ExpressionQueryMechanism.java:2500)

        at oracle.toplink.internal.queryframework.ExpressionQueryMechanism.selectAllRows(ExpressionQueryMechanism.java:2458)

        at oracle.toplink.queryframework.ReadAllQuery.executeObjectLevelReadQuery(ReadAllQuery.java:467)

        at oracle.toplink.queryframework.ObjectLevelReadQuery.executeDatabaseQuery(ObjectLevelReadQuery.java:874)

        at oracle.toplink.queryframework.DatabaseQuery.execute(DatabaseQuery.java:679)

        at oracle.toplink.queryframework.ObjectLevelReadQuery.execute(ObjectLevelReadQuery.java:835)

        at oracle.toplink.queryframework.ReadAllQuery.execute(ReadAllQuery.java:445)

        at oracle.toplink.internal.sessions.AbstractSession.internalExecuteQuery(AbstractSession.java:2265)

        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1079)

        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1063)

        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1037)

        at oracle.toplink.internal.sessions.AbstractSession.executeQuery(AbstractSession.java:1009)

        at oracle.tip.mediator.dispatch.db.DBAccess.getMessageFromDB(DBAccess.java:800)

        at oracle.tip.mediator.dispatch.db.DBAccess.getDeferredMessages(DBAccess.java:821)

        at oracle.tip.mediator.dispatch.db.DeferredDBLocker.getLockedMessages(DeferredDBLocker.java:153)

        at oracle.tip.mediator.common.listener.DBLocker.getLockedMessages(DBLocker.java:173)

        at oracle.tip.mediator.common.listener.DBLocker.run(DBLocker.java:93)

        at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)

        at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:184)

        at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)

Thank you all.

Best Answer

  • Ravi Jegga
    Ravi Jegga Member Posts: 809
    Answer ✓

    Step 2 is totally wrong and will NOT work. That is the root cause. If you just update the row to 11.7, it will NOT work.

    As mentioned, you should and must install RCU 11.7 which is already there in downloads site along with SOA 11.7. So download this zip file and unzip it.

    Before running 11.7 RCU, I would recommend to drop all old 11.5 schemas to free up database space. I hope you will be using SOA 11.7 only. So run old 11.5 RCU again. Select option to DROP and select proper prefix. Once all is cleaned, run RCU 11.7. This is must.

    Then delete old domain. Its corrupted. You can clean it by manually updating jdbc datasource files under config/jdbc folder. But I will NOT recommend this. Just delete this domain folder and from user_projects/appliations also delete the folder with same domain name.

    Create a brand new domain using config wizard. Select SOA or BPM whichever you want, and also Enterprise Manager. Then at database, carefully select 11.7 Schemas that you created earlier.

    Thanks

    Ravi Jegga

Answers

  • Ravi Jegga
    Ravi Jegga Member Posts: 809

    1. Which Version of SOA Suite software did you installed. Please give exact version like latest 11.7 or 11.6 etc.

    2. Which version of RCU did you installed. It should match Exactly with the same version of soa suite.

    3. When you run RCU, did you used any custom Prefix for databases or just used default like DEV which ends up like DEV_SOAINFRA, DEV_ORAMDS etc.

    4. In same database do you have multiple versions of RCU ran with different prefixes.

    5. Finally when you created soa domain, did you used right config wizard and pointed to right versions of soa_infra, mds schemas.

    Looks like issue is backend rcu schema is NOT matching with soa suite software.

    Thanks

    Ravi Jegga

    Ravi Jegga
  • 1007055
    1007055 Member Posts: 8

    Hi Ravi

    answers: 1) 

    **************************************************************

    INFO: Detected a WebLogic Installation.

    **************************************************************

    *****************************************************************************

    Oracle SOA Server version 11.1.1.7.0

              Build: 0

              Build time: Fri Mar 01 08:30:33 PST 2013

              Build type: release

              Source tag: PCBPEL_11.1.1.7.0SOABP_GENERIC_130301.0647.0008

    Oracle BAM Source Tag:ORABAM_11.1.1.7.0_GENERIC_130301.1059

    Oracle BPM Source Tag: PCBPEL_11.1.1.7.0SOABP_GENERIC_130301.0647.0008

    Oracle Implementation-Version: Oracle Middleware 11.1.1 (ASKERNEL_11.1.1.7.0_

    GENERIC_130228.1216, ADMINSERVER_11.1.1.7.0_GENERIC_130109.2300, J2EE

    _11.1.1.7.0_GENERIC_130224.1947, JDEVADF_11.1.1.7.0_GENERIC_130226.14

    00.6493, TOPLINK_11.1.1.6.0_GENERIC_111018.1700, ENTSEC_11.1.1.7.0_GE

    NERIC_130225.1523, FMWCONFIG_11.1.1.6.0_GENERIC_RELEASE)

    2. I have installed rcu version ofm_rcu_win_11.1.1.5.0 was run at my local to connect to the remote DB. This RCU schema were run as SYSDBA role.  All schema were created successfully. but while running Fmw wizard to setup SOA while configuring the JDBC component schema we faced an issue while testing the connections to jdbc connection url. errors were suggesting us to choose one of the schema suitable for each component schema

    for example if we have our schema prefix as labsoa_SOAINFRA of version 11.1.1.7.0 the created schema were 11.1.1.5.0. then suggestion on the error (as in connection Result.log as connection failed) to change it to the appropriate version to 11.1.1.7.0

    so we went and changed the RCU schema to 11.1.1.7.0 in the DB.. we had the same problem for labsoa_ORABAM,labsoa_ORASDPM, labsoa_MDS (for SOA MDS Schema).

    3. We did not use prefix as dev1 because we had some other schema with the same dev1 as prefix.

    4. yes We run rcu with different schema prefix names

    5. we run the FMW config with generic of SOA version 11.1.1.7.0 As I mentioned in the answer (2) we run into some issues but resolved by changing the versions in DB (for RCU schema.)

    1007055
  • 1007055
    1007055 Member Posts: 8

    It would be much appreciated if you can help me know what was the problem.

    can you also help me understand the error.

  • Ravi Jegga
    Ravi Jegga Member Posts: 809
    Answer ✓

    Step 2 is totally wrong and will NOT work. That is the root cause. If you just update the row to 11.7, it will NOT work.

    As mentioned, you should and must install RCU 11.7 which is already there in downloads site along with SOA 11.7. So download this zip file and unzip it.

    Before running 11.7 RCU, I would recommend to drop all old 11.5 schemas to free up database space. I hope you will be using SOA 11.7 only. So run old 11.5 RCU again. Select option to DROP and select proper prefix. Once all is cleaned, run RCU 11.7. This is must.

    Then delete old domain. Its corrupted. You can clean it by manually updating jdbc datasource files under config/jdbc folder. But I will NOT recommend this. Just delete this domain folder and from user_projects/appliations also delete the folder with same domain name.

    Create a brand new domain using config wizard. Select SOA or BPM whichever you want, and also Enterprise Manager. Then at database, carefully select 11.7 Schemas that you created earlier.

    Thanks

    Ravi Jegga

  • 1007055
    1007055 Member Posts: 8

    Hi Ravi,

    You are much appreciated for your valuable time and knowledge..

    Then delete old domain. Its corrupted. You can clean it by manually updating jdbc datasource files under config/jdbc folder. But I will NOT recommend this. Just delete this domain folder and from user_projects/appliations also delete the folder with same domain name.
    
    Create a brand new domain using config wizard. Select SOA or BPM whichever you want, and also Enterprise Manager. Then at database, carefully select 11.7 Schemas that you created earlier.
    

    Though I have not created a new domain. (still Ravi is correct)

    Issues were resolved by updating the new RCU schema with latest version of RCU 11.1.1.7.

    Here What I did is ran the rcu.bat on my local and connected to remote DB.created new schema for each components namely soa-infra,orabam,owsm,MDS. with a new prefix.

    I did not drop the previous schema for SOA.

    went to  *Domain-home*/config/jdbc/

    took the back up for all the *.xml files excluding read.xml(anyway its just an info file).

    Now edited the schema component. Someone might change their schema component password. but my suggestion is not to give any new passwords to the schema components while creating new RCU schema for SOA.

    What I did is changed the component passwords (I know how to mess up and also know how to fix if it's messed up) and ended up with errors.

    So I have now started the server with the command

    ./startWebLogic.sh -Dweblogic.configuration.schemaValidationEnabled=false

    Still I had errors coming up. But I least bothered about the errors because these errors can be solved once get to know what you are doing.

    My server started. Happy then

    Went to admin-url:port/console

    then  Home>Summary of JDBC Data Sources


    next lock & edit


    select each jdbc component and changed the password and confirm password for each
    then save each time for each  next  activate the changes.

    (as I changed all components passwords like <password-encrypted>asdl;lasdfadf=<password-encrypted/>   to <password>welcome1=<password/> in each *.xml file at *domain-home/config/jdbc*)


    I have restarted the Admin server from Command prompt. Expecting that I was doing correct.

    Succeeded. I did not believe that I have seen not even a single error.


    My sincere request that don't mess up with any *.xml file if you are not sure and make sure to take a back up


    Thank you.

    Thanks a lot.

    -Seshikanth

  • Ravi Jegga
    Ravi Jegga Member Posts: 809

    Hi Seshikanth

    1. Actually I was Stressing more on Point 2, where SOA 11.7 is Totally NOT supported with RCU 11.5 and that was the root cause for your issue in first place.

    2. I should have given more options once you address above thing.

    3. Yes, if you already had a BPM Domain with all soainfra, mds datasources created, still you can modiify backend RCU (remove and install again) as far as you maintain exactly same Prefix or names for schemas like soainfra, mds etc along with SAME Password. Rest will be same like db host, db port, sid. So simple run rcu drop everything. Run 11.7 RCU again and use same names for datasources with same password.

    4. Then just start the adminserver, soa server and you will be all set.

    5. Worst case, just drop everything and create a brand new domain. The Config Wizard should take like 5 mts to create a full fledged soa / bpm domain.

    6. And yes, do not modify jdbc xml files directly. Instead go to Weblogic Admin Console and for each DataSource and edit and change and put new password. This step would have been avoided, if you recreated the RCU 11.7 with same prefix and same password.

    Thanks

    Ravi Jegga

  • 1007055
    1007055 Member Posts: 8

    Hi Ravi,

    Your information was much helpful for me.

    It was a good opportunity for me learning the jdbc connections and its important especially in SOA.

    Thank you for your quick reply on this issue.

This discussion has been closed.