8
Setting Up DBA Studio

The DBA Management Pack features DBA Studio and SQL*Plus Worksheet.

DBA Studio combines the functionality of multiple database tools and master view detail so that you can access database administration features and manage multiple databases from one tool:

• Instance Management: Start or shut down a database, edit database initialization parameters, manage resource allocations and users' sessions.

• Security Management: Administer users, privileges, and profiles.

• Schema Management: Create, edit, and examine schema objects.

• Storage Management: Administer tablespaces, datafiles, rollback segments, and redo logs. You can also view controlfile and archive log information.

In previous releases of Enterprise Manager, there were individual database tools (Instance Manager, Schema Manager, Storage Manager, and Security Manager) for performing the above functions. Should you want to continue using these separate independent tools rather than the well-integrated DBA Studio, refer to the installation guide provided with the database release for instructions on installing them.

DBA Studio can be used to perform your database administration tasks and supports versions of Oracle databases back to 7.3.4. Analyze, Backup Management, Data Management, Dimension Creation, Summary Advisor, Create Table, and Create View wizards are also available.

This chapter discusses the topics listed below:

• DBA Studio in Standalone or Management Server Mode

• Setting Up DBA Studio in Standalone Mode

• Setting Up DBA Studio in OMS Mode

• Other DBA Studio Procedures

DBA Studio in Standalone or Management Server Mode

When you start DBA Studio, you can connect either directly to the databases (in standalone mode) or through an Oracle Management Server (in OMS mode).

Direct Connection to Databases

Run DBA Studio in standalone mode if you want to perform basic administrative tasks that do not require the job, event, or group system. If you connect in standalone mode, DBA Studio has access to the databases you have set up in a local record of databases.

Note: A Management Server and repository are not required if you only plan to run DBA Studio connected directly to the databases (in standalone mode).

Connection through the Oracle Management Server

Run DBA Studio in OMS mode if you want to:

• use the Oracle Enterprise Manager framework

• perform basic administrative tasks that require events or groups

• access all databases previously discovered from the Console

• run DBA Studio through a web browser

• use the analyze, backup, and data management wizards

If you connect to an Oracle Management Server, DBA Studio has access to all databases on the discovered nodes. The Oracle Management Server must be running for DBA Studio to connect to it.

Setting Up DBA Studio in Standalone Mode

To run DBA Studio in standalone mode, you do not have to have an Oracle Enterprise Management Server or repository set up.

To set up DBA Studio in standalone mode, you must perform the following tasks:

• start DBA Studio

• add net service names (the databases you want to manage) to the DBA Studio navigator tree

• connect to the database

• set up local preferred credentials if you want

Starting DBA Studio in Standalone Mode

1. Start the DBA Studio.
   • On Windows NT:

     You can start the DBA Studio from the Windows Start Menu->Programs->Oracle-<Oracle_Home_Name>-> DBA Management Pack->DBA Studio.

     You can also start the DBA Studio from the command line using the command:

     oemapp dbastudio
     

   • On UNIX:

     You can start the DBA Studio from the command line using the command:

     oemapp dbastudio
     
     

2. When the login dialog appears, choose Connect directly to databases and press OK.

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

Adding Databases to the Tree in DBA Studio Standalone Mode

The Add Database To Tree dialog appears automatically when you start DBA Studio for the first time; it is also available from the File menu.

The Add Database 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 DBA Studio 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.

.

Note: Adding a database manually automatically updates the local tnsnames.ora file located in your <Oracle_Enterprise_Manager_Home>/network/admin directory.

Note: Currently only TCP/IP service names can be manually entered.

Add selected databases from your local tnsnames.ora file

You can populate the DBA Studio navigator tree by reading the database service names from the local tnsnames.ora file located in your Oracle Enterprise Manager home. The Add Database To Tree dialog displays a list of databases identified in you 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.

Note: All protocols are supported when you import selected services from your tnsnames.ora file.

Connecting to a Database in DBA Studio Standalone Mode

There are four ways to connect to a database for DBA Studio:

• Click the plus symbol next to the DBA Studio navigator tree container

• Double-click the database icon in the DBA Studio navigator tree

• Select the Connect item from the File menu.

• Click the Connect icon from the toolbar.

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

Username

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

For example: system

Password

Your Oracle password for the database to which you are connecting.

For example: manager

Service Name

Network service name for the database to which you are connecting.

For example: use a Net8 service name, such as orcl.pjlee-pc, which connects to the orcl database on the pjlee.us.oracle.com machine.

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 use the Edit Local Preferred Credentials dialog available from the File menu.

The checkbox is not selected by default.

Editing Local Preferred Credentials in DBA Studio Standalone Mode

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

Note: The passwords are encrypted in the local file to prevent the file from being used on other machines.

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

DBA Studio stores a list of databases that are displayed in the DBA Studio navigator tree. If preferred credentials are specified for any of these databases, the username, encrypted password, and role are added to a local file.

DBA Studio maintains a local record of login credentials separately from the Oracle Management Server.

Note: If you cannot edit the local preferred credentials, check to see if you are in DBA Studio standalone mode.

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

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

2. In the Edit Local Preferred Credentials dialog, select the service name of the database and enter or update the preferences for connection 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: Confirm the password.

   • Role: Select the role from the pull-down list. You need to login with the SYSDBA or SYSOPER role to start up or shut down a database.

3. 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.

Setting Up DBA Studio in OMS Mode

To run DBA Studio in OMS mode, you must already have a repository and a Management Server set up and Intelligent Agents started on the nodes where your distributed services reside.

To set up DBA Studio in OMS mode, you must perform the following tasks:

• set up DBA Studio to connect to a Management Server

• start DBA Studio

• connect to the database

Setting Up DBA Studio to Connect to a Management Server

To set up DBA Studio to connect to an Oracle Management Server, follow the instructions below:

1. Ensure that the Oracle Intelligent Agents are started on the nodes you want to manage. Refer to Chapter 5, "Starting the Intelligent Agent" for information on starting your Intelligent Agents.

2. Ensure that the Oracle Management Server is started. Refer to Chapter 2, "Creating a Release 2.1 Repository" for detailed information on setting up a repository and Management Server and Chapter 3, "Controlling the Management Server" for detailed information about starting the Management Server.

3. Start the Console. Refer to Chapter 6, "Setting Up the Console" for information on starting the Console.

   Use the Discovery Wizard to discover the nodes where the desired databases reside. Refer to Chapter 6, "Setting Up the Console" for information on discovering nodes. DBA Studio will then have access to these discovered databases.

Note: If you want to add databases to the navigator tree for DBA Studio connected to an Oracle Management Server, you must use the Discovery Wizard from the Oracle Enterprise Manager Console. The navigator tree is populated from the repository and cannot be modified using DBA Studio.

4. Exit the Oracle Enterprise Manager Console.

Starting DBA Studio OMS Mode

1. Start DBA Studio.
   • On Windows NT:

     You can start DBA Studio from the Windows Start Menu->Programs->Oracle-<Oracle_Home_Name>-> DBA Management Pack->DBA Studio.

     You can also start DBA Studio from the command line using the command:

     oemapp dbastudio
     
     

   • On UNIX:

     You can start DBA Studio from the command line using the command:

     oemapp dbastudio
     
     

2. When the login dialog appears, choose Login to the Oracle Management Server.

3. Enter the credentials for the super administrator account:

   Administrator: sysman or the user the super administrator has created for you

   Password: oem_temp or the new password if you have changed it

   Management Server: the name of the node where the Oracle Management Server is running

4. Press the OK button. DBA Studio appears. The navigator tree is populated with the databases discovered through the Oracle Enterprise Manager Console.

Connecting to a Database in DBA Studio OMS Mode

There are four ways to connect to a database for DBA Studio:

• Click the plus symbol next to the DBA Studio navigator tree container

• Double-click the database icon in the DBA Studio navigator tree

• Select the Connect item from the File menu.

• Click the Connect icon from the toolbar.

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.

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

Username

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

For example: system

Password

Your Oracle password for the database to which you are connecting.

For example: manager

Service Name

Network service name for the database to which you are connecting.

For example: use a Net8 service name, such as orcl.pjlee-pc, which connects to the orcl database on the pjlee.us.oracle.com machine.

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 Preferred Credentials

Saving preferred credentials is an option which enables you to store login information in the repository, 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.

The checkbox is not selected by default.

Other DBA Studio Procedures

This section discusses the topics listed below:

• Accessing the Quick Tour in DBA Studio

• Connecting to the Database As a Different User

• Viewing Which Role You Are Connected As In DBA Studio

• Removing a Database from Tree in DBA Studio Standalone Mode

• Removing a Database from the Navigator in OMS Mode

• Adding Databases to the Navigator Tree For DBA Studio OMS Mode

• Changing from OMS Mode to Standalone Mode

• Changing from Standalone Mode to OMS Mode

Accessing the Quick Tour in DBA Studio

To access the Quick Tour in DBA Studio, you must first highlight a database or any of the nodes and click the Quick Tour button in the right-hand window.

Connecting to the Database As a Different User

In DBA Studio you do not have to disconnect in order to reconnect 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 File menu.

• Click the Connect icon from the toolbar.

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

You will automatically be disconnected and reconnected.

Viewing Which Role You Are Connected As In DBA Studio

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

Next to the database name, you can see the username and role you are connected as if you have connected with the SYSDBA role. For example, sys AS SYSDBA.

Removing a Database from Tree in DBA Studio Standalone Mode

To remove a database from the DBA Studio navigator tree, follow the steps below:

1. Highlight the database you want to remove.

2. From the File 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.

Note: Removing the database removes the entry from the DBA Studio Navigator tree. It does not remove the entry from the tnsnames.ora file or physically remove the database. If required, you have the option of adding the database to the navigator tree again.

Note: You can only remove databases from the navigator tree if you are connected to DBA Studio in standalone mode.

Removing a Database from the Navigator in OMS Mode

To remove a database from the navigator tree for DBA Studio connected to an Oracle Management Server, you must remove the database from the Oracle Enterprise Manager Console.

1. Start the Oracle Enterprise Manager Console.

2. Highlight the node where the database you want to remove resides.

3. Select the Remove Database item from the Navigator menu.

4. Exit the Oracle Enterprise Manager Console.

5. In DBA Studio, choose the Refresh item from the View menu. The node where the desired databases reside should disappear in the navigator tree.

Adding Databases to the Navigator Tree For DBA Studio OMS Mode

If you want to add databases to the navigator tree for DBA Studio connected to an Oracle Management Server, you must use the Discovery Wizard from the Oracle Enterprise Manager Console.

Note: Do not stop the Oracle Management Server or the Oracle Intelligent Agent.

1. Start the Oracle Enterprise Manager Console.

2. Choose the Discover Nodes item from the Navigator menu to launch the Discovery Wizard. For more information about service discovery, refer to the Oracle Enterprise Manager Administrator's Guide.

3. Specify the nodes where the desired databases reside and discover them. DBA Studio will have access to these databases.

4. Exit the Oracle Enterprise Manager Console.

5. In DBA Studio, choose the Refresh item from the View menu. The nodes where the desired databases reside should appear in the navigator tree.

Changing from OMS Mode to Standalone Mode

When DBA Studio is connected to an Oracle Management Server, the DBA Studio navigator tree is populated with the discovered databases from the Enterprise Manager Console.

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 Update tnsnames.ora File dialog from the File menu to select which services to copy to the local tnsnames.ora file.

2. If you want to save the preferred credentials to a local file, select the "Save Preferred Credentials Locally" checkbox in the Update tnsnames.ora File dialog.

Note: The passwords are encrypted in the local file to prevent the file from being used on other machines.

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

1. Start DBA Studio connected directly to databases.

2. From the File menu, select the Add Database To Tree item.

3. In the Add Databases to Tree dialog, select the net service names to add from the local tnsnames.ora file.

Changing from Standalone Mode to OMS Mode

If you have been using DBA Studio in standalone mode, 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 DBA Studio through a web browser; or perform backup and data management tasks. These tasks require you to run DBA Studio connected to an Oracle Management Server.

If you now decide to run DBA Studio 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 DBA Studio in standalone mode, you will need to discover the services from the Oracle Enterprise Manager Console if the databases are not already available from DBA Studio connected to the Oracle Management Server. For more information about service discovery, refer to the Oracle Enterprise Manager Administrator's Guide.

Note: To switch modes from DBA Studio in standalone mode to OMS mode, you need to close and restart DBA Studio.