Oracle Enterprise Manager Administrator's Guide

Library

Product

Contents

Index

Managing Instances and Sessions

Starting Instance Manager
Instance Manager Menus
Database Folder
Initialization Parameters Folder
Stored Configurations
Sessions Folder
In-Doubt Transactions Folder

This chapter describes how to use Instance Manager to manage instances and sessions. With Instance Manager, you can start up and shut down a database, view and edit the values of initialization parameters, resolve in-doubt transactions, and manage users' sessions. This chapter assumes that you have read Chapter 7, Overview of the Database Tools and are familiar with the interface elements of the database tools.

This chapter contains information on the following topics:

Starting Instance Manager

To start the Instance Manager, click on the Instance icon in the Launch Palette or choose Instance from the Launch menu.

If you have already connected to a database, the Instance window displays.
If a valid database connection has not been made, the Login Information dialog box displays. See Connecting to an Instance on page 1-17.

After the Instance Manager has successfully connected to a database, the Initialization parameters, Stored Configurations, In-Doubt Transactions, and Sessions folders display in a navigator on the left side of the Instance window. These folders are contained in the database folder which displays the name of the database the application is currently connected to.

The display on the right side of the window is determined by the objects selected on the left side of the screen. The right side may contain a multi-column scrolling list, property sheet, or dialog box.

An example of an Instance Manager window is shown in Figure 10-1.

Figure 10-1: The Instance Manager

For general information, see:

Instance Manager Menus

The Instance Manager includes the three standard menus, File, View, and Help, plus the Database, Sessions, Transactions, and Configuration menus. The options for each of these menus are described below. For information on the standard menus, see Application Menus on page 7-7.

Database Menu

The Database menu provides access to all options pertaining to Oracle instance startup and shutdown.

Startup to display the Startup property sheet that provides startup options and parameter file/configuration selection for instance startup.
Shutdown to display the Shutdown property sheet that provides standard options for instance shutdown.
Mount to mount an Oracle instance that has been started but is not currently mounted.
Open to open an Oracle instance that has been mounted but currently is not open.

Sessions Menu

The Sessions Menu provides access to all options that apply to database session management.

Disconnect to terminate any session that is selected from the Sessions folder in the navigator.
Restrict to restrict database access only to those users with the RESTRICTED SESSION system privilege.
Allow All to permit database access to all users.

Transactions Menu

The Transactions menu provides access to all options that apply to in-doubt transactions.

Force Commit to commit any transaction selected from the In-Doubt Transactions folder in the navigator.
Force Rollback to roll back a any transaction selected from the In-Doubt Transactions folder in the navigator.

Configuration Menu

The Configuration menu allows you to manage any configurations selected from the Stored Configurations folder in the navigator.

Remove to delete any configuration selected from the navigator.
Export to File to export any configuration selected from the navigator to an ASCII file.
Add parameter to add an initialization parameter to a stored configuration.
Remove parameter to delete a specific initialization parameter that is selected from the Initialization Parameters property sheet.

Attention:
If you alter an object contained in another object, all instances of the object in the database are changed.

Database Folder

The Database folder contains information about the current database: Initialization Parameters, Sessions, and In-doubt Transactions. The current database connection is displayed to the right of the folder in the navigator. When you start Instance Manager, the Database folder is automatically selected. This displays the Database property sheet.

Database Property Sheet

The Database property sheet displays when the Database folder is selected in the navigator. The property sheet consists of up to four pages:

Status
Startup
Shutdown
Archive (Displayed when logged in as SYSDBA)

Starting Up a Database

To start up an instance:

1.: Select the Database folder. The Database property sheet appears.
2.: Go to the Startup page and select the desired startup option.
3.: Click START UP.

Alternatively, you can access the Startup page of the Database property sheet by choosing Startup from the Database menu.

Attention:
Before starting up a release 7.1 or later database, you must connect as SYSDBA or SYSOPER. For information about connecting as SYSDBA or SYSOPER, see the Oracle7 Server Documentation Addendum. For release 7.0, you must be connected as INTERNAL before starting up the database. For information about starting up a database, see the Oracle7 Server Administrator's Guide.

Shutting Down a Database

To shut down a database:

1.: Select the Database folder. The Database property sheet appears.
2.: Go to the Shutdown page and select the desired shutdown option.
3.: Click Shutdown.

Alternatively, you can access the Shutdown page of the Database property sheet by choosing Shutdown from the Database menu.

If you are shutting down a remote database for the first time, make sure you have a local copy of the INIT.ORA file before attempting to restart the database.

Other applications create separate connections when you start them. When performing a shutdown in normal mode, remember to close these database connections, or the shutdown will not complete.

Attention:
Before shutting down a release 7.1 or later database, you must connect as SYSDBA or SYSOPER. For information about connecting as SYSDBA or SYSOPER, see the Oracle7 Server Documentation Addendum. For release 7.0, you must be connected as INTERNAL before shutting down the database. For information about shutting down a database, see the Oracle7 Server Administrator's Guide.

Mounting or Opening a Database

If you have previously started an instance without mounting the database, you can mount the database by choosing Mount from the Database menu. The Mount menu command mounts the database in exclusive mode, allowing the database to be mounted by only one instance at a time.

If you have previously mounted a database, you can open the database by choosing Open from the Database menu. The database is opened and is accessible to all users.

Initialization Parameters Folder

Initialization parameters specify the operational characteristics of a database. Instance Manager allows you view and edit these parameters. When you select the Initialization Parameters icon in the navigator, the Initialization Parameter property sheets appear.

Initialization Parameters Property Sheet

The Initialization Parameters property sheets consist of two basic and two advanced pages each with a multi-column scrolling list containing information about the parameters defined in the initialization parameter file used to start up your instance.

You can sort the Initialization list on each of the columns by clicking on the column heading. You can edit the values of parameters that can be updated.

Attention:
In order to start up or shut down a remote database, the INIT.ORA file must reside on both the local (Console) and remote (remote database) systems. The INIT.ORA file on both machines must be identical.

Basic Tuning

The Basic Tuning property sheet contains all initialization parameters that are considered essential for basic database operation.

Property sheet columns are defined as follows:

Parameter Name
Name of the initialization parameter.

Running Value
Current value of the initialization parameter while the database is running. Running values can only be changed if the parameter is dynamic.

New Value
Parameter value that will be written out to the INIT.ORA file upon database instance startup.

Instance Specific

The Instance Specific property sheet contains initialization parameters that pertain to a specific Oracle instance. Normally, these parameters will differ from one database to another.

Property sheet columns are defined as follows:

Parameter Name
Name of the initialization parameter.

Running Value
Current value of the initialization parameter while the database is running. Running values can only be changed if the parameter is dynamic.

New Value
Parameter value that will be written out to the INIT.ORA file upon database instance startup.

Advanced Tuning

The Advance Tuning property sheet, which appears when Instance Manager is run in Advanced UI mode, lists initialization parameters that normally fall beyond the realm of day-to-day database administration. Normally, these parameters are used for performance monitoring, or system tuning.

Property sheet columns are defined as follows:

Parameter Name
Name of the initialization parameter.

Running Value
Current value of the initialization parameter while the database is running. Running values can only be changed if the parameter is dynamic.

New Value
Parameter value that will be written out to the INIT.ORA file upon database instance startup.

See your Oracle Server documentation for database tuning information.

Derived

Property sheet columns are defined as follows:

Parameter Name
Name of the initialization parameter.

Running Value
Current value of the initialization parameter while the database is running. Running values can only be changed if the parameter is dynamic.

New Value
Parameter value that will be written out to the INIT.ORA file upon database instance startup.

See your Oracle Server documentation for database tuning information.

Editing Initialization Parameters

To edit any initialization parameter:

1.: Double-click on a specific parameter in any of initialization parameter list. The Edit Initialization Parameter dialog box appears with the Name and Current Value specified.
2.: Enter a value in the New Value text entry field.
3.: Click OK. The dialog box closes and the new value appears in the New Value column of the multi-column list.
4.: Click Apply from the Initialization Parameter property sheet to set the changes.

Applying non-dynamic initialization parameter changes requires that the database first be shut down. Regardless of whether you choose to shut down the database, Instance Manager asks if you wish to save the current set of parameters as a configuration file. See Stored Configurations on page 10-12 for more information.

Edit Initialization Parameter dialog box

The Edit Initialization Parameter dialog box consists of the following:

Name
Name of the selected parameter.

Current Value
Current parameter value. This field is only editable if the parameter is dynamic (modifiable while the database is running).

New Value
New parameter value upon restart of the database.

Resetting Edits

You can cancel any changes you have made to the parameter values with the Reset command button. Reset only cancels changes you made since the last Apply.

Applying Edits

You can save edits you make to parameter values by using the Apply command button. Any changes you make appear in the New Value column of the initialization parameter list except where parameters are dynamic. Whenever you apply an edit, the following actions occur:

If you have made changes to parameters that can be dynamically updated, the changes take effect when you click the Apply button.
If you have made changes to parameters that cannot be dynamically updated, the changes take effect after you have saved the changes and restarted the database.

Stored Configurations

Stored configurations allow you to create multiple database startup configurations without the need to track files initialization parameter files (INIT.ORA). Stored configurations exist in the registry and not as external files.

Stored Configuration Folder

Clicking on the Stored Configurations folder in the navigator displays the stored configuration multi-column list. This list consists of the following columns:

Configuration Name
User-specified name for the stored configuration.

Comments
User-specified description of the new stored configuration.

Creating a Stored Configuration

To create a stored configuration:

1.: Click Save from one of the initialization parameter property sheets (Basic Tuning, Instance Specific, Advanced Tuning, or Derived). The Save Configuration property sheet appears.
2.: Enter a configuration name.
3.: Enter any comments you wish to appear in the Comments column of the Stored Parameters mulit-column list.

Stored Configuration Property Sheet

Once a stored configuration is created, it appears in the navigator within the Stored Configurations folder. Selecting an individual stored configuration displays an initialization parameter property sheet containing a single page listing all parameters of the stored configuration. See Initialization Parameters Property Sheet on page 10-8. for explanatory information.

Editing a Stored Configuration

To edit a stored configuration:

Select an existing stored configuration from the Stored Configuration folder in the navigator. A single property sheet containing a list of initialization parameters appears. The parameters for stored configurations, are not categorized into Basic Tuning, Instance Specific, Advance Tuning, and Derived.

2.

Double-click on the desired initialization parameter. The Edit Initialization Parameter dialog box appears with the current value already entered.

3.

Enter a new value and click OK. The new value appears in the New Value column of the property sheet.

4.

When you are finished: To apply the edit, click Apply. Instance Manager prompts you if database shutdown is required.

To save the edit to a configuration file, click Save. You can either overwrite the selected stored parameter or specify that the changes be saved to a new stored configuration.

Deleting Parameters from a Stored Configuration

To delete an initialization parameter from a stored configuration:

1.: Select an existing stored configuration from the navigator.
2.: Select the desire parameter from the initialization parameter property sheet.
3.: Choose Remove Parameter from the Configuration menu. You can also execute the remove option from the context-sensitive menu.

Adding a Parameter to a Stored Configuration

To add an initialization parameter to a stored configuration:

1.: Select the desired stored configuration from the navigator.
2.: From the Configuration menu, choose Add Parameter. The Add Initialization Parameter dialog box appears.
3.: Enter the name of the new initialization parameter. Enter the startup value for the initialization parameter.
4.: Click OK.

Note: For a full list of initialization parameters and permissible values, see the Oracle 7 Server Reference Manual.

Add Initialization Parameter Dialog Box

The Add Initialization Parameter dilog box consists of the following:

Name
Initialization parameter name. See your Oracle Server documentation for a complete list of initializtion parameters.

Value
Valid initialization parameter value.

Creating a File from a Stored Configuration

Stored configurations are stored in the Windows NT registry. Hence, configurations created on a specific Windows server are only available on that machine. If you wish to make a configuration available to other machines, Instance Manager allows you to export stored configurations to an ASCII file.

To create a stored configuration file:

1.: Select a stored configuration from the navigator.
2.: Choose Export to File from the Configuration menu. You can also call up this option from the context-sensitive menu from the stored configuration in the navigator. A standard file Save As dialog box appears.
3.: Specify the desired file information and click OK.

Deleting a Stored Configuration

To delete a stored configuration:

1.: Select the desired configuration from the navigator.
2.: Choose Remove from the Configuration menu. Instance Manager asks if you want to remove the stored configuration.
3.: Click Yes.

Sessions Folder

The Session list contains information about the users connected to the database. You can sort the Sessions list on each of the columns by clicking on the column heading.

Sessions Multi-column List

When you click on the Sessions folder in the navigator, the Sessions multi-column list displays. The list consists of the following columns:

Session ID
Session identifier

Status
Whether a session is ACTIVE or INACTIVE

Username
Oracle USERID associated with the session.

Schema Name
Schema name associated with the user.

OS User
Operating system user name.

Terminal
Operating system terminal name.

Machine Name
Operating system machine through which the user is connected.

Program
Executable running through the session.

Sessions Property Sheet

The Sessions property sheet consists of a single General page. Columns of the Session list are described below:

Session ID
Session identifier.

Serial #
Session serial number, used to uniquely identify a session. In combination with the SID, guarantees that session-level commands are applied to the correct session in the event that the session ends and another session begins with the same session identifier.

Status
Whether a user session is active or inactive.

Username
Oracle username associated with the session.

Schema Name
Schema name associated with the user.

Program
Program you are currently running.

OS Information
User: Operating system username.

Terminal: Operating system terminal name.

Machine: Operating system machine through which the user is connected.

Disconnecting a User's Session

To disconnect a user's session:

1.: Select the session to disconnect from the Sessions multi-column list.
2.: Choose Disconnect from the Session menu.

Attention:
When you disconnect a session, the session is not actually terminated until the user tries to execute a database operation.

Restricting or Allowing Sessions

To make the database accessible only to users with the RESTRICTED SESSION system privilege, choose Restrict from the Session menu. Only users with the RESTRICTED SESSION system privilege are allowed to connect. Users already connected are not affected.

To make the database accessible to all users, choose Allow All from the Database menu. All users with the CREATE SESSION system privilege are allowed to connect.

See Chapter 9, Controlling Database Security for more information regarding roles and privileges.

In-Doubt Transactions Folder

The In-Doubt Transactions folder contains information about distributed transactions that failed in the PREPARED state. You can sort the Transactions list on each of the columns by clicking on the column heading.

Additional Information: For information about distributed transactions, see the Oracle7 Server Concepts.

In-Doubt Transactions Multi-column List

The columns of the In-Doubt Transactions list are described below:

Global ID
Global identifier for the transaction.

Local ID
Identifier on the local database for the transaction.

State
The state of the transaction: collecting, prepared, committed, heuristic commit, or heuristic abort.

Advice
Suggested action: C (Commit), R (Rollback), or null (no advice).

Commit Comment
Comment given with the COMMENT clause of the COMMIT WORK command.

In-doubt Transactions Property Sheet

The In-Doubt Transactions property sheet displays information about distributed transactions in which a commit was interrupted by a system, network, or any failure resulting from external factors.

Local ID
Name of the node that references data on other nodes to complete its part in the distributed transaction.

Global ID
Name of the node where the distributed transaction originates. The database application issuing the transaction is directly connected to this node.

State
State of the in-doubt transaction: collecting, prepared, committed, forced commit, forced rollback.

Advice
Suggested resolution: C for commit, R for rollback, null for states not requiring immediate action.

Date/Time Information
Failure Time: Date and time of transaction failure.

Last Automatic Retry: Last attempt by the RECO (recover) background process to resolve the transaction discrepancy.

Last Manual Force: Date and time of the last forced rollback or commit.

Commit Comment: Optional text entry field. Contents of this field are displayed in the

Forcing a Commit or Rollback

To commit an in-doubt transaction:

1.: Select the In-Doubt Transactions folder in the navigator. This displays the In-Doubt Transactions multi-column list.
2.: Select the transaction to be committed from the In-Doubt Transactions multi-column list.
3.: Choose Force Commit from the Transaction menu.

To roll back an in-doubt transaction:

1.: Select the In-Doubt Transactions folder in the navigator to display the In-Doubt Transactions multi-column list.
2.: Select the transaction to be rolled back from the multi-column list
3.: Choose Force Rollback from the Transaction menu.

Attention:
You cannot roll back an in-doubt transaction to a savepoint.

Prev Next

Library

Product

Contents

Index