Hide Forgot
Date of First Response: 2008-11-21 02:34:40 project_key: SOA When Oracle 10g is used as the DB for the management console - this warning is displayed once at console startup: 15:45:11,854 INFO [DatasourceConnectionProvider] Using datasource: java:/ManagementDS 15:45:11,867 INFO [SettingsFactory] RDBMS: Oracle, version: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - Production With the Partitioning, OLAP and Data Mining options 15:45:11,867 INFO [SettingsFactory] JDBC driver: Oracle JDBC driver, version: 10.2.0.2.0 15:45:11,893 INFO [Dialect] Using dialect: org.hibernate.dialect.OracleDialect 15:45:11,894 WARN [Oracle9Dialect] The Oracle9Dialect dialect has been deprecated; use either Oracle9iDialect or Oracle10gDialect instead 15:45:11,896 WARN [OracleDialect] The OracleDialect dialect has been deprecated; use Oracle8iDialect instead
Link: Added: This issue depends SOA-524
Link: Added: This issue depends SOA-528
Link: Added: This issue depends SOA-527
Link: Added: This issue is related to SOA-529
Can we have confirmation that fixes are in place for 4.2CP03.
Link: Added: This issue depends JBESB-2202
I have changed the management console and split the oracle configuration into oracle9i and oracle10g. While doing this I was wondering whether the initial error was actually caused by the SOA DB configuration tooling and, perhaps, that had been fixed independently of the ESB issue. We should take another look at the SOA 4.3 issues and find out *why* the error mysteriously disappeared in that stream.
There is a documentation change which needs to be reflected in the SOA docs but I forgot to update the ESB ones. The change is in the ESB_SOA_Monitoring_Guide.pdf and is as follows Page 1, section 1.1.1 "edit this file and change the db property to mysql or oracle respectively" should be changed to "edit this file and change the db property to mysql, oracle9i or oracle10g respectively" I'll create an ESB issue to handle this in the next ESB CP. Kev
Text replaced with: The file ${install_path}/jboss-as/tools/console/management-esb/db.properties defines the database settings for the console. By default this file contains the line: db=hsqldb which defines the database to use as HSQLDB. Changing the backend database is done by editing this file and specifying the identifier for your database here. The allowable values are: • hsqldb - Hypersonic Database. • mysql - MySQL • oracle9i - Oracle 9i • oracle10g - Oracle 10g You also must add your JDBC driver jar file into the server/${instance}/lib directory of your application server. JBoss ships with hsqldb.jar in this directory by default.
Len, the additional issue is SOA-709 and is marked as "won't fix" for CP03. I can add this if it is agreed and there is a need to respin.
Release Note: Oracle users can now specify the database property for the ESB Management console as oracle9i or oracle10g instead of oracle to avoid warnings being displayed at startup. This is documented in the ESB Monitoring Guide.
The warning no longer appears on SOA-P 4.2.0 CP03 CR5.
Link: Added: This issue related SOA-1121