2
The Standalone Console

Beginning with Release 9.0 when you launch the Enterprise Manager Console or various other Enterprise Manager applications, you are prompted to choose between launching the product standalone (i.e. not connecting to the middle tier Management Server) or logging into a Management Server.

Launching the Console standalone allows a single administrator to perform simple database schema, instance, storage, security, and other database tasks by connecting directly to the target database(s).

Launching standalone does not require a middle tier Management Server or Intelligent Agents on target machines.

This chapter discusses the topics listed below:

• Choosing to Launch the Console Standalone
• Starting the Standalone Console
• Adding Databases to the Tree in the Standalone Console
• Connecting to a Database in the Standalone Console
• Connecting to the Database As a Different User
• Viewing If You Are Connected As SYSDBA
• Removing a Database from the Tree
• Changing from Using the Console to the Standalone Console
• Editing Local Preferred Credentials in the Standalone Console
• Changing from Using the Standalone Console to the Console

Choosing to Launch the Console Standalone

When you launch the Enterprise Manager Console, you are prompted to choose between launching the product standalone or logging into a Management Server.

Choose to launch the Console standalone when you want to connect directly to your managed target(s) to perform administration tasks. With Enterprise Manager Release 9.0 the standalone Console only supports connecting directly to database targets, no other target types are currently supported.

Launching standalone does not require a Management Server or Intelligent Agents on managed targets. Consequently, when you launch the Console standalone, you do not have access to functionality typically available through the Management Server and Intelligent Agent, such as:

• Management of several different target types (e.g. database, web server, application server, applications, etc.)
• Sharing of administrative data among multiple administrators.
• Proactive notification of potential problems.
• Automation of repetitive administrative tasks.
• Backup and data management tools
• Customization, scheduling, and publishing of reports
• Running the client from within a web browser.

Starting the Standalone Console

On Windows-based platforms, you start the Console from the Windows Start Menu.

You can also start the standalone Console from the command line using the command:

C:\> oemapp console

On UNIX platforms, you start the Console from the command line using the command:

$ oemapp console

Figure 2-1 Enterprise Manager Login

Text description of the illustration login_st.gif

When the dialog appears, choose "Launch standalone" and press OK.

To bypass the Console login, you can enter the following command at any supported operating system command line:

oemapp console oem.loginmode=standalone

By entering the command, you will immediately see the standalone Console.

If you are starting the standalone Console for the first time, the left panel of standalone Console is empty because you have not yet added the databases you want to manage. The Add Databases To Tree dialog appears automatically so that you can add them to the navigator tree.

Adding Databases to the Tree in the Standalone Console

The Add Databases To Tree dialog appears automatically when you start the standalone Console for the first time; it is also available from the Navigator menu.

Figure 2-2 Add Databases to Tree

Text description of the illustration add_db_t.gif

The Add Databases To Tree dialog allows you to manually enter the Net service names or add them from the local tnsnames.ora file.

Add a database manually

You can add databases to the standalone Console navigator tree by manually filling in the following fields:

• SID: the database system identifier, usually the instance name, such as ORCL
• Hostname: the machine or node name where the database is located
• Port Number: the database listener port address, usually 1521 or 1526
• Net Service Name: A name which uniquely identifies a database when connecting to a machine. It is usually the global database name.

  For example: ORCL.world.

.

Add selected databases from your local tnsnames.ora file

You can populate the standalone Console navigator tree by reading the database service names from the local tnsnames.ora file located in your Oracle Enterprise Manager home. The Add Databases To Tree dialog displays a list of databases identified in your tnsnames.ora file from which you can select or deselect. Click the column header to the left of Service Name to either select or deselect all the databases. If you have deselected all the databases, you can choose specific databases by selecting their checkboxes.

Connecting to a Database in the Standalone Console

There are three ways to connect to a database for the standalone Console:

• Click the plus symbol next to the database icon in the Console navigator tree. The preferred credentials are used if the connection information has not been set previously.
• Double-click the database icon in the standalone Console navigator tree. The preferred credentials are used if the connection information has not been set previously.
• Select the database and then select the Connect item from the Navigator menu.

If no preferred credentials are set in the Oracle Enterprise Manager Console, the Database Connection Information dialog box appears. If preferred credentials are already set, you will connect to the database using this login information.

In the Database Connect Information dialog, enter the following information to connect to the database.

Username

The Oracle username for the database to which you are connecting.

For example: system

Password

The password for the username to which you are connecting.

For example: manager

Connect As

You can select from a pull-down list whether you want to connect to the database with NORMAL, SYSOPER, or SYSDBA privileges. Select NORMAL to connect to the database as an ordinary user. Select SYSOPER to connect to the database with special operator privileges, such as capabilities to shut down and start up the database. Select SYSDBA to connect to the database as a user with full database privileges such as the capability to grant any privileges to any user.

To use SYSOPER and SYSDBA privileges, a password file or OS group authentication must be created and set up for your database.

Save As Local Preferred Credentials

Saving preferred credentials is an option which enables you to store login information in a local file such as username, password, and role (NORMAL, SYSOPER, or SYSDBA). Passwords are always stored in encrypted format.

This login information is used when a connection is established for the database instead of having to type a username and password each time.

You can set preferred credentials by selecting the Save As Local Preferred Credentials checkbox or you can save credentials later by using the Edit Local Preferred Credentials dialog available from the Configuration menu.

Connecting to the Database As a Different User

In the standalone Console, you do not have to disconnect as a user before reconnecting as a different user.

If you are already connected to a database and you want to reconnect as a different user

• Right-click the database icon and select Connect from the context-sensitive menu.
• Select the Connect item from the Navigator menu.

When the Database Connect Information dialog appears, enter a different username and press OK.

You will automatically be disconnected and reconnected.

Viewing If You Are Connected As SYSDBA

When a connection is made to a database, a connection icon is displayed on top of the database icon in the standalone Console tree.

Next to the database name, you will see the username and role, if applicable, that you are connect as. For example, if you have connected as user SYS with the SYSDBA role, you should see "sys as SYSDBA."

Removing a Database from the Tree

To remove a database from the standalone Console navigator tree, follow the steps below:

1. Highlight the database you want to remove.
2. From the Navigator menu, choose Remove Database from Tree item.
3. A message appears, saying, "Remove the <name> database from tree. Are you sure?" Click the Yes button.

Changing from Using the Console to the Standalone Console

When the Console is connected to an Oracle Management Server, the Console navigator tree is populated with the discovered databases.

The following steps describe how to copy these databases so they can be used in standalone mode.

The databases displayed in the navigator tree can be added to the tnsnames.ora file and their associated preferred credentials saved to a local file:

1. Use the Add Services to tnsnames.ora from the Configuration menu to copy the services to the local tnsnames.ora file.

To make these databases available in standalone mode, you can perform the following steps:

2. Start the standalone Console.
3. From the Navigator menu, select the Add Databases To Tree item.
4. In the Add Databases to Tree dialog, select the Net service names to add from the local tnsnames.ora file.
5. To save the local preferred credentials of a service, select the Edit Local Preferred Credentials item from the Configuration menu.

Editing Local Preferred Credentials in the Standalone Console

The standalone Console stores a list of databases that are displayed in the standalone Console navigator tree. If preferred credentials are specified for any of these databases, the username, encrypted password, and role are added to the local file. The local record, dbastudio-<os_username>.crd, is located in the <Oracle_Enterprise_Manager_Home>/sysman/config/pref directory.

The login information is used when a connection is established to the database instead of having to type a username and password each time.

To save or edit the local preferred credentials of a service, you can perform the following steps:

1. From the Configuration menu, select the Edit Local Preferred Credentials item. The Edit Local Preferred Credentials dialog displays a list of services.

Figure 2-3 Edit Local Preferred Credentials

Text description of the illustration edit_pc.gif

• In the Edit Local Preferred Credentials dialog, select the service name of the database and enter or update the preferences for connecting to that database.
  • Username: Enter the username. This field is required if a password has been entered.
  • Password: Enter the password. You can leave this blank if you want to be prompted for a password when you connect to the database.
  • Confirm Password: Confirm the password. The contents of this field must be the same as the contents of the Password field.
  • Role: Select the role from the pull-down list. You must login with the SYSDBA or SYSOPER role to start up or shut down a database.
• Click the OK button at the bottom of the Edit Local Preferred Credentials dialog to save your updates.

  Note: You can save or overwrite the preferred credentials by selecting the "Save As Local Preferred Credentials" checkbox in the Database Connection dialog.

  
  
  

  Changing from Using the Standalone Console to the Console

  After you have started the standalone Console, and you want to connect to a management server (switching therefore from standalone into distributed mode), you must close and restart the Console.

  If you have been using standalone Console, the list of databases displayed in the navigator tree is retrieved from a local file.

  At some stage in the future, you may decide to administer jobs, events, and groups; run the database applications through a web browser; or perform backup and data management tasks. These tasks require you to run the Console connected to an Oracle Management Server.

  If you now decide to run the Console connected to an Oracle Management Server, the databases displayed in the navigator tree may be different than those in standalone mode, because the list of databases is retrieved from the repository and not from a local file.

  To add the databases that were available from the standalone Console, you will need to discover the services from the Oracle Enterprise Manager Console if the databases are not already available from the Console connected to the Oracle Management Server.