Error while launching forms on a SSL Enabled E-Biz applications 12.2

Installing Client JRE 1.8.0_25,1.7_76 or 1.7_75 for Server SSL Clients with Signed Jar Files results in New Untrusted Security Message

The issue could be because the server certificate is not having in the client machine  into the java store

server ssl set up into the java store on the client.

'The connection to this website is untrusted'
URL = https://company.com:443
The certificate is not valid

You can also find the above error while launching the forms.

Solution :

1. From the client, access: Control Panel->Java->Security-> Manage Certificates

2. User tab->Change drop down to 'Secure Site'

3. Import the server ssl certificate.  Not the code signing certificate, but the server user ssl certificate.

Reference Oracle Document:   1981654.1

These OPM-related update scripts were *not* intended to be included in the 12.2 upgrade driver.   These OPM table modifications are included in OPM Post-Upgrade steps.

In the u_merged.drv patch driver file, delete all references to the following files, and restart the adpatch session.

 GMFG5ITM.sql 

 GMFG5MCP.sql 

 GMFG6MEL.sql 

 GMFG6P00.sql 

 GMFG6P01.sql

 GMFG6P02.sql 

 GMFG6P03.sql 

 GMFG6P04.sql 

 GMFG6P05.sql 

 GMFG6P06.sql 

 GMFG6P07.sql 

 GMFG6P08.sql 

 GMFG6P09.sql 

 GMFG6P10.sql 

 GMFG6P11.sql 

 GMFG6P12.sql 

 GMFG6P14.sql 

 GMFG6P15.sql 

 GMFG6P16.sql 

 GMFG6P17.sql 

 GMFG6P18.sql 

 GMFG6P19.sql

uHalt all worker processes

uupdate $ORACLE_BASE/fs1/EBSapps/appl/au/12.0.0/patch/115/driver/u_merged.drv

uConfirm all adworker sessions are gone at the DB level

uRestart adpatch process

uPermanent Solution for 12.2 OPM Customers , oracle support released the pre-install patch "18688087"

uBug 18688087 - POOR PERFORMANCE ON GMFG6P03.SQL TASKS DURING 12.2 UPGRADE DRIVER

Manual method to add context file of FS1/FS2 File systems

FS_Clone or ADOP issues – basic check/Solution:

1) Before running fs_clone or any ADOP phases, we should make sure that there are three context files exists in FND_OAM_CONTEXT_FILES table. If not we have to run autoconfig on DB and Application nodes .

a. EXEC FND_CONC_CLONE.SETUP_CLEAN;

b. Run autoconfig on DB

c. Run autoconfig on App

Manual method to add context file of FS1/FS2 File systems :

$ADJVAPRG oracle.apps.ad.autoconfig.oam.CtxSynchronizer action=upload contextfile=/u01/oracle/appl/fs2/inst/apps/DEV_testdev/appl/admin/DEV_testdev.xml logfile=/tmp/patchctxupload.log

De-register a custom schema from the e-business suite

De-register a custom schema from the e-business suite

•Log on the Alert Manager responsibility and go to menu System/Installations , then delete the line     related to your custom schema.

•Log on the System Administrator responsibility , menu Security/Oracle/Register then delete the line

•related to your custom schema.

•Remove the relevant entry from the FND_OAM_CONTEXT_CUSTOM table and run AutoConfig on

• all nodes.

Custom top Impact with Online patching in E-Biz 12.2

Online Patching Issues : Custom Products registration in 12.2 

If you are an upgrade customer with a custom product top in the context file, but have not run AD Splice, you must:

1.Remove the relevant entry from the FND_OAM_CONTEXT_CUSTOM table.

2.Run AutoConfig on all nodes.

3.Apply the latest AD-TXK release update pack as needed.

4.Run AD Splice to add/register the custom product.

Points to be noted before creating a new custom product:

1) Custom production abbreviation should be less than 8 Characters.

2) Custom product should not have any "_" ( Underscore) in the name

3) Custom product should not start with Numeric value

4) Custom products should be registered with ad<name> 

5) Custom Products should not be registered using OAM, we should use adsplice.

         Eg:  Product name : Flex Interface 

                 We should create the name as FLEXINT

Note : With E-Business Suite 12.2.4 the possibility to use OAM for a Custom Product TOP has been removed. You need to use the adsplice Utility from the Command line to add your Custom Product TOP starting with EBS 12.2.4 and higher.


Related Oracle Note :1577707.1 

E-BUSINESS Suite 12.2 Important Logfile Locations

Few Logfile location on EBS R12.2.X


Admin server   -   $FMW_HOME/user_projects/domains/EBS_domain_$TWO_TASK/servers/AdminServer/logs/AdminServer.log

oacore logfile  -  $FMW_HOME/user_projects/domains/EBS_domain_$TWO_TASK/servers/oacore_server1/logs/oacore_server1.log

oacore out file  -  $FMW_HOME/user_projects/domains/EBS_domain_$TWO_TASK/servers/oacore_server1/logs/oacore_server1.out

oacore diagnostic log -  $FMW_HOME/user_projects/domains/EBS_domain_$TWO_TASK/servers/oacore_server1/logs/oacore_server1-diagnostic.log

oafm logfile -  $FMW_HOME/user_projects/domains/EBS_domain_$TWO_TASK/servers/oafm_server1/logs/oafm_server1.log

oafm outfile -  $FMW_HOME/user_projects/domains/EBS_domain_$TWO_TASK/servers/oafm_server1/logs/oafm_server1.out

oafm diagnostic log  - $FMW_HOME/user_projects/domains/EBS_domain_$TWO_TASK/servers/oafm_server1/logs/oafm_server1-diagnostic.log

form server log  - $FMW_HOME/user_projects/domains/EBS_domain_$TWO_TASK/servers/forms_server1/logs/forms_server1.log

form server access log  - $FMW_HOME/user_projects/domains/EBS_domain_$TWO_TASK/servers/forms_server1/logs/access.log

form server out file  - $FMW_HOME/user_projects/domains/EBS_domain_$TWO_TASK/servers/forms_server1/logs/forms_server1.out

form server diagnostic log  - $FMW_HOME/user_projects/domains/EBS_domain_$TWO_TASK/servers/forms_server1/logs/forms_server1-diagnostic.log

forms-c4ws_server1 log  - $FMW_HOME/user_projects/domains/EBS_domain_$TWO_TASK/servers/forms-c4ws_server1/logs/forms-c4ws_server1.log

forms-c4ws_server1 out file - $FMW_HOME/user_projects/domains/EBS_domain_$TWO_TASK/servers/forms-c4ws_server1/logs/forms-c4ws_server1.out

forms-c4ws_server1 diagnostic log  -  $FMW_HOME/user_projects/domains/EBS_domain_$TWO_TASK/servers/forms-c4ws_server1/logs/forms-c4ws_server1-diagnostic.log

Concurrent Managers Do Not Start

After Doing a Clone All the Concurrent Managers Do Not Start

In Oracle Application Release 11i and R12, after performing a clone when attempting to start the concurrent managers in the target instance using the command below:

sh adcmctl.sh stop apps/<Appspassword> under $COMMON_TOP/admin/scripts  - 11i

sh adcmctl.sh stop apps/<Appspassword> under $ADMIN_SCRIPTS_HOME       - R12

Errors can be found in ICM logfile :

Could not initialize the Service Manager FNDSM__. Verify that has been registered for concurrent processing.

Routine AFPEIM encountered an error while starting concurrent manager PASMGR with library /oasa/oracle/oasaappl/pa/11.5.0/bin/PALIBR.

Check that your system has enough resources to start a concurrent manager process. Contact your system administrator to  : 22-FEB-2012 18:24:41

Starting PASMGR Concurrent Manager                 : 22-FEB-2012 18:24:41

Could not initialize the Service Manager FNDSM_oatest_OASA. Verify that oasa has been registered for concurrent processing.

Routine AFPEIM encountered an error while starting concurrent manager PASMGR with library /oasa/oracle/oasaappl/pa/11.5.0/bin/PALIBR.

Check that your system has enough resources to start a concurrent manager process. Contact your system administrator to  : 22-FEB-2012 18:24:41

                     Process monitor session ended : 22-FEB-2012 18:24:41

==========

Cause

The issued was found to have been caused by the FND_NODES table having incorrect node entries (old node from the source instance) and that no Service Manager was found for the existing node.

Solution

1. Stop all middle tier services including the concurrent managers.

2. Stop the database.

3. Start the database.

4. Connect SQLPLUS as APPS user and run the following:

EXEC FND_CONC_CLONE.SETUP_CLEAN;
COMMIT;
EXIT;

=========================
NOTE:260887.1 – Steps to Clean Nonexistent Nodes or IP Addresses from FND_NODES
=========================

( Note : In the case of a clone instance, it is strongly recommended to clean the non-existing nodes )

5. Run AutoConfig on all tiers, first on the DB tier and then the APPS tiers , webtiers to repopulate the required system tables.

6. Connect to SQLPLUS as APPS user and run the following statement:

$sqlplus  apps/<Appspassword>

select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like ‘FNDSM%';

If the above SQL does not returning any rows/value then please do the following:

Go to $FND_TOP/patch/115/sql

Connect SQLPLUS as APPS user and run the following script :

SQL> @afdcm037.sql;

=========================
NOTE:218893.1 – How to Create The Service Manager ‘FNDSM’ on Oracle Applications
=========================

(Note : The same “afdcm037.sql” is used for Release 12 also ).

This script will create libraries for FNDSM and create managers for preexisting nodes.

Check again that FNDSM entries now exist:

select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like ‘FNDSM%';

7. Go to cd $FND_TOP/bin
$ adrelink.sh force=y “fnd FNDLIBR”
$ adrelink.sh force=y “fnd FNDSM”
$ adrelink.sh force=y “fnd FNDFS”
$ adrelink.sh force=y “fnd FNDCRM”

8. Run the CMCLEAN.SQL script from the referenced note below (don’t forget to commit).

=========================
NOTE:134007.1 – CMCLEAN.SQL – Non Destructive Script to Clean Concurrent Manager Tables
=========================

9. Start the middle tier services including your concurrent manager.

10. Retest the issue.