Sunday, August 30, 2020

EBS WF Background Process SQL

Monitor the progress on what is happening with the WF Background Processes by running these:

1. Show what is exactly on the Background Process Deferred Queue ready for processing

select w.user_data.itemtype "Item Type", w.user_data.itemkey "Item Key",
decode(w.state, 0, '0 = Ready',
1, '1 = Delayed',
2, '2 = Retained',
3, '3 = Exception',
to_char(w.state)) State,
w.priority, w.ENQ_TIME, w.DEQ_TIME, w.msgid
from wf_deferred_table_m w
where w.user_data.itemtype = '&item_type';

2. Monitor the Queue by Item Type ie APPS<itemtype>

select corrid, user_data user_data
from wf_deferred_table_m
where state = 0
and corrid = '&Corrid'
order by priority, enq_time; 

3. Monitor the Deferred Queue to see exactly what's coming off next

SELECT wfdtm.corrid, wfdtm.user_data.ITEMTYPE ITEM_TYPE,
wfdtm.user_data.ITEMKEY ITEM_KEY, wfdtm.enq_time,
DECODE(wfdtm.state,
0, '0 = Ready',
1, '1 = Delayed',
2, '2 = Retained',
3, '3 = Exception',
TO_CHAR(SUBSTR(wfdtm.state,1,12))) State
FROM wf_deferred_table_m wfdtm
WHERE wfdtm.state = 0
ORDER BY wfdtm.priority, wfdtm.enq_time; 

4. Show what frequency the FNDWFBG request is going to be resubmitted and its parameters:

select r.REQUEST_ID, r.REQUESTED_BY, r.PHASE_CODE, p.USER_CONCURRENT_PROGRAM_NAME, r.ARGUMENT_TEXT "Arguments",
Nvl(Substr(R.Argument_Text,0,Instr(R.Argument_Text,',')-1),'All Items') Item_Type,
Substr(R.Argument_Text,Instr(R.Argument_Text,',')+1,Instr(R.Argument_Text,',',1,2)-Instr(R.Argument_Text,',')-1) Min_Threshold,
Substr(R.Argument_Text,Instr(R.Argument_Text,',',1,2)+1,(Instr(R.Argument_Text,',',1,3)-1)-(Instr(R.Argument_Text,',',1,2))) Max_Threshold,
Substr(R.Argument_Text,Instr(R.Argument_Text,',',1,3)+1,(Instr(R.Argument_Text,',',1,4)-1)-(Instr(R.Argument_Text,',',1,3))) Deferred,
substr(r.ARGUMENT_TEXT,instr(r.ARGUMENT_TEXT,',',1,4)+1,(instr(r.ARGUMENT_TEXT,',',1,5)-1)-(instr(r.ARGUMENT_TEXT,',',1,4))) TIMEOUT,
substr(r.ARGUMENT_TEXT,instr(r.ARGUMENT_TEXT,',',1,5)+1) STUCK,
r.RESUBMIT_INTERVAL EVERY, r.RESUBMIT_INTERVAL_UNIT_CODE SO_OFTEN, r.RESUBMIT_END_DATE
FROM fnd_concurrent_requests r, FND_CONCURRENT_PROGRAMS_TL p
WHERE r.CONCURRENT_PROGRAM_ID = p.CONCURRENT_PROGRAM_ID
and p.USER_CONCURRENT_PROGRAM_NAME LIKE 'Workflow%Background%'
AND p.LANGUAGE = 'US'
and r.ACTUAL_COMPLETION_DATE is null
and r.PHASE_CODE in ('P','R');

 

Friday, August 28, 2020

Output Post Processor (OPP) Fails

 R12 E-Business Suite Output Post Processor (OPP) Fails To Pick Up Concurrent Requests With Error 'Unable to find an Output Post Processor service to post-process request nnnnn' (Doc ID 2215371.1)

 

SELECT fcp.concurrent_process_id  FROM apps.fnd_concurrent_queues fcq, apps.fnd_concurrent_processes fcp  WHERE concurrent_queue_name = 'FNDCPOPP'AND fcq.concurrent_queue_id = fcp.concurrent_queue_idAND fcq.application_id = fcp.queue_application_id AND fcp.process_status_code = 'A'

Thursday, August 27, 2020

Oracle EBS workflow sql handy for your job

select w.user_data.itemtype "Item Type", w.enq_time,w.user_data.itemkey "Item Key"  from apps.wf_deferred_table_m w order by w.enq_time desc

SELECT component_name, component_status FROM apps.fnd_svc_componentsWHERE component_type = 'WF_MAILER';

select message_type, count(1) from apps.wf_notifications where status='OPEN' and mail_status='MAIL' group by message_type;

select running_processes from apps.fnd_concurrent_queues where concurrent_queue_name = 'WFMLRSVC';

select component_status from apps.fnd_svc_components where component_id = (select component_id from apps.fnd_svc_components where component_name = 'Workflow Notification Mailer');


SELECT a.request_id, d.sid, d.serial# ,d.osuser,d.process , c.SPID FROM apps.fnd_concurrent_requests a, apps.fnd_concurrent_processes b, v$process c, v$session d WHERE a.controlling_manager = b.concurrent_process_id AND c.pid = b.oracle_process_id AND b.session_id=d.audsid AND a.phase_code = 'R'

select fcq.USER_CONCURRENT_QUEUE_NAME Container_Name, DECODE(fcp.OS_PROCESS_ID,NULL,'Not Running',fcp.OS_PROCESS_ID) PROCID, fcq.MAX_PROCESSES TARGET, fcq.RUNNING_PROCESSES ACTUAL, fcq.ENABLED_FLAG ENABLED, fsc.COMPONENT_NAME, fsc.STARTUP_MODE, fsc.COMPONENT_STATUS from APPS.FND_CONCURRENT_QUEUES_VL fcq, APPS.FND_CP_SERVICES fcs, APPS.FND_CONCURRENT_PROCESSES fcp, apps.fnd_svc_components fsc

where fcq.MANAGER_TYPE = fcs.SERVICE_ID and fcs.SERVICE_HANDLE = 'FNDCPGSC' and fsc.COMPONENT_STATUS = 'RUNNING' and fsc.concurrent_queue_id = fcq.concurrent_queue_id(+) and fcq.concurrent_queue_id = fcp.concurrent_queue_id(+) and fcq.application_id = fcp.queue_application_id(+) and fcp.process_status_code(+) = 'A'order by fcp.OS_PROCESS_ID, fsc.STARTUP_MODE

Sunday, July 19, 2020

Oracle EBS CPU July 2020 Patches

Doc : Oracle E-Business Suite Release 12 Critical Patch Update Knowledge Document (July 2020) (Doc ID 2679563.1)

Application Patch

ORACLE APPLICATIONS RELEASE 12.2: CPU PATCH FOR JUL 2020
Update31198342
ProductOracle Applications Utilities
ReleaseR12
PlatformOracle Solaris on SPARC (64-bit)
BuiltJUL-14-2020 03:37:24
Preparation Tasks The tasks in this section can be completed without taking any Application services or users offline.
Required Code levels [required]
This patch requires additional code levels to have been successfully
applied to your system before it can be applied.  These code levels,
as at the time that this patch was built, are listed below.  Please check
'My Oracle Support' to determine if any of these have been superseded
  • 12.2.3
  • R12.AD.C.delta.11
  • R12.TXK.C.delta.11
  5. Use SQL*Plus to run the script:

     UNIX:
     $ sqlplus /nolog
     SQL> @$ORACLE_HOME/appsutil/admin/adgrants.sql 

     Windows:
     C:\> sqlplus /nolog
     SQL> @%ORACLE_HOME%\appsutil\admin\adgrants_nt.sql 
Apply The PatchFor 12.0.X / 12.1.X / pre-upgrade patches (using adpatch), you must shut down all Application tier services before performing the tasks in this section. For 12.2.X patches (using adop), you can perform the tasks in this section without shutting down the Application tier services.
Apply patch [required]
Apply the patch with ADOP:
  adop phase=apply patches=31198342

Based on on the system 

Footnote 1: Additional Patches to be Applied After the CPU Patch

DB Patch
Oracle Database 19.0.0.0Combo OJVM Release Update 19.8.0.0.200714 and Database Release Update 19.8.0.0.200714 Patch 31326362See Document 2664876.1Critical Patch Update (CPU) Program July 2020 Availability Document (PAD). Note that patches listed for this product are yet to be fully tested with Oracle E-Business Suite.
Oracle Database 12.1.0.2OJVM PSU 12.1.0.2.200714 and Database PSU 12.1.0.2.200714 Combo Patch 31326396See Document 2664876.1Critical Patch Update (CPU) Program July 2020 Availability Document (PAD).


Oracle WebLogic Server 10.3.6.0PSU 10.3.6.0.200714 (Patch 31178492)See Document 2664876.1Critical Patch Update (CPU) Program July 2020 Availability Document (PAD).
When applying the Oracle WebLogic Server PSU, perform the following steps in case of conflicts:
  1. Roll back the reported conflicting patches.
  2. Apply the current Oracle WebLogic Server (WLS) PSU.
  3. Apply the overlay patches, if the patches have not already been included in the WLS PSU.
See Footnote 2 for known patch conflicts and corresponding overlay patches. If you encounter conflicts with any other patches, see Document 1306505.1Announcing Oracle WebLogic Server PSUs (Patch Set Updates).
Oracle Fusion Middleware 11.1.1.9 - Web Tier HomeSecurity Patch Update CPUJul2020 for OSS Patch 31304503See Document 2664876.1Critical Patch Update (CPU) Program July 2020 Availability Document (PAD).
We recommend that you enable TLS by following Document 1367293.1Enabling TLS in Oracle E-Business Suite Release 12.2, to increase security and to ensure that your application will continue to work after this patch is applied.
Note: In addition to following the instructions to enable TLS found in Document 1367293.1, you will need to follow the instructions in Document 2555355.1Prerequisite Steps to Configure Oracle Fusion Middleware 11.1.1.9 Components for Oracle E-Business Suite Release 12.2 Before Applying the July 2019 and Later FMW OSS Security Patch, to update the Oracle Fusion Middleware 11.1.1.9 default certificates.
Oracle Java (Java SE [JRE] Plug-in)Oracle Java Runtime Environment (JRE) 8 Update 261 Patch 31311324
Oracle JRE 7 Update 271 Patch 31311349
See Document 2682801.1Critical Patch Update (CPU) July 2020 for Oracle Java SE.
You should also review Document 393931.1, Deploying JRE (Native Plug-in) for Windows Clients in Oracle E-Business Suite Release 12, for information about the Java versions to use and the procedures to follow.
Review the requirements in Document 1591073.1Enhanced Jar Signing for Oracle E-Business Suite, to ensure compatibility with the latest Java CPU.
Oracle Java (JDK)Oracle JDK 7 Update 271 Patch 31311341See Document 2682801.1Critical Patch Update (CPU) July 2020 for Oracle Java SE.
You should also review the following My Oracle Support knowledge documents to uptake the latest JDK:
  • Document 1530033.1, Using the latest JDK 7.0 update with Oracle E-Business Suite Release 12.2.
  • Document 1467892.1, Using JDK 7.0 latest update with Oracle E-Business Suite Release 12.0 and 12.1.
Oracle Java (Java Web Start)Oracle JRE 8 Update 261 Patch 31311324See Document 2188898.1Using Java Web Start with Oracle E-Business Suite.

Footnote 2WLS Patch Conflicts and Corresponding Overlay Patches

The following table lists known patch conflicts and corresponding overlay patches to apply. If you encounter conflicts with any other patches, refer to Document 1306505.1Announcing Oracle WebLogic Server PSUs (Patch Set Updates).
Previous Overlay (SU) Patch Associated with Conflicting WLS PatchCurrent Overlay (SU) Patch to Apply
K25M, XIDD, RVBS, NJVF, K4AL, A5H6, QMJP, G9L4, UNUT, Z9PC, 6TP5, CW6U, CF5U, PSVV, S5C9, 47D2, D446, WT48, 9KCT, JJJF, CQ63, AYDX, 45ET , HMR4, TR6Y, CJXI, SLVI, WUH8, 159X, KRDE, X6TC, EV8H, WQKK, 96N5, R1EY, F5QI, ISBJ, PG5J, 1UWC, 7F9C, M3C7, EQDE, HJ2T, ZH8H, ZF83, 7P2C, EN8U, 9XLF, 7E7M, ZHMT, LLU8, IIYG, IJG4, 9UBP, 4R4W, IVAB, SUPD, BWKV, XGXMThere is no need for an overlay, as it has been included in the current PSU.
FC8V13845626 version 10.3.6.0.200714 (DTN2)

Table 3: Security Patches for Technology Stack Components With No New Patch in This CPU

Oracle ProductLatest Security PatchesMy Oracle Support Knowledge Document References and Supplementary Comments
Oracle Database 19.0.0.0Combo OJVM Release Update 19.7.0.0.200414 and Database Release Update 19.7.0.0.200414 Patch 30783543See Document 2633852.1Critical Patch Update (CPU) Program April 2020 Availability Document (PAD). Note that patches listed for this product are yet to be fully tested with Oracle E-Business Suite.
Oracle Fusion Middleware 11.1.1.9 - Web Tier HomeSecurity Patch Update CPUApr2020 for OHS Patch 31047338See Document 2633852.1Critical Patch Update (CPU) Program April 2020 Availability Document (PAD).
Oracle Fusion Middleware 11.1.1.9 - Oracle Common HomeSecurity Patch Update CPUOct2019 Patch 30368663See Document 2568292.1Critical Patch Update (CPU) Program October 2019 Availability Document (PAD).
Only apply the OUI portion of this patch. Follow the README under the oui directory to apply the patch.
Oracle Fusion Middleware 11.1.1.7 - Web Tier HomeSecurity Patch Update CPUJan2018 for OHS Patch 27197885
Merge Patch 19849290
See Document 2325393.1Patch Set Update and Critical Patch Update January 2018 Availability Document.
The merge patch is required for the Oracle Fusion Middleware component Oracle Security Service (OSS).
Oracle Fusion Middleware 11.1.1.7 - Oracle Common HomeSecurity Patch Update CPUJan2018 Patch 27251436See Document 2325393.1Patch Set Update and Critical Patch Update January 2018 Availability Document.
Only apply the OUI portion of this patch. Follow the README under the oui directory to apply the patch.
Database 11.1.0.7 client patches for FMW 11.1.1.7 or FMW 11.1.1.9PSU Patch 22290164 for UNIX
Bundle Patch 22607089 for Windows 32-Bit
Bundle Patch 22607090 for Windows x64
See Document 2074802.1Patch Set Update and Critical Patch Update January 2016 Availability Document.

Thursday, June 11, 2020

How to generate RSA Key

rsa - an old algorithm based on the difficulty of factoring large numbers. A key size of at least 2048 bits is recommended for RSA; 4096 bits is better. RSA is getting old and significant advances are being made in factoring. Choosing a different algorithm may be advisable. It is quite possible the RSA algorithm will become practically breakable in the foreseeable future. All SSH clients support this algorithm


@suthakar$pwd
/home/oracle/.ssh
@suthakar$ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (/home/oracle/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/oracle/.ssh/id_rsa.
Your public key has been saved in /home/oracle/.ssh/id_rsa.pub.
The key fingerprint is:
cd:3c:69:fa:b3:68:a6:6a:e0:63:eb:df:a5:4c:8c:4d oracle@suthakar.prince
The key's randomart image is:
+--[ RSA 2048]----+
|                 |
|                 |
|                 |
|         + .     |
|      E S B      |
|  .  =   o .     |
| . .. + o        |
|  + .+ ooo.      |
| oo=o.=+. oo     |
+-----------------+
@suthakar$pwd

@suthakar$ls -ltr
total 12
-rw-r--r--. 1 oracle oinstall  392 Feb  5  2018 known_hosts_org
-rw-r--r--. 1 oracle oinstall  404 Jun 11 21:52 id_rsa.pub
-rw-------. 1 oracle oinstall 1675 Jun 11 21:52 id_rsa
@suthakar$
you will see publickey and private key.

how to check the keylength
 ssh-keygen -lf id_rsa.pub
2048 cd:3c:69:fa:b3:68:a6:6a:e0:63:eb:df:a5:4c:8c:4d id_rsa.pub (RSA)
@suthakar$
cat id_rsa.pub >>authorized_keys
@suthakar$ls -ltr
total 16
-rw-r--r--. 1 oracle oinstall  392 Feb  5  2018 known_hosts_org
-rw-r--r--. 1 oracle oinstall  404 Jun 11 21:52 id_rsa.pub
-rw-------. 1 oracle oinstall 1675 Jun 11 21:52 id_rsa
-rw-r--r--. 1 oracle oinstall  404 Jun 11 22:03 authorized_keys

scp  authorized_keys username@xxxx :/user/home/oracle/.ssh/

 

16399723 ==> ABORT - Used to create uabort.drv file.


Patch Wizard/Applied Patches shows patches which haven't been applied. (Doc ID 2196963.1)

Wednesday, June 10, 2020

Exadata healthCheck

Oracle Exadata Database Machine EXAchk or HealthCheck (Doc ID 1070954.1