Wednesday, February 27, 2019

Unable To Generate Fnd Debug Logfiles And No Messages Are Writing To Fnd_log_messages

Dear Folks,

One of 12.2.4 customer facing issue several times to generate fnd log messages after the FND Diagnostics Profile is Set to 'Yes' at the Site Level.

It returns no rows in fnd_log_messages.

SQL> select count(*) from apps.fnd_log_messages;

 COUNT(*)
----------
     0

SQL> select max(LOG_SEQUENCE) from fnd_log_messages;

MAX(LOG_SEQUENCE)
-----------------


As per ML:: 2007068.1, We applied patch 22563940. Then issue resolved.

Expected Behavior
Expect FND Debugging to write to the fnd_log_messages tables.

The issue can be reproduced at will with the following steps:
1. Set FND Debugging

The issue has the following business impact:
Due to this issue, dba/appsdba cannot enable fnd debugging.

Now they are able to see rows in fnd_log_messages table.

Thanks.
Sreeharsha.



Thursday, February 21, 2019

Relink of module "FEMCCE" failed after CPU applied.

Dear Folks,



Recently, we've observed relink error while applying CPU (Q1-2019) Patches on to one of non-prod instance.

Relinking module 'FEMCCE' in product fem ...

make -f

/u01/app/***/$TWO_TASK/apps/apps_st/appl/admin/$TWO_TASK/out/link_fem_28563.mk

/u01/app/*****/$TWO_TASK/apps/apps_st/appl/fem/12.0.0/bin/FEMCCE


Starting  link of fem executable 'FEMCCE' on Mon Feb  4 22:21:45 EST 2019

 ORDER BY 2;


make: *** [/u01/app/****/$TWO_TASK/apps/apps_st/appl/fem/12.0.0/bin/FEMCCE]

Error 1

Done with link of fem executable 'FEMCCE' on Mon Feb  4 22:21:45 EST 2019


Relink of module "FEMCCE" 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/****/$TWO_TASK/apps/apps_st/appl/fem/12.0.0/bin,

and that there is sufficient space remaining on the disk partition

containing your Oracle E-Business Suite installation.



Done with link of product 'fem' on Mon Feb  4 22:21:45 EST 2019


adrelink is exiting with status 1


Verified, We don't have file exists at OS level.



[****@Kouuda scripts]$ ls -lrt /u01/app/****/$TWO_TASK/apps/apps_st/appl/fem/12.0.0/bin/FEMCCE

ls: cannot access /u01/app/****/$TWO_TASK/apps/apps_st/appl/fem/12.0.0/bin/FEMCCE: No such file or directory

Hence, we copied binary file from production and relinked it manually.


[****@ scripts]$ make -f /u01/app/****/$TWO_TASK/apps/apps_st/appl/admin/$TWO_TASK/out/link_fem_28563.mk /u01/app/****/$TWO_TASK/apps/apps_st/appl/fem/12.0.0/bin/FEMCCE

make: `/u01/app/****/$TWO_TASK/apps/apps_st/appl/fem/12.0.0/bin/FEMCCE' is up to date.


Now Patch completed successfully.


Thanks.

Sreeharsha

APP-FND-01372 : Please register System printer with Application object library.

Dear Folks,

In one of our EBS customer running on 11i. Customer facing issue while switching responsibilities. Below pop-up error window does appear while doing.

APP-FND-01372 : Please register System printer with Application object library.


Solution
=======

Verified, The profile value for Printer is set to "Null"

Hence Change profile value of "Printer" to "noprint" and save changes.


Now,  customer able to switch responsibilities.

Thanks.
Sreeharsha



Wednesday, February 13, 2019

txkrun.pl (forms deplyoment) failed with TXK::Common::setError & TXK::Process::run

Dear Folks,



In one of our EBS customer, we came across an issue with forms deployment post 10.1.2 patches as part of CPU.

forms deployment failing with below error.

Command error: <rc> = 38400, <command> = /u01/app/****/apps/tech_st/10.1.3/opmn/bin/opmnctl startproc instancename=forms

STACK TRACE

    TXK::Error::abort('TXK::Error','HASH(0x830c890)') called at /u01/app/****/apps/apps_st/appl/au/12.0.0/perl/TXK/Common.pm line 299

    TXK::Common::doError('TXK::Process=HASH(0x8b112d0)','Command error: <rc> = 38400, <command> = /u01/app/****/apps/...','undef') called at /u01/app/****/apps/apps_st/appl/au/12.0.0/perl/TXK/Common.pm line 314

    TXK::Common::setError('TXK::Process=HASH(0x8b112d0)','Command error: <rc> = 38400, <command> = /u01/app/****/apps/...') called at /u01/app/****/apps/apps_st/appl/au/12.0.0/perl/TXK/Process.pm line 449

    TXK::Process::run('TXK::Process=HASH(0x8b112d0)','HASH(0x8add484)') called at /u01/app/****/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkCfgOC4JApp.pl line 1587

    TXK::RunScript::execOPMNControl('HASH(0x8ce7fb8)') called at /u01/app/****/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkCfgOC4JApp.pl line 606

    require /u01/app/****/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkCfgOC4JApp.pl called at /u01/app/****/apps/apps_st/appl/au/12.0.0/perl/TXK/RunScript.pm line 105

    TXK::RunScript::require('TXK::RunScript','/u01/app/****/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txk...') called at /u01/app/****/apps/apps_st/appl/au/12.0.0/perl/TXK/Script.pm line 177



Steps to deploy forms (397174.1).

==============

*** cp $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml.orig_11Aug2018

*** vi $INST_TOP/ora/10.1.3/j2ee/forms/config/system-jazn-data.xml

Add OC4J Administrator credentials.

<name>oc4jadmin</name>

    <display-name>OC4J Administrator</display-name>

    <description>OC4J Administrator</description>

    <credentials>!welcome123</credentials>

   </user>

***

[****@jauauaua ~]$ cp $IAS_ORACLE_HOME/opmn/bin/opmnctl $IAS_ORACLE_HOME/opmn/bin/opmnctl.org

[****@jauauaua ~]$ cp $INST_TOP/ora/10.1.3/opmn/bin/opmnctl $IAS_ORACLE_HOME/opmn/bin/opmnctl

[****@jauauaua ~]$ cp $IAS_ORACLE_HOME/opmn/conf/opmn.xml $IAS_ORACLE_HOME/opmn/conf/opmn.xml.org

[****@jauauaua ~]$ cp $INST_TOP/ora/10.1.3/opmn/conf/opmn.xml $IAS_ORACLE_HOME/opmn/conf/opmn.xml

*** Stop the application /adstpall.sh

4.[****@jauauaua ~]$ $FND_TOP/bin/txkrun.pl -script=CfgOC4JApp

*** ALL THE FOLLOWING FILES ARE REQUIRED FOR RESOLVING RUNTIME ERRORS

*** Log File = /u01/app/k****/inst/apps/JAJAJ_jauauaua/logs/appl/rgf/TXK/txkCfgOC4JApp_Sat_Aug_11_16_55_58_2018.log

Program : /u01/app/****/k****/apps_st/appl/fnd/12.0.0/patch/115/bin/txkCfgOC4JApp.pl started @ Sat Aug 11 16:55:58 2018


*** Log File = /u01/app/****/inst/apps/JAJAJ_jauauaua/logs/appl/rgf/TXK/txkCfgOC4JApp_Sat_Aug_11_16_55_58_2018.log

Enter Application name for re-deployment ? forms

Enter Oc4j Instance password for re-deployment ?   <<Enter password welcome123>>

Run Autoconfig <Yes/No> ? No

6.Run AutoConfig on the instance by running the command:

$ $ADMIN_SCRIPTS_HOME/adautocfg.sh

7.Restart the application tier services by running the command:

$ $ADMIN_SCRIPTS_HOME/adstrtal.sh <apps user/apps password>



Solution when form deployment failing with above errors.

======================================
Add -Djdk.crypto.KeyAgreement.legacyKDF=true to oacore,forms,oafm start/stop properties in contextfile.

Ex::
****@jaidkalala ~]$ grep -i oacore $CONTEXT_FILE

                        <forms_jvm_start_options oa_var="s_forms_jvm_start_options">-server -verbose:gc -Xmx256M -Xms64M -XX:MaxPermSize=128M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB -XX:+UseParallelGC -XX:ParallelGCThreads=2 -Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false -Doracle.security.jazn.config=/u01/app/****/inst/apps/JUAUa_JAUAUAdkd/ora/10.1.3/j2ee/forms/config/jazn.xml -Djdk.crypto.KeyAgreement.legacyKDF=true</forms_jvm_start_options>

                        <forms_jvm_stop_options oa_var="s_forms_jvm_stop_options">-server -verbose:gc -Xmx256M -Xms64M -XX:MaxPermSize=128M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB -XX:+UseParallelGC -XX:ParallelGCThreads=2 -Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false -Djdk.crypto.KeyAgreement.legacyKDF=true</forms_jvm_stop_options>

                <oacore_server>

                        <oacore_jvm_start_options oa_var="s_oacore_jvm_start_options">-server -verbose:gc -Xmx1024M -Xms256M -XX:MaxPermSize=160M -XX:NewRatio=2  -XX:+PrintGCTimeStamps -XX:+UseTLAB -XX:+UseParallelGC  -XX:ParallelGCThreads=2  -Dcom.sun.management.jmxremote -Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false -Doracle.security.jazn.config=/u01/app/***/inst/apps/JUAUa_JAUAUAdkd/ora/10.1.3/j2ee/oacore/config/jazn.xml -Doracle.mds.custcache.maxentries=1000 -Djdk.crypto.KeyAgreement.legacyKDF=true</oacore_jvm_start_options>

                        <oacore_oc4j_options oa_var="s_oacore_oc4j_options">-out /u01/app/***/inst/apps/JUAUa_JAUAUAdkd/logs/ora/10.1.3/opmn/oacorestd.out -err /u01/app/***/inst/apps/JUAUa_JAUAUAdkd/logs/ora/10.1.3/opmn/oacorestd.err</oacore_oc4j_options>

                        <oacore_jvm_stop_options oa_var="s_oacore_jvm_stop_options">-server -verbose:gc -Xmx512M -Xms128M -XX:MaxPermSize=160M -XX:NewRatio=2  -XX:+PrintGCTimeStamps -XX:+UseTLAB -XX:+UseParallelGC  -XX:ParallelGCThreads=2  -Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy -Djava.awt.headless=true -Dhttp.webdir.enable=false -Djdk.crypto.KeyAgreement.legacyKDF=true</oacore_jvm_stop_options>



                        <oafm_jvm_start_options oa_var="s_oafm_jvm_start_options">-server -verbose:gc -Xmx256M -Xms64M -XX:MaxPermSize=128M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB -XX:+UseParallelGC -XX:ParallelGCThreads=2  -Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy  -Djava.awt.headless=true  -Dhttp.webdir.enable=false -Doracle.security.jazn.config=/u01/app/***/inst/apps/JUAUa_JAUAUAdkd/ora/10.1.3/j2ee/oafm/config/jazn.xml -Djdk.crypto.KeyAgreement.legacyKDF=true</oafm_jvm_start_options>

                        <oafm_oc4j_options oa_var="s_oafm_oc4j_options">-out  /u01/app/***/inst/apps/JUAUa_JAUAUAdkd/logs/ora/10.1.3/opmn/oafmstd.out -err  /u01/app/***/inst/apps/JUAUa_JAUAUAdkd/logs/ora/10.1.3/opmn/oafmstd.err</oafm_oc4j_options>

                        <oafm_jvm_stop_options oa_var="s_oafm_jvm_stop_options">-server -verbose:gc -Xmx256M -Xms64M -XX:MaxPermSize=128M -XX:NewRatio=2 -XX:+PrintGCTimeStamps -XX:+UseTLAB -XX:+UseParallelGC -XX:ParallelGCThreads=2  -Djava.security.policy=$ORACLE_HOME/j2ee/oacore/config/java2.policy  -Djava.awt.headless=true  -Dhttp.webdir.enable=false -Djdk.crypto.KeyAgreement.legacyKDF=true</oafm_jvm_stop_options>





** And ran autoconfig



**Forms deployment completed successfully.



Program : /u01/app/****/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkCfgOC4JApp.pl completed @ Wed Nov 7 21:39:02 2018



End of /u01/app/****/apps/apps_st/appl/fnd/12.0.0/patch/115/bin/txkCfgOC4JApp.pl : No Errors encountered



ML :: 2353710.1



Thanks

Sreeharsha

License A new product/Module in EBS using OAM.

Hello every one,

Let's see how we can do license a new module/product in EBS using Oracle Application Manager.

Here are the steps
==========

**Login as sysadmin user
**Go to System Administrator
**Go to Oracle Applications Manager
**Click on License Manager
**In license section select products.
**Click on Show more options and select License Applications Product
**Select required module and click next and submit.

Post steps
=======

3. Now using adadmin and choose first option 1.

            AD Administration Main Menu
   --------------------------------------------------

   1.    Generate Applications Files menu

   2.    Maintain Applications Files menu

   3.    Compile/Reload Applications Database Entities menu

   4.    Maintain Applications Database Entities menu

   5.    Change Maintenance Mode

   6.    Exit AD Administration
   
Select Generate Application Files menu

Enter your choice [6] : 1

         Generate Applications Files
   ----------------------------------------

   1.    Generate message files

   2.    Generate form files

   3.    Generate report files

   4.    Generate product JAR files

   5.    Return to Main Menu

Run below.

   ***Generate message files

   ***Generate form files

   ***Generate report files


Back to Main Menu

Select Compile/Reload Applications Database Entities menu

Enter your choice [6] : 3

        Compile/Reload Applications Database Entities
   ---------------------------------------------------

   1.    Compile APPS schema

   2.    Compile menu information

   3.    Compile flexfields

   4.    Reload JAR files to database

   5.    Return to Main Menu

Run following.

Compile APPS schema
Compile menu information
Compile flexfields

4. Run autoconfig 

5. Verify Product installed successfully or not using below query.

select fa.APPLICATION_SHORT_NAME, fpi.PATCH_LEVEL, DECODE(fpi.STATUS, 'I','Installed',
'S','Shared', 'N', 'Inactive', fpi.STATUS) Status , fpi.DB_STATUS
from fnd_product_installations fpi,FND_APPLICATION fa
where fpi.APPLICATION_ID in (
select APPLICATION_ID from FND_APPLICATION where APPLICATION_SHORT_NAME like 'AME')
and fa.APPLICATION_ID=fpi.APPLICATION_ID; 

6) Make sure we verify related TOPS available on File system level. 

Thanks.
Sreeharsha



Tuesday, February 12, 2019

UNNAMED data file in standby after adding new data file in primary – ORA-01111, ORA-01110, ORA-01157 , ORA-01274

Dear Folks,

We came across missing data file in standby after adding new data file in primary which causes MRP job terminate. This could be due to following reasons.

**Either we don't have sufficient  disk space/ASM available at standby host.
**standby_file_management parameter set to MANUAL.

i.e, if standby_file_management parameter is MANUAL on standby, MRP processes couldn't apply archives due to this wrong parameter settings, a UNNAMED data file being created at $ORACLE_HOME/dbs location.

From alert log
==========

File #59 added to control file as 'UNNAMED00059' because
the parameter STANDBY_FILE_MANAGEMENT is set to MANUAL
The file should be manually created to continue.
Errors with log +JDUAUA_FRA/xcmrc_stby/archivelog/2019_02_13/thread_1_seq_9619.319.1000088461
MRP0: Background Media Recovery terminated with error 1274
Errors in file /
ORA-01274: cannot add datafile '+JDUAUA_DATA/xcmrc/datafile/apps_ts_tx_data.299.1000076027' - file could not be created
Managed Standby Recovery not using Real Time Apply

Recovery stopped due to failure in applying recovery marker (opcode 17.30).

So from above log, we clearly identified missing data file=59

SQL> select file#,name from v$datafile where file#=59;

     FILE#
----------
NAME
--------------------------------------------------------------------------------
        59
+JDUAUA_DATA_DATA/xcmrc/datafile/apps_ts_tx_data.299.1000076027


Identify the missing datafile from standby

     FILE#
----------
NAME
--------------------------------------------------------------------------------
        59
/u01/app/oraxx/JDUAUA_DATA/db/tech_st/11.2.0/dbs/UNNAMED00059

Hence created missing data file in Standby.

SQL > alter database create datafile '/u01/app/oraxx/JDUAUA_DATAdb/tech_st/11.2.0/dbs/UNNAMED00059' as '+JDUAUA_DATA_DATA' size 5576m

Database altered.

Enabled standby_file_management to AUTO

SQL> alter system set standby_file_management=AUTO sid='*';

System altered.

Start MRP process.
===========

SQL> recover managed standby database disconnect from session;
Media recovery complete.

Thanks.
Sreeharsha


RMAN-6091: no channel allocated for maintenance (of an appropriate type)

Hello Every one,

Recently, In one of our EBS customer, we came across issue with RMAN backup post CPU Q3 patches  on to 12.1.0.2 instance. The backup failing with below error.

RMAN> delete noprompt archivelog until time 'sysdate -3' backed up 1 times to sbt;
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of delete command at 02/03/2019 20:17:05
RMAN-06091: no channel allocated for maintenance (of an appropriate type)

Hence, we've implemented workaround  as per ML 2428682.1

allocate disk channel and delete the datafile copies and archivelog copies.


run {
allocate channel ch1 type 'sbt_tape''";
backup database
include current controlfile ;
}
allocate channel for maintenance device type disk;
crosscheck archivelog all;
delete force noprompt archivelog all;


Workaround::2
============

Apply patch  28432129.


Expected behavior
============

Event after applying the patch 28432129, RMAN may fail with an Error RMAN-6091.

Enhancement Request will be implemented in the future release:" Bug 28593955 : RMAN-6091 ERRORS SEEN EVEN AFTER APPLYING THE PATCH 28432129 "

Note:: This bug 28593955 still yet to implemented by oracle. So we need to apply patch 28432129

Bug fix 28432129 only to allow deletion of archive log and image copies (Not backupsets) , So having some maintenance command mail fail if appropriate channels are not allocated.

Rman never deleted disk backups from SBT channels.

Suggested changes to RMAN scripts to avoid an error.

1) Move all maintenance commands into separate RUN{} or outside RUN{} block as shown in above command and allocate required channels (DISK and TAPE, if RMAN needs to operate on backup files residing on both device types).

2) Have backup commands by allocating whatever device type channels the user wants to create backup files

We should still stick to requirement to have correct device types allocated for maintenance commands operations to work correctly.

Thanks.
Sreeharsha