Top 50 Oracle Apps Dba Interview Questions You Must Prepare 07.Jul.2022

GWYUID stands for Gateway User ID and password. Usually like APPLSYSPUB/PUB

For system to be Rapid Clone enabled, it should be Autoconfig enabled. You should have Rapid Clone Patches applied.

You can use ojspCompile.pl perl script shipped with Oracle apps to compile JSP files. This script is under $JTF_TOP/admin/scripts. Sample compilation method is

perl ojspCompile.pl --compile --quiet

US directory is default language directory in Oracle Applications. If you have multiple languages Installed in your Applications then you will see other languages directories besides US, that directory will contain reports, fmx and other code in that respective directory like FR for France, AR for Arabic.

0 & Y are flags for FND Executable like FNDCPASS & FNDLOAD where 0 is request id.  'Y' indicates the method of invocation i.e. it is directly invoked from the command-line not from the Submit Request Form.

cgi stands for Common Gateway Interface and these are Script Alias in Oracle Apps used to access forms server . Usually Form Server access directly via http://hostname:port/dev60cgi/f60cgi.

In order to start discoverer you can use script addisctl.sh under $OAD_TOP/admin/scripts/$CONTEXT_NAME or startal.sh under $ORACLE_HOME/discwb4/util (under Middle/Application Tier)

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

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

APPL_TOP, COMMON_TOP, DB_TOP,ORA_TOP 7

  • 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.

adident utility in oracle apps is used to find version of any file .

For example:“adident Header <filename>”

PCP is acronym for Parallel Concurrent Processing. Usually you have one Concurrent Manager executing your requests but you can configure Concurrent Manager running on two machines. So for some of your requests primary CM Node is on machine1 and secondary CM node on machine2 and for some requests primary CM is on machine2 & secondary CM on machine1.

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.

IMAP stands for Internet Message Access Protocol and Java Notification mailer require IMAP server for Inbound Processing of Notification Mails.

.ldt & .lct stands for Loader data file & Loader configuration files, used frequently in migrating customization, profile options, configuration data etc. across Instances.

Lets first understand what is cache size in Concurrent Manager. When Manager picks request from FND CONCURRENT REQUESTS Queues, it will pick up number of requests defined by cache size in one shot & will work on them before going to sleep. So in my views if you don't define cache size while defining CM then it will take default value 1, i.e. picking up one request per cycle.

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.

Rapid Clone automatically updates Global oraInventory during configuration phase. You don't have to do anything manually for Global oraInventory.

Multi Node System in Oracle Applications 11i me you have Applications 11i Component on more than one system. Typical example is database, Concurrent Manager on one machine and Forms Server, Web Server on second machine.

XXX_TOP is top level directory in Oracle Application 11i for respective Component.

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

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

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.

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

GWYUID is defined in dbc i.e. Database Connect Descriptor file. It is used to connect thin clients to database.

You can query for table FND_NODES and check for column, SUPPORT_CP (for Concurrent Manager) SUPPORT_FORMS (for forms server), SUPPPORT_WEB (Web Server), SUPPORT_ADMIN (Admin Server), and SUPPORT_DB for database tier. You can also check same from CONTEXT File (xml file under APPL_TOP/admin).

GUEST_USER_PWD(Guest/Oracle) is used by JDBC Thin Client where as GWYUID is used by Thick Clients like via Forms Connections.

Various options available with adpatch depending on your AD version are:

autoconfig, check_exclusive, checkfile, compiledb, compilejsp, copyportion, databaseportion, generateportion, hotpatch, integrity, maintainmrc, parallel, prereq, validate

TWO_TASK mocks your TNS alias which you are going to use to connect to database. Let’s assume you have database client with TNS alias defined as PROD to connect to Database PROD on machine teachmeoracle.com listening on port 152@Then usual way to connect is sqlplus username/passwd@PROD; now if you don't want to use @PROD then you set TWO_TASK=PROD and then can simply use sqlplus username/passwd then sql will check that it has to connect to TNS alias define by value PROD i.e. TWO_TASK

If forgot password link is enabled and sysadmin account is configured with mail id user forget password link else you can reset sysadmin password via FNDCPASS.

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

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.

$COMMON_TOPadminscriptsContextnameadstrtal.sh apps/apps

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.

DBC. as name suggests is a database connect descriptor file which stores database connection information used by application tier to connect to database. This file is in directory $FND_TOP/secure also called as FND_SECURE.

MRC also called as Multiple Reporting Currency in Oracle Apps. By default you have currency in US Dollars but if your organization’s operating books are in other currency then you as apps DBA need to enable MRC in Apps.

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

Yes, database & db listener should be UP when you apply any driver patch in apps. Even if driver is not updating any database object connection is required to validate apps & other schema and to upload patch history information in database tables.

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.

You can use ad utility adlicmgr to license product in Oracle Apps.

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

  • Yes, you can restore FNDLIBR executables
  • Run adadmin on concurrent manager node
  • Select Maintain Applications Files menu
  • Then select Relink Applications programs
  • When prompts for “Enter list of products to link ('all' for all products) [all]” select FND
  • When prompt for “Generate specific executables for each selected product [No]?” select YES
  • From list of executables select FNDLIBR this will create new FNDLIBR executables

There are three $ORACLE_HOME in Oracle Apps, Two for Application Tier (Middle Tier) and One in Database Tier.

# ORACLE_HOME 1: On Application Tier used to store 8.0.6 techstack software. This is used by forms, reports & discoverer.

# ORACLE_HOME 2: On Application Tier used by iAS (Web Server) techstack software. This is used by Web Listener & contains Apache.

# ORACLE_HOME 3: On Database Tier used by Database Software usually 8i, 9i or 10g database.

select RELEASE_NAME from fnd_product_groups;

You should see output like

RELEASE_NAME

11.5.9 or 11.5.10.2

Client side – Control panel

Server side – SID_hostname.xml (s_jinit_ver_)

  • Apache(http)
  • Jserver(jre)
  • Forms Server(f60srv)
  • Metric Server(d2ls)
  • Metric Client(d2lc)
  • Report Server(rwm60)
  • Concurrent Server(FNDLIBR)
  • Discoverer