Oracle Application Language installation

1. Check if there is enough disk space on the  system Extra disk space is required for each additional  languages.

4   GB of disk space is require in $APPL_TOP for  each additional language 10 GB of disk space is required in oradata for each additional language 

2. Active the new Language(s) using Oracle  Applications Manager

Login to http://$mt_hostname.$domainname:$port_prefix15 as sysadmin 

Select Site Map -> System Configuration: Licence  Manager -> Languages

Select all the Languages that are in list

Select Next -> Submit

3. Maintain Multilingual Tables and  compile objects

Login to MT host 

Run adadmin

Select 4. Maintain Applications Database Entities

Select 3. Maintain Multi-Lingual Tables

Once this has completed use adadmin to  Maintain Snapshot information:- 

Select 7. Return  to Main Menu

Select 2. Maintain Applicatiosn Files Menu

Select 5. Maintain snapshot information

Select 2. Update current view snapshot (Note: This step can take a while - approximately 2 hours on a  test system)

Select 7. Return to Main Applications Files Menu

Select 7. Return to Main Menu

Select 3. Compile Reload Applications  Database Entities menu

Select 3. Compile flexfields

4. Manifest file for NLS

1 Generate the Manifest File

 Pre-req patch : 5635729 (for latest adgennls.pl file)

Login to $mt_hostname as ap$cust_id

perl $AD_TOP/bin/adgennls.pl

This generates a manifest file in the $APPL_TOP/admin/$TWO_TASK directory

This file contains all the active lanaguages.

2 Upload the Manifest

Copy this manifest file to your PC.

Login to https://updates.oracle.com/TransSync with you Metalink username and password.

Use the Request a New Patch button to upload the correct file and press Submit.

Note: Also choose 'Get Latest Translations'

You should  receive an email to your oracle email account once the NLS patch is available - it usually takes 7 - 8 hours.

Note: If you do not receive an email with the confirmation for a completed patch you may want to check https://updates.oracle.com/TransSync periodically - once the patch is available it should be listed on this page. The requested patch can be listed as 'In Progress',  'Merged Translation' or 'Full Translation' so please verify this before downloading it to the customer mid tier. Some patches can take up to 2 days for creation.

3 Download NLS Patch and apply.

Once the patch is available go back to https://updates.oracle.com/TransSync and you will see your patch.

If you can access updates.oracle.com directly from the server you can ftp the patch directly to the server (use your Metalink username and password).

If you cannot access updates.oracle.com  - click on the patch to download it to your PC then upload it to the server and apply.

 

Thanks

Srinivas

R12.2 interview Q&A

1. What is Jinitiator in Oracle Apps?

2. Where is Jinitiator being used in Oracle Apps ?

3. Why OC4J replaced with WebLogic server 11g?

4. Why we are still using Oracle Apps server 10g R3(10.1.2.3) for Forms & Reports

5. Why we used Dual File system in R12.2 ?

Application Tier File System has changed in 12.2 to Dual File System to support ………. (answer this in comment) ?  Register here for Oracle Apps DBA 12.2 Training to learn more on Dual File System or Online Patching (ADOP).

6. How do we know Apps tier is using FS1 or FS2 (where FS1 and FS2 are two file system from Apps Dual File System in 12.2)?

7. FS1 or FS2 (dual file system) is independent to each other – TRUE / FALSE ?

8. What is role of Concurrent Manager ?

9. Why do Concurrent Manager Fail (some of the scenarios in which manager could fail) ?

10. What is Database Version that comes with EBS and Can we use any database version with EBS or are there any restrictions ?

11. What is the purpose of patching in Oracle Apps (E-Business Suite) and is it Compulsory to Patch (More Question on Patching on Day3 of Apps DBA Training) ?

Well these are just handful of hundreds of questions we answer either in online class or in support ticket (all our trainings comes with 1 Year support for any queries) or in our

To ask questions like these or learn more about Oracle Apps DBA in 30 Days, register for our Oracle Apps DBA (R12.2) Training

 

 

Thanks 

Srini

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)

Thanks
Srini

EBS R12.2 : add managed server oacore,oafm,forms,forms-c4ws

By default there is single Web Application Services in EBS 12.2

If you want to increase number of server either oacore, oafm, forms or forms-c4ws then below instruction need to follow. In below example we are adding one more oacore server.

To check current edition:
echo $FILE_EDITION

Follow below steps to add oacore services

Step 1: Take backup of $CONTEXT_FILE from both edition

Step 2: Run script on run edition:
[applmgr@ebs122 ~]$ perl $AD_TOP/patch/115/bin/adProvisionEBS.pl ebs-create-managedserver 
-contextfile=/apps01/applmgr/TEST/fs2/inst/apps/TEST_ebs122/appl/admin/TEST_ebs122.xml 
-managedsrvname=oacore_server2 -servicetype=oacore -managedsrvport=7203 -logfile=/tmp/oacore2.log
Enter the APPS Schema password:
Enter the WebLogic AdminServer password:

The logfile for this session is located at /tmp/oacore2.log

Check the logfile for any error message.

[applmgr@ebs122 ~]$ vi /tmp/oacore2.log

Step 3: Run autoconfig on run edition 

[applmgr@ebs122 ~]$ adautocfg.sh
Enter the APPS user password:
AutoConfig completed successfully.

Step 4: [applmgr@ebs122 ~]$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -ctxfile=$CONTEXT_FILE -outfile=/tmp/txkSetAppsConf.log
mod_wl_ohs.conf generated successfully

apps.conf generated successfully


Step 5: Stop/start http services on run edition
[applmgr@ebs122 ~]$ cd $ADMIN_SCRIPTS_HOME
[applmgr@ebs122 scripts]$ adapcctl.sh stop

You are running adapcctl.sh version 120.0.12020000.2

Stopping OPMN managed Oracle HTTP Server (OHS) instance ...
opmnctl stopproc: stopping opmn managed processes...

adapcctl.sh: exiting with status 0

[applmgr@ebs122 scripts]$ adapcctl.sh start

You are running adapcctl.sh version 120.0.12020000.2

Starting OPMN managed Oracle HTTP Server (OHS) instance ...
opmnctl start: opmn is already running.
opmnctl startproc: starting opmn managed processes...

adapcctl.sh: exiting with status 0


Now add oacore server info intoPATCH edition:

Step 6: Set patch edition env
[applmgr@ebs122 ~]$ echo $FILE_EDITION

patch

Step 7:

Start up the WebLogic Administration Server of the PATCH file system by executing the below command on the PATCH file system 

[applmgr@ebs122 scripts]$ adadminsrvctl.sh start forcepatchfs                   
You are running adadminsrvctl.sh version 120.10.12020000.2

Enter the WebLogic Admin password:
Enter the APPS Schema password:
Starting WLS Admin Server...
Refer /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/admin/log/adadminsrvctl.txt for details

adadminsrvctl.sh: exiting with status 0

adadminsrvctl.sh: check the logfile /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/admin/log/adadminsrvctl.txt for more information 

Step 8: From Run Addition execute below script with service name and port number

[applmgr@ebs122 scripts]$ perl $AD_TOP/patch/115/bin/adProvisionEBS.pl ebs-create-managedserver 
-contextfile=$CONTEXT_FILE -managedsrvname=oacore_server2 -servicetype=oacore -managedsrvport=7204 -logfile=\tmp\oacore2_2.log
Enter the APPS Schema password:
Enter the WebLogic AdminServer password:

Step 9: 
[applmgr@ebs122 scripts]$ perl $AD_TOP/bin/adSyncContext.pl 
-contextfile=/apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/appl/admin/TEST_ebs122.xml
Enter the APPS user password:
Enter the WebLogic AdminServer password:
The log file is /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/rgf/Sun_Jan_5_15_14_03_2014/adSyncContext.log

Step 10: 
Instantiate the fsclone_config.txt file on the PATCH file system of all Application tier nodes by running the following command after sourcing the RUN file system:

java oracle.apps.ad.autoconfig.InstantiateFile -e <PATCH_CONTEXT_FILE> -tmpl  \
<PATCH_AD_TOP>/admin/template/fsclone_config_txt.tmp -out  \
<PATCH_INST_TOP>/appl/admin/fsclone_config.txt
[applmgr@ebs122 scripts]$ java oracle.apps.ad.autoconfig.InstantiateFile -e /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/appl/admin/TEST_ebs122.xml -tmpl  /apps01/applmgr/TEST/fs1/EBSapps/appl/ad/12.0.0/admin/template/fsclone_config_txt.tmp -out  /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/appl/admin/fsclone_config.txt
Enter the APPS password : APPS

Step 11:
Execute below script from RUN file system
On the node containing the Oracle HTTP Server, execute the following script from the RUN file system, passing the context file from the PATCH file system. This will update the Oracle HTTP Server configuration files on the PATCH file system with the new managed server port number.

[applmgr@ebs122 scripts]$ perl $FND_TOP/patch/115/bin/txkSetAppsConf.pl -ctxfile=/apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/appl/admin/TEST_ebs122.xml \
> -outfile=/tmp/oacore2_3.log
mod_wl_ohs.conf generated successfully

apps.conf generated successfully

Step 12: Stop weblogic services from PATCH file system:
[applmgr@ebs122 scripts]$ adadminsrvctl.sh stop

You are running adadminsrvctl.sh version 120.10.12020000.2

Enter the WebLogic Admin password:
Enter the APPS Schema password:
Stopping WLS Admin Server...
.Refer /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/admin/log/adadminsrvctl.txt for details

adadminsrvctl.sh: exiting with status 0

adadminsrvctl.sh: check the logfile /apps01/applmgr/TEST/fs1/inst/apps/TEST_ebs122/logs/appl/admin/log/adadminsrvctl.txt for more information 

Step 13: Start newly added managed server from run edition:

admanagedsrvctl.sh start oacore_server2

Step 14: Check the status of server weblogic console:

Thanks 

Srini