1) What is APPS and APPLSYS users ?

Ans :


APPS is the runtime user for E-Business Suite. Owns all the applications code in the
database. APPS Schema Contains Synonyms to the objects of All Products (AP,AR, GL
etc ) and Triggers, views, packages, procedures, functions but the owner of all GL tables is GL user , AP tables is AP , and AR tables is AR Schema. Apps is a schema which does not contain any tables of itself. The default password is apps.


Applsys schema contains all the tables required for administarative purpose. The default password is apps.

APPLSYS schema contains shared APPS foundation objects like FND,AD,WF related data like tables and Indexes.

2) What is APPLSYSPUB ?

Applsyspub schema is responsible for password checking.The default password is pub.Applsyspub is used for authentication by having read only views.

3) Why do we keep the same password for APPS & APPLSYS ?

This is required during Oracle Applications Login. The process is as follows :

a) Initial Sign on (http://hostname.domain.com:port)

This uses APPLSYSPUB schema to authenticate and validate AOL username & password (OPERATIONS/WELCOME using GUEST user account).

Once this aunthentication is validated successfully we get to see the responsibility page.

b) Selecting the assigned responsbility requires APPLSYS schema validation and then it connects to APPS schema.

c) Since it uses both applsys and apps during signon process this expects both the password to be identical. Try changing apps password to something else and try to login, the validation at the last stage would fail.

4) What would happen if you change the passwords for APPS, APPLSYS with “alter user” command.

Changing the apps password using “alter user” corrupts the password

Oracle Application stores passwords in FND_USER and FND_ORACLE_USERID

Column Value Keys
FND_USER APPS password username/password
FND_ORACLE_USERID user password APPS password

The APPLSYS.FND_ORACLE_USERID table contains all the Oracle Applications related database accounts – there is one database account for each Oracle Applications module (i.e., GL = General Ledger). The application needs access to these database schemas to perform various functions, thus it must have access to the database account password. All the passwords in the FND_ORACLE_USERID table are encrypted using the APPS password as the key.

Thus changing the password using “Alter User” command will not reflect the password in FND_ORACLE_USERID.

5) How would you recover the executable once lost ?

What would happen … if FNDLIBR executable is deleted from $FND_TOP/bin while the Application is up and running.

Any executable that is lost can be recreated using adadmin using

Option 2 : Maintain Applications Files menu


Option 1 : Relink Applications programs

If a DBA deletes the FNDLIBR executable during runtime users will still be able to run the reports however if a DBA tries to restart the service it will raise an error.

Manager Log file shows the error :

Starting PATCH_0913@PATCH Internal Concurrent Manager — shell process ID 29919









Reviver is ENABLED

sh: line 34: FNDLIBR: command not found

The PATCH_0913@PATCH internal concurrent manager has terminated with status 127 – giving up.

6) Which table stores the Application URL ? (http://hostname.domain.port)

select * from icx_parameters;



7) Elaborate on “splice” in adsplice ?

AD Splicer registers off-cycle product as a valid Oracle Applications product for the given release

• The splicing process enables AutoPatch and AD Administration to recognize the off-cycle product

• AD Splicer uses control files to manage the splicing process

– These are not related to the database control files

Off-cycle products are generally released as patches. All product files and control files necessary to splice in the product are included in the patch.

There is one product configuration file, called newprods.txt. The product configuration file must be edited for your specific system before the off-cycle product can be properly spliced.

8) FNDFS and FNDSM – Difference and whats the significance.

FNDFS — Also known as RRA(Report Review Agent) is the default text viewer within Oracle Applications, which allows users to view report output and log files.

FNDSM — Executable and a service required for GSM(Generic Service Management). It is initiated by starting Oracle Apps Listener.

9) What is OC4J ? – Used for Application Server

OC4J (Oracle Containers for Java/ J2EE) provides an execution environment for J2EE applications. It is needed by iAS & Developer (10.1.2 and 10.1.3) in R12.

10) What is OPMN ?

OPMN is installed and configured with every Oracle Application Server installation type and is essential for running Oracle Application Server.

Oracle Process Manager & Notification Server (OPMN) is a new addition to R12 E-Business Suite Technology Stack. OPMN manages all Oracle Application Server 10g Components (like 1. Oracle HTTP Server, 2. OC4J etc)

11) Suppose we need to apply AR and AP patches – can we merge the patches together and apply ?

Yes we can merge them and apply as they belong to the same family ( Finance Module )

12) Whats the need to adpreclone.pl?

ADPRECLONE is a feature provided in Oracle Applications 11i/R12 to clone the system i.e create a replica of source system for testing purpose.

ADPRECLONE — Used as a pre-requisite before starting the cloning procedure

adpreclone creates a staging directory under $COMMON_TOP

for e.g : $COMMON_TOP/clone

adpreclone.pl captures all the drivers and templates required to clone the target system using the source systems information.

13) Can we clone the instance without adpreclone – is it recommended.

Yes we can clone the instance without running adpreclone and it is always referred to as “MANUAL CLONING”. Although it is not recommended by Oracle, DBA’s prefer this way when they have to refresh only the database.

14) What would “u” driver do while applying a patch ?

U driver is a unified driver supplied in all the patches in R12

Prior to R12 in 11i patches were released with 3 specific drivers

i) c driver — Copies the files provided by the patch to their respective tops

ii) d driver — Executes the files copied the c driver into the database for e.g : packages, ldt files, xdf files etc

iii) g driver — Generates forms and reports provided in the patch.

This consumes a lot of time as a DBA needs to run the patch utility everytime a driver needs to be applied and hence resulting in long down time.

To avoid this process and reduce the downtime ORACLE has released unified drivers referred as “U”  driver which is a combination of these 3 drivers and will execute the patch sequentially from c driver to d driver and then g driver.

15) Why is the Batch Size defined as 1000 by default ?

This is to decide the rows for commits during a patch or any administrative tasks that are in progress.

16) Can I open another session and run adadmin  while a patch application is in progress?

Yes you can run provided none of the workers are running for the current patch process.

17) Are the existing DB connections dropped if the DB listener is restarted ?

No existing users will be able to continue their work. Any new connection will not be able to go through.

18) How to compile invalid objects from the middle tier ?

You can complie invalid objects using adadmin

Option 3 : and then Option 1

19) How to find what Oracle Application client is using ?

select release_name from fnd_product_groups;

20) How to check the version of any file in Oracle Applications ?

Go to the TOP directory

cd $AP_TOP/patch/115/sql

strings -a filename |grep ‘$Header

Share →
Skip to toolbar