Author: Syed Saad Ali
Oracle AD Controller
- ADCTRL is used to manage worker processes that perform a pivotal role in the function of batch processing for patching and many other Applications activities.
- ADCTRL is located under $AD_TOP/bin directory with Oracle E-Business Suite.
Procedure to Run AD controller
Step 1 : Login as Applications Tier user & run the environment file.
$cd /prod/ebs/apps/prodappl
$ . ./APPSORA.env
Step 2 : Run the following AD controller command.
$ adctrl
You will be prompted for the location of $APPL_TOP, Password of APPLSYS and APPS. After providing the above information the AD controller menu will appear as shown below.
AD Controller Menu
- Show worker status
- Tell worker to restart a failed job
- Tell worker to quit
- Tell manager that a worker failed its job
- Tell manager that a worker acknowledges quit
- Restart a worker on the current machine
- Exit
Checking Status of the Worker
choose the first option “Show worker status“.
Note: If there is no session used by the workers, then the following message will appear:
Error: The FND_INSTALL_PROCESSES table does not exist.
This above given table is used for communication with the worker processes, and if it does not exist, it means that the workers are not running, and the ad utility has not started them yet.
Meaning of Worker Status
STATUS |
Description |
| Waiting | The worker is idle. |
| Assigned | A job was assigned by the manager to a worker but the worker didn’t start the job. |
| Running | The worker is running a job. |
| Failed | The job failed due to an error. |
| Fixed, Restart | When a jobs restart after the error has been fixed (during this time the worker run the failed job). |
| Restarted | After the error has been fixed, the worker will have the status “Fixed, Restart” and after that “Restarted”. (The status will not change to “Running”) |
| Completed | The job was completed and the manager did not yet assigned another job to that worker. |
Database Processing Phases Concept
- Whenever a Database Patch operation will runs, the tasks are divided into functions. This is done by Oracle when the patch is created.
- Suppose a patch will create 2 tables and 2 sequences. In this case the patch driver contains 2 phases, one for tables creation and one for sequences creation.
- Because the sequences could be created in the same time, this will be done in parallel by using more workers.
Examples of Database Processing Phases:
seq = create sequence
tab = create tables, synonyms, grants privileges on tables pls = create package specification
plb = create package body
vw = create views
List of All active Transactions
ORACLE APPLICATIONS R12 ARCHITECTURE
- Oracle E-Business Suite Release-12 have a Multi-tiered Architecture, that supports Oracle Applications products.
- They are comprised of a Database Tier which manages the Oracle Database and stores all data.
- An Application Tier hosts various servers, manages communication between the desktop and database tier and contains the application file system.
- A Client Desktop through which user access Oracle Applications.
Architecture-R11i vs R12
1. Desktop Tier
- The client interface is provided through HTML for HTML-based applications, and via a Java applet in a Web browser for the traditional Forms-based applications.
- In Oracle Applications Release 12, each user logs in to Oracle Applications through the E-Business Suite Home Page on a desktop client web browser.
- The E-Business Suite Home Page provides a single point of access to HTML-based applications, Forms-based applications, and Business Intelligence applications.
- Oracle JInitiator will no longer be required to run Oracle Forms in E-Business Suite Release 12.
- Oracle Forms in Release 12 will run directly in the native Sun Java2 Standard Edition plug-in.
- The Forms client applet is a general-purpose presentation applet that supports all Oracle Applications Forms-based products, including those with customization and extensions.
- The Forms client applet is packaged as a collection of Java Archive (JAR) files.
- The JAR files contain all Java classes required to run the presentation layer of Oracle Applications forms.
2. Application Tier
- The application tier has a dual role, hosting the various servers and service groups that process the business logic, and managing communication between the desktop tier and the database tier.
- This tier is sometimes referred to as the middle tier.
- Four servers or service groups comprise the basic application tier for Oracle Applications:
- Web services
- Forms services
- Concurrent Processing server
- Admin server
3. Database Tier
- The database tier contains the Oracle database server, which stores all the data maintained by Oracle Applications.
- The database also stores the Oracle Applications online help information. More specifically, the database tier contains the Oracle data server files and Oracle Applications database executable that physically store the tables, indexes, and other database objects for your system.
- The database server does not communicate directly with the desktop clients, but rather with the servers on the application tier, which mediate the communications between the database server and the clients.
Oracle RMAN Commands List
Here is the list of key most RMAN commands that are used for Backup and related activities:
LIST Commands
LIST Commands are generic RMAN commands that will show/list various types of information when executed within RMAN utility.
RMAN> list backup;
It lists all the backups taken using RMAN utility.
RMAN> list backup of database;
The above command lists out all the (individual) files that are in the backup.
RMAN> list backup of tablespace system;
The above command lists out all the files that are in the backup that belong to the tablespace ‘system’.
RMAN> list backup of control file;
The above command lists out all backups of the control file.
CONFIGURE Commands
CONFIGURE commands in RMAN are used to configure/setup various initial settings:
RMAN>CONFIGURE RETENTION POLICY TO REDUNDANCY2;
The above commands indicates how many days the backup copies need to be retained. Default is 1 day.
RMAN> CONFIGURE RETENTION POLICY CLEAR;
The above command resets the Retention policy to the default value of 1 day.
CONFIGURE BACKUP OPTIMIZATION ON;
The above command verifies to make sure that identical files are NOT backed up to the device specified.
CONFIGURE BACKUP OPTIMIZATION CLEAR;
The above command resets the Optimization option to the default value.
SHOW Commands
Show commands are used to show/display the configuration setting values.
RMAN> show all;
The above command shows all the current configuration settings on the screen.
RMAN> show retention policy;
The above command shows the current retention policy.
RMAN> show default device type;
The above command shows the default device type configured for backups.
RMAN> show datafile backup copies;
The above command shows the number of backup copies available in the target database.
BACKUP Commands
Backup commands are the real commands which do the actual backup work.
RMAN> backup database;
The above command backs up the database (target).
RMAN> backup database include current controlfile plus archive log;
The above command backs up the target database and the current control file and archive log files.
REPORT Commands
Report commands list/report specific information. The difference between report and list command is report command output is in a better format.
RMAN> report obsolete;
The above command reports which backups can be deleted.
DELETE Commands
Delete commands delete/remove specific items from the server, repository catalog.
RMAN> delete obsolete;
The above command deletes all the backups that are older based on the retention policy setup.