Tuesday, September 29, 2015

12.2 oacore managed server starts in ADMIN mode - java.lang.ClassNotFoundException

Issue:

EBS 12.2 Application services are bounced as part of regular maintenance. During startup oacore_server1 Managed server started in ADMIN mode rather than RUNNING mode.

Below are the errors found in oacore_server1.log file.

Caused By: java.lang.ClassNotFoundException: oracle.apps.bne.integrator.document.ooxml.BneCreateDocumentService

Solution:

web.xml has some how updated with incorrect values for servlet class.

At Line 341 of file
$FMW_HOME/Oracle_EBS-app1/applications/oacore/html/WEB-INF/web.xml Below is the found value:


<servlet-class>oracle.apps.bne.integrator.document.ooxml.BneCreateDocumentService</servlet-class>

Update the value with below change:
<servlet-class>oracle.apps.fnd.txk.util.TXKSubstituteProductServlet</servlet-class>

Save changes and bounce oacore_server1 managed server.

Tuesday, September 1, 2015

fs_clone failed during adopValidations

Issue

Found the below errors in  the adop validation file.. adopValidations_detailed.log under $ADOP_LOG_DIR/3/fs_clone_XXX/ 

-----------------------------
ERROR: The following required ports are in use:
-----------------------------
7812 : Managed Server Port 11
7412 : Managed Server Port 7
7612 : Managed Server Port 5
7212 : Managed Server Port 3
Corrective Action: Free the listed ports and retry the adop operation.

Completed execution : ADOPValidations.java

Found that Patch Context File in Database has incorrect port number for Admin Servers, Managed ports.

Fix:

Updated the correct ports in context file and uploaded context file to database.


$ADJVAPRG oracle.apps.ad.autoconfig.oam.CtxSynchronizer action=upload  contextfile=<Path of Context File> logfile=/tmp/patchctxupload15.log
 

Data not Loading on Endeca application pages

Data not Loading on Endeca application pages


Performed fresh Endeca setup on already existing setup, But after the setup is completed below are the few issues identified
1)     Data is not loaded on Endeca pages, only layout is displayed.
2)     Pages related to information Discovery like datasources,framework settings,etc., in Endeca Studio under Control Panel is showing blank
3)     Formatting of Endeca page is not correct

StudioManagedServer.log file showed below errors:
"53808" Local Address: "/192.168.1.1" Local Port: "8004" Protocol: "http">
####<Jul 6, 2015 6:26:26 AM CDT> <Error> <HTTP> <endeca.oracle.com> <StudioManagedServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1436181986656> <BEA-101019> <[ServletContext@992134090[app:studio-portal module:/endeca-datasource-config-portlet/ path:/endeca-datasource-config-portlet spec-version:2.5]] Servlet failed with IOException
java.io.FileNotFoundException: /tmp/liferay/minifier/endeca-datasource-config-portlet/js/DatasourceWindow.js_Q_browserId=ie&minifierType=js&languageId=en_US&t=1436178201000_E_CONTENT_TYPE (Permission denied)


Fix:
1)     Provide permissions to Endeca Unix owner on /tmp
2)     Restart Endeca Services

Endeca Extension HTTP-404 Page not found

Issue – HTTP-404 Page not found


User is trying to navigate to Endeca pages and receives http-404 page not found error. Below is the screenshot.
















Fix:
Verify the  profile option FND_ENDECA_PORTAL_URL and make sure it is correctly set.

Endeca Extensions There was an error when trying to access the data source

Issue 1- Datasource Error


There was an error when trying to access the data source. Please confirm with your system administrator that the data source is available.
Below error is observed on Endeca Pages when a clone of EBS Instance is completed.















  Below are the few causes for the issue:
1)      The source EBS may not have Endeca application configured.
2)      Not executed Concurrent program “Populate Endeca Metadata for iProcurement” after any metadata changes performed on Endeca side <-- This is specific to iProcurment page
3)      Endeca data source ebsdb is not listing target managed servers
Launch Console of Endeca Server -> Datasources -> click on datasource ebsdb ->  Monitoring -> Testing. This screen should list the Studio Managed server.



Studio log file reported below errors: (/u01/Oracle/Middleware/user_projects/domains/endeca_domain/servers/StudioManagedServer/logs/StudioManagedServer.log)
####<Jun 8, 2015 10:18:46 PM CDT> <Error> <Deployer> <hpeidrd01.hpinc.com> <StudioManagedServer> <[ACTIVE] ExecuteThread: '17' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <0000KrMKwR45yW^5xVWByW1LT_gK000000> <1433819926781> <BEA-149205> <Failed to initialize the application 'ebsdb' due to error weblogic.application.ModuleException: .
weblogic.application.ModuleException:
        at weblogic.jdbc.module.JDBCModule.prepare(JDBCModule.java:327)
Caused By: weblogic.common.resourcepool.ResourceSystemException:
 Could not connect to 'oracle.apps.fnd.ext.jdbc.datasource.AppsDataSource'.

 The returned message is: ORA-01017: invalid username/password; logon denied

 It is likely that the login or password is not valid.
 It is also possible that something else is invalid in
 the configuration or that the database is not available.
        at weblogic.jdbc.common.internal.JDBCUtil.parseException(JDBCUtil.java:301)
        at weblogic.jdbc.common.internal.PooledConnectionEnvFactory.makeConnection(PooledConnectionEnvFactory.java:317)
        at weblogic.jdbc.common.internal.PooledConnectionEnvFactory.createResource(PooledConnectionEnvFactory.java:97)
        at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1310)

Fix:
The password of EBS User ENDECADM in console is incorrect. Update the correct password for user ENDECADM in console to correct value and save it.
Console -> Lock & Edit in change center -> Datasource -> click on ebsdb -> configuration -> Connection Pool.
Update the password to correct value  and click on Save.
Activate Changes on control center

Once the changes are activated we should be able to see the Managed Server.