Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

Saturday, November 18, 2017

Concurrent Manager


FNDFS and FNDSM

application listener support two services FNDFS and FNDSM.

Apps Listener usually run on All Oracle Applications 11i Nodes with listener alias as APPS_$SID is mainly used for listening requests for services like FNDFS & FNDSM.

FNDFS or the Report Review Agent (RRA) is the default text viewer within Oracle Applications, which allows users to view report output and log files. Report Review Agent is also referred to by the executable FNDFS.

FNDSM is the Service manager. FNDSM is executable & core component in GSM ( Generic Service Management Framework ). You start FNDSM services via APPS listener on all Nodes in Application Tier.

Scenario  where we can't see the output of Concurrent Requests:
check the fndwrr.exe size in production and compare it with  Test Instance.
fndwrr.exe is present in  $FND_TOP/bin
If there is any difference then relink the FNDFS executable.
adrelink.sh force=y "fnd FNDFS" 

https://oraclehub.wordpress.com/2013/05/08/not-able-to-view-concurrent-request-output/

Application Patch

Bug Definition: A software bug is an error, flaw, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways.
AD_BUGS: 
Holds information about the various Oracle Applications bugs whose fixes have been applied (ie. patched) in the Oracle Applications installation.
AD_APPLIED_PATCHES:
Holds information about the "distinct" Oracle Applications patches that have been applied.
If 2 patches happen to have the same name but are different in content (eg. "merged" patches), then they are considered distinct and this table will therefore hold 2 records.
A patch can deliver solution for more than one bug, so ad_applied_patches may not give u the perfect information as in case of ad_bugs.

Difference:

AD_BUGS contains all bug numbers fixed on your system, while AD_APPLIED_PATCHES contains all patch numbers which were applied to your system only.

 if you use merged patches, always check AD_BUGS.

select bug_number from ad_bugs where bug_number in ('&bug_number');

For example: if you apply 11.5.10 CU2, it will add a row with patch_name=3480000 to AD_APPLIED_PATCHES and it will insert thousands of entries in AD_BUGS (including 3480000).



What are the different types of patches?
oneoff, mini packs, family packs, maintanance packs, rollup pathches, colsolidated patches.
What is a oneoff patch?
An oneoff patch is a small patch of (20-90K size) without any pre-req’s
An one-off patch is a small patch (of without any pre-requisites) to fix a bug.
What is a mini pack ?
A mini pack is one which will upgrade any product patchset level to next level like AD.H to AD.I
What is Family pack ?
A Family pack is one which will upgade the patchset level of all the products in that family to perticular patchsetlevel.
What is Maintanance pack ?
A maintanance pack will upgrade applications from one version to another like 11.5.8 to 11.5.9
What is a Rollup patch?
A rollup patch is one which will deliver bug fixes identified after the release of any major application versions like 11.5.8/11.5.9
What is consilidated patch?
Consolidated patches will come into pictures after upgrades from one version of applications to anoter, all post upgrade patches will a consolidated and given as consolidated patch.
 What are the tables adpatch will create and when?
Adpatch will create FND_INSTALL_PROCESSES and AD_DEFERRED_JOBS table when it will apply d,g and u drivers.
What is the significance of FND_INSTALL_PROCESSES and AD_DEFERRED_JOBS table?
FND_INSTALL_PROCESSES table will store the worker information like what job is assigned to which worker and its status.
AD_DEFERRED_JOBS will come into picture when some worker is failed, it will be moved to AD_DEFERRED_JOBS table, from where again adpatch will take that job and try to resign, after doing this 3 times if still that worker is failing, then adpatch will stop patching and throw the error that perticular worker has failed. We need to trouble shoot and restrart the worker.
While applying a patch if that patch is failing because of a pre-req then how you will apply that pre-req patch and resume with the current patch?
We need to take the backup of FND_INSTALL_PROCESSES and AD_DEFERRED_JOBS tables and restart directory at APPL_TOP/amdin/SID and then use adctrl to quit all the workers. Then apply the pre-req patch , after that rename u r restart directory to its original name and create FND_INSTALL_PROCESSES and AD_DEFERRED_JOBS tables from the bcakup tables. Start adpatch session and take the options want to continue previous session.
What is the significance of backup directory under u r patch directory?
When we apply a patch it will keep the copy of the files which its going to change in file system.
How adpatch will know the file versions of the patch delivered files?
With each patch a file with name f.ldt is delivered , which contain the file versions of the files dilivered with the patch. Adpatch will use this file to compare the file versions of files its delivering with the file on file system.
How adpatch knows what are the pre-req’s for the patch which it is applying?
With every patch a file called b.ldt file will be delivered which contain the pre-req information. adpatch load this into databse using FNDLOAD and check , whether those pre-req patches were applied or not.

What are the different modes you can run your adpatch?
1.Interactive – default mode

2.Non interactive – Use defaults files to store prompt values

(adpatch defaultsfile= interactive=no)

3. Test – Without actually applying a patch just to check what doing.(adpatch apply=no)

4. Pre-install – (adpatch preinstall=y)

This mode will be usefull to discrease upgrade downtime as its applies bus fixes without running SQL,EXEC and generate portion of patch.

Adpatch Reducing Patching Downtime:
Use a shared application-tier file system
Distribute worker processes across multiple servers
Merge multiple patches using AD Merge Patch
Run AD Patch in non-interactive mode
Defer system-wide database tasks until the end
Avoid resource-related bottlenecks
Increase batch size (Might result into negative )
adpatch options=noautoconfig

Checkfile

The chekfile option of adpatch tells adpathc to check for already executed exec, SQL, and exectier commands.

adpatch options=nocheckfile



Compile Database

By defaulty autopatch compiles the invalid objects after the patch application,

adpatch options=nocompiledb



Compile JSP

By defaulty autopatch compiles the java server pages (jsp) after the patch application,

adpatch options=nocompilejsp



adpatch options=nocopyportion

adpatch options=nodatabaseportion

adpatch options=nogenerateportion



Maintenance Mode

If you wish to apply a patch regardless of the system being in maintenance mode you can use options=hotpatch.

adpatch options=hotpatch



Pre requisite Patch Check

If you wish adpatch not to check for pre requisite patches before application of the main patch

adpatch options=noprereq



Maintain MRC

You can use the maintainmrc option to specify weather you wish adpatch to execute the Maintain MRC schema as a part of the patch application or not.


adpatch options=nomaintainmrc

Where would I find .rf9 file, and what exactly it does?
These files are used during restart of a patch in case of patch failure because of some reason.

What are .odf file in apps patch?
odf stands for Object Description Files used to create tables & other database objects while applying a patch.

What is .lgi file?
lgi files are created with patching along with .log files . .lgi files are informative log files containing information related to patch. You can check .lgi files to see what activities patch has done.