Explore topic-wise InterviewSolutions in .

access_log FILE by DEFAULT is LOCATED in $IAS_ORACLE_HOME/ Apache/Apache/logs. LOCATION of this file is DEFINED in httpd.conf by patameter CustomLog or TransferLog.

access_log file by default is located in $IAS_ORACLE_HOME/ Apache/Apache/logs. Location of this file is defined in httpd.conf by patameter CustomLog or TransferLog.

By USING SELECT COUNT(*) from TABLENAME

By using select count(*) from tablename

A cluster provides an OPTIONAL METHOD of storing table data. A cluster is comprised of a group of tables that share the same data blocks, which are grouped together because they share common columns and are often used together. For example, the EMP and DEPT table share the DEPTNO column. When you cluster the EMP and DEPT, Oracle physically STORES all rows for each department from both the EMP and DEPT tables in the same data blocks. You should not use clusters for tables that are FREQUENTLY accessed individually.

A cluster provides an optional method of storing table data. A cluster is comprised of a group of tables that share the same data blocks, which are grouped together because they share common columns and are often used together. For example, the EMP and DEPT table share the DEPTNO column. When you cluster the EMP and DEPT, Oracle physically stores all rows for each department from both the EMP and DEPT tables in the same data blocks. You should not use clusters for tables that are frequently accessed individually.

A CURSOR is a MECHANISM by which you can assign a name to a “select STATEMENT” and MANIPULATE the information WITHIN that SQL statement.

A cursor is a mechanism by which you can assign a name to a “select statement” and manipulate the information within that SQL statement.

The implicit cursor is used by Oracle SERVER to test and parse the SQL statements and the explicit CURSORS are DECLARED by the programmers.

The implicit cursor is used by Oracle server to test and parse the SQL statements and the explicit cursors are declared by the programmers.

FNDSM is executable and core component in GSM ( Generic Service Management Framework DISCUSSED above). You start FNDSM SERVICES via APPS listener on all Nodes in Application Tier in E-Business SUITE.

FNDSM is executable and core component in GSM ( Generic Service Management Framework discussed above). You start FNDSM services via APPS listener on all Nodes in Application Tier in E-Business Suite.

GSM stands for Generic Service Management Framework. Oracle E-Business Suite consist of VARIOUS compoennts like Forms, Reports, Web Server, Workflow, Concurrent Manager .

Earlier each service used to start at their own but managing these services (given that) they can be on various machines distributed across network. So Generic Service Management is EXTENSION of Concurrent Processing which manages all your services , provide fault TOLERANCE (If some service is down ICM through FNDSM and other processes will try to start it even on REMOTE server) With GSM all services are centrally MANAGED via this Framework.

GSM stands for Generic Service Management Framework. Oracle E-Business Suite consist of various compoennts like Forms, Reports, Web Server, Workflow, Concurrent Manager .

Earlier each service used to start at their own but managing these services (given that) they can be on various machines distributed across network. So Generic Service Management is extension of Concurrent Processing which manages all your services , provide fault tolerance (If some service is down ICM through FNDSM and other processes will try to start it even on remote server) With GSM all services are centrally managed via this Framework.

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. This confuses version control and build tools (CVS, Subversion, make, SCONS); they believe you've made significant changes to the source. COMPILE_ALL=SPECIAL does not do this.

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. This confuses version control and build tools (CVS, Subversion, make, scons); they believe you've made significant changes to the source. COMPILE_ALL=SPECIAL does not do this.

mod_osso is module in Oracle's HTTP Server SERVES as Conduit between Oracle Apache Server and Singl Sign-On Server where as mod_ose is ALSO ANOTHER module in Oracle's HTTP Server serves as conduit between Oracle Apache and Oracle Servlet Engine.

mod_osso is module in Oracle's HTTP Server serves as Conduit between Oracle Apache Server and Singl Sign-On Server where as mod_ose is also another module in Oracle's HTTP Server serves as conduit between Oracle Apache and Oracle Servlet Engine.

Apps PATCH WORKER can fail in case it doesn't find expected data, OBJECT, FILES or any thing which driver is trying to update/edit/modify. Possible SYMPTOMS may be underlying tables/objects are invalid, a prereq patch is missing, login information is incorrect, inconsistency in seeded data.

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

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.

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.

No, C DRIVER only COPIES files in File System. Database Object might be INVALIDATED during D driver when these OBJECTS are created/dropped/modified.

No, C driver only copies files in File System. Database Object might be invalidated during D driver when these objects are created/dropped/modified.

MAIN CONFIGURATION FILES in Oracle Apps Web Server are httpd.conf, apps.conf, oracle_apache.conf, httpd_pls.conf jserv.conf, ssp_init.txt, jserv.properties, zone.properties plsql.conf, wdbsvr.app, plsql.conf.

Main configuration files in Oracle Apps Web Server are httpd.conf, apps.conf, oracle_apache.conf, httpd_pls.conf jserv.conf, ssp_init.txt, jserv.properties, zone.properties plsql.conf, wdbsvr.app, plsql.conf.

APPLICATIONS start/stop SCRIPTS are in DIRECTORY $COMMON_TOP/admin/scripts/$CONTEXT_NAME.

applications start/stop scripts are in directory $COMMON_TOP/admin/scripts/$CONTEXT_NAME.

Jserv CONFIGURATION FILES are STORED in $IAS_ORACLE_HOME/Apache/Jserv/etc.

Jserv configuration files are stored in $IAS_ORACLE_HOME/Apache/Jserv/etc.

MRC also called as Multiple Reporting Currency in ORACLE Apps. Default you have currency in US Dollars but if your organization operating BOOKS are in other currency then you as apps dba NEED to enable MRC in Apps. How to enable MRC COMING soon..

MRC also called as Multiple Reporting Currency in oracle Apps. Default you have currency in US Dollars but if your organization operating books are in other currency then you as apps dba need to enable MRC in Apps. How to enable MRC coming soon..

You can use ad UTILITY adlicmgr to licence PRODUCT in Oracle APPS.

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

ADSPLICE UTILITY in ORACLE apps is utility to add a NEW PRODUCT..

ADSPLICE UTILITY in oracle apps is utility to add a new product..

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.

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.

Utility adrepgen is used to COMPILE Reports.Synatx is given below adrepgen userid=apps 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.Synatx is given below adrepgen userid=apps 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 option 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 option 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. Usually informative logs.

.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. Usually informative logs.

AUTOCONFIG is UTILITY to configure your Oracle APPLICATION environment. .xml file is REPOSITORY of all configuration from which AutoConfig picks configuration and polulates related files.

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

In order to check list of files changes 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 changes 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.

NO DATA FOUND is an exception which is raised when either an implicit query RETURNS no data, or you ATTEMPT to reference a ROW in the PL/SQL table which is not yet defined. SQL%NOTFOUND, is a BOOLEAN attribute indicating whether the recent SQL statement does not MATCH to any row.

NO DATA FOUND is an exception which is raised when either an implicit query returns no data, or you attempt to reference a row in the PL/SQL table which is not yet defined. SQL%NOTFOUND, is a BOOLEAN attribute indicating whether the recent SQL statement does not match to any row.

The Where CURRENT Of statement allows you to UPDATE or delete the record that was last fetched by the CURSOR.

The Where Current Of statement allows you to update or delete the record that was last fetched by the cursor.

Cursor variable is USED to MARK a work area where Oracle stores a multi-row QUERY output for processing. It is LIKE a pointer in C or PASCAL. Because it is a TYPE, it is defined as TYPE REF CURSOR RETURN ;.

Cursor variable is used to mark a work area where Oracle stores a multi-row query output for processing. It is like a pointer in C or Pascal. Because it is a TYPE, it is defined as TYPE REF CURSOR RETURN ;.

The return type of a CURSOR VARIABLE can be %ROWTYPE or record_name%TYPE or a record type or a ref cursor type. A SCALAR data type like number or varchar can’t be USED but a record type may evaluate to a scalar value.

The return type of a cursor variable can be %ROWTYPE or record_name%TYPE or a record type or a ref cursor type. A scalar data type like number or varchar can’t be used but a record type may evaluate to a scalar value.

Using OPEN cursor_name and CLOSE cursor_name commands. The cursor must be opened before using it in order to fetch the result SET of the query it is associated with. The cursor needs to be closed so as to RELEASE resources earlier than end of transaction, or to free up the cursor VARIABLE to be opened again.

Using OPEN cursor_name and CLOSE cursor_name commands. The cursor must be opened before using it in order to fetch the result set of the query it is associated with. The cursor needs to be closed so as to release resources earlier than end of transaction, or to free up the cursor variable to be opened again.

Pass a cursor variable as an argument to a PROCEDURE or function. You can, in ESSENCE, share the results of a cursor by PASSING the reference to that result SET.

Pass a cursor variable as an argument to a procedure or function. You can, in essence, share the results of a cursor by passing the reference to that result set.

ADIDENT UTILITY in oracle apps is used to find VERSION of any FILE. AD Identification. for EX. "adident Header.

ADIDENT UTILITY in oracle apps is used to find version of any file. AD Identification. for ex. "adident Header.

VARIOUS options available with adpatch DEPENDING on your AD VERSION are autoconfig, check_ exclusive, checkfile, compiledb, compilejsp, copyportion, databaseprtion, generateportion, hotpatch, integrity, maintainmrc, parallel, prereq, VALIDATE.

Various options available with adpatch depending on your AD version are autoconfig, check_ exclusive, checkfile, compiledb, compilejsp, copyportion, databaseprtion, generateportion, hotpatch, integrity, maintainmrc, parallel, prereq, validate.

YES, USE options=hotpatch as MENTIONED above with ADPATCH

Yes, use options=hotpatch as mentioned above with adpatch

USE adadmin to change Maintenance mode is ORACLE Apps. With AD.I you need to enable maintenance mode in order to APPLY apps patch via adpatch UTILITY. If you don't want to put apps in maintenance mode you can use adpatch options=hotpatch FEATURE.

Use adadmin to change Maintenance mode is Oracle Apps. With AD.I you need to enable maintenance mode in order to apply apps patch via adpatch utility. If you don't want to put apps in maintenance mode you can use adpatch options=hotpatch feature.

You can TAKE advantage of following :

• Merging patches via admrgpch.
• USE various adpatch options like nocompiledb or nocompilejsp.
• Use defaults file.
• Staged APPL_TOP during upgrades.
• Increase batch SIZE (MIGHT result into negative ).

You can take advantage of following :

dbc as NAME says is 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.

dbc as name says is 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.

RAPID Clone will automatically Update GLOBAL oraInventory during CONFIGURATION phase. You don't have to do any THING manually for Global oraInventory.

Rapid Clone will automatically Update Global oraInventory during configuration phase. You don't have to do any thing manually for Global oraInventory.

YES, this is now supported via Rapid CLONE, Check if your system has all prerequisite patches for Rapid Clone and you are on latest rapid clone PATCH.

Yes, this is now supported via Rapid Clone, Check if your system has all prerequisite patches for Rapid Clone and you are on latest rapid clone patch.

A FUNCTION ALWAYS RETURNS a value, while a PROCEDURE does not. When you call a function you must always assign its value to a VARIABLE.

A function always returns a value, while a procedure does not. When you call a function you must always assign its value to a variable.

The FORMAL parameters are the names that are DECLARED in the parameter list of the header of a module.

The actual parameters are the values or expressions PLACED in the parameter list of the actual call to the module.

The formal parameters are the names that are declared in the parameter list of the header of a module.

The actual parameters are the values or expressions placed in the parameter list of the actual call to the module.

YES. In such case you don’t NEED to SPECIFY any value and the ACTUAL parameter will take the default value provided in the function definition.

Yes. In such case you don’t need to specify any value and the actual parameter will take the default value provided in the function definition.

No. A FUNCTION has to RETURN a VALUE,an OUT PARAMETER cannot return a value.

No. A function has to return a value,an OUT parameter cannot return a value.

Multi Node SYSTEM in Oracle Applications 11I means you have Applications 11i Component on more than one system. Typical example is DATABASE, Concurrent Manager on one machine and forms, Web Server on SECOND machine is example of TWO Node System.

Multi Node System in Oracle Applications 11i means you have Applications 11i Component on more than one system. Typical example is Database, Concurrent Manager on one machine and forms, Web Server on second machine is example of Two Node System.

This file is defined by environment variable FORMS60_WEB_CONFIG_FILE This is usually in DIRECTORY $OA_HTML/bin on forms tier. This file is used by any forms CLIENT SESSION. When a user try to access forms , f60webmx picks up this file and based on this configuration file creates a forms session to user/client.

This file is defined by environment variable FORMS60_WEB_CONFIG_FILE This is usually in directory $OA_HTML/bin on forms tier. This file is used by any forms client session. When a user try to access forms , f60webmx picks up this file and based on this configuration file creates a forms session to user/client.

These FILES are used during restart of patch in case of patch FAILURE because of some reason.

These files are used during restart of patch in case of patch failure because of some reason.

US directory is defauly 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, simplifies chinese or spanish.

US directory is defauly 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, simplifies chinese or spanish.

• ICM - INTERNAL CONCURRENT Manager which MANAGES concurrent Managers.
• Standard Managers - Which Manage processesing of requests.
• CRM - Conflict Resolution Managers , resolve conflicts in case of incompatibility.

APPS.env is main ENVIRONMENT FILE which inturn calls other environment files LIKE . env under $APPL_TOP, .env under 806 ORACLE_HOME and custom. env for any CUSTOMIZED environment files.

APPS.env is main environment file which inturn calls other environment files like . env under $APPL_TOP, .env under 806 ORACLE_HOME and custom. env for any Customized environment files.

For syetem to be Rapid CLONE enabled , it should be AUTOCONFIG enabled (Check above How to confirm if Apps 11I is Autoconfig enabled). You should have Rapid Clone Patches applied , Rapid Clone is PART of Rapid Install Product whose Family Pack Name is ADX. By DEFAULT all Apps 11i Instances 11.5.9 and above are Autoconfig and Rapid Clone enabled.

For syetem to be Rapid Clone enabled , it should be Autoconfig enabled (Check above How to confirm if Apps 11i is Autoconfig enabled). You should have Rapid Clone Patches applied , Rapid Clone is part of Rapid Install Product whose Family Pack Name is ADX. By default all Apps 11i Instances 11.5.9 and above are Autoconfig and Rapid Clone enabled.