THE AD ADMINISTRATION UTILITY

1
WHAT IS AD ADMINISTRATION?
AD Administration performs many important administrative
tasks to ensure Oracle Applications runs smoothly. You can
use AD Administration to complete some runtime tasks
during or after an installation or upgrade, or any time
thereafter. These tasks are divided into two categories: file
system tasks and database tasks.

Similar to AutoInstall and AutoPatch, adadmin can run

parallel workers for most database tasks and some file
system tasks.

2
BEFORE RUNNING ADADMIN
There are a few steps to perform before you run adadmin.
These are the same preparatory steps you would follow for running
any other AD utility, such as AutoPatch or AutoInstall.

1. Log in as applmgr. Make sure this account is using a

Bourne shell (or Korn shell on some platforms).

2. Run the environment file for the Oracle Applications

product group you want to update.
• This is normally <db_name>.env
• To run the environment file, make sure you are in a Bourne or Korn
shell, and type:
$ . $APPL_TOP/<db_name>.env
• Depending on your setup, you may have already run this file when
you logged in.

3. Verify that $ORACLE_HOME and $ORACLE_SID or

$TWO_TASK point to the correct database and directory.
• To check these variables, "echo" them in UNIX:
$ echo $TWO_TASK
->v1103
$ echo $ORACLE_HOME
->/db02/webhome/v1103
$ echo $ORACLE_SID
->atlcol06_v1103

4. Ensure that your PATH is set correctly.

• At the UNIX prompt, just type:
$ echo $PATH
->/appl01/v1103/fnd/11.0.28/bin:/appl01/v1103/ad/11.0.28/bin:
/db02/webhome/v1103/bin:/usr/sbin:/usr/bin:/usr/ccs/bin:
/usr/ucb:/dba/dbaprod:/usr/local/bin:
/hrdev/cobol.solaris/cobol/bin:/hrdev/cobol.solaris/cobol
• Look for $ORACLE_HOME/bin in the path. If it is not there, you can
add it using the command:
$ PATH=$PATH:$ORACLE_HOME/bin; export PATH

3
• Other directories need to be in your PATH as well, such as the
location of the jre executable (from the Java Runtime
Environment).
You should update adovars.env to include all non-database specific
directories in your PATH.

5. Ensure you have sufficient temporary disk space.

• You should have at least 50 MB in the temporary directories
denoted by $APPLTMP and $REPORTS25_TEMP.
• You should also have space in the operating system’s default
temporary directory (usually /tmp or /usr/tmp).

6. To start AD Administration, type "adadmin": at the

command line. Adadmin resides in the AD_TOP/bin.
$ adadmin
Copyright (c) 1997 Oracle Corporation
Redwood Shores, California, USA
All rights reserved
Oracle Applications AD Administration
Version 11.0.28
NOTE: You may not use this utility for custom development
unless you have written permission from Oracle Corporation.

4
RUNNING AD ADMINISTRATION
AD Administration asks you some initial questions.

Answering questions in AD Administration is similar to

AutoInstall.
• If you’ve used AutoInstall or AutoPatch before, most of these
questions look familiar to you.
• Pressing [Return] in answer to a question accepts the default
answer in brackets. Typing "abort" exits immediately.
• You can exit AD Administration by entering abort at any prompt.
• Similar to AutoInstall and AutoPatch, AD Administration creates
and uses restart files (ada*.rf9).

AD Administration confirms your APPL_TOP is correct.

• AD Administration log, output and restart files are written under
APPL_TOP.
Your default directory is ’/d01/appl/110’.
Is this the correct APPL_TOP [Yes] ?

AD Administration asks for the name of the log file.

• By default this is adadmin.log.
• If a log file of the same name already exists, adadmin appends this
session to the end of the log file and includes the line "Start of
AD Administration" at the beginning of each session.
AD Administration records your AD Administration session in a text file
you specify.Enter your AD Administration log file name or press [Return]
to accept the default file name shown in brackets.

Filename [adadmin.log] :

You can receive an email message if adadmin encounters a

failure.
You can be notified by email if a failure occurs.
Do you wish to activate this feature [Yes] ?

You chose to be notified by email when a failure occurs.

Please enter the email id(s) (separated by space) that notifications
should be sent to [applmgr] :

5
Some SQL scripts perform row set processing. You can set
the number of rows these scripts process.
Please enter the batchsize [1000] :

AD Administration asks what types of files you currently

have.
NOTE: If you do not have or choose not to have certain types of files
installed in this APPL_TOP, you may not be able to perform certain
tasks.

Example 1: If you don’t have files used for installing or upgrading

the database installed in this area, you cannot install or upgrade
the database from this $APPL_TOP.

Example 2: If you don’t have forms files installed in this area, you
cannot generate them or run them from this $APPL_TOP.

Example 3: If you don’t have concurrent program files installed in this

area, you cannot relink concurrent programs or generate reports from
this $APPL_TOP.

Do you currently have files used for installing or upgrading the

database installed in this $APPL_TOP [Yes] ?

Do you currently have Java and HTML files for Self-Service Applications
installed in this APPL_TOP [Yes] ?

Do you currently have Oracle Applications forms files installed

in this $APPL_TOP [Yes] ?

Do you currently have concurrent program files installed

in this $APPL_TOP [Yes] ?

AD Administration asks you to confirm the database and

database home directory.
You are about to use or modify Oracle Applications product tables
in your ORACLE database ’apptest’
using ORACLE executables in ’/d01/oracle/prod/8.0.5’.

Is this the correct database [Yes] ?

• If these values are not correct, exit adadmin (by typing abort) and
edit your $ORACLE_HOME and $ORACLE_SID or $TWO_TASK
variables as needed.

6
AD Administration asks for the SYSTEM password. It then
determines the username for your Application Object Library
user.
AD Administration needs the password for your ’SYSTEM’ ORACLE schema
in order to determine your installation configuration.

Enter the password for your ’SYSTEM’ ORACLE schema: manager

Connecting to SYSTEM......Connected successfully.

AD Administration determines the Application Object Library

schema from information in the data dictionary. It then asks
for the password for the AOL schema:
The ORACLE username specified below for Application Object Library
uniquely identifies your existing product group: APPLSYS

Enter the ORACLE password of Application Object Library [APPS] :

AD Administration determines other installation information.

AD Administration is verifying your username/password.
Connecting to APPLSYS......Connected successfully.
...
Reading product information from file...
Reading language and territory information from file...
Reading language information from applUS.txt ...
Reading database to see what industry is currently installed.
Reading FND_LANGUAGES to see what is currently installed.
Currently, the following language is installed:
Code Language Status
---- --------------------------------------- ---------
US American English Base
Your base language will be AMERICAN.
Setting up module information.
Reading database for information about the modules.
Saving module information.
Reading database for information about the products.
Connecting to SYSTEM......Connected successfully.
Connecting to APPLSYS......Connected successfully.
Connecting to SYSTEM......Connected successfully.
Reading database for information about how products depend on each
other.
Connecting to APPLSYS......Connected successfully.
Saving product information.
Connecting to SYSTEM......Connected successfully.
...
After asking these initial questions, AD Administration takes
you to the main menu.

7
AD ADMINISTRATION MAIN MENU
You can choose to maintain your Oracle Applications’
database objects or files.
AD Administration Main Menu

1. Maintain Applications Database Objects menu

2. Maintain Applications Files menu

3. Exit AD Administration

8
MAINTAINING DATABASE OBJECTS
If you choose this option you are presented with a new
submenu of choices.
Maintain Applications Database Objects

1. Validate APPS schema(s)

2. Compile APPS schema(s)

3. Recreate grants and synonyms for APPS schema(s)

4. Compile flexfield data in AOL tables

5. Maintain multi-lingual tables

6. Check DUAL table

7. Maintain MultiLingual schema(s)

8. Maintain Multiple Reporting Currencies schema(s)

9. Convert to MultiOrg

10. Return to Main Menu

Enter your choice :

Let’s look at each of these options, one at a time.

adadmin validates your init.ora parameters against

applora.txt if you select any database maintenance
tasks.

+ Note: Some tasks may not be available depending on the

configuration of your Applications database. The numbers of the
various options may therefore differ slightly (from task 7 and on).

9
1. Validate APPS schema(s)
What does it do?

Runs $AD_TOP/admin/sql/advrfapp.sql to detect problems that must be fixed

(serious discrepancies) and problems that you may want to fix (potential
discrepancies) in APPS schemas.

Specifically, the script:

• Verifies Applications packages, public synonyms, and grants required in
• SYSTEM schema
• Verifies all schemas have required AD packages
• Detects synonyms with same name as Applications schemas
• Checks for incorrectly-registered APPS schemas
• Verifies synchronization between FND_PRODUCT_INSTALLATIONS and
FND_ORACLE_USERID
• Finds invalid synonyms or missing grants/synonyms in APPS schemas
• Lists tables/sequences in APPS schema(s) and base schemas
• Identifies packages with lines of 255 characters or more (breaks MRC)
• Identifies code objects in base schemas
• Checks for invalid objects in APPS schema(s)

Adadmin will display messages to show its progress.

An output file, <APPS schema name>.lst, is produced for each APPS schema in
$APPL_TOP/admin/<db_name>/out. Review the file and fix any problems listed
by following the instructions given after the problem.

When would you run it?

You can run this task at any time, but it is most effective if run:
• immediately after an upgrade,
• before converting to Multi-Org or Multiple Reporting Currencies,
• after performing an export/import (migration), or
• when doing custom development in APPS schema(s).

You may also want to run this task whenever receiving a runtime error that
suggests a problem coming from the AD_DDL package. For example, when
flexfield view generator or document sequences fail.

10
2. Compile APPS schema(s)
What does it do?
This task compiles all invalid packages, procedures or triggers that
reside in the APPS schema(s).

This step can be run with parallel workers.

When would you run it?

You can run this task at any time, but it is most effective if run:
• when you move custom packages to the APPS schema and need to compile
them,
• after applying patches that alter packages in the APPS schema, or
• when a package is corrupt and needs to be re-compiled to be fixed.

Sample run:
Enter your choice : 2

Enter the number of workers [3] : 3

Connecting to SYSTEM/MANAGER......Connected successfully.

[Later...]
Assigned: file adappsgs.pls on worker 1 for product ad username APPLSYS.

Time is: Thu Jun 25 1998 17:43:51

Completed:file adappsgs.pls on worker 1 for product ad username APPLSYS.

Time is: Thu Jun 25 1998 17:44:36

Completed:file adappsgs.pls on worker 2 for product ad username APPLSYS.

Time is: Thu Jun 25 1998 17:44:36

Completed:file adappsgs.pls on worker 3 for product ad username APPLSYS.

Time is: Thu Jun 25 1998 17:44:36

[Later...]

Done maintaining APPS account(s).

11
3. Recreate grants and synonyms for APPS schema(s)
What does it do?
This task identifies missing grants from a base product schema to the
corresponding APPS schema or missing synonyms in the APPS schema for the
object, then recreates them. It also ensures the Applications Public schema is
set up correctly.

This task does not set up grants and synonyms for MultiLingual or
MultiCurrency schemas. To do that you must choose that specific task.

This task runs $FND_TOP/admin/sql/afpub.sql to set up grants and synonyms

for the Applications Public schema (APPLSYSPUB by default).

Then it runs $AD_TOP/admin/sql/adappsgs.sql for every Oracle Applications

base product schema (such as APPLSYS or GL). If the package notices a grant
or synonym that should exist but doesn’t, it recreates it in your database.

This step can be run with parallel workers.

Adadmin will display messages to show its progress.

When would you run it?

Occasionally, for some reason or another, grants and synonyms are missing
from an installation of Oracle Applications. This may occur as a result of custom
development, incomplete database migrations (export/imports), or patch and
administrative sessions that failed to complete successfully.

4. Compile flexfield data in AOL tables

What does it do?
This step compiles data structures into AOL tables for use by AOL features. It
runs the program $FND_TOP/bin/fdfcmp to do this.

Adadmin will display messages to show its progress.

When would you run it?

Generally, you would recompile these data structures in AOL tables after
applying a patch that changes the setup of flexfields. The patch usually indicates
that this step should be performed.

This step is never required, as FlexFields will automatically compile the data
when first used. This step alleviates a one-time runtime compilation performance
hit when automatically compiling the data.

12
5. Maintain multi-lingual tables
What does it do?
This task executes the <PROD>NLINS.sql or <PROD>NLADD.sql scripts for
multi-lingual products (AOL, AK, AX, AS, and AZ).

Multi-lingual operation uses translation (_TL) tables, which contain all translated
data associated with base tables. Each row in the translation table has a working
language and a source language. The working language indicates the rows that
are returned when running Applications forms in that language. The source
language indicates what language the data is really in.

When inserting or deleting a row in a base table/translation table through a form,

the form inserts or deletes the row, then calls a
PL/SQL procedure that copies that row in the translation table once for each
active language, setting the source language to the current working language.
(Updates are a little more complex.) This means it is up to the user to actually
translate the data later, either by running the form and updating in the other
language(s), or by manually updating the translation tables.

When installing a language for the first time, the NLINS and
NLADD scripts initially set up this process by calling this package for every
translation table owned by the product. This adadmin task re-runs these scripts
to correct any discrepancies— i.e.: fix data that was replicated for some active
languages, but not all. For each missing row, it copies the matching row for the
base language, and sets the source language equal to the base language. The
data must later be replaced by translated data, either by a patch, or manually by
the user.

The NLADD script is provided by each of the multi-lingual products in the base
release and run by AutoInstall. If it needs to be patched (because of a data
model change), it is re-released as an NLINS script. AD Administration runs the
NLINS script if it exists, or the NLADD script if it doesn’t. The NLADD and NLINS
operate identically.

Adadmin will display messages to show its progress.

+ Note: There may be a <PROD>NLINS.sql script in the base release if it was

patched after the final freeze, but it will not be called by AutoInstall.

When would you run it?

Technically, this task should never have to be run as long as all updates to the
base tables are done through Applications forms.

13
If there seems to be data missing from your translation tables, you should
choose this task to ensure the translation table contains rows for all translated
data in all active languages. This may occur if you are updating data in the
tables manually or through some other mechanism (not recommended!), or if you
have applied a patch that added new seed data improperly. (Patches to
translated data should use loaders, which populate the translation table
automatically, or SQL scripts, in which case the table handler must be called
explicitly to propagate the data to other languages.)

For example, suppose you have English and German installed. A query when
running Applications in English returns 30 rows, but when running in German
only returns 28 rows. This suggests the two extra rows exist in the translation
table for English, but not for German. The <PROD>NLINS or <PROD>NLADD
scripts, called through this adadmin task, should fix the problem.

6. Check DUAL table

What does it do?
This step looks for a DUAL table in the SYS schema, and verifies that it is
accessible by Applications by granting full access on it to PUBLIC.

If no such table exists, or if the table exists but has more than one row, AD
Administration displays an error message and fails. If the DUAL table exists and
has exactly one row, AD Administration succeeds.

Connecting to SYSTEM......Connected successfully.

SYS.DUAL has the correct number of rows.

Granting privileges on SYS.DUAL ...

Review the messages above, then press [Return] to continue.

When would you run it?

You would run this step if, for some reason, your DUAL table was dropped or
has the wrong number of rows.

Virtually no part of Applications will work if this happens.

Common symptoms include frequent occurrences of "ORA-1427: single-row
subquery returns more than one row" or "ORA-1403: no data found" errors.

14
7./8. Maintain MultiLingual or Multiple Reporting Currencies
schema(s)
What does it do?
This task invokes PL/SQL packages (see admntmls.pls and admntmcr.pls in
$AD_TOP/admin/sql) which maintain database objects for these features.

MRC and MLS are both implemented using "adjunct APPS schemas", meaning a
complete copy of the objects in each APPS schema is replicated (and enhanced,
in some cases) into an APPS_MRC and/or APPS_MLS schema. Whenever a
change is made to an APPS schema, the modifications must be reflected in the
adjunct schemas; otherwise, MRC and MLS functions may fail.

This task is only displayed on the Database Objects menu if you have
MultiLingual (MLS) or Multiple Reporting Currency (MRC) functionality currently
installed.

+ Note: If either of these menu items is not on the screen, subsequent menu
items are renumbered accordingly.

MultiLingual support is not built into base Release 11.0, although it may be
available later. (The menu option exists for Consultants implementing MLS.)

This step can be run with parallel workers.

Adadmin will display messages to show its progress.

When would you run it?

You must run this task (either or both, if the features are installed) after every
patch that updates the database to ensure that the data model is correct for
these features.

AutoPatch displays a message reminding you when this is necessary.

15
9. Convert to Multi-Org
What does it do?
This option allows you to convert a standard data group (not Multi-Org and not
Multiple Sets of Books architecture) into a Multi-Org product group with one
Operating Unit.

Before running this task, you must define an Operating Unit and set the site-level
AOL profile "MO:Operating Unit" to point to it. This profile value is used when
converting your existing data.

The specific steps adadmin performs in this task are:

• Prompts for a number of parallel workers
• Confirms you want to run this task
• Creates scripts to disable and re-enable triggers in your APPS schema
• Disables all triggers in your APPS schema
• Converts seed data and transaction data to Multi-Org (the most time-
consuming part of the operation)
• Re-enables all previously-enabled triggers in your APPS schema

This task only displays on the Database Objects menu if you have not run it
previously or if you use a Multiple Sets of Books Architecture.

+ Note: If the menu item is not on the screen, subsequent menu items are
renumbered accordingly.

When would you run it?

You run this option to set up the Multiple Organization Architecture for the first
time in a product group.

Warning: All users must log off Applications prior to and during this step
and you must shut down all concurrent managers.

This task may take anywhere from a few hours, for a fresh install, too much
longer, for an existing production database with a great deal of data. Part of the
conversion process involves updating every row in every Organization-sensitive
table with the ORG_ID of the default Operating Unit.

16
10. Convert to Multiple Reporting Currencies
What does it do?
This task creates and populates the adjunct APPS schema used for the Multiple
Reporting Currencies (MRC) feature.

Before running this task, you must perform several manual steps that validate
and clean up your data, to reduce the chances of failure during the conversion
process. See Appendix A of the Oracle Applications Installation manual for the
complete process.

The specific steps adadmin performs in this task are:

• Prompts for a number of parallel workers,
• Confirms you want to run this task,
• Creates your MRC schema(s) (one per product installation group),
• Creates the correct system privileges and grants in your MRC schema(s),
• Registers your MRC schema(s) with Oracle Applications,
• Sets up one or more data groups for your MRC schema(s),
• Makes multiple copies of MRC responsibilities in all other sets of books if
running in a configuration using MSOBA,
• Calls a PL/SQL procedure (see $AD_TOP/admin/sql/admntmcr.pls) which
replicates database objects from your APPS schema to your MRC schema(s),
• Compiles all invalid objects in your MRC schema(s),
• Creates MRC triggers in your APPS schema.

This task only displays on the Database Objects menu if you have not run it
previously (and therefore have not implemented MRC support).

+ Note: If the menu item is not on the screen, subsequent menu items are
renumbered accordingly.

When would you run it?

You run this option to set up the Multiple Reporting Currencies feature for the
first time.

Warning: All users must log off Applications prior to and during this step
and you must shut down all concurrent managers.

This task may take anywhere from a few hours, for a fresh install, to much
longer, for an existing production database with a great deal of data. Part of the
conversion process involves updating every row in every Organization-sensitive
table with the ORG_ID of the default Operating Unit.

17
MAINTAINING FILES
If you choose option to maintain files then you are presented
with another submenu of choices.
Unix:
Maintain Applications Files

1. Create Applications environment file

2. Relink Applications programs

3. Copy files to destinations

4. Verify files necessary for runtime

5. Generate message files

6. Generate form files

7. Generate report files

8. Return to Main Menu

Enter your choice:

NT
Maintain Applications Files
----------------------------------------

1. Create Applications environment subkey in registry

2. Copy files to destinations

3. Verify files necessary for runtime

4. Generate message files

5. Generate form files

6. Generate report files

7. Return to Main Menu

Enter your choice :

Menu item number one is different for Unix and NT.

The Unix menu has an additional item: number 2. You don’t need to relink on
NT.

18
This will be different in 11i, because the object files will be shipped for NT and
relinking also has to happen on NT.

19
1. Create Applications environment file/ Create Applications
environment subkey in registry
What does it do?
This creates an environment file for your current Oracle Applications
configuration. It also creates the env.html file that is stored under $JAVA_TOP
and used by the security procedures for HTML-based functionality.

When would you run it?

Choose this task any time your environment settings have changed or need to
be changed. Examples of this include:
• when you move a product top directory to another disk,
• when you installed a new product group using the existing APPL_TOP,
• when you want to change your log/output directories,
• when you want to enable or disable parallel concurrent processing,
• when your environment file is missing or corrupted.
Do not edit your environment files manually, as there are dependencies that are
easily overlooked (such as the env.html file).

NT:
Enter the name of your Oracle Applications registry subkey below.
Subkey name [VD11] :

The concurrent managers can put all the log and report files in a
where the client machines can view them.

Enter the name of this common area below, or press [Return]

if you want log and report files for each application to go
in that application's log and output subdirectories.

Enter the name of the common area: [E:\oa\appltst\common\VD11]

Enter the log subdirectory name for this product group [log] :
Enter the output subdirectory name for this product group [out] :
Enter the directory for Applications temporary files [C:\temp] :
Enter the directory for Oracle Reports temporary files [C:\temp] :

Some PL/SQL programs produce temporary log/output files. The directories

used for this must be listed in the init.ora parameter "utl_file_dir".
The value of utl_file_dir for this database is:

"E:\oa\orant\plsql80\temp"

Enter the directory for temporary log/output files from PL/SQL programs.
Directory:

If all of your products are not physically located in the same APPL_TOP,
AD Administration cannot generate the correct environment file without
reading the file E:\oa\appltst\admin\topfile.txt.
Make sure the product locations listed in this file are correct
before contining, or type "abort" to exit AD Administration.

Do you want to read topfile.txt [Yes] ?

20
2. Relink Applications programs
What does it do?
Relinks your Oracle Applications binary executables.

When would you run it?

If you install a new version of or a patch to the Oracle8 Server, the networking
layer, or another underlying technology component that Oracle Applications
relies on, then you should relink all programs.
You should also relink when a patch readme.txt file tells you to.
• Most patches link executables automatically, but some executables may
require other technology components that may not be installed.
Before performing the relink, adadmin reminds you to ensure your environment
file exists and is correct, and that you have listed any executables you want to
backup in the adlinkbk.txt file.

AD Administration asks which products you want to link. You can choose all
products (the default), or a subset of products. You then have the option of
linking all executables (the default) or only specific ones for each product you
have chosen. Finally, you can link with debug information intact (typically you
should only do this if instructed to do so by Support/Development).

If you choose to link only specific executables, adadmin shows a list of

executables for the first product and allows you to list the programs you want to
link. It then links those programs and repeats the process for all other products
you’ve selected.

21
Sample run Unix:
Enter your choice : 2

AD Administration uses your Oracle Applications environment file

to set up the environment for relinking Applications.

Before proceeding with the relink, you may optionally want to:
- Go back to the menu by answering No below.
- Use an option on the Maintain Files menu
to generate your Applications environment file.
- Edit the file to add any customizations.
- Verify the list of executables in adlinkbk.txt which are saved
before relinking and add any additional executables as desired.
- Choose this option again, and proceed with the relink.

Do you wish to proceed with the relink [Yes] ?

Enter the name of your Oracle Applications environment file below.

File name [apptest.env] :

Reading product executable information...

Enter list of products to link (’all’ for all products) [all] : oe inv

Generate specific executables for each selected product [No] ? yes

Relink with debug information -

choose ’Yes’ only if instructed by Oracle Support (Yes|No) [No] :

Relinking selected modules in Oracle Order Entry.

List of executables in Oracle Order Entry :

OEBSHC OECMWC OEKCII OEOBOE OEOCSO

OEORPC OEPAII OEPCPL OEPMLP OEPREL
OERLDI OERLRI OERPRS OESHTM OEVINV
OEWREL OEZMAI WSHARI WSHREL

Enter executables to relink, or enter ’all’ [all] : OEORPC

**********************************************************
You are running adrelink, version 110.33

Start of adrelink session

...

22
3. Copy files to destinations
What does it do?
Oracle Applications’use of Oracle Forms, Oracle Reports, Java and
HTML files require some files to be installed under common directories. This
option reads the product driver files to determine the set of files to copy from the
product tree to the destination (such as AU_TOP or JAVA_TOP). You are
prompted if you wish to copy a file only if it is missing (the default), or to
overwrite.

When would you run it?

If you encounter problems where Oracle Applications cannot find a necessary
file, then run this option.

The problem would typically manifest itself in form and report generation, or
while executing HTML-based functionality.
Do you wish to copy UNCONDITIONALLY when a target file exists [No] ?

Adadmin will display messages to show its progress.

4. Verify files necessary for runtime

What does it do?
This task verifies that all necessary product files required for the current
installation configuration are present. It operates in the same way as it does in
AutoInstall. It compares all the files in the product driver files (fndfile.drv,
arfile.drv etc.) against the files that are actually on the server.

When would you run it?

If you encounter a problem with a file missing at runtime, then run this task.
AD Administration records the output from
"verifying that all required files exist" in a file in the
E:\oa\appltst\admin\VD11\out directory.
If the file already exists, it will be overwritten.

Please enter the filename you wish to use or press [RETURN] to accept
the default filename
[admvrf.lst] :

Adadmin will display messages to show its progress.

23
5. Generate message files
What does it do?
This step generates the binary US.msb files for each Application and each
language from the database definition.

When would you run it?

Generally, you should only regenerate Applications messages files when the
readme.txt portion of a patch tells you to do so.
Adadmin will display messages to show its progress.

+ Note: In Release 11.0, AutoPatch can only automatically generate messages

on an admin server. Therefore whenever message files need to be regenerated,
it is always documented as a manual step in the readme.txt file.

6. Generate form files

What does it do?
This task generates Oracle Forms 4.5 PL/SQL libraries, menu files, and binary
(.fmx) files based on the source (.fmb) files.

The task first verifies your database character set, then asks for each type of file
if you want to regenerate Forms PL/SQL library files (pll to plx), menu files (mmb
to mmx), and executable files (fmb to fmx). The defaults are to regenerate all file
types.

The remainder of the task operates in the same manner as the "Relink
Applications programs" task. It asks which products you want to regenerate files
for, then asks if you want to regenerate specific forms objects for each selected
product.

If you choose to generate only specific objects, adadmin shows, in turn, a list of
library files, a list of menu files, and a list of forms files for the first product and
allows you to list the programs you want to link. It then generates those files and
repeats the process for all other products you’ve selected.

This task can be run with parallel workers.

When would you run it?

Since form generation is extremely time consuming, you should only perform this
task if installing a language in a character set other than what it is shipped in, or
if instructed to in the readme.txt of a patch.

24
Sample run:
Enter your choice : 6

Enter the number of workers [3] :

Your current character set is "WE8ISO8859P1".

Do you want to generate Oracle Forms objects

using this character set [Yes] ?

Do you want to regenerate Oracle Forms PL/SQL library files [Yes] ?

Do you want to regenerate Oracle Forms menu files [Yes] ?

Do you want to regenerate Oracle Forms executable files [Yes] ?

Enter list of products (’all’ for all products) [all] : qa

Generate specific forms objects for each selected product [No] ? yes

Reading product form information...

Selecting Oracle Forms PL/SQL library files and menu files to

generate...

Selecting library and menu files for Oracle Quality...

List of libraries and menus in Oracle Quality :

QLTCORE.pll QLTENGIN.pll QLTRES.pll QLTTXN.pll QLTVAL.pll

Enter libraries and menus to generate, or enter ’all’ [all] : all

Selecting product forms to generate...

Selecting forms for Oracle Quality...

List of forms in Oracle Quality :

QLTALINF.fmx QLTCHMDF.fmx QLTCIMDF.fmx QLTPLMDF.fmx QLTRSINF.fmx

QLTRSMDF.fmx QLTSCMDF.fmx QLTSPECF.fmx QLTSTAND.fmx

Enter forms to generate, or enter ’all’ [all] : QLTRSINF.fmx

QLTRSMDF.fmx

Generating Oracle Forms objects...

...

25
7. Generate report files
What does it do?
This step generates Oracle Reports PL/SQL libraries and binary (.rdf) files. You
should only perform this task if installing a language in a character set other than
what it is shipped in, or if instructed to in the readme.txt of a patch.

The task operates similarly to form generation. It first verifies your database
character set, then asks for each type of file if you want to regenerate Reports
PL/SQL library files (pll to plx), and executable files (rdf to rex, back to rdf). The
defaults are to regenerate all file types.

It then asks which products you want to regenerate files for, then asks if you
want to regenerate specific reports objects for each selected product.

If you choose to generate only specific objects, adadmin shows a list of library
files, followed by a list of reports, for the first product and allows you to list the
programs you want to link. It then generates those files and repeats the process
for all other products you’ve selected.

When would you run it?

You should only regenerate Applications report files when the readme.txt portion
of a patch tells you to do so.

26
NEW AND CHANGED FEATURES
11.0 New Features
• Support for installation files in a subdirectory under
$APPL_TOP/admin.
• Support for failure notifications via email.
• More granularity on relinking of executables and generation of
forms, menus, and PL/SQL libraries.
• Support for MRC conversion and MRC and MLS maintenance.

Changes from 10.7

• Different interview questions to determine file types for the
installation you are maintaining.
• AD Administration requires a database connection and that you
specify the SYSTEM password.
• Dropped support for validation of SYSTEM.DUAL as Applications
code should no longer reference this. Validate DUAL instead.
• Removed support for CRT as there is no use of SQL*Forms.
• Removed support for compiling menu or form structures in AOL
tables.
• Removed "Return to Main Menu" options from the submenus. Use
• [Return] instead.

Changes from 10.6

• The additional step "Identify extra files" in the file system was
removed.
• The "Verify database objects" task was removed. This verification
would not account for patches made to the data model.
• The default password for the AOL schema is APPS (previously
FND).

27