Skip to main content

Weblogic Server not coming up using script startWebLogic

Issue:

 Weblogic service is not coming up  using script (startWebLogic.sh).

 Dec 10, 2014 6:44:29 PM AST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: Could not obtain an exclusive lock to the embedded LDAP data files directory: 
<01/06/2012 10:56:47 AM EST> <Error> <Store> <BEA-280061> <The persistent store "_WLS_AdminServer" could not be deployed: weblogic.store.PersistentStoreException: [Store:280105]The persistent file store "_WLS_AdminServer" cannot open file _WLS_ADMINSERVER000000.DAT
<MW_HOME>/user_projects/domains/IDMDomain/servers/AdminServer/data/ldap/ldapfiles because another WebLogic Server is already using this directory. Ensure that the first WebLogic Server is completely shutdown and restart the server.>
<Dec 10, 2014 6:44:29 PM AST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Dec 10, 2014 6:44:29 PM AST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Dec 10, 2014 6:44:29 PM AST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
Casue:

 Weblogic service fails to start for many reasons:

 1. Force shutdown of the Weblogic Service.
2. Unable to lock the files required to start the service.

 Solution:

 1. Navigate to Idapfiles location under server and delete the “EmbeddedLDAP.lok” file from there, location would be e.g.<MW_HOME>/user_projects/domains/<Domain_Name>/servers/AdminServer/data/ldap/ldapfiles

 EmbeddedLDAP.lok” won't allow Admin server to come up, then perform the following additional steps.

 1. cd $DomainHome/servers/AdminServer/data/store
2. find . –name *.DAT
3. Verify the file name in your result and error message should be same.
4. Rename this file and move from this directory to some other directory.
5. find "EmbeddedLDAP.lok" and "AdminServer.lok" as well and remove the same.
6. check the port using netstat –an | grep <Weblogic server port>, there should not be any open connection to this port.
7. Start your weblogic server either via weblogic script or node manner.

Note: .DAT file is very important file, and contains business data as well in Production system. Please take a backup of this file before doing any operation on it, so that later this file can be analysed to complete those transaction.

Labels:

Comments

Post a Comment

Popular posts from this blog

Node id does not exist for the current application server id

Issue: After completing cloning procedure, you generally may across the following issue. "Node id does not exist for the current application server id". Solution: First stop the application. Run adgendbc.sh script to configure apps tier dbc file with the correct id from the database instance. Start the application and test your issue. Location of script: 11i: $COMMON_TOP/admin/install/$CONTEXT_NAME R12: $INST_TOP/admin/install [appldev@erptest install]$ sh adgendbc.sh (Note: It will prompt you to give apps username and apps password.)
Post a Comment
Read more

How to change EBS R12 database and application port number

On Database Tier 1. Logon as oracle database user and source environment for R12 RDBMS ORACLE_HOME 2. Start database instance for which you want to change R12 port 3. Backup contextfile 4. Change as below in contextfile         dbport  : Change database port from 1521 to 1541         db_ons_localport : 6300 to 6320         db_ons_remoteport : 6400 to 6420         cmanport : 1521 to 1541 5. Run adautocfg.sh On Apps Tier Change Application port from 8000 to 8020 1. Logon as application manager user and source environment for R12 2. Backup contextfile 3. Run adpreclone    $ perl ./adpreclone.pl appsTier 4. Run adcfgclone and choose new port pool    $ cd $COMMON_TOP/clone/bin    $ perl ./adcfgclone.pl appsTier 5. Check new application URL SQL> select home_url from icx_parameters; HOME_URL ----------...
Post a Comment
Read more

Oracle R12 : You are trying to access a page that is no longer active

Login fails “You are trying to access a page that is no longer active.” The issue can be reproduced at will with the following steps: Issue : After cloning process the login page of Oracle E-Business Suite R12 show the above error. Solution :  For this you need to update the new hostname in the  icx_parameteres table 1.   SQL> SELECT SESSION_COOKIE_DOMAIN FROM icx_parameters; SESSION_COOKIE_DOMAIN --------------------- erp.local.com (This is hostname of Source Application Tier) 2. SQL>update icx_parameters set SESSION_COOKIE_DOMAIN = ‘target.local.com’; 1 row updated. SQL> commit; Commit complete. (This has changed the SESSION_COOKIE_DOMAIN of target application to target hostname.domain_name) 3. SQL> SELECT SESSION_COOKIE_DOMAIN FROM icx_parameters; SESSION_COOKIE_DOMAIN --------------------- target.local.com
Post a Comment
Read more