RW-50015:
Error: – HTTP Listener is not responding. The service might not have started on
the port yet. Please check the service and use the retry button (Like This Error).
Checking Application status :-
=================================================================
[applmgr@apps14 scripts]$ ./adoacorectl.sh status
Processes in Instance: PROD_apps14.apps14.com 
-------------------+--------------------+---------+---------
ias-component | process-type | pid | status 
-------------------+--------------------+---------+---------
OC4J | oafm | 21168 | Alive 
OC4J | forms | 21078 | Alive 
OC4J | oacore | 20943 | Alive 
HTTP_Server | HTTP_Server | N/A | Down 
Cause:-
===============================================================
Due to missing library. /usr/lib/libdb.so.2
if you got this type of error then you can take a new terminal and Down the all application services and follow below steps.
Solution:=
================================================================
* Shut all application services.
* create the below link for library file
root ]# ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2
* Startup all application services. And press the Retry button
 
* Shut all application services.
* create the below link for library file
root ]# ln -s /usr/lib/libgdbm.so.2.0.0 /usr/lib/libdb.so.2
* Startup all application services. And press the Retry button
after  check the oacore status
applmgr@apps14
scripts]$ ./adoacorectl.sh status
You are
running adoacorectl.sh version 120.13
Checking
status of OPMN managed OACORE OC4J instance ...
Processes in
Instance: PROD_apps14.apps14.com
---------------------------------+--------------------+---------+---------
ias-component                    | process-type       |    
pid | status
---------------------------------+--------------------+---------+---------
OC4JGroup:default_group          | OC4J:oafm          |   
4024 | Alive
OC4JGroup:default_group          | OC4J:forms         |   
3946 | Alive
OC4JGroup:default_group          | OC4J:oacore        |   
3858 | Alive
 HTTP_Server                             | HTTP_Server        |   
3801 | Alive 
 
No comments:
Post a Comment