Custom Application in Oracle EBS R12.2

Creating a Custom Application in Oracle E-Business Suite Release 12.2 (Doc ID 1577707.1)

Developing and Deploying Customizations in Oracle E-Business Suite Release 12.2 (Doc ID 1577661.1)

Oracle EBS 12.2.4 application tier autoconfig fails after database upgrade from 11.2.0.3 to 11.2.0.4

Problem

Oracle EBS 12,2,4 application tier autoconfig fails with following error.

WARNING: [AutoConfig Error Report]
The following report lists errors AutoConfig encountered during each
phase of its execution.  Errors are grouped by directory and phase.
The report format is:
      <filename>  <phase>  <return code where appropriate>

  [PROFILE PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /u01/CRP/fs1/inst/apps/CRP_oracle/admin/install
      jtfictx.sh              INSTE8_PRF         1

AutoConfig is exiting with status 1

Cause

DECLARE
*
ERROR at line 1:
ORA-20000: Oracle Text error:
DRG-50857: oracle error in drixmd.GetIndexRec
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at "CTXSYS.DRUE", line 160
ORA-06512: at "CTXSYS.CTX_DDL", line 948
ORA-06512: at "CTXSYS.AD_CTX_DDL", line 336
ORA-06512: at line 96



Solution
connect /as sysdba

ALTER SESSION SET CURRENT_SCHEMA=SYS;
grant select on SYS.DBA_PROCEDURES to ctxsys;

ALTER SESSION SET CURRENT_SCHEMA=CTXSYS;
SET PAGESIZE 0
SELECT 'Calling ctx/admin/driacc.plb on ' || SYSTIMESTAMP FROM dual;
SET PAGESIZE 10

@@?/ctx/admin/driacc.plb;

@$ORACLE_HOME/rdbms/admin/utlrp.sql

set serveroutput on
execute sys.validate_context;

select comp_name, status, substr(version,1,10) as version from dba_registry where comp_id = 'CONTEXT';

Reference
 Can Not Validate CTXSYS.DRIACC Package (Doc ID 1906873.1)

Oracle EBS R12 JSP Compilation Issue Resolution

Modify the value of "s_apctimeout" to -1 in the apps tier $CONTEXT_FILE which means indefinite wait.

Then Execute the autoconfig on application tier.

Then recompile the JSP again.

EBS R12.2 ADOP Patching & Issues

ADOP Patching Cycle

# Prepare for patching:
$ adop phase=prepare

# Apply patches:
$ adop phase=apply patches=<patch number>

# Finalize patch application:
$ adop phase=finalize

# Perform cutover:
$ adop phase=cutover

$ . <EBS_ROOT>/EBSapps.env run

These steps are performed post-cutover.
$ perl <AD_TOP>/bin/admkappsutil.pl

This will create the appsutil.zip file in <INST_TOP>/admin/out.

On the database tier, as the oracle user:

Copy or ftp the appsutil.zip file to the RDBMS_ORACLE_HOME, 

then run the following commands:

$ cd <RDBMS_ORACLE_HOME>
$ unzip -o appsutil.zip

Run AutoConfig on the database tier.

Run AutoConfig on the run file system of each application tier node.

Start the application tier services. 

# Perform cleanup:
$ adop phase=cleanup

$ adop phase=fs_clone 

ADOP Important queries 

select ADOP_SESSION_ID,PREPARE_STATUS,APPLY_STATUS,
FINALIZE_STATUS,CUTOVER_STATUS,CLEANUP_STATUS,
ABORT_STATUS,STATUS,ABANDON_FLAG,NODE_NAME 
from AD_ADOP_SESSIONS order by ADOP_SESSION_ID;

Note: STATUS
N - Not Applied In the current node but applied in other nodes
R - Patch Application is going on.
H - Patch failed in the middle. (Hard Failure)
F - Patch failed in the middle but user tried to skip some failures.
S - Patch Application succeeded after skipping the failed jobs.
Y - Patch Application succeeded.
C - Reserved for clone and config_clone. Indicates clone completed 

select ADOP_SESSION_ID, BUG_NUMBER, STATUS, 
APPLIED_FILE_SYSTEM_BASE, PATCH_FILE_SYSTEM_BASE, 
ADPATCH_OPTIONS, NODE_NAME, END_DATE, CLONE_STATUS
from ad_adop_session_patches
order by end_date desc; 

ADOP Patching Issues

Issue :

Error while running command: adop phase=prepare

ERROR at line 1:

ORA-20008: No Concurrent Manager is defined that can run concurrent program

ADZDPATCH

ORA-6512: at "APPS.AD_ZD_ADOP", line 240

Solution:

FNDLOAD
 apps/apps 0 Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct 
$AD_TOP/patch/115/import/US/adzdpatch.ldt - CUSTOM_MODE=FORCE 

Oracle EBS Important Profile Options

ICX: Limit Time
Determines the maximum number of hours a user can be logged on per session.

ICX:Session Timeout
Determines the length of time (in minutes) of inactivity in a user's form session before the session is disabled.

"ICX: Limit Time" is used to control the total time a session can be logged in, regardless of what activity is being done.
It is always assigned to higher value than "ICX: Session Timeout".

Configure Oracle EBS R12 with RAC

Using Oracle 12c Release 1 Real Application Clusters with Oracle E-Business Suite Release 12 (Doc ID 1490850.1)
Using Oracle Real Application Clusters 11g Release 2 with Oracle E-Business Suite Release 12 (Doc ID 823587.1)