Oracle E-Business Suite – R12.2 Post Install checks (HTTP, Help Page, Login Page, JSP) got failed

This post is from our Oracle Apps DBA (R12.2) Training for E-Business Suite  (In which we cover Architecture, Installation, File System, WebLogic Concepts, Patching, Cloning , Common Tasks and difference in 12.2 from previous version, Register here for Oracle Apps DBA 12.2 Training )

One of the trainee from our current batch, having an issue in Oracle E-Business Suite R12.2 (EBS) installation where some of the post-install checks (Help Page, Login Page, JSP, HTTP, Virtual Directorywas failed as shown below:

post_install_checks_failed

Click on X symbol, to know the error message for the issue as here I clicked on  X symbol beside HTTP and it display, below window with error message

error_message

After that I checked in EBS Installation logs /u01/oracle/PROD/fs1/inst/apps/PROD_iamdemo07/logs/08261229.log for the root cause of the issue and below are the error messages:

RW-50015: Error: – Http Server Virtual Directories is not responding. The service might not have started on the port yet. Please check the service and use the retry button.

JSP

—-

checking URL = http://<hostname>:8088/OA_HTML/jtfTestCookie.jsp

RW-50015: Error: – JSP is not responding. The service might not have started on the port yet. Please check the service and use the retry button.

Login Page

———–

RW-50015: Error: – Login Page is not responding. The service might not have started on the port yet. Please check the service and use the retry button.

WLS Domain Validation

———————

EBS Domain validation failed for RUN filesystem.

————————————————–

Check Domain deployment logs and re-deploy the RUN domain.

————————————————————

Log file at : /u01/oracle/PRD12288/fs1/EBSapps/appl/admin/PROD_iamdemo07/log .

——————————————————————————-

EBS Domain validation failed for PATCH filesystem.

————————————————-

Check Domain deployment logs and re-deploy the PATCH domain.

Log file at : /u01/oracle/PRD12288/fs2/EBSapps/appl/admin/PROD_iamdemo07/log .

Connecting AdminServer

======================

Connecting to t3://<hostname>:7090 with userid weblogic …

This Exception occurred at Thu Aug 27 05:03:07 BST 2015.

javax.naming.CommunicationException [Root exception is java.net.ConnectException: t3://<hostname>:7090: Destination unreachable; nested exception is:

 java.net.ConnectException: Connection refused; No available router to destination]

Error while connecting Admin Server !!!

Exiting WebLogic Scripting Tool.

.end std out.

.end err out.

ERROR: Unable to add the loggers for oacore application

ERROR: Failed to create the EBS domain.

Failed to deploy the E-Business Suite domain

 Then I came to know that EBS domain was not created and deployed successfully and When  I checked on AdminServer log file /u01/oracle/PROD55/fs1/FMW_Home/user_projects/domains/EBS_domain_PROD55/servers/AdminServer/logs

It was showing below error message:

Caused By: java.io.FileNotFoundException: /tmp/.ovdlock.tmp (Permission denied)
at java.io.RandomAccessFile.open(Native Method)
at java.io.RandomAccessFile.<init>(RandomAccessFile.java:233)
at oracle.ods.virtualization.config.ConfigureAdapters.configure(ConfigureAdapters.java:512)
at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.pushLdapNamesTolibOvd

(OvdIGFServiceProvider.java:312)
at oracle.security.jps.internal.igf.ovd.OvdIGFServiceProvider.prepareDataPush2libOvd

(OvdIGFServiceProvider.java:370)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider$NoLibOvd.getInstance

(LdapIdentityStoreProvider.java:339)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance

(LdapIdentityStoreProvider.java:118)
at oracle.security.jps.internal.idstore.ldap.LdapIdentityStoreProvider.getInstance

(LdapIdentityStoreProvider.java:74)
at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.findServiceInstance

(ContextFactoryImpl.java:139)
at oracle.security.jps.internal.core.runtime.ContextFactoryImpl.getContext

(ContextFactoryImpl.java:170) 

Fix for this issue:

1. As /tmp/.ovdlock.tmp was not having permission Installation failed. So we have change the permission to 777 with below command:

chmod -R 777 /tmp/.ovdlock.tmp

2. Another is to run the adProvision.pl script which is located under $AD_TOP/patch/115/bin and delete failed EBS domain as

perl adProvisionEBS.pl ebs-delete-tech -contextfile=/u01/oracle/PROD55/fs1/inst/apps/PROD55_iamdemo07/

appl/admin/PROD55_iamdemo07.xml -techtype=wls

3. Then again run the adProvision.pl script which is located under $AD_TOP/patch/115/bin on both file system (RUN and Patch) and Create EBS domain as

a) Run adProvision.pl script on RUN file system (fs1)

perl adProvisionEBS.pl ebs-deploy-alltech -contextfile=/u01/oracle/PROD55/fs1/inst/apps/PROD55_iamdemo07/appl/

admin/PROD55_iamdemo07.xml 

You should see below output:

NMProcess: <Aug 19, 2015 2:22:57 PM> <INFO> <EBS_domain_PROD55> <AdminServer> <Rotated server output log to “/u01/oracle/PROD55/fs1/FMW_Home/user_projects/domains/EBS_domain_PROD55/

servers/AdminServer/logs/AdminServer.out00001″>
NMProcess: Aug 19, 2015 2:22:57 PM weblogic.nodemanager.server.LogFileRotationUtil log
NMProcess: INFO: Rotated server output log to “/u01/oracle/PROD55/fs1/FMW_Home/user_projects/domains/EBS_domain_PROD55/

servers/AdminServer/logs/AdminServer.out00001″
NMProcess: <Aug 19, 2015 2:22:57 PM> <INFO> <EBS_domain_PROD55> <AdminServer> <Server error log also redirected to server log>
NMProcess: Aug 19, 2015 2:22:57 PM weblogic.nodemanager.server.LogFileRotationUtil log
NMProcess: INFO: Server error log also redirected to server log
NMProcess: <Aug 19, 2015 2:22:57 PM> <INFO> <EBS_domain_PROD55> <AdminServer> <Server output log file is ‘/u01/oracle/PROD55/fs1/FMW_Home/user_projects/domains/EBS_domain_PROD55/servers/AdminServer/logs/AdminServer.out’>
NMProcess: Aug 19, 2015 2:22:57 PM weblogic.nodemanager.server.AbstractServerManager log
NMProcess: INFO: Server output log file is ‘/u01/oracle/PROD55/fs1/FMW_Home/user_projects/domains/

EBS_domain_PROD55/servers/AdminServer/logs/AdminServer.out’
Creation and deployment of E-Business Suite domain completed..
<Aug 19, 2015 2:30:18 PM BST> <Warning> <JNDI> <BEA-050001> <WLContext.close() was called in a different thread than the one in which it was created.>

b) Run adProvision.pl script on Patch file system (fs2)

perl adProvisionEBS.pl ebs-deploy-alltech -contextfile=/u01/oracle/PROD55/fs2/inst/apps/PROD55_iamdemo07/appl/

admin/PROD55_iamdemo07.xml 

4. Start All EBS services as

cd $ADMIN_SCRIPTS_HOME

./adstrall.sh <apps_username>/<apps_password>

You should see below output:

All enabled services for this node are started.

adstrtal.sh: Exiting with status 0

adstrtal.sh: check the logfile /u01/oracle/PROD55/fs1/inst/apps/PROD55_iamdemo07/logs/appl/admin/log/adstrtal.log for more information …

This will create complete domain and managed servers.

After that, clicked on Retry button and all Post Install checks passed but one post install check “WLS Domain Validation” have warning message so we can ignore this and proceed further without having any issue as EBS Domain was successfully completed.

WLS_Check_Failed

Now Oracle E-Business Suite R12.2 Installation completed successfully.

Access the EBS URL: http://hostname:port

If you want to learn more about Oracle Apps DBA (Architecture, Installation, WebLogic, Patching, Cloning and other maintenance tasks with the upgrade of Oracle E-Business Suite 12.2.0 to 12.2.4) then have a look at our Oracle Apps DBA (R12.2) Training.

Note: We are so confident on our workshops that we provide 100% Money back guarantee, in unlikely case of you being not happy after 2 sessions, just drop us a mail before third session and We’ll refund FULL money (or ask us from our 100s of happy trainees in our private Facebook Group)

Share This Post with Your Friends over Social Media!

About the Author SeemaYadav

Oracle Consultant at K21 Technologies - Oracle Gold Partner specialising in Design, Implement, and Support.

Leave a Comment:

[1Z0-932]
[1Z0-932]
[index]
[index]
[523.251,1046.50]
[523.251,1046.50]
[523.251,1046.50]
[523.251,1046.50]
[index]
[index]
[523.251,1046.50]
[523.251,1046.50]
[523.251,1046.50]
[523.251,1046.50]