Hide Forgot
Date of First Response: 2009-12-16 10:47:14 Workaround Description: after running the schema tool, replace <type-mapping>Oracle10g</type-mapping> with <type-mapping>Oracle9i</type-mapping> in deploy/oracle-ds.xml project_key: SOA tools/schema/oracle10g/template/oracle-ds.xml: <metadata> <type-mapping>Oracle10g</type-mapping> </metadata> This has to be changed to Oracle9i to match the entry in standardjbosscmp-jdbc.xml.
Fixed with revision 4546 of: build-tools/resource/schema-tool/oracle10g/template/oracle-ds.xml Commit message: SOA-1716 Use Oracle9i type-mapping in order to be consistent with other EAP components.
Still present in jbm-oracle-ds.xml
Fixed with revision 4631 of: build-tools/resource/schema-tool/schema-tool/oracle10g/template/jbm-oracle-ds.xml Commit message: SOA-1716 Set the type-mapping to Oracle9i for the jbm datasource as well.
Verified in ER7.