Oracle Apps DBA tool: ADADMIN instructions

ADADMIN usage

ADADMIN is used to maintain the Oracle Apps file system and database. It is a common tool for Apps DBAs.

(The ADADMIN execution file is located under $ AD_TOP/bin)

Usage

Oracle@www.bkjia.com ~ $Adadmin

If the ADADMIN command cannot be run, it is likely that the environment variable is not set. You can run ". $ APPL_TOP/instance. env" to set the environment variable. During adadmin execution, the password of the database system user and the password of the apps user are required.

Menu items of ADADMIN

ADADMIN has five level-1 menus, each of which has detailed functional items.

Level 1 menu

AD Administration Main Menu

1. Generate Applications Files menu
2. Maintain Applications Files menu
3. Compile/Reload Applications Database Entities menu
4. Maintain Applications Database Entities menu
5. Change Maintenance Mode
6. Exit AD Administration

Detailed function items under each level-1 menu

Generate Applications Files

If the system user cannot access Message, Form, or Report, you can try to solve the problem by using the menu under "Generate Applications Files.

1. Generate message files

This task generates message binary files in the $ PROD_TOP/mesg directory from oracle application object library tables. We generally perform this task only when implements ucted to do so in a readme file of a patch.

2. Generate form files

Generate the fmx file under $ AU_TOP/forms/<LANG>/in <PROD> _ TOP/forms/<LANG>.

3. Generate report files

Generate a report file (. rdf) based on the Installation Language)

4. Generate graphics files

This task generates Oracle graphics files for all installed programming ages. extension of the file name like (*. ogd), The serious of prompts and actions in this task are very similar to the prompts and actions in the Generate form files task.

5. Generate product JAR files

GenerateJava archive (JAR) files whenever you upgrade the Developer technology stack orwhen recommended by Oracle Support Services. It signs JAR files (if on the Webserver) and does the following: ■ Generates product JAR files in JAVA_TOP and copies them to APPL_TOP. ■ Generates other Java-related files under APPL_TOP and JAVA_TOP. ■ Recreates Java libraries (export borg.zip and export borg2.zip) under APPL_TOP andJAVA_TOP.

6. Return to Main Menu

Maintain Applications Files

"Maintain Applications Files" is mainly used to keep your system Files up to date. For example, you need to copy a file from a specific location or convert the character set of the file.

1. Relink Applications programs

Relinks Oracle Applications executable programs with the Oracle server libraries so that they function with the Oracle database. For each product, choose whether to link all executables or only specific ones. Note: The default is to relink without debug information. Use the debug option only when requested to do so by Oracle Support Services.

2. Create Applications environment file

3. Copy files to destinations

Copies files from each product area to central locations where they can be easily referenced by non-Applications programs. this option uses revision-based copy logic to ensure that the destination file versions are the same as, or higher than, the source file versions.
Note: Were commend that you do not use the force option to overwrite existing files unless than ucted by Oracle Support Services. copying files with this option updates all JAR files. JInitiator then downloads required JAR files to each client again, causing runtime performance degradation.
The file types and their respective destinations are shown in the following table:
These files: copied to (UNIX) Java files $ JAVA_TOP HTML files $ OAH_TOP Media files $ OAM_TOP Note: When this option is used to copy reports or graphics files, the default destinationis under AU_TOP.

4. Convert character set

Preparesthe files in the APPL_TOP for conversion to another character set, and then performs the conversion.
When you choose this option, AD Administration presents another submenu, which contains options for scanning your files in preparation for the conversion. the scan searches for exceptions-files that will have incomplete (lossy) conversions-so that you can fix potential problems before you actually convert the character set. choose one of the following scan options.
1. Scan the APPL_TOP for exceptions. Scans the APPL_TOP and creates three files in the admin \ <SID> \ out directory.
File Contents Admanifest_excp.lst Lists files that will not be converted because of lossy conversion. admanifest. lst Lists files thatcan be converted. Admanifest_lossy.lst Lists files with lossy conversions, including line by line detail.
Review the files listed in admanifest_excp.lst. fix files that report lossy conversion before you convert the character set. repeat this task until there are no entries in admanifest_excp.lst. if you need to see more detail, review admanifest_lossy.lst.
2. Scan a CUSTOM directory for exceptions. Collects the same information as the firsttask, but scans custom Applications directories rather than the APPL_TOPdirectory. 3. Convert character set. Run this task only if admanifest_excp.lst has no entries. Itprompts you for the manifest file (admanifest. lst) created when you ran the scan option (s ).
The utility backs up the product source files and the APPL_TOP/admin source files. it saves product files in the <PROD> _ TOP directories in the format <prod> _ s _ <char_set>. zip. it saves admin source files in the APPL_TOP/admin directory in the format admin_s _ <char_set>. zip

5. Maintain snapshot information

There are two types of snapshots: APPL_TOP snapshots and global snapshots. an APPL_TOP snapshot lists patches and versions of files in the APPL_TOP. A global snapshot lists patches and latest versions of files in the entire Applications system (that is, every SS all APPL_TOPs ).

Both APPL_TOP snapshots and global snapshots may be either current view snapshots or named view snapshots. A current view snapshot is created once and updated when appropriate to maintain a consistent view. A partial view snapshot allows you to synchronize only selected files from a current view. A named view snapshot is a copy of the current view snapshot at a participant time (not necessarily the latest current view snapshot) and is not updated.

Patch Wizard uses the information contained in the global current view snapshot to determine which patches have already been applied. autoPatch uses the APPL_TOP current view snapshot to determine if all prerequisite patches have been applied to that APPL_TOP. snapshot information is stored in the AD_SNAPSHOTS, AD _ SNAPSHOT_FILES, and AD_SNAPSHOT_BUGFIXES tables.

During a new installation, Rapid Install creates a current snapshot as a baseline. and, each time you run AutoPatch, it automatically creates a new (updated) snapshot so that the information is current as of the application of the patch.

Maintain Snapshot Information menu options:

■ List snapshots (stored in the system)
■ Update current view snapshot (full or partial APPL_TOP and global)
■ Create named snapshot (select a current view snapshot to copy and name)
■ Export snapshot to file (select one to export to a text file)
■ Import snapshot from (a text) file
■ Delete named snapshot (select a snapshot for deletion)

6. Check for missing files

Verifies that all files needed to run Oracle Applications for the current configuration are in the current APPL_TOP. Choose this task if you suspect there are files missing in your APPL_TOP.

7. Return to Main Menu

1 2 Next Page