SOA Server Does Not Start When SQL Server Is Used As A Repository On A 64-bit Operating System (Doc ID 1317137.1)

Last updated on MAY 09, 2016

Applies to:

Oracle SOA Suite - Version 11.1.1.4.0 and later
Microsoft Windows x64 (64-bit) - OS Version: 7
Microsoft Windows x64 (64-bit)
Microsoft Windows x64 (64-bit) - Version: 2008 R2
***Checked for relevance on 07-June-2013***

Symptoms

 

The issue occurs using SOA with a SQL Server Database on a 64-bit Windows.
The AdminServer is up and running but the Managed SOA Server(s) can not be started.


A new SOA Application was installed.
In order to configure SQL Server with SOA the following steps need to be followed:
Oracle® Fusion Middleware Installation Guide for Oracle SOA Suite and Oracle Business Process Management Suite Part Number E13925-04
XA Configuration Required to Start the SOA Infrastructure on Microsoft SQL Server
http://download.oracle.com/docs/cd/E17904_01/doc.1111/e13925/troubleshooting.htm#INSOA308

When the managed soa server(s) are starting, in the AdminServer-diagnostic.log the following exception is generated:

[AdminServer] [ERROR] [] [oracle.mds] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: f0908eb5035c2d5c:46f691a8:12f78337a75:-8000-0000000000000002,0] [APP: soa-infra] [[
oracle.mds.lcm.exception.MDSLCMException: MDS-01330: unable to load the configuration document MDS
MDS-01329: unable to load the element "persistence-config "
MDS-01370: The configuration of the MetadataStore to metadata-store-usage "soa-infra-store" is invalid.
[FMWGEN][SQLServer JDBC Driver][SQLServer]Could not find stored procedure 'mds_getRepositoryVersion'.

at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:710)
at oracle.mds.internal.lcm.deploy.DeployManager.startDeployment(DeployManager.java:198)
at oracle.mds.internal.lcm.MDSLifecycleListenerImpl.start(MDSLifecycleListenerImpl.java:215)
...
Caused by: oracle.mds.config.MDSConfigurationException: MDS-01330: unable to load the configuration document MDS
MDS-01329: unable to load the element "persistence-config "
MDS-01370: The configuration of the MetadataStore to metadata-store-usage "soa-infra-store" is invalid.
[FMWGEN][SQLServer JDBC Driver][SQLServer]Could not find stored procedure 'mds_getRepositoryVersion'.


at oracle.mds.config.PConfig.loadFromBean(PConfig.java:690)
at oracle.mds.config.PConfig.loadFromBean(PConfig.java:517)
at oracle.mds.config.PConfig.<init>(PConfig.java:341)
at oracle.mds.internal.lcm.MDSLCMManager.getContentConfig(MDSLCMManager.java:2011)
at oracle.mds.internal.lcm.deploy.DeployManager.deploy(DeployManager.java:505)
...
]]
[AdminServer] [ERROR] [SDP-25088] [oracle.sdp.messaging.engine] [tid: [ACTIVE].ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid: f0908eb5035c2d5c:46f691a8:12f78337a75:-8000-0000000000000038,0] [APP: usermessagingserver] Unable to refresh the driver locator cache, due to the following error: EJB Exception: : Local Exception Stack: [[
Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.4.0) (Build 101210)): oracle.toplink.exceptions.DatabaseException
Internal Exception: java.sql.SQLSyntaxErrorException: [FMWGEN][SQLServer JDBC Driver][SQLServer]Invalid object name 'DRIVER_INFO'.
Error Code: 208
Call: SELECT DRIVER_NAME, MIME_TYPES, PROTOCOLS, CARRIERS, SENDER_ADDRESSES, COST, DELIVERY_TYPES, SPEED, STATUS_TYPES, CHECKSUM, SUPPORTS_CANCEL, ENCODINGS, SUPPORTS_REPLACE, SUPPORTS_TRACKING, SUPPORTS_STATUS_POLLING, DEFAULT_SENDER, CAPABILITY, LOCK_VERSION FROM DRIVER_INFO
Query: ReadAllQuery(oracle.sdpinternal.messaging.config.DriverInfo)
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)
...
Caused by: java.sql.SQLSyntaxErrorException: [FMWGEN][SQLServer JDBC Driver][SQLServer]Invalid object name 'DRIVER_INFO'.
at weblogic.jdbc.sqlserverbase.dda4.b(Unknown Source)
at weblogic.jdbc.sqlserverbase.dda4.a(Unknown Source)
...
; nested exception is: Exception [TOPLINK-4002] (Oracle TopLink - 11g Release 1 (11.1.1.4.0) (Build 101210)): oracle.toplink.exceptions.DatabaseException
Internal Exception: java.sql.SQLSyntaxErrorException: [FMWGEN][SQLServer JDBC Driver][SQLServer]Invalid object name 'DRIVER_INFO'.
Error Code: 208
Call: SELECT DRIVER_NAME, MIME_TYPES, PROTOCOLS, CARRIERS, SENDER_ADDRESSES, COST, DELIVERY_TYPES, SPEED, STATUS_TYPES, CHECKSUM, SUPPORTS_CANCEL, ENCODINGS, SUPPORTS_REPLACE, SUPPORTS_TRACKING, SUPPORTS_STATUS_POLLING, DEFAULT_SENDER, CAPABILITY, LOCK_VERSION FROM DRIVER_INFO
Query: ReadAllQuery(oracle.sdpinternal.messaging.config.DriverInfo)
]]

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms