Search This Blog

Sunday, 22 November 2015

Oracle 11.2.0.3 (11gR2) installation error message “File not found WFMLRSVCApp.ear”




11gr2 Installation error, when I was installing 11.2.0.3 I was shocked to see this error. Even after performing all the pre-reqs i encountered this issue.


 


Cause:

The issue is due to not unzipping the  p10404530_112030_Linux-x86-64_1of7.zip and  p10404530_112030_Linux-x86-64_2of7.zip properly.
Unzipped the files again, Installation will finish the installation successfully.
 


 

Saturday, 14 November 2015

OBIEE Weblogic Managed Server FORCE SHUT DOWN

Error :

Nov 12, 2015 12:21:26 AM CST> <Emergency> <Security> <BEA-090087> <Server failed to bind to the configured Admin port. The port may already be used by another process.>
<Nov 12, 2015 12:21:26 AM CST> <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default". The address 192.168.2.1 might be incorrect or another process is using port 9704: java.net.BindException: Address already in use.>
<Nov 12, 2015 12:21:26 AM CST> <Critical> <WebLogicServer> <BEA-000362> <Server failed. Reason: Server failed to bind to any usable port. See preceeding log message for details.>
<Nov 12, 2015 12:21:26 AM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FAILED>
<Nov 12, 2015 12:21:26 AM CST> <Error> <WebLogicServer> <BEA-000383> <A critical service failed. The server will shut itself down>
<Nov 12, 2015 12:21:26 AM CST> <Notice> <WebLogicServer> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN>
<Nov 12, 2015 12:21:26 AM CST> <Notice> <Cluster> <BEA-000163> <Stopping "async" replication service>

OR

Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default[3]". The address fe80:0:0:0:2acf:e9ff:fe64:20eb%0 might be incorrect or another process is using port 7001: java.net.BindException: Can't assign requested address.>
 <Error> <Server> <BEA-002606> <Unable to create a server socket for listening on channel "Default[2]". The address fe80:0:0:0:0:0:0:1%0 might be incorrect or another process is using port 7001: java.net.BindException: Can't assign requested address.>
<Notice> <Server> <BEA-002613> <Channel "Default[4]" is now listening on 127.0.0.1:7001 for protocols iiop, t3, ldap, snmp, http.>
<Warning> <Server> <BEA-002611> <Hostname "localhost", maps to multiple IP addresses: 127.0.0.1, 0:0:0:0:0:0:0:1, fe80:0:0:0:0:0:0:1%1>
<Notice> <Server> <BEA-002613> <Channel "Default[5]" is now listening on 0:0:0:0:0:0:0:1:7001 for protocols iiop, t3, ldap, snmp, http.>
<Notice> <Server> <BEA-002613> <Channel "Default[1]" is now listening on 192.168.2.93:7001 for protocols iiop, t3, ldap, snmp, http.>
<Notice> <Server> <BEA-002613> <Channel "Default" is now listening on 192.168.1.2:7001 for protocols iiop, t3, ldap, snmp, http.>

Reason:

1. There may be another server is running, which used Managed server port. Usually it will be 9704.

2. May be Admin server is started on one IP Address and Managed Server is starting on another address. This may happen bcos. In /etc/hosts file in windows/linux. there may be multiple IP Addresses provided than the Server will be ponted to multiple IP Address.

3. May be OBIEE Weblogic instance IP address got changed


Solution :

1. On both Linux and Windows, you need to update your hosts file (/etc/hosts or %SYSTEMROOT%\system32\drivers\etc\hosts respectively).
The manual says to put the following in your Windows hosts file, after the standard 127.0.0.1 localhost entry:
127.0.0.1 on Linux or 10.10.10.10 on Windows is common. 

Check you IP address. Verify it ping correctly.

1. In OBIEE FMW, Config.XML file. 

[[$FMW_HOME]/instances/instance1/config/OracleBIServerComponent/coreapplication_obis1 ]

Search for : "FMW_SECURITY_SERVICE_URL" in Conig XML. Verify the IP Address is mentioned is same as /etc/hosts file.

3. instanceconfig.xml file located at 
$FMW_HOME]/instances/instance1/config/OracleBIPresentationServicesComponent/coreapplication_obips1

Verify the IP Address is mentioned is same as /etc/hosts file.

Now Try to Restar the Servers.

Even though if its gives error as

"<Server failed to bind to the configured Admin port. The port may already be used by another process.>

Need to check which server is using port.


Linux :

netstat -an <port number>
or

netstat -anp | grep LISTEN | grep $portnumber


Identify the Process. Either stop the Process or Kill the Process to resolve this issue.

Error Staring Managed Server : cannot open file _WLS_BI_SERVER1000000.DAT

The persistent store "_WLS_bi_server1" encountered a fatal error, and it must be shut down: weblogic.store.PersistentStoreFatalException: [Store:280105]The persistent file store "_WLS_bi_server1" cannot open file _WLS_BI_SERVER1000000.DAT.

Error:
weblogic.store.PersistentStoreException: [Store:280105]The persistent file store "_WLS_bi_server1" cannot open file _WLS_BI_SERVER1000000.DAT.
        at weblogic.store.io.file.Heap.open(Heap.java:325)
        at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:104)
        at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:431)
        at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:422)
        at weblogic.store.admin.AdminHandler.activate(AdminHandler.java:126)

OR

 <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1306852872205> <BEA-320000> <The Diagnostics subsystem is initializing on Server wls_ods1.> 
<Info> <Store> <ojoid01> <wls_ods1> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <> <> <> <1306852872303> <BEA-280008> <Opening the persistent file store "WLS_DIAGNOSTICS" for recovery: directory=/mwhome/user_projects/domains/IDMDomain/servers/wls_ods1/data/store/diagnostics requestedWritePolicy="Disabled" fileLockingEnabled=true driver="wlfileio3".> 
 <Critical> <WebLogicServer> <ojoid01> <wls_ods1> <main> <> <> <> <1306852872315> <BEA-000386> <Server subsystem failed. 
Reason: 
java.lang.NullPointerException
java.lang.NullPointerException
  at weblogic.store.io.file.StoreFile.close(StoreFile.java:432)
  at weblogic.store.io.file.Heap.open(Heap.java:307)
  at weblogic.store.io.file.FileStoreIO.open(FileStoreIO.java:104)
  at weblogic.store.internal.PersistentStoreImpl.recoverStoreConnections(PersistentStoreImpl.java:413)
  at weblogic.store.internal.PersistentStoreImpl.open(PersistentStoreImpl.java:404)
  at weblogic.store.xa.PersistentStoreManagerXA.createFileStore(PersistentStoreManagerXA.java:118)
  at weblogic.diagnostics.archive.DiagnosticStoreRepository.getStore(DiagnosticStoreRepository.java:91)
  at weblogic.diagnostics.lifecycle.DiagnosticSystemService.start(DiagnosticSystemService.java:128)
  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
  at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
  at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)

OR

weblogic.diagnostics.lifecycle.DiagnosticComponentLifecycleException: weblogic.store.PersistentStoreException: [Store:280020]There was an error while reading from the log file
  at weblogic.diagnostics.lifecycle.ArchiveLifecycleImpl.initialize(ArchiveLifecycleImpl.java:44)
  at weblogic.diagnostics.lifecycle.DiagnosticFoundationService.start(DiagnosticFoundationService.java:107)
  at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)....
.........
Caused by: java.io.IOException: Error reading from file, No such file or directory, errno=2
  at weblogic.store.io.file.direct.DirectIONative.read(Native Method)
  at weblogic.store.io.file.direct.DirectFileChannel.read(DirectFileChannel.java:133)

  at weblogic.store.io.file.StoreFile.read(StoreFile.java:281)

Reason for Error:

The file $DOMAIN_HOME/servers/<ServerName>/data/store/diagnostics/WLS_DIAGNOSTICS000000.DAT is somehow corrupted.

The Archive component of the WebLogic Diagnostics Framework (WLDF) captures and persists all data events, log records, and metrics collected by WLDF from server instances and applications running on them and saves them into this file. So having this file corrupted prevents the server from writing the WLDF information, and hence it fails to start.

Solution:

Backup and remove the WLS_DIAGNOSTICS000000.DAT file, then restart the server: a new file will be created automatically.

This should not affect the server performance. It will only cause the loss of the archived diagnostic information (which is likely already lost since the file is corrupt).


Restart the Managed Server.



Oracle DoC ID: 

1. WebLogic Managed Servers Fail During Startup with NullPointerException on the Persistent File Store (Doc ID 1327538.1)
2.   WebLogic Server Diagnostics File is Corrupt or Locked (Doc ID 1059924.1)

Error Starting Managed Server in OBIEE - The persistent file store "BipJmsStore" cannot open file BIPJMSSTORE000000.DAT

Error Starting Managed Server in OBIEE - The persistent file store "BipJmsStore" cannot open file BIPJMSSTORE000000.DAT

Error:

The persistent store "BipJmsStore" encountered a fatal error, and it must be shut down: weblogic.store.PersistentStoreFatalException: [Store:280105]The persistent file store "BipJmsStore" cannot open file BIPJMSSTORE000000.DAT.


Reason For Error :

The above error is due to, 
1. The user who is starting the Server is not having permissions to open the file
2. Operating file system problem
3. File is corrupted.
4. In most cases, the managed server is not shutdown /closed properly. It may be killed in linux with kill -9 or CTRL+C.

NOTE : Renaming or removing the DAT file does not help resolve the issue.

Solution :

Create a new JMS store:
1. Login to the WLS console
2. Go to Services->Persistent Stores
3. Click on "Lock & Edit"
4. Click on New->CreateFileStore
5. Give the new store a name, select bi_server1 as the target and give it a Directory name (usually the same one as the store name). Make sure to create the directory first on the OS (under <DOMAIN_HOME>) and you only need to enter the name of the directory not the full path.
6. Click Ok
7. Activate the changes
8. Go to Services->Messaging->JMS Servers->BipJmsServer
9. Click on "Lock & Edit"
10. Select the new store you created as the persistent store
11. Save and activate the changes
12. Start the managed server.
If you want/need to keep the configuration on its original state you can remove the BipJmsStore and redo the procedure.

Refer the Oracle DOC ID 1571685.1

Error while restarting Manager Server in the Weblogic server instance

Error while restarting Manager Server in the Weblogic server instance

Error :
An error occurred while initializing the Embedded LDAP Server. The exception thrown is java.lang.ClassCastException: com.octetstring.vde.backend.BackendRoot cannot be cast to com.octetstring.vde.backend.standard.BackendStandard. This may indicate a problem with the data files for the Embedded LDAP Server. This managed server has a replica of the data contained on the Master Embedded LDAP Server in the Admin server. This replica has been marked invalid and will be refreshed on the next boot of the managed server. Retry the reboot of this server.


I got the above error while restarting the Managed Server  [ bi_Server1 ]. The Admin server was UP and RUNNING, but the we try to start Managed Server its starts but suddenly shut down with above mentioned error in bi_server1.log or bi_server.out files.


Solution :

Navigate to that server instance directory and browse inside that for the
OBIEE_Domain/domain-name/servers/server-name/data/ldap/ldapfiles directory path

You will get below listed files in that particular directory

-rw-r--r--   1 weblogic weblogic   79649      Sep 13  18:48 EmbeddedLDAP.data
-rw-r--r--   1 weblogic weblogic       0          Sep 13  18:48 EmbeddedLDAP.delete
-rw-r--r--   1 weblogic weblogic     648        Sep 13  18:48 EmbeddedLDAP.index
-rw-r--r--   1 weblogic weblogic       0          Sep 13  18:48 EmbeddedLDAP.lok
-rw-r--r--   1 weblogic weblogic   80126      Sep 13  18:48 EmbeddedLDAP.tran
-rw-r--r--   1 weblogic weblogic       8          Sep 13  18:48 EmbeddedLDAP.trpos

Just delete the below listed files inside the directory
-rw-r--r--   1 weblogic weblogic       0      Sep 13 18:48 EmbeddedLDAP.delete
-rw-r--r--   1 weblogic weblogic       0      Sep 13 18:48 EmbeddedLDAP.lok

Now restart the instance from the bin directory, this will get your Server up and running without issue.

Restart the Server

cd $OBIEE_DOMAIN/user_projects/domains/bifoundation_domain/bin

nohup ./startManagedWebLogic.sh bi_server1 http://hostname:7001 > managed_server1.log &

tail -f managed_server.log