Oracle Application Interview Questions and Answers-3

Page-3

31: What are the problems u have faced while shutting down applications?
A : While shutting down application generally concurrent manager won’t go down because some or the other request may be running. We will see what are the concurrent requests running by querying fnd_concurrent_requests, fnd_concurrent_program_vl, v$session, v$process and v$sqltext.
If that request is only doing some select statement then we will kill those requests, otherwise we will check what time it will take to complete by querying the previous runs of that request and then we will decide what to do.

32: Where is HTML Cache stored in Oracle Apps Server?
A : Oracle HTML Cache is available at $COMMON_TOP/_pages,
$IAS_ORACLE_HOME/Apache/modplsql/cache

33: How do you know if a specific Oracle patch has been applied in apps to your environment?
A : Use table ad_bugs in which column bug_number is the patch number.

34: For a PL/SQL based concurrent program do you have to issue a commit at the end?
A : The concurrent program runs within its own new session. In APPS, the default database setting enforces a commit at the end of each session. Hence no explicit COMMIT is required.

35: What is a Jinitiator?
A : Jinitiator is the Oracle JVM used to run the applet instead of using browsers own JVM.
When we access forms applet first time, oracle jinitiator will be installed automatically.

36: Which adpatch drivers should be run first? If they are run in the wrong order can they be run again?
A : You should run them in alphabetical order c, d, then g.
you can run them again in the correct order.

37: Where (on which tier) do you run the three different patch drivers?
A : The "c" and "g" drivers are run on all tiers.
The "d" driver is only run on the database tier.

38: What are various modes of applying a patch?
A : adpatch can apply patches in
Test mode : In test mode, AutoPatch does not apply the patch. Instead, it lists each file it would have copied, relinked, executed, or generated and shows exactly what actions it would have performed had it applied the patch.
Pre-install mode : Pre-install mode is generally used during the upgrade process to update AD utilities, apply pre-upgrade patches, or work around other patching issues.
Non-interactive mode : Non-interactive patching is a way to avoid some of the prompts and automate the patching process. For this you have have to create defaults file

39: Can we invoke more than one adadmin session simultaneously? If so when? If not Why?
A : Yes & No you can run adadmin if FND_INSTALL_PROCESSES is NOT locked by any session. If this table is in use by any session then you can’t run adadmin at same time.

40: I am applying a patch, can I open another session in another node and run adpatch?
A : No

41: How to determine Oracle Apps 11i Version?
A : select RELEASE_NAME from fnd_product_groups;
You should see output like
RELEASE_NAME-----------------------11.5.10.2

42: How to find opatch Version?
A : opatch is utility to apply database patch, In order to find opatch version execute "$ORACLE_HOME/OPatch/opatch version"

43: How to find out invalid objects in the database?
A : select count(*) from dba_objects where status ='INVALID'

44: What are the different types of patches?
A : oneoff, mini packs, family packs, maintanance packs, rollup pathches, colsolidated patches.

45: What is a oneoff patch?
A : An oneoff patch is a small patch of (20-90K size) without any pre-req’s

<< page-2 >>                                                                                                                 << page-4>>