XSD Created for DBAdapter Which Is Based On Object In Schema Name Like OPS$XXXX Results In Invalid XSD
Last updated on SEPTEMBER 04, 2013
Applies to:Oracle SOA Suite - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
- When a DBAdapter is created in JDeveloper to call a Procedure, and this procedure uses a database type from a username in a this format: OPS$XXX, the generated XML schema file will have the '$' in the name of the type. The result of this is to make the generated XSD file invalid.
- The issue also reproduces in the following scenario described below:
If DB adapter used as query having special characters, error occurs in generated xsd.
SELECT TRUNC(SYSDATE) FROM DUAL the variable at the generated schema will be "TRUNC(SYSDATE)" - this also results in the generated XSD error being invalid.
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