Connectivity with a Microsoft SQL Server 2005 Security Database May Fail With Some Webcenter Interaction Products
Last updated on DECEMBER 02, 2016
Applies to:Oracle-BEA AquaLogic Pathways - Version 1.5.0 and later
Oracle WebCenter Interaction Common Security - Version 1.0 and later
Oracle WebCenter Ensemble - Version 10.3.0.0 and later
Oracle WebCenter Interaction Common Remoting Servic - Version 2.0.0 and later
Oracle WebCenter Analytics - Version 2.5 and later
Information in this document applies to any platform.
***Checked for relevance on 28-Jan-2014***
Connectivity with a MS SQL Server 2005 Security Database may fail with some Webcenter Interaction Activity Services, if the Security Database Password has the particular string pattern, 'ORACLExxxxxxxx'.
For example, WebCenter Analytics 10.3.0.1 is one of the Activity Services that utilizes the 'Common Security Services' component. When Analytics connects to the Security Database in SQL Server 2005, 'Common Security Services' incorrectly chooses to use an Oracle dictionary to submit queries to the database.
When analyzing a PTSPY trace of the Analytics product, the Common Security Services logs the following message:
WrapperStartStopAppMain com.bea.common.security.service.StoreService Using dictionary class "org.apache.openjpa.jdbc.sql.OracleDictionary".
The wrapper.log of the Analytics Service shows an invalid MS SQL Server 2005 Query with an 'incorrect syntax' error:
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