Explore topic-wise InterviewSolutions in .

By CHANGING the ORDER of the columns that are used in the index, in the Where condition, or by concatenating the columns with some CONSTANT VALUES.

By changing the order of the columns that are used in the index, in the Where condition, or by concatenating the columns with some constant values.

AUTOCONFIG is UTILITY to configure your Oracle Application ENVIRONMENT. XML file is repository of all configuration from which AutoConfig picks configuration and POPULATES related files.

Autoconfig is Utility to configure your Oracle Application environment. xml file is repository of all configuration from which AutoConfig picks configuration and populates related files.

In order to check list of files CHANGED during autoconfig , you can run adchkcfg UTILITY which will generate HTML report. This report will list all files and profile OPTIONS going to CHANGE when you run AutoConfig.

In order to check list of files changed during autoconfig , you can run adchkcfg utility which will generate HTML report. This report will list all files and profile options going to change when you run AutoConfig.

In Oracle DATABASE there is something called Cost Based OPTIMIZER (CBO) which other than doing many things also does query optimization. That is it determines the best or optimum method to run a query. Now when large changes to the data or database take place, the system performance may get slow. DBMS_STATS is the package which COLLECTS statistics for Cost Based Optimizer. Collecting Statistics lets the CBO know about the best methods for query optimization. The statistics include the Table statistics, Column statistics, Index statistics and System statistics. The DBMS_STATS package INCLUDES the following procedures.

1. GATHER_INDEX_STATS, Index statistics
2. GATHER_TABLE_STATS, Table, column, and index statistics
3. GATHER_SCHEMA_STATS,Statistics for all OBJECTS in a schema
4. GATHER_DICTIONARY_STATS,Statistics for all dictionary objects
5. GATHER_DATABASE_STATS,Statistics for all objects in a database 

Of all of the above usually the most used is GATHER_SCHEMA_STATS to gather statistics of all objects within a particular Schema. The Gather Schema Statistics process should be run on a regular basis (weekly at a minimum) and anytime large changes to the data or database take place.

In Oracle Database there is something called Cost Based Optimizer (CBO) which other than doing many things also does query optimization. That is it determines the best or optimum method to run a query. Now when large changes to the data or database take place, the system performance may get slow. DBMS_STATS is the package which collects statistics for Cost Based Optimizer. Collecting Statistics lets the CBO know about the best methods for query optimization. The statistics include the Table statistics, Column statistics, Index statistics and System statistics. The DBMS_STATS package includes the following procedures.

Of all of the above usually the most used is GATHER_SCHEMA_STATS to gather statistics of all objects within a particular Schema. The Gather Schema Statistics process should be run on a regular basis (weekly at a minimum) and anytime large changes to the data or database take place.

By DEFAULT standard LOCATION is $APPLCSF/$APPLLOG, in some cases it can GO to $FND_TOP/log as WELL.

By default standard location is $APPLCSF/$APPLLOG, in some cases it can go to $FND_TOP/log as well.

This DEPENDS on which WORKFLOW MAILER you are running C Mailer or JAVA Mailer.

This depends on which workflow mailer you are running C Mailer or Java Mailer.

CHECKS if a REQUEST in QUEUE can be run in parallel with the RUNNING request.

Checks if a request in queue can be run in parallel with the running request.

If you are running APPS on WINDOWS you'll be SAD to hear that it’s not certified with Windows Operation System. More over you can share across same operation system like LINUX to Linux & SOLARIS to Solaris.

If you are running Apps on Windows you'll be sad to hear that it’s not certified with Windows Operation System. More over you can share across same operation system like Linux to Linux & Solaris to Solaris.

Sharing Application Tier (including APPL_TOP, COMN_TOP, ORA_TOP) across all Middle Tier Nodes in CONFIGURATION is called as Shared Application Tier. So I can SAY shared APPL_TOP is subset of shared Application Tier, INITIALLY shared APPL_TOP came out & based on its advantages & popularity LATER COMMON_TOP & ORA_TOP files were also included & ENTIRE concept is called as Shared Application Tier.

Sharing Application Tier (including APPL_TOP, COMN_TOP, ORA_TOP) across all Middle Tier Nodes in configuration is called as Shared Application Tier. So I can say shared APPL_TOP is subset of shared Application Tier, initially shared APPL_TOP came out & based on its advantages & popularity later COMMON_TOP & ORA_TOP files were also included & entire concept is called as Shared Application Tier.

First you will try to check how far the query has gone (if in v$session_longops for example, or READING some session statistics) and if there is contention with another session (such as a lock for example) because it talks about a 'concurrent request'.

Method 1: Trace the session USING dbms_system.set_sql_trace_in_session (or) if u r using 10g, using dbms_monitor and look at the trace file to identify where the ISSUE is. You can get the explain plan and tune the query.

Method 2:

1. Is this a new query (or) an existing query
2. Look for the wait event associated to this query.
3. Based on the sql hash value, look at the sql_text from v$sql
4. Run an explain plan (or) use oradebug and trace the query if what BIND variables are using and how the data distribution is.
5. Based on the above information, look for when statistics was collected

Once u understand where the problem is, then solutions can be defined ranging from creating sql profiles / stored outlines (or) adding hints to the query and thoroughly test your changes.

Always REMEMBER to make one change and test for performance change. If you make a series of changes, it will be very difficult to isolate which has caused the performance improvement.

First you will try to check how far the query has gone (if in v$session_longops for example, or reading some session statistics) and if there is contention with another session (such as a lock for example) because it talks about a 'concurrent request'.

Method 1: Trace the session using dbms_system.set_sql_trace_in_session (or) if u r using 10g, using dbms_monitor and look at the trace file to identify where the issue is. You can get the explain plan and tune the query.

Method 2:

Once u understand where the problem is, then solutions can be defined ranging from creating sql profiles / stored outlines (or) adding hints to the query and thoroughly test your changes.

Always remember to make one change and test for performance change. If you make a series of changes, it will be very difficult to isolate which has caused the performance improvement.

AD_BUGS holds information about the VARIOUS Oracle Applications bugs whose fixes have been applied (i.e. 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 (e.g. "MERGED" patches), then they are considered distinct and this table will therefore hold 2 records.

AD_BUGS holds information about the various Oracle Applications bugs whose fixes have been applied (i.e. 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 (e.g. "merged" patches), then they are considered distinct and this table will therefore hold 2 records.

UTILITY adrepgen is used to COMPILE Reports. Syntax is given below adrepgen userid=apps<psswd> source = $PRODUCT_TOPsrwfilename.rdf DEST=$PRODUCT_TOPsrwfilename.rdf stype=rdffile dtype=rdffile logfile=x.log overwrite=yes batch=yes dunit=character

Utility adrepgen is used to compile Reports. Syntax is given below adrepgen userid=apps<psswd> source = $PRODUCT_TOPsrwfilename.rdf dest=$PRODUCT_TOPsrwfilename.rdf stype=rdffile dtype=rdffile logfile=x.log overwrite=yes batch=yes dunit=character

FND_INSTALLED_PROCESS and AD_DEFFERED_JOBS are the tables that GET UPDATED while applying a PATCH mainly d or unified driver.

FND_INSTALLED_PROCESS and AD_DEFFERED_JOBS are the tables that get updated while applying a patch mainly d or unified driver.

If in your adctrl there are SIX options shown then seventh is HIDDEN option. (If there are seven options VISIBLE then 8th option is to Skip WORKER depending on ad version).

If in your adctrl there are six options shown then seventh is hidden option. (If there are seven options visible then 8th option is to Skip worker depending on ad version).

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.

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.

1. Login as applmgr and set the environment. For the Windows environment also, you have to test that CLASSPATH contains %JAVA_TOP%, %JAVA_TOP%loadjava.zip
2. Create a PATCH_TOP directory in the Base Directory (at the same level as APPL_TOP, COMMON_TOP, etc: this is just a recommendation) for the patches which will be downloaded. If this directory exists, this step can be skipped. An OS environment variable could be created for this directory. This will be done only one time, when the first patch will be applied.
3. DOWNLOAD the patch you want to apply in PATCH_TOP directory and unzip the patch.
4. Understand the README.txt file and complete the prerequisite or manual steps. Here, if there are any patched to apply as pre-requisite, in general, is created a document with all the steps involving in the PATCHING process and the pre-requisite patches will be applied before the initial patch.
5. Ensure that the PLATFORM variable environment (under UNIX, Linux, Solaris) is set
6. Shut down APPS services. The database services and the listener must be up and running.
7. Enable Maintenance Mode.
8. Start AutoPatch in interactive mode. This task must be done from the directory where the patch driver is/was unzipped. Also, respond to the adpatch prompts. If there are more drivers to apply (there is no unified drive: there could be a database (d), copy (c) or generate (g) driver) restart the adpatch and apply the other patches.
9. Review the log files. By DEFAULT, the LOCATION is $APPL_TOP/admin//log and the file is adpatch.log.
10. Review the customizations (if any). If a customization was modified by this patch, the customization must be applied again.

• USE FNDCPASS to CHANGE APPS password.
• Manually modify wdbsvr.app/cgiCMD.dat files.
• Change any DB links pointing from other INSTANCES.

• TRACE his session (with waits) and use TKPROF to analyze the trace file.
• Take a statspack report and analyze it.
• o/s MONITORING USING top/iostat/sar/vmstat.
• Check for any network bottleneck by using basic tests like ping RESULTS.

The LOCATION of LOG files is determined by PARAMETER $APPLCSF/$APPLLOG and that of output files by $APPLCSF/$APPLOUT.

The location of log files is determined by parameter $APPLCSF/$APPLLOG and that of output files by $APPLCSF/$APPLOUT.

Most LIKELY the FNDFS LISTENER is down. LOOK at the VALUE of OUTFILE_NODE_NAME and LOGFILE_NODE_NAME in the FND_CONCURRENT_REQUESTS table. Look at the FND_NODES table. Look at the FNDFS_ ENTRY in tnsnames.ora.

Most likely the FNDFS listener is down. Look at the value of OUTFILE_NODE_NAME and LOGFILE_NODE_NAME in the FND_CONCURRENT_REQUESTS table. Look at the FND_NODES table. Look at the FNDFS_ entry in tnsnames.ora.

• Check GUEST user/password in the DBC FILE, PROFILE OPTION guest user/password, the DB.
• Check whether APACHE jserv is up.
• Run IsItWorking, FND_WEB.PING, aoljtest, etc.

AutoConfig uses a context file to MAINTAIN key CONFIGURATION FILES. A context file is an XML file in the $APPL_TOP/admin directory and is the centralized repository. When you run AutoConfig it reads the XML files and creates all the AutoConfig managed configuration files. For each configuration file MAINTAINED by AutoConfig, there EXISTS a template file which determines which values to pick from the XML file.

AutoConfig uses a context file to maintain key configuration files. A context file is an XML file in the $APPL_TOP/admin directory and is the centralized repository. When you run AutoConfig it reads the XML files and creates all the AutoConfig managed configuration files. For each configuration file maintained by AutoConfig, there exists a template file which determines which values to pick from the XML file.

Rapid Cloning Steps for Windows R12Source System:

1. Run adpreclone.pl in Database Node
2. Perl $ORACLE_HOMEappsutilscripts$CONTEX_NAMEadpreclone.pl dbTier
3. Run adpreclone.pl in Apps Node
4. Perl $ADMIN_SCRIPTS_HOMEadpreclone.pl appsTier
5. Shut down the Applications and database
6. Change all services type into manual (option)
7. Restart the system (option)
8. Check if any FNDLIBR programs are running or not
9. Take a cold backup of database and applications

Target System:

Prepare your target system as per the SOURCE system configuration

1. Install Windows Server 2003 service pack 2 Enterprise Edition
2. Install Visual Studio 2005
3. Install Active perl
4. Install Cygwin Change make version from 3.81 into 3.80
5. Copy the Source system backup into target system
6. Set perl locations by using existing env file(It varies between DB node and Apps Node, We will set this two times)
7. Goto the $ORACLE_HOMEappsutilclonebin FOLDER and the post clone scripts
8. Run Postclone scripts in db Tier
9. Perl $ORACLE_HOMEappsutilcloneBinadcfgclone.pl dbTier
10. Run Postclone in Apps Tier
11. Perl $COMMON_TOPclonebinadcfgclone.pl appsTier

Finishing Tasks:

1. Update the profile options Rapid clone will update the site level profile options only, we need to update instance level profile options manually
2. Update the printer settings
3. Update the workflow configuration settings

Cloning an Oracle Applications instance will not update the host and instance specific information used by Oracle Workflow. Review the following tables and columns to verify there is no instance specific data in the Workflow configuration on the target system.

Important Notes:

• While running Postclone in appsTier it PROMPTS HOSTNAME, we should give like hostname.domainname for example sys10.sample.com
• While running post clone in appsTier it prompts visual studio directory don’t include BIN folder. For example give like c:vcVC, don’t give like c:vcVCbin

Rapid Cloning Steps for Windows R12Source System:

Target System:

Prepare your target system as per the source system configuration

Finishing Tasks:

Cloning an Oracle Applications instance will not update the host and instance specific information used by Oracle Workflow. Review the following tables and columns to verify there is no instance specific data in the Workflow configuration on the target system.

Important Notes:

Since ICM is down so it can't reach other managers &AMP; can't shutdown them but YES if because of some reason Standard Manager DIES & ICM is already dead Standard managers will not start. The ICM does the work of DISTRIBUTING the CONCURRENT request to standard managers. If ICM goes down the concurrent requests in standard managers will be running fine. But no new request will be assigned to the standard managers. So wait until all your concurrent requests gets completed and then bounce the concurrent managers to start your ICM.

Since ICM is down so it can't reach other managers & can't shutdown them but yes if because of some reason Standard Manager dies & ICM is already dead Standard managers will not start. The ICM does the work of distributing the concurrent request to standard managers. If ICM goes down the concurrent requests in standard managers will be running fine. But no new request will be assigned to the standard managers. So wait until all your concurrent requests gets completed and then bounce the concurrent managers to start your ICM.

Oracle Enterprise Single Sign-On Suite PROVIDES users with unified sign-on and authentication across all their enterprise resources, including desktops, client-server, custom and host-based mainframe APPLICATIONS. EVEN if users travel or SHARE workstations, they can enjoy the flexibility of a single log-on that eliminates the need for multiple usernames and passwords and HELPS enforce strong password and authentication policies.

Oracle Enterprise Single Sign-On Suite provides users with unified sign-on and authentication across all their enterprise resources, including desktops, client-server, custom and host-based mainframe applications. Even if users travel or share workstations, they can enjoy the flexibility of a single log-on that eliminates the need for multiple usernames and passwords and helps enforce strong password and authentication policies.

Choose USERS from the Manage menu to create a new user. This opens the Manage Users dialog box, where you choose New to enter information for a new user.

You provide the following user information:

User :Enter a NAME that identifies the user.

User Type : Select the type of the user.

Usernames :Choose Edit to access the Edit User dialog box where you can associate one or more user names with the user and specify whether the user is AUTHORIZED to create shareable documents.

Other:Provide information that is specific to the client type. For example, for a thin-client workstation, you enter the SHELLS directory of the component where you are creating the user and the Express Server instance to which the user's personal database will be connected.

ADDING a new user creates a user task and sends it to the Task Processor. If you are not running the Task Processor in the background, you must run it in the FOREGROUND to process the user task.

Choose Users from the Manage menu to create a new user. This opens the Manage Users dialog box, where you choose New to enter information for a new user.

You provide the following user information:

User :Enter a name that identifies the user.

User Type : Select the type of the user.

Usernames :Choose Edit to access the Edit User dialog box where you can associate one or more user names with the user and specify whether the user is authorized to create shareable documents.

Other:Provide information that is specific to the client type. For example, for a thin-client workstation, you enter the SHELLS directory of the component where you are creating the user and the Express Server instance to which the user's personal database will be connected.

Adding a new user creates a user task and sends it to the Task Processor. If you are not running the Task Processor in the background, you must run it in the foreground to process the user task.

Oracle STORES all the environment specific values in an xml file stored in $APPL_TOP/admin directory, which they CALL an application CONTEXT file. This file is created by running adbldxml.sh/adbldxml.pl (Located in $AD_TOP/bin). Adbldxml.sh in turn runs oracle.apps.ad.context.GenerateContext java class.

Context file is GENERATED by plugging in environment specific values in the context file TEMPLATE (don’t confuse this template with the configuration file templates) $AD_TOP/admin/template/adxmlctx.tmp. In older versions of 11i these replacement values were gotten from config.txt file (created by rapidwiz during installation), but in later versions, these values are gotten from the information, in existing configuration files and the database. adbldxml.sh/adbldxml.pl (in newer versions of autoconfig) creates a detailed log file, detailing the source for each context variable.

Oracle stores all the environment specific values in an xml file stored in $APPL_TOP/admin directory, which they call an application context file. This file is created by running adbldxml.sh/adbldxml.pl (Located in $AD_TOP/bin). Adbldxml.sh in turn runs oracle.apps.ad.context.GenerateContext java class.

Context file is generated by plugging in environment specific values in the context file template (don’t confuse this template with the configuration file templates) $AD_TOP/admin/template/adxmlctx.tmp. In older versions of 11i these replacement values were gotten from config.txt file (created by rapidwiz during installation), but in later versions, these values are gotten from the information, in existing configuration files and the database. adbldxml.sh/adbldxml.pl (in newer versions of autoconfig) creates a detailed log file, detailing the source for each context variable.

Autoconfig is method of configuring Oracle Applications. All the INFORMATION required to configure Oracle Apps 11i is stored in file called Context file. So there are two context files, one for Database Tier and Second for Application Tier. Context file is repository for CONFIGURATION information stored in xml format. Its xml file and file name format is <SID&GT;_<HOSTNAME>.xml so if your machine name is MACHINE1 and SID is VISION then context file name will be VISION_MACHINE1.xml

Autoconfig is method of configuring Oracle Applications. All the information required to configure Oracle Apps 11i is stored in file called Context file. So there are two context files, one for Database Tier and Second for Application Tier. Context file is repository for configuration information stored in xml format. Its xml file and file name format is <SID>_<HOSTNAME>.xml so if your machine name is MACHINE1 and SID is VISION then context file name will be VISION_MACHINE1.xml

Apps LISTENER usually RUN on all Oracle APPLICATIONS 11i Nodes with listener alias as APPS_$SID and is MAINLY used for listening requests for services like FNDFS & FNDSM.

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

You set profile options at the FOLLOWING LEVELS

• Site level
• APPLICATION level
• RESPONSIBILITY level
• USER level

You set profile options at the following levels

$APPL_TOPadminsidlog

$APPL_TOPadminsidlog

adident HEADER GLXSTEA.fmx

adident Header GLXSTEA.fmx

To VALIDATE synonyms, MISSING synonyms and all grants USE adadmin. After VALIDATING it will produce a REPORT in the location $APPL_TOPadminsidout*.out

To validate synonyms, missing synonyms and all grants use adadmin. After validating it will produce a report in the location $APPL_TOPadminsidout*.out

These FILES contain the PREVIOUS session INFO about adadmin. LOCATION is $APPL_TOPadminsidrestart*.rf9

These files contain the previous session info about adadmin. Location is $APPL_TOPadminsidrestart*.rf9

SELECT TEXT from dba_source where NAME='package name' and type='PACKAGE BODY' and rownum&LT;10>/rdbms/admin)

select text from dba_source where name='package name' and type='PACKAGE BODY' and rownum<10>/rdbms/admin)

It is a file which stores APPS passwords in HARD CODED format i.e. wdbsvr

It is a file which stores apps passwords in hard coded format i.e. wdbsvr

$COMMON_TOPadminscriptsContextnameadstrtal.sh apps/apps

$COMMON_TOPadminscriptsContextnameadstrtal.sh apps/apps

• $AD_TOP/bin
• adadmin
• ADPATCH
• adsplice
• adident
• adrelink
• adlicmgr

C:/programfiles/oracle/Jinitiator.

c:/programfiles/oracle/Jinitiator.

APPL_TOP, COMMON_TOP, DB_TOP,ORA_TOP 7

APPL_TOP, COMMON_TOP, DB_TOP,ORA_TOP 7

• APACHE(http)
• Jserver(jre)
• Forms Server(f60srv)
• Metric Server(d2ls)
• Metric Client(d2lc)
• REPORT Server(rwm60)
• CONCURRENT Server(FNDLIBR)
• DISCOVERER

Appsora.env, appsSID_hostname.env, adovars.env, APPSSID_hostname

Appsora.env, appsSID_hostname.env, adovars.env, APPSSID_hostname

One-off, mini, DIAGNOSTICS, cu, rup, language, help, PLATFORM SPECIFIC, OS, OPATCH, Interoperability, family pack and MAINTENANCE pack.

One-off, mini, diagnostics, cu, rup, language, help, platform specific, OS, OPatch, Interoperability, family pack and maintenance pack.

FND – Application Object LIBRARY, AU – Application Utilities, AD – Application DBA

FND – Application Object Library, AU – Application Utilities, AD – Application DBA

adadmin, adctrl, ADPATCH, adlicmgr, admrgpch, adsplice and adworker

adadmin, adctrl, adpatch, adlicmgr, admrgpch, adsplice and adworker

CLIENT SIDE – CONTROL PANEL

SERVER side – SID_hostname.xml (s_jinit_ver_)

Client side – Control panel

Server side – SID_hostname.xml (s_jinit_ver_)

• HTTP –v – APACHE
• f60gen – FORMS
• ar60run – REPORTS

Both the options will compile all the PL/SQL in the resultant .FMX, .PLX, or .MMX FILE but COMPILE_ALL=YES ALSO CHANGES the CACHED version in the source .FMB, .PLL, or .MMB file.

Both the options will compile all the PL/SQL in the resultant .FMX, .PLX, or .MMX file but COMPILE_ALL=YES also changes the cached version in the source .FMB, .PLL, or .MMB file.

mod_osso is ORACLE SINGLE Sign-On MODULE where as mod_ose is module for Oracle SERVLET ENGINE.

mod_osso is Oracle Single Sign-On Module where as mod_ose is module for Oracle Servlet Engine.

APPS Patch worker can fail in case it doesn't find expected data, object, files or anything which driver is TRYING to update/edit/modify. Possible symptoms may be UNDERLYING tables/objects are INVALID, a prerequisite patch is missing, login information is incorrect, inconsistency in seed data.

Apps Patch worker can fail in case it doesn't find expected data, object, files or anything which driver is trying to update/edit/modify. Possible symptoms may be underlying tables/objects are invalid, a prerequisite patch is missing, login information is incorrect, inconsistency in seed data.