Tuesday, 22 September 2015

PatchWizard - Analyze Specific Patches completes with Error R12 RPC3

EBS : 12.1.3
DB   :

Analyzing RPC3(20203366) patch kept completing with status Error 
I was trying to analyze RPC3 patch with patchwizard "Analyze Specific Patches" option. Downloaded the patch to patch staging area and and submitted for patch analysis with "Analyze Specific Patches" option

zip files 1 through 7 p20203366_12.1.0_R12_LINUX_* were available in the patch stage directory /u01/oracle/patches

Main request error
The set completed normally with outcome Error. The outcome was determined by the stage Submit Patch Download, Upload & Analysis Request (3).

Sub request

Sub Request Logfile has these contents

Downloading patches for bug: 20203366
User has not specified any codeline for the patch 20203366Found the following patch(es) on metalink: Branchline: p20203366_12.1.0_R12_LINUX_7of7.zip Customer's onsite codeline (AU) : 1  Customer's codeline does not match  Ignoring download of patch p20203366_12.1.0_R12_LINUX_7of7.zip WARNING: No patches found for bug: 20203366ERROR: No patches found for the patch list: 20203366----------------------------End of patch download----------------------------End of Patch Download Program for patch list.... [Sep 17, 2015 11:29:11 AM]+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++Calling Patch Upload Program for Patchlist.... [Sep 17, 2015 11:29:11 AM]+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Starting Upload Process... Parameter List  20203366Program Execution Start time: [Sep 17, 2015 11:29:11 AM]Stage Dir is  /u01/oracle/patchesEntity hastable created. Total entries : 239Starting processing patch 20203366 at [Sep 17, 2015 11:29:11 AM]****No codeline specifiedLooking for appropriate patch in the stage directory : /u01/oracle/patchesWARNING: The zip file for patch  20203366 does not exist in the stage directory   /u01/oracle/patchesEnd processing patch 20203366 at [Sep 17, 2015 11:29:11 AM]
**WARNING: No patch metadata uploaded**Patches which encountered problems during Upload :

The patches were kept under /u01/oracle/patches in fact it was a requirement since 12.1.2 to be kept under ad/nonad

After creating new directory nonad and placing patch zip files under that directory patchwizard was able to continue but failed at a later stage.

Applied patch wizard patch 20390398(R12.ADO.B.delta.7) which finally solved the issue.

Now patchwizard is able to complete the request and give patch analysis

Thursday, 8 January 2015

Transferring  FSG from one instance to another
Transferring FSG from once instance to another is very easy using seeded 
'Program - FSG Transfer' concurrent program.

There are two steps involved 
1. Create a database link(db link that connects to source) in the target instance
2. Run Program - FSG Transfer

Creating Database link
On the target instance create a database link to connect to source instance.

It can be created using Database Links screen under General Ledger Controller  Responsibility

General Ledger > Setup>System>Database Links

Database Name : Name of the Source Database

Description: Description to understand what this dblink is for

Connect String: Different methods can be used to connect to source database like Esyconnect/connection descriptor/Service name alias

Example using different methods

By using Connect Descriptor


By EasyConnect

If you want use service_name aliase create an entry in tnsnames and use that

Domain Name: Enter domain name of your database server

If the info provided is correct it will create a database link

Running 'Program - FSG Transfer' to transfer FSG

Now use Program - FSG Transfer to transfer FSG from source to Target

Note: The transfer program is run from Target machine, so always make sure you are creating db link and submitting "Program - FSG Transfer " on the target instance