I have installed WLS 11g on OEL-5.5 and created domain successfully. But unable to start Weblogic Server (getting the following error). The sys password is working fine in Repository Database (schema for Middleware).
WLS 11g (10.3.6)
OS- OEL 5.5 64bit
I found a strange thing during Domain creation, all the details (Port, SID, hostname, sys with password) are fine but while doing Test Connection , it failed. I faced this issue on both 32-bit & 64-bit OEL while the Database, Listener were up and running. I have used the same details while running RCU in middleware repository Database and it was completed successfully with proper schema creation. There was no issue on connectivity or Database availability, but still failed to connect (JDBC) to Database while domain creation. When I clicked next (evenif after failing Test Connection), the domain was created properly. But unable to start WLS Server.
[oradb02@mannat bin]$ pwd
[oradb02@mannat bin]$ ls -lrt
drwxr-x--- 2 oradb02 oinstall 4096 Oct 9 22:22 service_migration
drwxr-x--- 2 oradb02 oinstall 4096 Oct 9 22:22 server_migration
drwxr-x--- 2 oradb02 oinstall 4096 Oct 9 22:22 nodemanager
-rwxr-x--- 1 oradb02 oinstall 1984 Oct 9 22:22 stopWebLogic.sh
-rwxr-x--- 1 oradb02 oinstall 2426 Oct 9 22:22 stopManagedWebLogic.sh
-rwxr-x--- 1 oradb02 oinstall 5699 Oct 9 22:22 startWebLogic.sh
-rwxr-x--- 1 oradb02 oinstall 3213 Oct 9 22:22 startManagedWebLogic.sh
-rwxr-x--- 1 oradb02 oinstall 13266 Oct 9 22:22 setDomainEnv.sh
[oradb02@mannat bin]$ ./setDomainEnv.sh
[oradb02@mannat bin]$ ./startWebLogic.sh
JAVA Memory arguments: -Xms256m -Xmx512m -XX:MaxPermSize=256m
WLS Start Mode=Production
=================== ERROR ==================================================================================
<Oct 11, 2012 8:10:02 AM IST> <Info> <Security> <BEA-090905> <Disabling CryptoJ JCE Provider self-integrity check for better startup performance. To enable this check, specify -Dweblogic.security.allowCryptoJDefaultJCEVerification=true>
<Oct 11, 2012 8:10:04 AM IST> <Info> <Security> <BEA-090906> <Changing the default Random Number Generator in RSA CryptoJ from ECDRBG to FIPS186PRNG. To disable this change, specify -Dweblogic.security.allowCryptoJDefaultPRNG=true>
<Oct 11, 2012 8:10:06 AM IST> <Info> <WebLogicServer> <BEA-000377> <Starting WebLogic Server with Java HotSpot(TM) 64-Bit Server VM Version 20.8-b03 from Sun Microsystems Inc.>
<Oct 11, 2012 8:10:12 AM IST> <Info> <Management> <BEA-141107> <Version: WebLogic Server 10.3.6.0 Tue Nov 15 08:52:36 PST 2011 1441050 >
<Oct 11, 2012 8:10:25 AM IST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: [Management:141266]Parsing Failure in config.xml: javax.management.InvalidAttributeValueException: Illegal value for Properties: user=sys,sysdba>
<Oct 11, 2012 8:10:25 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Oct 11, 2012 8:10:25 AM IST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Oct 11, 2012 8:10:25 AM IST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
While Domain Creation sys user name and password are never required for the repository database .
Sys user name and password are required for the RCU utility to create the schema in the repository database which has different owner ( schema username and schema password ).
Once the schema the schema is created , then while creating the domain we have to specify the DB details ( hostame , port ) and the schema username and password .
Yes, it is correct that during RCU installation installer asks the database details. But there is a screen "Configure RDBMS Security Store Database" during Domain creation. I put the correct details as I have given during RCU (successfully created the schemas), but when I clicked "Test Connection", it failed. I completed the Domain creation after clicking next and now getting the above error while starting WLS.
I guess it comes with Optional Configuration of Keystore Credentials for "RDBMS Security Store" option(domain creation).
But evenafter putting correct details (sys password), why this error came out.