Monitoring the Oracle Database Appliance - Practical Oracle Database Appliance - page 98

Using the Enterprise Manager Configuration Assistant (EMCA)
As with anything a DBA does from the command line, you need to set your Oracle Home for the database that is
to be configured. On the Oracle Database Appliance, this is as simple as running the oraenv command to set the
environment. Listing 6-1 gives an example of how to set the environment and how to check the environment once set.

Listing 6-1. Setting the Oracle Environment and Checking It

$ . oraenv
ORACLE_SID = [oracle] ? dboda
The Oracle base has been set to /u01/app/oracle

$ env | grep ORA
ORACLE_SID=dboda
ORACLE_BASE=/u01/app/oracle
ORACLE_HOME=/u01/app/oracle/product/11.2.0.3/dbhome_1

Now that the Oracle environment is set, you can run the emca utility from either the bin directory under the
Oracle Home or from where you currently are. Listing 6-2 illustrates running the emca utility from the Oracle Home
bin directory.

Listing 6-2. Execute EMCA from bin

$ cd $ORACLE_HOME/bin
$ ./emca

When running the emca command, there are optional parameters that can be passed on the command line to
help configure the Database Control. Table 6-1 will help you understand what these parameters are. The Enterprise
Manager Configuration Assistant (EMCA) command follows a simple form, as outlined in Listing 6-3.

Listing 6-3. EMCA Command Pattern

./emca [operation] [mode] [flags] [parameters]

Table 6-1. EMCA Command-Line Parameters

Parameter Description

-respFile Specifies the path of an input file listing parameters for EMCA to use while

performing its configuration operation. For more information, see “Using an
Input File for EMCA Parameters.”

-SID

Database system identifier.

-PORT Port number for the listener servicing the database.

-ORACLE_HOME Database Oracle Home, as an absolute path.

-ORACLE_HOSTNAME Local database hostname.

-LISTENER_OH Oracle home from which the listener is running. If the listener is running from

an Oracle Home other than the one on which the database is running, the
parameter LISTENER_OH must be specified.

( continued )