Monday, June 29, 2015

Script to collect diagnostic information required to analyze AD and TXK issues in EBS Release 12.2.x



Patch 19045166: SCRIPT TO COLLECT DIAGNOSTIC INFORMATION FOR 12.2 AD/TXK BUGS


This script has to be run in all the middletier nodes of the instance.

To use the script:
1. Unzip the patch to a new folder
2. Confirm the following files are present after unzipping.
        adzddbdetails.sql
        adzddiagnostic.pl
        adzdedndetails.sql
        README.txt
3. Source the Apps Tier run environment file
4. Run the master perl script adzddiagnostic.pl with the command "perl adzddiagnostic.pl"
5. Supply the apps database user password the script prompts for.
6. The script creates a file "diagnostic_info_.*" in the working directory.

7. Attach the file to the SR for analysis.

[dba1mgr@xxxx /apps/dba1mgr/UpgradePatches/12.2.4Upgradepatches]$ perl adzddiagnostic.pl

Enter the APPS password:

Please wait. Validating credentials...
Removing information collected from previous runs, if any...

$Header: /source/addev/ad/12.0/diag/bin/RCS/adzddiagnostic.pl,v 120.0.12020000.4 2015/03/27 11:48:02 rraam noship

Step  1 of 22 : Creating directories required to copy the diagnostic information....Done
Step  2 of 22 : Getting adop -status information....Done
Step  3 of 22 : Copying the ADOP logs folder....Done
Step  4 of 22 : Spooling contents of AD_ZD_LOGS table....Done
Step  5 of 22 : Spooling contents of AD_ZD_DDL_HANDLER table....Done
Step  6 of 22 : Getting the required information from Database....Done
Step  7 of 22 : Getting edition specific information from run edition....Done
Step  8 of 22 : Copying run and patch context files....Done
Step  9 of 22 : Getting adutconf report....Done
Step 10 of 22 : Getting perl code level in the instance....Done
Step 11 of 22 : Getting C code level in the instance....Done
Step 12 of 22 : Getting listener.ora and tnsnames.ora....Done
Step 13 of 22 : Checking if adop process is active....Done
Step 14 of 22 : Copying Instance Logs from run file system....Done
Step 15 of 22 : Copying Instance Logs from patch file system....Done
Step 16 of 22 : Copying Domain configuration file....Done
Step 17 of 22 : Downloading context file from database....Done
Step 18 of 22 : Copying inventory.xml....Done
Step 19 of 22 : Executing txkInventory.pl....Done
Step 20 of 22 : Copying /etc/hosts....Done
Step 21 of 22 : Trying to connect to patch edition....Done

Completed collecting all the diagnostic information.

Step 22 of 22 : Archiving the diagnostic_info folder....Done

Please provide the file diagnostic_info_tblnxdbtst.tar.bz2 for further analysis.


Wednesday, June 24, 2015

ADOP Error: The table APPLSYS.TXK_TCC_RESULTS does not exist The EBS Technology Codelevel Checker needs to be run on the following node(s)


Download Patch 17537119 from My Oracle Support  and apply on DB Tier.If any Pre-req patches are missed from the out put please apply those patches.

2. Read the Instructions to run the Database checker utility (checkDBpatch.sh or checkDBpatch.cmd for Windows) from the patch's readme.

3. Follow the steps below :
- Login as the RDBMS ORACLE_HOME owner on the DB tier.
- Unzip the patch
- Confirm the following files are present after unzipping.
    checkDBpatch.sh
    checkDBpatch.cmd
    txk_R1220_DB_base_bugs.xml
    README.txt
- Run the script and Supply the values the script prompts for.
- The script provides a list of one-offs that are either missing, or need to be rolled back.
- Take the appropriate actions based on the results provided by the script.

 +===============================================================+
 |    Copyright (c) 2005, 2014 Oracle and/or its affiliates.     |
 |                     All rights reserved.                      |
 |               EBS Technology Codelevel Checker                |
 +===============================================================+

Executing Technology Codelevel Checker version: 120.24
Enter the full path to the DB Context file :/oracle/xxxx/oradata/VISDB/11.2.

Bugfix XML file version: 120.0.12020000.23

Proceeding with the checks...

Getting the database release ...
Setting database release to 11.2.0.3

 DB connectivity successful.

Created the table to store Technology Codelevel Checker results.

STARTED Pre-req Patch Testing : Wed Jun 24 09:52:12 EDT 2015

Log file for this session : ./checkDBpatch_2527.log

Got the list of bug fixes to be applied and the ones to be rolled back.
Checking against the DB ORACLE_HOME...

Opatch is at the required version.

Found patch records in the inventory.

All the required one-offs are not present in the given ORACLE_HOME
List of missing bug fixes:
14046443
17912217
18260550
18419770
18614015
18685209
18689530
18828868
19393542
19472320
19791273
19896336
19949371
20294666

** Please refer to MOS Doc ID "1594274.1:Oracle E-Business Suite Release 12.2: Consolidated List of Patches and Technology Bug Fixes" to find the corresponding patch that delivers the bug fix. If an overlay patch is needed for any particular patch listed, the footnote for that patch also applies to the overlay patch.**

Stored Technology Codelevel Checker results in the database successfully.

Apply the missing bug fixes and run the script again to confirm.

FINISHED Pre-req Patch Testing : Wed Jun 24 09:52:14 EDT 2015

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

Applied all the list of patches.17912217 is superseeded of 20294666 Patch.

How To Run The 12.2 EBS Technology Code Level Checker (ETCC) ? (Doc ID 2008451.1)

Tuesday, June 23, 2015

10.3.6.0.7 PSU Patch Application Process while Upgrading 12.2.0 to 12.2.4

10.3.6.0.7 PSU Patch Application Process:

My current weblogic version is 10.3.6 .Which is come by while Installing 12.2.0 Oracle applications.
In my way of upgrading to 12.2.4 I ahve to apply the latest patches to my current weblogic version.

Using the smart update utility is easy to apply the patches on weblogic.

Go to the FMW_HOME/utils/bsu location you will be find bsu.sh file.

Run sh bsu.sh file on vnc server.

Before this step please down load the patch and unzip the patch 17572726 on FMW_FOME/utils/bsu/cache_dir.





1. Remove following patches, they are included in 10.3.6.0.7 
VFS8,D33T,ll4G 







All patches has been removed.Now we are going to apply the main PSU patch.





2. Complete following steps for patch YIJF 

c. Apply patch 13729611 for 10.3.6.0.7 (You must download the 10.3.6.0.7 version for YIJF:13729611) 

Downloaded the latest patch 13729611 and kept in cache_dir folder.
When using the bsu.sh script to install an Oracle WebLogic Server patch, you may receive an out of memory error for either "GC overhead limit" or "Java heap space". In such a case, run the commands shown below (the examples are for UNIX).For any overlay patches we have to change bsu.sh file as below.

MEM_ARGS="-Xms256m -Xmx512m
to

                        MEM_ARGS="-Xms512m -Xmx1024m -XX:+UseParallelGC"


Now Re launch the ./bsu.sh It will prompt the patches information as below.
 Click and Apply BLTG patch which is repalced YIJF .

Now the PSu patch hasbeen applied succesfully.

Monday, June 22, 2015

How to Install EM 12c Agent in Silent Mode using a Response File

Installation Steps:

1. Get the agent image:

login to the OMS_HOME/bin 

Run emcli login to establish a session.

[gridagt@xxxxxx bin]$ ./emcli login -username=sysman -password=welcome123
Login successful
[gridagt@xxxxx bin]$ ./emcli sync
Synchronized successfully
[gridagt@xxxxx bin]$ ./emcli get_supported_platforms
-----------------------------------------------
Version = 12.1.0.4.0
 Platform = Linux x86-64
-----------------------------------------------
Platforms list displayed successfully.

[gridagt@xxxxxx bin]$ ./emcli get_agentimage -destination=/apps/gridagt/agentimage -platform="Linux x86-64" -version=12.1.0.4.0

=== Partition Detail ===
Space free : 22 GB
Space required : 1 GB
Check the logs at /apps/gridagt/OEM12c/12.1.0/gc_inst/em/EMGC_OMS1/sysman/emcli/setup/.emcli/get_agentimage_2015-05-11_10-33-17-AM.log
Downloading /apps/gridagt/agentimage/12.1.0.4.0_AgentCore_226.zip
File saved as /apps/gridagt/agentimage/12.1.0.4.0_AgentCore_226.zip
Downloading /apps/gridagt/agentimage/12.1.0.4.0_PluginsOneoffs_226.zip
File saved as /apps/gridagt/agentimage/12.1.0.4.0_PluginsOneoffs_226.zip
Downloading /apps/gridagt/agentimage/unzip
File saved as /apps/gridagt/agentimage/unzip
Agent Image Download completed successfully.
EM 12c: How to Install EM 12c Agent in Silent Mode using a Response File (Doc ID 1360083.1)

2. Steps to deploy the agent:

  • Transfer the downloaded ZIP file to a temporary directory (/tmp) on the destination host where you want to install the Management Agent.

Stop the WF emails after clone.


1) Update the notifications you do not want sent, in the WF_NOTIFICATIONS table.  Check the WF_NOTIFICATIONS table. Records where status = 'OPEN' and mail_status = 'MAIL' are notifications that will have an e-mail notification sent.

SQL> select notification_id, status, mail_status, begin_date from WF_NOTIFICATIONSwhere status = 'OPEN' and mail_status = 'MAIL';   Above script willshow which notifications are waiting to be e-mailed.  
 
To update a notification so that it will not get e-mailed. Set the MAIL_STATUS = 'SENT'. The
mailer will think the e-mail has already been sent and it will not send it again.. (Users can 
still reply to the notification from the worklist page in the applications). 
Example:
update WF_NOTIFICATIONS set mail_status = 'SENT' where mail_status = 'MAIL'; 
OR
update wf_notifications
set mail_status = 'SENT'
where end_date is not null
and status = 'CLOSED'
and MAIL_STATUS = 'MAIL';
 
 
This will update all notifications waiting to be sent by the mailer. 
2. Then run the script wfntfqup.sql to purge the WF_NOTIFICATION_OUT queue and rebuild it with data currently in the WF_NOTIFICATIONS table. This is what purges all notifications waiting in the queue to be sent.  It will then populate the queue with the current data in the wf_notifications table. 
Since you have changed the mail_status = 'SENT" it will not enqueue these messages again.. Only the ones where mail_status = 'MAIL' and status = 'OPEN' will be placed in the WF_NOTIFICATION_OUT queue and sent by the mailer. 


sqlplus apps/apps @$FND_TOP/patch/115/sql/wfntfqup.sql 
SQL*Plus: Release 10.1.0.5.0 - Production on Mon Jun 22 16:10:37 2015

Copyright (c) 1982, 2005, Oracle.  All rights reserved.


Connected to:
Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

SQL> @@wfntfqup.sql

PL/SQL procedure successfully completed.

Elapsed: 00:00:03.01

Commit complete.

Elapsed: 00:00:00.00
**** TEMPORARY TABLES / AQs created ****

PL/SQL procedure successfully completed.

Elapsed: 00:00:00.12
**** Messages backed up ****

Commit complete.

Elapsed: 00:00:00.00
**** wfaqback.sql completed,  executing SQLs from wfntfqup

PL/SQL procedure successfully completed.

Elapsed: 00:02:10.21
***  invoking wfaqrenq.sql ******
*** Re-enqueing messages

PL/SQL procedure successfully completed.

Elapsed: 00:00:00.12

Commit complete.

Elapsed: 00:00:00.01
***** Re-enqueue OF Alerts completed *****
Disconnected from Oracle Database 11g Enterprise Edition Release 11.1.0.7.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options

847889.1 - Stop Workflow Notification Emails During Clone
828812.1 - How To Stop Old Outbound Workflow Notification Email Messages During Clone Activity

562551.1 - Workflow Java Mailer FAQ
Which Table Stores the NEW Test Address 'set override address'?


SQL> select fscpv.parameter_value
from fnd_svc_comp_params_tl fscpt
,fnd_svc_comp_param_vals fscpv
where fscpt.display_name = 'Test Address'
and fscpt.parameter_id = fscpv.parameter_id;


3. Now start the mailer.