My Oracle Support Banner

DB Schema Name Appears in the DB Adapter Mappings File, which Makes Migration of the SOA Composite App Difficult (Doc ID 1571814.1)

Last updated on AUGUST 31, 2018

Applies to:

Oracle SOA Platform - Version 11.1.1.6.0 and later
Information in this document applies to any platform.

Symptoms

When the DB Adapter is configured to connect to a database in JDeveloper, the resulting artifact files created by the DbAdapter wizard can contain the Database schema name.

reference files:

{dbadapter_component_name}-or-mappings.xml

{dbadapter_component_name}-properties.xml

 

As an example,

In the EMPDB-properties.xml file:

   <?xml version = '1.0' encoding = 'UTF-8'?>
    <!DOCTYPE properties SYSTEM "http://java.sun.com/dtd/properties.dtd">
    <properties>
       <entry key="DEV_DBCB.EMPLOYEE.IDNUME:db_column_type">DECIMAL</entry>
       <entry key=""DEV_DBCB.EMPLOYEE.IDAGRU:db_column_size">20</entry>

And In the EMPDB-or-mappings.xml file:

      <class-mapping-descriptor xsi:type="object-relational-class-mapping-descriptor">
         <class>EMPDB.EMPLOYEE</class>
         <alias>DEV_DBCB.EMPLOYEE</alias>

 

 and:     <tables>
            <table name="DEV_DBCB.EMPLOYEE"/>
         </tables>

 
Because these are .xml files, they cannot be modified via a config plan. A strategy is needed for migrating the DB Adapter related code to different environments.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.