Saturday, March 30, 2019

APP-PAY-06882: Assertion failure detected at location py3vntsetup:2

Dear Folks,

Recently we have faced issue in Vertex monthly data upgrade where the program "Quantum Data Update installer" had failed with below error.

LOCATION py3vntsetup:2
APP-PAY-06882: Assertion failure detected at location py3vntsetup:2.

Cause:        an internal error has occurred at location py3vntsetup:2.  

Action:        please contact your Oracle customer representative.

Work Around
+++++++++++

1) Check TAX_DATA & TAX_LIBRARIES paths ,if they are pointing to the wrong path.

SQL> select * from pay_action_parameters where parameter_name like 'TAX%';

PARAMETER_NAME
----------------------------------------------------------------------
PARAMETER_VALUE
--------------------------------------------------------------------------------
TAX_DATA
/u01/app/appki/****/apps/apps_st/appl/pay/12.0.0/vendor/quantum/data

TAX_LIBRARIES
/u01/app/***/******/apps/apps_st/appl/pay/12.0.0/vendor/quantum/lib

From Above, TAX_LIBRARIES path pointed to the production. Hence we've corrected it to right path.

SQL> update pay_action_parameters set parameter_value = '/u01/app/***/*****/apps/apps_st/appl/pay/12.0.0/vendor/quantum/lib' where parameter_name = 'TAX_LIBRARIES';

1 row updated.

SQL> commit;

Commit complete.

2) Run Quantum Data Update installer program. It should be completed normal.

Thanks.
Sreeharsha

Wednesday, March 20, 2019

How to change APPS password in EBS 11i

***************How to change APPS Password in EBS 11i******************

Here are the steps to change apps password in 11i EBS

1) Shut down the application on all nodes
2) Take the backup below files on all application nodes.

$IAS_ORACLE_HOME/Apache/modplsql/cfg/wdbsvr.app
$ORACLE_HOME/reports60/server/CGIcmd.dat  (8.0.6 Oracle_home)
$FND_TOP/resource/wfmail.cfg

3) Backup below tables
=====================

SQL> create table FND_USER_BK_<YYYYMMSS> as select * from FND_USER;
SQL> create table FND_ORACLE_USERID_BK_<YYYYMMSS> as select * from FND_ORACLE_USERID;

4) Change apps password using below command.

FNDCPASS apps/<appspwd> 0 Y system/<pwd> SYSTEM APPLSYS <new password>

 **Changing APPLSYS user password will automatically changes APPS user password.

5) Change APPS password in the following files.

$IAS_ORACLE_HOME/Apache/modplsql/cfg/wdbsvr.app
$ORACLE_HOME/reports60/server/CGIcmd.dat  (8.0.6 Oracle_home)
$FND_TOP/resource/wfmail.cfg

6) Start Application on all the nodes.

7 ) Validate services.

8) Recreate DB links if any needed.

9) Check any cron job that have apps password hardcoded.

Thanks.
Sreeharsha


Tuesday, March 19, 2019

ICM log file location in R12 oracle EBS

                      ****ICM log file location in EBS R12****


All concurrent log files stay at the location $APPLCSF/$APPLLOG

1) Login into Apps environment and source the env file.

2) Go to $APPLCSF/$APPLLOG location

3) ls -lrt *$TWO_TASK*

[****@*****log]$ ls -lrt *$TWO_TASK*
-rw-r--r-- 1 24852359 Mar 20 01:07 KAPI_0801.mgr

4) Identify the internal concurrent manager log file (SID_MMDR.mgr)

5) If you want to identify other manager log files.

******Standard manager log:  wxxxx.mgr.   (xxxx represents Process ID )

                      EX :: -rw-rw-r-- 1 ****** 624100 Mar 20 01:09 w19983.mgr

***** Conflict resolution manager log :: cxxx.mgr  

                   EX: [***@*****log]$ ls -ltr c*.mgr
                              -rw-rw-r-- 1 **** ***1021 Nov  4 01:00 c19947.mgr

***** Transaction manager log:  txxxx.mgr

                  EX :: -rw-rw-r-- 1 *** *** 2672 Feb 28 13:24 t19939.mgr



Option 2
======

You can identify ICM log file using below query.

SELECT 'ICM_LOG_NAME=' || fcp.logfile_name
FROM fnd_concurrent_processes fcp, fnd_concurrent_queues fcq
WHERE fcp.concurrent_queue_id = fcq.concurrent_queue_id
AND fcp.queue_application_id = fcq.application_id
AND fcq.manager_type = '0'
AND fcp.process_status_code = 'A';

EX ::

SQL> SELECT 'ICM_LOG_NAME=' || fcp.logfile_name
FROM fnd_concurrent_processes fcp, fnd_concurrent_queues fcq
WHERE fcp.concurrent_queue_id = fcq.concurrent_queue_id
AND fcp.queue_application_id = fcq.application_id
AND fcq.manager_type = '0'
AND fcp.process_status_code = 'A';
  2    3    4    5    6  
'ICM_LOG_NAME='||FCP.LOGFILE_NAME
--------------------------------------------------------------------------------
ICM_LOG_NAME=/u01/app/****/KLSPI/inst/apps/KLSPI_servername/logs/appl/conc/lo
g/KLSPI_0801.mgr

Option 3
======

We can identify ICM log file from frontend.

Log in to Sysadmin Responsibility

Go to ->Concurrent -> Manager -> Administer -Processes -> Click button Internal Manager Log.

Thanks
Sreeharsha.



Workflow mailer log file location Oracle EBS R12

Workflow log location
++++++++++++++


cd $APPLCSF/$APPLLOG

ls -ltr FNDCPGSC*.txt


OR

Below query shows active workflow log file.


SELECT fcp.logfile_name
FROM fnd_concurrent_queues fcq, fnd_concurrent_processes fcp, fnd_lookups flkup
WHERE concurrent_queue_name in (‘WFMLRSVC’)
AND fcq.concurrent_queue_id = fcp.concurrent_queue_id
AND fcq.application_id = fcp.queue_application_id
AND flkup.lookup_code=fcp.process_status_code
AND lookup_type =’CP_PROCESS_STATUS_CODE’
AND meaning=’Active’;


--------------------------------------------------------------------------------
/u01/app/****/****/inst/apps/PSSPI_servername/logs/appl/conc/log/FNDCPGSC200
49.txt

Thanks
Sreeharsha

ORA-01403: No Data Found Has Been Detected In FND_CONC_RAC_UTILS

Dear Folks,

In one of our EBS customer running on 12.2.4. We've noticed few errors in internal concurrent manager log after user terminated a custom request.

Below observed in concurrent request log file.

--------------------------------------------------------------
An error occured in client-side routine afpsmckp for Service Manager FNDSM_*****_EBSPROD. The routine returned code 1.
Check for preceding errors and as well as the service manager log file for further details."
18-MAR-2019 11:03:10 - Could not submit job to kill concurrent process 188273: Oracle error 100: ORA-01403: no data found has been detected in FND_CONC_RAC_UTILS.SUBMIT_MANAGER_KILL_SESSION.

Solution
====

Apply Patches  24408550 and Patch 19479047 as per ML 1988419.1. Then issue resolved. No errors can see in ICM log file.

Concurrent Programs Fails With ORA-01403: No Data Found Has Been Detected In FND_CONC_RAC_UTILS (Doc ID 1988419.1)

Thanks.
Sreeharsha.

Monday, March 18, 2019

Patch Impact Analysis

col patch_name format a8 heading "Patch|Name"
col instance_name format a10 heading "Instance|Name"
col name format a10 heading "Node Name"
col APPL_TOP format a10
col subdir format a20
col filename format a18
col latest format a20
col driver_file_name format a13 heading "Driver|File|Name"
col action format a10
set lines 150
set pages 1000
Select
J.PATCh_NAME,
H.APPLICATIONS_SYSTEM_NAME Instance_Name,
H.NAME,
I.DRIVER_FILE_NAME,
D.APP_SHORT_NAME appl_top,
D.SUBDIR,
D.FILENAME,
max(F.VERSION) latest,
E.ACTION_CODE action
from
AD_BUGS A,
AD_PATCH_RUN_BUGS B,
AD_PATCH_RUN_BUG_ACTIONS C,
AD_FILES D,
AD_PATCH_COMMON_ACTIONS E,
AD_FILE_VERSIONS F,
AD_PATCH_RUNS G,
AD_APPL_TOPS H,
AD_PATCH_DRIVERS I,
AD_APPLIED_PATCHES J
where
A.BUG_ID = B.BUG_ID and
B.PATCH_RUN_BUG_ID = C.PATCH_RUN_BUG_ID and
C.FILE_ID = D.FILE_ID and
E.COMMON_ACTION_ID = C.COMMON_ACTION_ID and
D.FILE_ID = F.FILE_ID and
G.APPL_TOP_ID = H.APPL_TOP_ID and
G.PATCH_DRIVER_ID = I.PATCH_DRIVER_ID and
I.APPLIED_PATCH_ID = J.APPLIED_PATCH_ID and
B.PATCH_RUN_ID = G.PATCH_RUN_ID and
C.EXECUTED_FLAG = 'Y' and
G.PATCH_DRIVER_ID in
 (select PATCH_DRIVER_ID
 from AD_PATCH_DRIVERS
 where APPLIED_PATCH_ID in
 (select APPLIED_PATCH_ID
 from AD_APPLIED_PATCHES
 where PATCH_NAME in('22284589')) )
GROUP BY
J.PATCH_NAME,
H.APPLICATIONS_SYSTEM_NAME,
H.NAME,
I.DRIVER_FILE_NAME,
D.APP_SHORT_NAME,
D.SUBDIR,
D.FILENAME,
E.ACTION_CODE;