Autoconfig post 12C upgrade from 11g failed with "ORA-01804: failure to initialize timezone information"

Autoconfig post 12C upgrade from 11g failed with "ORA-01804: failure to initialize timezone information"

Error

DB Autoconfig failed with below error:

[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: /s01/app/oracle/db_tech_st/12.1.0.2/appsutil/TEST1_linx32
      afdbprf.sh              INSTE8_PRF         1

  [APPLY PHASE]
  AutoConfig could not successfully execute the following scripts:
    Directory: /s01/app/oracle/db_tech_st/12.1.0.2/appsutil/TEST1_linx32
      adcrobj.sh              INSTE8_APPLY       1

AutoConfig is exiting with status 2


afdbprf.sh started at Sun Jun 10 00:00:26 EDT 2018


The environment settings are as follows ...

       ORACLE_HOME : /u01/app/orad1i/db/tech_st/12.1.0.2
        ORACLE_SID : TEST1

Executable : /u01/app/orad1i/db/tech_st/12.1.0.2/bin/sqlplus

ERROR:

ORA-01804: failure to initialize timezone information

Cause

It is not able to find the TimeZone parameter  value in the specified path

[oracle@linx32  ~]$ echo $ORA_TZFILE
/u01/app/orad1i/db/tech_st/12.1.0.2/oracore/zoneinfo/timezlrg.dat

[oracle@linx32 ~]$ ls -ltr /u01/app/orad1i/db/tech_st/12.1.0.2/oracore/zoneinfo/timezlrg.dat

ls: cannot access /u01/app/orad1i/db/tech_st/12.1.0.2/oracore/zoneinfo/timezlrg.dat.: No such file or directory

Solution

Create a soft link to existing Time zone file

oracle@linx32 ~]$ cd /u01/app/orad1i/db/tech_st/12.1.0.2/oracore/zoneinfo

[oracle@linx32 ~] ln -s timezlrg_25.dat timezlrg.dat

[orad1i@nchlamsdb01 zoneinfo]$ ls -ltr timezlrg.dat

lrwxrwxrwx 1 oracle dba 11 Jun 11 10:24 timezlrg.dat -> timezlrg_25.dat

Re-run  Autoconfig, it shoud work.

Enable/Add new langauge in Oracle Apps R12

1. Check the Character set whether new language you are enabling is supporing or not? Refer Note Note 393861.1

2. Activate new language from License Manager from Oracle Application Manager

3. Check from the tables, new language is activated or not?

SQL> select NLS_LANGUAGE from FND_LANGUAGES where INSTALLED_FLAG in ('B','I');

NLS_LANGUAGE
------------------------------
AMERICAN
SPANISH
FRENCH

4. Run Maintain Multi-lingual Tables from Adadmin

5. Run Maintain Snapshot information from Adadmin

6. Run the Translation Synchronization Patch utility (adgennls.pl) using below command

perl $AD_TOP/bin/adgennls.pl

The manifest generated from the tool is located at : $APPL_TOP/admin/$TWO_TASK/out/adgennls.txt

7. After you generate your manifest, you can go to http://updates.oracle.com/TransSync (use your My Oracle Support username and password).
   Follow the instructions on the screen to upload the manifest file. A Translation synchronization patch will be generated specifically based    on your manifest for each of your active language. The patch will synchronize the language file versions and American English file versions    in your Applications instance.

8. Install the Release 12 NLS Help for the new language (optional)

Known issues
-------------

+ Performance Issue with Maintain Multilingual Tables EGONLINS.sql And INVNLINS.sql Taking Long Time (Doc ID 1391050.1)
+ Performance Issues Using Maintain Multi-Lingual Table, INVNLINS.SQL (Doc ID 981868.1)
+ Bug 12922572 : WHEN RUNNING MAINTAIN MULTILINGUAL TABLES, EGONLINS AND INVNLINS TAKE MORE 24 HR

Oracle DST upgrade procedure from V14 to V25

DST upgrade procedure from V14 to V25

1. Check the invalid count before upgrade

select count(1) from dba_objects where status='INVALID';

2. Check the Tz version before upgrade.

SQL> SELECT version FROM v$timezone_file;

   VERSION
---------------
14

3. Bringdown apps services and Database and listerner

$ADMIN_SCRIPTS_HOME/adstpall.sh apps/apps

sqlplus '/ as sysdba'
shut immediate
lsnrctl stop TEST2

4. Set the inventory

cat /etc/oraInst.loc
inventory_loc=/etc/oracle/oraInventory
inst_group=dba

5. Verify the inventory

$ORACLE_HOME/OPatch/opatch lsinventory

6.Apply DST25 Patch

cd /stageall/patches/DST/22037014
$ORACLE_HOME/OPatch/opatch apply

7.Verify patch applied or not?

$ORACLE_HOME/OPatch/opatch lsinventory | grep 22037014

8.Post steps of DST  patch

Download scripts from Note: 1585343.1

cd /stagall/patches/DST/DBMS_DST_scriptsV1.9

Conn / as sysdba
spool countstatsTSTZ.log
@countstatsTSTZ.sql
spool off

Conn / as sysdba
spool upg_tzv_check.log
@upg_tzv_check.sql
spool off

Conn / as sysdba
spool upg_tzv_apply.log
@upg_tzv_apply.sql
spool off

9.Verify DST version post upgrade

SQL> SELECT version FROM v$timezone_file;

VERSION
--------------
25

10.Verify invalid objects

select count(1) from dba_objects where status='INVALID';

11. Bring up services, validate the environment and release
------------------------------------------------------------
sqlplus ' /as sysdba'
startup
exit
lsnrctl start TEST2


$ADMIN_SCRIPTS_HOME/adstrtal.sh apps/apps


Ref Note : Scripts to automatically update the RDBMS DST (timezone) version in an 11gR2 or 12cR1 database . (Doc ID 1585343.1)

Adrelink Failed on FNDLOAD With Error: /usr/lib/gcc/x86_64-redhat-linux/4.4.7/32/libgcc_s.so: undefined reference to `__stack_chk_fail@GLIBC_2.4'

Adrelink Failed on FNDLOAD With Error: /usr/lib/gcc/x86_64-redhat-linux/4.4.7/32/libgcc_s.so: undefined reference to `__stack_chk_fail@GLIBC_2.4'

adrelink fails with beow error

-lcommon10 -lgeneric10  -lcore10 -lxml10 -lunls10 -lsnls10 -lnls10 -lcore10
-lnls10 -lclient10 -lnnetd10 -lvsn10 -lcommon10 -lgeneric10 -lcore10
-lxml10 -lunls10 -lsnls10 -lnls10 -lcore10 -lnls10  `cat
/PRD1/app//PROD/apps/tech_st/10.1.2/lib/sysliblist` -ldl -lm -lpthread
/usr/lib/gcc/x86_64-redhat-linux/4.4.7/32/libgcc_s.so: undefined reference to
`__stack_chk_fail@GLIBC_2.4'
collect2: ld returned 1 exit status
make: *** [/PRD1/app//PROD/apps/apps_st/appl/fnd/12.0.0/bin/FNDLOAD]
Error 1
Done with link of fnd executable 'FNDLOAD' on Sat Nov 5 19:59:20 EDT 2016

Relink of module "FNDLOAD" failed.
See error messages above (also recorded in log file) for possible
reasons for the failure. Also, please check that the Unix userid
running adrelink has read, write, and execute permissions

Solution:

pdate AS 10g (10.1.2 and 10.1.3) Oracle Homes (Oracle Linux 6, RHEL 6, Oracle Linux 7 and RHEL 7 only)

After installation, users must update the stub libraries in the 10.1.2 and 10.1.3 Oracle Homes using Patch 12415211.  In following the instructions below, please note that Opatch should not be used to install this patch.

Users must specifically copy the files in the patch to the specified directories as follows for the 10.1.2 Oracle Home:

$ cd <12.1_INSTALL_DIR>/apps/tech_st/10.1.2/lib
$ cp -p -R stubs stubsORIG
$ cd stubs
$ cp <PATCH_INSTALL_DIR>/12415211/files/lib/stubs/libgcc_s-2.3.2-stub.so .
$ ln -s libgcc_s-2.3.2-stub.so libgcc_s.so.1
$ ln -s libgcc_s.so.1 libgcc_s.so
After this is done and sourcing the APPS<CONTEXT_NAME>.env file, users should relink all 10.1.2 executables by running the $ORACLE_HOME/appsutil/clone/adlnktools.sh script and ensuring that there are now no errors in the make log file output from the script.

The instructions for the 10.1.3 Oracle Home are:

$ cd <12.1_INSTALL_DIR>/apps/tech_st/10.1.3/lib
$ cp -p -R stubs stubsORIG
$ cd stubs
$ cp <PATCH_INSTALL_DIR>/12415211/files/lib/stubs/libgcc_s-2.3.2-stub.so .
$ ln -s libgcc_s-2.3.2-stub.so libgcc_s.so.1
$ ln -s libgcc_s.so.1 libgcc_s.so
$IAS_ORACLE_HOME/appsutil/clone/adlnkweboh.sh

Reference Note:

Target CLONE Instance: Adrelink Failed on FNDLIBR With Error: /usr/lib/gcc/x86_64-redhat-linux/4.4.7/32/libgcc_s.so: undefined reference to `__stack_chk_fail@GLIBC_2.4' (Doc ID 2057857.1)

Adrelink Fails With Error tech_st/10.1.2/lib/stubs/libc.so.6 collect2: ld returned 1 exit status

Adrelink Fails With Error tech_st/10.1.2/lib/stubs/libc.so.6 collect2: ld returned 1 exit status

/u01/app/applmgr/TST123/apps/tech_st/10.1.2/lib/sysliblist` -ldl -lm

-lpthread

/usr/bin/ld: cannot find /u01/prod/apps/tech_st/10.1.2/lib/stubs/libc.so.6

collect2: ld returned 1 exit status

make: *** [/u01/app/applmgr/TST123/apps/apps_st/appl/ad/12.0.0/bin/adpchnew]

Error 1

Done with link of ad executable 'adpchnew' on Thu Oct 27 22:11:12 EDT 2016

Relink of module "adpchnew" failed.

See error messages above (also recorded in log file) for possible

reasons for the failure.  Also, please check that the Unix userid

running adrelink has read, write, and execute permissions

on the directory /u01/app/applmgr/TST123/apps/apps_st/appl/ad/12.0.0/bin,

and that there is sufficient space remaining on the disk partition

containing your Oracle Applications installation.

Relinking module 'adrebase' in product ad ...

Solution:

B) Workaround

1. Source 10.1.2 OH

2. Execute the following command to edit the file:

vi $ORACLE_HOME/lib/stubs/libc.so

Update file contents from:

GROUP ( < Old ORACLE_HOME >/lib/stubs/libc.so.6 /usr/lib/libc_nonshared.a )

to:

GROUP ( < New ORACLE_HOME >/lib/stubs/libc.so.6 /usr/lib/libc_nonshared.a )

3. After this update, using the 'oracle' account, execute the following command:

$ rm -fr /tmp/* (all oracle owned files)

4. Source the APPS Envrionment, then apply the following steps:

  a) Execute the script $IAS_ORACLE_HOME/appsutil/clone/adlnkweboh.sh

  b) Execute the script $ORACLE_HOME/appsutil/clone/adlnktools.sh

Ref Note:

After Cloning Adrelink Fails With Error tech_st/10.1.2/lib/stubs/libc.so.6 collect2: ld returned 1 exit status (Doc ID 1275418.1)

Find out HRMS Family Pack level upto RUP9

SELECT 'HR_PF.' ||
DECODE (BUG_NUMBER,'2115771' ,'A(2115771)',
'2268451' ,'B(2268451)',
'2502761' ,'C(2502761)',
'2632500' ,'D(2632500)',
'2803988' ,'E(2803988)',
'2968701' ,'F(2968701)',
'3116666' ,'G(3116666)',
'3233333' ,'H(3233333)',
'3127777' ,'I(3127777)',
'3333633' ,'J(3333633)',
'3500000' ,'K(3500000)',
'5055050' ,'K RUP1(5055050)',
'5337777' ,'K RUP2(5337777)',
'6699770' ,'K RUP3(6699770)',
'7666111' ,'K RUP4(7666111)',
'9062727' ,'K RUP5(9062727)',
'10015566' ,'K RUP6(10015566)',
'12807777', 'K RUP7(12807777)',
'14488556', 'K RUP8(14488556)',
'17774746','.K RUP9(17774746)') ||
' patchset is installed ' "HR Family Pack",
to_char(last_update_date,'DD-MON-YYYY HH24:MI:SS') "DATE APPLIED"
FROM AD_BUGS
WHERE BUG_NUMBER in ('2115771','2268451','2502761','2632500','2803988',
'2968701','3116666','3233333','3127777','3333633','3500000', '5055050',
'5337777','6699770','7666111','9062727','10015566','12807777','14488556','17774746')
ORDER BY to_number(BUG_NUMBER) DESC
/

Ref Note: SQL: HRMS Products Installation Status (Doc ID 414631.1)

Find out ATG RUP level patches information upto RUP7

select
substr(bug_number,1,10) BUG,
decode(bug_number,
'3438354','ATG_PF.H',
'4017300','ATG_PF.H RUP 1',
'4125550','ATG_PF.H RUP 2',
'4334965','ATG_PF.H RUP 3',
'4676589','ATG_PF.H RUP 4',
'5473858','ATG_PF.H RUP 5',
'5903765','ATG_PF.H RUP 6',
'6241631','ATG_PF.H RUP 7') PATCH,
creation_date Applied_date
FROM apps.ad_bugs
WHERE bug_number IN
(
'3438354',
'4017300',
'4125550',
'4334965',
'4676589',
'5473858',
'5903765',
'6241631')
order by bug_number desc
/

Source: How To Find Which Release Update Pack (RUP) Patches Have Been Applied For Release 12 (Doc ID 560498.1)

Unable To Create New Legal Entities - ORA-06512: at "CTXSYS.DRVDML" , ORA-06512: at "HR.DR$HR_LOCATIONS_N1TC

Unable To Create New Legal Entities - ORA-06512: at "CTXSYS.DRVDML" , ORA-06512: at "HR.DR$HR_LOCATIONS_N1TC

Solution:

Disable the trigger

HR.DR$HR_LOCATIONS_N1TC

Note: (Doc ID 1516486.1)

BI Publisher (formerly XML Publisher) Requests Are Failing With Error "OPP Error Oracle.apps.xdo.XDOException: Error Creating Lock File

BI Publisher (formerly XML Publisher) Requests Are Failing With Error "OPP Error Oracle.apps.xdo.XDOException: Error Creating Lock File

Error

oracle.apps.xdo.XDOException: Error creating lock file
        at oracle.apps.xdo.oa.util.FontCacheManager.createLockFile(FontCacheManager.java:363)
        at oracle.apps.xdo.oa.util.FontCacheManager.getFontFromDB(FontCacheManager.java:412)
        at oracle.apps.xdo.oa.util.FontCacheManager.getFontFilePath(FontCacheManager.java:221)
        at oracle.apps.xdo.oa.util.FontHelper.createFontProperties(FontHelper.java:432)
        at oracle.apps.xdo.oa.util.ConfigHelper.getFontProperties(ConfigHelper.java:166)
        at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5817)
        at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3459)
        at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3548)
        at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:302)
        at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:179)
[9/10/14 4:28:52 AM] [493966:RT178323863] Output file was found but is zero sized - Deleted
[9/10/14 4:28:52 AM] [UNEXPECTED] [493966:RT178323863] oracle.apps.xdo.XDOException: Error creating lock file
        at oracle.apps.xdo.oa.util.FontCacheManager.createLockFile(FontCacheManager.java:363)
        at oracle.apps.xdo.oa.util.FontCacheManager.getFontFromDB(FontCacheManager.java:412)
        at oracle.apps.xdo.oa.util.FontCacheManager.getFontFilePath(FontCacheManager.java:221)
        at oracle.apps.xdo.oa.util.FontHelper.createFontProperties(FontHelper.java:432)
        at oracle.apps.xdo.oa.util.ConfigHelper.getFontProperties(ConfigHelper.java:166)
        at oracle.apps.xdo.oa.schema.server.TemplateHelper.runProcessTemplate(TemplateHelper.java:5817)
        at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3459)
        at oracle.apps.xdo.oa.schema.server.TemplateHelper.processTemplate(TemplateHelper.java:3548)
        at oracle.apps.fnd.cp.opp.XMLPublisherProcessor.process(XMLPublisherProcessor.java:302)
        at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:179)

Troubleshooting

1. Check the error in OPP logs. Log file location is

cd $APPLCSF/$APPLLOG
ls --ltr FNDOPP* | tail

Solution

1. Login to Front End, Goto XML Publisher Administrator -> Administration -> General Tab -> Temporary directory

2. Make sure the Temporary directory path is set correctly as mentioned in the above

3. Make sure that this directory can be written to by applmgr from the node that the OPP is running on. You can use the touch command to test this.

4. Set the temporary directory to it's own directory at least 20x larger than the largest data file used by XMLP. Start off with at least 5GB.

5. Try resetting the diretory to a different directory on the same mount as the OPP

6 Bounce Concurrent Manager

7. Retest the issue

Reference: Doc ID 1512691.1

Find out APPS/SYSADMIN password in Oracle Apps R12 if you lost or forgotten

Step to Find APPS PASSWORD :

Step #1

sqlplus> sqlplus system/system_password
sqlplus / as sysdba

Step#2:  Create Function to decrypt the encrypted password

SQL> create FUNCTION apps.decrypt_pin_func(in_chr_key IN VARCHAR2,in_chr_encrypted_pin IN VARCHAR2) RETURN VARCHAR2 AS LANGUAGE JAVA NAME 'oracle.apps.fnd.security.WebSessionManagerProc.decrypt(java.lang.String,java.lang.String) return java.lang.String';
/
Function created.

Step#3: Query for password

set linesize 200 long 300

SQL> select ENCRYPTED_FOUNDATION_PASSWORD from apps.fnd_user where USER_NAME='GUEST';

ENCRYPTED_FOUNDATION_PASSWORD

--------------------------------------------------------------------------------

ZG379C5C883FF56235BE975D075A6FD2E7A749279B7BFCE331530B443E86F41A1966E3E4B1864519DB88BC07D58666AD837B

Step#4:  Get the Apps password using encrypted guest password

SQL> SELECT apps.decrypt_pin_func('GUEST/ORACLE','ZG379C5C883FF56235BE975D075A6FD2E7A749279B7BFCE331530B443E86F41A1966E3E4B1864519DB88BC07D58666AD837B') from dual;

APPS.DECRYPT_PIN_FUNC('GUEST/ORACLE','ZG379C5C883FF56235BE975D075A6FD2E7A749279B

--------------------------------------------------------------------------------

APPS123

Step#5: Test apps password

SQL> conn apps/APPS123;

Connected.

Step to Find SYSADMIN PASSWORD :

Step# 1:

SQL> conn apps/APPS123;

Connected.

Step#2:

SQL> CREATE OR REPLACE PACKAGE get_pwd AS

FUNCTION decrypt (KEY IN VARCHAR2, VALUE IN VARCHAR2)

RETURN VARCHAR2;

END get_pwd;

/ 

Package created.

Step# 3:

SQL>

 CREATE OR REPLACE PACKAGE BODY get_pwd  AS

 FUNCTION decrypt (KEY IN VARCHAR2, VALUE IN VARCHAR2)

 RETURN VARCHAR2

 AS  LANGUAGE JAVA NAME 'oracle.apps.fnd.security.WebSessionManagerProc.decrypt(java.lang.String,java.lang.String) return java.lang.String'; END get_pwd;

 /

Package body created.

Step# 4:

SQL> SELECT usr.user_name,

       get_pwd.decrypt

  2    3            ((SELECT (SELECT get_pwd.decrypt

  4                                (fnd_web_sec.get_guest_username_pwd,

  5                                 usertable.encrypted_foundation_password

  6                                )

  7                        FROM DUAL) AS apps_password

  8                FROM fnd_user usertable

  9               WHERE usertable.user_name =

 10                        (SELECT SUBSTR

 11                                    (fnd_web_sec.get_guest_username_pwd,

 12                                     1,

 13                                       INSTR

 14                                            (fnd_web_sec.get_guest_username_p

 15                                             '/'

 16                                            )

 17                                     - 1

 18                                    )

 19                           FROM DUAL)),

 20             usr.encrypted_user_password) PASSWORD

  FROM fnd_user usr

 WHERE usr.user_name = '&USER_NAME';

Enter value for user_name: SYSADMIN

old  23:  WHERE usr.user_name = '&USER_NAME'

new  23:  WHERE usr.user_name = 'SYSADMIN'

USER_NAME                                     PASSWORD

------------------------                        -----------------

SYSADMIN                                        SYSADMIN123

Step#5 :  Bellow sql will help you to validate SYSADMIN Password

SQL> select fnd_web_sec.validate_login('SYSADMIN','SYSADMIN123) from dual;

FND_WEB_SEC.VALIDATE_LOGIN('SYSADMIN','SYSADMIN123')

--------------------------------------------------------------------------------

Y

Unable to determine SMTP server to use: set FND_SMTP_HOST

Outpost Processor has encountered the below error.

This error can be found in OPP logs:
----------------------------------------
[GC 14000K->8905K(20284K), 0.0074280 secs]
ProcessorException: Unable to determine SMTP server to use: set FND_SMTP_HOST
        at oracle.apps.fnd.cp.opp.EmailDeliveryProcessor.deliver(EmailDeliveryProcessor.java:66)
        at oracle.apps.fnd.cp.opp.DeliveryProcessor.process(DeliveryProcessor.java:91)
        at oracle.apps.fnd.cp.opp.OPPRequestThread.run(OPPRequestThread.java:176)
----------------------------------------

Solution:

1. Log into System Administrator responsibility.
2. Navigate to Profile - System.
3. Query up the %smtp% profiles.
4. Set the following profile values to the defined host and port:
FND:smtp Host (Hostname or IP)
FND:smtp Port (Default is 25)

Ref : R12: "PostProcessorException: Unable to determine SMTP server to use: set FND_SMTP_HOST" Error In OPP manager log file When Selecting Delivery Opts in FNDRSRUN to Send Email Notifications (Doc ID 1240768.1)

Migrate AOL objects from one environment to another environment using FNDLOAD

The Generic Loader (FNDLOAD) is a concurrent program that can transfer Oracle Application entity data between database and text file. The loader reads a configuration file to determine which entity to access. In simple words FNDLOAD is used to transfer entity data from one instance/database to other. For example if you want to move a concurrent program/menu/value sets developed in DEVELOPMENT instance to PRODUCTION instance you can use this command.

To FNDLOAD Concurrent Programs

FNDLOAD apps/$CLIENT_APPS_PWD O Y DOWNLOAD $FND_TOP/patch/115/import/afcpprog.lct XX_CUSTOM_ORACLE_INTERFACE_PROG.ldt PROGRAM APPLICATION_SHORT_NAME="XXGMS" CONCURRENT_PROGRAM_NAME="XX_CUSTOM_ORACLE_INTERFACE_PROG"
##Note that
##---------
## XXGMS will be your custom GMS Application Shortname where concurrent program is registered
## XX_CUSTOM_ORACLE_INTERFACE_PROG
Will be the name of your request group
## XX_CUSTOM_ORACLE_INTERFACE_PROG.ldt is the file where concurrent program definition will be extracted
## ##To upload
FNDLOAD apps/$CLIENT_APPS_PWD O Y UPLOAD $FND_TOP/patch/115/import/afcpprog.lct XX_CUSTOM_ORACLE_INTERFACE_PROG.ldt

To FNDLOAD Request sets with stages

## For this you will be firstly required to download the request set definition.
## Next you will be required to download the Sets Linkage definition
## Well, lets be clear here, the above sequence is more important while uploading
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct XX_GL_MY_INTERFACE_SET.ldt REQ_SET REQUEST_SET_NAME="FNDRSSUB4610101_Will_look_like_this"
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcprset.lct XX_GL_MY_INTERFACE_SET_LINK.ldt REQ_SET_LINKS REQUEST_SET_NAME="FNDRSSUB4610101_Will_look_like_this"
## Note that FNDRSSUB4610101 can be found by doing an examine on the
########----->select request_set_name from fnd_request_sets_vl
########----->where user_request_set_name = 'User visible name for the request set here'
## Now for uploading the request set, execute the below commands
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct XX_GL_MY_INTERFACE_SET.ldt
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afcprset.lct XX_GL_MY_INTERFACE_SET_LINK.ldt

To FNDLOAD Request groups

FNDLOAD apps/$CLIENT_APPS_PWD O Y DOWNLOAD $FND_TOP/patch/115/import/afcpreqg.lct XX_MY_REPORT_GROUP_NAME.ldt REQUEST_GROUP REQUEST_GROUP_NAME="XX_MY_REPORT_GROUP_NAME" APPLICATION_SHORT_NAME="XXGMS"
##Note that
##---------
## <> will be your Application Shortname where request group is registered
## XX_MY_REPORT_GROUP_NAME
Will be the name of your request group
## ##To upload this Request Group in other environment after having transferred the ldt file

FNDLOAD apps/$CLIENT_APPS_PWD O Y UPLOAD $FND_TOP/patch/115/import/afcpreqg.lct

To FNDLOAD responsibility

FNDLOAD apps/$CLIENT_APPS_PWD O Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct XX_PERSON_RESPY.ldt FND_RESPONSIBILITY RESP_KEY="XX_PERSON_RESPY"
## note that XX_PERSON_RESPY is the responsibility key
## Now to upload
FNDLOAD apps/$CLIENT_APPS_PWD O Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct XX_PERSON_RESPY.ldt

To FNDLOAD Profile options

FNDLOAD apps/$CLIENT_APPS_PWD O Y DOWNLOAD $FND_TOP/patch/115/import/afscprof.lct POR_ENABLE_REQ_HEADER_CUST.ldt PROFILE PROFILE_NAME="POR_ENABLE_REQ_HEADER_CUST" APPLICATION_SHORT_NAME="ICX"
## Note that
## POR_ENABLE_REQ_HEADER_CUST is the short name of profile option
## We aren't passing the user profile option name in this case. Validate using ...
########----->select application_id, PROFILE_OPTION_NAME || '==>' || profile_option_id || '==>' ||
########----->USER_PROFILE_OPTION_NAME
########----->from FND_PROFILE_OPTIONS_VL
########----->where PROFILE_OPTION_NAME like '%' || upper('&profile_option_name') || '%'
########----->order by PROFILE_OPTION_NAME
########----->/
## Now to upload
FNDLOAD apps/$CLIENT_APPS_PWD O Y UPLOAD $FND_TOP/patch/115/import/afscprof.lct POR_ENABLE_REQ_HEADER_CUST.ldt

To FNDLOAD User definitions

FNDLOAD apps/$CLIENT_APPS_PWD 0 Y DOWNLOAD $FND_TOP/patch/115/import/afscursp.lct ./XX_FND_USER_PASSI.ldt FND_USER USER_NAME='GANESH'
#Do not worry about your password being extracted, it will be encrypted as below in ldt file
#BEGIN FND_USER "GANESH"
# OWNER = "GEMBALI"
# LAST_UPDATE_DATE = "2007/06/12"
# ENCRYPTED_USER_PASSWORD = "ZGE45A8A9BE5CF4339596C625B99CAEDF136C34FEA244DC7A"
# SESSION_NUMBER = "0"To upload the FND_USER using FNDLOAD command use 
FNDLOAD apps/$CLIENT_APPS_PWD 0 Y UPLOAD $FND_TOP/patch/115/import/afscursp.lct ./XX_FND_USER_PASSI.ldt 
Notes for using FNDLOAD against FND_USER:-
1. After uploading using FNDLOAD, user will be promoted to change their password again during their next signon attempt.
2. All the responsibilities will be extracted by FNDLOAD alongwith User Definition in FND_USER 
3. In the Target Environment , make sure that you have done FNDLOAD for new responsibilities prior to running FNDLOAD on users.

Notes :

1. Give special attention when downloading Menus or Responsibilities.
In case your client has several developers modifying Responsibilities and Menus, then be ultra carefull. Not being carefull will mean that untested Forms and Functions will become available in your clients Production environment besides your tested forms, functions and menus.
2. Be very careful when downloading flexfields that reference value sets with independent values for GL Segment Codes.
By doing so, you will download and extract all the test data in GL Codes that might not be applicable for production.
3. There are several variations possible for FNDLOAD, for example you can restrict the download and uploads to specific segments within Descriptive Flex Fields. Please amend the above examples as desired for applying appropriate filterations.
4. The list of examples by no mean cover all possible FNDLOAD entities.
5. FNDLOAD is very reliable and stable, if used properly. This happens to by one of my favourite Oracle utilities.
6. Last but not the least, please test your FNDLOAD properly, so as to ensure that you do not get any unexpected data. In past I have noticed undesired results when the Lookup gets modified manually directly on production, and then the FNDLOAD is run for similar changes. If possible, try to follow a good practice of modifying FNDLOADable data only by FNDLOAD on production environment.
7. As the name suggests, FNDLOAD is useful for FND Related objects. However in any implementation, you will be required to migrate the Setups in Financials and Oracle HRMS from one environment to another. For this you can use iSetup. "Oracle iSetup".
Some of the things that can be migrated using Oracle iSetup are
GL Set of Books, HR Organization Structures, HRMS Employees, Profile Options Setup, Suppliers, Customers, Tax Codes & Tax Rates, Financials Setup, Accounting Calendars, Chart of Accounts, GL Currencies.

APP-FND-00002: Password must contain at least one letter and at least one number

Workaround to fix while giving weak passwords to application users when changing using FNDCPASS

Error:

FNDCPASS apps/apps123 0 Y system/manager USER SYSADMIN sysadmin

Log filename : L8833563.log


Report filename : O8833563.out

cat L8833563.log

+---------------------------------------------------------------------------+

Application Object Library: Version : 12.0.0

Copyright (c) 1979, 1999, Oracle Corporation. All rights reserved.

 module: 

+---------------------------------------------------------------------------+

Current system time is 18-APR-2013 12:58:23

+---------------------------------------------------------------------------+

APP-FND-00002: Password must contain at least one letter and at least one number.

+---------------------------------------------------------------------------+

Concurrent request completed

Current system time is 18-APR-2013 12:58:23

Workaround:

Set the following profile option value to No. and Change password. Revert back profile option value

Signon Password Hard to Guess

Other profile options related to Password are below:

1-Signon password failure limit
2-Signon Password Length
3-Signon Password No Reuse

Simple PCP configuration

Simple PCP configuration on Non RAC Environment

1. Assume that you have your Application tier is shared across all internal middle tiers
2. Assume you have two CM nodes
3. Stop the Concurrent Managers on both the CM nodes
4. Apply patch 9074947 on application tier
5. set APPLDCP value ON in the context file of both the CM nodes.
6. Run autoconfig on Both cm nodes
7. Verify tnsnames.ora on both CM nodes has FNDFS entries of both the nodes
8. Ensure Internal Monitors on both CM nodes is defined properly and have workshifts assigned to them
9. Make sure 2 Internal monitor Managers of both the nodes is activated. If not activate from Concurrent -> Manager -> Administrator
10. Use the following query to find out your concurrent managers details.

SELECT distinct C.USER_CONCURRENT_QUEUE_NAME, C.MAX_PROCESSES, C.RUNNING_PROCESSES, C.TARGET_PROCESSES, C.NODE_NAME, C.NODE_NAME2
FROM APPLSYS.FND_CONCURRENT_QUEUE_CONTENT A, APPLSYS.FND_CONCURRENT_PROGRAMS B, APPS.FND_CONCURRENT_QUEUES_VL C
WHERE type_id = b.concurrent_program_id and c.concurrent_queue_id = a.concurrent_queue_id;

10. Now Define Primary and secondary nodes for each concurrent manager from Concurrent -> Manager -> Define as per your configuration.
11. Bring up Concurrent Managers on both the CM nodes.
12. Test the concurrent managers by submitting two uniqe concurrent programs that should be running on managers on both the nodes.

Failover Testing

Test Case #1

1. Bring down Apps Listener on CM node 2 using kill -9
2. Kill all FNDLIBR process on CM node 2 using kill -9
3. Start Apps listener on CM node 2 after 5 mins.
4. Monitor CM2, you should see all the managers on CM2 should come up automatially

Test Case #2

1. Bring down apps listener on CM node2 using kill -9.
2. Start the managers on CM1, you should see managers of CM2 will start on CM node 1.
3. Bring up Apps listenr on CM2.
4. You should see, Managers of CM2 should fall back to CM2 from CM1.

Test Case #3

1. Bring down host of CM node 2. It should be shutdown.
2. You should see all the managers of CM2 should be failed over to CM1
3. Bring up host of CM node2.
4. Bring up apps listener on cm node2.
5. You should see all the managers of CM2 should fall back to CM2 fro CM1.

Oracle Note id : How to Setup and Test Failover of PCP on Non-RAC Environments. [ID 743716.1]

How to Create The Service Manager ‘FNDSM’ on Oracle Applications

Run below command to check if node is registered for FNDSM:-
select CONCURRENT_QUEUE_NAME from FND_CONCURRENT_QUEUES where CONCURRENT_QUEUE_NAME like ‘FNDSM%’;

if not then use Note.218893.1 :How to Create The Service Manager ‘FNDSM’ on Oracle Applications

Solution

From the Application tier:

1. Log in as applmgr
2. cd to $FND_TOP/patch/115/sql
3. Run the script: afdcm037.sql
4. This script will create libraries for FNDSM and create Managers for
Preexisting Nodes.

Note: Service Manager “FNDSM” can not be created from form:
Concurrent> Manager> Define under Sysadmin Responsibility.

Reference <bug:6085070 FNDSM TRIGGER CAUSES SERVICE MANAGER NOT TO BE CREATED AFTER CLONING SINGLE NODE>

How to enable Apache and Jserv Debugging in Oracle Apps 11i?

PURPOSE:-If a user experiences an error, request a screen shot of the error and any further error details that they can report.If the error is reproducible, enable the following middle tier debug settings and collect diagnostic information appropriately and upload to support for troubleshooting.

Looking for Jserv.log at $IAS_ORACLE_HOME/Apache/Jserv/logs then enable…
For Temporary purpose manually editing configuration files.
1) Shut Down Apache Server
2) Backup the existing files in the following files:
$IAS_ORACLE_HOME/Apache/Apache/logs
$IAS_ORACLE_HOME/Apache/Jserv/logs
$IAS_ORACLE_HOME/Apache/Jserv/logs/jvm
3) Enable debug logging for Apache
s_apache_loglevel=debug (In Context File)
Or
loglevel debug (In $IAS_ORACLE_HOME/Apache/Apache/conf/httpd.conf)
4) Enable debug logging for mod_jserv
s_apjservloglevel=debug (In Context File)
Or
ApJServLogLevel debug (In $IAS_ORACLE_HOME/Apache/Jserv/etc/jserv.conf)
5) Enable debug logging for Jserv
s_oacorelog=true (In Context File)
Or
log=true log.channel=true log.channel.info=true log.channel.debug=true
(In $IAS_ORACLE_HOME/Apache/Jserv/etc/jserv.properties)
6) Enable debug logging for Forms Listener Servlet JVM. (Optional)
s_oaformslog=true (In Context File)
Or
log=true log.channel=true log.channel.info=true log.channel.debug=true
(In $IAS_ORACLE_HOME/Apache/Jserv/etc/forms.properties)
7) Restart Apache
(If Context File had been edited in above steps then run autoconfig to update the configuration files.) 8) Replicate the Problem.
9) Review the following files from the $IAS_ORACLE_HOME/Apache/Jserv/logs directory
a) mod_jserv.log
b) jserv.log
c) All files from the $IAS_ORACLE_HOME/Apache/Jserv/logs/jvm directory These will
have filenames of the form jvm.jvm.stdoutstderr For example,
OACoreGroup.0.stderr
d) $COMMON_TOP/rgf/instance_hostname/javacache.log

Source: http://leenus2b.wordpress.com

For R12: How To : How to enable Apache, OC4J and OPMN logging in Oracle Applications R12  use Doc id [ID 419839.1]

Forms Servlet mode to Socket mode conversion on Release 12 Apps

How to convert Forms server to Socket mode  from Servlet mode in Oracle Apps R12

Run the following command to enable Forms Socket Mode on Forms/web nodes (Place correct context file name and port value)

$FND_TOP/bin/txkrun.pl -script=ChangeFormsMode -contextfile=$CONTEXT_FILE -mode=socket  -port=9030 -runautoconfig=No


Where port = forms port and contextfile=your environment contextfile

To Start/Stop/check Status of forms servers use following scripts

cd $ADMIN_SCRIPTS_HOME
./adformsrvctl.sh status/stop/start

MSG-00102: Error Message :ORA-20100: File o0000071.tmp creation for FND_FILE failed.

Troubleshooting Details

If a PL/SQL Concurrent Program can't write to an external file, you will receive an error message similar to:

MSG-00102: Error Message :ORA-20100: File o0000071.tmp creation for FND_FILE failed.
You will find more information on the cause of the error in request log.
ORA-06512: at "APPS.FND_FILE", line 378
ORA-06512: at "APPS.FND_FILE", line 473
ORA-06512: at "APPS.AP_TRIAL_BALANCE_PKG", line 192
REP-1419: 'beforereport': PL/SQL program aborted.

NOTE: Applications also produces temporary PL/SQL output files used in concurrent processing. These files are written to a location on the database server node specified by the APPLPTMP environment setting. The APPLPTMP directory must be the same directory as specified by the utl_file_dir parameter in your database initialization file.
.
Rapid Install sets both APPLPTMP and the utl_file_dir parameter to the same default directory. As the temporary files placed in this directory may contain context sensitive information, it should be a secure directory on the database server node with read and write access for the database server owner. In a multi-node system, the directory defined by APPLPTMP does not need to exist on the application tier servers. During an upgrade with AutoUpgrade, you must provide the utl_file_dir parameter value for the APPLPTMP environment setting.


To isolate where the problem is, verify the following:

1) Make sure that the name of the file is valid (the file name should not include characters like "^")

2) Make sure that APPLPTMP is set to a valid directory and that BOTH the applmgr user and the database user have read and write permissions on that directory (normally, it can be set to the same directory as APPLTMP)

3) Make sure that the file does not exit on the directory pointed by APPLPTMP

4) Make sure the directory pointed by APPLPTMP is the first entry on the utl_file_dir. Also, verify that all the entries on the utl_file_dir are valid and that the applmgr has read/write permissions.

If using an spfile, verify the proper syntax to set utl_file_dir:

Eg:  ALTER SYSTEM SET UTL_FILE_DIR='directory1','directory2' scope=spfile;

5) If still having problems, check if you can write a file directly using FND_FILE, which is the package used by the Application. From sqlplus, connected as the apps user, run:

    SQL> exec FND_FILE.PUT_LINE(FND_FILE.LOG, 'THIS IS A TEST');

This should dump a file on APPLPTMP.

If this test works, it would indicate that FND_FILE is ok and the problem is possibly with the Application.

You may want to leave only one entry on utl_file_dir for this test.

6) If still having problems, check if you can write a file using UTL_FILE, which is used by FND_FILE.

Run the PL/SQL below, changing to the first entry on utl_file_dir (you may want to leave just one entry on utl_file_dir for this test).

set serveroutput on
DECLARE
  file_location VARCHAR2(256) := '';
  file_name VARCHAR2(256) := 'utlfile1.lst';
  file_text VARCHAR2(256) := 'THIS IS A TEST';
  file_id UTL_FILE.file_type;
BEGIN
  file_id := UTL_FILE.fopen(file_Location, file_name, 'W');
  UTL_FILE.put_line(file_id, file_text);
  UTL_FILE.fclose(file_id);
EXCEPTION
  WHEN UTL_FILE.INVALID_PATH
  THEN dbms_output.put_line('Invalid path ' || SQLERRM);
    WHEN OTHERS
  THEN dbms_output.put_line('Others '|| SQLCODE || ' ' || SQLERRM);
END;
/

This program should dump a file on the requested directory. If the test fails, the problem is probably on the Database side.

If it works, the problem is probably on FND_FILE. In this scenario, check the versions of AFCPPIOS.pls and AFCPPIOB.pls.

Source : Troubleshooting ORA-20100 on Concurrent Processing [ID 261693.1] (suppot.oracle.com)

"Error Occurred While Attempting to Establish an Applications File Server Connection"

Error:

" An error occurred while attempting to establish an Applications File Server connection. There may be a network configuration problem, or the TNS listener may not be running on "
Solutions to Check

1. Is this a Multinode Install or a Single Node Install.
- If this is a Multinode Install, you will need access to the Middle Tier and the Backend Tier (Concurrent Processor) 8.0.6 ORACLE_HOME/network/admin/tnsnames.ora files

- If this is a Single Node Install, you need access to the Concurrent Processor 8.0.6 ORACLE_HOME/network/admin/tnsnames.ora file

2. Run a report, is there actually a Report Output and Log file being produced at the Operating System level?
- Check the $APPLCSF/out and the $APPLCSF/log directories for the Request_ID out and log file
- If there are no log and output file being produces there Check the permissions on those directories (APPLMGR should have write)
- If $APPLCSF is not set, check the $FND_TOP/log and out for output and logs

3. Confirm that there are 2 listener processes actively running for the Instance that you cannot view reports on -- 1 from 8.0.6 and from 8.1.6 directory structures
- type the following:
ps -ef | grep tnslsnr
- If there is only 1 listener running from the 8.1.6 directory structure
That is the Database Listener
The FNDFS listener needs to be started separately from the Database Listener
- To start the FNDFS Listener:
a. Log the Operating System Level as the APPLMGR account user
b. Set the environment for the $APPL_TOP & 8.0.6 $ORACLE_HOME (APPSORA.env)
c. Go to the $OAD_TOP/admin/scripts (Common_top area)
d. Run the following script:

adalnctl.sh start APPS_SID

(you can confirm the FNDFS Listener name from viewing the 8.0.6 ORACLE_HOME/network/admin/listener.ora file)

4. Check the actual machine name for the Concurrent Processor Server
- type the following:
uname -n

5. Go to the Applications and check the CONCURRENT > MANAGER > ADMINISTER screen in the System Administrator Responsibility The INTERNAL MANAGER NODE NAME; is it the same as what was returned from question 4?
- If it is the same then continue with next step
- If it is not the same,
Shutdown Concurrent Managers and update the FND table:
a. Go to the $OAD_TOP/admin/scripts
b. adcmctl.sh apps/apps stop
c. Connect to SQL*PLUS apps/apps

d. SQL > select target_node from FND_CONCURRENT_QUEUES;
--------------------
This may return the name of an old machine

e. SQL > update FND_CONCURRENT_QUEUES set target_node='' where target_node='';

f. SQL > commit;
g. SQL > exit
h. adcmctl.sh apps/apps start

6. In the 8.0.6 TNSNAMES.ora file, look at the FNDFS_ connection string entry.
Is the hostname value the same as is in questions 4?
- The Rapid Install creates 2 or sometimes 3 FNDFS entries in the TNSNAMES.ora
a. 1 with the FNDFS_
b. 1 with the FNDFS_
c. 1 with the FNDFS_
- The one that is the correct entry is FNDFS_ (hostname being what is returned from a "uname -n")
- If this file does not contain the correct Hostname value
Make a backup of it and edit it to change the FNDFS entry.

7. Check the Network Connection for the FNDFS entry that was defined by the Rapid Install.
- At the Operating System Level
a. tnsping FNDFS_
- This should return the Hostname name and Port information identical to the FNDFS entry in the TNSNAMES.ora file

8. Check the Following PROFILE > SYSTEM Options in The System Administrator Responsibility

CONCURRENT: Report Access Level (this must be set to USER or RESPONSIBILITY)
RRA: Service Prefix (this should be BLANK)
RRA: Enabled (this must be set to YES)
VIEWER: Text (this should be BLANK to view with the default text viewer)
- Viewer: Text can Be set to "browser" to view with Netscape or IE

9. This step should be performed in a case where there might have been patches applied and possibly the FNDFS executable was not Relinked, or it may be missing from the file system or corrupted.
- Shutdown the FNDFS Listener
a. $OAD_TOP/admin/scripts/adalnctl.sh stop APPS_SID
- Rename or Move the Current FNDFS executable before relinking
a. $FND_TOP/bin
mv FNDFS FNDFS.bak
b. As APPLMGR account user
adrelink.sh force=y "fnd FNDFS"
- Start the FNDFS Listener
a. $OAD_TOP/admin/scripts/adalnctl.sh start APPS_SID

Metalink Note : ID 117012.1

FAQs - How do we know how many users are connected to Oracle Applications.

FAQs - How do we know how many users are connected to Oracle Applications.

1. Enable Profile Option "Sign-On Audit" at "Form" level.
2. Run "Purge Signon Audit" request.
3. Security:Users -> Monitor" option
4  or with the below sql query  mentioned below.

select distinct fu.user_name User_Name,fr.RESPONSIBILITY_KEY Responsibility
from fnd_user fu, fnd_responsibility fr, icx_sessions ic
where fu.user_id = ic.user_id AND
fr.responsibility_id = ic.responsibility_id AND
ic.disabled_flag='N' AND
ic.responsibility_id is not null AND
ic.last_connect like sysdate;

5. Can use this SQL statement to count concurrent_users in Oracle apps:

select count(distinct d.user_name) from apps.fnd_logins a,
v$session b, v$process c, apps.fnd_user d
where b.paddr = c.addr
and a.pid=c.pid
and a.spid = b.process
and d.user_id = a.user_id
and (d.user_name = 'USER_NAME' OR 1=1)