Lack of information and direction creates errors in the server start up when trying to configure an Oracle DefaultDS

Description of problem: Lack of information and direction creates errors in the server start up when trying to configure an Oracle DefaultDS.

Version-Release number of selected component (if applicable):

How reproducible: go to 2.3. Configuring a datasource for Oracle DB
http://docs.redhat.com/docs/en-US/JBoss_Enterprise_Application_Platform/5/html/Getting_Started_Guide/Configuring_a_datasource_for_Oracle_DB.html

If I follow the directions here I get error after error and the solutions are not simple to track down. So I wrote out the commands for a linux install that will walk you through the steps that need to added to make the set up of an Oracle DS as DefaultDS work.

1. cd /var/lib/jbossas/server/xxx/deploy/messaging/
2. rm hsqldb-persistence-service.xml
a. this is in the docs/examples/jms/ also so you don’t need to save a copy of it.
3. cp /var/lib/jbossas/docs/examples/jms/oracle-persistance-service.xml .
4. vim oracle-persistence-service.xml
a. do a find on ‘Channel’
b. comment out the 4 lines below the Note that tells you to comment out the lines, like so.
<!--depends optional-attribute-name="ChannelFactoryName">jboss.jgroups:service=ChannelFactory</depends>
<attribute name="ControlChannelName">jbm-control</attribute>
<attribute name="DataChannelName">jbm-data</attribute>
<attribute name="ChannelPartitionName">${jboss.partition.name:DefaultPartition}JMS</attribute->

5. chown jboss:jboss *
6. cd /var/lib/jbossas/server/xxx/deploy
7. vim default-oracle-ds.xml
a. The database listed in <type-mapping>Oracle9i</type-mapping> should match one of the <type-mapping> found in /var/lib/jbossas/server/xxx/conf/standardjbosscmp-jdbc.xml
b. In this case make sure it is set to <type-mapping>Oracle9i</type-mapping>
8. restart jBoss.

This link is older but helped; https://community.jboss.org/wiki/ChangeDefaultDataSource

Also it would help if you could list what the Roles and Permissions should be set to for the User that is used in the DefaultDS for Oracle. SYSTEM with all permissions is not practical for most databases. You explain this for the MySQL install but not for Oracle.