Portal 4.0 switch to Oracle yields ORA-24327

Question

I'm switching from the cloudscape database to an
Oracle 8.1.7 database for the Portal 4.0 pools
(commerce and dataSync) and the realm under the portalDomain.
I followed the directions enumerated in
http://e-docs.bea.com/wlp/docs40/deploygd/oraclnew.htm
WLS6.1/Portal4.0 is running on Solaris.
utils.dbping is successful.
sqlplus is successful
Booting the portal server is not successful. It yields:
<Nov 6, 2001 10:52:40 AM EST> <Notice> <Management> <Loading configuration file
./config/portalDomain/config.xml ...>
<Nov 6, 2001 10:52:49 AM EST> <Info> <Logging> <FileLogger Opened.>
Starting Loading jDriver/Oracle .....
---------- LOGIN ERROR CODE: 24327
<Nov 6, 2001 10:52:59 AM EST> <Emergency> <Server> <Unable to initialize the server:
'Fatal initialization exception
Throwable: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSException:
An error occured creating a database connection for the realm.]
java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSException:
An error occured creating a database connection for the realm.]
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:62)
at weblogic.security.SecurityService.initializeRealm(SecurityService.java:258)
at weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:390)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
'>
The WebLogic Server did not start up properly.
Exception raised: java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSException:
An error occured creating a database connection for the realm.]
java.lang.IllegalAccessError: Exception[com.bea.p13n.security.realm.RDBMSException:
An error occured creating a database connection for the realm.]
at weblogic.security.acl.Realm.getRealm(Realm.java:91)
at weblogic.security.acl.Realm.getRealm(Realm.java:62)
at weblogic.security.SecurityService.initializeRealm(SecurityService.java:258)
at weblogic.security.SecurityService.initialize(SecurityService.java:115)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:390)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:202)
at weblogic.Server.main(Server.java:35)
Reason: Fatal initialization exception
Any help would be appreciated.
Regards,
Matt

Answer 1

thx your response is very very usefull!!!
"Matthew Marquand" <[email protected]> wrote:
>
Just minutes ago I found the problem. It was
caused from faulty documentation at:
http://e-docs.bea.com/wlp/docs40/deploygd/oraclnew.htm
The "set your properties to this" examples look like
the following:
     user=@ORACLE_USER@;
     server=@ORACLE_NET_SERVICE_NAME@,
     weblogic.t3.waitForConnection=true;
     weblogic.t3.waitSecondsForConnection=999999999999,
     weblogic.jts.waitSecondsForConnectionSecs=999999999999,
     verbose=false
I changed the @TAG@ parms correctly but note the inconsistent use of
',' vs. ';'
Not knowing what was required I did what the doc told me to do
and therefore screwed up my config.xml such that the server
wouldn't boot.
Every property should be semi-colon separated and not comma
separated.
The trailing comma on the server name was triggering an
attempt to connect to "NCFEDB_D," (which is not in tnsnames.ora)
rather than "NCFEDB_D".
Just thought I reply to my own issue since it seems this
problem is somewhat rampant on this newsgroup with no
clear alternatives other than just the basic "verify your ORACLE_HOME"
variable.
Matt