Explore topic-wise InterviewSolutions in .

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.

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.

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.

For PRODUCTS LIKE Payable, RECEIVABLES which uses MRC and if MRC is ENABLED then each transaction table in BASE schema related to currency now has an associated MRC sub tables.

For products like Payable, Receivables which uses MRC and if MRC is enabled then each transaction table in base schema related to currency now has an associated MRC sub tables.

No, apps_mrc schema is dropped with 11.5.10 UPGRADE & 11.5.10 new INSTALL. This is REPLACED by more Integrated Architecture.

No, apps_mrc schema is dropped with 11.5.10 Upgrade & 11.5.10 new Install. This is replaced by more Integrated Architecture.

PLL->PLD f60gen module=MSCOSCW3.pll module_type=library userid=apps/ module_access=file output_file=MSCOSCW1.pld script=yes.

pld -> pll f60gen module=MSCOSCW3.pld userid=apps/ module_type=library module_access=file output_file=MSCOSCW1.pll parse=y batch=yes compile_all=special.

pll->pld f60gen module=MSCOSCW3.pll module_type=library userid=apps/ module_access=file output_file=MSCOSCW1.pld script=yes.

pld -> pll f60gen module=MSCOSCW3.pld userid=apps/ module_type=library module_access=file output_file=MSCOSCW1.pll parse=y batch=yes compile_all=special.

Form Server START up LOG file default LOCATION is $OAD_TOP/admin/log/$CONTEXT_NAME/f60svrm.txt

FORMS Run Time DIAGNOSTICS default location is $ORACLE_HOME/forms60/log/$CONTEXT_NAME

Form Server Start up log file default location is $OAD_TOP/admin/log/$CONTEXT_NAME/f60svrm.txt

Forms Run Time Diagnostics default location is $ORACLE_HOME/forms60/log/$CONTEXT_NAME

odf stands for Object Description FILES USED to create tables & other database objects while APPLYING a patch.

odf stands for Object Description Files used to create tables & other database objects while applying a patch.

.ldt & .lct stands for Loader data file & Loader configuration files, used frequently in MIGRATING customization, PROFILE options, configuration data etc. ACROSS Instances.

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

.PLS FILE STANDS for plsql files. In apps PATCH these files CONTAIN CODE to create package spec or package body or both.

.PLS file stands for plsql files. In apps patch these files contain code to create package spec or package body or both.

• 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

MAKE is utility in Unix/Linux to maintain , UPDATE & GENERATE a file MAINLY EXECUTABLE.

make is utility in Unix/Linux to maintain , update & generate a file mainly executable.

When forms run in SOCKET Mode these are DEDICATED CONNECTION between Client Machine & Form Server. When Forms run in SERVLET mode there will be additional JVM for Forms Request in that case and you won't start form via adfrmctl.sh.

When forms run in SOCKET Mode these are dedicated connection between Client Machine & Form Server. When Forms run in servlet mode there will be additional JVM for Forms Request in that case and you won't start form via adfrmctl.sh.

IMAP STANDS for Internet Message Access Protocol and JAVA Notification mailer require IMAP server for Inbound PROCESSING of Notification MAILS.

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

Use ADPATCH flags=hidepw while APPLYING PATCHES in apps to hide apps or system password being displayed on SCREEN.

Use adpatch flags=hidepw while applying patches in apps to hide apps or system password being displayed on screen.

When client makes a forms connection in ORACLE Applications, forms client session uses configuration file DEFINED by ENVIRONMENT VARIABLE FORMS60_WEB_CONFIG_FILE.

When client makes a forms connection in Oracle Applications, forms client session uses configuration file defined by environment variable FORMS60_WEB_CONFIG_FILE.

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

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

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.

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.

GUEST_USER_PWD(Guest/Oracle) is used by JDBC Thin CLIENT where as GWYUID is used by Thick Clients like VIA FORMS CONNECTIONS.

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

GWYUID is defined in dbc i.e. DATABASE Connect DESCRIPTOR FILE. It is USED to connect THIN clients to database.

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

GWYUID stands for GATEWAY USER ID and password. Usually like APPLSYSPUB/PUB

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

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

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

ADMIN Server will be on First MACHINE with concurrent PROCESSING server.

Admin Server will be on First machine with concurrent processing server.

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.

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.

Rapid clone updates profile options specific to site LEVEL. If you have any profile option SET at other levels like SERVER, responsibility, user....level then RESET them.

Rapid clone updates profile options specific to site level. If you have any profile option set at other levels like server, responsibility, user....level then reset them.

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.

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.

Oracle HTML Cache is available at $COMMON_TOP/_pages for some PREVIOUS VERSIONS you might find it in $OA_HTML/_pages.

Oracle HTML Cache is available at $COMMON_TOP/_pages for some previous versions you might find it in $OA_HTML/_pages.

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.

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.

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)

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)

You can START FORMS server in SOCKET or SERVLET by DEFAULT Forms are CONFIGURED to start in socket mode.

You can start forms server in SOCKET or SERVLET by default Forms are configured to start in socket mode.

FORMS configuration at TIME of startup is in SCRIPT adfrmctl.sh and appsweb_$CONTEXT_NAME.cfg for forms client connection used each time a USER initiates forms connection.

Forms configuration at time of startup is in script adfrmctl.sh and appsweb_$CONTEXT_NAME.cfg for forms client connection used each time a user initiates forms connection.

Yes you have to USE both in APPS, for apps patches you will use opatch utility and for APPLYING DATABASE PATCH in apps you will use opatch utility.

Yes you have to use both in apps, for apps patches you will use opatch utility and for applying database patch in apps you will use opatch utility.

# ADPATCH is UTILITY to APPLY ORACLE apps Patches whereas

# opatch is utility to apply database patches

# adpatch is utility to apply oracle apps Patches whereas

# opatch is utility to apply database patches

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

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

You can USE adadmin utility to compile or you can use utlrp.sql script SHIPPED with ORACLE DATABASE to compile Invalid Database Objects.

You can use adadmin utility to compile or you can use utlrp.sql script shipped with Oracle Database to compile Invalid Database Objects.

SQLPLUS> select count(*) from dba_objects where STATUS LIKE 'INVALID';

SQLPLUS> select count(*) from dba_objects where status like 'INVALID';

WEB Listener is Web Server listener which is listening for web Services (HTTP) request. This listener is STARTED by adapcctl.sh & DEFINED by DIRECTIVE (LISTEN, Port) in httpd.conf for Web Server.

Web Listener is Web Server listener which is listening for web Services (HTTP) request. This listener is started by adapcctl.sh & defined by directive (Listen, Port) in httpd.conf for Web Server.

lsnrctl start APPS_$SID (replace SID with your Instance NAME) so if your SID is VISION then USE lsnrctl status APPS_VISION.

lsnrctl start APPS_$SID (replace SID with your Instance Name) so if your SID is VISION then use lsnrctl status APPS_VISION.

In Oracle 11I, you have script adalnctl.sh which will start your APPS listener. You can ALSO start it by command lsnrctl start APPS_$SID (REPLACE sid by your Instance SID Name).

In Oracle 11i, you have script adalnctl.sh which will start your apps listener. You can also start it by command lsnrctl start APPS_$SID (Replace sid by your Instance SID Name).

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.

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.

ICM STAND for Internal Concurrent Manager, which controls other managers. If it finds other managers down, it checks & tries to restart them. You can say it is an administrator to other concurrent managers. STANDARD Manager: These are normal managers which performs ACTIONS on the requests and does batch or single request processing. CRM is acronym for CONFLICT Resolution Manager and is used to resolve conflicts between managers & requests. If a request is submitted whose execution is CLASHING or it is defined not to run while a particular type of request is running then such requests are assigned to CRM for incompatibilities & conflict resolution.

ICM stand for Internal Concurrent Manager, which controls other managers. If it finds other managers down, it checks & tries to restart them. You can say it is an administrator to other concurrent managers. Standard Manager: These are normal managers which performs actions on the requests and does batch or single request processing. CRM is acronym for Conflict Resolution Manager and is used to resolve conflicts between managers & requests. If a request is submitted whose execution is clashing or it is defined not to run while a particular type of request is running then such requests are assigned to CRM for incompatibilities & conflict resolution.

Report Server is started by executable rwmts60 on CONCURRENT manager NODE & this file is under $ORACLE_HOME/bin Execute COMMAND on your server LIKE

ps -ef | grep rwmts60

Report Server is started by executable rwmts60 on concurrent manager Node & this file is under $ORACLE_HOME/bin Execute command on your server like

ps -ef | grep rwmts60

If you are running GL month end reports or taxation reports annually these reports might take couple of days. Some of these requests are very resource INTENSIVE so you can have one node running long running resource intensive requests while other PROCESSING your day to day short running requests. Another scenario is when your requests are very CRITICAL and you want high resilience for your CONCURRENT Processing Node, you can configure PCP. So if node1 goes down you still have CM node available processing your requests.

If you are running GL month end reports or taxation reports annually these reports might take couple of days. Some of these requests are very resource intensive so you can have one node running long running resource intensive requests while other processing your day to day short running requests. Another scenario is when your requests are very critical and you want high resilience for your Concurrent Processing Node, you can configure PCP. So if node1 goes down you still have CM node available processing your requests.

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.

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.

Report Review Agent (RRA) also referred by EXECUTABLE FNDFS is DEFAULT text viewer in ORACLE Applications 11I for viewing output files & log files.

Report Review Agent (RRA) also referred by executable FNDFS is default text viewer in Oracle Applications 11i for viewing output files & log files.

This value is determined from PROFILE option "APPLICATIONS Database ID"

This value is determined from profile option "Applications Database ID"

DBC file is QUITE important as whenever Java or any other PROGRAM like FORMS want to CONNECT to database it uses dbc file. Typical entry in dbc file is

• GUEST_USER_PWD
• APPS_JDBC_URL
• DB_HOST

DBC file is quite important as whenever Java or any other program like forms want to connect to database it uses dbc file. Typical entry in dbc file is

SELECT RELEASE_NAME from fnd_product_groups;

You should SEE OUTPUT LIKE

RELEASE_NAME

11.5.9 or 11.5.10.2

select RELEASE_NAME from fnd_product_groups;

You should see output like

RELEASE_NAME

11.5.9 or 11.5.10.2

plsql & SESSION CACHE are STORED under $IAS_ORACLE_HOME/ Apache/modplsql/cache directory.

plsql & session cache are stored under $IAS_ORACLE_HOME/ Apache/modplsql/cache directory.

In order to IMPROVE PERFORMANCE mod_pls (Apache component) caches some database content to file. This plsql CACHE is used to store session INFORMATION. plsql cache is used to store plsql cache i.e. used by mod_pls

In order to improve performance mod_pls (Apache component) caches some database content to file. This plsql cache is used to store session information. plsql cache is used to store plsql cache i.e. used by mod_pls