Copyright: Copyright (C) Oracle Corporation 1997, all rights reserved


Oracle Enterprise Manager: Introduction

Oracle Enterprise Manager (OEMGR) consists of multiple components that integrate into a powerful graphical user interface (GUI). OEMGR features allow you to quickly and easily administer databases and networks. The components include:

•	Console and related services, which provide the framework for OEMGR components that manage and monitor the services in the network environment.

•	Database Tools and Utilities, which provide easy-to-use tools for administering databases in the network.

•	Administrator Toolbar, which provides quick access to the Oracle Enterprise Manager database administration tools.

•	Intelligent Agents, which communicate with the Console to manage and monitor services, such as databases, on nodes throughout the network.

•	Value-Added Products, which include additional Oracle products, such as the Performance Pack, that can be purchased to help manage your system.

•	Online Help, which provides context-sensitive help for components of Oracle Enterprise Manager.

Note: Select the Help_Topics button to view a list of topics and index entries.

Attention: See the Oracle Enterprise Manager Messages Manual for information about error messages for Oracle Enterprise Manager and its components.

  Related Topics

  How to ...


Enterprise Manager Features

Oracle Enterprise Manager combines a graphical console, agents, common services, and tools to provide an integrated, comprehensive systems management platform for managing Oracle products. From Enterprise Manager's Console, you can:

•	Administer, diagnose, and tune multiple databases.

•	Distribute software to multiple servers and clients.

•	Schedule jobs on multiple nodes at varying time intervals.

•	Monitor events on objects throughout the network.

•	Customize your display using multiple graphic maps and groups of network objects, such as nodes and databases.

•	Integrate participating Oracle or third-party tools.

Attention: See the Oracle database compatibility matrix in the Oracle Enterprise Manager Readme for information on the specific Oracle7 server releases that are supported by Oracle Enterprise Manager and its components.

  Related Topics


Repository

The repository is a set of tables in an Oracle database. Each administrator is associated with a specific repository in a database. Any information related to the tasks performed by the administrator is stored in that repository. For example, the repository contains information about the jobs you submitted and the events being monitored for you. The repository also stores information about maps and groups.

The repository tables can be installed in any database accessible to the Console. An administrator can log on to the repository database from any machine. Also, the repositories for the administrators do not have to be in the same database. For information on setting up a repository, see the Oracle Enterprise Manager Installation Guide.

Note: Only one repository should be set up for each username. If you create identical users with repositories in different databases, this can cause problems with agent notifications. The intelligent agents use the unique username when tracking jobs and events. The username is appended to the Console location when creating a return address for notifications.

When you log in to the Console, you must enter the connect information for the database that contains your repository. The Console looks up the repository associated with your username. See notes on Connecting to a Repository.

Note: You should not log on to the Console repository multiple times with the same username. A warning displays if you attempt this. You should only ignore the warning if the previous Console session was aborted or a machine was disconnected. When a username is logged in multiple times, agent notifications are sent to most recent login.

The information in the repository can be updated by third-party applications that integrate into the Enterprise Manager Console. Refer to the "Repository Control Interface" in the Oracle Enterprise Manager Application Developer's Guide.

  Related Topics


Discovery Cache

The discovery cache is an efficient in-memory list of information about services and nodes. While you are logged into the Console, the discovery cache stores the current view of the network, including the user-defined groups and the states of nodes and services. When the you log out of the Console, the contents of the discovery cache are stored in the repository.

The next time you start the Console, the discovery cache is loaded with information from the repository and updated with any new information that has been discovered. The new information can include a new service or object discovered by the daemon, or a state that changed since last login.

The information in the discovery cache can be accessed by third-party applications that integrate into the Enterprise Manager Console. Refer to the "Discovery Cache Interface" in the Oracle Enterprise Manager Application Developer's Guide.

  Related Topics


Server Manager Line Mode

For the times when a command line interface is necessary or desirable, Oracle Server Manager provides a conversational line mode. In line mode, you can explicitly execute database administration (DBA) commands on a command line.

You may want to use Server Manager in line mode when a graphical device is unavailable, such as when dialing-in from a non-GUI terminal, or when performing unattended operations, such as running nightly batch jobs or batch scripts that do not require user intervention.

For information about entering commands in line mode, see SQL Worksheet. For information on the DBA commands, see DBA Commands.

  Related Topics


Online Help

Enterprise Manager uses the Microsoft Windows online help system to provide you with help information for windows and dialog boxes in the Console and database tools. The Help system is context sensitive, but you can also search through help information to find a particular topic.

There are several ways of accessing the online Help system. In a main window, such as the Console window, you can access the Help system by pressing F1 or choosing Contents from the Help menu. In a dialog box, click the Help button or press F1 to access the online Help system. For information on the Help menu, see Help Menu.

When using this online help, note the following:

•	To view a complete list of the help topics, select the Help_Topics button in the menu bar at the top of a help window. Choose the Contents tab in the Help Topics window.

•	To view topics in sequential order, click on the >> button in the menu bar. Click on the << button to return to the preceding topic.

  Related Topics


Enterprise Manager Documentation

Oracle Enterprise Manager Documentation in HTML format is provided on the OEMGR installation CD. If you install the documentation, you can view the following manuals with a web browser:

•	Oracle Enterprise Manager Installation Guide

•	Oracle Enterprise Manager Concepts Guide

•	Oracle Enterprise Manager Administrator's Guide

•	Oracle Enterprise Manager Oracle Expert User's Guide

•	Oracle Enterprise Manager Oracle Trace User's Guide

•	Oracle Enterprise Manager Performance Monitoring User's Guide

•	Oracle Enterprise Manager Messages Manual

•	Oracle Enterprise Manager Application Developer’s Guide

Printed copies of these guides can be ordered.

  Related Topics


Value Added Products

Oracle produces a number of additional administration utilities that can be purchased separately and integrated into the Enterprise Manager Console.

Performance Pack Monitoring and Diagnostic Utilities

Oracle provides easy-to-use tools for monitoring and diagnosing databases. These utilities include:

•	Oracle Lock Manager

•	Oracle Performance Monitoring

•	Oracle Tablespace Manager

•	Oracle TopSessions

•	Oracle Expert

•	Oracle Trace

The utilities allow you to gather and inspect specific performance statistics that are useful for tuning your database. For information on monitoring and diagnostic tools, see the Oracle Performance Monitoring User's Guide, the Oracle Expert User's Guide, and the Oracle Trace User's Guide.

Note: You can view the online help for the monitoring and diagnosing tools if the products have been installed.

•	Oracle Performance Pack Online Help

•	Oracle Expert Online Help

•	Oracle Trace Online Help

  Related Topics


Property Sheets

A property sheet is a dialog box used to specify options when you are creating or altering a composite instance, such as a user or tablespace. A property sheet consists of one or more pages that are labeled with page tabs. By default, one page is open when the sheet is entered, but all pages show page tabs. To access another page, click its page tab.

When a composite instance is selected in the tree list on the left side of an application window, the Alter property sheet that is associated with the object is usually displayed on the right side of the window. The properties available for each sheet are specific to the group type.

Property sheets generally contain the following command buttons:

Action

Implements an action specified in the property sheet. Apply would save any changes made to an edit property sheet and Create would create a new the object specified by the Create property sheet.

Note: The action button saves all changes contained in the property sheet, not just those in the current page.

Revert

Cancels any changes made to the property sheet and resets the fields to previously saved values.

Show SQL

Opens or closes the SQL window to show or hide the SQL statements that are used to execute commands.

Help

Displays online Help about the property sheet.

  Related Topics


Dialog Boxes

Dialog boxes allow you to make selections, enter information, or confirm actions. You exit a dialog box by clicking a button. In many cases, you first enter field values, or choose options from pop-up menus or buttons, before you exit. The boxes generally contain one or more of the following command buttons.

OK

Executes the action button that was specified and closes the dialog box. The name of this button may vary.

Cancel

Cancels any changes made and closes the dialog box.

Apply

Implements any changes made to the dialog box.

SQL

Opens or closes the SQL window to show or hide the SQL statements that are used to execute commands.

Help

Displays online Help about the dialog box.

  Related Topics


File Open Dialog Box

The following options allow you to specify which file to open:

File Name

Type or select the filename you want to open. This box lists files with the extension you select in the List Files of Type box.

List Files of Type

Select the type of file you want to open.

Drives

Select the drive where the file that you want to open is located.

Directories

Select the directory where the file that you want to open is located.

Network...

Choose this button to connect to a network location, assigning it a new drive letter.

  Related Topics


File Save As Dialog Box

The following options allow you to specify the name and location of the file that you want to save:

File Name

Type a new filename to save the file with a different name. A filename can contain up to eight characters and an extension of three characters. If an extension is specified in the List Files of Type box, it will be automatically added to the filename.

Drives

Select the drive where you want to store the file.

Directories

Select the directory where you want to store the file.

Network...

Choose this button to connect to a network location, assigning it a new drive letter.

  Related Topics


Print command

Use this command to print a document. This command presents a Print dialog box, where you may specify the range of pages to be printed, the number of copies, the destination printer, and other printer setup options.

  Related Topics


Print dialog box

The following options allow you to specify how the document should be printed:

Printer

This is the active printer and printer connection. Choose the Setup option to change the printer and printer connection.

Setup

Displays a Print Setup dialog box, so you can select a printer and printer connection.

Print Range

Specify the pages you want to print:

•	All: Prints the entire document.

•	Selection: Prints the currently selected text.

•	Pages: Prints the range of pages you specify in the From and To boxes.

Copies

Specify the number of copies you want to print for the above page range.

Collate Copies

Prints copies in page number order, instead of separated multiple copies of each page.

Select the quality of the printing. Generally, lower quality printing takes less time to produce.

  Related Topics


Print Progress Dialog

The Printing dialog box is shown during the time that Enterprise Manager is sending output to the printer.  The page number indicates the progress of the printing.

To abort printing, choose Cancel.

  Related Topics


Print Preview command

Use this command to display the active document as it would appear when printed. When you choose this command, the main window will be replaced with a print preview window in which one or two pages will be displayed in their printed format. The print preview toolbar offers you options to view either one or two pages at a time; move back and forth through the document; zoom in and out of pages; and initiate a print job.

  Related Topics


Print Preview toolbar

The print preview toolbar offers you the following options:

Print

Bring up the print dialog box, to start a print job.

Next Page

Preview the next printed page.

Prev Page

Preview the previous printed page.

One Page/Two Page

Preview one or two printed pages at a time.

Zoom In

Take a closer look at the printed page.

Zoom Out

Take a larger look at the printed page.

Close

Return from print preview to the editing window.

  Related Topics


Print Setup command

Use this command to select a printer and a printer connection. This command presents a Print Setup dialog box, where you specify the printer and its connection.

  Related Topics


Print Setup dialog box

The following options allow you to select the destination printer and its connection.

Printer

Select the printer you want to use. Choose the Default Printer; or choose the Specific Printer option and select one of the current installed printers shown in the box. You install printers and configure ports using the Windows Control Panel.

Orientation

Choose Portrait or Landscape.

Paper Size

Select the size of paper that the document is to be printed on.

Paper Source

Some printers offer multiple trays for different paper sources. Specify the tray here.

Options

Displays a dialog box where you can make additional choices about printing, specific to the type of printer you have selected.

Network...

Choose this button to connect to a network location, assigning it a new drive letter.

  Related Topics


Exit command

Use this command to end your Enterprise Manager session. You can also use the Close command on the application Control menu. Enterprise Manager prompts you to save documents with unsaved changes.

  Related Topics


Undo/Can't Undo command

Use this command to reverse the last editing action, if possible. The name of the command changes, depending on what the last action was. The Undo command changes to Can't Undo on the menu if you cannot reverse your last action.

  Related Topics


Cut command

Use this command to remove the currently selected data from the document and put it on the clipboard. This command is unavailable if there is no data currently selected. Cutting data to the clipboard replaces the contents previously stored there.

  Related Topics


Copy command

Use this command to copy selected data onto the clipboard. This command is unavailable if there is no data currently selected. Copying data to the clipboard replaces the contents previously stored there.

  Related Topics


Paste command

Use this command to insert a copy of the clipboard contents at the insertion point. This command is unavailable if the clipboard is empty.

  Related Topics


Clear All

Use this command to clear all the text from the window pane.

  Related Topics


Select All

Use this command to select all the text in the window pane.

  Related Topics


Toolbar command

Use this command to display and hide the Toolbar, which includes buttons for some of the most common commands in Enterprise Manager. A check mark appears next to the menu item when the Toolbar is displayed.

See Toolbar for help on using the toolbar.

  Related Topics


Toolbar

The toolbar is displayed across the top of the application window, below the menu bar. The toolbar provides quick mouse access to many tools used in Enterprise Manager.

To hide or display the Toolbar, choose Toolbar from the View menu.

  Related Topics


Status Bar command

Use this command to display and hide the Status Bar, which describes the action to be executed by the selected menu item or depressed toolbar button, and keyboard latch state. A check mark appears next to the menu item when the Status Bar is displayed.

See Status Bar for help on using the status bar.

  Related Topics


Status Bar

The status bar is displayed at the bottom of the application window. To display or hide the status bar, use the Status Bar command in the View menu.

The left area of the status bar describes actions of menu items as you use the arrow keys to navigate through menus.  This area similarly shows messages that describe the actions of toolbar buttons as you depress them, before releasing them. If after viewing the description of the toolbar button command you wish not to execute the command, then release the mouse button while the pointer is off the toolbar button.

The right areas of the status bar indicate which of the following keys are latched down:

CAP	The Caps Lock key is latched down.

NUM	The Num Lock key is latched down.

SCRL	The Scroll Lock key is latched down.

  Related Topics


Search for Help On

Use this command to display the index entries for the online help.

  Related Topics


Using Help

Use this command for instructions about using Windows Help.

  Related Topics


About ...

Use this command to display the copyright notice and version number of the Oracle Enterprise Manager Console or component.

  Related Topics


Using Enterprise Manager

To run Oracle Enterprise Manager, you must install Enterprise Manager on a computer running Windows NT or Windows 95. Before you can use Enterprise Manager, there must be a repository available in a database on any node accessible to the Enterprise Manager Console. The version of the repository must be compatible with the OEMGR Console. To use the Job and Event systems, an Intelligent Agent must be running on the node that you plan to run jobs or monitor events.

Additional information is included in:

•	Privileged Operations

•	Administration of a Remote Database

•	Starting Enterprise Manager

•	Launching Tools

For instructions on installing Oracle Enterprise Manager, see the Oracle Enterprise Manager Installation Guide.

  Related Topics


Privileged Operations

To perform an operation or task using Enterprise Manager, you must have the appropriate privileges. To fully utilize Oracle Enterprise Manager, you should make sure you have DBA system privileges when you connect to the Console.

For example, to create a tablespace using Enterprise Manager, you must have the CREATE TABLESPACE system privilege. Because many of Enterprise Manager's windows include information selected from data dictionary tables, you need the SELECT ANY TABLE system privilege. These system privilege are part of the SYSDBA/SYSOPER role.

Enterprise Manager does not enable any additional roles, so any privileges you need must be part of your default roles and privileges. For information about privileges and roles, refer to the Oracle7 Server Concepts and Oracle7 Server Administrator's Guide.

  Related Topics


Administration of a Remote Database

Before submitting a database administration task, such as starting up or shutting down a database, through the Oracle Enterprise Manager Job system, you need to set up the database password file on the node where the database and agent are located. This can be done on a Unix platform using the password file creation utility orapwd. Enter the following at the Unix operating system prompt:

orapwd file=$ORACLE_HOME/dbs/orapw$ORACLE_SID password=manager

Additional Information: Refer to the operating system-specific documentation for your Oracle database for the exact name of the password file creation utility for your system.

Also, you need to add the following to the init.ora database initialization file:

REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE

Note: When you log onto Oracle Enterprise Manager, you need to connect as SYSDBA (or SYSOPER) to have the privileges to startup and shutdown databases.

  Related Topics


Starting Enterprise Manager

To start Oracle Enterprise Manager, double-click on the Enterprise Manager icon in the Oracle program group.

Note: Only one instance of the Oracle Enterprise Manager Console can be run on a machine. However, you can run multiple instances of the DBA tools.

Connecting to a Repository

When you start Enterprise Manager, the copyright window displays, then the Login Information dialog box appears. Use the login box to connect to the Oracle database instance where your repository for Enterprise Manager is stored. For information on connecting to an Oracle database, see Entering Login Information.

Note: The versions of the Oracle Enterprise Manager and the OEMGR repository must be compatible. For example, you cannot use a version 1.2 repository with a version 1.3 OEMGR Console. If the existing OEMGR repository version is older than the Oracle Enterprise Manager Console version, the existing repository will be upgraded automatically when you log into the repository. A dialog box will display that informs you of the upgrade. If the Oracle Enterprise Manager Console version is older than the OEMGR repository version, you will need to install a more recent, compatible version of OEMGR.

Note: You should not log on to the Oracle Enterprise Manager repository multiple times with the same username. A warning displays if you attempt this and you are using the same repository. You should only ignore the warning if the previous Console session was aborted or a machine was disconnected. The intelligent agents use the unique username when tracking jobs and events. The username is appended to the Console location when creating a return address for notifications. When a username is logged in multiple times, agent notifications are sent to most recent login.

Warning: Oracle Enterprise Manager requires unique usernames across all repositories whether or not the repositories are in different databases. Identical users cause problems with agent notifications.

  Related Topics


Launching Tools

You can launch the Enterprise Manager tools as separate applications, through the Console, or with the Administrator Toolbar. To launch a tool separately, double-click on the application icon in the Oracle program group. Enter the connect information in the Login Information dialog box.

For information on connecting to an Oracle database, see Entering Login Information.

To launch a tool through the Console, you can:

•	Select the database you want to administer in the Navigator tree or in the Map window, then choose the application in the Console Tools menu or in the launch palette.

•	Select the database you want to administer in the Navigator tree, then choose the application from the Related Tools menu of the context-sensitive menu.

•	Choose the application in the Console Tools menu or in the launch palette, then enter connect information in the Login Information dialog box.

Note: When you select a database before launching a tool, you are connected to the database according to the preferred credentials that have been set up for the database or the credentials you used to log on to the Console. If connection to the database fails for any reason, the Login Information dialog box displays. See Preferred Credentials for more information.

Note: Some database administration tools will not run or have limited functionality when the Console is not running. See the online help for specific database administration tools.

  Related Topics


Oracle Administrator Toolbar

The Oracle Administrator Toolbar provides quick access to the Oracle Enterprise Manager Database Administration (DBA) Tools and Utilities without the Console.

When the Administrator Toolbar is first installed, it includes the Oracle Instance Manager, Oracle Schema Manager, Oracle Security Manager, Oracle Storage Manager, and Oracle SQL Worksheet DBA tools. To launch a tool, click on its icon or name depending on the format of the toolbar.

The toolbar can be configured to:

•	Display specific DBA tools

•	Customize the format of the toolbar

•	Be present on the desktop at all times

•	Connect to a default username, database name, and password

•	Provide access to programs from other vendors

See Administrator Toolbar Menu for menu options that allow you to customize the toolbar.

Note: Some database administration tools will not run or have limited functionality when the Console is not running. See the online help for the specific database administration tool.

Additional information:

Administrator Toolbar Customize: General Page

Administrator Toolbar Customize: Applications Page

Administrator Toolbar Customize: Databases Page

  Related Topics


Oracle Administrator Toolbar, menu
Oracle Administrator Toolbar Menu

The Administrator Toolbar menu displays when you click the right mouse button on the toolbar.

Customize

Displays the Toolbar Customize property sheet pages: General, Applications, and Databases.

Databases

Displays the list of database entered in the Toolbar Customize: Databases Page. This item is only active when you click the right mouse button on a tool set up as a database application in the Applications page.

Database Status

Displays the status of the default database specified in the Toolbar Customize: Databases Page.

Application Bar/Float Bar

Toggles the toolbar between the application and float styles. The format of these styles is set up in the General page.

Help

Accesses the online help system menu options. You can also press F1 to display help.

Exit

Exits the toolbar.

  Related Topics


Toolbar Customize: General Page
Administrator Toolbar Customize: General Page

This page allows you to determine the format and location of the Administrator Toolbar.

Floating Bar format:

Always on Top

Select this option if you want the toolbar to remain in the foreground.

Hide Title Bar

Select this option if you do not want the toolbar title to be shown.

Button Size

Select the toolbar icon size in the floating toolbar.

Application Bar format:

Top

Displays the application toolbar at the top of the screen.

Bottom

Displays the application toolbar at the bottom of the screen.

Left

Displays the application toolbar at the left of the screen.

Right

Displays the application toolbar at the right of the screen.

Auto Hide

Automatically hides the toolbar when the Customize property sheet or Database Status dialog box displays.

Always on Top

Select this option if you want the toolbar to remain in the foreground.

Select OK to save the options you have selected. The toolbar displays with the modified view options. Select Cancel to close the property sheet without saving any modifications.

  Related Topics


Toolbar Customize: Applications Page
Administrator Toolbar Customize: Applications Page

This page allows you to add, configure, and remove Database Administration (DBA) Tools and Utilities from the Administrator Toolbar.

Note: To select an application, click on the button just to the left of the listed application.

Name column

You can edit the application name that appears in the toolbar by editing the name field in the page.

Show? column

You can click in the column to toggle the field. Rather than delete applications from the page, you may choose to not show the icon in the toolbar.

DB App? column

You can click in the column to toggle the field. This field identifies an application as a database administration tool.

The Path column cannot be modified.

Add button

Starts the Create Application in Toolbar wizard.

•	On the first page of the wizard, select the Browse button to locate the executable name of the application with the Windows File Selection dialog. The applications are usually located in the <ORACLE_HOME>\BIN directory.

•	On the next page, enter the application name that you want to appear in the toolbar. Choose Yes if the application administers a database; otherwise choose No. If Yes selected, you can display the list of databases from the Databases page when you click the right mouse button on the application icon in the toolbar and select the Databases menu option. The application will attempt to connect to the selected database in the list.

Delete button

Removes the selected application in the page and removes the icon from the toolbar.

Move Up/Move Down buttons

Moves the selected application up or down in the page. This changes the location of the application icon in the toolbar.

Select OK to save any updates. The toolbar displays with the modifications. Select Cancel to close the property sheet without saving any modifications.

  Related Topics


Toolbar Customize: Databases Page
Administrator Toolbar Customize: Databases Page

With this page you can specify databases you want to administer, plus the credentials for accessing the databases. Databases entered here display in a list when you select Databases from the Toolbar menu.

Note: To select a service, click on the button just to the left of the listed service.

Service column

You can enter and edit the name of the service that you want to administer.

Default column

Click on this column to toggle the default status. When you select Database Status from the Toolbar menu, the status is displayed for the default database. If a database service is set as the default, the database tools attempt to connect to this database when started.

User/Password columns

Enter the username and password that you want to use when you connect to this service.

Connect As column

Choose the role that you want to use when connecting to the database. The available roles are NORMAL, SYSDBA, and SYSOPER.

Delete button

Removes the selected service in the page.

Move Up/Move Down buttons

Moves the selected service up or down in the page. This changes the location of the service in the list that displays when you select Databases from the Toolbar menu.

Select OK to save any updates. Select Cancel to close the property sheet without saving any modifications.

  Related Topics


Entering Login Information

The Login Information dialog box is used to connect to an Oracle database. You can display the Login Information connect dialog box by selecting a database in the Navigator window and choosing Connect from the Navigator menu. You can also select a database in the Navigator window with the right-mouse to display the login box.

When OEMGR is executed, the Login Information dialog box automatically displays for you to connect to the repository database. See notes on Connecting to a Repository.

If you launch a DBA tool and a database connection is not made, the Login Information dialog box displays for you to enter valid connect information. See Launching Tools.

The elements of the dialog box are described below:

Username

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

Password

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

Service Name

SQL*Net service name for the database to which you are connecting. You should use SQL*Net Version 2 service names, such as NY_FINANCE, when connecting. The connect strings for the service names must be set up correctly. Otherwise, the agents used by the Job and Event systems will not be able to locate the database. For information on configuration files, see the Oracle Enterprise Manager Installation Guide.

Connect As

Pop-up menu containing NORMAL, SYSOPER, and SYSDBA for Oracle7 release 7.1 or later. Only Normal is allowed for release 7.0. SYSOPER and SYSDBA roles allow you the maximum database administration privileges. You will need SYSDBA or SYSOPER privileges to run job tasks such as shutdown or startup on the database.For more information on SYSOPER and SYSDBA roles, see the Oracle7 Server Administrator's Guide.

Note: If you try to connect as SYSDBA and do not have SYSDBA privileges, an error message states that an invalid username/password was entered. The error message should state that invalid logon credentials were entered.

OK

Initiates connection.

Cancel

Exits dialog box without connecting.

Help

Displays help information.

See User Preferred Credentials for information on user preferred credentials when connecting to a database.

Multiple Connections

In Enterprise Manager you can have multiple database connections open simultaneously. For example, you can launch several database applications on different databases. The service name you specify when you connect becomes part of the title for each window associated with that connection.

Note: The number of connections you can have open simultaneously depends on the system and network you are using.

  Related Topics


Network Topology Generator: Input Dialog Box

The Oracle Network Topology Generator is used if you have an existing SQL*Net installation without the SQL*Net configuration tool, Network Manager 3.1. The Network Topology Generator generates or modifies the topology.ora file that is used with Intelligent Agent versions prior to 7.3.3 and OEMGR versions prior to 1.3 to populate the Console Navigator tree.

When the Network Topology Generator starts, the input file dialog box displays. Select one of the two filenames that can be read by the Network Topology Generator: tnsnames.ora and topology.ora.

With the Network Topology Generator, you can:

•	Input an existing tnsnames.ora file and generate a topology.ora file. The tnsnames.ora file must be correctly formatted; only SQL*Net Version 2 connect strings are accepted.

•	Edit an existing topology.ora file.

See the Service Name List Dialog Box.

Note: The topology.ora file creates the relationships between the services, such as databases, and the nodes that they reside on. The tnsnames.ora file identifies the names, but not the types, of the services in the network. When the Network Topology Generator generates a topology.ora file from a tnsnames.ora file, it defaults all services to databases and attempts to create the node name using the network address that is read. You may need to edit entries that have been generated to create the appropriate agent and listener entries.

  Related Topics


Network Topology Generator: Service Name List Dialog Box

Multi-column List

Service Name

Name of the TNS connect descriptor.

Service Type

Type of network service. ORACLE_DATABASE is chosen by default.

Node Name

Name of the network node.

Listener Name

Name of the listener that is generated by the Network Topology Generator. The listener name is a composite name using the following format: LISTENER_node name.domain name

Preferred Instance

Name of the parallel server's preferred instance. The preferred instance is the node which the console tries to contact when it first connects to the parallel server. This is an attribute of the OPS_INSTANCE service type.

Parallel Server

Name of the parallel server to which the instance belongs. This is an attribute of the OPS_INSTANCE service type.

Buttons

Input File

The Input File text field displays the full path and filename of the tnsnames.ora or topology.ora file

Browse

Displays the standard Open File dialog box.

Create

Displays the Network Service Details Dialog Box with all text fields active.

Edit

Displays the Network Service Details Dialog Box with the Name field grayed out. All other fields are active. To edit an existing entry, select an entry from the Service Name multi-column list and click on the Edit button. The Network Service Details dialog box appears with all fields active except the Service Name. Enter the desired parameters and click OK.

Delete

Deletes a selected entry from the Service Name multi-column list.

To delete an existing entry, select an item from the Service Name multi-column list and click on the Delete button.

Merge OPS

Merges the contents of a specified parallel server topology file with the current contents of the list box. Entries in the specified parallel server topology file over write the existing entries in the list box if they have the same servicename.servicetype. When you select this button, you need to specify the parallel server topology file in the file dialog box that displays.

Write File

Displays the standard file Save As dialog box. Enter a filename, then click on the Write button to create a new topology.ora file.

Exit

Quits the Network Topology Generator.

Help

Displays online help.

  Related Topics


Network Topology Generator: Network Service Details Dialog Box

The Network Service Details dialog box allows you to create and edit entries in the topology.ora file. Enter the desired parameters and click OK. The dialog box contains:

Service

Name: Service name

Type: Service type (OPS_DATABASE, OPS_INSTANCE, ORACLE_AGENT, ORACLE_DATABASE, ORACLE_LISTENER, ORACLE_NAMESERVER, ORACLE_TRACE, RDB_DATABASE,)

Service Relationship

Node Name: Name of the network node.

Listener Name: Derived name of the following format:

LISTENER_node name.domain name

Preferred Instance: Name of the node which the Console initially tries to contact when connecting to the parallel server. This service relationship is valid only for the OPS_DATABASE service type.

Parallel Server: Name of the parallel server to which the instance belongs. This service relationship is valid only for the OPS_INSTANCE service type.

  Related Topics


Info

Oracle Enterprise Manager Online Help
Release: 1.3.5
Help File: vocus
Copyright © 1996, 1997 Oracle Corporation


Console: Overview

The Enterprise Manager Console is a graphical user interface that provides Menus, Toolbars, Launch palettes, Online Help, and the framework to allow access to Oracle tools, plus utilities available through other vendors.

The Console components and related services include:

•	Event Management

•	Job Scheduling

•	Map

•	Navigator

•	Oracle Parallel Server (OPS) Support

•	Communication Daemon

•	Discovery Cache

•	Repository

The format of the Console screen and the applications displayed are determined by the products purchased and user preferences.

  Related Topics


Console, menus
Console Menus

The Console menu bar provides access to the following menus:

•	File

•	View

•	Navigator

•	Map

•	Job

•	Event

•	Tools

•	Help

When using the Console menus, note that:

•	Some menus include other menus as well. For example, when you select the Show Map item from the Map menu, a menu containing a list of saved maps displays.

•	Menu options vary depending on the objects selected or the active window in the Console. The Tools menu items vary depending on the setup of your system.

•	When a menu item is dimmed, it is not currently available. Menu items that end with an ellipsis (...) indicate that you will be asked to enter more information to complete the command.

•	Context-sensitive menus can be displayed for objects in Console windows.

  Related Topics


File Menu

The File menu items allow you to manipulate maps, open or close database connections, and change login connections. The File menu is described below:

Preferences...

Displays the User Preferences property sheet that contains the user credentials for services accessed through the Console. See Preferred Credentials for more information.

Print Setup

Determines the print setup for the Oracle Enterprise Manager.

Exit

Exits Enterprise Manager.

  Related Topics


View Menu

The View menu allows you to determine whether toolbars, palettes, or windows are displayed or hidden.

Note: At least one window must be visible in the Console.

Show Navigator Pane

Hides or shows the Navigator window. The menu item is checked or unchecked.

Show Map Pane

Hides or shows the Map. The menu item is checked or unchecked.

Show Job Pane

Hides or shows the Job Scheduling window. The menu item is checked or unchecked.

Show Event Pane

Hides or shows the Event Management window. The menu item is checked or unchecked.

Launch Palettes Menu

Hides or Shows the the launch palettes, such as Applications and Performance Pack, that are set up for Enterprise Manager. You can choose to hide or show all the palettes. See Launch palettes and Tools menu for information on launching tools.

Toolbar

Hides or shows the Enterprise Manager toolbar.

Status Bar

Hides or shows the Status bar at the bottom of the Console.

Advanced Mode

Displays additional property sheets that allow you to access advanced features.

  Related Topics


Tools Menu

The Tools menu allows you to execute database applications and other utilities that have been installed on your system. The menu options in the Tools menu depend on your system configuration.

You can also execute the applications from a launch palette or the Administration Toolbar. See Launching Tools.

Applications

This menu option lists the database administration tools and utilities that you can execute from the Console. See Database Tools and Utilities.

Performance Pack

This menu option lists the optional Performance Pack applications that you can execute from the Console. See Value-Added Products.

Daemon Manager

The Daemon Manager executes the communication daemon monitoring program.

  Related Topics


Help Menu

From the Help menu, you can access the Enterprise Manager online Help system.

Contents

Displays the overview topic of the Oracle Enterprise Manager help system.

Search for Help On...

Displays the Help Topics window containing lists of topics, index entries, and keywords that you can locate in the help system.

Using Help

Displays information on using the Microsoft Windows help system.

About Oracle Enterprise Manager

Displays a dialog box containing version information about Oracle Enterprise Manager and its components.

  Related Topics


Toolbars

The Enterprise Manager provides toolbar options that allow you to:

•	Perform various menu options for the Event, Job, and Map components.

•	Hide or show the Navigator, Job, Event, or Map panes.

The toolbar icons represent the items in the menus. The toolbar options are enabled depending on the objects viewed or selected in a window. Move the mouse cursor over a toolbar icon to display the description of the icon's function in the status bar at the bottom of the Console.

The toolbar can be:

•	Moved to the top or bottom of the Console window, or can float as a separate window.

•	Displayed or hidden through the View menu.

  Related Topics


Launch Palettes

The launch palettes contain the applications that you can launch from the Enterprise Manager Console.

•	Each palette represents a portion of the Tools menu options. The palette is the same as the Tools menu except that the palette provides icons rather than text items to represent the applications.

•	The launch palette items vary depending on the applications that have been installed on your system.

•	The palettes can be moved to the top, bottom, or sides of the Console window, or can float as a separate window. The palettes can either be displayed or hidden through the View menu.

•	Move the mouse cursor over a palette icon to display the description the icon's function in the status bar at the bottom of the Console.

For more information, see Launching Tools.

  Related Topics


User Preferred Credentials

This feature allows you to set up specific usernames, passwords, and roles for different services in your network. You determine the preferences for accessing a database, node, or listener with the information you enter in the User Preferences property sheet. These preferences are used when you access a database, listener, or node in the Navigator or Map. See Job Credentials for permissions needed to run job tasks.

The User Preferences property sheet displays a list of databases, listeners, and nodes in the network, along with the service type and the username for accessing the service. The property sheet is accessed with the Preferences option of the Console File menu. Each row in the list of the property sheet includes:

•	Service Name

•	Service Type (database, listener, or node)

•	Username

Note: The names of the parallel servers appear in the list, but the names of the individual parallel server instances do not. When you set the preferred credentials for a parallel server, its instances inherit those credentials.

You can click on a column heading to sort on that column.

If you have not set up preferences for a database, listener, or node, the login information that you entered to access the Console will be used. If that information is not valid for a database, you will have to enter login information each time you access the object. See Entering Login Information.

  Related Topics


Setting User Preferred Credentials

The User Preferences property is displayed with the Preferences option of the File menu. Select any row to access and update the preferences fields for the object identified in the row. Enter the preferences for the connection to the service.

Username

Enter the username.

Password

Enter the password.

Confirm

Confirm the password.

Role

Select the role from the pull-down list.

Note: You need to login with the SYSDBA or SYSOPER role to start up or shut down a database.

Click the OK button at the bottom of the property sheet to save your updates. For more information about dialog boxes and property sheets, see Property Sheets and Dialog Boxes.

  Related Topics


Navigator: Overview

The Navigator discovers and graphically displays objects in a network environment. The Navigator tree shows a direct view of the network's nodes and services, the objects they contain, and the relationships among objects. The Navigator also provides methods for administering the objects.

The topics discussed include the following:

•	Navigator Window

•	Navigator Menu

•	Navigator Context-Sensitive Menus

•	Manipulating Objects in the Navigator

•	Example: Using the Navigator

•	Example: Filtering Folders

For information on using the Navigator with Oracle Parallel Servers, see Parallel Server Support.

  Related Topics


Navigator Window

The Navigator window provides:

•	A view of the objects in a network environment and the relationships among the objects.

•	A method of accessing the objects and administering tasks on the objects.

•	The source for drag and drop objects to create maps.

•	A source of objects to launch DBA tools and other applications.

The Navigator window can be hidden or shown by selecting Show Navigator Pane in the Console View menu. You can also hide or show the window by clicking on the Navigator icon in the Console toolbar.

Each object type in the Navigator tree is identified by an icon and name. If there is a '+' or '-' to the left an object's icon and name, the object is a container that can be expanded to display other objects. A container that is represented by a folder icon is a logical grouping, or collection, of one specific type of object, such as databases, tablespaces, or users. Other containers are objects that hold multiple types of objects.

The top-most object in the Navigator tree is the network container. The network folder contains:

•	Databases folder

•	Groups folder

•	Listeners folder

•	Names Servers folder

•	Nodes folder

•	Parallel Servers folder

You can expand the tree containers to view the objects and relationships that are in the network environment. For example, you can expand a node to view the databases, names servers, and listeners on the node. You can expand the Groups folder to view the user-defined groups. You can expand a database to view:

•	Datafiles

•	In-Doubt Transactions

•	Profiles

•	Redo Log Groups

•	Roles

•	Rollback Segments

•	Schema Objects

•	Tablespaces

•	Users

For more information, see Tree Population.

Note: Refer to the specific DBA tools chapter that administers an object for more information on an object's relationships.

  Related Topics


Tree Population

The Console populates the Navigator tree with information the Communication Daemon discovers about the services in a SQL*Net network. These services include:

•	Databases

•	Groups

•	Listeners

•	Names Servers

•	Nodes

•	Parallel Servers

With Intelligent Agent releases prior to 7.3.3, the Communication Daemon discovers services by reading the topology.ora file that is generated with the Network Manager application or is created manually. Using the information in the topology file, the daemon provides a model of the network. If release 7.3.3 of the intelligent agent is installed, the Navigator Discovery feature is used to populate the Navigator tree with information obtained from the 7.3.3 Intelligent Agent .

Note: If you drop a database, name server, listener, or node object from the Navigator tree and the topology file is used to discover services, the entry for the object must also be deleted from the topology.ora file. Use Oracle Network Manager to update the topology file. If you drop the objects without updating the topology file, the objects will appear again in the Navigator tree when you restart Enterprise Manager.

Note: If you change or update the topology file and restart Enterprise Manager, the entries in the previous topology file will still appear in the Navigator tree until you drop them from the tree list.

For more information on the Communication Daemon, see Intelligent Agents and Communication Daemon. For information on the configuration files, see the Oracle Enterprise Manager Installation Guide.

  Related Topics


Launching Tools

Before you launch a database tool from the Console, select a database or database object in the Navigator tree. You can execute a tool from the Tools menu or by choosing the Related Tools option from the right-mouse menu.

You are connected to the database according to the user preferences that have been set up for the database or the credentials you used to log on to the Console. If connection to the database fails for any reason, the Login Information dialog box displays. For information on user preferred credentials, see Preferred Credentials. For information about connecting to an instance of a database, see Entering Login Information.

  Related Topics


User-defined Groups

User-defined groups are created with the Create Group option of the Map menu. The group types are:

•	Database Groups

•	Listener Groups

•	Names Server Groups

•	Node Groups

•	Parallel Server Groups

You can use groups to organize related objects in the tree. For more information on groups, see The Map Window.

Creating Maps

You can drag and drop nodes, databases, groups, listeners, and names servers from the Navigator tree to the Map window to add those objects to a map. See Map.

  Related Topics


Navigator Menu
Navigator Menu Options

The Navigator menu options allow you to:

•	Create, Create Like, Quick Edit, and Remove objects in the Navigator tree

•	Connect, Disconnect, Startup, and Shutdown databases

•	Discover Services on a node in the network

•	Create and Remove Split Views of the Navigator tree

•	Filter Folders in the Navigator tree

A subset of the Navigator menu options is also available with the Navigator Context-Sensitive Menus.

  Related Topics


Navigator Create, Edit, and Remove Menu Options

These Navigator menu options allow you to create, edit, and remove objects and are enabled according to the object selected in the Navigator tree. The objects include nodes, listeners, databases, and database objects.

Note: For information on operations for an object type, see the chapter in this guide that discusses the specific application that manipulates the object type. For example, if you want information on the create or alter property sheet of user, profile, or role object types, see Security Manager. For an overview of the database application tools, see Database Tools and Utilities.

Create Object

Allows you to create a specified object type.

•	Object is the same type as the object selected in the tree list.

•	After selecting an object, the create property sheet displays to allow you to create a new object.

Note: You cannot create databases, nodes, listeners, or names servers.

Create Object Like

Allows you to create an object similar to the selected object in the tree list.

Quick Edit Object

Allows you to alter or edit an object of a specified type. The Object is determined by the type of the object selected in the tree list.

Remove Object

Allows you to delete all occurrences of the object selected in the tree list.

Suggestion: It is often much easier to Filter Folders than remove objects in the Navigator tree. Filtering allows you to quickly include the object in the tree if necessary at a later time.

Note: To remove a node from the Navigator tree that has been discovered with the Discovery Background option, you must first remove the node from the node list. Then remove the node from the tree with the Navigator Remove option.

Note: If you want to drop a database, name server, listener, or node object from the Navigator tree, you must also delete the entry for the object in the topology.ora file. If you drop the object without updating the topology.ora file, the object will appear again in the Navigator tree when you restart Enterprise Manager. If you change topology files and restart Enterprise Manager, the entries in the old topology file will still appear in the Navigator tree until you drop them from the tree list.

  Related Topics


Navigator Connect, Disconnect, Startup, and Shutdown Menu Options

These options allow you to administer databases and are enabled according to the object selected in the Navigator tree.

Connect

Displays the Login Information dialog box to connect to a database instance. For information about connecting to an instance of a database, see Entering Login Information.

Note: When you expand a database container, you are implicitly connecting to the database.

Disconnect

Disconnects from a database instance.

Startup

Starts up a database. See Instance Manager.

Shutdown

Shuts down a database. See Instance Manager.

  Related Topics


Navigator Split and Remove View Menu Options

These menu options allow you to create and remove new view pages in the Navigator window.

Split View

Creates a new view page in the Navigator window that contains only the currently selected object, such a single folder or a single user. Click on the tab of a page to move the page and its contents to the front of the Navigator window.

For example, to create a new view that contains a specific object, such as the DEMO database:

1.	Select the DEMO database in the tree.

2.	Select the Split View menu option to create a separate view in the Navigator window.

Remove Split View

Removes the current split view from the Navigator. Make sure the view that you want to delete is at the front of the Navigator window.

  Related Topics


Navigator Context-Sensitive Menus

When you click the right mouse button on an object in the Navigator tree, a context-sensitive menu displays. This menu contains a subset of the menu options in the Navigator menu, plus menu options from the database tool that administer the object. For information on the DBA tools menu options, see the chapter of the guide that discusses that tool.

For example, if you click the right mouse button on a user, such as SCOTT, the following menu options would display:

•	Create

•	Create Like

•	Remove

•	Split View

•	Quick Edit

•	Related Tools.

Note: Related Tools in this example are the database tools that administer users. In this case, Security Manager is a related tool.

Note: For information on menu options for an object type, see the chapter in this guide that discusses the specific application that manipulates the object type. For example, if you want information on the menu options for user, profile, or role object types, see Security Manager. For an overview of the database application tools, see Database Tools and Utilities.

  Related Topics


Manipulating Objects in the Navigator

The Navigator interface provides easy manipulation of the objects in the tree list.

•	Discovering Services

•	Viewing Specific Tree Objects

•	Expanding and Collapsing Objects

•	Administering Objects

•	Copying Tree Objects

•	Filtering Folders

  Related Topics


Discovering Services

The Navigator Discovery feature provides a Wizard Option for populating the Navigator tree and identifying the network services that the Oracle Enterprise Manager will administer. This feature works only with nodes that have the Intelligent Agent release 7.3.3 or later installed and running.

Other Navigator Discovery options are:

•	Update SQL*Net Option

•	Status Option

Note: You can continue to use a topology.ora file, in addition to the Discovery feature, for nodes that do not have the release 7.3.3 or later agent installed, or for nodes that cannot be discovered due to non-TCP/IP network configurations. See the Oracle Enterprise Manager Installation Guide for information on the Intelligent Agent and configuration files.

Note: If you add services to a node, you must restart the agent on that node before discovering the new services with the Navigator Discovery option.

  Related Topics


Discovery Wizard Option
Wizard Option

The Wizard option of the Navigator Discovery feature allows you to select the nodes you want to display in the Navigator tree and manage with Oracle Enterprise Manager. There are two types of discovery:

•	Immediate executes an immediate, one-time discovery of nodes.

•	Background discovers nodes continuously at a specified interval.

  Related Topics


Discovery Wizard: Immediate

With Immediate discovery, the selected nodes are discovered as soon as you select Finish. The nodes are not re-discovered until you initiate Immediate discovery again.

Node/IP Address

Enter the names or addresses of the nodes that you want to display in the Navigator tree. Select Add to enter the node in the Available Nodes list.

Load

Use the Load option to load a list of node names or addresses from a file or the Navigator.

Nodes to Discover: Available

Use the << button to place nodes into the Selected Nodes list. Use the Remove button to remove a node.

Nodes to Discover: Selected

Use the >> button to move a node from the Selected to the Available list.

Finish

After you select Finish, the services on the nodes in the Selected list are discovered, and status of the current discovery is displayed.

To complete the Discovery process, select the Update SQL*Net Option to update the SQL*Net configuration.

  Related Topics


Discovery Wizard: Background

With Background discovery, the nodes that you enter are automatically re-discovered on the frequency that you determine.

Page 1

Node/IP Address

Enter the names or addresses of the nodes that you want to display in the Navigator tree. Select Add to enter the node in the Nodes to Discover list. Use the Remove button to remove a node from the list.

Load

Use the Load option to load a list of node names or addresses from a file or the Navigator.

Next

Select Next to move to the next page of the wizard.

Page 2

Frequency

Enter the frequency interval in minutes for node re-discovery.

Finish

After you select Finish, the nodes and their services are discovered, and status of the current discovery is displayed. The nodes are re-discovered on the specified interval.

To complete the Discovery process, select the Update SQL*Net Option to update the SQL*Net configuration.

Note: To remove a node from the Navigator tree that has been discovered in Background mode, you must first remove the node from the node list. Then remove the node from the tree with the Navigator Remove option. See Navigator Menu.

  Related Topics


Discovery Load Option

Load Node names from a text file

Use this option to load a text file that contains a list of node names or addresses that you want to discover. In the text file, each name or address must be on a separate line followed by a carriage return.

Load Node names from Navigator

Use this option to load the list of node names that are in the Navigator tree.

After the list of nodes has been loaded, edit the list if necessary to remove any nodes that you do not want to discover.

  Related Topics


Discovery Update SQL*Net Option
Update SQL*Net Option

This option updates the SQL*Net configuration file (tnsnames.ora) with Discovery information. This should be run after a Discovery operation.

  Related Topics


Discovery Status Option
Status Option

This option displays the status of the current discovery process. The node name and information about the most recent discovery attempt is displayed.

You can stop the current discovery process with the Stop Discovery button.

  Related Topics


Viewing Specific Tree Objects

In large, complex environments you may not wish to view the entire system in one tree so the Navigator has been designed to be highly flexible.

With the Split View menu option, you can split the Navigator tree into views that are displayed in separate pages in the Navigator window. You simply click on the tab of a page to move the page and its contents to the front of the Navigator window.

With the Filter Folder menu option, you can filter the objects in a folder in the Navigator window allowing you to determine which objects are displayed. In a very large system, this option allows you to display only those objects that you need to access. You can use standard SQL wildcard characters when entering the filtering criteria.

  Related Topics


Expanding and Collapsing Objects

The Navigator tree provides various methods for expanding and collapsing objects.

•	To expand and display the contents of a container, click on the '+' to the left of a container's icon and name. The contents of the container varies depending on the type of object container.

Note: The tree list display is often the result of queries executed on a database over a network. Because of this, there may be a delay when expanding a container.

•	When you expand a database, you implicitly connect to the database. The Console uses the preferred credentials that have been set up or the credentials used when you logged on to the Console. If the connection to the database fails for any reason, the Login Information dialog box displays.

For information on user preferred credentials, see Preferred Credentials. For information about connecting to an instance of a database, see Entering Login Information.

•	To collapse a container, click on the '-' to the left of a container's icon and name. You can also double-click on containers to collapse and expand them.

  Related Topics


Administering Objects

You can perform some of the administrative tasks that are in the DBA tool applications through the Navigator. The Navigator provides a subset of the options for administering an object.

•	To administer an object, select the object in the Navigator tree and choose the administration task from the Navigator menu. The menu options available vary according to the object selected. When you create or edit an object, the property sheet for that object displays. See Navigator Menu.

For information on the property sheets, see the chapter on the DBA tool that administers the object.

•	When you choose to edit a database, the database property sheet displays. If the connection to the database fails for any reason, the Login Information dialog box displays.

For information on user preferred credentials, see Preferred Credentials. For information about connecting to an instance of a database, see Entering Login Information. For information on the database instance property sheet, see Instance Manager.

•	When you select tree objects with the right mouse button, a context-sensitive menu displays with a subset of the Navigator menu options and a Related Tools menu. The Related Tools menu lists the database tools that administer the object. For information on the context-sensitive (right mouse) menu options, see Navigator Context-Sensitive Menus. For information on the Navigator menu options, see Navigator Menu.

  Related Topics


Copying Tree Objects

You can drag and drop a limited set of objects in the tree list to make copies of the object in different locations. For example, you can drag and drop a user or role from one database to another to create an identical user in a different database.

Note: If you drag and drop a user to a database where the user’s Default or System tablespace does not exist, you are prompted to reassign the tablespace. If you choose to reassign the tablespace, the User property sheet displays. If you do not choose to reassign the tablespace, you cannot add the user.

•	To make an identical copy of a user in several databases, select the user you want to copy from one database and drag and drop the user to the additional databases where you want the user to appear.

•	To add a role or privilege to a user in a database, select the role or privilege in the tree and drag and drop the role or privilege to the appropriate folder under the user.

Note: If you attempt a drag and drop operation that cannot be done, a circle with a slash appears to alert you.

  Related Topics


Filtering Folders

With the Navigator Filter Folder menu item you can filter folders to display specific sets of objects. The filtering is determined by the criteria you enter in the filter dialog box. You can use SQL operators in the criteria field.

When you select the Filter Folder menu item, the Filter Folder dialog box displays.

To Filter a folder:

1.	Select the folder you want to filter.

2.	Choose Filter Folder from the Navigator menu.

3.	Enter the criteria that you want to filter on in the Filter Text field. You can use SQL operators in the criteria field, such as %. The filter is case-sensitive. See Filtering Folders example.

4.	Click the OK button.

5.	Expand the folder to view the filtered contents.

To turn off filtering:

1.	Select the folder where you want to remove the filter.

2.	Choose Filter Folder from the Navigator menu.

3.	Check the Disable Filter box to turn off filtering.

4.	Click the OK button.

  Related Topics


Example: Using the Navigator

This example shows you how to manipulate various objects in the Navigator tree.

1.	Click on the '+' to the left of the Network folder to expand the tree. If there is a '-' instead of a '+', the folder is already expanded.

2.	Select the Databases folder from the Navigator tree and choose Split View from the Navigator menu to create a new page in the Navigator window. Create a new page for the Nodes folder.

3.	In the Databases page, click on the '+' sign to the left of the Databases folder to expand the branch and display the databases.

4.	Click on the '-' sign to the left of the Databases folder to collapse the branch.

5.	In the Nodes page, click on the '+' sign to the left of the Nodes folder to expand the branch.

6.	Click on the '+' sign to the left of any node to expand the node. Each node contains a Databases, Listeners, and Names Servers folder. However, the folders may not contain any items.

7.	Click on the '+' sign to the left of the Databases, Listeners, and Names Servers folders to expand the folders and view the contents. The folders may not contain any items.

8.	Continue to expand the objects in the Databases, Listeners, and Names Servers folders until everything is expanded. When you expand some objects, such as a database, you may need to enter login information. See Entering Login Information.

9.	Select any object in the tree and pull down the Navigator menu. Note the options that are available. These are the administrative tasks that can be performed on this object in the Navigator.

10.	Select the same object in the tree and hold down the right mouse button to display a context-sensitive menu. Note the options that are available.

11.	Select a Users folder in an expanded database. Expand the Users folder and select a user with the right mouse button. Choose Quick Edit from the context-sensitive menu to display the property sheet. Click the OK button when you are finished viewing the pages of the property sheet.

12.	Select the Databases page in the Navigator window and choose Remove Split View from the Navigator menu. Remove the Nodes page from the Navigator window.

  Related Topics


Example: Filtering Folders

This example shows how to display only the databases that begin with "db".

1.	Select the Databases folder in the Navigator tree.

2.	With the Databases folder selected, choose Filter Folder from the Navigator menu.

3.	Enter db% in the Filter Text field of the Filter Folder dialog box to display only those databases that begin with "db". Click the OK button to filter the databases branch.

4.	Make sure the Disable Filter button is not checked.

5.	Click the OK button.

  Related Topics


Job Scheduling: Overview

The Job Scheduling services allow you to automate standard and repetitive tasks, such as executing a SQL script or running an operating system program. With the Job system, you can create and manage jobs, schedule execution of jobs, and view information about the jobs. Jobs can be scheduled on a single node or multiple nodes in the network, provided that the node has an intelligent agent running on it. The topics include:

•	Job Scheduling Process

•	Job Window

•	Job Menu

•	Active Jobs Page

•	Job History Page

•	Job Library Page

•	Creating, Modifying, or Viewing a Job

•	Example: Creating a Job

•	Job Output Window

•	Predefined Job Tasks

For information on jobs for an Oracle Parallel Server, see Parallel Server Support.

  Related Topics


Job Scheduling Process

The Job scheduling process includes:

•	Creating a job. This involves:

•	Determining the type and destination of the job.

•	Determining the tasks of the job.

•	Determining the task parameters.

•	Scheduling the times that the job executes.

•	Saving and modifying a job, if desired.

•	Submitting a job to the Job system.

•	Viewing the job history to review the results of the job.

  Related Topics


Job Tasks

The Job system provides a variety of pre-defined job tasks, or you can submit your own tasks by executing a SQL*Plus script or running an operating system program. Job tasks are implemented in the Tool Command Language (Tcl) scripts with Oracle extensions to include database specific commands. For more information on job scripts, see the Oracle Enterprise Manager Application Developer's Guide.

The tasks are grouped by the destination of the task:

•	Databases, which also include Node tasks

•	Name Servers, which also include Node tasks

•	Nodes

•	Listeners, which also include Node tasks

The task scripts allow you to:

•	Execute operating system programs or shell scripts.

•	Execute SQL and DBA scripts.

•	Perform database administration tasks including, starting up and shutting down Oracle databases.

•	Start up and shut down SQL*Net Listeners.

•	Distribute and install software.

For information on the predefined job tasks and their parameters, see Predefined Job Tasks.

You can combine two or more pre-defined tasks into one job, called a composite job. Composite jobs can contain test conditions based on the success of a task. For example, if a composite job consists of two tasks, starting up a database and then running a SQL script, you can specify that the script be run only if the database was successfully started.

You can create jobs that can be used as fixit jobs for event conditions that are monitored with the Event Management System. Fixit jobs cannot be scheduled. See Event Management for information on monitoring events in the system.

Note: You need to set up a password file to perform administration tasks, such as start up or shut down, on a remote database. See Administration of a Remote Database.

  Related Topics


Submitting Jobs

The Job system is simple to use because the task of scheduling and managing jobs is centralized in the Enterprise Manager Console. The administrator only needs to submit a job once, regardless of the number of destinations on which the job will run or the number of times the job will be run. See Job Credentials for permissions needed to run job tasks.

When you submit a job, the Console's daemon process sends the job information to the appropriate intelligent agents on the destinations you selected. The agents are responsible for executing the job on schedule and returning job status messages back to the daemon.

Note: There is usually a slight delay between the submitting the job and the notification by the agent.

To schedule a job, you do not have to connect to the node on which the job will be run. You only need to submit the job to the Console and specify the destinations on which it should run. The destinations can include nodes, databases, listeners, names servers, and user-defined groups that have been created with the Map system.

Note: Jobs can only be run on nodes where an intelligent agent is running. If you send a job to a group, the job is only scheduled on the nodes in the group where the agent is running.

The Job system of Enterprise Manager allows you to efficiently run jobs on multiple remote nodes by transferring job information to the agents servicing the nodes. When a job is executed, it is run by the agent on that node, thus minimizing network traffic between the remote node and the Console and communication daemon. In addition, jobs can be run on multiple nodes simultaneously because there is an intelligent agent residing on each node.

When you submit a job to one or more remote sites, it is possible that any one of those site may be down. If a site or its agent is down, the communication daemon queues any job requests that could not be delivered to the site. Once the site can be contacted, the daemon submits the queued job to the agent.

  Related Topics


Job Credentials

Jobs are normally run with the user preferences of the administrator who submitted the job. This means that jobs cannot be used to perform functions the administrator could not perform if logged into the machine directly. For example, to write a job output file to the ORACLE_HOME/network/agent/ directory, the administrator must have permissions to write to that directory.

Because jobs are categorized by the type of service they act on, the job system knows what credentials to pass to the agent. If the job runs on a node, the job system passes either the user preferences for the node or, if none are specified, your Console username and password. If the job runs on a service, such as a database, the job system also passes the user preferences for the service. For information on user preferences, see Preferred Credentials.

  Related Topics


Job Window

You can view the different pages of job information by selecting the page tabs in the Job window. The pages in the Job window are:

•	Active Jobs

•	Job History

•	Job Library

You can switch between the pages by clicking on the tab of each page. The rows in both pages can be sorted on any column by clicking on the column heading.

The Job window can be hidden or shown by selecting Job in the Console View menu. You can also hide or show the window by clicking on the Job system icon in the Console toolbar.

  Related Topics


Active Jobs

The Active Jobs page contains a summary of the active jobs on the network. These are jobs that you have submitted to the job system and are not yet completed. Each row is an execution of a particular job scheduled on a specific destination. While a job may execute multiple times, the job listed in the Active Jobs page is the one that is currently scheduled or running. You can use the Show Details menu option to display the details of the selected job. You cannot modify these jobs.

Note: You can double-click on a job listed in the Active Jobs page to view the job details.

•	Job type is determined by an icon at the left of each row. For example:

•	A database icon signifies a database.

•	A computer icon signifies a node.

•	An ear icon signifies a listener.

•	A NS icon signifies a names server.

•	Job Name is the name of the job.

•	Status of job is one of the following:

•	Submitted: The job has been submitted to the agent at the job destination.

•	Scheduled: The job has been successfully delivered to the agent and is scheduled for execution.

•	Running: The job execution has started. After the job executes, the job execution is displayed in the Job History page. If this is the last scheduled execution of the job, the job is removed from the Active Jobs page. Otherwise, the job remains in the Active Jobs page and has the status of Scheduled. Unless you view the Active Jobs page at the exact time that the job is executing, you would not see the Running status.

•	Pending Deletion: The job has been selected for deletion. When the deletion is successful, the job is removed from the Active Jobs page and added to the Job History page.

•	Fixit: The fixit job has been submitted.

•	Fixing: The fixit job is executing. A fixit job remains in the Active Jobs page until it is deleted.

•	Destination of the job.

•	Next Execution Time of the job. A fixit job cannot be scheduled and displays Unknown for the next execution time.

  Related Topics


Job History

Job History contains a list of previous job activities, such as multiple executions of a job. These are jobs that have been submitted to an agent and have executed successfully or unsuccessfully. This page also lists deleted jobs. You cannot modify these jobs.

•	Job type is determined by an icon at the left of each row. These icons are the same as the Active Jobs page. See Active Jobs.

•	Job Name is the name of the job.

•	Destination of the job.

•	Status of job is one of the following:

•	Completed: The job has executed successfully.

•	Failed: The job execution has failed.

•	Deleted: The job has been deleted.

For the other status categories, see Active Jobs.

•	Execution Start Time is the time when the job started or was deleted. Because the order of agent notifications may vary, it is possible that the Console receives a completed or failed notification before a running notification. If this happens, the start time displays Unknown.

•	Execution End Time is the time when the job finished, failed, or was deleted.

Note: You can double-click on a job listed in the Job History page to display the Job property sheet and view the Job Output dialog box, if output exists for the job. If no output is produced by a job, a message displays that states that there is no output for the job. If the output includes only blank spaces, the dialog box is blank.

Saving Job History

You can save the jobs from the Job History page to a text file and clear the jobs from the Job History window. This prevents the Job History page from being overloaded with obsolete jobs that occurred in previous days.

  Related Topics


Job Library

Job Library contains a list of the jobs that you have created and saved. These jobs can be submitted to the job system at a later date. This is useful if you want to submit the same job at different times. You can use the Modify Saved Job menu option to modify a job selected in this page.

•	Job Name is the name of the job.

•	Job Description is the user supplied description of the job.

Note: You can double-click on a job listed in the Job Library page to modify the job.

  Related Topics


Job Menu

The Job menu allows you to manage jobs. The menu options are enabled depending on the items selected in the Job window.

Job menu options allow you to:

•	Create, Show, Remove, Modify, and Submit Jobs

•	Save, Print, and Clear Job History

Context-Sensitive Menus

If you select an item in the Job window with the right mouse button, the context-sensitive menu for that item appears. This menu is a subset of the Job menu.

  Related Topics


Job Create, Show Details, Remove, Modify, and Submit Menu Options

These Job menu options allow you to create, show, remove, modify, and submit jobs.

Note: When you submit or delete a job, there is usually a slight delay while the agent processes the request.

Create Job

Allows you to create a new job. See also Creating, Modifying, or Viewing a Job.

Show Details

Displays the property sheet for the selected job in the Active Jobs page of the Job window. The property sheet is in read-only format. Active jobs can be removed but not modified. See also Creating, Modifying, or Viewing a Job.

Remove Job

Removes the selected job from the Active Jobs page of the Job window. If you experience problems removing a job, see the Delete option of the Daemon Manager Menu.

Modify Saved Job

Allows you to modify the job selected in the Job Library page of the Job window. The property sheet is the same as the property sheet for creating a new job. See also Creating, Modifying, or Viewing a Job.

Note: You can also double-click on a job listed in the Job Library page of the Job window to modify the saved job.

Submit Saved Job

Submits the selected saved job to the Job system.

  Related Topics


Job Save, Print, and Clear History Menu Options

These Job menu options allow you to save, print, and clear job history.

Save History

Saves the contents of the Job History page to a text file. Enter a valid file name or select an existing file in the file selection dialog box.

Note: This action is recommended before clearing the Job History window.

Print History

Prints the jobs listed in the Job History page.

Note: This action is recommended before clearing the Job History window.

Clear History

Clears the jobs listed in the Job History page.

Note: The information is deleted from the repository.

  Related Topics


Creating, Modifying, or Viewing a Job

When you create, modify, or view details of a job, similar property sheets display. The contents of the Create Job and Job Details property sheets are nearly identical. The property sheets contains:

•	General Page

•	Task Page

•	Parameters Page

•	Schedule Page

•	Progress Page (Show Details only)

See also:

•	Output Dialog Box

•	Example: Creating a Job

Attention: When submitting a job that consists of multiple tasks, an error may occur if the string of arguments that was sent is longer than the internal buffer. If that error occurs when submitting a job, divide the tasks among multiple jobs and resubmit the jobs.

  Related Topics


Creating Jobs

To create a new job:

1.	Select Create Job from the Job menu to display the Create Job property sheet.

2.	Complete the pages of the Create Job property sheet.

3.	Determine whether the job is ready to submit.

a.	Click on the Submit button to submit the job to the agents at the selected destinations. The job appears in the Active Jobs window.

b.	Click on the Save button to save the job. The job appears in the Job Library window. You can modify or submit a saved job at a later time.

Note: There is usually a slight delay between the submitting the job and the notification by the agent.

  Related Topics


Modifying Jobs

Note: Only saved jobs that are in the Job Library page of the Job window can be modified. Submitted jobs in the Active Jobs window cannot be modified.

To modify a saved job:

1.	Select a saved job in the Job Library page of the Job window.

2.	Select Modify Saved Job from the Job menu to display the Job Details property sheet.

3.	Update the pages of the Job Details property sheet.

4.	Determine whether the job is ready to submit.

a.	Click on the Submit button to submit the job to the agents at the selected destinations. The job appears in the Active Jobs window.

b.	Click on the Save button to save the job. The job appears in the Job Library window. You can modify or submit a saved job at a later time.

  Related Topics


Viewing Job Details

To view the details of a job:

•	Select a job in the Active Jobs page of the Job window.

•	Select Show Details from the Job menu to display the Job Details property sheet.

•	View the pages of the Job Details property sheet. This property sheet cannot be modified.

  Related Topics


Job Property Sheet: General Page

The General page allows you to determine job name, description, type, fixit job status, and destinations.

Job Name

Enter the name of the new job.

Description

Enter the description of the job.

Fixit Job

Check this box if you want to use this job as fixit job to correct an event condition. The fixit job must be submitted to the destination where the event is being monitored. A fixit job cannot be scheduled.

The job can be selected from the Fixit Job list in the Event Set Management Parameters page after it has been successfully submitted to an agent. For information on fixit jobs with events, see Event Set Property Sheet: Parameters Page.

Destination Type

Select the destination type from the pull-down list: Database, Listener, Node, Names Server, or Parallel Servers.

Job destinations

Select the destinations of the job in the Available Destinations list and click the << (Add) button to move the destination to the Selected Destinations list.

The destinations are determined by the Job Type. The destinations include databases, listeners, nodes, names servers, and groups of these objects.

•	For an operating system task, a list of nodes and node groups displays.

•	For a database task, a list of databases and database groups displays.

•	For a listener task, a list of listener and listener groups displays.

•	To remove a destination from a job, select the destination in the Selected Destination list and click the >> (Remove) button.

Note: Only network objects that have an agent running are included in the list of available destinations.

  Related Topics


Job Property Sheet: Task Page

The Task page allows you to choose the tasks that you want the job to perform.

Available Tasks

Select a task and click on the << (Add) button to include the task in the job. You can add multiple tasks to the job from the Available Tasks scrolling list.

For information on job tasks and parameters, see Predefined Job Tasks.

Selected Tasks

You can remove tasks from this list. Select the task and click on the >> (Remove) button.

Arrow buttons

Use the arrow buttons to change the order of the tasks or to make a task conditional on a previous task.

•	You can change the order in which the tasks are executed. Select a task in the Selected Tasks list and click on the up or down arrow button to position the task.

•	You can make a task conditional on a previous task. Select a task and press the right arrow button to indent the task. A conditional, or indented, task is executed only if the previous task located further to the left successfully executes.

Note: If any task does not execute, control moves to the next task on the same level as the task that did not execute.

•	You can also select a task and click the left arrow button to move the task to the left and eliminate conditional execution.

  Related Topics


Job Property Sheet: Parameters Page

On the Parameters Page, you specify parameter settings for the selected job tasks. To set the parameters for a task, select the task in the Selected Tasks list. The parameters for the selected task are displayed on the right side of the Parameters Page.

Selected Tasks

Select the task that you want to set parameters for.

Task Parameters

Specify the parameters for the selected task. You can enter values in the entry boxes or select values from the pull-down lists.

The parameters vary according to the job task. For information on the specific task parameters, see Predefined Job Tasks.

For some jobs, you can override the preferred credentials for connecting to the service. This allows you to enter a username and password. For information on user preferences, see Preferred Credentials for more information.

  Related Topics


Job Property Sheet: Schedule Page

The Schedule page allows you to schedule the execution of the job task.

Execute

Select the frequency that you want the task executed. The choices are Immediately, Once, On Interval, On Day of Week, and On Date of Month.

•	Immediately submits the task as soon as you finish the setup process. The task executes only one time.

•	Once schedules the task only one time at the date and time you choose.

•	On Interval allows you to schedule a specific time interval between task executions. The interval can be a combination of hours and minutes, or number of days. Select the value you want to change and click on the scroll buttons. You can also type in a new value.

•	On Day of Week allows you to schedule the task on one or multiple days (Sunday, Monday, etc.) of the week. Click on the days of the week to select the days you want the task scheduled.

•	On Date of Month allows you to schedule the task on one or multiple days (1 - 31) of the month. Click on the dates of the month to select the dates you want the task scheduled.

Note: If you choose a day, such as 31, that is not in a month, the job will not be run in that month.

Start Execution

Choose the first date and time that you want the task executed. This is the starting time for any task scheduled on an interval.

•	Select the month, day, or year in the Date field and click on the scroll buttons to change the value. You can also type in new values.

•	Select the hour, minute, or AM/PM in the Time field and click on the scroll buttons to change the value. You can also type in new values.

End Execution

Choose the last date and time that you want the task executed. This option does not apply if you chose the Immediately or Once execution options.

•	Select the month, day, or year in the Date field and click on the scroll buttons to change the value. You can also type in new values.

•	Select the hour, minute, or AM/PM in the Time field and click on the scroll buttons to change the value. You can also type in new values.

Time Zone

Select the time zone from the pull-down list. The choices are Agent, Console, and GMT.

Note: Only the Agent time zone is available with this release.

•	Agent: The agent schedules the task execution at each destination based on the actual system time of each agent. Tasks are not necessarily run simultaneously.

•	Console: The agent schedules the task execution simultaneously on all destinations based on the system time of the Console.

•	GMT: The agent schedules the task execution simultaneously on all destinations based on Greenwich Mean Time.

For information on Oracle Parallel Server job task scheduling, see Parallel Server Job Scheduling.

  Related Topics


Job Property Sheet: Progress Page

The Progress page contains a list of all the occurrences of a specific job. Each row in the page summarizes a status change of the job.

When you display the Progress page by double-clicking on a job execution, the page displays the notifications only for the destination and execution time of the job occurrence selected.

•	If you select an execution from the History Page, the Progress page typically displays Submitted, Scheduled, Running, and Completed or Failed notifications for that execution.

•	If you select an execution from the Active Jobs page, the Progress page displays those notifications that have already been received.

To view the notifications associated with other destinations or execution times, select other destinations or execution times from the pull-down lists. You can also select <All> in either list to view all notifications. If the job has been Deleted on a destination, the Deleted notification always displays at the top of the Progress Page.

Note: The Progress page is only available with the Show Details option of the Job menu.

The columns contain the following information:

Job Type

The job type is depicted with an icon at the left of the row. These icons are the same as the Active Jobs page. See Active Jobs.

•	A file icon signifies a database.

•	A computer icon signifies a node.

•	An ear icon signifies a listener.

•	A NS icon signifies a names server.

Status

For information on the status of a job, see Active Jobs and Job History.

Destination

This is the destination of the specific occurrence of the job.

Notification Time

This is the time the Console was notified.

The following options are available on the page:

Destination

Select the destination of the job occurrences you want to view from the pull-down list. Select <All> for all destinations. The list of job occurrences changes according to the selection.

Execution

Select the execution time of the job occurrences you want to view from the pull-down list. Select <All> for all executions. The list of job occurrences changes according to the selection.

Save As

Select the Save As button to save the list of job occurrences as a local file using the standard Windows file dialog box.

Print

Select the Print button to print the list of job occurrences in the Progress page.

Show Output

If output exists for an occurrence of a job, you can display the output in the Output dialog box. To display any existing output:

•	Select the job occurrence in the list and click on the Show Output button.

•	You can also double-click on a selected job to display output.

  Related Topics


Job Output Dialog Box

The Job Output dialog box displays any output as a result of the execution of an occurrence of a job.

Note: If no output is produced by a job, a message displays that states that there is no output for the job. If the output includes only blank spaces, the dialog box is blank.

With the Output dialog box displayed, the following options are available:

Save As

Select the Save As button to save the output as a local file using the standard Windows file dialog box.

Close

Select the Close button to exit the dialog box after viewing it.

Print

Select the Print button to print the contents of the dialog box.

  Related Topics


Example: Creating a Job

This example illustrates how to complete the General, Tasks, Parameters, and Schedule Pages when creating a job.

1.	Select Create from the Job menu to create a new job. The Create Job property sheet displays.

2.	Enter a name for the new job in the Job Name field of the General page. You may also enter a description for the job in the Description field.

3.	Do not check the Fixit Job box for this job. You can create jobs that are used specifically as fixit jobs. Fixit jobs can be run automatically in response to an event occurrence. For information on fixit jobs with events, see Event Set Property Sheet: Parameters Page.

4.	Select Database from the Destination Type pull-down list.

5.	Select a destination from the Available Destinations list, then click on the << (Add) button to add the destination to the Selected Destinations list.

6.	Repeat the previous step for another destination. You are choosing the destinations where the job will be run.

7.	Click on the Tasks page tab of the Create Job property sheet.

8.	Select Run SQL*Plus from the Available Tasks list, then click the << (Add) button to add the task to the Selected Tasks list.

9.	Click on the Parameters page tab of the Create Job property sheet to set the following parameters:

a.	Click on the Browse button to locate the name of the existing SQL*Plus script file that you want to run. After you locate the file in the file selection box, click the OK button. The contents of the SQL*Plus script appears in the Script Text box. Edit the contents of the existing SQL*Plus script if necessary. Click on the Save button to save your updates.

Note: If you want to create a new script, enter SQL*Plus commands in the Script Text box before entering a SQL*Plus filename. For example, you could enter “SELECT * FROM dba_users;”. When you are finished, click the Save button and provide a name for the new SQL*Plus script file.

b.	Enter any command-line parameters that you want to run with the SQL*Plus script in the SQL Parameters field.

c.	Do not check the Override Preferred Credentials box. If you do not override the credentials, the information that is set up with the User Preferred Credentials property sheet is used.

10.	Click on the Schedule page tab of the Create Job property sheet to schedule the execution of the job.

11.	Select the On Interval Execute button to execute the job on a specific interval.

12.	Set the Start Execution Date of the job to 3/1/97. Select the month value in the Start Execution Date field and enter 3. You can also click on the up and down arrows to change the value when a number is selected.

13.	Repeat the process in the previous step for the day and year values of the Start Execution Date.

14.	Change the Start Execution Time to 12:00 AM. Use the same procedure that you used to set the date.

15.	Check the End Execution box to allow you to set a final execution date for this job.

16.	Set the End Execution Date of the job to 6/30/97. Set the End Execution Time of the job to 12:00 AM.

17.	Select Agent from the Time Zone pull-down list. This job will execute at the local time zone where the agent is located. This is the time zone of the destination.

18.	Select the Every ... Days button to set the job frequency for day interval. Click on the up arrow to change the value to 3 days.

19.	Click the Save button to save the new job in the Job Library window. You may want to modify this job later.

20.	Select the job in the Job Library window and choose the Modify Saved Job menu option from the Job menu. You can also double-click on the job.

21.	Click on the Submit button to submit the job to the agents at the selected destinations.

When the agent begins processing the job, the job appears in the Active Jobs page in the Job window. If the job is processed successully, the job will start executing on 3/1/97 at 12:00 AM.

  Related Topics


Job Error Dialog
Job Error Dialog Box

This dialog box displays to warn you of an error condition. You should correct the condition before continuing with the job operation.

  Related Topics


Predefined Job Tasks

This section lists the Job Scheduling system predefined job tasks and their parameters. This information is entered in the Tasks and Parameters pages of the Create Job property sheet. The name and the parameters are listed for each task.

The job tasks are written in the Tool Control Language (Tcl) enhanced with Oracle Tcl commands (OraTcl). You can write your own Tcl script and submit it with the Run Tcl job task.

The tasks are divided into several categories:

•	Oracle Database Tasks

•	Operating system or Host Tasks

•	SQL*Net Listener Tasks

•	Data Manager Tasks

•	Software Manager Distribution Tasks

•	Parallel Server Tasks

Note: For information on using Tcl and OraTcl to write custom job scripts, see the Oracle Enterprise Manager Application Developer's Guide.

  Related Topics


Oracle Database Tasks

These are the tasks that can be run on databases and database groups. In addition, you can run operating system or host job tasks.

•	Run SQL*Plus

•	Run DBA Script

•	Shutdown Database

•	Startup Database

•	Backup

Note: You need to set up a password file to perform administration tasks on a remote database. See Administration of a Remote Database.

  Related Topics


Run SQL*Plus

This job executes a SQL*Plus script, allowing any legal SQL or PL/SQL script(s) to be run, including all SQL*Plus formatting commands. You can load a previously created script or simply type SQL commands in the Script Text box. You can record and save SQL commands with the Log menu options and use those saved commands as a script. When you create a SQL script, save it in the ORACLE_HOME\sysman\scripts\sql directory to make the script easily accessible.

Parameters:

1.	SQL File Name. The file must be accessible from the Console. Click on the Browse button to display the standard Windows File selection box to locate the name of an existing file. When you click the OK button after locating a SQL*Plus file, the contents of the file are displayed in the Script Text box.

Note: If you want to create a new SQL*Plus script file, first click the Save button and enter a file name in the File Name field of the Save As dialog box.

2.	SQL Parameters. Enter one or more arguments that you want the script to use.

3.	Override Preferred Credentials. You can use the preferred credentials that have been set up for the database, or you can enter a username and password. If you check the box to override the credentials, then you need to enter:

a.	User Name. Username for accessing the database.

b.	Password. Password for the username.

Note: See Preferred Credentials for more information.

4.	Script Text. You can edit the commands in the Script Text box. Click the Save button to save the updates.

Note: If you want to save the changes to a different file, you can change the name of the SQL file in the File Name field of the Save As dialog box.

Hint: If you need to determine whether a SQL error has occurred during the running of a SQL script, include “WHENEVER SQLERROR EXIT SQL.SQLCODE” at the beginning of the script. This should return the error code to the operating system as the return value.

  Related Topics


Run DBA Script

This job executes a Server Manager line mode script that contains DBA commands. You can record and save SQL commands with the Log menu options and use those saved commands as a script. When you create a DBA script, save it in the ORACLE_HOME\sysman\scripts\dba directory to make the script easily accessible.

Parameters:

1.	DBA Script Name. The file must be accessible from the Console. Click on the Browse button to display the standard Windows File selection box to locate the name of an existing file. When you click the OK button after locating a DBA script file, the contents of the file are displayed in the Script Text box.

Note: If you want to create a new script file, first click the Save button and enter a file name in the File Name field of the Save As dialog box.

2.	Override Preferred Credentials. You can use the preferred credentials that have been set up for the database, or you can enter a username and password. If you check the box to override the credentials, then you need to enter:

a.	User Name. Username for accessing the database.

b.	Password. Password for the username.

c.	Connect As. Select the role you want to connect as from the pull-down list.

Note: See Preferred Credentials for more information.

3.	Script Text. You can edit the commands in the DBA Script box. Click the Save button to save the updates.

Note: If you want to save the changes to a different file, you can change the name of the DBA script file in the File Name field of the Save As dialog box.

  Related Topics


Shutdown Database

This job task shuts down an Oracle database instance.

Parameters:

1.	Mode:

•	Normal

•	Immediate

•	Abort

2.	Role:

•	SYSDBA

•	SYSOPER

3.	Override Preferred Credentials. Check the box if you want to override the preferred credentials that have been set up for the database. If you check the box to override the credentials, then you need to enter:

a.	User Name. Enter the username for accessing the database.

b.	Password. Enter the password for the username.

Note: See Preferred Credentials for more information.

  Related Topics


Startup Database

This job task starts up an Oracle database instance.

Parameters:

1.	Startup State. Select the start up state from the pull-down list:

•	Startup instance, mount, and open database

•	Startup instance and mount database

•	Startup instance only

2.	Parameter File. Enter the initialization parameter filename you want to use for the database. This file is located on the node where the agent and database reside. For example with a database on a Unix platform:

/rdbms/oracle73/myinit.ora

3.	Override Preferred Credentials. Check the box if you want to override the preferred credentials that have been set up for the database. If you check the box to override the credentials, then you need to enter:

a.	User Name. Enter the username for accessing the database.

b.	Password. Enter the password for the username.

Note: See Preferred Credentials for more information.

4.	Mount Mode. Select the mount option from the pull-down list:

•	Exclusive

•	Normal

•	Parallel

5.	Connect As. Select the connecting role from the pull-down list:

•	Sysdba

•	Sysoper

6.	Restrict Connections. Check this box if you want to restrict this session of the the database.

7.	Force Startup. Check this box if you want to force the startup of a database that is running.

  Related Topics


Backup

This job allows you to submit a backup script that has been created with Oracle Backup Manager. The scripts for backing up a database are generated in the Tcl language. You can only update the Backup File Name field.

Parameters:

1.	Backup File Name. The file must be accessible from the Console. Click on the Browse button to locate the backup script filename (.bdf). When you have found the filename with the file selection box, select the file and click on the OK button.

Note: The remaining parameter fields are set according to the selected backup script. The fields are read-only and cannot be modified.

2.	Model Service.

3.	Database status during backup.

a.	Up. Perform a backup when the database is running.

b.	Down. Perform a backup when the database is shut down.

4.	Tablespace status during backup.

a.	Online. Perform a backup when the tablespace is online.

b.	Offline. Perform a backup when the tablespace is offline.

5.	Tablespace to backup.

6.	Backup method.

•	Disk

•	Tape

•	OS Command

7.	Arguments.

8.	Command Style.

a.	Multiple files.

b.	Individual files.

  Related Topics


Operating System or Host Tasks

These are the tasks that can be run on the host's operating system.

•	Broadcast Message

•	Run OS Command

•	Run Tcl Script

  Related Topics


Broadcast Message

This job allows you to submit a broadcast message to the selected destinations.

Parameters:

1.	Message Text. Enter the message text that you want sent to the selected destinations.

  Related Topics


Run OS Command

This is a generic method of running any program or script that is executable on that host, provided your credentials allow you to do that.

Parameters:

1.	OS command or shell script name. The command or script must be accessible from the node where the agent and database reside. You may have to include the path for the agent to locate and execute the command or script.

2.	One or more arguments to the command. For example: -l -p foo

  Related Topics


Run Tcl Script

This job executes a Tcl script. This is a generic method of running any Tcl script that is executable on that host, provided your credentials allow you to do that.

For information on writing custom job tasks, see the Oracle Enterprise Manager Application Developer's Guide. For information on Tcl, see "Tcl and the Tk Toolkit," by John K. Outsterhout, published by Addison-Wesley Publishing Company, 1994. For examples of Tcl job scripts, review the scripts located in ORACLE_HOME\network\agent\jobs\oracle subdirectories on the machine where an agent has been installed. When you create a Tcl script, save it in the ORACLE_HOME\sysman\scripts\tcl directory to make the script easily accessible.

Parameters:

1.	TCL File Name. The file must be accessible from the Console. Click on the Browse button to display the standard Windows File selection box to locate the name of an existing file. When you click the OK button after locating a Tcl script file, the contents of the file are displayed in the Script Text box.

Note: If you want to create a new Tcl script file, first click the Save button and enter a file name in the File Name field of the Save As dialog box.

2.	Parameters. One or more command-line arguments that you want the script to use. The arguments must be delimited by quotes.

3.	Input Files. Enter the filenames for any input files that are accessed by the Tcl script file.

4.	Script Text. You can edit the commands in the Script Text box. Click the Save button to save the updates.

Note: If you want to save the changes to a different file, you can change the name of the Tcl script file in the File Name field of the Save As dialog box.

  Related Topics


SQL*Net Listener Tasks

These are the tasks that can be run on SQL*Net Listeners. In addition, you can run operating system or host job tasks.

•	Shutdown Listener

•	Startup Listener

Shutdown Listener

This stops the SQL*Net Listener.

Parameters:

1.	Password for the listener if you choose to override the default password.

Startup Listener

This can be invoked to start the SQL*Net Listener.

Parameters: None

  Related Topics


Event Management: Overview

The Event Management System (EMS) allows you to monitor specific event conditions that occur in your network environment. You choose predefined events on nodes, databases, or listeners, then select the threshold parameters for which you want to be notified. You can notify specific system administrators when an event condition occurs. For some events, you can also choose to execute a fixit job that automatically corrects the problem. The following topics are discussed:

•	Event Management Process

•	Event Categories and Types

•	Event Window

•	Event Menu

•	Creating or Modifying an Event Set

•	Example: Creating an Event Set

•	Registering an Event Set

•	Example: Registering an Event Set

•	Acknowledging Events

•	Setting up Administrators

•	Mail Configuration

•	Paging Services Configuration

•	Modem Settings

•	Predefined Events

  Related Topics


Event Management Process

The Event Management System allows you to efficiently monitor a large system. Using EMS and intelligent agents, you can effectively monitor a large number of databases 24 hours a day, and be notified when a problem is detected. You can also pinpoint only those services you wish to monitor.

EMS can be extended to include other tools and applications that detect events independent of the intelligent agents. These tools and applications can be integrated into EMS and communicate directly with the intelligent agents.

In the Event Management System, event settings are stored based on the administrator registering the event. This allows administrators of large systems to customize their event systems to their preferences and tasks. Administrators receive only those messages related to the events that they have submitted.

The Event Management System includes the following processes:

•	Determining administrators, mail and paging services, and the system modem.

•	Using event sets.

•	Notifying administrators.

•	Interpreting and correcting an event occurrence.

  Related Topics


Determining Administrators

With EMS, you first set up the notification services and the administrators that need to be notified for the events. If you plan to notify administrators other than the current Console operator, you need to determine:

•	The settings for the system modem.

•	The mail and paging services that are used to contact administrators.

•	The mail address and paging numbers for each administrator.

•	The system responsibility and availability of each administrator.

  Related Topics


Using Event Sets

Next, you need to create event sets, which are simply a group of events that you want to monitor. Oracle Enterprise Manager includes a variety of predefined events that you can use when creating event sets. The events are grouped by the following services:

•	Database

•	Listener

•	Node

Note: Only the UpDown events are included with Oracle Enterprise Manager. Additional events are available with the optional Performance Pack. For more information on events and their parameters, see Predefined Events.

Some events have parameters with suggested default threshold values that you can customize for your system. You can also create your own custom events. EMS events are implemented as Tcl scripts. For more information on writing custom event scripts, see the Oracle Enterprise Manager Application Developer's Guide.

You can also use several predefined event sets that have been installed with Enterprise Manager. See Predefined Event Sets.

Event sets are applied, or registered, to specific destinations, such as nodes, listeners, or databases. The status of an applied event set can be viewed in the Status page of the Modify Registration property sheet. This property sheet is displayed with the Modify Registration option of the Event menu.

The event scripts are stored, registered, and executed on a node with the permissions of the agent. The agent is responsible for detecting when a specific event condition has occurred and, when specified, running a job to fix the problem.

Note: You need to create fixit jobs with the Job system before you can associate them with an event.

Event scripts can save a state, such as values of global variables, between executions of an event script. This allows the agent to remember if it has already detected a certain event and eliminates redundant event messages to the Console.

The Event Management system uses the Console's daemon process to register event set information with the appropriate intelligent agents on nodes in the network. You determine the frequency that an agent checks an event. See Event Set Property Sheet: Parameters Page for details on setting the frequency interval for an event.

  Related Topics


Interpreting Events

All events return values and some events produce output messages. The events return color values depending on the severity of the event. The colors are displayed on the event severity icon that is located:

•	Next to the event listed in the Event window.

•	On the object in the map window. For information on the Map window, see Map.

The colors of the event severity icon are:

•	Event cleared (green)

•	Warning (yellow)

•	Alert (red)

Note: Some events, such as UpDown, Probe, and User Blocks events, do not return a warning value because the warning threshold parameter is not used. The event has either occurred or not occurred.

Some events produce output messages that are displayed in the Error Messages for Event list in the Status page of the Modify Registration property sheet. See Registration Status page.

  Related Topics


Notifying Administrators

When an event condition occurs, the agent is responsible for alerting the Console and administrators. The administrators can be notified in various ways, such as electronic mail or paging. Notification occurs as follows:

•	A notification is sent when the threshold of the event exceeds the level specified by parameter values. If the event does not have parameters, a notification is sent when the event occurs.

•	If the threshold of the event remains above the level specified by parameter values longer than the specified frequency interval, a new notification is not sent.

•	If the event condition changes from a warning to an alert, a new notification is sent.

•	If the event condition changes from alert to warning, a new notification is sent to update the event window.

Each event is logged in the repository and can be viewed and acknowledged in the Event window of the Console.

Note: Refer to the appropriate documentation for information on how to correct event conditions. For example, if an Oracle database problem occurs, refer to the Oracle7 Server Administrator's Guide.

  Related Topics


Correcting Problems

When an event occurs, you need to correct the problem. In some cases, you can create a fixit job specifically for the event. These situations are noted in Predefined Events.

In other cases, the solution requires careful attention by a system administrator. For example, space management event conditions may require an administrator to increase space requirements and resource management conditions may require an administrator to adjust initialization parameters. For information on how to correct event conditions, refer to the appropriate documentation.

•	For Oracle database problems, refer to the following guides:

•	Oracle7 Server Administrator's Guide

•	Oracle7 Server Tuning

•	Oracle7 Server Reference

•	Oracle7 Server SQL Reference.

•	For network problems, refer to the Oracle Network Manager Administrator's Guide.

  Related Topics


Event Categories and Types

The predefined events for the database, listener, and node service types are grouped into categories:

•	Fault Management events

•	Space Management events

•	Resource Management events

•	Performance Management events

Note: Only the UpDown events are included with Oracle Enterprise Manager. Additional events are available with the optional Performance Pack. For more information on events and their parameters, see Predefined Events.

Fault Management Events

This category of events monitors for catastrophic conditions on the system, such as a database, node, or listener is down. Immediate action needs to be taken by the administrator. Examples of events available in this category include:

•	UpDown (Database)

•	UpDown (Listener)

Most of these events do not require any threshold values because the event checks whether the service is up or down.

Space Management Events

This category of events tracks possible space problems, such as running out of space on a disk or archive device. Examples of space management events in this category include:

•	Disk Full

•	Archive Full

To check for space management events, set a threshold on the free space left. For example, set an alert if the free space on a disk falls below a specific number of bytes. In order to properly choose the threshold value, you need to know the characteristics of the tablespaces. For example, you would want to know whether the tablespaces contain online transaction processing (OLTP) tables or decision support tables. The former usually has a very fast growth rate, while the latter almost never grows.

Resource Management Events

This category of events tracks possible resource problems, such as exceeding datafile or lock limits. Examples of resource management events in this category include:

•	Datafile Limit

•	Lock Limit

To check for resource management events, set a threshold on the percentage of a resource used. For example, you can set an alert if the percentage of the datafile resource used is greater than a specified value.

Performance Management Events

This category of event monitors the system for performance problems, such as excessive CPU load or library cache miss rate. Examples of events in this category include:

•	CPU Load

•	Library Cache

To check for performance management events, set a threshold on a system value. For example, you can set an alert if the library cache miss rate is greater than a specific value. The set of threshold values is system specific, depending on the hardware platform, number of users, and other factors.

  Related Topics


Event Window

The Event Management window contains the following pages:

•	Outstanding Events

•	Event History

•	Registrations

•	Event Set Library

You can switch between the pages by clicking on the tab of each page. The rows in both pages can be sorted on any column by clicking on the column heading.

The Event window can be hidden or shown by selecting Show Event Pane in the Console View menu. You can also hide or show the window by clicking on the square clock icon in the Console toolbar.

  Related Topics


Outstanding Events Page

The Outstanding Events page displays event sets that have been applied and have occurred.

Severity

Severity of the event: alert, warning, and clear. These are represented by red, yellow, and green circles.

Event

Name of the event.

Node

Node where the event was monitored.

Type

Type of service that the event monitors, such as Database, Listener, or Node.

Destination

The service that is being monitored.

Date

Date of the event.

Event Message

Message associated with the event, such as "Database went down" or "Tablespace SYSTEM reached 90% capacity."

Ack. Text

The comment entered when the event was acknowledged.

Acknowledging Events

To acknowledge an event that has occurred, double-click on the event to display the Acknowledge Event property sheet. You can also select an event and choose the Acknowledge option in the Event menu. When you acknowledge an event, you can enter notes on the nature and progress of the event condition. See Acknowledging Events.

  Related Topics


Event History Page

The Event History page displays a history of events that have occurred and have been acknowledged by an administrator or cleared by an agent. The Event History Page contains the same columns as the Outstanding Events page, plus the following:

Cleared By

Name of user that cleared the event.

Ack. Date

Date that the event was acknowledged.

Viewing Acknowledgments

To view any comments made by the administrator that acknowledged the event, double-click on the event to display the Acknowledge Event dialog box.

Saving Event History

You can save the events from the Event History page to a text file and clear the events from the Event History window. This prevents the Event History page from being overloaded with obsolete events that occurred in previous days.

  Related Topics


Registrations Page

The Registrations page displays the event sets that have been applied and registered to monitor events on any network objects. The Registrations page contains the following information:

Type

Type of event set, such as Database, Node, or Listener is signified by an icon.

Destination

The service that event is monitoring.

Set Name

Name of the event set that is registered.

Event Status

The number of the pending, and successful, and failed events in the event set.

Modify Registrations Property Sheet

Select Modify Registration from the Event menu or double-click on a registered event set to display the property sheet for the event set. The property sheet allows you to view and modify registration information.

Select the status page tab to display a detailed view of the status of each event. Some events produce output messages that are displayed in the Error Messages for Event list in the Status page of the Modify Registration property sheet. See Registration Status page.

  Related Topics


Event Set Library Page

The Event Set Library page displays the event sets that you have been created and predefined event sets. The Event Set Library page contains the following information:

Type

Type of event set, such as Database, Node, or Listener is signified by an icon.

Set Name

Name of the event set.

Description

Description of the event set.

# of Events

Number of events in the set.

Event Set Property Sheet

Double-click on an event set to display the property sheet for the event set. The property sheet allows you to view and modify the event sets.

  Related Topics


Predefined Event Sets

Several predefined event sets have been installed with Enterprise Manager. These appear in the Event Set Library page of the Event window. You can apply these event sets to destinations on your network. The predefined event sets include:

•	Oracle DB UpDown: checks whether a database is up or down.

•	Oracle Host UpDown: checks whether a node is up or down.

•	Oracle Listener UpDown: checks whether a listener is up or down.

•	Oracle DB Fault: checks whether a database fault event has occurred.

•	Oracle DB Resource: checks whether any of the resource event limits have been exceeded for a database.

Note: Only the UpDown event sets are included with Oracle Enterprise Manager. Additional event sets are available with the optional Performance Pack.

To view the specific events assigned to these event sets, double-click on the event set in the Event Set Library page and view the Event page of the Event Set Management property sheet. For more information on events and their parameters, see Predefined Events.

  Related Topics


Event Menu

The Event menu allows you to manage events and administrator information. Menu options are enabled depending on the items selected in the Event window.

Event menu options allow you to:

•	Create, Modify, and Remove Event Sets

•	Acknowledge Events, Register Events, Modify Registration, and Remove Registration

•	Save, Print, and Clear Event History

•	Set up administrator lists and the configure services for notification

Context-Sensitive Menus

If you select an item in the Event window with the right mouse button, the context-sensitive menu for that item appears. This menu is a subset of the Event menu.

  Related Topics


Event Create, Modify, and Remove Event Set Menu Options

These menu options allow you to create, modify, and remove event sets.

Create Event Set

Displays the Event Set Management property sheet and allows you to create the definition of a new event set. See Creating or Modifying an Event Set.

Modify Event Set

Modifies the definition of an existing event set.  See Creating or Modifying an Event Set.

Remove Event Set

Removes the selected event set from the Event window.

  Related Topics


Event Acknowledge, Register, Modify Registration, and Remove Registration Menu Options

These menu options allow you to acknowledge, apply, modify, and remove event registrations.

Acknowledge Event

Acknowledges the selected event in the Outstanding Events page. Enter any optional comments on the nature or progress of the event condition in the General page of the Acknowledge Event property sheet, then click on the Move to History button to move the event to the Event History page or click on the Keep button to leave the event in the Outstanding Events page. See Acknowledging Events.

Register Event Set

Registers, or applies, the selected event set to a destination. This action monitors the destination, or network object. See Registering an Event Set.

Modify Registration

Modifies the selected registered event set. See Registering an Event Set.

Remove Registration

Removes the selected registered event set. If you experience problems removing an event, see the Delete option of the Daemon Manager Menu.

Note: When you register or remove an event, there is usually a slight delay while the agent processes the request.

  Related Topics


Event Save, Print, and Clear History Menu Options

These menu options allow you to save, print, and clear event history.

Save History

Saves the contents of the Event History page to a file.

Print History

Prints the contents of the Event History page to a file.

Clear History

Clears the contents of the Event History page to a file.

  Related Topics


Event Administrator and Configure Menu Options

These menu options allow you to set up administrator lists and the configure services for notifying the administrators.

Administrator List

Displays a list of administrators in the Administrators dialog box. Each row in the list contains the Administrator's Name, Paging Service, Email Service, and Email ID.

You can add, delete, and modify administrator information in the Administrators dialog box. When add or modify an administrator, the Administrator property sheet appears. The property sheet contains the General, Systems, and Availability pages. See Setting up Administrators.

Configure Services

Displays the Services Configuration menu. You can configure Mail, Paging, or Modem information.

•	To configure mail services, see Mail Configuration.

•	To configure paging services, see Paging Services Configuration.

•	To configure modem settings, dialing information, and trace log, see Modem Settings.

  Related Topics


Creating or Modifying an Event Set

Event sets include the service type and the event information that you want to monitor. Event sets can consist of multiple events. To create or modify an event set:

1.	Choose the Create Event Set option from the Event menu to display the Event Set Management property sheet

2.	Complete or modify the fields in the General and Events pages of the property sheet to create a new event set.

Note: The property sheet for creating a new event set is the same as the property sheet for modifying an event set, except that the event set name field is read-only.

Note: You can use several predefined event sets that have been installed with Oracle Enterprise Manager. See Predefined Event Sets.

For information on the pages of the property sheet, see the following topics:

•	Event Set Property Sheet: General Page

•	Event Set Property Sheet: Events Page

•	Event Set Property Sheet: Parameters Page

•	Example: Creating an Event Set

  Related Topics


Event Set Property Sheet: General Page

On the General page, you determine the event set name, description, and service type.

Name:

Enter an event set name.

Service Type:

Select a service type from the pull-down list. The types include Database, Node, or Listener.

Description:

Enter a description for the event set.

Accept third party events

Check this box to allow the Event system to accept event sets that have been created by third-party vendors. For informaton on creating event scripts, see the Oracle Enterprise Manager Application Developer’s Guide.

  Related Topics


Event Set Property Sheet: Events Page

On the Events page, you determine the events that you want to monitor.

Available Events:

Select the events in the list you want to monitor in this event set, then click on the << (Add) button to move the events to the Selected Events list.

For information on available predefined events, see Predefined Events.

Selected Events:

Select the events in the list you want to remove from this event set, then click on the >> (Remove) button.

  Related Topics


Event Set Property Sheet: Parameters Page

The fixit job, frequency, and parameter settings are entered in the Event Information section of the Parameters page of the Event Set Management property sheet. The settings and types of parameters vary according to the event selected. Some events do not have parameters.

Choose Fixit Job

A fixit job is designed to correct a problem. For example, you may want the agent to run a job to restart a database when the database instance has shut down unexpectedly. Fixit jobs have been created with the Job system and have been designated as fixit jobs. The jobs must be submitted and running on the same destination that the event is set on.

•	Select an existing fixit job from the pull-down list. These are jobs that have been created with the Job system and have been designated as fixit jobs. The jobs must be submitted and running on the same destination that the event is set on.

•	Select <None> to stop a fixit job from executing.

For more information, see Job Scheduler.

Frequency

Determine the frequency that you want the event to monitor the selected destinations. The frequency determines how often the event condition is checked. For example, if the frequency is set to 30 seconds, the event condition is checked every 30 seconds. To ensure timely notification, set the frequency to the smallest interval possible. To set the frequency:

•	Enter a value in the frequency field or select a value from the pull-down list.

•	Select the interval units from the pull-down list.

See Notifying Administrators for information on the notification frequency.

Parameters

The parameters for an event are displayed when the event is selected in the Selected Events list. The parameters vary according to the event selected. Some events do not have parameters.

You can accept the default values or change the values for the parameters. To enter parameter values for an event, you can do one of the following:

•	Enter a value directly into a parameter field.

•	Double-click on an item in a scrolling list to display the parameter dialog box. Enter a value in a parameter field.

For specific information on parameters of predefined events, see Predefined Events.

  Related Topics


Example: Creating an Event Set

In the following example, a new event set for monitoring database space management is created and the General, Events, and Parameters Pages are completed.

1.	To create a new event set, select Create Event Set from the Event Menu to display the General page of the Event Set Management property sheet.

2.	Enter an event set name in the Name field.

3.	Select Database from the Service Type pull-down list. The new event set will monitor Oracle databases.

4.	Enter a brief description of and comments about the event set in the Description field. The events in this example will monitor space management.

5.	Do not check the Accept third party events box.

6.	Click on the Events page tab to display the Events page.

7.	Select the Archive Full event. This Space management event monitors the amount of available space left on the device where archive logs are stored.

8.	Click on the << (Add) button. The event is moved to the Selected Events list and will be added to the event set.

9.	Select the Maximum Extents event. This Space management event monitors the number of available extents for table, index, cluster, or rollback segments.

10.	Click on the << (Add) button. The event is moved to the Selected Events list and will be added to the event set.

11.	Click on the Parameters page tab to display the Parameters page.

12.	Select Archive Full in the Selected Events list to display the Event Information and Parameters for the event.

13.	Do not select a fixit job. These are jobs that have been created with the Job system and have been designated as fixit jobs.

14.	Do not change the frequency that the event monitors the destination. The default frequency interval is acceptable.

15.	Change the Alert and Warning threshold values to 3000 and 6000 respectively. Place the cursor in the field and edit the default values. You can also select the entire default value and enter the new value.

16.	Select Maximum Extents in the Selected Events list to display the Event Information and Parameters for the event.

17.	Do not select a fixit job. These are jobs that have been created with the Job system and have been designated as fixit jobs.

18.	Do not change the frequency that the event monitors the destination. The default frequency interval is acceptable.

19.	Double-click on Warning threshold in the scrolling list, to change the value of the parameter.

20.	Enter 3 in the New Value field of the Enter Parameter Value dialog box, then click the OK button.

21.	Double-click on Alert threshold in the scrolling list, to change the value of the parameter.

22.	Enter 2 in the New Value field of the Enter Parameter Value dialog box, then click the OK button.

23.	Do not change the other parameters. Note that the * in the Tablespace name, Segment name, and Segment type parameter fields signifies all existing values.

24.	Click the OK button at the bottom of the property sheet to save and exit. The new event set appears in the Event Set Library page of the Event window.

You can now register this event set to the destinations you want to monitor.

  Related Topics


Registering an Event Set

You need to register, or apply, an event set to monitor events on specific destinations in the network environment. To register an event set:

1.	Choose the Register Event Set option of the Event menu to display the Register Event Set property sheet.

2.	Complete the fields in the General and Notification pages of the property sheet to register the event set.

To modify or view an event set:

1.	Select a registered event set in the Registrations page of the Event window.

2.	Choose the Modify Registration option of the Event menu to display the Modify Registration property sheet.

3.	You can modify fields in the Notification page but not the General page. Display the Status page to view of the status of each event at every destination.

Note: There is usually a slight delay between the registering the event set and the notification by the agent.

The Register Event Set and Modify Registration property sheets are very similar. The property sheets contain:

•	General page (read only when modifying)

•	Notification page

•	Status page (Modify Registration only)

•	Example: Registering an Event Set

  Related Topics


Registration Property Sheet General Page

On the General page, you identify the event set and destinations that you want the event set to monitor.

Warning: Do not register an UpDown event against the database or node where the repository table is stored. Note that the UpDown event is included in the Oracle DB Fault predefined event set.

The communication between the agent and communication daemon can cause problems with the repository database connection. If the database or node is down, the event cannot notify the Console because the repository is not available.

Service Type:

Select a service type from the pull-down list. The types include Database, Node, or Listener.

Set Name:

Select an existing event set name from the pull-down list.

Description:

Displays the description of the event set.

The Available destinations vary according to the service type and event set selected.

Available Destinations:

Select the destinations in the list you want to monitor in this event set, then click on the << (Add) button.

Note: Only network objects that have an agent running are included in the list of available destinations.

Selected Destinations:

Select the events in the list you want to remove from this event set, then click on the >> (Remove) button.

  Related Topics


Registration Property Sheet Notification Page

On the Notification page, you determine who is notified and how they are notified for each destination.

Note: You need to set up administrators and notification methods before you complete this page. See Setting up Administrators.

Destination

Select a destination from the pull-down list.

Notify Operator on Duty

Check this option to notify the operator that is on duty when the event occurs.

Cause SNMP Trap At Agent

Check this box to trap the notification at the destination where the agent is located. The notification is sent via the SNMP Master Agent to an SNMP Console, such as HP OpenView, rather than the OEMGR Console.

Operators

Select an operator in the list, then select the notification method for this operator.

Notification Method

Choose the method for notifying the operator selected in the Operators list.

•	Check the EMail box to notify the selected operator by mail.

•	Check the Paging box to notify the selected operator by pager.

  Related Topics


Example: Registering an Event Set

In the following example, an event set for monitoring database space management is registered to a group of databases.

1.	To register the event set to a destination, select Register Event Set from the Event menu.

2.	Select Database from the Service Type pull-down list in the General Page.

3.	Select the event set name from the Set Name pull-down list.

4.	Select a database from the Available Destinations list, then click on the << (Add) button. The database is moved to the Selected Destinations list and will be monitored for the events in the event set.

5.	Repeat the previous step for several additional databases.

6.	Click on the Notification page tab to display the Notification page.

7.	Check the Notify Operator on Duty box. For this example, do not notify other administrators by paging or mail.

8.	Click the OK button at the bottom of the property sheet to save and exit. The event set appears in the Registrations page of the Event window. Each destination database is listed separately with the event set.

9.	After the agent for a destination processes the event set, the event set appears in the Outstanding Events page of the Event window.

When threshold values are exceeded for the events, a notification is sent to Console window. This notification will change the color of the circle in the Severity column for the event in the Outstanding Events page. If the destination database icon is displayed in the Map window, the flag on the icon changes color. The colors and their meaning are:

•	Event cleared (green)

•	Warning (yellow)

•	Alert (red)

  Related Topics


Registration Property Sheet Status Page

On the Status page, you can view the status and output messages (if any) of each event at every destination where the event has been registered. The page contains the following:

Destination

Select an event destination from the pull-down list. The events registered at this destination display in the Status of Registered Event list.

Status of Registered Event at Destination

Select an event in the list to view the error messages (if any) for the selected event.

Error Message for Event

Scroll through the list of messages (if any) to view the output of the event. The specific output of each event is described in Predefined Events.

  Related Topics


Example: Viewing Event Registration Status

To view the status and output messages of an event:

1.	Select the event in the Registrations page of the Event window.

2.	Select Modify Registration from the Event menu or double-click on the selected registration to display the Modify Registration property sheet.

3.	Click on the Status page tab of the Modify Registration property sheet.

4.	Select the Destination of the event.

5.	Select the Name of the event in the Status of Registered Events list.

6.	Scroll through the error messages (if any) in the Error Message for Event list.

  Related Topics


Acknowledging Events

Acknowledging events allows you to add comments to an event and move the event from the Outstanding Events to the Event History page.

To acknowledge an event that has occurred, double-click on the event in the Outstanding Events page to display the Acknowledge Event property sheet. You can also select an event and choose the Acknowledge option in the Event menu. This property sheet can also be displayed after the event has been moved to the Event History page to allow you to view event information.

The Acknowledge Event property sheet contains the General and Notification pages. After you have viewed the information on the pages and entered any optional comments in the Comments field of the General page, you can:

•	Click on the Move to History button to move the event to the History page.

•	Click on the Keep button to save any comments and leave the event in the Outstanding Events page.

Acknowledge Event General Page

The General page contains the following fields. Only the Comments field can be updated.

Event

Name of the event.

Date

Date that the event occurred.

System

System where the event occurred.

Node

Destination node.

Event Message

A message describing the event that took place.

Comments

Enter an optional comment for this event. Comments are useful for explaining how the problem was corrected.

Acknowledge Event Notification Page

The Notification page contains the Notification Status field. This field is for display only and cannot be updated.

  Related Topics


Configuring Mail

The Mail Configuration dialog box allows you to determine the mail service information for your system. You must set up this information correctly to notify administrators by mail.

To configure mail services, select the Configure Services Mail option in the Event menu. In the Mail Configuration dialog box, define the information in the following fields:

Current Mail Engine

Set up the mail engine to match the mail engine of your system. Select from the following options in the pull-down list:

•	MAPI (Microsoft Mail Messaging System)

•	SMTP (Simple Mail Transport Protocol)

•	None

MAPI Setup

See the Windows documentation and online help for information on setting up and using the Microsoft Mail Messaging System.

Send Mail As

Enter an optional name or label that you want to attach to the address of the email notification. For example, eventsys.

Password

Enter the password for the MAPI system.

SMTP Setup

SMTP is a TCP/IP-based mail protocol and requires that TCP/IP services are set up on the Console machine. To set up TCP/IP services, access Network settings in the Control Panel of the Console system.

Send Mail As

Enter an optional name or label that you want to attach to the address of the email notification. For example, eventsys.

SMTP Server:

Enter the location of the SMTP mail server, such as smtpserve.world.

  Related Topics


Configuring Paging Services

You configure the paging service names, access numbers, and communication settings with the Paging Services Configuration dialog box. These paging services can be assigned to the administrators you define in the Administrator List dialog box.

To configure paging services, select the Configure Services Paging option in the Event menu. In the Paging Services Configuration dialog box, you can add, modify, or delete paging services.

Adding Paging Services

To add a new paging service:

1.	Select the Add button in the Paging Services Configuration dialog box.

2.	Enter a name for the paging service in the Service Name field of the New Service Name dialog box. This name will appear in the General page of the Administrator property sheet. Select the OK button.

3.	Enter the phone number that accesses the paging service in the Access Number field. Enter digits only.

4.	Determine the Communication Settings fields in the dialog box.

Modifying Paging Services

To modify a paging service:

1.	Select a paging service name in the Paging Services Names list of the Paging Services Configuration dialog box.

2.	Modify the phone number in the Access Number field if necessary.

3.	Modify the Communication Settings fields in the dialog box if necessary.

Deleting Paging Services

To delete a paging service:

1.	Select a paging service name in the Paging Services Names list of the Paging Services Configuration dialog box.

2.	Select the Delete button.

  Related Topics


Communication Settings

These settings define how the system communicates with the paging service. Before changing any settings, use the defaults. For more information on the required settings, contact the paging service.

Baud Rate:

Select the baud rate from the pull-down list.

Data Bits:

Select the data bits from the pull-down list.

Stop Bits:

Select the stop bits from the pull-down list.

Parity:

Select the parity from the pull-down list.

Flow Control:

Select the flow control from the pull-down list.

  Related Topics


Entering Modem Settings

You determine the system modem information, outside line dialing information, and trace log option with the Modem Settings dialog box. This information must be set up correctly to dial a paging service.

To configure the modem settings, select the Configure Services Modem option in the Event menu. In the Modem Settings dialog box, complete the fields in the dialog box to set up the system modem. For more information, see the documentation for the modem.

Serial Port

Select the serial port number of the modem connection from the pull-down list.

Modem Type

Select the modem type from the pull-down list. If your modem is not listed, choose Other.

Init Command

Enter the initialization string for the modem or accept the default command. Refer to your modem documentation for additional information.

Dialing Information

Check the box if you need to enter a prefix to access an outside line. Enter the prefix to access an outside line in the adjacent field.

Trace Log

Check the box to create a trace log. Enter the pathname of the log file in the adjacent field.

  Related Topics


Setting up Administrators

The Event Management system allows you to set up the administrators that are notified when an event occurs. You can then select specific administrators to be notified when applying an event set. When using a paging service or mail notification, each administrator can be assigned responsibility for specific systems at specific days and times.

Each administrator can be associated with both an email ID and a pager number. The administrator's schedule can be set up for any hours on any days of the week by specific system. For example, an administrator can be scheduled from 7:00 AM through 12:00 PM from Monday to Friday, 10:00AM through 2:00 PM on Saturday, and not available on Sunday.

Note: If you plan to use a mail or paging service for notification, you need to configure the mail, paging, and modem settings for your system before you set up administrators. See Mail Configuration, Paging Services Configuration, and Modem Settings.

To manage administrators, choose Administrator List in the Event menu to display the Administrator List dialog box. From the dialog box, you can add, modify, and delete administrators.

Adding Administrators

To add a new administrator definition:

1.	Click on the Add button in the Administrator dialog box to display the Administrator property sheet.

2.	Complete the General, Systems, and Availability pages in the Administrator property sheet to set up a new administrator.

Modifying Administrators

To modify an administrator definition:

1.	Select an administrator in the list.

2.	Click on the Modify button in the Administrator dialog box to display the Administrator property sheet.

3.	Modify the General, Systems, and Availability pages in the Administrator property sheet.

Deleting Administrators

To delete an administrator definition:

1.	Select an administrator in the list.

2.	Click on the Delete button in the Administrator dialog box to delete the administrator.

For more information, see:

•	Administrator Paging Property Sheet: General Page

•	Administrator Paging Property Sheet: Systems Page

•	Administrator Paging Property Sheet: Availability Page

  Related Topics


Administrator Paging Property Sheet: General Page

The General page contains the Administrator's Name, Comments, Paging Information, and EMailing Information. Complete this page to set up the paging service and email address for the administrator. You can also send a test page or email with the Test options on this page.

Name:

Enter the name of the administrator.

Comments:

Enter any comments.

Paging Information:

Carrier:

Select the name of the paging carrier service from the pull-down list. The carriers are set up with the Configure Paging Services option in the Event menu.

Pin:

Enter the paging Pin.

Test

Click the Test button to check the accuracy of the Paging information. In the Test Pager dialog box, select the paging service from the pull-down list, enter the PIN number, and enter a message. Click on the Send button to send a test page to the selected administrator.

EMailing Information:

MAPI Mail ID:

Enter the MAPI mail address of the administrator.

SMTP Mail ID:

Enter the SMTP mail address of the administrator, such as jayr@smp.com.

Test

Click the Test button to check the accuracy of the mail information. In the Test Email dialog box, enter a message and click on the Send button to send a test email to the administrator.

  Related Topics


Administrator Paging Property Sheet: Systems Page

The Systems page defines the systems that the administrator is responsible for.

Available Systems:

Select the names of the systems that the administrator is responsible for, then click the << (Add) button.

Systems responsible for:

Select the names of the systems that the administrator is no longer responsible for, then click the >> (Remove) button.

  Related Topics


Administrator Paging Property Sheet: Availability Page

The Availability page defines the Notification method and the Availability of the administrator for each system that the administrator is responsible for.

Notification:

Select the notification method, All, Email, or Paging, from the pull-down list.

Suggestion: Paging is recommended for urgent events or critical systems.

Systems responsible for:

Select the name of the system in the tree list that the administrator is responsible for.

Availability

Select the hours and days of the week in the table when the administrator is available for the system selected in the list.

  Related Topics


Predefined Events

This section lists the Event Management System predefined event scripts with their parameters and return values. Events are available for database, listener, and node services. The event scripts are written in the Tool Command Language (Tcl) enhanced with Oracle Tcl commands (OraTcl). The following topics are discussed:

•	Managing Events

•	Database Events

•	Node Events

•	Listener Events

Note: For information on using Tcl and OraTcl to write custom event scripts, see Oracle Enterprise Manager Application Developer's Guide.

  Related Topics


Managing Events

The Event Mangement System monitors database, listener, and node service types. The database, listener, and node events are grouped into categories:

•	Fault Management events

•	Space Management events

•	Resource Management events

•	Performance Management events

For information on event categories and service types, see Event Categories and Types.

Note: Only the UpDown events are included with Oracle Enterprise Manager. Additional events are available with the optional Performance Pack.

Entering Event Information

The fixit job, frequency, and parameter settings are entered in the Event Information section of the Event Set Property Sheet: Parameters Page.

Interpreting Return Values and Output

All events return values and some events produce output messages. The events return color values depending on the severity of the event. The colors are displayed on the event severity icon. See Interpreting Events.

Some events produce output messages that are displayed in the Error Messages for Event list in the Status page of the Modify Registration property sheet. See Registration Status page.

Correcting Problems

When an event occurs, you need to correct the problem. In some cases, you can create a fixit job specifically for the event. In other cases, the solution requires careful attention by a system administrator. See Correcting Problems.

  Related Topics


Database Events

Database events are divided into the following categories:

•	Fault Management events

•	Alert

•	UpDown (Database)

•	User Blocks

•	Probe

•	Space Management events

•	Archive Full

•	Dump Full

•	Maximum Extents

•	Chunk Small

•	Resource Management events

•	Datafile Limit

•	Lock Limit

•	Process Limit

•	Session Limit

•	User Limit

•	Performance Management events

•	Disk I/O

•	Net I/O

•	Buffer Cache

•	Library Cache

•	Data Dictionary Cache

•	Response Time

•	SysStat Table

•	SysStat Table Delta

•	Chained Row

  Related Topics


Database Fault Management Events

This category of events monitors for catastrophic conditions on the system. Immediate action needs to be taken by the administrator.

•	Alert

•	UpDown (Database)

•	User Blocks

•	Probe

  Related Topics


Alert

This event signifies that the database being monitored has generated errors to the alert file since the last sample time.

Parameters: none

Output: Alert log since last sample time.

  Related Topics


UpDown (Database)

This event checks whether the database being monitored is available.

Parameters: none

Action: The Startup Database job task can be set up as a fixit job for automatically correcting the problem. To avoid the fixit job executing when the database was brought down intentionally, turn off the fixit job option temporarily.

Note: If the listener serving a database is down, this event is triggered because the Intelligent Agent uses the listener to communicate with the database.

  Related Topics


User Blocks

This event signifies that a database user has been blocked for more times than the value specified in the Number of occurrences parameter.

Parameters:

•	Number of occurrences: Number of occurrences a user can be blocked before an alert is generated

Output: Session Id of the user who has been blocked.

  Related Topics


Probe

This event checks whether a new connection can be established to a database. If the database is down or if the maximum number of users are connected, this event is triggered.

Parameters: none

Note: If the listener serving a database is down, this event is triggered because the Intelligent Agent uses the listener to communicate with the database.

  Related Topics


Database Space Management Events

This category of events tracks possible space problems.

•	Archive Full

•	Dump Full

•	Maximum Extents

•	Chunk Small

  Related Topics


Archive Full

If ARCHIVE MODE is on, this event checks for free space available on the archive destination device. If the space available is less then the threshold value given in the threshold arguments, then an alert or warning is generated.

Parameters:

•	Alert threshold: Free space threshold in kilobytes for alert.

•	Warning threshold: Free space threshold in kilobytes for warning.

Output: Space available.

  Related Topics


Dump Full

This event checks for the free space available on the USER_DUMP_DEST and BACKGROUND_DUMP_DEST destination device. If the space available is less than the threshold value given in the arguments, then an alert or warning is generated.

Parameters:

•	Alert threshold: Free space threshold in kilobytes for alert.

•	Warning threshold: Free space threshold in kilobytes for warning.

Output: Space available.

  Related Topics


Maximum Extents

This event checks for the space utilization of the segments (table, index, cluster, or rollback) specified by the Tablespace name, Segment name, and Segment type parameters. If any segment is reaching its maximum extent, then the administrator is notified. To be more specific, if the maximum extent minus the number of existing extent is less than the threshold values specified in the threshold arguments, then a warning or alarm is generated.

Parameters:

•	Tablespace name: Filter of the tablespace names to be monitored, or * for all tablespaces. Examples of filter are “SYSTEM” and IN (“SYSTEM”, “TOOL”).

•	Segment name: Filter of the segment names to be monitored, or * for all segments. Examples of filter are “SYSTEM” and IN (“SYSTEM”, “TOOL”).

•	Segment type: Filter of the segment types to be monitored, or * for all segment types.

•	Alert threshold: Threshold for alert.

•	Warning threshold: Threshold for warning.

Output: Segment and tablespace names.

  Related Topics


Chunk Small

This event checks for the largest chunk free space in the tablespace specified by the Tablespace name, Segment name, and Segment type parameters. If any table, index, cluster or rollback segments within the tablespace cannot allocate the additional number of extents specified in the threshold arguments, then a warning or alarm is generated.

Parameters:

•	Tablespace name: Filter of the tablespace names to be monitored, or * for all tablespaces. Examples of filter are “SYSTEM” and IN (“SYSTEM”, “TOOL”).

•	Segment name: Filter of the segment names to be monitored, or * for all segments. Examples of filter are “SYSTEM” and IN (“SYSTEM”, “TOOL”).

•	Segment type: Filter of the segment types to be monitored, or * for all segment types.

•	Alert threshold: Threshold for alert.

•	Warning threshold: Threshold for warning.

Output: Segment and tablespace names.

  Related Topics


Database Resource Management Events

This category of events tracks possible resource problems.

•	Datafile Limit

•	Lock Limit

•	Process Limit

•	Session Limit

•	User Limit

  Related Topics


Datafile Limit

This event checks for the utilization of the datafile resource against the threshold values specified by the threshold arguments. If the percentage of the resource used exceeds the threshold values specified in the arguments, then a warning or alarm is generated.

Parameters:

•	Alert threshold: Threshold value for alert.

•	Warning threshold: Threshold value for warning.

Output: Current value and the specified limit.

  Related Topics


Lock Limit

This event checks for the utilization of the lock resource against the threshold values specified by the threshold arguments. If the percentage of the resource used exceeds the threshold values specified in the threshold arguments, then a warning or alarm is generated.

Parameters:

•	Alert threshold: Threshold value for alert.

•	Warning threshold: Threshold value for warning.

Output: Current value and the specified limit.

  Related Topics


Process Limit

This event checks for the utilization of the process resource against the threshold values specified by the threshold arguments. If the percentage of the resource used exceeds the threshold values specified in the threshold arguments, then a warning or alarm is generated.

Parameters:

•	Alert threshold: Threshold value for alert.

•	Warning threshold: Threshold value for warning.

Output: Current value and the specified limit.

  Related Topics


Session Limit

This event checks for the utilization of the session resource against the threshold values specified by the threshold arguments. If the percentage of the resource used exceeds the threshold values specified in the threshold arguments, then a warning or alarm is generated.

Parameters:

•	Alert threshold: Threshold value for alert.

•	Warning threshold: Threshold value for warning.

Output: Current value and the specified limit.

  Related Topics


User Limit

This event checks whether the number of users logged on is reaching the license limit. If the percentage of the resource used exceeds the threshold values specified in the threshold arguments, then a warning or alarm is generated.

Parameters:

•	Alert threshold: Threshold value for alert.

•	Warning threshold: Threshold value for warning.

Output: Current value and the specified limit.

  Related Topics


Database Performance Management Events

This category of event monitors the system for performance problems.

•	Disk I/O

•	Net I/O

•	Buffer Cache

•	Library Cache

•	Data Dictionary Cache

•	Response Time

•	SysStat Table

•	SysStat Table Delta

•	Chained Row

  Related Topics


Disk I/O

This event monitors the real time database physical I/O rate against the threshold values specified by the threshold arguments. If the number of occurrences exceeds the values specified, then a warning or alarm is generated.

Parameters:

•	Number of occurrences: Number of occurrences that I/O rate exceeds thresholds before an alert is generated.

•	Alert threshold: Threshold for alert.

•	Warning threshold: Threshold for warning.

Output: Current rate.

  Related Topics


Net I/O

This event monitors the SQL*Net I/O rate against the threshold values specified by the threshold arguments. If the number of occurrences exceeds the values specified, then a warning or alarm is generated.

Parameters:

•	Number of occurrences: Number of occurrences that I/O rate exceeds thresholds before an alert is generated.

•	Alert threshold: Threshold for alert.

•	Warning threshold: Threshold for warning.

Output: Current rate.

  Related Topics


Buffer Cache

This event monitors the buffer cache hit ratio against the threshold values specified by the threshold arguments. If the number of occurrences is below the values specified, then a warning or alarm is generated.

Parameters:

•	Number of occurrences: Number of occurrences that cache hit ratio is below thresholds before an alert is generated.

•	Alert threshold: Threshold for alert.

•	Warning threshold: Threshold for warning.

Output: Current ratio.

  Related Topics


Library Cache

This event monitors the library cache miss ratio against the threshold values specified by the threshold arguments. If the number of occurrences exceeds the values specified, then a warning or alarm is generated.

Parameters:

•	Number of occurrences: Number of occurrences that cache hit ratio exceeds thresholds before an alert is generated.

•	Alert threshold: Threshold for alert.

•	Warning threshold: Threshold for warning.

Output: Current ratio.

  Related Topics


Data Dictionary Cache

This event monitors the data dictionary cache miss ratio against the threshold values specified by the threshold arguments. If the number of occurrences exceeds the values specified, then a warning or alarm is generated.

Parameters:

•	Number of occurrences: Number of occurrences that cache miss ratio exceeds thresholds before an alert is generated.

•	Alert threshold: Threshold for alert.

•	Warning threshold: Threshold for warning.

Output: Current ratio.

  Related Topics


Response Time

This event checks for the response time of a user-provided application program. An alarm or warning will be generated if the response time (milliseconds) exceeds the threshold values specified in the arguments.

Parameters:

•	Command: Name of the user-provided program.

•	Parameters: Parameters for the user-provided program.

•	Number of occurrences: Number of occurrences that exceeds thresholds before an alert is generated.

•	Alert threshold: Threshold for alert.

•	Warning threshold: Threshold for warning.

Output: Response time.

  Related Topics


SysStat Table

You can monitor any system statistic available in the database with this event. An alarm or warning will be generated if the value of the selected V$SYSSTAT parameter exceeds the values specified by the threshold arguments.

Parameters:

•	Number of occurrences: Number of occurrences that exceeds thresholds before an alert is generated.

•	Alert threshold: Threshold for alert in seconds.

•	Warning threshold: Threshold for warning in seconds.

•	Parameter name: The name of the parameter in the V$SYSSTAT table that you want to monitor.

Output: Current value.

  Related Topics


SysStat Table Delta

You can monitor any system statistic available in the database with this event. The threshold values are compared to the difference between the last sample point and the current sample point of the V$SYSSTAT parameter. An alarm or warning will be generated if the calculated difference exceeds the values specified by the threshold arguments.

Parameters:

•	Number of occurrences: Number of occurrences that exceeds thresholds before an alert is generated.

•	Alert threshold: Threshold for alert in seconds.

•	Warning threshold: Threshold for warning in seconds.

•	Parameter: The name of the parameter in the V$SYSSTAT table that you want to monitor.

Output: Current value.

  Related Topics


Chained Row

This event monitor whether there are chained rows are found in the segments specified by the parameters. If chained rows are found, an alert is generated.

Parameters:

•	Segment name: Filter of the segment names to be monitored, or * for all segments. Examples of filter are “SYSTEM” and IN (“SYSTEM”, “TOOL”).

•	Segment owner: Filter of the segment owners to be monitored, or * for all owners. Owners “SYS” and “SYSTEM” are excluded.

•	Segment type: Filter of the segment types to be monitored, or * for all segment types. Only segment type “TABLE” and “CLUSTER” are allowed.

Output: The names of the segments that have chained rows.

Comment: This event may take a while to run and you may want to schedule the frequency for once a day at non-business hours.

  Related Topics


Node Events

Node events are divided into the following categories:

•	Fault Management events

•	UpDown (Node)

•	Space Management events

•	Disk Full

•	Swap Full

•	Performance Management events

•	CPU Load

•	CPU Utilization

•	Paging Rate

Note: All the Node events are supported on a Unix platform. For other platforms, see your platform-specific documentation.

  Related Topics


Node Fault Management Events

This category of events monitors for catastrophic conditions on the system. Immediate action needs to be taken by the administrator.

UpDown (Node)

This event checks whether a node is available.

Parameters: none

  Related Topics


Node Space Management Events

This category of events tracks possible space problems.

•	Disk Full

•	Swap Full

  Related Topics


Disk Full

This event checks for the space used by the disk specified by the Disk name parameter. If the free space available falls below the threshold values specified in the threshold arguments, then a warning or alarm is generated.

Parameters:

•	Disk name: Names of the disk to be monitored separated by a space, or * for all disks.

•	Alert threshold: Free space threshold in kilobytes for alert.

•	Warning threshold: Free space threshold in kilobytes for warning.

Output: Disk name and space available on the disk.

  Related Topics


Swap Full

This event checks for the space used by the swap space. If the space available falls below the threshold values specified in the threshold arguments, then a warning or alarm is generated.

Parameters:

•	Alert threshold: Free space threshold in kilobytes for alert.

•	Warning threshold: Free space threshold in kilobytes for warning.

Output: Space available.

  Related Topics


Node Performance Management Events

This category of event monitors the system for performance problems.

•	CPU Load

•	CPU Utilization

•	Paging Rate

  Related Topics


CPU Load

This event checks for the real time CPU load against the threshold values specified by the threshold arguments. If the number of occurrences exceeds the values specified, then a warning or alarm is generated.

Parameters:

•	Number of occurrences: Number of occurrences before an alert is generated.

•	Alert threshold: Alert threshold for alert.

•	Warning threshold: Warning threshold for warning.

Output: Current value.

  Related Topics


CPU Utilization

This event checks for the CPU utilization against the threshold values specified by the threshold arguments. If the number of occurrences exceeds the values specified, then a warning or alarm is generated.

Parameters:

•	Number of occurrences: Number of occurrences before an alert is generated.

•	Alert threshold: Alert threshold for alert.

•	Warning threshold: Warning threshold for warning.

Output: Current value.

  Related Topics


Paging Rate

This event checks the paging rate against the threshold values specified by the threshold arguments. If the number of occurrences exceeds the values specified, then a warning or alarm is generated.

Parameters:

•	Number of occurrences: Number of occurrences before an alert is generated.

•	Alert threshold: Alert threshold for alert.

•	Warning threshold: Warning threshold for warning.

Output: Current rate.

  Related Topics


Listener Events

The UpDown (Listener) event is in the fault management events category. This category of events monitors for catastrophic conditions on the system. Immediate action needs to be taken by the administrator.

Listener Fault Management Events

UpDown (Listener)

This event checks whether the listener on the node being monitored is available.

Parameters: none

Action: The Listener Startup job task can be set up as a fixit job for automatically correcting the problem. To avoid the fixit job executing when the listener was brought down intentionally, turn off the fixit job option temporarily.

  Related Topics


Map: Overview

The Map system allows you to create customized graphical views of network objects. You can modify and save these maps of your network environment. You can also create user-defined groups of network objects to help you organize the objects in the maps. With the Map customized views, you can manage and monitor a subset or group of objects in your system. You simply create a specific map comprised of databases, groups, listeners, names servers, and nodes that you need to monitor, then recall the map whenever you need to view it.

The topics about maps include:

•	The Map Window

•	The Map Menu

•	Expanding Objects in a Map

•	Creating Maps

•	Modifying Maps

•	Removing Maps

•	Example: Creating a Map

•	Creating Groups

•	Modifying Groups

•	Removing Groups

•	Example: Creating a Group

  Related Topics


Map Window

The Map window provides an area for constructing a graphical custom view of the network environment. The Map window can be hidden or shown by selecting Map Window in the Console View menu. You can also hide or show the window by clicking on the world icon in the Console toolbar.

You can launch a database tool using an object in the map. Select a database icon in the Map window, then select a DBA tool from the Tools Application menu. You are connected to the database according to the user credentials that have been set up for the system. For information on the user preferred credentials, see Preferred Credentials.

Map objects, such as nodes or databases, that are registered event destinations graphically display the status of the event for the object.

  Related Topics


Manipulating Map Views

Maps are created by dragging and dropping databases, groups, nodes, names servers, and listeners from the Navigator tree into the Map window. You can create, update, and save any number of maps. In addition, you can add a bitmap as a background to the map for visual identification or to graphically show the location of nodes. For example, you can use a map drawing of a city or state for the background of your map. Maps can be quickly displayed by selecting the map name from pull-down list in the Console toolbar or from the Show Map item in the Map menu.

You can create map views of subsets of nodes and services to be managed. Map views might be based on:

•	Functionality

•	Organizations

•	Geographic location

For example, the administrator who is responsible for the databases in the San Francisco office can construct a map view containing only those databases. The administrator responsible for the Human Resources department in Chicago can create another map view containing the subset of nodes in Chicago. The background of the maps can be set to a bitmap of either San Francisco or Chicago to help identify the map view.

You can also create user defined groups of network objects to further organize your network view.

  Related Topics


User-Defined Groups

User defined groups of network objects help organize your network view.

•	A group is a collection of similar objects such as databases, listeners, Names Servers, or nodes that share a common location or function.

•	A group can be added to a map view or another user-defined group.

•	A group is represented by a group icon and name. The icon represents the type of group, such as databases.

•	You can double-click on the group's icon to expand the group, and view and update the group's members and sub-groups.

•	Groups appear in the Navigator tree after they are created.

For example, you could create a group of databases called CHI_MAIL that contains the mail databases in Chicago. You could add this group to a map view that contains all the databases in the U.S. or you could add this group to a user-defined group of all databases in Chicago. Grouping nodes or services can simplify tasks that are applied to all members of the group. For example, in order to execute a SQL script on all the databases in the CHI_MAIL group, you can use the Job Scheduling services to schedule a job on the group. The job that executes the SQL script will be scheduled on all the databases in the group.

  Related Topics


Map Status Monitors

You can determine at a glance the status of an object or user-defined group on a map. If the object or group has been registered as an event destination, the state of the event condition is graphically displayed. Each object, such as a node or database, that is a registered destination displays a signal flag that graphically depicts the status of the event on the object. For more information on events, see Event Management.

•	If the flag signal is green, there are no problems on the objects that are monitored.

•	If the flag is yellow, there is a condition detected that should be checked.

•	If the flag is red, there is a severe problem detected by an event and the object requires immediate attention.

•	If the object or group is down or unavailable, the object displays a circle with a slash through it. The icon only displays if the UpDown event registered to the object or group.

•	If there is no icon, then the object in not being monitored.

User-defined groups inherit the worst state of any of the members. If one service in a group is down, the group displays a circle with a slash through it.

Note: For status monitors to display on a map object, an agent must be servicing the object.

  Related Topics


Expanding Objects in a Map

All objects in a map can be expanded by double-clicking on the object's icon. You can double-click on some objects to open property sheets. The property sheets allow you to both view and alter the definitions of the objects.

•	You can double-click on databases to display property sheets.

•	You can double-click on a node or user-defined group to expand the object and display the contents of the node or group.

For information about dialog boxes and property sheets, see Property Sheets and Dialog Boxes.

Groups

When you double-click on a group icon, the group expands to display the objects in the group. You can drag and drop objects from the Map, the Navigator tree, and other groups to add them to the group. You can delete objects by selecting them and pressing the Delete key.

Nodes

When you double-click on a node icon, the node expands to display the databases, listeners, and names servers on the node.

Note: The objects cannot be altered in the expanded node window.

Databases

When you double-click on a database, the database instance property sheet displays. If the connection to the database fails for any reason, the Login Information dialog box displays.

For information on the user preferred credentials, see Preferred Credentials. For information about connecting to an instance of a database, see Entering Login Information.

The database instance property sheet contains the Status, Startup, and Shutdown pages. You cannot start up or shut down a database instance unless you have connected to the database as SYSDBA or SYSOPER.

For information on the database instance property sheet, see Instance Manager.

  Related Topics


Listener/Name Server Property Sheet

Note: Listener and Names Servers property sheets are not available with this release.

  Related Topics


Map Menu

The Map menu allows you to customize and manage network views. You can create, save, modify, and remove maps and user-defined groups.

Map menu options allow you to:

•	Create, Modify, Remove, Save, and Show Maps

•	Create, Modify, and Remove Groups

•	Remove selected items in the Map window

Remove Selection

Deletes the selected item from the map window. You can also delete an object from the current map or group by selecting the object and pressing the Delete key.

  Related Topics


Map Create, Modify, Remove, Save, and Show Maps Menu Options

These menu options allow you to create, modify, remove, save, and show maps.

Create Map

Creates a new map with the name you enter. See Creating Maps.

Modify Map

Changes the bitmap used as the background of a map. See Modifying Maps.

Remove Map

Deletes an existing map from the current repository. See Removing Maps.

Show Map

Displays a list of saved maps for your selection. Select a map from the list to display it in the Map window. You can also select a map from the Map pull-down list in the console toolbar.

Save Map As

Saves the current map with the name you enter. Enter a name in the Map Name field of the Save Map As dialog box and click OK. You can also select a map name in the Existing Maps list and click OK. The maps are stored in the repository.

Note: If the map has been updated but not saved, you are prompted to save when you select Create Map from the Map menu or Exit from the File menu.

  Related Topics


Map Create, Modify, and Remove Groups Menu Options

These menu options allow you to create, modify, and remove groups.

Create Group

Adds a new group to the current map or a selected group. See Creating Groups.

Modify Group

Changes the bitmap used as the background of a group. See Modifying Groups.

Remove Groups

Removes an existing group from the current map or group, or deletes the group from the entire system. See Removing Groups.

  Related Topics


Creating Maps

To create a new map:

1.	Select the Create Map menu item to display the Create a New Map dialog box.

2.	Enter a name in the Map Name field.

3.	Check the Use Background Bitmap box if you want to add a bitmap to the background of the map. If you check the box, enter the name of the bitmap file in the Bitmap File field or click the Browse button to locate the file with the standard Windows file selection dialog box. When a bitmap is added to a map, the bitmap is stored in the database repository.

Note: If you check the box and do not enter the name of the bitmap file in the Bitmap File field, no bitmap will be used.

4.	Click the OK button when you have finished entering a filename or an optional bitmap filename.

See Example: Creating a Map.

Adding or Deleting Objects in a Map

To add or delete objects in the map:

1.	Drag and drop databases, groups, listeners, nodes, and objects in expanded groups from the Navigator tree to add the object in the map window. Only one instance of an item can exist on a map or group.

2.	Select objects in the map and press the Delete key to remove objects from the map. You can also select an item and choose the Remove Selection menu option.

The map is automatically saved when you close the map. You can also select the Save Map As menu option to save the new map.

  Related Topics


Modifying Maps

To change the bitmap background of a map:

1.	Select the Modify Map menu item to display the Modify Map dialog box.

2.	Enter a name in the Map Name field. If an existing map is displayed, the name of the map is automatically entered in the Map Name field. The name cannot be modified.

3.	Determine whether you want a bitmap background for the map.

a.	Click on the empty Use Background Bitmap box if you want to add a bitmap to the background of the map. After you check the box, enter the name of an existing bitmap file in the Bitmap File field or click the Browse button to locate the file with the standard Windows file selection dialog box.

b.	If the box already has a check and you want to change the bitmap, enter a new name in the Bitmap File field or click the Browse button to locate the file with the standard Windows file selection dialog box.

c.	If the box already has a check and you want to remove the bitmap background, click on the box to remove the check the box and the bitmap from the map.

4.	Click the OK button when you have finished entering an optional bitmap filename.

  Related Topics


Removing Maps

To delete an existing map from the current database repository:

1.	Select the Remove Map menu item to display the Remove Map dialog box.

2.	Select the map you want to remove from the map names in the Existing Maps list.

3.	Click the OK button.

Note: Groups that are displayed on the removed map are not dropped from the system. The groups remain in the Navigator tree.

  Related Topics


Example: Creating a Map

The following example illustrates how to create a new map.

1.	Select Create Map from the Map menu to create a new map.

2.	Enter a name for the new map.

3.	Check the Use Background Bitmap box to add a bitmap to the background. Enter a bitmap name in the Bitmap File field or click on the Browse button to locate the bitmap filename.

4.	Click on the OK button to create the new map with a bitmap background.

5.	Expand the Databases branch of the Navigator tree.

6.	Drag and drop several databases from the tree into the Map window.

7.	Expand the Nodes branch of the Navigator tree.

8.	Drag and drop several nodes from the tree into the Map window.

9.	Double-click on a node icon in the map to open the node window and view the contents. A node may contain databases, listeners, and names servers.

10.	Close (Alt-F4) the node window when you are finished viewing the contents.

11.	Any updates made to a map are saved automatically. If you want to make a revised map but keep the original:

a.	Select Save Map As from the Map menu.

b.	Enter a new name for the updated map.

c.	Make updates to the map.

Maps are listed in the pull-down map list and in the Show Map option of the Map menu.

  Related Topics


Creating Groups

To create a new group in the current map or group:

1.	Select the Create Group menu item to display the Create a Group dialog box.

2.	Enter a name for the new group in the Group Name field of the dialog box.

3.	Select the group type from the pull-down list. The group types are Database, Listeners, Names server, and Node.

4.	Check the Use Background Bitmap box if you want to add a bitmap to the background of the group. If you check the box, enter the name of the bitmap file in the Bitmap File field or click the Browse button to locate the file with the standard Windows file selection dialog box. When a bitmap is added to a group, the bitmap is stored in the database repository.

Note: If you check the box and do not enter the name of the bitmap file in the Bitmap File field, no bitmap will be used.

5.	Click the OK button to save the group.

The new group icon appears in the current map and is empty. You need to add objects to the group. The new group can be added to other maps and groups. To add an existing group to the current map or another group, drag and drop the group from the Navigator tree or a different group into the map or group window to add the object.

See Example: Creating a Group.

Creating a Group with the Navigator

To create a new group in the Navigator tree:

1.	Select an existing group or one of the Group type folders with the right mouse button.

2.	Choose the Create menu option.

3.	Follow the steps listed for creating a group. Note that the group type has been determined by the group type selected in the Navigator and cannot be changed.

Adding or Deleting Objects in a Group

To add or delete objects in a group window:

1.	Double-click on a group icon in a map to expand the group.

2.	Drag and drop groups, nodes, listeners, names servers, or databases from the Navigator tree, the current map, or a different group into the group window to add the object to the group.

Note: Only one instance of an item can exist in the group. The objects must be of the group type.

3.	Select an object in the group and press the Delete key to delete an object from a group.

Note: When you add or delete objects in a group, the updates are reflected in every occurrence of the group. Any updates to a group are automatically saved as the updates are made.

To add or delete objects from a group in the Navigator tree:

1.	Drag and drop groups, nodes, listeners, names servers, or databases from the Navigator tree, or a different group into the group folder to add the object to the group.

2.	Expand the group in the tree. Select an object in the group and press the Delete key to delete an object from a group. You can also choose the Remove from Group option in the Navigator menu.

  Related Topics


Modifying Groups

To modify the bitmap background of a group:

1.	Select a group in the map window.

2.	Select the Modify Group menu item to display the Modify Group dialog box. The name of the group is automatically entered in the name field. The name cannot be modified.

3.	Determine whether you want a bitmap background for the group.

a.	Click on the empty Use Background Bitmap box if you want to add a bitmap to the background of the group. After you check the box, enter the name of an existing bitmap file in the Bitmap File field or click the Browse button to locate the file with the standard Windows file selection dialog box.

b.	f the box already has a check and you want to change the bitmap, enter a new name in the Bitmap File field or click the Browse button to locate the file with the standard Windows file selection dialog box.

c.	If the box already has a check and you want to remove the bitmap background, click on the box to remove the check the box and the bitmap from the group.

4.	Click the OK button when you have finished entering an optional bitmap filename.

  Related Topics


Removing Groups

To remove a group from the current map or group, or from the entire system:

1.	Select the Remove Groups menu item to display the Remove Groups dialog box.

2.	Select the radio button for deleting the group from the current map or group, or from the system.

Note: If you remove a group from the current map or group, you can add the group again at a later time. If you remove the group from the system, the group is deleted from database repository and must be created again.

3.	Select the group names from the list and click the OK button. You can select multiple groups.

Additional methods for removing groups are:

•	Select the group in the map window and press the Delete key, or choose Remove Selection from the Map menu. The group is removed from the group or map but still exists in the system.

•	Select the group in the Navigator tree using the right mouse button and choose the Remove menu option. When you delete a group from another group, the group is only removed from the parent group and is not removed from the system. When you delete a group from a group folder, the group is removed from the entire system.

  Related Topics


Example: Creating a Group

The following example illustrates how to create a new user-defined map group.

1.	Use the Show Map menu item or the pull-down list of maps to select the map where you want to add the new group.

2.	Select Create Group from the Map menu to display the Create a Group dialog box.

3.	Enter a name for new group in the Group Name field.

4.	Select Database Group from the Group Type pull-down list. This is the default and should already be selected.

5.	Check the Use Background Bitmap box to add a bitmap to the background. Enter a bitmap name in the Bitmap File field or click on the Browse button to locate the bitmap filename.

6.	Click on the OK button to create the new group. An icon for the new group appears in the current map.

7.	Double-click on the new group icon in the map to open the group window.

8.	Expand the Databases branch of the Navigator tree.

9.	Drag and drop several databases into the group window.

10.	Double-click on one of the database icons to display the property sheet. You may have to enter login information to access the database. For information about connecting to an instance of a database, see Entering Login Information.

11.	Click OK to close the database property sheet when you are finished viewing the pages.

12.	Close (Alt-F4) the group window. The updates to the group are saved.

The new group can be added to other maps or groups by dragging and dropping the group from the Navigator tree.

  Related Topics


Intelligent Agents and Communication Daemon: Overview

The Oracle Enterprise Manager Console works with Intelligent Agents and a Communication Daemon to gather information about the network environment, communicate with network objects, and manage jobs and events. The Daemon Manager administers communication between the agent and daemon. Topics discussed in this section include:

•	Intelligent Agents

•	Communication Daemon

•	Daemon Manager

  Related Topics


Intelligent Agents

The agents are intelligent processes running on remote nodes in the network. An agent is installed on the same node as the service it supports. However, the agent can support more than one service on a particular node. For example, if two databases are installed on one machine, a single agent can support both databases. The agents are responsible for:

•	Accepting jobs or events from the Console or other third-party applications.

•	Canceling jobs or events as directed by the Console or other applications.

•	Running jobs, collecting their results and output, and queueing them for the communication daemon.

•	Checking for events, and queueing the resulting event reports for the Communication Daemon.

•	Returning job and event reports to the appropriate communication daemon.

•	Handling Simple Network Management Protocol (SNMP) requests, if SNMP is supported on the agent's platform.

Using Tcl scripts submitted as jobs or events, you can program an agent to perform a task or to detect problems. By submitting a fixit job along with an event registration, you can also program an agent to correct a problem when it is detected.

Characteristics

Agents are autonomous because they can function without requiring that the console or daemon be running. An agent that services a database can run without the database being up, allowing the agent to start up or shut down the database.

The Intelligent Agents can independently perform administrative tasks or jobs at any time, without active participation by the administrator. Similarly, the agents can autonomously detect and react to events, allowing them to monitor the system and execute a fixit job to correct problems without the intervention of the administrator.

The agents operate independently of the Console, allowing them to execute jobs and monitor events even when the administrator has logged out of the Console. The agents queue any job or event messages destined for that administrator, and deliver them when the administrator logs in to a Console again. Information about jobs and events are stored in flat files on the agent's node. These files have a ".q" extension. On a Windows platform theyare stored in the $ORACLE_HOME\network\agent directory.

Note: The agent queues a maximum of 500 messages. After the limit is reached, the oldest messages are dropped.

Network Encryption

Network encryption can be accomplished with the Secure Network Services option of SQL*Net. The Secure Network Services (SNS) option uses a sophisticated algorithm to provide strong encryption on TNS connections. When the agent supports direct TCP/IP connections, as an option instead of TNS, SNS features will still be accessible. For information on SNS, see Secure Network Services Administrator’s Guide.

  Related Topics


SNMP Support

The agents support SNMP, so applications can communicate directly with the agent using SNMP protocol. The agents provide access to Oracle's database Management Information Base (MIB) variables.

Although the agent supports SNMP, the communication daemon does not use that protocol to communicate with the agent. You can submit jobs or events that access Oracle MIB variables even when the database resides on a platform that does not support SNMP.

  Related Topics


Agent Event and Job Support

The agents are responsible for executing jobs and monitoring for events. Jobs and events are implemented as Tcl scripts. When the agent executes a job or tests for an event, it runs the appropriate Tcl script.Because jobs can be long-running or complicated tasks, such as a database backup job, the agent does not execute the job in its process space. Jobs are run in a separate process. When the job is completed, the agent sends the results to the communication daemon. In contrast, event scripts are typically run directly by the agent. Event scripts are used for detecting exceptions and are expected to have short execution times.

When the daemon sends a message to an agent on behalf of an administrator logged into the Console, the daemon sends the agent information about the administrator's language and character set environment. The agent uses the NLS environment information when it performs database administration tasks on behalf of the administrator. This allows administrators to manage databases in their native languages. For example, an administrator in France can administer a database in Germany and receive messages in French.

  Related Topics


Installing the Agent

An agent must be installed on the same node as the database that the agent services. For information on installing and configuring the agent, see the Oracle Enterprise Manager Installation Guide or the Oracle server platform-specific installation documentation or readme file for your system.

For more information on SNMP, see the Oracle Network Manager Administrator's Guide, Oracle SNMP Support Reference Guide, and Oracle Network Products Messages Manual.

  Related Topics


Communication Daemon

The Communication Daemon is a process that runs with the Console on the client machine. There is one communication daemon for each Console. The Communication Daemon is responsible for:

•	Communicating with agents on nodes to schedule and manage jobs.

•	Communicating with agents on nodes to submit and monitor events.

•	Queueing operations that fail and retrying them periodically.

•	Discovering the SQL*Net services in the system.

•	Contacting nodes periodically to determine if they are up.

•	Maintaining a cache of connections to agents on nodes.

The Communication Daemon is implemented as a multi-threaded process. For example, separate threads in the daemon perform activities such as submitting jobs and events to agents, discovering new services in the network, or receiving messages from agents. Because the daemon's threads operate independently, the daemon can perform various operations simultaneously and perform efficiently in large busy distributed environments.

Communication between the daemon and the agents is vital to the Job and Event systems. The daemon must be able to send messages to the agents in order to submit jobs and events. The agents must be able to send messages to the daemon to report results and status messages for the jobs and events.

Note: Job Scheduling and Event Management rely on communication between the Console, agent, and daemon, and require SQL* Net V2.3, which is included with the Oracle Enterprise Manager product.

The daemon and agents communicate using Oracle Remote Operations, which is a remote procedure call mechanism based on the Transparent Network Substrate (TNS). The daemon and agents can also use Oracle Secure Network Services (SNS) to maintain the security of their network transmissions. The daemon can communicate with any agent in the system, regardless of the different protocols used in the distributed environment.

  Related Topics


Message Queues

The daemon and agents use message queues for the messages they send. Using queues ensures that no messages are lost even when the communication daemon or agent is down. The daemon maintains several queues for messages. The operations queue contains job and event requests sent by the Console. For example, when you submit a new job to the Job system, the Console queues the new job request on the daemon's operations queue.

Failed Queue

When the daemon retrieves a job or event request from its operation queue, it tries to contact the agent that should receive the request. If it cannot contact the agent, the daemon places the request in its failed queue. Periodically the daemon tries to contact the agent which is responsible for the operation request in the failed queue. If the daemon successfully contacts the agent, the operation request is removed from the failed queue and sent to the responsible agent.

Notification Queue

The daemon maintains a notification queue for job and event notification. The notification queue contains messages about the status of jobs and events. When the daemon receives a message from an agent regarding a job or event, it places the message in the notification queue. When the daemon changes the status of a job or event it also places a message in the queue.

For example, when the daemon has successfully submitted a new job to an agent, it places a message in the notification queue updating the job's status to submitted. Messages in the notification queue are used to update the job and event information stored in the repository.

  Related Topics


Connection Cache

In order for a daemon and an agent to pass messages, they must establish a connection. Rather than requiring that the daemon or agent create a new connection each time it wants to send a message, the daemon maintains a cache of connections. If a connection is needed and it already exists in the cache, it can be reused. This reduces the overhead involved in creating new connections. Connections in the cache are aged out using a least recently used algorithm.

  Related Topics


Daemon Manager

The Oracle Daemon Manager allows you to manage communication between the Console's Communication Daemon and Intelligent Agents. The Daemon Manager provides a menu for performing administration tasks and a tree structure for viewing:

•	Agent Pending Operations

•	Agent Pending Notification queries

•	Monitored Nodes

•	Daemon Configuration Parameters

•	Setting Daemon Parameters

•	Daemon Manager Menu

Note: If you launch the Daemon Manager when Oracle Enterprise Manager is not running, you can only configure the parameter settings.

Agent Pending Operations

The Agent Pending Operations folder lists the nodes that have pending job or event operations that have not been delivered to the agent. When viewing this folder, a multi-column list displays on the right side of the screen. The list identifies the node name, the last contact, the last connect attempted, and the number of job and event operations for each node. The nodes are listed in the following folders:

•	Job Operations

•	Event Operations

Application Pending Notifications

The Application Pending Notifications folder lists the third-party applications and users that have pending job or event notifications that have not been delivered to the agent. When viewing this folder, a multi-column list displays on the right side of the screen. The list identifies the username, application, and number of job and event notifications for each application. The applications and users are listed in the following folders:

•	Job Notifications

•	Event Notifications

Monitored Nodes

The Monitored Nodes folder lists the nodes that are being monitored for the UpDown event. When viewing this folder, a multi-column list displays on the right side of the screen. The list identifies the node name, the last contact, and the last connect attempted for each node. If you select a specific node in the tree, additional information identifies the application and user for that node.

  Related Topics


Daemon Configuration Parameters

The communication daemon parameters and settings are viewed and updated with Oracle Daemon Manager. The defaults are usually sufficient to run OEMGR. The parameters for the communication daemon include:

Listening Address

The address of the listener. The setting must be a valid TNS address. If this address is set, the daemon uses this address and the TCP/IP Port setting is ignored. This parameter should only be set if you want to use a protocol other than TCP/IP, such as the SPX protocol.

Note: When entering an address, make sure you are using a valid TNS address. For more information, see the Oracle Network Manager Administrator's Guide.

TCP/IP Port

The TCP/IP port that the daemon listens on. If the Listening Address parameter is not set, the daemon listens using TCP/IP with this port setting. The default is 7770. If an error message displays regarding “failed to listen for incoming requests”, you may to need change the default value.

Number of Cached Connections

The number of open connections to agents. The default is 5 connections.

Networking Polling Timer

The frequency that the daemon checks for incoming data from an agent. The default is 3 seconds.

Service Discovery Timer

Frequency that the daemon queries for additional services that have been added to the network. The default is 1800 seconds.

Node Heartbeat Timer

Frequency that the daemon checks to see if a node is up. This applies to nodes registered with the UpDown event. The default is 60 seconds.

Node Heartbeat Interval

Frequency that the daemon checks if a node is up after the node has been determined to be up and working. This can be set to a different value than the Node Heartbeat Timer so that a working node is checked ata a less frequent interval. The default is 60 seconds.

Operation Retry Timer

Frequency that the daemon retries any failed operation. The default is 60 seconds.

Number of Worker Threads

The number of threads available. This setting should match the connection cache. The default is 5.

Register User at Startup

Determines whether the user is registered at the computer where OEMGR is started. If set to 1, the user is registered at the machine where OEMGR is started. If set to 0, the registration is ignored. The default is 1.

  Related Topics


Setting Daemon Parameters

To view and update the parameters and settings:

1.	Select Configuration Parameters in the Daemon Manager tree on the left side of the screen to view the parameters and settings. The parameters are displayed on the right side of the screen. Usually, the default settings are sufficient.

2.	Double-click on a parameter listed on the right side of the screen to display a dialog box that allows you to update the parameter setting.

3.	Enter a new setting value in the dialog box. You can also:

a.	Click on the Default button to enter the default value.

b.	If a Listening Address has been entered, click on the Remove button to remove the address.

4.	Click on the Set button to save the value or click on the Cancel button to exit the dialog box without changing the parameter setting.

Note: A new parameter setting is used the next time Oracle Enterprise Manager is executed.

Attention: You need to have permission to update the NT registry in order to change the parameters.

  Related Topics


Daemon Manager Menu

The menu options of the Oracle Daemon Manager are:

File menu

Exit

Exits the Daemon Manager.

Edit menu

Delete

Deletes the selected operation from the tree and the daemon queue. Also notifies the Console of the change. When problems persist with a job or event operation, the Console and agent may be out of sync. This can happen due to data corruption or the accidental deletion of files. The Delete option allows you to remove the operation from the repository. You may also need to delete the operation in the files that the agent maintains on the node where the agent is running. On a Windows platform, those files are stored in the $ORACLE_HOME\network\agent directory and have a ".q" extension. The agent must be shut down and all the ".q" files must be deleted. This removes all the jobs and events from that node.

Control menu

Force Service Discovery

Forces the daemon to check for the current network objects.

Force Operation Retry

Forces the retry of operations for all nodes. This is useful if the Console machine has been disconnected or if you are dialing into the network at intervals.

Force Node Heartbeating

Forces the daemon to monitor (heartbeat) the nodes to see if they are up.

Node menu

Ping

Pings the monitored node to check whether the agent on the node is running.

Help menu

Contents

Displays the overview topic of help.

About...

Displays version information about the program.

  Related Topics


Database Administration Tools and Utilities

The database tool and utility applications are the primary administrative components of Oracle Enterprise Manager. You can use these applications to perform most of your DBA administration tasks. The tools and utilities include:

•	Backup Manager

•	Data Manager

•	Instance Manager

•	Security Manager

•	Server Manager Line Mode

•	Schema Manager

•	Software Manager

•	SQL Worksheet

•	Storage Manager

You can launch these tools through separate applications in the Console Tools menu or launch palette on objects selected in the Navigator or Map. Some of the functions of these applications can also be performed from the Navigator; however, the full set of functions is accessed through each application.

If you want to run tasks on a specific group of objects, such as users, you would launch the Security application which provides complete task-oriented administration of the user objects. If you just wanted to alter an object, such as the user SCOTT or the tablespace TABLE1, you could usually run that task from the Navigator.

Note: To view a list of the help topics, click on the Help_Topics button in the menu bar at the top of this window.

  Related Topics

  How to ...


Application Features

The design of the applications allows you to:

•	Use the graphical interface to execute the commands quickly and conveniently by pointing and clicking with the mouse rather than manually entering the SQL commands to perform these tasks.

•	Concurrently perform multiple tasks in multiple Oracle Enterprise Manager windows.

•	Administer multiple databases simultaneously in multiple windows.

•	Centralize database administration tasks for both local and remote databases running on any Oracle platform in any location worldwide. In addition, these Oracle platforms can be connected by any network protocols supported by SQL*Net and the MultiProtocol Interchange.

•	Perform DBA administrative tasks using Oracle Enterprise Manager's line mode interface when a graphical user interface is unavailable or undesirable. The line mode option is available on all platforms.

The applications allow you to perform the following database administration tasks:

•	Manage instances, initialization parameters, and sessions

•	Manage schema objects

•	Control security

•	Manage storage

•	Enter and execute SQL statements, PL/SQL code, and Oracle Enterprise Manager DBA commands

•	Back up, recover, and restore a database

•	Export and import data from an Oracle database

Additional applications can be purchased to allow you to:

•	Diagnose your database system

•	Manage a replication environment

  Related Topics


Application Objects

This section provides an overview of the objects administered by the database tools and utilities and briefly describes the objects that each application manages. For detailed descriptions of the objects and commands available in each application, see the specific chapter on the application.

Types of Objects

The database tools and utilities applications provide a tree list of groups and instances to organize the objects associated with the application. The tree list displays on the left side of an application window after the application has successfully connected to a database.

The groups and instances are usually contained in a database container. The database container is the root of the tree list and displays the name of the database that the application is connected to.

Containers hold other objects and display a '+' or '-' to the left of the object's icon and name. A container can be expanded or collapsed to show or hide its contents. Objects that do not contain other objects do not display a '+' or '-' to the left of the object's icon or name.

•	A group is a container that holds a group of specific object types and is identified with a folder icon. For example, a Users group contains only users.

•	A composite or expandable instance is container that consists of various objects. For example, the user SCOTT is a composite instance that consists of the system privileges, object privileges, and roles that have been granted to SCOTT. Composite instances have property sheets that can be edited.

•	A simple instance is a single object that does not contain other objects. For example, a system privilege, such as ALTER TABLESPACE, is an instance and does not contain any objects.

  Related Topics


Manipulating Tree Objects

When navigating in the tree list, you can:

•	Click on the '+' to the left of an icon to expandand display the contents of a container. You can also double-click on a collapsed container icon or name.

•	Click on the '-' to the left of an icon to collapse a container. You can also double-click on an expanded container icon or name.

Suggestion: For the fastest performance when expanding or collapsing containers in the tree list, click only on the '+' or '-' to the left of the container rather than double-clicking an object name. If you select an object in the tree list, the application pauses to refresh the contents of the window on the right side before expanding or collapsing the container.

•	Select the Collapse and Expand menu options in the View menu to collapse and expand containers.

•	Click on a group name, such as Users or Tablespaces, to display a multi-columnscrolling list of summary information on the objects in the container in the right side of the application window.

•	Click on a composite instance, such as the SYSTEM tablespace or the user SCOTT, to display the Alter property sheet for the object. Menu commands are also enabled for the group you selected.

Attention: If you alter an instance, such as a datafile named DATA1 or a role named CLERK, in any location of the tree list, all occurrences of the object in the tree are changed.

•	Drag and drop an object onto a container to assign the object to the container. For example, you can drag and drop a role named CLERK onto the user named SCOTT to grant the CLERK role to SCOTT.

  Related Topics


Application Menus

Database tools and utilities applications include several main pull-down menus in the menu bar:

•	File menu

•	Edit menu

•	View menu

•	Log menu

•	Help menu

The applications include other menus that are specific to the groups that the application manages. For example, the Security Manager provides the User, Profile, and Role menus in addition to the standard menus.

When a menu item is dimmed, it is not currently available. Menu items that end with an ellipsis (...) indicate that you will be asked to enter more information to complete the command.

Context-Sensitive Menus

Context-sensitive menusmay also be provided when you select an tree list object or item in the multi-column list with the right mouse button. This feature provides quick access to a subset of the menu options provided in the menu bars. Normally, objects in an application tree list (or the console Navigator) and objects in a multi-column list have associated context-sensitive menus.

  Related Topics


File Menu

The File menu items allow you to open or close application windows and create new connections. The File menu includes:

Change Database Connection

Displays the Connect dialog box to connect to an instance and open a window for that database. See Entering Login Information. To connect to multiple databases concurrently, you need to launch the application multiple times from the console.

Enable Roles

Choose a role from the multi-column list of available roles.

Exit

Exits the application.

  Related Topics


Enable Roles

Use the Enable Roles option to select the roles you want to use when administering the database. You can select all the roles available or choose a specific role.

  Related Topics


Edit Menu

The Edit menu contains the standard editing menu items. These commands are useful when editing text in the SQL Worksheet. These editing capabilities may also be available for use in property sheets and dialog boxes, although sometimes via keyboard equivalents only.

Undo/Redo

Cancels the last action or performs the last action again on selected text.

Warning: The Undo menu item, when available, undoes the last edit you performed on the text. It does not undo the last operation performed on the database you are administering.

Cut

Cuts selected text.

Copy

Copies selected text.

Paste

Pastes selected text at the location of the cursor.

Select All

Selects all the text in a document or selects all objects in a list.

Clear All

Clears all text in a window.

Applications may contain the following additional menu items:

Preferences

Allows you to determine various settings for the application interface.

  Related Topics


View Menu

The View menu allows you to show or hide objects, such as the toolbar or status line, and expand, collapse, or refresh the tree list.

Refresh

Refreshes the tree list. This command is useful when other database administrators are making changes to the objects you are viewing, or when you are making changes in a different window, such as a SQL Worksheet.

Filter Folder

Filters the tree list based on criteria you choose. This allows you to display only the objects that match the criteria.

Expand One Level

Opens and displays the next level of items contained in the selected objects in the tree. Expanding a container can be delayed because the objects displayed in the listing are often queries on remote databases.

Collapse Branch

Closes the selected container in the tree list.

Collapse All

Closes all open containers in the tree list.

Toolbar

Shows or hides the toolbar.

Status bar

Shows or hides the status bar.

Advanced Mode

Displays additional property sheets that allow you to access an application’s advanced database administration features.

  Related Topics


Log Menu

The Log menu options allow you to record and save the SQL statements that you have executed. When you save the statements to a file, you can also choose to schedule a job using the file on multiple databases. This feature provides the ability to perform identical actions on multiple databases without having to enter each SQL statement over again. If the databases are not identical, you can simply edit the SQL statements in the file before running the file on a database.

Record

Start recording the SQL statements that are executed through the application.

Stop

Stop recording SQL statements.

A dialog displays for you to save the recorded statements in a file. Enter a filename for the file. You can schedule a job that would run the file of SQL statements.

Pause

Pause the recording of statements while you execute actions that you do not want recorded.

  Related Topics


Help Menu

From the Help menu, you can access the Oracle Enterprise Manager online Help system. For more information about Oracle Enterprise Manager online Help system, see Online Help.

Contents

Displays the overview page for Oracle Enterprise Manager help.

Search for help on

Displays a search dialog box. You can either search by index or key word.

Using Help

Displays a dialog box containing information about the Help system. See Using Help for information about the Help dialog box.

About Application

Displays a dialog box containing version information about the application.

Additional Menus

Most database tool and utility applications include pull-down menus that contain the commands available for specific groups. The menu titles usually match the names of the groups. For example, the Security application provides the User, Profile, and Role menus.

Some of the menu commands, such as Drop, require that you selectan individual object first. These commands are unavailable until you select an appropriate object. Unavailable commands are represented by dimmed menu items. Other menu items, such as Create, do not require an object selection and are never dimmed.

A menu item can be dimmed even when an object is selected because the command does not apply to that particular object. For example, you cannot drop an object type group, such as the Users group.

Some menu items are followed by an ellipsis (...). This indicates that to complete the command, the application prompts you for more information with a dialog box or property sheet.

Attention: Context-sensitive menusmay also be provided when you select an object with the right mouse button. This feature provides quick access to a subset of the menu options provided in the menu bars.

For detailed information about the application menus, see the chapters on the specific applications.

  Related Topics!ALink(OEMGR database tools;dbappmenus;OEMGR DBA Commands)


Using Spreadsheets

Some property sheet, particularly those requiring large amounts of data, use spreadsheets for simplified data entry. Spreadsheets consist of a table in which data is typed directly into rows and categorized by columns. Some entry fields in the spreadsheet have predefined content and are toggled by clicking on the table cell with the left mouse button.

For most spreadsheets, context-sensitive menus are available. After selecting a single row using the left mouse button, clicking the right mouse button calls up a context-sensitive menu that is appropriate for a particular application.

Newly added rows are indicated by a plus ‘+’ sign in the far left column of the spreadsheet until you click Apply.

  Related Topics!ALink(OEMGR database tools;dbappmenus;OEMGR DBA Commands)


Storage Manager

With Oracle Storage Manager you can perform administrative tasks associated with managing database storage. These tasks include managing tablespaces and rollback segments, and adding and renaming datafiles. You can also launch other database tools and utilities from the application. Storage Manager displays a tree listing and multi-column lists to allow you to manipulate and view objects. Storage Manager manages datafiles, rollback segments, and tablespaces with the following menus:

•	Datafile menu

•	Rollback menu

•	Tablespace menu

  Related Topics


Datafile Menu Options

When you select the Datafiles container or a datafile in the container, various menu options in the Datafile menu are enabled. Depending on what objects are selected in the tree list, the Datafile menu allows you to perform the following operations:

•	Create to create a new datafile.

•	Create Like to create a new datafile based on an existing datafile.

•	Place Online to place a datafile online.

•	Take Offline to take a datafile Offline.

  Related Topics


Datafile Property Sheet: General Page

The General page of the Datafile property sheet allows you to modify existing datafile parameters or create a new datafile when the Create menu option is selected from the Datafile menu.

Note: When altering a tablespace, the fields on this page cannot be modified if the datafile belongs to a read-only tablespace.

Name

Name of the datafile to be created. Enter the file and path name of the new datafile. The filename must be specified according to the conventions of your operating system. When altering an existing datafile, you can rename the datafile by typing in a new name.

Attention: You must rename a datafile if you have changed the name of the corresponding operating system file or if you have moved the file to a new location. To rename a datafile, its tablespace must be offline.

Attention: When you rename a datafile using the Storage application, the name of the operating system file is not changed. The new filename is only associated with the tablespace. Before renaming the datafile using the Storage application, you must change the name of the file through your operating system.

Tablespace

Name of the tablespace to which the new datafile belongs. Use the drop-down list to choose the tablespace. You can only choose the tablespace when the datafile is created.

Status

Online: Specifies that the datafile be placed online.

Offline: Specifies that the datafile be place offline.

Note: When adding a datafile to either a new or existing tablespace, the Online and Offline option will be disabled.

Note: When altering a tablespace, the fields on this page cannot be modified if the datafile belongs to a read-only tablespace.

To determine the file size, select either the Use Existing File or New File Size option.

Size

File Size

Allows you to designate the file size of a new or existing file. Enter the size of the new or existing datafile. Use the unit buttons to specify either kilobytes or megabytes.

Reuse Existing File

Designates that the datafile already exists and should be reused.

  Related Topics


Datafile Property Sheet: AutoExtend Page

The AutoExtend page (available in Advanced UI mode) sets the Auto Extend feature for a datafile used in a database that is version 7.2 or later. The page consists of the following:

Note: If the datafile belongs to a read-only tablespace, all the fields on this page are disabled.

Enable Auto Extend

Determines whether the Auto Extend feature is enabled or disabled. Disabled is the default setting. If the box is not checked, the other fields on the page are disabled.

Increment

Determines the size and units of the increment size.

Maximum Extent

Unlimited:  Sets the maximum extent size to Unlimited. This option is specified by default.

Value:  Allows you to specify the maximum extent size and units.

  Related Topics


Rollback Menu Options

The Rollback Segment menu allows you to perform the following operations:

•	Create to create a new rollback segment.

•	Create Like to create a new rollback segment based on an existing rollback segment.

•	Remove an existing rollback segment.

•	Shrink an existing rollback segment (7.2 or later Oracle databases)

•	Place Online to place a rollback segment online.

•	Take Offline to take a rollback segment offline.

These menu options are enabled depending on the object selected in the tree list.

  Related Topics


Create Rollback Segment: General Page

The General page of the Create Rollback Segment property sheet is described below:

Name

Name of the rollback segment to be created. Enter the name of the new rollback segment. The rollback segment name can only contain characters from your database character set and can be at most 30 characters long.

Tablespace

Name of the tablespace in which to create the rollback segment. Choose the tablespace from the drop-down list.

Status

Online: Specifies that the rollback segment be placed online.

Offline: Specifies that the rollback segment be place offline.

  Related Topics


Create Rollback Segment: Extents Page

On the Extents page you can specify the storage characteristics of the rollback segment.

The Extents page contains the following fields:

Override Default Values

If this box is checked, you can edit all of the fields on the Extents page. If the box is not checked, the default value for each field displays and the values cannot be modified. This checkbox is only enabled during rollback Segment creation.

Initial Size

Size of the rollback segment's first extent. Enter the size of the initial extent. Use the unit button to specify either kilobytes or megabytes. The default is the size of 5 data blocks.

Next Size

Size of the next extent allocated to the rollback segment. Enter the size of the next extent. Use the unit button to specify either kilobytes or megabytes. The default is the size of 5 data blocks.

Optimal Size

Optimal size for the rollback segment. Optimal is not displayed for offline rollback segments. Enter the value for Optimal. Use the unit button to specify either kilobytes or megabytes. Oracle tries to maintain the optimal size of the rollback segment by dynamically deallocating extents when their data is no longer needed for active transactions.

A blank field assumes the default value. The default value of Optimal is null. If Optimal is null, Oracle never deallocates the rollback segment's unused extents.

The value of Optimal can never be less than the space initially allocated to the rollback segment, as specified by the values of Initial Extent, Next Extent, and Minimum Extents.

Minimum Number

Total number of extents to be allocated when the rollback segment is created. This field is only enabled when creating a rollback segment. Enter the minimum number of extents. The default and minimum value is 2.

Maximum

Maximum number of extents that can be allocated to the rollback segment. The default is operating system dependent. Enter the maximum number of extents. The default and maximum values depend on the data block size.

  Related Topics


Shrinking a Rollback Segment

To shrink an existing rollback segment, select the rollback segment from the multi-column list and choose Shrink from the Rollback menu. The Shrink Rollback Segment dialog box appears.

You can also display the Shrink Rollback Segment property sheet by selecting a rollback segment from the multi-column list and choosing Shrink from the context-sensitive menu.

Shrink Rollback Segment Dialog Box

The Shrink Rollback Segment dialog box contains the following information:

Shrink to

Optimal Size: Optimal size of rollback segments.

Size: Specify a specific number of bytes in active extents in the rollback segment.

Attention: You can only shrink a rollback segment that is online.

  Related Topics


Status Pop-up Menu

Status

Status of the rollback segment to be created. Newly created segments default to Offline status.

•	If you are altering an existing rollback segment, the Change Status button is enabled.

•	If the status is Offline, click the Change Status button to change the status to Online.

•	If the status is Online, click the Change Status button to change the status to Offline.

•	If the status is Partly Available, you can select the Place Online option from a pop-up list.

•	If the status is Needs Recovery, you can select the Take Offline option from a pop-up list.

  Related Topics


Tablespace Menu Options

The Tablespace menu allows you to perform the following operations:

•	Create to create a new tablespace.

•	Remove an existing tablespace.

•	Add Datafile to add a datafile to a tablespace.

•	Add Rollback Segment to add a rollback segment to a tablespace

•	Place Online to place a tablespace online.

•	Take Offline (Normal, Temporary, Immediate)

•	Make Read-Only to make a tablespace read-only.

•	Make Writeable to make a tablespace read/write.

•	Backup Wizard to run a backup wizard that creates a tablespace backup script.

These menu options are enabled depending on the object selected in the tree list.

  Related Topics


Create Tablespace: General Page
Tablespace Property Sheet: General Page

The General page of the Create Tablespace property sheet contains fields that define the tablespace. These fields are described below:

Name

Name of the tablespace to be created. Enter the name of the new tablespace. The tablespace name can only contain characters from your database character set and can be at most 30 characters long.

Status

Status of the tablespace to be created. To select the status, click the Change Status button.

•	If the status is Offline, click the button to change the status to Online.

•	If the status is Online, click the button to display a pop-up menu with Offline Normal, Offline Immediate, or Offline Temporary options. Select one of the Offline options.

•	If the status is Online and the database is version 7.1 or later, a Read-Only option is also available. If a tablespace has read-only status, the Make Writeable menu option is enabled. When you select the Make Writeable menu option, the tablespace becomes both readable and writeable and the status is changed to online.

Note: The Read-Only option is disabled if there any open transactions in the database or any active rollback segments in the tablespace.

Datafiles

Multi-column scrolling list of the datafiles belonging to the tablespace. The columns include Name, Status. Size, and % Full. These are the same columns as those in the Datafiles multi-column list.

Add

Displays the Create Datafile property sheet, which allows you to specify each new datafile belonging to the new tablespace. When you create a new datafile, the status column in the datafile list reads NEW.

Edit

Displays the Quick Edit Datafile property sheet, which allows you to edit the file specification for the datafile selected in the Datafiles scrolling list. You can also double-click on a datafile in the Datafiles scrolling list to display the Quick Edit Datafile property sheet. This property sheet is the same as the Create Datafile property sheet.

Remove

Removes the datafile selected in the Datafiles scrolling list. You can also press the Delete key to remove a selected datafile. You can only remove a datafile that has been newly created and has not been committed to a tablespace.

Type

Permanent:  Specifies that the tablespace will be used to hold permanent database objects. This option is selected by default.

Temporary:  Specifies that the tablespace will only be used to hold temporary objects (sort segments). No permanent object can reside in a temporary tablespace.

Attention: This option is only available for Oracle version 7.3 or greater. For more information on temporary tablespaces and their application, see Oracle7 Server Concepts.

  Related Topics


Create Tablespace: Extents Page
Tablespace Property Sheet: Extents Page

On the Extents page, you can specify the default storage parameters for all objects created in the tablespace. The Default Storage page contains the following fields:

Override Default Values

If this box is checked, you can edit all of the fields on the Default Storage page. If the box is not checked, the default value for each field displays and the values cannot be modified. This checkbox is only enabled during tablespace creation.

Note: If you do not enter an integral multiple of the operating system data block size when defining the size of extents, your entry is increased to the next multiple. If you do not enter a value, the default value remains. If a default value has not been explicitly specified, the field contains "Default."

Initial Size

Size of the object's first extent. Enter the size of the initial extent. Use the unit button to specify either kilobytes or megabytes. If you do not specify a size, the default is the size of 5 data blocks.

Next Size

Size of the next extent to be allocated to the object. Enter the size of the next extent. Use the unit button to specify either kilobytes or megabytes. If you do not specify a size, the default is the size of 5 data blocks.

Increase Size By

Percent by which each extent after the second grows over the previous extent. Enter a value for percent increase. If you do not specify a value, the default is 50.

Minimum Number

Total number of extents to be allocated when an object is created in the tablespace. Enter the minimum number of extents. If you do not specify a number, the default value is 1.

Maximum Number

Maximum number of extents that can be allocated to an object created in the tablespace.

Unlimited: When selected, allows you to create a number of extents that is only limited by the amount of contiguous free space in a tablespace.

Value: When selected, allows you to specify the maximum number of extents. If you do not specify a value, the default value applies. The default and maximum values depend on the data block size.

  Related Topics


 HIDM_VAG_TOOL_DEFRAG

Used by string table

  Related Topics


 HIDM_VAG_TOOL_BACKUP

Used by string table

  Related Topics


 HIDM_VAG_TOOL_RECOVERY

Used by string table

  Related Topics


 HIDM_VAG_TS_ALTER

Used by string table

  Related Topics


 HIDM_VAG_DF_ALTER

Used by string table

  Related Topics


 HIDM_VAG_RB_ALTER

Used by string table

  Related Topics


 HIDM_VAG_WIZ_TSBKUPTS

Used by string table

  Related Topics


 HIDR_VAOG_POP_OFFLINE

menu

  Related Topics


 HIDR_VAOG_POP_ONLINE_TS

Menu

  Related Topics


 HIDR_VAOG_POP_ONLINE_CREATE

Not used

  Related Topics


 HIDR_VAOG_POP_ONLINE_TS1

Menu

  Related Topics


 HIDD_VAOG_TS_GEN1

Not used

  Related Topics


Security Manager

With the Security application you can create, alter, and drop users, roles, and profiles. The Security application manages the following groups:

•	Users

•	Profiles

•	Roles

  Related Topics


Users Menu Options

The User menu contains the following menu options:

•	Create to create a new user.

•	Create Like to create a new user based on the selected user in the tree list.

•	Remove to delete the selected user in the tree list.

•	Revoke Privilege to remove a selected privilege or role.

•	Add Privileges to User to add multiple privileges to one or more users.

•	Change Account Status to lock, unlock, or expire a selected user account.

Note: These menu options are enabled depending on the object selected in the tree list or multi-column list.

  Related Topics


Create User Property Sheet: General Page
User Property Sheet: General Page

The General page allows you to specify a user’s name (when creating a new user), their default profile, authentication method, and the default tablespace. The Create User property sheet contains the following:

Name

The name of the user to be created. Enter the name of the new user. The username can only contain characters from your database character set and can be at most 30 bytes long.

Profile

The profile assigned to the user. Use the drop-down list to choose the profile you want to assign to the user. The DEFAULT profile is assigned if you do not make a selection.

Authentication

The method Oracle uses to authenticate the user.

•	Global: Specifies that the user be identified globally amongst multiple databases. Note: The global authorization option is only available with Oracle 8 databases.

•	External: Specifies that the operating system verify the user.

•	Password: Requires a password for logon. Enter the password in the adjacent text entry field. Enter the password again in the Confirm text entry field for verification.

Expire Now: When checked, the user’s password is expired immediately. If you create a new user with this option selected, the user’s password must be changed during the first attempted login. This feature is available for Oracle8 databases only.

Tablespaces

The user's default and temporary tablespaces.

•	Use the drop-down list to choose the default tablespace for objects the user creates.

•	Use the drop-down list to choose the tablespace for the user's temporary segments.

Status

Lock: When selected, locks the user’s account and disables access to the account.

Unlock: When selected, unlocks the user’s account and enables access to the account.

Note: Status is enabled for Oracle8 databases only.

  Related Topics


Create User Property Sheet: Privileges Page
User/Roles Property Sheet: Roles/Privileges Page

The Roles/Privileges page allows you to specify or revoke the system privileges and roles assigned to the user. The Privileges page contains the following:

Privilege Type:

A drop-down list containing System Privileges and Roles. Your selection in the drop-down list determines what is displayed on the rest of the page.

Available

Displays the list of available roles or system privileges available for assignment to a user.

If you selected Roles, the roles that you can grant to a user display in a scrolling list. These are roles you have created and roles you have been granted with the Admin Option. I

Roles that you add to the user are assigned as default roles unless you change the specification by clicking on the role’s entry in the Default column.

You must add the roles with the Admin Option in a separate operation from the roles you want to add without the Admin Option.

Note: When you grant the DBA and RESOURCE rolesto a user or role with Oracle7 release 7.2.2 or later, the user or role is also granted the UNLIMITED TABLESPACE system privilege. When you revoke either role from a user or role, the UNLIMITED TABLESPACE system privilege is also revoked. The UNLIMITED TABLESPACE can also be revoked independent of the DBA and RESOURCE roles.

System Privileges: If you select System Privileges, system privileges that you are able to grant to a user display in a scrolling list. These are the system privileges the you have been granted with the Admin Option. If you have the GRANT ANY PRIVILEGE system privilege, all privileges are listed. Select the privileges that you want to add to the user.

Attention: If you want to change the Admin or Grant option of a current privilege or role, you must add the privilege or role with Admin or Grant option specified as you want.

Up and Down Arrows

Up Arrow: Adds roles or system privileges that are selected in the Available list to the Granted spreadsheet.

Down Arrow:  Removes roles or system privileges that are selected in the Granted spreadsheet.

Granted

An editable spreadsheet displaying roles or system privileges assigned to a user. New additions (selected but not yet applied) are identified by a hand with a plus sign. When creating a user, the spreadsheet consists of three columns:

System Privilege or Role

Name of the role or system privilege.

Admin Option

When checked, allows the user to grant the system privileges to other users or roles. By default, Admin Option is disabled. You enable the Admin Option by clicking on the spreadsheet entry. In this case, the “X” becomes a check.

Default. (Users property sheet only)

When checked, establishes the role as a default for the user upon system logon.

When creating a Role, this spreadsheet consists of two columns: System Privilege or Role and Admin Option.

  Related Topics


 User/Roles Property Sheet: Object Privileges Page

The Object Privileges page, available in Advance UI mode, allows you to grant or revoke privileges for a specific user on schema objects. This page contains the following:

Objects

A tree listing of schemas in the database and objects in the schemas displays in the Object window. Click on the '+' to the left of a container icon to display the objects contained in the schema, then select the objects that you want to grant privileges for. After the object is selected, the available privileges for the object are displayed to the right in the Available Privileges scrolling list.

You can grant an object privilege that you have been granted with the Grant Option. If you are the owner of the object, you can grant all privileges on the object. Select the privileges you want to grant for the selected object. The scrolling list includes the privileges you can grant on this object.

Grant Option box to allow the user to grant the object privilege to other users and roles.

Click the Add button to add the selected object privileges to the user.

Available Privileges

Displays privileges available for the schema object selected in the tree list.

Up and Down Arrows

Down Arrrow: Adds privileges that are selected in the Available Privileges list to the Granted Object Privileges spreadsheet.

Up Arrow:  Removes privileges that are selected in the Granted Object Privileges spreadsheet.

Granted Object Privileges

An editable spreadsheet displaying object privileges to be made available to a user. New additions (selected but not yet applied) are identified by a hand with a plus sign.

When creating a new user, the spreadsheet consists of two columns indicating the name of the object privilege and whether or not the Grant Option is specified for that privilege.

When enabled, the Grant Option allows the user to grant the specific object privilege to other users and roles. By default, this option is disabled. To enable the grant option, click on the specific spreadsheet entry. The “X” is replaced with a check.

When creating a role, the spreadsheet consists of a single Object Privilege column.

  Related Topics


Create User Property Sheet: Default Roles Page
User Property Sheet: Default Roles Page

On the Default Roles page of the Create User property sheet, you can specify the default roles assigned to a user. Oracle enables the user's default roles at logon.

Note: Only a role granted directly to the user can be specified as a default role. A role granted through another role cannot be a default role.

The Default Role page contains the following:

Default:

Scrolling list of the default roles granted to the user. To remove a role as a default, select the roles you wish to remove as the user's default roles and click Remove Default button.

Note: Roles assigned as non-default roles for a user need to be activated explicitly by the user after connecting to the database.

Non-Default:

Scrolling list of the non-default roles that have been granted to the user. To add a role as a default, select the roles you wish to designate as the user's default roles and click the Add Default button.

Click on the Apply button to save any changes you have made to the property sheet. See property sheet command buttons.

  Related Topics


Create User Property Sheet: Quotas Page
User Property Sheet: Quotas Page

The Quotas page, available in Advanced UI mode, allows you to specify the tablespaces in which the user can allocate space and the maximum amount of space the user can allocate in each tablespace. The Quotas page contains the following items:

Quota Details

Scrolling list of the tablespaces in the database and the maximum amount of space the user has been allowed in each tablespace. The list can be sorted on the Tablespace or Quota Size column. To specify a quota size for a tablespace, select the tablespace in the scrolling list and specify a quota size by clicking on the None, Unlimited, or Value button.

None: Click the None button if you do not want the user to have any quota on the selected tablespace.

Unlimited: To specify an unlimited quota for the tablespace, click the Unlimited button. With an unlimited quota, the user can allocate an unbounded amount of space in the tablespace.

Value: To specify a specific quota, click the Value button and enter a quota value in the adjacent text entry field. Select the K or M button to specify kilobytes or megabytes.

  Related Topics


Profile Menu Options

The Profile menu contains the following menu options:

•	Create to create a new profile.

•	Create Like to create a new profile that is based on the selected profile.

•	Remove to delete the selected profile.

•	Assign Profile to Users to assign a profile to a specific user.

Note: These menu options are enabled depending on the object selected.

  Related Topics


Create Profile: General Page
Profile Property Sheet: General Page

The General page allows you to enter the following information:

•	Profile name

•	Details on the Session, CPU, Connect, and Idle times

•	Database Services Parameters

This property sheet contains the following:

Name

Name of the new profile.

Details

These fields determine the amount of time allocated to the CPU per Session, CPU per Call, Connect Time, and Idle Time for this profile. The fields are:

CPU/Session

Total amount of CPU time allowed in a session. The limit is expressed in seconds.

CPU/Call

Maximum amount of CPU time allowed for a call (a parse, execute, or fetch). The limit is expressed in seconds.

Connect Time

Maximum elapsed time allowed for a session. The limit is expressed in minutes.

Idle Time

Maximum idle time allowed in a session. Idle time is a continuous period of inactive time during a session. Long-running queries and other operations are not subject to this limit. The limit is expressed in minutes.

Database Services

These fields determine the database services allocated to this profile. The fields are:

Concurrent Sessions

Maximum number of concurrent sessions allowed for a user.

Reads/Session

Total number of data block reads allowed in a session. The limit includes blocks read from memory and disk.

Reads/Call

Maximum number of data block reads allowed for a call (a parse, execute, or fetch) to process a SQL statement.

Private SGA

Maximum amount of private space a session can allocate in the shared pool of the System Global Area (SGA). The Private SGA limit applies only if you are using the multi-threaded server architecture. The limit is expressed in kilobytes (Kbytes).

Composite Limit

Total resource cost for a session. The resource cost for a session is the weighted sum of the CPU time used in the session, the connect time, the number of reads made in the session, and the amount of private SGA space allocated.

Entering Values

You can enter a value in a field or choose from the drop-down list adjacent to the field. Click on the down-arrow to display the list. The drop-down list provides the following choices:

Default

Use the limit specified for this resource in the DEFAULT profile.

Unlimited

The user's access to this resource is unlimited.

Values

Select one of the existing values. The default values vary by field and are common values for the field. If you have entered a value in the field, that value appears in the drop-down list.

Attention: In the SQL Worksheet, you can use the SQL command ALTER RESOURCE COST to specify the weights for the resources in the Composite Limit. For information about the ALTER RESOURCE COST command, see the Oracle7 Server SQL Reference.

  Related Topics


 Profile Property Sheet: Password Page

The Password page allows you to set account password parameters. This page consists of the following:

Expire Password

Expire in  Limits the number of days after which a password expires. Select a value from the drop-down list, or enter a specific value.

Lock Limits the number of days during which a password can be changed following the first successful login after password expiration.

Keep Password History

Keep Specifies the number of times a password must be changed before it can be reused. Keep for is disabled if a value is specified in this field.

Keep for Limits the number of days before a password can be reused after it expires. Keep is disabled if a value is specified in this field.

Enforce Password Complexity

Allows a PL/SQL password verification routine to be used when creating a profile. NULL is selected by default.

Lock account on failed logon

Lock after Limits the number of failed logon attempts allowed before a user is locked out from the account.

Lock for Specifies the number of days the account is locked after failing the specified number of logon attempts. If UNLIMITED is specified, only the database administrator can unlock the account.

Note: If Default is selected for any password options, values defined in the Default profile are used.

  Related Topics


Role Menu Options

The Role menu contains the following menu options:

•	Create to create a new role.

•	Create Like to create a new role based on the selected role.

•	Remove to delete the selected role.

•	Revoke Privilege to remove a privilege or role from a role.

•	Add Privileges to Roles to add privileges or roles to roles.

Note: These menu options are enabled depending on the object selected.

  Related Topics


Create Role: General Page
Roles Property Sheet: General Page

The General page allows you to specify the name of the role (when creating a new role) and the authentication method.

Name

Name of the role to be created. This field is only active when creating a role.

Authentication

Method used to enable the role.

•	None : Specifies that a user granted the role may enable it without specifying a password.

•	Global: Specifies that a user granted the role may enable it globally amongst multiple databases. Note: The global authorization option is only available with Oracle 8 databases.

•	External: Specifies that the operating system verifies the user enabling to the role.

•	Password: Requires a password to enable the role. Enter the password in the adjacent text entry field. Enter the password again in the Confirm text entry field for verification.

Click on the Apply button to save any changes you have made to the property sheet. See property sheet command buttons.

  Related Topics


Adding Privileges or Roles to Users

You can assign subroles and grant individual privileges to multiple roles. To add roles and grant privileges to roles, choose Add Privileges to Roles from the Role menu to display the Add Privileges to Roles dialog box.

A scrolling list of roles is displayed in the top half of the dialog box. Select the roles in the list to which you want to add privileges or roles.

Select System Privileges, Object Privileges, or Roles from the drop-down list. The display at the bottom half of the dialog box varies according to your selection.

Roles

If you selected Roles, the roles that you can grant to a role display in a scrolling list. These are roles you have created and roles you have been granted with the Admin Option. If you have the GRANT ANY ROLE system privilege, all roles are listed. Select the roles that you want to add to the role.

•	Click the With Admin Option box to allow the role to grant the role to other users or roles. If you grant a role with the Admin Option, the role can also alter or drop the role.

•	Click the Apply button to add the selected roles to the role.

Attention: You must add the roles with the Admin Option in a separate operation from the roles you want to add without the Admin Option.

System Privileges

A scrolling list of the system privileges that you are able to grant to a role. These are the system privileges you have been granted with the Admin Option. If you have the GRANT ANY PRIVILEGE system privilege, all privileges are listed. Select the privileges that you want to add to the role.

•	Click the With Admin Option box to allow the role to grant the system privileges to other users or roles.

•	Click the Add button to add the selected system privileges to the role.

Attention: You must add the privileges with the Admin Option in a separate operation from the privileges you want to add without the Admin Option.

Object Privileges

A tree listing of schemas in the database and objects in the schemas displays in the Object window. Click on the "+" to the left of a container icon to display the objects contained in the schema, then select the objects to which you want to grant privileges. After the object is selected, the available privileges for the object is displayed to the right in the Privileges scrolling list.

Select the privileges you want to grant for the selected object. The scrolling list includes the object privileges you can grant on an object. Click the Apply button to add the selected object privileges to the role.

Click on the Apply button to save any changes you have made in the dialog box. See dialog box command buttons.

  Related Topics


Assigning a Profile to a User

To assign a profile to multiple users in the database, choose the Assign Profile to Users menu option.

Select the profile that you want to assign from the drop-down list in the Assign Profile dialog box. In the scrolling list, select the users to which you want to assign the profile. Click on the Apply button to assign the selected profile to the users. Click OK to close the dialog box.

  Related Topics


 HIDM_VAC_DB

  Related Topics


 HIDM_VAC_ENABLE_ROLES

  Related Topics


Schema Manager

With the Schema application you can create, edit, and examine schema objects. The Schema application manages the following groups:

•	Clusters

•	Database Links

•	Functions and Procedures

•	Indexes

•	Packages and Package Bodies

•	Refresh Groups

•	Sequences

•	Snapshots and Snapshot Logs

•	Synonyms

•	Tables

•	Triggers

•	Views

  Related Topics


Object Menu Options
Object Menu

The Schema manager includes four standard menus, File, Edit, View, Logging, and Help, plus the Object menu.  The Object menu contains the following menu options:

Create

Creates a new schema object.

Create Like

Allows you to create a new schema object based on the currently selected object in the tree list.

Remove

Removes the selected schema object in the tree list.

Grant Privilege on

Grant object privileges to a user or role.

Create Synonym for

Creates a new synonym for a schema object.

Create Index on

Allows you to quickly create indexes on tables and clusters selected from the tree list.

Truncate (Oracle 8 only)

Removes all rows from a partition in a table.

•	Drop Storage: Specifies that the space from the deleted rows be dealocated and made available for use by other schema objects in the tablespace.

•	Reuse Storage: Specifies that the space from the deleted rows remains allocated to the partition.

Make Local Indexes Unusable (Oracle 8 only)

Marks the local index partitions corresponding to a table partition unusable.

Rebuild Unusable Local Indexes (Oracle 8 only)

Rebuilds all unusable local index partitions corresponding to a table partition. This operation is not parallelized.

Merge Partition (Oracle 8 only)

Combines adjacent partitions.

  Related Topics


View By Object/Schema
View By Object/SchemaMenu Options

Use these menu options to organize the tree list by schema type or by object type. By default, the tree list is displayed alphabetically by object type.

By selecting By Schema from the View menu, you can view the tree list by schemas defined within the connected database. All schemas defined in the database are listed alphabetically in the tree list as folders. You expand the specific schema container in the tree list to view the complete list of schema object types defined for that schema.

  Related Topics


Granting Object Privileges

The Grant Object Privileges dialog box allows you to assign object privileges to a user or a role. The dialog box consists of the following elements:

Grant

Scrolling list of all privileges available for  the selected schema object.

On Schema Object

Selected schema object's type and name.

To

Scrolling list of all users an roles defined in the database.

With Grant Option

When checked, this option allows a user to grant the object privileges to other users and roles.

  Related Topics


Granting an Object Privilege

To grant an object privilege:

1.	Select the desired privilege(s) from the Grant list.

2.	Select a user or role from the To list. Click the With Grant Option box to allow the user to grant the object privilege to other users and roles.

3.	Click OK.

  Related Topics


Cluster Property Sheet: General Page

This page allows you to define the cluster name, type, and cluster key column attributes. The General page contains the following:

Name

Name of the cluster being defined.

Schema

Name of the schema containing the cluster. The drop-down list contains all schemas available in the current database.

Size

An estimate of the total amount of space required to store the average number of rows associated with each cluster key value or hash value (kilobytes or megabytes)

Type: Index Cluster

When selected, indicates that an index  is specifically defined for the cluster.

Type: Hash Cluster

When selected, indicates that related rows are stored in the same data block.

Hashkeys: Maximum number of unique hash values that can be generated by the hash function.

Hash Function: Specify that Oracle's internal hash function use the current function (Default) or bypass the Oracle internal hash function and specify a SQL expression.

Cluster Key Columns

Column: Name of the column

Datatype: CHAR, VARCHAR2, NUMBER, LONG, RAW, LONG RAW, DATE, ROWID, MLSLABEL

The following buttons appear when creating a new cluster.

New:  Displays the Column Details dialog box.

Edit:  Displays the Column Details dialog box for the cluster key column selected in the list.

Remove:  Deletes a cluster key column that is selected in the list.

  Related Topics


Create Database Link Property Sheet: General Page
Database Link Property Sheet: General Page

The Database Links property sheet allows you to define links to schema objects residing on remote databases. This property sheet contains of the following:

Name

The name of the database link being defined. You can specify any valid Oracle identifier.

Public

Specifies that the database link be available to all users (public) or only the owner (private). The setting defaults to Private when creating a new database link.

Connection Details

Privileged Link (Oracle 8 only)

Need to do determine function

Anonymous Link:  Specifies that the database link use the username and password of the user accessing the database link.

Named Link

Username:  Username used to connect to the remote database.

If the Username field is left blank during the creation process, the newly defined link acquires the username of the person accessing the remote database.

Password:  Password used to connect to the remote database.

If the Username and Password fields are left blank, the database link uses the username password of the person accessing the database link.

Service Name: Database specification of a remote database.

Test:  Checks the validity of the Username, Password, and Service Name when a database link is created. Only available when altering a database link.

Creation Date

Displays the date of database link creation. By default, the current date is displayed.

  Related Topics


Create Index Property Sheet: General Page
Index Property Sheet: General Page

The General page of the index property sheet allows you to define an index on one or more columns of a table or a cluster. The General page consists of the following information:

Name

Name of the index. When creating an index you can specify a valid Oracle identifier

Schema

Schema in which the index will be defined. The default schema for a new index is the user's default schema. When creating an index link, you can also select any schema defined in the connected database from the Schema drop-down list.

Index Type (Oracle 8 only)

Specifies whether a partitioned index is local (equi-partitioned with the underlying table) or global (patitioning defined explicitly when you create the index). Partitioning of global indexes must be maintained manually.

Index On

Table/Cluster:

Specifies whether the index is to be placed on a table or cluster.

Schema:

Drop-down list displaying available schema to which the index can belong.

Table:

Drop-down list displaying all available tables belonging to the selected schema.

Table Spreadsheet

Table Columns:  Column names of the table selected in the Table drop-down list.

Order:  Order of the columns selected for the index. Columns are ordered in the sequence in which it is added to the index.

To add a column to the index, click on the desired column in the spreadsheet. The order of the column appears in the Order column.

To remove a column from the index click on the desired column entry in the spreadsheet. The column are automatically reordered.

Options

Unique:  Specifies that the value of the column (or combination of columns) in the table to be indexed must be unique.

Sorted (Default):  If deselected, indicates to Oracle 7 that rows are stored in the database are in ascending order and therefore do not have to be sorted when creating the index.

Recoverable:  Specifies that the creation of the index will be logged in the redo log file.

  Related Topics


PLSQL Property Sheets:  General Pages
Package Property Sheet: General Page

The Package property sheet allows you to define a stored package of encapsulated collection of related procedures. This property sheet consists of the following information:

Name

Name of the package being defined.

Schema

Name of the schema containing the package. The drop-down list displays the names of all available schemas

Recompile

Recompile the PL/SQL source for the package so that it can be stored and executed from within the database.

Dates

Created:  Date the package was originally created.

Last Modified:  Date the package was last modified.

Status

Current status of the package (valid or invalid).

Show Errors/Hide Errors:  Opens or closes the Error Messages dialog box. This button is available when the package status is invalid.

Package Source

PL/SQL source code for the package.

  Related Topics


Create Sequence Property Sheet: General Page
Sequence Property Sheet: General Page

The Sequence property sheet allows you to define a database object from which users may generate unique integers. The General page contains the following information:

Name

Name of the sequence being defined. During the Create operation, you can specify a valid Oracle identifier as the name of the sequence.

Schema

Schema in which the sequence is defined. The default schema for a new sequence is the user's default schema. During the Create operation, you can choose a schema from those defined in the connected database from the drop-down list.

Type: Ascending

When selected, sequence values increase from the initial value towards the maximum value. This is the default setting when creating a sequence.

Type: Descending

When selected, the sequence values decrease from the initial value towards the minimum value.

Values

Minimum: Smallest allowed value of the sequence. When creating a sequence, this field is initially blank. If this field is blank when you click the Create button, a default value of one for an ascending sequence or -1026 for a descending sequence will be used.

Maximum: Largest permitted value of a sequence. When creating a sequence this field is initially blank.  If left blank when the Create button is selected, a default value of 1027 for an ascending sequence and -1 for a descending sequence will be used.

Increment: Interval by which the sequence increases or decreases (Ascending sequence). When creating a sequence, this field is initially blank. If left blank when the Create button is selected, a default value of 1 is used. Only positive integers are accepted in this field.

Decrement: Interval by which the sequence decreases (Descending sequence). When creating a sequence, this field is initially blank. If left blank when the Create button is selected, a default value of 1 is used. Only positive integers are accepted in this field.

Initial: The starting value of the sequence. If the field is blank when the Create button is selected, a default value of the sequence's minimum  will be used for an ascending sequence. For a descending sequence, a default value of the sequence's maximum value is used.

Recent: The most recent value of the sequence. This field is active when altering an existing sequence.

Options

Cycle Values: When checked, specifies that the sequence should continue to generate values after reaching its minimum or maximum value. For ascending sequences, the minimum value is generated after the maximum is reached. For descending sequences, the maximum value is generated after the minimum is reached. If Cycle Values is not checked, the sequence will stop generating values when it reaches its minimum or maximum. When creating a sequence, this checkbox is unchecked by default.

Order Values: When checked, specifies that the sequence numbers are to be generated in order of request. When creating a sequence, this checkbox is unchecked by default.

Cache: Number of values to be pre-allocated and stored by the database. There are three options:

Default: The default value is 20.  This option is selected by default.

No Cache: Specifies that values of the sequence not be pre-allocated.

Size: The smallest acceptable value is 2. For sequences that cycle, this value must be less than the number of values in the cycle.  If the maximum number of values the sequence can generate is less than the cache size, the cache size will be automatically changed to the maximum number of possible values.

  Related Topics


Snapshot Property Sheet: General Page

The General page allows you to define the name, schema, refresh type, and subquery for a snapshot. The General page contains the following:

Name

Name of the snapshot being defined. During the Create operation, you can specify a valid Oracle identifier as the name of the sequence.

Schema

Name of the schema containing the snapshot. The drop-down list contains all available schemas within the connected database.

Refresh Type

Type of refresh for automatic refreshes:

Complete: Specifies a refresh that executes the subquery.

Fast: Specifies a refresh using only the updated data stored in the snapshot log associated with the master table.

Force: Specifies a fast refresh if one is possible or a complete refresh if fast refresh is not possible.

Start Date:  Date snapshot refresh is to begin.

Next Date:  Expression that calculates the interval at which the snapshot is updated.

Updatable

When selected, indicates that the snapshot can be updated. When used in conjunction with the Replication Option, updates are propagated to the master.

Snapshot Subquery

Snapshot query executed by Oracle when you create the snapshot. Results of the query are placed in the snapshot. (Create only)

  Related Topics


Snapshot Log Property Sheet: General Page

The Snapshot Log property sheet allows you to define a snapshot log, which is used to refresh the master table’s snapshots. The General page contains the following:

On Master Table

Schema: Name of the schema to which the master table belongs. The drop-down list displays all schemas available to the user.

Table: Name of the master table. The drop-down list displays all tables belonging to the selected schema.

Log Table

Name of the table that stores the ROWID and timestamp of rows updated in the master table.

Log Trigger

Name of the AFTER ROW trigger on the master table that tells Oracle to insert the ROWIDs and timestamps of inserted, updated, and deleted rows into the master snapshot log.

Current Snapshots

Scrolling list displaying the snapshots associated with the snapshot log.

  Related Topics


Create Refresh Group: General Page
Refresh Group: General Page

The Refresh Group general page allows you to define the name, schema, refresh interval, and rollback segment to use for a group of snapshots. The General page consists of the following information:

Name

Name of the Refresh group.

Schema

Name of the schema containing the refresh group.The drop-down list displays all available schemas.

Refresh

Refreshes the current refresh group immediately.

Broken

When checked, marks a job as broken so Oracle will not attempt to execute the job.

Delete group when last member deleted

Upon deleting the last refresh group member, the refresh group is automatically deleted.

Refresh

Next Date:  Next date that you want a refresh to occur.

Interval:  Function used to calculate the next time to refresh the snapshots in the refresh group.

Continue refresh despite conflicts:  Select this option if you want the refresh to proceed even if there are outstanding conflicts logged in the DefError table for the snapshot's master. Active for updatable snapshots only.

Push changes from snapshot to master before refresh: When selected, allows you to push changes from the snapshot to its associated master before refreshing the snapshot. Otherwise, these changes may appear to be temporarily lost.  Active for updatable snapshots only. This option is selected by default.

Rollback Segment

Use default rollback segment:  When selected, the default rollback segment is used. Segment name and Segment Schema are grayed out.

Segment Name:  Name of the rollback segment to use while refreshing snapshots.

  Related Topics


Create Refresh Group: Snapshot Page
Refresh Group: Snapshot Page

The Snapshot page consists of the following information:

Available

Scrolling list containing all available snapshots.

In Group

Scrolling list containing all snapshots in the refresh group.

To add a snapshot to the refresh group, select an item from the Available list and click Add. The snapshot appears in the In Group list. Click Apply.

To remove a snapshot from the refresh group, select an item in the In Group list and click Remove.  Click Apply

  Related Topics


Create Synonym: General Page
Synonym: General Page

The General page allows you to create a synonym for an existing schema object or view the settings for an existing synonym. The General page consists of the following information:

Name

Name of the synonym.

Schema

Name of the schema containing the synonym. The drop-down list contains all available schemas within the connected database.

As Alias For

Local Database/Remote Database: Allows you to create a synonym from an object on a local database or an accessible database on the network.

Object Type (Local)/DB Link (Remote): Drop-down list containing available database object types (tables, snapshots, etc.) for local databases. If Remote Database is selected the field label changes to DB Link. In this case, the drop-down list contains all database links defined for the current instance.

Schema:  Drop-down list containing all available schemas for the current instance (local databases). If Remote Database is selected, the schema name must be typed in explicitly.

Object:  Drop-down list containing all available database objects for the selected schema.

  Related Topics


Creating a Synonym

To create a Synonym:

1.	Choose Create from the Object menu.

2.	Select Synonym from the Create Object dialog box.

3.	Click OK.. The Create Synonym property sheet appears.

4.	Fill in the requisite information and click Create.

You can also create a synonym by selecting a schema object in the tree list and choosing Create Synonym for from the Object menu. All requisite information is filled in except the name of the synonym.

  Related Topics


Create Table: General Page
Table Property Sheet: General Page

The General page allows you to define or view the primary attributes of a table such as column definitions, schema in which the table resides, or query used to populate a new table. The General page contains the following information:

Name

Name of the table being defined. During the Create operation, you can specify a valid Oracle identifier as the name of the table.

Schema

Schema in which the table is defined. The default schema for a new table is the user's default schema. During the Create operation, you can choose a schema from those defined in the connected database via the drop-down list.

Define Columns / Define Query (Create mode only) / Columns

An editable spreadsheet allowing you to edit or add columns to a database table. The columns of this spreadsheet consist of Column (name), Datatype, Default, Nulls? and Cluster Column. New additions (defined but not yet created) are identified by a hand with a plus sign. The spreadsheet consists of six columns:

Name : Name of the table column being defined or edited. You can specify a valid Oracle identifier as the name of the column. This field is disabled for columns that have already been defined in the database.

Datatype: Column's Oracle datatype. See Oracle7 Server Administrator's Guide for specific information on Oracle datatypes. You can select one of the following items: CHAR, VARCHAR2, NUMBER, LONG, RAW, LONG RAW, DATE, ROWID, MLSLABEL

Length: Number of bytes allowed for values defined in the column (for CHAR, VARCHARZ, NUMBER, RAW).

Precision (for NUMBER datatype): Number of digits to the right of the decimal point. If CHAR is selected in the Datatype drop-down list, you may specify length. If VARCHAR2 or RAW is selected, you may specify a length.  If NUMBER is selected, you may specify a length, a length and a precision, or neither.

Nulls?:  When checked, indicates that the column being defined is not permitted to contain null values.

Default Value: An expression that serves as the default value for this column in any rows for which the INSERT statement omits a value for the column.

Define Query

When selected, a scrolling editable text area appears allowing you to enter a SQL query to be used to populate the table. A query does not have to be specified (Create mode only).

  Related Topics


Create Table: Column Details Dialog Box

The Column Details dialog box contains the following:

Name

Name of the table column being defined or edited. You can specify a valid Oracle identifier as the name of the column. This field is disabled for columns that have already been defined in the database.

Datatype

Column's Oracle datatype. See Oracle7 Server Administrator's Guide for specific information on Oracle datatypes.

You can select one of the following items: CHAR, VARCHAR2, NUMBER, LONG, RAW, LONG RAW, DATE, ROWID, MLSLABEL

Length: Number of bytes allowed for values defined in the column (for CHAR, VARCHARZ, NUMBER, RAW).

Precision (for NUMBER datatype): Number of digits to the right of the decimal point.

If CHAR is selected in the Datatype drop-down list, you may specify length. If VARCHAR2 or RAW is selected, you may specify a length.  If NUMBER is selected, you may specify a length, a length and a precision, or neither.

Values

Default:  An expression that serves as the default value for this column in any rows for which the INSERT statement omits a value for the column.

No Nulls:  When checked, indicates that the column being defined is not permitted to contain null values.

Is Cluster Column

Drop-down list box allowing you to specify an associated column in the cluster key.

This drop-down list box is only enabled if a cluster has been selected on the Table General page.

  Related Topics


Create Table Property Sheet: Constraints Page
Table Property Sheet: Constraints Page

The Constraint page allows you to define or edit integrity constraints for a table. This page contains the following information.

Constraints on Table

An editable spreadsheet containing the following columns:

Name: Name of the table constraint being defined.

To define a new constraint, you can enter a valid Oracle identifier as the name of the constraint.  If no name is entered, a default name will be assigned by the database.  This field is disabled if the column has already been defined in the database.

Type: The type of constraint. The drop-down list displays available constraint types: UNIQUE, PRIMARY, FOREIGN, CHECK.

Disable: Indicates that the constraint should be disabled (checked) or enabled (‘x’) when the constraint is created. Click on the spreadsheet cell to toggle this setting.

Referenced Schema: Schema referenced by the foreign key in the constraint being defined. The drop-down list displays all available schema for the database. This list is active only when FOREIGN is selected as the constraint type.

Referenced Table:  Table referenced by the column being defined. This drop-down list displays all tables contained within the Referenced Schema.

Cascade on Delete: When checked, indicates that rows will automatically be removed from the child table if they reference values contained in the referenced key column of rows being removed from the parent table. You toggle this setting by clicking on the desired spreadsheet cell. This control is disabled if a query is defined at Create time or if the column has already been defined in the database.

Check Condition: Check constraint to be included in the table constraint currently being defined.

You can enter the text of the check constraint in this spreadsheet cell or a valid expression. For more information see Oracle 7 Server SQL Reference.

Constraint Definition

An editable spreadsheet displaying both table and referenced columns.

Table Columns:  Column on which the constraint is to be placed. The drop-down list displays all columns in the table. This cell is active for UNIQUE and PRIMARY key constraints.

Referenced Columns:  Columns (unique or primary key) referenced by a foreign key in a referential integrity constraint. The drop-down list displays all columns available in the referenced table.

Dropping a Constraint on a Table.

To drop a constraint from a table:

1.	Using the left mouse button, click on the entry select button located to the immediate left of an individual row in the Constraints on the Table spreadsheet.

2.	Click the right mouse button to display the pop-up menu.

3.	Select Drop to delete the constraint, or Drop with Cascade to tell Oracle to drop the constraint and maintain referential integrity by also removing dependent foreign key values if a referenced primary or unique key value is removed.

Removing a Constraint Definition (Create mode only)

To remove a constraint definition:

1.	Using the left mouse button, click on the entry select button located to the immediate left of an individual row in the Constraints on the Table spreadsheet. The table columns or referenced columns appear in the Constraint Definition spreadsheet.

2.	In the Constraint Definition spreadsheet, select the desired constraint by clicking on the entry select button located to the immediate left of an individual row in the Constraint Definition spreadsheet.

3.	Click the right mouse button to display the pop-up menu.

4.	Select Remove.

  Related Topics


Create Table Property Sheet: Status Page
Table Property Sheet: Status Page

The Status page contains the following information:

Unique Constraint

Do Not Change Status:  Maintains existing unique constraint settings.

Enable:  Enables unique constraint on specified columns.

Disable:  Disables unique constraints on specified columns.

Drop:  Indicates that the unique constraint should be dropped (on the specific columns). This group is enabled when defining a unique constraint on the Constraint page.

Columns:  Columns on which a unique constraint has been placed.

Save Exceptions to

These controls are enabled when the Enable radio button is selected.

Schema: Schema to which exceptions to the unique/primary key constraints being enabled should be saved.

Table:  Table to which exceptions to unique/primary key constraints being enabled should be saved.

Cascade

This control is only active when you disable or drop a constraint.

When checked, indicates that the integrity constraints that depend on the specified integrity constraint should be disabled.

Primary Key Constraint

This group box is enabled when defining a unique constraint on the Constraint page.

Do Not Change Status: Maintains existing primary key constraint settings.

Enable:  When selected, enables primary key constraint.

Disable:  When selected, disables primary key constraint.

Drop: Indicates that the constraint should be dropped (checked) or not dropped (not checked) when created.

Triggers

This control is only enabled when editing a table.

Do Not Change Status: Maintains existing trigger settings.

Enable All: Enables all triggers defined in the table.

Disable All: Disables all triggers defined in the table.

  Related Topics


Create Triggers Property Sheet: General Page
Triggers Property Sheet: General Page

The General page allows you to define the primary characteristics of a trigger such as the name of trigger, schema to which the trigger belongs, and the trigger body.  This page contains the following information:

Name

Name of the trigger being defined.

Schema

Schema in which the trigger is to be defined. The default schema for a new trigger is SYSTEM.

Trigger On

Schema: Drop-down list displaying all available schema in the database. This field specifies the schema that contains the table.

Table: Drop-down list displaying all available tables in the selected schema. This field specifies the name of the table on which the trigger is to be created. Triggers on SYS schema tables cannot be created.

Replace if Exists

When selected, indicates that a trigger is to be recreated (if it already exists) without dropping, recreating and regenerating object privileges previously granted.

Enabled

When checked, indicates that a trigger is enabled.

During a Create operation, this control is checked and disabled. It is not checked and enabled if a trigger is disabled.

Trigger Body

Defines the PL/SQL block that Oracle executes to fire the trigger.

  Related Topics


Create Triggers Property Sheet: Timing Page
Triggers Property Sheet: Timing Page

The Timing page allows you to specify the conditions that initiate a trigger. This page contains the following information:

Triggering Statement

Fire Trigger

Before/After: Indicates that Oracle fires the trigger before or after executing the triggering statement.

Insert: When checked, indicates that Oracle fire the trigger whenever an INSERT statement adds a row to a table.

Delete: When checked, indicates that Oracle fires the trigger whenever a DELETE statement removes a row from a table.

Update of Columns: Indicates that Oracle fires the trigger whenever an UPDATE statement changes a value in a column selected in the multi-select list. It is only enabled and populated when the Update checkbox is selected.

Trigger for Each Row

When checked, designates the trigger to be a row trigger. Oracle fires a row trigger once for each row that is affected by the triggering statement and meets the optional trigger constraint defined in the Condition field. When not checked, the trigger is a statement trigger and is fired only once when the triggering statement is issued (assuming the optional trigger constraint is met).

Referencing

Old as: New name for default correlation name OLD.

New as: New name for default correlation name NEW.

You can use correlation names in the PL/SQL block and WHEN clause of a row trigger to refer specifically to old and new values of the current row.  The default correlation names are OLD and NEW.

Condition

Specifies the trigger restriction.

The trigger restriction contains a SQL condition that must be satisfied for Oracle to fire the trigger.  This condition must contain correlation names and not a query.  You can only specify a trigger restriction for a row trigger.  Oracle evaluates this condition for each row affected by the triggering statement. See the Oracle7 SQL Reference manual for more information.

  Related Topics


Create View Property Sheet: General Page
View Property Sheet: General Page

The General page allows you to define the primary characteristics of a view such as view name, schema to which it belongs, and query text The General page contains the following information:

View

Name of the view being defined. During a Create operation, you can specify a valid Oracle identifier as the name of the view.

Schema

Schema in which the view should be defined.  The default schema for a new view is the user's default schema. During a Create operation, you can choose a schema from those defined in the connected database.

Query Text

Identifies columns and rows of the table(s) that the view is based on. A view's query can be any SELECT statement without the ORDER BY or FOR UPDATE clauses.  Its select list can contain up to 254 expressions.

  Related Topics


Create View Property Sheet: Aliases Page

The Aliases page consists of a scrolling list of all aliases for the view

  Related Topics


Schema Objects: Storage Page

The Storage page allows you to specify database storage parameters for a particular schema object. This page contains the following information:

Use Cluster Parameters  (Table Property Sheet only)

Indicates that the storage parameters for the table being defined will be obtained from the cluster to which the table belongs. The setting of this control is automatically determined based on whether or not the table is a member of a cluster.

Tablespace

Name of the tablespace that contains the database object being defined.

Extents

Initial Size: Size of the object's first extent. You can enter a value, the minimum being the size of one data block. The default value is the size of five data blocks.

Next Size:  Size of the next extent to be allocated to the object. The default value is the size of five datablocks. The smallest permissible value is the size of one datablock.

Increase Size by:  Percent by which each extent grows (after the second extent) compared to the previous extent.

Minimum Number:  Total number of extents allocated when a segment is created. The default value is one. You can enter a value of one or greater.

Maximum Number: Total number of extents, including the first, that an Oracle database can allocate for the object. There are two extent options available, Unlimited and Value.

Unlimited: When selected, allows you to create a number of extents that is only limited by the amount of contiguous free space in a tablespace.

Value: When selected, allows you to specify the maximum number of extents. If you do not specify a value, the default value applies. The default and maximum values depend on the data block size. You can enter a value of one or greater.  The default value varies.

  Related Topics


Create Schema Object Dialog Box
Create Object Dialog Box

When you select Create from the Object menu, the Create Object dialog box appears. The Create Object dialog box displays all schema object types in an alphabetic list. Select an object type and click on the Create button. The appropriate Create property sheet appears.

If a particular schema object is already selected in the tree list, the object type will be automatically selected in the Create Schema Object list.

  Related Topics


HIDM_VAS_OBJECT_ALTER

  Related Topics


HIDM_VAS_TRUNCATE_PART

  Related Topics


Table/Index Property Sheet: Partition Page

The Partition page allows you to select columns for inclusion as part of a table or index partition. The page consists of the following:

Columns

Partition Columns

Scrolling list displaying columns from the table or index selected for inclusion as part of the partition.

Table Columns / Columns In (Index only)

Scrolling list displaying all columns in a table or, when partitioning an index, all columns indexed within the selected table.

Partitions in Table/Index

Multi-column list displaying all partitions defined within the table or index. Columns of this table consist of the following:

Partition

Name of the partition.

Tablespace

Tablespace to which the partition belongs.

High Value

An ordered list of, separated by commas, corresponding to the Partition Columns list. The values displayed represent the upper-bound for the partition. Values in this list must be greater than the high bound value for the highest existing partition in the table.

New (Table or Create Index property sheet)

Displays the Create Partition property sheet allowing you to create a new partition for the columns chosen in the Partition Columns list.

Edit

Displays the Edit Partition property sheet allowing you to modify the selected partition.

Remove

Deletes the selected partition. More than one partition must exist before the Remove button is enabled.

  Related Topics


Defining a Table Partition

  Related Topics


HIDD_VAOS_PARTCOL_LIST

  Related Topics


HIDD_VAOS_TBCOL_LIST

  Related Topics


Error Messages Dialog Box

The Error Messages dialog box displays PL/SQL error messages generated when creating or applying changes to a function, package, or package body. For error message cause and action, see the Oracle Server Messages manual for your specific release.

  Related Topics


Procedure Property Sheet: General Page

The Procedure property sheet allows you to define a stand-along stored procedure, or procedure to be included as part of a package. The General page consists of the following information:

Name

Name of the procedure being defined.

Schema

Name of the schema containing the procedure. The drop-down list displays the names of all available schemas

Recompile

Recompile the PL/SQL source for the procedure so that it can be stored and executed from within the database.

Dates

Created:  Date the package was originally created.

Last Modified:  Date the package was last modified.

Status

Current status of the package (valid or invalid).

Show Errors/Hide Errors:  Opens or closes the Error Messages dialog box. This button is available when the procedure  status is invalid.

Package Source

PL/SQL source code for the procedure.

  Related Topics


 Function Property Sheet: General Page

The General page allows you to define a stored function. This property sheet consists of the following:

Name

Name of the function being defined.

Schema

Name of the schema containing function.  The drop-down list contains all schemas available through the database connection.

Recompile

Recompile the PL/SQL source for the function so that it can be stored and executed from within the database.

Dates

Created: Date the function was originally created.

Last Modified:  Date the function was last modified.

Status

Current status of the Function (valid or invalid).

Show Errors: Displays the Error Message dialog box listing the errors encountered while trying to compile the function source. This button is only enabled when the function status is invalid. For detailed error message information pertaining to PL/SQL, see the Oracle Server Messages Manual.

Source

Function SQL statements or PL/SQL constructs.

  Related Topics


 Package Body Property Sheet: General Page

The General page allows you to define the body of a stored package. This property sheet consists of the following information:

Name

Name of the package body being defined.

Schema

Name of the schema containing this package body. The drop-down list contains all schemas available through the database connection.

Recompile

Recompile the PL/SQL source for the package body so that it can be stored and executed from within the database.

Source (Package Body)

PL/SQL source code for the package body.

Status

Current status of the package (valid or invalid).

Show Errors/Hide Errors:  Opens or closes the Error Messages dialog box. This button is available when the package status is invalid.

Dates

Created:  Date the package body was originally created.

Modified:  Date the package body was last modified.

  Related Topics


HIDD_VAOS_TPNEW_GEN

  Related Topics


 Edit High Value Dialog Box

The Edit High Value dialog box allows you to specify the partitioning key for the selected column in the partition. Collectively, the values specified for each column define the ordering of the partitions in the table or index. This dialog consists of the following:

Column Name

Name of the selected column.

High Value

Partitioning key value for the column.

  Related Topics


 Schema Objects: Options Page

Use Cluster Parameters  (Table Property Sheet only)

Indicates that the storage parameters for the table being defined will be obtained from the cluster to which the table belongs.

The setting of this control is automatically determined based on whether or not the table is a member of a cluster.

Space Usage

% Free:  Percentage of space in each of the object's data blocks that is reserved for future updates to the object. You can enter values from 0 to 99.

% Used:  Minimum percentage of used space that an Oracle database maintains for each data block of the object. A block becomes a candidate for row insertions when its used space falls below the % Used value. You can enter a value from 1 to 99.  The default value is 40.

Number of Transactions

Initial:  Initial number of transaction entries allocated within each data block allocated to the object. You can enter a value from 1 or 2(for clusters and indexes) to 255.

Maximum:  Maximum number of concurrent transactions that can update a data block allocated to the object. You can enter a value from 1 to 255.

Freelists

Lists:  Number of free lists for each of the free list groups for the table, cluster, or index. You can enter a value of one or greater.  The default value is one.

Groups:  Number of groups of free lists for a table, cluster, or index. You can enter a value of one or greater.  The default value is one.

Parallel

Degree:  The degree of parallelism when creating an index using the parallel query option.

Instances:  Maximum number of instances allowed to participate in parallel query processing.

  Related Topics


 View Property Sheet: Advanced Page

The Advance page allows you to specify options or place constraints on the view. This page consists of the following:

Options

Replace if Exists

When checked, specifies that the view is to be recreated, if it already exists, without dropping, recreating, and regenerating object privileges previously granted on it.

Force

When checked, specifies that the view is to be created regardless of whether the view's base tables exist or the owner of the schema containing the view has privileges on them.

Read Only

When checked, specifies that no deletes, inserts or updates can be performed through the view.

Constraint

Specifies the name assigned to the CHECK OPTION constraint.

With Check Option

When checked, specifies that inserts and updates performed through the view must result in rows that the view query can select.

The CHECK OPTION cannot make this guarantee if there is a subquery in the query of this view or any view on which this view is based.

If you omit this identifier, Oracle automatically assigns the constraint a name of the form:  SYS_Cn, where n is an integer that makes the constraint name unique within the database.

  Related Topics


 Table Property Sheet: Cluster Columns Page

The Cluster Columns page (active when creating a new table) allows you to associate database cluster key columns with columns in a newly created table.

Cluster

Drop-down list displaying all clusters available in the schema selected on the General page of the Table property sheet.

Table Column :  Drop-down list displaying all columns in the new table.

Cluster Column:  Cluster key columns contained within the selected cluster.

To clear the Table Column entries, reselect the current cluster from the drop-down list.

  Related Topics


 HIDD_VAOS_TB_QUERY

  Related Topics


 HIDD_VAOS_RBT_PART

  Related Topics


 HIDD_VAOS_LBT_PART

  Related Topics


 HIDD_EDIT_HIGHVAL_BT

  Related Topics


 HIDD_EDITHV_COL_NAME

  Related Topics


 HIDD_EDIT_SPLIT_BT

  Related Topics


New Table Dialog Box

The New Table dialog box gives you the option of selecting one of two methods for creating a new database table.

Options

Use Table Wizard

Allows  Schema Manager to guide you through the steps of creating a table using a rule-based wizard.

Create Table Manually

Calls up the Create Table property sheet. Using the property sheet allows you to create a customized table

  Related Topics


Creating a New Table

The new table is creating


Table Wizard: Introduction

Page 1 of the Table Wizard allows you to define the table name, schema, and tablespace to which the new table belongs.

What do you want the name of the new table to be?

Enter any valid Oracle identifier. See the Oracle 7 Server SQL Reference Guide for database object naming conventions.

Which schema do you want the table to be part of?

Select one schema from the drop-down list. The list contains all available schema in the database.

Which tablespace do you want to create the table in?

Select one tablespace from the drop-down list. The list contains all tablespaces located in selected schema.

  Related Topics


 Table Wizard: Columns Definition

Page 2 of the Table Wizard allows you to define the table columns.

Column Name

Enter any valid Oracle identifier. For more information on naming conventions, see the Oracle 7 Server SQL Reference Guide.

Column

Select the specific datatype for the column from the drop-down list. For more information on datatype usage, see the Oracle 7 Server Administrator’s Guide.

Length

Specify the number of bytes allowed for values defined in the column.

Precision

Specify the number of digits to the right of the decimal point.

Does this column have a default value? If so, please enter.

Enter an expression that serves as the default value for this column in any rows for which the INSERT statement omits a value for the column.

Insert

Adds the current column definition to the table.

Remove

Removes the current column definition from the table.

Left Arrow

Go to the previously defined column. At lease one column must be defined for this button to be active.

Column Status

Displays the column number and the total number of columns for the table.

Right Arrow

Go to the next defined column.

  Related Topics


 Table Wizard: Primary Key Definition

Page 3 of the Table Wizard allows you to define primary key constraints on table columns.

No, I don’t want to create a primary key.

Selected by default, specifies that no primary keys are to be defined for the table.

Yes, I want to create a primary key.

Specifies that a primary key is to be created. When this option is selected, all columns previously defined on page 2 of the Table Wizard appear in the multi-column list.Click on the Order field for each column to display the position of that column in the primary key. To remove a column from the primary key, click on the or column entry again to pull it out of the sequence of columns. Columns re-order automatically.

  Related Topics


Table Wizard: Primary Key Definition
 Table Wizard: Null and Unique Constraints

Page 4 of the Table Wizard allows you to define null and unique constraints on the columns of the table. The column name and datatype are displayed for each column. You can page through the defined columns by clicking on the left or right arrows.

Can the column value be null?

Yes is selected by default.

Does the column value have to be unique?

No is selected by default.

Left Arrow

Go to the previously defined column. At lease one column must be defined for this button to be active.

Column Status

Displays the column number and the total number of columns for the table.

Right Arrow

Go to the next defined column.

  Related Topics


 Table Wizard: Foreign Key Definitions

Page 5 of the Table Wizard allows you to define foreign key constraints. The column name and datatype are displayed for each column.

Is the column a foreign key?

No, the column is not a foreign key

This setting is selected by default.

Yes, the column is a foreign key

Referenced Schema

Drop-down list displaying all available schema in the current database. By default, the user’s schema appears in the text entry field.

Referenced Table

Drop-down list displaying all available tables in the Reference Schema. This field is only active when a schema is selected

Referenced Column

Drop-down list displaying all columns available in the Referenced Table.

Note: After selecting this option, it may take a few seconds for these fields to become active.

Left Arrow

Go to the previously defined column.

Column Status

Displays the column number and the total number of columns for the table.

Right Arrow

Go to the next defined column.

  Related Topics


 Table Wizard: Check Conditions

Page 6 of the Table Wizard allows you to specify check conditions for table columns. The column name and datatype are displayed for each column.

Does this column have a check condition?

No, the column doesn’t have check condition.

This setting is selected by default.

Yes, the column has a check condition.

When selected, the text entry field becomes active. Examples are given for check constraints. For more information, see Oracle 7 Server SQL Reference.

Left Arrow

Go to the previously defined column.

Column Status

Displays the column number and the total number of columns for the table.

Right Arrow

Go to the next defined column.

  Related Topics


 Final Review

Page 7 of the Table Wizard allows you to view the table definitions you set on the previous pages. This page allows you to re-order the columns using the Up and Down arrows. To change table definitions, or edit column definition, go back to the appropriate page of the Table Wizard.

  Related Topics


 HIDD_VAOS_COLLIST_STATICTEXT

  Related Topics


 HIDD_VAOS_PARTLIST_STATICTEXT

  Related Topics


Snapshot Property Sheet: Cluster Page

The Cluster page allows you to define the cluster to which a snapshot belongs. This property sheet contains the following:

Cluster

Cluster to which the snapshot belongs. The drop-down list displays all clusters contained within the selected schema.

Column Name

Name of the column to be used as part of the snapshot. Click Add to add the column name to the Snapshot Columns list.

Snapshot Columns

Scrolling list of all columns added to the snapshot. Use the Up/Down arrows to reorder the list of columns (column order must match the order in the cluster).

Remove

Deletes the selected snapshot column from the list.

  Related Topics


Creating a Cluster

  Related Topics


Create Like Cluster

  Related Topics


Editing a Cluster

  Related Topics


Creating a Database Link

  Related Topics


Create Like Database Link

  Related Topics


Viewing a Database Link

  Related Topics


Creating a Function

  Related Topics


Create Like Function

  Related Topics


Altering a Function

  Related Topics


Creating an Index

  Related Topics


Create Like Index

  Related Topics


Altering and Index

  Related Topics


Creating a Package Body

  Related Topics


Create Like Package Body

  Related Topics


Editing a Package
Editing a Package Body

  Related Topics


Creating a Package

  Related Topics


Create Like Package

  Related Topics


Editing a Package

  Related Topics


Creating a Procedure

  Related Topics


Create Like Procedure

  Related Topics


Altering a Procedure

  Related Topics


Creating a Refresh Group

  Related Topics


Create Like Refresh Group

  Related Topics


Altering a Refresh Group

  Related Topics


Creating a Sequence

  Related Topics


Create Like Sequence

  Related Topics


Altering a Sequence

  Related Topics


Creating a Snapshot Log

  Related Topics


Create Like Snapshot Log

  Related Topics


Altering a Snapshot Log

  Related Topics


Creating a Snapshot

  Related Topics


Create Like Snapshot

  Related Topics


Editing a Snapshot

  Related Topics


Creating a Synonym

  Related Topics


Create Like Synonym

  Related Topics


Altering a Synonym

  Related Topics


Creating a Table

  Related Topics


Create Like Table

  Related Topics


Altering a Table

  Related Topics


Creating a Trigger

  Related Topics


Create Like Trigger

  Related Topics


Altering a Trigger

  Related Topics


Creating a View

  Related Topics


Create Like View

  Related Topics


Altering a View

  Related Topics


Partition Property Sheet: General Page

The Partition property sheet allows you to define or edit partition parameters. In addition

Name

Name of the partition.

High Values

Multi-column list displaying the Column Name, Datatype, and High Value for the columns selected for inclusion in the partition.

Edit

Displays the Edit High Value dialog box, allowing you to change the high value for the selected column.

Logging

When selected, specifies that modifications to the table partition will be logged in the redo log file.

Exchange Partition

When selected, converts a partition to a non-partitioned table and a table to partition of a partitioned table.

Tables: Drop-down list allowing you to specify the table with which a partition is to be exchanged.

Include Indexes: Specifies that the local index partitions be exchanged with the corresponding regular indexes.

No Validation:  When selected, specifies that the proper collation of rows in the exchanged table are not checked. By default, validation is used. If any row in the exchanged table does not collate properly, an error will be returned.

Parallel

When selected,

Degree

Instances

  Related Topics


Instance Manager

With the Instance Manager you can start up or shut down a database, examine and edit database initialization parameters, manage in-doubt transactions, and manage users' sessions. The Instance Manager manages the following groups:

•	Database

•	Initialization Parameters

•	Stored Configurations

•	Sessions

•	In-Doubt Transactions

  Related Topics


Diconnecting a User's Session
Disconnecting a User's Session

To disconnect a user's session, select the session to disconnect from the Session folder list and choose Disconnect from the Session menu. The Disconnect Session alert box appears to allow you to confirm the action.

  Related Topics


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.

  Related Topics


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. When the database is mounted in exclusive mode, it can only be mounted by 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.

  Related Topics


Database Property Sheet

The Database property sheet displays when the Database container is selected in the tree list. The property sheet consists of three pages:

•	Status

•	Startup

•	Shutdown

  Related Topics


Database Property Sheet: Status Page

The Status page contains information about the status of the current database and the memory assigned to the System Global Area (SGA). The SGA is a shared memory region that contains data and control information for an Oracle instance. For more information about the System Global Area, see the Oracle7 Server Concepts.

The contents of the Status page are described below:

SGA

Database Buffers: Size of the database buffer cache (in bytes).

Fixed Size: Memory allocated to the area of the SGA that contains general information about the state of the database and the instance. No user data stored here (in bytes).

Redo Buffers:  Size of the redo log buffer (in bytes).

Variable Size:  Memory allocated to variable size data structures (in bytes).

Started: Operational status of the database.

Mounted:  Mount status of the database.

Open: Open status of the database.

Other information in this property sheet includes release information and installed options.

Attention: If the database is not running, the message "ORACLE not available" is displayed.

  Related Topics


Database Property Sheet: Startup

The Startup page contains information pertinent to database startup.

Startup Options

Force:  Force an instance to start regardless of the operating circumstances.

Restrict:  Starts an instance in restricted mode. Connections are limited to those users who have been granted the RESTRICTED SESSION system privilege.

Parallel:  Allows multiple instances to access a single database concurrently.

No Mount:  No database will be mounted upon instance startup.

Mount:  Mount a database upon instance startup.

Mount and Open: Mount and open a database upon instance startup.

Don't use Stored Parameters (checkbox)

Parameter File:  Database initialization file (e.g. INIT.ORA).

Attention: The Don't use Stored Parameters checkbox only appears when initialization parameters are stored in the repository. If visible and not checked, a new INIT.ORA file will be created.

  Related Topics


Startup Property Sheet/Database Property Sheet: Startup Page

Startup options allow you to start up the current database in any stage or mode and also allows you to use either a conventional initialization parameter file or a stored configuration.

Startup Options

No Mount:  No database will be mounted upon instance startup.

Mount:  Mount a database upon instance startup.

Mount and Open: Mount and open a database upon instance startup.

Force:  Force an instance to start regardless of the operating circumstances.

Restrict:  Starts an instance in restricted mode. Connections are limited to those users who have been granted the RESTRICTED SESSION system privilege.

Parallel:  Allows multiple instances to access a single database concurrently.

Configuration:  Stored configuration. This option is grayed out if no configurations have been stored in the registry.

Parameter File:  Database initialization file (e.g. init.ora).

Browse/View:  Opens file search dialog box to browse for a parameter file or view the currently selected stored configuration.

START UP

Starts up the database.

  Related Topics


Shutdown Property Sheet/Database Property Sheet: Shutdown Page

The Shutdown page provides you with options for shutting down a database.

If you are shutting down a remote database for the first time using Instance Manger or Backup Manager, make sure you have a local copy of the initialization parameter file before attempting to restart the database.

Shutdown Options

Normal:  Normal database shutdown.

Immediate:  Immediate database shutdown

Abort:  Abort the instance and shut down the database instantaneously.

Property sheet buttons:

Shutdown

Shuts down the database.

Additional Information: See Oracle7 Server Administrator's Guide for more information on database startup and shutdown.

  Related Topics


Sessions Container
Sessions Property Sheet

The Sessions property sheet displays information about the users connected to the database. This property sheet contains the following information.

Session ID

Session identifier.

Serial #

Session serial number, used to uniquely identify a session. In combination with the , 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 USERID 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.

  Related Topics


Forcing a Commit or Rollback

To commit an in-doubt transaction;

1.	Select the transaction to be committed from the Transaction multi-column list.

2.	Choose Force Commit from the Transaction menu or the right-hand select menu.

To roll back an in-doubt transaction,

1.	Select the transaction to be rolled back from the Transaction multi-column list

2.	Choose Force Rollback from the Transaction menu or from the right-hand select menu.

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

  Related Topics


Initialization Parameters Property Sheet

The Initialization Parameter property sheet lists all initialization parameters specified in a stored configuration.

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.

The property sheet consists of the following:

Parameter Name

Name of the initialization parameter.

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

Property sheet buttons:

Apply

Immediately applies changes made to initialization parameters. If database shutdown and restart is required, Instance Manager prompts you accordingly. In either case, Instance Manager asks if you wish to save the changes to a stored configuration.

Save

Saves the current changes to a stored configuration.

Reset

Reverses any changes made to initialization parameters made since the last Apply.

  Related Topics


Editing Initialization Parameters

To edit any initialization parameter, double-click on a specific parameter in the Initialization Parameter List.  The Edit Initialization Parameter dialog box appears.

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

Writing Parameters to a File

To save the parameter changes to a separate file, choose Export Parameters To File from the Tools menu. A standard SaveAs file dialog box appears.

  Related Topics


Initialization Parameters Edit Dialog Box
Edit Initialization Parameters 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.

  Related Topics


Importing Initialization Parameters from a File

You load initialization parameters from a file by choosing Import Parameters From File from the Tools menu. A standard file Open dialog box appears.

  Related Topics


Exporting Initialization Parameters to a File

To save the parameter changes to a separate file, choose Export Parameters To File from the Tools menu. A standard SaveAs file dialog box appears.

  Related Topics


Importing Initialization Parameters from a Database

With Oracle Server release 7.3.2, you can import initialization parameters from a running database. Some of these parameters are "derived" from existing parameters and may not appear in the original INIT.ORA file. To add these derived parameters to the Initialization Parameter List viewing and/or editing, select Import Parameters From Database from the Tools menu. A Warning dialog box appears allowing you to add any or all available derived parameters to those selected for display and/or edit in the Initialization Parameter List.

  Related Topics


Warning Dialog: Derived Parameters List

The Warning dialog box consists of the following:

Selected Parameters

List of derived parameters selected to appear in the Initialization Parameters List. Available Parameters 	List of available derived parameters that may or may not appear in the INIT.ORA file.

Add

Adds a parameter selected in the Available Parameters list to the Selected Parameters list.

Remove

Removes a parameter from the Selected Parameters list.

  Related Topics


Oracle Instance Manager: Repository Startup Options

If you start Instance Manager before starting the Oracle Enterprise Manager console, the Oracle Instance Manager repository startup options dialog box appears.

By default, Supply Repository Details is selected. Click OK to display a second Login Information dialog box, allowing you to connect to the database where an Enterprise Manager repository resides. Selecting Continue without Connecting to Repository allows you to start up Instance Manager, however, you will not be able to edit initialization parameters.

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

  Related Topics


 Save Configuration Dialog Box

The following options allow you to save the currently displayed configuration to the registry.

Configuration Name

User selected configuration name.

Comments

User specified comments that appear in the Stored Configurations multi-column list.

  Related Topics


 Database Property Sheet: Archive Page

The Archive page appears when you connect to an Oracle 8 database with SYSDBA privileges and allows you to specify backup and restore options . This page consists of the following:

Database Log Mode

Specifies whether the connected database is in ARCHIVELOG mode or NOARCHIVELOG mode. For information on switching database archive modes, see Oracle 7 Server Administrator’s Guide.

Automatic Archival

Allows you to specify that redo log files be automatically archived. To enable Automatic archiving upon instance startup, set the LOG_ARCHIVE_START initialization parameter to TRUE. This option is enabled when the connected database is running in ARCHIVELOG mode.

Archive Destination

Specifies the destination where the archive log files are to be created. If you are archiving to disk, it is recommended that a dedicated disk with sufficient storage be used.

Archive Format

Specified the naming convention for the archived log files. ARC, appended with the backup set number (%S) and the backup stamp number (%T), is used to form a unique filename for the backup set.

%P  Backup Piece Number—This value starts at 1 for each backup set and is incremented by 1 as each backup piece is created.

%S  Backup Set Number— This value is a control file counter that is incremented for each backup set. The counter value starts at 1 and is unique for the lifetime of the control file.

%T  Backup Stamp—This value indicates the number of seconds since a fixed reference date/time (currently midnight of January 1, 1988).

Last SCN Archived

The last system change number that was archived. The SCN uniquely identifies the last committed database transaction.

  Related Topics


 Basic Tuning Property Sheet

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.

Basic Tuning Initialization Parameters:

•	compatible

•	db_files

•	db_file_multiblock_read_count

•	db_block_buffers

•	dml_locks

•	global_names

•	log_checkpoint_interval

•	log_archive_start

•	log_buffer

•	max_dump_file_size

•	mts_dispatchers

•	mts_listener_address

•	mts_max_dispatchers

•	mts_max_servers

•	mts_servers

•	processes

•	sequence_cache_entries

•	sequence_cache_hash_buckets

•	shared_pool_size

•	remote_login_passwordfile

•	rollback_segments

Property sheet buttons:

Apply

Immediately applies changes made to initialization parameters. If database shutdown and restart is required, Instance Manager prompts you accordingly. In either case, Instance Manager asks if you wish to save the changes to a stored configuration.

Save

Saves the current changes to a stored configuration.

Reset

Reverses any changes made to initialization parameters made since the last Apply.

  Related Topics


 Instance Specific Property Sheet

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.

Instance-specific Initialization Parameters:

•	background_dump_dest

•	control_files

•	core_dump_dest

•	db_block_size

•	db_domain

•	db_name

•	ifile

•	init_sql_files

•	instance_number

•	license_max_sessions

•	license_max_users

•	license_sessions_warning

•	log_archive_dest

•	rollback_segments

•	user_dump_dest

Property sheet buttons:

Apply

Immediately applies changes made to initialization parameters. If database shutdown and restart is required, Instance Manager prompts you accordingly. In either case, Instance Manager asks if you wish to save the changes to a stored configuration.

Save

Saves the current changes to a stored configuration.

Reset

Reverses any changes made to initialization parameters made since the last Apply.

  Related Topics


 Advanced Tuning Property Sheet

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.

Property sheet buttons:

Apply

Immediately applies changes made to initialization parameters. If database shutdown and restart is required, Instance Manager prompts you accordingly. In either case, Instance Manager asks if you wish to save the changes to a stored configuration.

Save

Saves the current changes to a stored configuration.

Reset

Reverses any changes made to initialization parameters made since the last Apply.

  Related Topics


 Derived Property Sheet

The Derived property sheet, which appears when Instance Manager is run in Advance UI mode, lists initialization parameters that depend on other initialization parameters for their specific value.

Initialization parameters

•	cache_size_threshold

•	cpu_count

•	db_block_lru_latches

•	db_block_size

•	db_file_multiblock_read_count

•	enqueue_resources

•	gc_freelist_groups

•	gc_releasable_locks

•	hash_area_size

•	instance_number

•	log_simultaneous_copies

•	mts_service

•	sessions

•	sort_area_retained_size

•	sort_direct_writes

•	temporary_table_locks

•	transactions

•	transactions_per_rollback_segment

Property sheet buttons:

Apply

Immediately applies changes made to initialization parameters. If database shutdown and restart is required, Instance Manager prompts you accordingly. In either case, Instance Manager asks if you wish to save the changes to a stored configuration.

Save

Saves the current changes to a stored configuration.

Reset

Reverses any changes made to initialization parameters made since the last Apply.

  Related Topics


 Stored Configuration Viewer

The Stored Configuration viewer allows you to view all initialization parameters associated with a specific stored configuration.

Note:  You can not edit initialization parameters from the viewer.

  Related Topics


 Add Initialization Parameter Dialog Box

The Add Initialization Parameter dialog box consists of the following:

Name

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

Value

Valid parameter value.

  Related Topics


Database Menu

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

Startup

Displays the Startup property sheet that provides startup options and parameter file/configuration selection for instance startup.

Shutdown

Displays the Shutdown property sheet that provides standard options for instance shutdown.

Mount

Mounts an Oracle instance that has been started but is not currently mounted.

Open

Opens an Oracle instance that has been mounted but currently is not open.

  Related Topics


Sessions Menu

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

Disconnect

Disconnects any session that is selected from the Sessions container in the tree list.

Restrict

Restricts database access only to those users with the RESTRICTED SESSION system privilege.

Allow All

Allows database access to all users.

  Related Topics


Transactions Menu

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

Force Commit

Commits any transaction selected from the In-Doubt Transactions container in the tree list.

Force Rollback

Rolls back a any transaction selected from the In-Doubt Transactions container in the tree list.

  Related Topics


 Configuration Menu

The Configuration menu allows you to manage any configurations selected from the Stored Configurations container in the tree list.

Remove

Removes any configuration selected from the tree list.

Export to File

Exports any configuration selected from the tree list to an ASCII file.

Add parameter

Allows you to add an initialization parameter to a stored configuration.

Remove parameter

Removes a specific initialization parameter that is selected from the Initialization Parameters property sheet.

  Related Topics


Stored Configurations

Stored configurations allow you to create instance startup configurations that are readily accessible and easily customizable. Unlike initialization parameter files (e.g. INIT.ORA), stored configurations are stored in either the NT or Win95 registry, eliminating the need to search for specific parameter files.

If desired, stored configurations can be exported to an ASCII file for use as an initialization parameter file.

When the Stored Configurations container is selected from the tree list, a multi-column list displays the following information:

•	Configuration Name

•	Description

  Related Topics


Database

When the database is selected from the tree list, three property sheets display the database status, startup, and shutdown. The current database you are logged into is displayed.

  Related Topics


Initialization Parameters

When in Basic UI mode, Basic Tuning and Instance Specific initialization parameters are displayed. If Advanced UI mode is used, property sheets displaying Advanced Tuning and Derived initialization parameters are also displayed.

  Related Topics


In-doubt Transactions

If any distributed transaction commits are interrupted due to system or network problems, Instance Manager lists them in the In-Doubt Transactions container. The multi-column list displays transaction identification, the current state of the transaction, and any comments or advice entered by the user.

  Related Topics


Sessions

Instance Manager allows you to view session information for all users connected to the database.

When the Sessions container is selected from the tree list, a multi-column list displays the following information:

•	Session ID

•	Status

•	Username

•	Schema Name

•	OS User

•	Terminal

•	Machine Name

•	Program

  Related Topics


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, commited, 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

  Related Topics


Creating a Stored Configuration

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.

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 Descriptions column of the Stored Parameters mulit-column list.

  Related Topics


Editing Stored Configurations

To edit a stored configuration:

1.	Select an existing stored configuration from the Stored Configuration container in the tree list. 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.

  Related Topics


Deleting Parameters from a Stored Configuration

To delete an initialization parameter from a stored configuration:

1.	Select an existing stored configuration from the tree list.

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.

  Related Topics


Adding a Parameter to a Stored Configuration

To add an initialization parameter to a stored configuration:

1.	Select the desired stored configuration from the tree list.

2.	From the Configuration menu, choose Add Parameter. The Add Initialization Parameter dialog box appears.

3.	Enter the name of the new initialization parameter.

4.	Enter the startup value for the initialization parameter.

5.	Click OK.

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

  Related Topics


Creating a File from a Stored Configuration

Stored configurations are stored in the 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 tree list.

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 tree list. A standard file Save As dialog box appears.

3.	Specify the desired file information and click OK.

  Related Topics


Deleting a Stored Configuration

To delete a stored configuration:

1.	Select the desired stored configuration from the tree list.

2.	Choose Remove from the Configuration menu or from the context-sensitive menu.

  Related Topics


 HIDM_VAI_SE_ALTER

Not used


 HIDM_VAI_TR_ALTER

Not used


 HIDD_VAI_SHUTDOWN_OPTIONS


 HIDD_VAI_ABOUTBOX

Not used


 HIDD_VAI_CREATE


 HIDD_VAI_SAVE_PARAMETER_FILE


 HID_VAOI_DB_SAVE


 HID_VAOI_DB_START_SHUT


 HIDD_VAOI_STARTUP_OPTIONS


 HIDD_VAOI_SHUTDOWN_OPTIONS


Oracle Backup Manager Overview

Backup Manager

Oracle Backup Manager backs up tablespaces of a database and manages redo logfile archiving. With Oracle Backup Manager, you can:

•	Review the backup status of tablespaces and datafiles

•	Review the logging and archival status of redo log groups and members

•	Shut down or start up the database

•	Create a job script to back up tablespaces of the database

•	Display archive log information

•	Manually archive redo log files

•	Add a new redo log group or member

  Related Topics


Oracle Backup Main Window
Oracle Backup Manager

Backup Manager allows you to create scripts for backing up tablespaces of a database and managing redo logfile archiving. The Oracle Backup Manager main window includes these components:

•	Menu bar

•	Tree list

•	Right panel

  Related Topics


Backup Tree List

The Oracle Backup Manager tree list is located on the left side of Oracle Backup Manager main window. At the highest level, it displays the Database container, which displays the name of the database to which the application is connected. The database container contains two containers:

•	Tablespaces container

•	Redo Log Groups container

•	Right panel

  Related Topics


Backup Tablespaces Container

The Tablespaces object type container contains each tablespace in the database arranged alphabetically in a tree list. A particular tablespace can be expanded to show each of its datafiles.

When you select:

•	The Tablespaces object type container, a multi-column list displays a row of summary information for each tablespace in the database.

•	An individual tablespace, a multi-column list displays a row of summary information for each datafile in the tablespace.

For information about managing tablespaces, see the Oracle7 Server Concepts, the Oracle7 Server Administrator's Guide, and the Oracle7 Server SQL Reference.

  Related Topics


Redo Log Group Containers

The Redo Log Groups object type container contains each redo log group of the database. A particular redo log group can be expanded to show its redo log members contained within a Redo Log Members object type container.

When you select:

•	The Redo Log Groups object type container, a multi-column list displays a row of summary information for each redo log group in the database.

•	An individual redo log group, a property sheet for that redo log group displays.

•	The Redo Log Members object type container for a particular redo log group, a multi-column list displays a row of summary information for each of its redo log members.

•	An individual redo log member, a property sheet for that redo log member displays.

  Related Topics


Backup Right Panel

The display on the right side of the window is determined by the object selected in the tree list. The right side may contain:

•	Multi-column list for the Tablespaces container

•	Multi-column list for the Tablespace container

•	Redo Log Group property sheet

•	Redo Log Member property sheet

  Related Topics


Multi-column List for the Tablespaces Container

When you select the Tablespaces object type container in the tree list, a multi-column list displays on the right. This list includes a row for each tablespace in the database. The columns of the list are:

Status Bar

Hides or shows the Status bar at the bottom of the Console.

Contents

Displays the overview topic of the Oracle Enterprise Manager help system.

Tablespace

Name of the tablespace.

Size (M)

Total size in megabytes of the datafiles that comprise the tablespace.

Backup Status

Backup status of the tablespace: Active (an online backup of this tablespace is currently in progress), Not Active (no online backup of this tablespace is currently in progress); or Offline.

Online Backup Started

Date and time the online backup of this tablespace started. If this column is empty, no online backup of this tablespace is currently in progress.

  Related Topics


Multi-column List for the Tablespace Container

When you select an individual Tablespace object type container in the tree list, a multi-column list displays on the right. This list includes a row for each datafile in the tablespace. The columns of the list are:

Filename

Directory path and filename of this datafile.

File ID

File ID of this datafile.

Status

Status of this datafile: Available, Invalid, or Undefined.

Size (M)

Total size in megabytes of this datafile.

  Related Topics


Property Sheet for a Redo Log Group

When you select a particular redo log group in the tree list, a property sheet for this redo log group displays on the right. The items of this property sheet are:

Group #

Displays the redo log group number for this redo log group.

Use Existing File(s)

Click this button to allow Oracle Enterprise Manager to use existing file(s).

New File(s) Size

Click this button in order to specify the size of the new Redo Log Group file(s).

KM Bytes

If you click the New File(s) Size button, enter the new file(s) size in the Bytes box and click K (default) to specify that the new file(s) size is in kilobytes, or M to specify that the new file(s) size is in megabytes.

Current Members

Displays the filenames and directory paths for the redo log members of this redo log group.

Remove

Disabled in this property sheet.

New Member

Enter a new member for this redo log group in the New Member box.

Click the Browse button to display the Open dialog box, from which you can select the redo log file you want to enter in the New Member box.

Add

Adds a new redo log member to this redo log group.

The Add button is enabled when you enter a new redo log member in the New Member box.

  Related Topics


Property Sheet for a Redo Log Member

When you select a particular redo log member in the tree list, a property sheet for this redo log member displays on the right. The items of this property sheet are:

Filename

New filename of the redo log group member.

Group

Displays the redo log group to which the redo log member belongs.

  Related Topics


Oracle Backup Manager Menus

Backup Manager includes four standard menus, File, View, Log, and Help. It also includes two pull menus that are specific to this application:

•	Backup

•	Logfile

  Related Topics


Backup Menu

The Backup menu includes the following items:

Shutdown Database

Shuts down the database.

Startup Database

Starts up the database.

Restrict Sessions

Makes the database accessible only to users with the RESTRICTED SESSION system privilege. Users already connected are not affected.

Allow All Sessions

Makes the database accessible to all users with the CREATE SESSION system privilege.

Backup Tablespace Wizard

Allows you to create a job script for backing up the tablespaces of the database.

Begin Online Backup

Prepares the selected tablespace for an online backup.

When you choose Begin Online Backup, two columns of the Tablespaces multicolumn list indicate that fact: the Backup Status column changes to "Active,"and the Online Backup Started column shows the data and time the backup was started.

The Begin Online Backup menu item is enabled when an individual tablespace is selected, that tablespace is online, and the backup status of that tablespace is not currently active.

End Online Backup

Notifies the database that the online backup is complete.

When you choose End Online Backup, two columns of the Tablespaces multicolumn list indicate that fact: the Backup Status column changes to "Not Active,"and the Online Backup Started column no longer contains any information for that tablespace.

The End Online Backup menu item is enabled when an individual tablespace is selected, that tablespace is offline, and that tablespace is currently being backed up.

Place Tablespace Online

Places the selected tablespace online.

The Place Tablespace Online menu item is enabled when an individual tablespace is selected, and that tablespace is offline.

Take Tablespace Offline

Places the selected tablespace online.

The Place Tablespace Offline menu item is enabled when an individual tablespace is selected, and that tablespace is online.

Backup Control File

Displays the Backup Control File dialog box, from which you can enter the name and directory location of the backup control file for the database.

  Related Topics


Logfile Menu

The Logfile menu includes the following menu items:

Enable Automatic Archiving

Enables automatic archiving of online redo log files.

Disable Automatic Archiving

Disables automatic archiving of online redo log files.

Show Archive Log Info

Displays archive log information.

Manually Archive

Allows you to manually (explicitly) archive specified redo log files for the current database instance.

Switch Logfile

Allows you to switch redo log groups. Choosing Switch Logfile automatically enables the next redo log group to become the current redo log group.

Force Checkpoint

Forces a checkpoint. During a checkpoint, all modified database buffers are written to the appropriate datafiles.

Add Log Group

Creates a new redo log group for the database.

Drop Log Group

Allows you to remove a redo log group from the database.

The Drop Log Group menu item is enabled when an individual redo log group container is selected.

Add Log Member

Allows you to create a new member for an existing redo log group.

Drop Log Member

Allows you to remove a redo log file from a redo log group.

The Drop Log Member menu item is enabled when an individual redo log file is selected.

  Related Topics


Reviewing the Backup Status of Tablespaces and Datafiles

You can review the backup status of tablespaces and datafiles.

  Related Topics


Reviewing the Status of Redo Log Groups and Members

With the Oracle Backup Manager, you can:

•	Review the logging and archival status of redo log groups

•	Review the logging and archival status of redo log members

  Related Topics


Creating a Job Script to Back Up Tablespaces

To create a backup job script in order to back up one or more tablespaces of the database, choose Backup Tablespace Wizard from the Backup menu. The Backup Tablespace Wizard displays.

Attention: It is best to create a separate backup job script for each database you plan to back up, as it is highly unlikely that the data structures of any two databases would match.

The Backup Tablespace Wizard includes four pages that you complete in order to create a backup job script, which you can then run from the Job subsystem of the Console.

The Backup Wizard contains four pages:

•	Page 1

•	Page 2

•	Page 3

•	Page 4

  Related Topics


Page 1 of the Backup Wizard

Page 1 of the Tablespace Backup Wizard allows you to specify the status of the database that will be required in order to complete the backup. The buttons are:

Up

Click this button if you want to back up the tablespace(s) when the database is still operating (up). (This is the default.)

Tablespaces online (hot): Click this button if you want to back up the tablespace(s) when the database is up and the tablespace(s) are online.

This button is enabled only when the Up button is selected. When the Up button is selected, this button is selected by default.

Tablespaces offine (cold): Click this button if you want to back up the tablespace(s) when the database is up and the tablespace(s) are offline.

This button is enabled only when the Up button is selected.

Down

Click this button if you want to back up the tablespace(s) when the database is down.

Attention: The backup job script you are creating will not perform the tasks of bringing the database up or down, or bringing the tablespaces online or offline. Instead, the backup job script will require that the conditions you specify are met before the backup is initiated.

  Related Topics


Page 2 of the Backup Wizard

Page 2 of the Tablespace Backup Wizard allows you to specify the particular tablespaces of the database to be backed up. The items of Page 2 are:

Selected Tablespaces

Lists the tablespaces of the database that you want to back up.

Arrow buttons

Use the left arrow button to add tablespaces selected in the Available Tablespaces box to the list of tablespaces in the Selected Tablespaces box.

Use the right arrow button to remove tablespaces selected from the Selected Tablespaces box to the list of tablespaces in the Available Tablespaces box.

Double-clicking on a tablespace in either box performs the same operation the arrow keys perform —it transfers the tablespace from one of these boxes to the other.

Available Tablespaces

Select the tablespaces in this box that you want to back up.

  Related Topics


Page 3 of the Backup Wizard

Page 3 of the Tablespace Backup Wizard allows you to specify the backup method to be used during backup. The items of Page 3 are:

Write to Disk

Click this button to specify that the backup be written to disk. (This backup method is the default.)

Directory: Enter the directory path for the backup file in this box.

The Directory box is enabled only when the Write to Disk button is selected.

Write to Tape

Click this button to specify that the backup be written to tape.

Tape Device: Enter the device ID of the tape drive on the host to be used for backup.

The Tape Device box is enabled only when the Write to Tape button is selected.

Archive Using OS Command Line

Click this button if you want to archive the backed up tablespaces using a command at the operating system prompt.

Command: In this box, enter the command to be invoked at the operating system prompt.

All tablespaces selected for backup on page 2 of the Backup Wizard are converted to a datafiles. Type %S in the command string to back up the tablespace datafiles.

For example: tar cf /vol/tape %S

The Command box is enabled only when the Archive Using OS Command Line button is selected.

  Related Topics


Page 4 of the Backup Wizard

Page 4 of the Tablespace Backup Wizard allows you to specify the filename of the file that will contain the backup job script you are creating using the Tablespace Backup Wizard. The items of Page 4 are:

Script Name

In this box, enter the filename and directory path of the file that will contain the backup script.

Click the Browse button in order to use a standard Save As dialog box to select a file that will contain the backup job script. This file will then appear in the Filename box.

Finish

Click this button to create the backup job script. (This script is not a TCL script.)

If creating the backup script was not successful, a message indicates how to correct the problem. If the backup script was created successfully, a message indicates that fact.

Attention: In order to run the backup job that you have created, use the Job subsystem of the Console.

  Related Topics


Shutting Down and Starting Up the Database

The Backup menu includes options for shutting down and starting an Oracle database:

•	Shut Down Database

•	Start Up Database

  Related Topics


Shutting Down the Database

To shut down the database, choose Shutdown Database from the Backup menu. The Shutdown property sheet appears.

Attention: Before shutting down a release 7.1 or later database, you must connect as SYSDBA or SYSOPER. Before shutting down a release 7.0 database, you must connect as INTERNAL.

The items of the Shutdown property sheet are:

Shutdown Options

Normal:  Shuts down the database in normal mode.

Immediate:  Shuts down the database in immediate mode. (This is the default.)

Abort:  Shuts down the database in the abort mode.

Shut Down

Click this button to shut down the database in the mode you have selected.

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

  Related Topics


Starting Up the Database

To start up the database, choose Startup Database from the Backup menu. The Startup property sheet appears.

Attention: Before starting up a release 7.1 or later database, you must connect as SYSDBA or SYSOPER. Before starting up a release 7.0 database, you must connect as INTERNAL.

The items of the Startup property sheet are:

Startup Options

Force:  Forces an instance to start regardless of the operating circumstances.

Restrict:  Starts an instance in restricted mode. Connections are limited to those users who have been granted the RESTRICTED SESSION system privilege.

Parallel:  Allows multiple instances to access a single database concurrently.

No Mount:  Starts up the instance and mounts the database. The database is accessible only to database administrators.

Mount:  Mounts a database upon instance startup. The database is accessible only to database administators.

Mount and Open: Starts up the instance, and mounts and opens the database.

Stored Parameters

This checkbox only appears when initialization parameters are stored in the repository. If visible and not checked, a new INIT.ORA file will be created.

Parameter File

Name of the parameter file used to start the instance.

If you do not specify a parameter file, Oracle Enterprise Manager looks for the parameter file in the default location on your local machine. For information about the default location for the parameter file, see your operating system-specific Oracle documentation.

Browse:  Displays the standard Open dialog box, allowing you to locate the parameter file.

Startup

Click this button to start up the database.

  Related Topics


Displaying Archive Log Information

To display information from the archive log, choose Show Archive Log Info from the Logfile menu. The Archive Log Information window displays.

The Archive Log Information window includes the following information:

Database Log Mode

Indicates the currently enabled archive log mode: Archive Mode or No Archive Mode.

Automatic Archival

Indicates the current status of automatic archival: Enabled or Disabled.

Archive Destination

Indicates the current destination device or directory for the archived redo log group.

Oldest Online Log Sequence

Indicates the log sequence number of the oldest filled online redo log group.

Current Log Sequence

Indicates the log sequence number of the current online redo log group.

  Related Topics


Manually Archiving Redo Log Files

To manually (explicitly) archive redo log files, choose Manually Archive from the Logfile menu. A secondary menu offers you the following options for manually archiving redo log files.

Current

Archives the current redo log group, as well as any filled, but not yet archived online redo log groups.

All

Archives all filled, but not yet archived, online redo log groups.

Next

Archives the next online redo log group that has been filled but not yet archived.

Group

Archives the selected redo log group.

Logfile

Archives the redo log group associated with the selected redo log file (member).

Regardless of which Manually Archive submenu item you choose, the Archive Logfiles dialog box appears, allowing you to specify the destination directory for the archived redo log groups. The Archive Logfiles dialog box contains the following item:

Destination Directory

In this box, enter the destination directory for the redo log group(s) you are archiving manually. (The default destination directory is that specified in the Archive Destination field of the Archive Log Information window.)

Click this button to display a standard Open dialog box, from which you can select a destination directory for the redo log group(s) you are archiving manually.

  Related Topics


Adding a New Redo Log Group or Member

Among other menu items, the Backup menu includes:

•	Add Redo Group

•	Add Redo Member

  Related Topics


Adding a New Redo Log Group to the Database
Redo Log Group Property Sheet

The Redo Log Group property sheet allows you to create a new redo log group, or view the parameters of an existing redo log group. The Create Redo Log Group property sheet includes these elements:

Group #

Displays the redo log group number that Oracle Enterprise Manager has automatically generated for this new redo log group. (For example, if redo log groups 1 and 2 already exist for the database, 3 appears by default in the Group # box.)

Files

Use Existing File(s): Allows reuse of an existing file(s).

New File(s) Size : Allows you to specify the size of the new Redo Log Group file(s) (Kilobytes or Megabytes).

Current Members

Displays the current members of this redo log group.

The Current Members box is empty when the Create Redo Log Group property sheet first displays. After you add a new member to this redo log group, the new member then appears in this box.

Remove

Remove the redo log group member that is selected in the Current Members box.

New Member

Name of the new member.

...

Displays a standard Open dialog box, from which you can select the redo log file you want to enter in the New Member box.

Add

Adds the new member for this redo log group that is specified in the New Member box.

Create

Creates the new redo log group.

  Related Topics


Adding a New Member to an Existing Redo Log Group

To create a new member for an existing redo log group, choose Add Log Member from the Logfile menu. The Create Redo Log Member property sheet appears. The Create Redo Log Member property sheet includes these elements:

Filename

Enter the filename of the new member of the redo log group shown in the Group box.

Group

From this box, select the redo log group to which you want to add a new member.

Use Existing File

Click this button to specify that Oracle Enterprise Manager reuse an existing file.

New File

Click this button to specify that Oracle Enterprise Manager create a new file.

  Related Topics


Using Help

Click on a Help button to learn about the task at hand. You can also press the F1 key at any time.

  Related Topics


Specifying Destination Files

For more information, see the Backup Control File dialog box and the Archive Logfiles dialog box.

  Related Topics


The Backup Control File Dialog Box

Choosing Backup Control File from the Backup menu displays the Backup Control File dialog box, allowing you to specify the name and directory location of the backup control file for the database.

  Related Topics


The Archive Logfiles Dialog Box

When you choose Manually Archive submenu item from the Logfile menu, the Archive Logfiles dialog box displays. This dialog box allows you to specify the destination directory for the archived redo log groups. The Archive Logfiles dialog box contains the following items:

Destination Directory

In this box, enter the destination directory for the redo log group(s) you are archiving manually. (The default destination directory is that specified in the Archive Destination field of the Archive Log Information window.)

Click this button to display a standard Open dialog box, from which you can select a destination directory for the redo log group(s) you are archiving manually.

  Related Topics


Oracle 8 Backup and Recovery from this point


Backup Manager Oracle 8
Oracle Backup Manager

The Oracle Backup Manager provides an easy-to-use graphical user interface for Recovery Manager, the advanced backup and recovery utility for Oracle 8. Backup Manager Wizards (both backup and restore operations) guide you through complex backup and restore operations.

•	Backup Wizard

•	Restore Wizard

  Related Topics


Backup Menu

Backup Set

Allows you to define a backup set for the selected object. Selected objects must consist of the same type (datafiles or archivelogs).

Image Copy

Allows you to define an image copy for the selected object. An image copy contains a single input file (datafile, archivelog, or control file).

Backup Wizard

Simplifies the job of backing up a database, tablespaces, datafiles, or archivelogs using an intelligent Wizard to guide you through the backup process.

  Related Topics


Recover Menu

Restore

Restore the selected database objects in the tree or multi-column list. Restoring a datafile or tablespace requires that these objects be offline, or that the database be closed.

Switch

Switches the datafile copy to the current datafile.

Recover

Recover the selected object in the tree list.

Error Status

Displays Needs Recovery status for datafiles.

Restore Wizard

Starts the Restore Wizard that guides you through the restore, switch, and recover processes.

  Related Topics


Catalog Menu

The Catalog menu allows you to manage the recovery catalog, a separate database normally residing on a remote system that contains information about the structure and previous backups of the target database.

Resync

Re-synchronizes the Recovery Catalog for the target database. The recovery catalog must be periodically resynced from the target database in order to ensure the catalog is up-to-date. The recovery catalog is not updated automatically when a log switch occurs or when an log is archived.

Reset

Reset the Recovery Catalog for the target database. You must reset the recovery catalog if the target database had been previously opened with the RESETLOGS option.

Register

Register the target database with the Recovery Catalog. You must register the target database with the recovery catalog before attempting any backup or recovery operation for the first time.

Connect string

Allows you to define the connect string to the Recovery catalog.

Use Recovery Catalog

Use the Recovery Catalog or V$views for database backup and recovery.

  Related Topics


Database Menu

The Database menu allows you to control primary database operations such as startup, shutdown, or enabling various backup and recovery options.

Shutdown

Shuts down the target database.

Startup

Starts a target database instance.

Enable Automatic Archiving

Starts the ARCH process that archives the online log files every time the LGWR process switches log files.

Disable Automatic Archiving

Stops automatic archiving of online log files.

Manually Archive

Allows you to manually archive the current redo log group (Current), all filled redo log groups (All), the next redo log group (Next), a select redo log group (Group), or an individual logfile member (Logfile).

Switch Logfile

Switches the current redo log group.

Force Checkpoint

Triggers a checkpoint. Note: After a checkpoint has been triggered, the redo in the redo log files is no longer useful for crash/instance recovery.

Add Log Group

Creates a new redo log group.

Drop Log Group

Deletes the selected redo log group.

Add Log Member

Adds a logfile to a redo log group.

Drop Log Member

Deletes the selected redo logfile member.

  Related Topics


Channel Menu

The Channel menu allows you to define connections to one or more devices for backup and recovery. Each definition is called a channel. At least one channel must be defined before performing a backup, copy, restore, or recover operation.

Create

Allows you to create a new channel definition.

Create Like

Allows you to create a new channel with the same connection properties as the selected channel.

Remove

Deletes the selected channel.

  Related Topics


Backup Wizard Introduction
Backup Wizard: Introduction

The Introduction page of the Backup Wizard allows you to select from a variety of backup operations.

The type of backup you select determines which procedure the Backup Wizard guides you through. The following backups types are available:

Database

Tablespaces

Datafiles

Archivelogs Only

For more information on backups and related strategies, see your Oracle Server Administrator’s Guide.

  Related Topics


Backup Wizard Tablespaces
Backup Wizard: Tablespaces

This page allows you to select the tablespaces you want to back up in the target database.

Selected Tablespaces

Lists the tablespaces of the database that you want to back up.

Arrow buttons

Use the down arrow button to add tablespaces selected in the Available Tablespaces box to the list of tablespaces in the Selected Tablespaces box.

Use the up arrow button to remove tablespaces selected from the Selected Tablespaces box to the list of tablespaces in the Available Tablespaces box.

Double-clicking on a tablespace in either box performs the same operation the arrow keys perform —it transfers the tablespace from one of these boxes to the other.

Available Tablespaces

Select the tablespaces in this box that you want to back up.

  Related Topics


Summary Page

The Summary page appears when you click the Finish button from either the Restore or Backup Wizard. Information about the backup or restore job you just created using the Wizard is summarized before submission to the Oracle Enterprise Manager job system. The following areas are summarized: JOB NAME, JOB DESCRIPTION, JOB ACTION, and JOB DETAILS.

Clicking OK submits the job the Oracle Enterprise Manager job system.

  Related Topics


Archive Logfiles Dialog Box

The Archive Logfiles dialog box allows you to specify the device and or directory to which archived logfiles will be stored. By default, the current archive logfile directory is displayed.

  Related Topics


Schedule Page
Backup Set/Image Copy Property Sheet: Schedule Page

The Schedule page allows you to schedule the execution of a backup or image copy.

Execute

Drop-down list allowing you to select the frequency of backup or image copy execution. The choices are Immediately, Once, On Interval, On Day of Week, and On Date of Month.

•	Immediately submits the task as soon as you finish the setup process. The task executes only one time.

•	Once schedules the task only one time at the date and time you choose.

•	On Interval allows you to schedule a specific time interval between task executions. The interval can be a combination of hours and minutes, or number of days. Select the value you want to change and click on the scroll buttons. You can also type in a new value.

•	On Day of Week allows you to schedule the task on one or multiple days (Sunday, Monday, etc.) of the week. Click on the days of the week to select the days you want the task scheduled.

•	On Date of Month allows you to schedule the task on one or multiple days (1 - 31) of the month. Click on the dates of the month to select the dates you want the task scheduled.

Note: If you choose a day, such as 31, that is not in a month, the job will not be run in that month.

Start Execution

Choose the first date and time that you want the task executed. This is the starting time for any task scheduled on an interval.

•	Select the month, day, or year in the Date field and click on the scroll buttons to change the value. You can also type in new values.

•	Select the hour, minute, or AM/PM in the Time field and click on the scroll buttons to change the value. You can also type in new values.

End Execution

Choose the last date and time that you want the task executed. This option does not apply if you chose the Immediately or Once execution options.

•	Select the month, day, or year in the Date field and click on the scroll buttons to change the value. You can also type in new values.

•	Select the hour, minute, or AM/PM in the Time field and click on the scroll buttons to change the value. You can also type in new values.

Time Zone

Select the time zone from the pull-down list. The choices are Agent, Console, and GMT.

Note: Only the Agent time zone is available with this release.

•	Agent: The agent schedules the task execution at each destination based on the actual system time of each agent. Tasks are not necessarily run simultaneously.

•	Console: The agent schedules the task execution simultaneously on all destinations based on the system time of the Console.

•	GMT: The agent schedules the task execution simultaneously on all destinations based on Greenwich Mean Time.

  Related Topics


Redo Log Group Property Sheet General Page
Redo Log Group Property Sheet: General Page

The Redo Log Group property sheet allows you to create a new redo log group, or view the parameters of an existing redo log group. The Create Redo Log Group property sheet includes these elements:

Group #

Displays the redo log group number that Oracle Enterprise Manager has automatically generated for this new redo log group. (For example, if redo log groups 1 and 2 already exist for the database, 3 appears by default in the Group # box.)

Files

Use Existing File(s): Allows reuse of an existing file(s).

New File(s) Size : Allows you to specify the size of the new Redo Log Group file(s) (Kilobytes or Megabytes).

Current Members

Displays the current members of this redo log group.

The Current Members box is empty when the Create Redo Log Group property sheet first displays. After you add a new member to this redo log group, the new member then appears in this box.

Remove

Remove the redo log group member that is selected in the Current Members box.

New Member

Name of the new member.

...

Displays a standard Open dialog box, from which you can select the redo log file you want to enter in the New Member box.

Add

Adds the new member for this redo log group that is specified in the New Member box.

Create

Creates the new redo log group.

  Related Topics


Redo Log Member Dialog Box

The Redo Log Member dialog box allows you to view an existing or add a new redo log member to a redo log group in the target database.

Filename

Filename of the new member of the redo log group shown in the Group box. When creating a new redo log member, this field is editable.

Group

Redo log group to which the redo log member belongs. When creating a new redo log member, you can select from all groups available in the target database using the drop-down list.

Use Existing File (Create Only)

When selected, specifies that Oracle Backup Manager reuse an existing file.

New File (Create Only)

When selected, specifies that Oracle Backup Manager create a new file.

  Related Topics


Channels Property Sheet General Page
Channels Property Sheet: General Page

The General page allows you to create, view, or modify a channel. A channel establishes a connection from Backup Manager to the target database for backup or restore operations. Multiple channels can be created to allow multiple backup sets or file copies to be read or written in parallel by a single job.

Note: At least one channel must exist before performing backup or restore operations.

Channel Name

User-specified name of the channel.

Default Channel for this database

When checked, specifies that the current channel be used by default whenever the currently connected target database is accessed.

Channel available for all databases

When checked, makes the current channel available to any target database.

Channel Type

Drop-down list allowing you to select from one of the following device types:

Disk:  Backup sets written to disk.

Device Name:  Specifies that a port-specific string specifying the name of a sequential I/O device be used.

Device Type:  Specifies either a disk or platform-specific specification of a sequential I/O device or device access method be used.

Format: Unique backup set name.  The following parameters can be used

%p Backup piece number within the backup set. This value starts at 1 for each backup set and is incremented by 1 as each backup piece is created.

%s Backup set number. The counter value starts at 1 and is unique for the lifetime of the controlfile.

%t Backup set timestamp. Note: The combination of %s and %t can be used to form a unique name for the backup set.

Destination (active when Channel Type is set to Disk): Drive and path where backup sets are stored.

Device Name: Port-specific string specifying the name of a sequential I/O device.

Device Type: Disk or platform-specific specification of a sequential I/O device or device access method.

Parameters: Port-specific string specifying parameters pertaining to the allocated I/O device.

  Related Topics


Switch Property Sheet
Switch Property Sheet: General Page

The General page allows you to convert a copy of a datafile into a datafile used by the target database. When a switch is performed, the datafile copy is registered with the controlfile, thus making it a datafile that can be accessed by the database.

Tag

When selected, a drop-down list allows you to select the datafile copy you wish to make current via the datafiles’ tag.

Datafile

When selected, allows you to select from a list of available datafile copies. The multi-column list displays the following file attributes:

CPDate  Date and time of the last datafile backup or image copy.

Tag  Tag associated with the datafile, if any.

Name  Actual name of the datafile.

  Related Topics


Backup Set Property Sheet General Page
Backup Set Property Sheet: General Page

(Datafiles and Tablespaces)

The General page allows you to specify the backup level, a tag, and whether or not the control file is backed up. To backup a range of datafiles, use the Backup Wizard.

Choose an incremental backup level

Click on the up or down arrow to specify a backup level. Backup Manager allows you to specify up to five levels of backup:   0: full backup, 1-4: incremental backup

Enter or choose a tag

Optionally, you can specify a tag by entering a character string of less than 30 characters. You can also use the drop-down list box to select an existing tag.

Defining a tag gives you a symbolic way to refer to a collection of image copies or backup sets. You can also use tags to specify specific input files to a restore or switch.

Include control file with this backup

Select this option if you want the control file backed up with the backup set.

  Related Topics


Datafiles Property Sheet General Page
Datafiles Property Sheet: General Page

The General page lets you view general information such as name, location, and size of the selected datafile. This page also allows you to change the online/offline status of the selected datafile.

Name

Full path and name of the selected datafile. This field is read-only.

Tablespace

Tablespace to which the datafile belongs. This field is read-only.

Status

The current datafile online/offline status is selected. You can change the status of the datafile by clicking on the desired option and then clicking the Apply button

Size (K bytes)

Datafile size in kilobytes.

  Related Topics


Tablespace Property Sheet General Page
Tablespace Property Sheet: General Page

The Tablespace property sheet allows you to alter the status of the tablespace selected in the tree list. In addition, all datafiles contained within the tablespace are displayed.

Name

The full path and name of the selected tablespace.

Status

Indicates the current status of the selected tablespace and also allows you to change the status. The following options are available:

Online:  Places the selected tablespace online.

Offline:  Takes the selected tablespace offline. When this option is selected, a drop-down list appears to the right allowing you to select the following priorities:

Normal:-Used if no error conditions exist for any of the datafiles of the tablespace.

Temporary-Used if there are error conditions for one or more datafiles of the tablespace.

Immediate- Note: You cannot take a tablespace offline immediately if the database is running in NOARCHIVELOG mode.

Read Only:  Makes the selected tablespace read-only to prevent further write operations on the datafiles in the tablespace.

Datafiles

A scrolling multi-column list displaying all datafiles contained within the tablespace. For each datafile, the full name and path, size (K), date and time of the last backup, whether the datafile needs to be backed up, and any datafile errors are displayed.

  Related Topics


Backup Set Property Sheet Parameters Page
Backup Set Property Sheet: Parameters Page

The Parameters page allows you to set storage parameters for the current backup set.

Max. Files per Backup Set

When checked, it allows you to set the maximum number of files that can be placed in a single backup set. If the number of files selected for the current backup exceed this number, multiple backup sets are created. In addition, multiple channels, if defined and available, will also be used.

Format

Format

Unique backup set name.  The following parameters can be used:

%p Backup piece number within the backup set. This value starts at 1 for each backup set and is incremented by 1 as each backup piece is created.

%s Backup set number. The counter value starts at 1 and is unique for the lifetime of the controlfile.

%t Backup set timestamp. Note: The combination of %s and %t can be used to form a unique name for the backup set.

Destination (visible when Channel Type is set to Disk))

Drive and path where backup sets are stored.

  Related Topics


Image Copy Property Sheet General Page
Image Copy Property Sheet: General Page

The General Page allows you to enter the requisite information for a complete image copy of a datafile, or control file. An image copy is a direct copy of the selected input file that contains no header or trailer blocks.

Image copy backups can be written only to disk. No compression is used. Restoring a file with an image copy involves substituting the image copy for the actual file.

Destination

The drive and/or full path to the directory where you store image copies. The filename of the selected input file is used by default. The default backup directory is defined by the default channel for the target database.

Channel

Use the drop-down list to select an available channel.

Note: Before performing an image copy, you must define at least one channel.

Enter or choose a tag

Optionally, you can specify a tag by entering a character string of less than 30 characters. You can also use the drop-down list box to select an existing tag.

Defining a tag gives you a symbolic way to refer to a collection of image copies or backup sets. You can also use tags to specify specific input files to a restore or switch.

  Related Topics


Backup Set Property Sheet Channels Page
 Backup Set Property Sheet: Channels Page

The Channels page allows you to select the channel(s) used for the current backup set.

Choose channel type

Drop-down list allowing you to select one of the following channel types:

Disk:  Displays all available channels that write to disk.

Device:  Displays all available channels that write to a sequential I/O device or use an OS-specific device access method.

Selected channels

List of channels selected for use by the current backup.

To remove an entry from the Selected channels list, double-click on the entry.

Available channels

List of available channels for use by the current backup.

To add an entry to the Selected channels list, double-click on the Available channels entry.

  Related Topics


Control File Property Sheet General Page
 Control File Property Sheet: General Page

This property sheet displays all available control files used by the target database. The multi-column list displays the name and location of the control file as well as its status.

  Related Topics


Restore Property Sheet Rename Page
 Restore Property Sheet: Rename Page

The Rename page allows you to restore the selected datafile(s) to a new location. When datafiles are restored to a new location, they are considered datafile copies. For this reason, a switch is automatically performed.

Original Name

The full path and filename of the selected datafile(s). This field is not editable.

New Name

Enter a new filename and/or a new path.

You can copy all or sections of the Original Name entry and paste it into the New Name field by highlighting the desired text and selecting the desired action from the pop-up menu.

  Related Topics


Archived Logs Property Sheet General Page
 Archived Logs Property Sheet: General Page

The General page allows you to view parameters for the selected archived redo log file.

Filename

Full path and name of the archived redo log file.

Thread No.

Numeric archived redo logfile identifier used for multiple instance environments. Thread numbers are used to identify archived redo logfiles belonging to a specific instance when Oracle, with the Parallel Server option, is run in parallel mode. A default value of 1 is used for single instance environments.

Log Sequence No.

Unique numeric identifier for the selected archived redo log file. During media recovery, Oracle applies redo log files in ascending order by using the log sequence number of the necessary archived and online redo log files.

Size (K Bytes)

Physical size of the redo log file in kilobytes.

Backed Up

Status as to whether the selected redo log file has been backed up

  Related Topics


Channels Property Sheet Limits Page
 Channels Property Sheet: Limits Page

The Limits page allows you to set the limits for any backup or copy operation. For any setting, you move the slider bar to change the its value. The middle number on the scale changes according to the position of the slider bar.

Maximum Capacity (Mb)

When checked, it allows you set the maximum number of megabytes that a backup operation can write to a single backup piece.

Maximum Read Rate (Kb/s)

When checked, it allows you to control the number of blocks per second read by a backup or copy operation from or to any input datafile. Controlling the read rate ensures that a backup or copy operation does not consume excessive disk bandwidth, which can degrade online performance.

Maximum Open Files

When checked, it allows you to control the maximum number of input files that a backup operation can have open simultaneously. Setting maximum number of open files is particularly useful when backing up a large number of archivelogs into a single backup set.

  Related Topics


Archived Logs Property Sheet Record Page
 Archived Logs Property Sheet: Record Page

The Record page allows you to view the time stamp and system change number of the selected archived log.

Starts At

Date: Archive date and time for the first member in the redo log group.

System Change No.: Low SCN for the first member of the redo log group

Ends At

Date: Archive date and time for the last member of the redo log group.

System Change No.: High SCN for the last member of the redo log group.

  Related Topics


Jobs Property Sheet Job Job History Page
 Jobs Property Sheet: Job History page

The Job History page contains a list of previous job activities, such as multiple executions of a job. These are jobs that have been submitted to an agent and have executed successfully or unsuccessfully. This page also lists deleted jobs. You cannot modify these jobs.

Job Name

The name of the job.

Status

Status of job is one of the following:

Completed: The job has executed successfully.

Failed: The job execution has failed.

Deleted: The job has been deleted.

Execution Start Time

Time when the job started or was deleted. Because the order of agent notifications may vary, it is possible that the Console receives a completed or failed notification before a running notification. If this happens, the start time displays Unknown.

Execution End Time

Time when the job finished, failed, or was deleted.

  Related Topics


Jobs Property Sheet Job Library Page
 Jobs Property Sheet: Job Library Page

The Job Library page displays jobs created and saved using either the Backup or Restore Wizard. This is useful if you want to submit the same job at different times or if you want to make minor modifications to an existing job without having to redefine it from scratch using one of the Wizards.

Double-click on an entry in the Job Library list to start the associated Wizard with the stored parameters already set. You can either submit the job, or modify the settings and save it again.

Job Name

Application generated name of the job.

Job Description

Application generated description of the job.

  Related Topics


Datafiles Property Sheet Backup Page
 Datafiles Property Sheet: Backup Page

The Backup page lists all scheduled backups for the selected datafile.

Time

Date and time of the backup.

Backup Type

Indicates whether or not the backup is a backup set or an image copy. Note: Datafile backup sets may also contain a controlfile backup.

Level

Indicates whether a backup of the datafile is full or incremental. Levels range from 0  (full backup) to 4. Levels one to four are user-defined and allow you to set up different levels of incremental backups. For example, you might set up the following backup scheme:

Level 0-Monthly full backup

Level 1-Weekly incremental

Level 2-Daily incremental

Tag

User-defined name representing one or more backup sets or image copies. The maximum length of a tag is 30 characters.

Name

Full path and name of a datafile.

  Related Topics


Jobs Property Sheet Active Jobs Page
 Jobs Property Sheet: Active Jobs Page

The Active Jobs page contains a summary of the active backup and restore jobs that have been submitted to the Oracle Enterprise Manager job system and are not yet completed. You cannot modify these jobs.

Job Name

Name of the job.

Status

Execution status of the job. Status may be one of the following:

Submitted: The job has been submitted to the agent at the job destination.

Scheduled: The job has been successfully delivered to the agent and is scheduled for execution.

Running: The job execution has started. After the job executes, the job execution is displayed in the Job History page. If this is the last scheduled execution of the job, the job is removed from the Active Jobs page. Otherwise, the job remains in the Active Jobs page and has the status of Submitted. Unless you view the Active Jobs page at the exact time that the job is executing, you would not see the Running status.

Pending Deletion: The job has been selected for deletion. When the deletion is successful, the job is removed from the Active Jobs page and added to the Job History page.

Next Execution Time

Date and time of the job start time.

Job Type

Backup or Restore.

  Related Topics


Backup Wizard Datafiles
 Backup Wizard: Datafiles

This page allows you to select the available datafiles you want to back up in the target database.

Available Datafiles

List of available datafiles in the target database.

Arrow buttons

Use the down arrow button to add datafiles selected in the Available Datafiles box to the list of datafiles in the Selected Datafiles box.

Use the up arrow button to remove datafiles selected from the Selected Datafiles box to the list of datafiles in the Available Datafiles box.

Double-clicking on a datafile in either box performs the same operation the arrow keys perform —it transfers the datafile from one box to the other.

Selected Datafiles

Lists the datafiles of that you have chosen to back up.

Include controlfile

Backs up the target database controlfile along with the datafiles.

  Related Topics


Backup Wizard Archived Logs
 Backup Wizard: Archived Logs

This page allows you to select archived log files for backup.

None (Not available if Archivelogs Only is selected on the Introduction page)

Selected by default, no archived logs are backed up.

All

When selected, all archive logs for the target database are backed up.

Selected

When selected, allows you to choose a range of archived log files by date.

From

Choose the first date and time of the archived log you want backed up.

•	Select the month, day, or year in the Date field and click on the scroll buttons to change the value. You can also type in new values.

•	Select the hour, minute, or AM/PM in the Time field and click on the scroll buttons to change the value. You can also type in new values.

Until

Choose the last date and time of the archived log you want backed up.

•	Select the month, day, or year in the Date field and click on the scroll buttons to change the value. You can also type in new values.

•	Select the hour, minute, or AM/PM in the Time field and click on the scroll buttons to change the value. You can also type in new values.

Delete the archived logs after they have been backed up.

When selected, deletes the archived log file after backup is performed.

  Related Topics


Backup Wizard Channels
 Backup Wizard: Channels

The Channels page allows you to select the channel(s) used for the current backup operation.

Choose channel type

Drop-down list allowing you to select one of the following channel types:

Disk:  Displays all available channels that write to disk.

Device:  Displays all available channels that write to a sequential I/O device or use an OS-specific device access method.

Selected channels

List of channels selected for use by the current restore operation.

Arrow buttons

Use the left arrow button to add channels selected in the Available channels box to the list of channels in the Selected channels box.

Use the right arrow button to remove channels selected from the Selected channels box to the list of channels in the Available Channels box.

Double-clicking on a channel in either box performs the same operation the arrow keys perform —it transfers the channel from one box to the other.

Available channels

List of available channels for use by the current restore operation.

  Related Topics


Backup Wizard Backup Options
 Backup Wizard: Backup Options

The Backup Options page allows you to define general options for the backup set.

Enter or choose a tag

Optionally, you can specify a tag by entering a character string of less than 30 characters. You can also use the drop-down list box to select an existing tag.

Defining a tag gives you a symbolic way to refer to a collection of image copies or backup sets. You can also use tags to specify specific input files to a restore or switch.

Choose an incremental backup level

Click on the up or down arrow to specify a backup level. Backup Manager allows you to specify up to five levels of backup:   0: full backup, 1-4: incremental backup

  Related Topics


Backup Wizard Parameters
 Backup Wizard: Parameters

The Parameters page allows you to set storage parameters for the current backup set.

Max. Files per Backup Set

When checked, it allows you to set the maximum number of files that can be placed in a single backup set. If the number of files selected for the current backup exceed this number, multiple backup sets are created. In addition, multiple channels, if defined and available, will also be used.

Format

Format

Unique backup set name.  The following parameters can be used:

%p Backup piece number within the backup set. This value starts at 1 for each backup set and is incremented by 1 as each backup piece is created.

%s Backup set number. The counter value starts at 1 and is unique for the lifetime of the controlfile.

%t Backup set timestamp. Note: The combination of %s and %t can be used to form a unique name for the backup set.

Destination (visible when Channel Type is set to Disk))

Drive and path where backup sets are stored.

  Related Topics


Backup Wizard Schedule
 Backup Wizard: Schedule Page

The Schedule page allows you to schedule the execution of a backup or image copy.

Execute

Drop-down list allowing you to select the frequency of backup or image copy execution. The choices are Immediately, Once, On Interval, On Day of Week, and On Date of Month.

•	Immediately submits the task as soon as you finish the setup process. The task executes only one time.

•	Once schedules the task only one time at the date and time you choose.

•	On Interval allows you to schedule a specific time interval between task executions. The interval can be a combination of hours and minutes, or number of days. Select the value you want to change and click on the scroll buttons. You can also type in a new value.

•	On Day of Week allows you to schedule the task on one or multiple days (Sunday, Monday, etc.) of the week. Click on the days of the week to select the days you want the task scheduled.

•	On Date of Month allows you to schedule the task on one or multiple days (1 - 31) of the month. Click on the dates of the month to select the dates you want the task scheduled.

Note: If you choose a day, such as 31, that is not in a month, the job will not be run in that month.

Start Execution

Choose the first date and time that you want the task executed. This is the starting time for any task scheduled on an interval.

•	Select the month, day, or year in the Date field and click on the scroll buttons to change the value. You can also type in new values.

•	Select the hour, minute, or AM/PM in the Time field and click on the scroll buttons to change the value. You can also type in new values.

End Execution

Choose the last date and time that you want the task executed. This option does not apply if you chose the Immediately or Once execution options.

•	Select the month, day, or year in the Date field and click on the scroll buttons to change the value. You can also type in new values.

•	Select the hour, minute, or AM/PM in the Time field and click on the scroll buttons to change the value. You can also type in new values.

Time Zone

Select the time zone from the pull-down list. The choices are Agent, Console, and GMT.

Note: Only the Agent time zone is available with this release.

•	Agent: The agent schedules the task execution at each destination based on the actual system time of each agent. Tasks are not necessarily run simultaneously.

•	Console: The agent schedules the task execution simultaneously on all destinations based on the system time of the Console.

•	GMT: The agent schedules the task execution simultaneously on all destinations based on Greenwich Mean Time.

  Related Topics


Restore Wizard Introduction
 Restore Wizard: Introduction

The Introduction page of the Restore Wizard allows you to select from the following types of restore operations:

Database

Tablespaces

Datafiles

The type of restore you select determines which procedure the Restore Wizard guides you through.

Depending on the status of the target database (ARCHIVELOG, NOARCHIVELOG, mounted and open, or mounted only), some options will be disabled.

For more information on restore operations and related strategies, see your Oracle Server Administrator’s Guide.

  Related Topics


Restore Wizard Channels
 Restore Wizard: Channels

The Channels page allows you to select the channel(s) used for the current restore operation.

Choose channel type

Drop-down list allowing you to select one of the following channel types:

Disk:  Displays all available channels that write to disk.

Device:  Displays all available channels that write to a sequential I/O device or use an OS-specific device access method.

Selected channels

List of channels selected for use by the current restore operation.

Arrow buttons

Use the left arrow button to add channels selected in the Available channels box to the list of channels in the Selected channels box.

Use the right arrow button to remove channels selected from the Selected channels box to the list of channels in the Available Channels box.

Double-clicking on a channel in either box performs the same operation the arrow keys perform —it transfers the channel from one box to the other.

Available channels

List of available channels for use by the current restore operation.

  Related Topics


Restore Wizard Datafiles
 Restore Wizard: Datafiles

This page allows you to select the available datafiles you want to restore in the target database.

Available Datafiles

Lists available datafiles in the target database.

Arrow buttons

Use the down arrow button to add datafiles selected in the Available Datafiles box to the list of datafiles in the Selected Datafiles box.

Use the up arrow button to remove datafiles selected from the Selected Datafiles box to the list of datafiles in the Available Datafiles box.

Double-clicking on a datafile in either box performs the same operation the arrow keys perform —it transfers the datafile from one box to the other.

Selected Datafiles

Lists the datafiles in the target database you have chosen to restore.

  Related Topics


Restore Wizard Tablespaces
 Restore Wizard: Tablespaces

This page allows you to select the tablespaces you want to restore in the target database.

Available Tablespaces

Lists the tablespaces available in the target database.

Arrow buttons

Use the down arrow button to add tablespaces selected in the Available Tablespaces box to the list of tablespaces in the Selected Tablespaces box.

Use the up arrow button to remove tablespaces selected in the Selected Tablespaces box to the list of tablespaces in the Available Tablespaces box.

Double-clicking on a tablespace in either box performs the same operation the arrow keys perform —it transfers the tablespace from one of these boxes to the other.

Selected Tablespaces

Lists the tablespaces of the database that you want to restore.

  Related Topics


Backup Set Property Sheet General Page
 Backup Set Property Sheet: General Page (Archivelogs)

The General page allows you to specify that archivelog files be deleted after backup. To backup a range of archived log files, use the Backup Wizard.

Delete the archived logs after they have been backed up

When checked, archived log files are deleted after being backed up.

  Related Topics


Recover Property Sheet General Page
 Recover Property Sheet: General Page

The General page allows you to select the channel for recovery of the selected object in the tree list. This property sheet consists of the following:

Choose channel type

Drop-down list allowing you to select one of the following channel types:

Disk:  Displays all available channels that read from disk.

Device:  Displays all available channels that read from a sequential I/O device or use an OS-specific device access method.

Selected channels

List of channels selected for use by the current recover operation.

To remove an entry from the Selected channels list, double-click on the entry.

Available channels

List of available channels for use by the current recover operation.

To add an entry to the Selected channels list, double-click on the Available channels entry.

  Related Topics


Restore Property Sheet Channels Page
 Restore Property Sheet: Channels Page

The Channels page allows you to select the channel(s) used for the current restore operation.

Choose channel type

Drop-down list allowing you to select one of the following channel types:

Disk:  Displays all available channels that write to disk.

Device:  Displays all available channels that write to a sequential I/O device or use an OS-specific device access method.

Selected channels

List of channels selected for use by the current restore operation.

Arrow buttons

Use the left arrow button to add channels selected in the Available channels box to the list of channels in the Selected channels box.

Use the right arrow button to remove channels selected from the Selected channels box to the list of channels in the Available Channels box.

Double-clicking on a channel in either box performs the same operation the arrow keys perform —it transfers the channel from one box to the other.

Available channels

List of available channels for use by the current restore operation.

  Related Topics


Backup Wizard Save or Submit
 Backup Wizard: Save/Submit

The Save/Submit page allows you to specify job identification and submission options.

Backup job identification

Name: Name of the backup job.

Description: Intuitive description of the job.

Operation

Save this backup configuration to the library:  When selected, saves the job to the Backup Manager Job Library. Once saved in the Job Library, the Wizard settings are stored for future use and can be easily reused or modified.

Initiate backup:  When selected, the job is immediately submitted to the Oracle Enterprise Manager job system for execution.

  Related Topics


Restore Property Sheet General Page
 Restore Property Sheet: General Page

The General page allows you to specify the type of restore operation performed by Backup Manager.

Select restore method

Allow Rman to choose the best available backup set.:  Selected by default, this option allows Backup Manager to select automatically the most recent backup set or file copy available.

Restore to Tag:  When selected, allows you to select the backup set or file copy using the files’ tag. Select the desired tag using the drop-down list. If backup sets or file copies are found with the same tag, the tag with the most recent timestamp is selected.

Recover object after restore

When selected, recovery is automatically performed after the restore operation.

  Related Topics


 Until Dialog Box

The Until dialog box allows you to restore the target database to a specific point in time. By default, the most recent time available is used.

  Related Topics


Restore Wizard Rename
 Restore Wizard: Rename

The Rename page allows you to restore the selected datafile(s) to a new location. When datafiles are restored to a new location, they are considered datafile copies. For this reason, a switch is automatically performed.

Original Name

The full path and filename of the selected datafile(s). This field is not editable.

New Name

Enter a new filename and/or a new path.

You can copy all or sections of the Original Name entry and paste it into the New Name field by highlighting the desired text and selecting the desired action from the pop-up menu.

  Related Topics


 Error Datafiles Dialog Box

The Error Datafiles dialog box appears automatically if a problem is found with one or more datafiles.

Name

The full path and name of the datafile.

Tablespace

Name of the tablespace to which the datafile belongs.

Error

Error, if any, generated by the Recovery Manager utility. See your Oracle 8 Recovery Manager documentation for more information.

Needs Recovery

Datafile status as to whether the datafile needs recovery. Depending on the type error, the column may be blank.

File Status

Recovery status for the datafile. In most cases, RECOVERY will be the default entry.

  Related Topics


Backup Wizard Introduction
 Backup Wizard: Introduction

The Introduction page of the Backup Wizard allows you to select the type of backup you want to perform: database, tablespaces, datafiles, or archive logs only.

The type of backup you select determines which procedure the Backup Wizard guides you through. The following backups types are available:

Database

Tablespaces

Datafiles

Archivelogs Only

NOTE: In NOARCHIVELOG mode, only the Database backup option is available.

For more information on backups and related strategies, see your Oracle Server Administrator’s Guide.

  Related Topics


IDs bellow to be used in future version of Backup Manager


HIDM_VAR_BK_RESTRICTSESS

String Table

Allow only users with RESTRICTED SESSION privileges to connect


HIDM_VAR_BK_ALLOWALLSESS

String Table

Allow all users to connect.


HIDM_VAR_BK_BKUPTS

String Table

Run a wizard to create tablespace backup script \n Backup Wizard


HIDM_VAR_BK_BEGOLBKUP

String Table

Put the selected tablespace in online backup mode.


HIDM_VAR_BK_ENDOLBKUP

String Table

Take the selected tablespace out of online backup mode.


HIDM_VAR_BK_TSONLINE

String table

Put the selected tablespace online.


HIDM_VAR_BK_TSOFFLINE

String Table

Take the selected tablespace offline.


HIDM_VAR_BK_CFILE

String table

Back up the control file.


HIDM_VAR_LG_ARCLOGINFO

String Table

Display information about the archive log status.


HID_TEST_RMANDEBUGMODE

Not used.


HIDD_VAR_CHANNELS_LOW

not used


HIDD_VAR_RESTORE_UNTIL


HIDD_VAR_RC_ADDTOCATALOG


HIDD_VAR_RC_CHANGE_CATALOG


HIDD_VAR_STORED_SCRIPTS


HIDD_VAR_RECOVER


HIDD_VAR_UNTIL


HIDD_VAR_JOBS


HIDD_LIB_JOBNAME


HIDD_VAR_RECOVER_UNTIL


HIDD_VAR_JOB_PROGRESS


HIDD_VAR_JOB_OUTPUT


HIDD_VAR_RECOVERABLE


HIDD_VAR_ARCHIVED_LOGS_SEL


HIDD_VAR_RECOVER_GENERAL

Informational dialog? If you choose OK now, the database will be backed up to the most recent time possible.


Oracle Data Manager

Oracle Data Manager allows you to transfer data to and from Oracle databases. Data Manager displays a tree listing and User and Table property sheets to allow you to manipulate and view objects. Wizards are accessed with the Data menu.

Oracle Data Manager Wizards

Oracle Data Manager provides wizards for an easy and efficient interface for exporting, importing, and loading data to and from an Oracle database.

Export Wizard

Import Wizard

Load Wizard

Note: The Advanced Mode option is always activated with Data Manager.

Attention: Data Manager is only supported on release 7.3.3 or later of the Oracle Database server.

  Related Topics


Data Manager Job Tasks
Oracle Data Manager Tasks

The Data Manager export, import, and load functions can also be run as job tasks submitted through the Job Scheduling system.

Data Manager Export task options

Data Manager Import task options

Data Manager Load task options

  Related Topics


Oracle Data Manager: Data Menu
Data Menu

The Data Manager menu accesses wizards for exporting, importing, and loading data to and from an Oracle database.

Export Wizard

Import Wizard

Load Wizard

  Related Topics


Data Manager: User Property Sheet

The General page of the Data Manager Table property sheet lists the number of objects that the selected user owns. These objects include:

•	Tables

•	Snapshots

•	Refresh Groups

•	Jobs

•	Database Links

•	Sequences

•	Clusters

•	Synonyms

Note: The fields in this page are read-only and cannot be updated.

  Related Topics


Data Manager: Table Property Sheet

The General page of the Data Manager Table property sheet lists the number of objects that are contained in the selected table. These objects include:

•	Constraints

•	Table Grants

•	Table Indexes

•	Column Comments

•	Referential Restraints

•	Triggers

Note: The fields in this page are read-only and cannot be updated.

  Related Topics


Oracle Data Manager Export Wizard: Page 1
Data Manager Export Wizard: Page 1

The Export wizard guides through the process of exporting data from an Oracle database. This exported data can be later imported into an Oracle database. The Export option is accessed from the Data menu.

Hint: Before you choose the Export menu option, select the objects you want to export in the tree in the Data Manager window. These objects will automatically be selected for export in the wizard.

Local Machine

Specifies that the file that will contain exported data is on the local machine.

Remote Machine

Specifies that the exported data file is on the remote machine that contains the connected database. This option uses the Job Scheduling system and is only available when the Console is running.

Filename

Enter the name of the file where you want to store the exported data. Use the Browse button to locate an existing file or change the directory where the file is located.

  Related Topics


Oracle Data Manager Export Wizard: Page 2
Data Manager Export Wizard: Page 2

Note: Any objects selected in the tree in the Data Manager window appear in the Selected Objects window. You can remove any objects with the up-arrow button.

Expand the Available Objects tree to locate the objects you want to export.

In the list of Available Objects, select the items that you want to export. Use the arrow buttons to move objects to and from the Selected Objects window.

  Related Topics


Oracle Data Manager Export Wizard: Page 3
Data Manager Export Wizard: Page 3

Check the following associated objects that you want to export.

•	Grants

•	Indexes

•	Rows

•	Constraints

Specify whether the data path employed should be conventional (relative) or direct (explicit). Check the Direct box for a faster export that bypasses SQL command processing.

  Related Topics


Oracle Data Manager Export Wizard: Page 4
Data Manager Export Wizard: Page 4

Record Length

Enter the length of the desired record file, in bytes, or use operating system defaults.

Buffer Size

Enter the size of the buffer used to retrieve data rows, in bytes, or use operating system defaults.

Check Generate Log File if you want to have a log file written during the export. Enter a filename or choose Browse to use an existing file or change directories.

  Related Topics


Oracle Data Manager Export Wizard: Page 5
Data Manager Export Wizard: Page 5

Accept the defaults or specify advanced options for the export.

Export Read-Consistent View of Data

Specifies that data should be exported in read-consistent format.

Merge Extents for Import

Specifies if you want to compress table data into one extent during an import.

Increment Type

Specifies whether the Export operation should be non-incremental, complete, cumulative, or incremental. An incremental export only exports tables that have changed since the last export. A cumulative export exports tables that have changed since the last cumulative or complete export. A complete exports all tables and updates the tables used to track incremental and cumulative exports.

Statistics Type

Specifies whether statistical analysis should be performed when exported data is imported back into an  Oracle database, and whether it should be computed or an estimate.

  Related Topics


Oracle Data Manager Export Wizard: Page 6
Data Manager Export Wizard: Page 6

You can execute the export task immediately or schedule the task for various times. This page is the similar to the Schedule Page of the Job Scheduling system.

  Related Topics


Oracle Data Manager
Data Manager Export Wizard: Page 7

The export setups that have been defined display for you to review. Choose Finish to schedule the export or move back to any page to update the setups. If you choose Finish, the Export Status dialog displays.

  Related Topics


Oracle Data Manager Load Wizard: Page 1
Data Manager Load Wizard: Page 1

The Load wizard guides you through the process of loading data into an Oracle database. This data is in text or other non-Oracle data format. The Load option is accessed from the Data menu.

Local Machine

Specifies that the control file is on the local machine.

Remote Machine

Specifies that the control file is on the remote machine that contains the connected database. This option uses the Job Scheduling system and is only available when the Console is running.

Control File

Enter the name of the control file. Use the Browse button to locate an existing file or change the directory where the file is located. The control file tells the Oracle SQL language utility how to interpret the data contained in an ASCII file containing delimited or fixed-length rows.

You must specify an existing control filename. An example of a simple control file is:

LOAD DATA

INFILE *

INTO TABLE dept

FIELDS TERMINATED BY ’,’ OPTIONALLY ENCLOSED BY ’”’

(deptno, dname, loc)

BEGINDATA

12,Research,”Saratoga”

10,”Accounting”,Cleveland

LOAD DATA must be the first statement in a control file.

INFILE identifies the data file. An asterisk (*) signifies that the data is in the control file.

INTO identifies the table where the data is loaded. INTO requires the table to be empty; APPEND allows records to be added.

Usually field data is separated by commas (,). Optionally, field data can be enclosed in quotes.

Column names are enclosed in parentheses ( ) and separated with commas.

BEGINDATA signifies where the data begins in the control file.

For information on control files, see the the Oracle7 Server Utilities Guide.

  Related Topics


Oracle Data Manager Load Wizard: Page 2
Data Manager Load Wizard: Page 2

Specify any optional files that are used or created during the load.

Data File

Specifies the name of the ASCII data file to be loaded. Type the full path and filename, or click Browse to locate the target filename. If this field is left blank, the Loader uses the control filename and assumes the data is is in the control file.

Log File

Specifies the name of the log file, which registers the information of  the loading process. Type the full path and filename or click Browse to locate an existing log file to use.

If this field is left blank, the Loader uses the control filename.

Bad File

Specifies the name of the bad file, which holds information on data records that caused errors and were rejected by the Oracle database. Type the full path and filename or click Browse to locate an existing bad file.

Discard File

Specifies the name of the discard file, which holds information on data records that were not rejected by the Oracle database but were nevertheless not inserted. Type the full path and filename or click Browse to locate an existing discard file.

Parallel File

Specifies an Oracle Parallel Server file.

  Related Topics


Oracle Data Manager Load Wizard: Page 3
Data Manager Load Wizard: Page 3

Specify any Advanced Load options.

Data Path

Specifies whether data will be loaded into the Oracle7 database through the conventional data path or the direct data path.

Records to Skip

Type the number of logical records from the beginning of the file that should be skipped during the load operation. This parameter is useful when you need to restart a load operation that has previously been interrupted.

Records to Load

Type the number of records to load. If you have previously specified a number of records to skip, the load operation begins after skipping those records.

Rows per Commit

Type the number of rows to commit to the bind array

Maximum Errors

Type the maximum number of errors to allow before the load operation terminates.

Maximum Discards

Type the maximum number of discarded records to allow before the load operation terminates.

Maximum Bind Array

Type the maximum size of the bind array, in bytes.

  Related Topics


Oracle Data Manager Load Wizard: Page 4
Data Manager Load Wizard: Page 4

You can execute the load task immediately or schedule the task for various times. This page is the similar to the Schedule Page of the Job Scheduling system.

  Related Topics


Oracle Data Manager Load Wizard: Page 5
Data Manager Load Wizard: Page 5

The load setups that have been defined display for you to review. Choose Finish to schedule the load or move back to any page to update the setups. If you choose Finish, the Load Status dialog displays.

  Related Topics


Oracle Data Manager Import Wizard: Page 1
Data Manager Import Wizard: Page 1

The Import wizard guides you through the process of importing data to an Oracle database. This data has been previously exported from an Oracle database. The Import option is accessed from the Data menu.

Local Machine

Specifies that the file to be imported is on the local machine.

Remote Machine (available with a future release)

Filename

Enter the name of the file that contains the exported data you want to import. Use the Browse button to locate an existing file or change the directory where the file is located.

  Related Topics


Oracle Data Manager Import Wizard: Page 2
Data Manager Import Wizard: Page 2

Importable Objects

This tree contains the importable objects in the specified file. Select an object in the tree and choose the down arrow button to move the object to the Selected Objects tree.

Selected Objects

This tree contains the objects that will be imported. To remove an object from the list, select the object and choose the up arrow button.

  Related Topics


Oracle Data Manager Import Wizard: Page 3
Data Manager Import Wizard: Page 3

Associated Objects

Specifies whether the Import operation will include user rights (Grants), rows, indexes, or constraints.

Note: You can import table definitions without needing to import table rows.

Ignore Creation Errors

Click here if you do not want Import to report "object already exist" errors when attempting to create the new database objects.

  Related Topics


Oracle Data Manager Import Wizard: Page 4
Data Manager Import Wizard: Page 4

Record Length

Type the length of the desired record file, in bytes, or accept the operating system default.

Buffer Size

Type the size of the buffer used to transfer data rows, in bytes, or accept the operating system default.

Generate Log File

Generates an import log file.

Note: If you click Generate Log File you must also type a Log File name, as described below.

Log File

Specifies the name of the log file to capture screen output during the import operation. Type the full path and filename or click Browse to locate the target filename.

  Related Topics


Oracle Data Manager Import Wizard: Page 5
Data Manager Import Wizard: Page 5

Increment Type

None

Specifies not to make an incremental import.

Restore

Specifies a restored incremental import.

System

Specifies a system incremental import.

Write Index Commands to a File

Creates a file to hold index-creation SQL statements generated during the import operation.

Note: If you click Write Index Commands to a File, you must also type an Index File name, as described below.

Index File

Specifies the name of the index file to use during the import operation. Type the full path and filename or click Browse to locate the target filename.

Commit after each array

COMMITs each array after it is inserted (one at a time).

Overwrite existing data files

If you are importing a full database, specifies that the imported data overwrites the existing data files that currently comprise the database.

  Related Topics


Oracle Data Manager Import Wizard: Page 6
Data Manager Import Wizard: Page 6

You can execute the import task immediately or schedule the task for various times. This page is the similar to the Schedule Page of the Job Scheduling system.

  Related Topics


Oracle Data Manager Import Wizard: Page 7
Data Manager Import Wizard: Page 7

The import setups that have been defined display for you to review. Choose Finish to schedule the import or move back to any page to update the setups. If you choose Finish, the Import Status dialog displays.

  Related Topics


Oracle Data Manager
Export Status Dialog

This dialog displays status of the export. Check the listing for any errors or problems.

  Related Topics


Oracle Data Manager
Import Status Dialog

This dialog displays status of the import. Check the listing for any errors or problems.

  Related Topics


Oracle Data Manager
Load Status Dialog

This dialog displays status of the load. Check the listing for any errors or problems.

  Related Topics


Data Manager User Credentials
Oracle Data Manager User Credentials

Enter the user and password for the database. This overrides any default user credentials that have been set up.

  Related Topics


Export options: Oracle Data Manager
Oracle Data Manager Export Options

Oracle Data Manager Export task is used to transfer specified tables, database objects, or a full database to an operating system file. You specify objects and parameters with the export options.

Model Database

Select the model database from the list box. This database provides examples of tables and users that are available for exporting. If only one destination database has been selected, it would be the model database. If multiple destination databases are selected, the model database would contain tables and users common to all the destination databases.

Export File

Specifies the operating system file that will contain the exported data. Type the full path and filename or click Browse to locate the target filename.

To Be Exported

Specifies whether you are exporting tables, users, or an entire database to an operating system file.

Note: If you click Tables or Users you must also click Specify.

Specify

Specify allows you to select from the list of database objects available to export.

Objects to Export

Specifies whether the Export operation will include user rights (Grants), rows, indexes, or constraints.

Note: You can export table definitions without needing to export table rows.

User...

The User option allows you to specify a username and password for the selected destination database. This username and password override the preferred credentials for the database.

Advanced...

Select Advanced options if you want to edit record length or buffer size, or generate log files during the export.

  Related Topics


Export options: Oracle Data Manager
Data Manager Export Objects

The Export Objects dialog box displays a list of the objects available to export. The objects displayed vary depending on whether you previously specified that Tables or Users be exported.

Select the desired object(s), then click the appropriate button below to make the object available for export.

Export

Moves the selected object to the Selected Tables/Owner list.

Export All

Exports all objects displayed in the Remaining Tables/Owners list. All objects move to the Selected Tables/Owner list.

Don't Export

Removes an object from the Selected Tables/Owner list. The object moves to the Remaining Tables/Owner list.

Export None

Removes all objects from the Selected Tables/Owner list. All objects move back to the Remaining Tables/Owner list.

OK

Saves your changes and close the dialog box.

  Related Topics


Advanced Export Options dialog box

The Advanced Export Options dialog box enables you to create an export log file and edit such advanced export parameters as record length and buffer size.

Record Length

Type the length of the desired record file, in bytes.

Buffer Size

Type the size of the buffer used to retrieve data rows, in bytes.

Log File

Specifies the name of the log file to use during the export operation. Type the full path and filename or click Browse to locate the target filename.

Export Read-Consistent View of Data

Click here to specify that data should be exported in read-consistent format.

Increment Type

Specifies whether the Export operation should be non-incremental, complete, cumulative, or incremental.

Record Export Operation in Database

Specifies if you want the export process recorded in the database.

Statistics Type

Specifies whether statistical analysis should be performed when exported data is imported back into the Oracle database, and whether it should be computed or an estimate.

Data Path

Specifies whether the data path employed should be conventional (relative )or direct.(explicit).

Merge Extents for Import

Specifies if you want to compress table data into one extent during an import.

  Related Topics


RIDH_Data_Mgr_db_Export_Advance


Import options: Oracle Data Manager dialog box
Oracle Data Manager Import Options

Oracle Data Manager Import task is used to transfer specified tables, database objects, or a full database into an Oracle database.

Unless you want to import only tables, you may select as many options as desired:

Import File

Specifies the operating system file to export into the Oracle database. Type the full path and filename or click Browse to locate the target filename.

To Be Imported

Specifies whether you will import tables, users, or an entire database.

Note: If you click Tables or Users you must also click Specify.

Specify

Select Specify to select specific Tables or Users from the list of tables or users available to import.

Objects to Import

Specifies whether the Import operation will include user rights (Grants), rows, indexes, or constraints.

Note: You can import table definitions without needing to import table rows.

Ignore Creation Errors

Click here if you do not want Import to report "object already exist" errors when attempting to create the new database objects.

User...

The User option allows you to specify a username and password for the selected destination database. This username and password override the preferred credentials for the database.

Advanced...

Select Advanced options if you want to edit record length or buffer size, or generate a log file during import.

  Related Topics


Import Objects dialog box
Data Manager Import Objects

The Import Objects dialog box displays a list of the objects available to import. The objects displayed vary depending on whether you previously specified that Tables or Owners be imported.

Select the desired object(s), then click the appropriate button below to make the object available for import.

Import

Moves the selected object to the Selected Tables/Owner list.

Import All

Import all objects displayed in the Remaining Tables/Owners list. All objects move to the Selected Tabless/Owner list.

Don't Import

Removes an object from the Selected Tables/Owner list. The object moves to the Remaining Tables/Owner list.

Import None

Removes all objects from the Selected Tables/Owner list All objects move back to the Remaining Tables/Owner list.

OK

Saves your changes and close the dialog box.

  Related Topics


RIDH_Data_Mgr_db_Import_Objects


Advanced Import Options dialog box

The Advanced Import Options dialog box enables you to create an import log time and edit such advanced import parameters as record length and buffer size.

Record Length

Type the length of the desired record file, in bytes.

Buffer Size

Type the size of the buffer used to transfer data rows, in bytes.

Generate Log File

Generates an import log file.

Note: If you click Generate Log File you must also type a Log File name, as described below.

Log File

Specifies the name of the log file to capture screen output during the import operation. Type the full path and filename or click Browse to locate the target filename.

Increment Type

None

Specifies not to make an incremental import.

Restore

Specifies a restored incremental import.

System

Specifies a system incremental import.

Write Index Commands to a File

Creates a file to hold index-creation SQL statements generated during the import operation.

Note: If you click Write Index Commands to a File, you must also type an Index File name, as described below.

Index File

Specifies the name of the index file to use during the import operation. Type the full path and filename or click Browse to locate the target filename.

Commit after each array

COMMITs each array after it is inserted (one at a time).

Overwrite existing data files

If you are importing a full database, specifies that the imported data overwrites the existing data files that currently comprise the database.

  Related Topics


RIDH_Data_Mgr_db_Import_Advance


Load options: Oracle Data Manager
Data Manager Load Options

The Data Manager Load task options are used to create a SQL*Loader control file for loading data into an Oracle database. The control file tells the Oracle SQL language utility how to interpret the data contained in an ASCII file containing delimited or fixed-length rows. The control file also specifies any optional associated files.

Control File

Specifies the name of the control file. Type the full path and filename or click Browse to locate the target filename.

Optional Files

Data File

Specifies the name of the ASCII data file to be loaded. Type the full path and filename or click Browse to locate the target filename.

If this field is left blank, the Loader uses the control filename.

Log File

Specifies the name of the log file, which registers the information of  the loading process. Type the full path and filename or click Browse to locate an existing log file to use.

If this field is left blank, the Loader uses the control filename.

Bad File

Specifies the name of the bad file, which holds information on data records that caused errors and were rejected by the Oracle database. Type the full path and filename or click Browse to locate an existing bad file.

Discard File

Specifies the name of the discard file, which holds information on data records that were not rejected by the Oracle database but were nevertheless not inserted. Type the full path and filename or click Browse to locate an existing discard file.

User...

The User option allows you to specify a username and password for the selected destination database. This username and password override the preferred credentials for the database.

Advanced...

Select Advanced options if you want to edit any of the parameters SQL*Loader uses to load your ASCII files, such as records to skip, rows per COMMIT, and data path.

  Related Topics


Advanced SQL Loader dialog box
Advanced Load Options dialog box

The Advanced Load Options dialog box enables you to edit parameters used to load ASCII files.

Records to Skip

Type the number of logical records from the beginning of the file that should be skipped during the load operation. This parameter is useful when you need to restart a load operation that has previously been interrupted.

Records to Load

Type the number of records to load. If you have previously specified a number of records to skip, the load operation begins after skipping those records.

Rows per Commit

Type the number of rows to commit to the bind array

Maximum Errors

Type the maximum number of errors to allow before the load operation terminates.

Maximum Discards

Type the maximum number of discarded records to allow before the load operation terminates.

Maximum Bind Array

Type the maximum size of the bind array, in bytes.

Data Path

Specifies whether data will be loaded into the Oracle7 database through the conventional data path or the direct data path.

  Related Topics


RIDH_Data_Mgr_db_Loader_Advance


SQL Worksheet

Using the SQL Worksheet, you can enter, edit, and execute SQL and PL/SQL code. You can also execute the Server Manager DBA commands. You can also run scripts from the SQL Worksheet. The SQL Worksheet maintains a history of the commands you have issued, so you can easily retrieve and re-execute previous commands.

  Related Topics


Starting a SQL Worksheet

You can start a SQL Worksheet from the Enterprise Manager Console window by choosing SQL Worksheet from the Tools menu. The new worksheet is connected to the database you have selected in the Navigator tree list or in the Map window.

Connecting to a database from a Worksheet

When you start a SQL Worksheet from the Enterprise Manager console, you are automatically connected to the same database as the console. You can change this connection by issuing the CONNECT command from the input pane of the worksheet. The title of the SQL Worksheet window also changes to reflect your new connection.

If you execute the CONNECT command from the input pane without any arguments, the Login Information dialog box appears. You can use this dialog box to specify a new connection for that worksheet. You can also specify the connection using arguments in the CONNECT command.

  Related Topics


Command History

A SQL Worksheet maintains a history of the last 20 command executions you have issued in that worksheet. To bring up the Command History dialog box, click Command History or choose Command History from the Worksheet menu.

Note: Command executions larger than 100K are not recorded in the Command History.

The Command History dialog box contains a scrolling list of the commands in the worksheet's command history. The Command History dialog box contains the following:

Command List

Displays an abbreviated list of the last 20 command exectutions.  Explicit SQL commands associated with each command execution are displayed in the Command Text pane.

Command Text Pane

Displays all SQL commands associated with the selected entry in the Command List.

Done

Closes the dialog box without retrieving any text.

Get

Retrieves the selected item in the Command List command. See Retrieving a Selection from the Command History for more information about retrieving commands.

Help

Displays help information for the Command History dialog box.

  Related Topics


Executing Commands

Executing Commands in the Input Pane

To execute the command you have entered in the input pane, click the Execute icon in the input pane toolbar. You can also execute the command by choosing Execute from the Worksheet menu.

When you execute a command, the command and its output appear in the output pane. However, if you set the parameter ECHO to off, only the output of the command is displayed.

After you execute a command, the command remains in the input pane, but is selecte. You can then type in the next command, and it replaces the previous command.

Executing Server Manager  DBA Commands

In a SQL Worksheet you can execute the Server Manager DBA commands described in the DBA Command Reference. Some of these commands behave differently when executed in a SQL Worksheet than when executed in line mode. These commands are summarized below:

@

Displays the standard file selection dialog box when you issue the @ command without specifying a filename.

CONNECT

Displays the Connect dialog box when you issue the CONNECT command without specifying complete connect information.

HELP

Displays the Help window.

SPOOL

Displays the standard file selection dialog box for your platform when you issue the SPOOL command without specifying a filename.

RECOVER

If recovery is needed, displays the Recover dialog box when you issue the RECOVER command without arguments. Otherwise, an error message is generated.

EXIT

Closes the worksheet.

Note: The line mode command HOST is not available in the SQL Worksheet.

  Related Topics


Retrieving a Selection from the Command History

Retrieving a Selection from the Command History

To retrieve a command from the Command History dialog box, select the desired command execution entry in the Command List. All SQL commands associated with this entry are displayed in the Command Text pane. Click Get. The contents of the Command Text pane appear in the input pane replacing any existing text.

You can also drag and drop commands directly into the input pane by selecting an entry in the Command List and dropping it into the input pane. The text associated with the entry appears in the input pane.

To retrieve only a portion of a command execution from the Command Text pane, select the text you wish to retrieve and press Ctrl-C (copy). Move the cursor to the worksheet's input pane, place the cursor at the position where you want the text inseerted and press Ctrl-V (paste).

If no text is selected in the input pane, the copied text is inserted at the cursor position. If you have selected text in the input pane, then the retrieved text replaces the selected text. After you have retrieved text from the command history, you can edit or execute the command, as desired.

Retrieving a Command Using the Worksheet Menu

You can also retrieve command executions without using the Command History dialog box. The Previous Command and Next Command menu items and input toolbar icons retrieve commands from the command history and enter them in the input pane, completely replacing the existing contents of the input pane.

  Related Topics


Running Scripts

From a SQL Worksheet, you can run any script that contains SQL, PL/SQL, or Server Manager DBA commands. There are four ways to run scripts from a SQL Worksheet:

•	Clicking the Open Worksheet Icon from the input pane toolbar

•	Choosing Run Script from the Worksheet menu

•	Draging and dropping a SQL script from the Windows NT file manager into the worksheet's input pane.

•	Executing the Server Manager DBA @ command from the input pane

Clicking the Open Worksheet icon in the input pane toolbar or selecting the Open menu item displays the standard file selection dialog box. After you select the file and click OK, the content of the SQL script appears in the worksheet's input pane. Click the Execute icon or select the Execute menu item to run the script.

Selecting the Run Script menu item also displays the Run Script dialog box. Select the desired script and click OK. The Server Manager DBA @ command appears with the full path and filename of the selected script in the input pane. The script is run automatically.

To drag and drop scripts from the Windows file manager, select the desired script in the file manager and drop it into the input pane. The content of the script appears in the input pane. Click the Execute icon to run the script.

You can also run a script from the input pane of a worksheet by entering an @ command followed by the script name. The following figure illustrates running a script from the input pane of a worksheet. If you enter an @ command without a script name, your platform's standard file selection dialog box appears to allow you to specify a script name.

Note: In a script you can run other scripts. In the original script you can include the line @@second_scriptname to run another script called second_scriptname. The @@ command indicates that the second script is in the same directory as the original script.

  Related Topics


Writing Output to a File

The Spool menu option allows you to write output to a specified file. Selecting the Spool menu option from the Worksheet menu, or cli

  Related Topics


Previous Commnad
Previous Command

Retrieves the previous command from the command history and enters it in the input pane. The retrieved command replaces the entire contents of the input pane.

  Related Topics


Next Command

Retrieves the next command from the command history and enters it in the input pane. The retrieved command replaces the entire contents of the input pane.

Next Command is unavailable if you have currently retrieved the most recent command from the command history.

  Related Topics


Stop Spooling

The Spool menu item, Save Output As icon, and Save Worksheet As icon allow you to save the work you have performed in a SQL Worksheet. Each of these Worksheet menu commands displays the standard file selection dialog box, which you can use to specify the file in which to save your work.

The Spool menu item allows you to dynamically save all output of your worksheet session to a specified file. Enterprise Manager continues to save the output of your worksheet until you choose Stop Spooling from the menu.

Note: The SQL Worksheet appends a file extension, such as .log or .txt, to the name of each file created by the Spool, Save Output As, and Save Worksheet As commands.

  Related Topics


Change Database Connection

Displays the Login Information dialog box. This allows you to change the current database connection. By default, when you start a SQL Worksheet from the Enterprise Manager console, you are automatically connected to the same database as the console.

  Related Topics


New Worksheet

Clears the contents of the input pane. You are prompted to save your existing work.

  Related Topics


Open

Displays the Open Worksheet dialog box. This allows you to open an existing .SQL or ascii text file. The contents of the file appear in the input pane.

  Related Topics


Save

Saves the contents of the input pane to the current file.

  Related Topics


Save As

Saves the contents of the input pane to a file other than the one that is currently open.

  Related Topics


Output Save As

Save Output As allows you to write the current contents of your worksheet's output pane to a specified file. The output pane contains the last 32 KB of output and the last 100 lines of text. The actual amount may vary by operating system. Any text that has scrolled out of the output pane is also written to the file. The Save Worksheet As  menu item and icon (located in the input pane toolbar) writes the contents of the worksheet's input pane to a specified file.

  Related Topics


Print

Prints the contents of the input pane.

  Related Topics


Output Print

Prints the contents of the output pane.

  Related Topics


Recovery

When you issue the RECOVER command from a SQL Worksheet, the Recovery dialog box appears, if recovery is needed.

From the Recovery dialog box, you can apply the next log file, apply all the log files, or cancel recovery. You can specify the name of the log file to apply or apply the default.

  Related Topics


Entry

Lower window pane. Enter and edit commands in the input pane.

  Related Topics


Display

Upper window pane. Displays recently executed commands and output. SQL Worksheet stores the last 32 KB of output for display in the output pane. The actual amount stored varies depending upon the amount of system memory available.

  Related Topics


Empty

  Related Topics


Starting a SQL Worksheet

  Related Topics


Entering and Editing Commands in a SQL Worksheet

  Related Topics


Executing Commands from a SQL Worksheet

  Related Topics


Server Manager Line/Mode

Server Manager Line mode is useful for performing unattended operations, such as running nightly batch jobs or scripts. In addition, you can use line mode when a graphical device is unavailable.

  Related Topics


DBA Commands

The DBA commands are listed below. Select a command to display syntax and usage information.

•	@

•	ARCHIVE LOG

•	CONNECT

•	DESCRIBE

•	DISCONNECT

•	EXECUTE

•	EXIT

•	HELP  Server Manager Line Mode Only

•	HOST Server Manager Line Mode Only

•	PRINT

•	RECOVER

•	REMARK

•	SET

•	SHOW

•	SHUTDOWN

•	SPOOL

•	STARTUP

•	VARIABLE

Note: If a reserved word is used as an object name in a DBA command, it must be enclosed in quotes. For example, to start up a database that is named with the reserved word V7, issue the command as follows:

STARTUP OPEN 'V7'

  Related Topics


@ (at symbol)

Purpose

Run scripts containing SQL, PL/SQL, and DBA commands.

Prerequisites

You must have previously created the script and stored it as an operating system file.

Syntax

@ command ::=

Line Mode Behavior

If you omit the scriptname argument, you are prompted for the script name.

SQL Worksheet Behavior

If you omit the scriptname argument, the standard file selection dialog box for your system displays. You can then select the script file.

Usage Notes

This command enables you to run scripts of statements. To insert comments in the script, use the  REMARK command. To spool the output, use the SPOOL command before running the script.

Do not use the @ command alone within a script unless you specify the full path name of the script.

To run other scripts from within a script, you can use the @@ command. In the original script include the line @@second_scriptname to run another script called second_scriptname. The @@ command indicates that the second script is in the same directory as the original script.

Additional Information:  For information about the standard file selection dialog box for your system, see your operating system-specific documentation.

Return to the DBA Command List


ARCHIVE LOG Command

Purpose

Start or stop automatic archiving of online redo log files, manually (explicitly) archive specified redo log files, or display information about redo log files.

Note: This command applies only to the current instance. To specify archiving for a different instance or for all instances in a Parallel Server, use the SQL command ALTER SYSTEM.

Prerequisites

You must be connected to an open Oracle database as INTERNAL, SYSOPER, or SYSDBA.

Syntax

ARCHIVE LOG command ::=

where:

LIST

Requests a display that shows the range of redo log files to be archived, the current log file group's sequence number, and the current archive destination (specified by either the optional command text or by the initialization parameter LOG_ARCHIVE_DEST).

If you are using both ARCHIVELOG mode and automatic archiving, the display might appear like:

Database log mode             Archive Mode

Automatic archival            Enabled

Archive destination           DISK9:ARCH

Oldest online log sequence    30

Next log sequence to archive  33

Current log sequence          33

Because the log sequence number of the current log group and the next log group to archive are the same, automatic archival has archived all log groups up to the current one.

If you are using ARCHIVELOG but have disabled automatic archiving, the last three lines might look like:

Oldest online log sequence     30

Next log sequence to archive   30

Current log sequence           33

If you are using NOARCHIVELOG mode, the "next log sequence to archive" line is suppressed.

The log sequence increments every time LGWR begins to write to another redo log file group; it does not indicate the number of logs being used. Every time an online redo log file group is reused, the contents are assigned a new log sequence number.

STOP

Disables automatic archival. If the instance is still in ARCHIVELOG mode and all redo log file groups fill, database operation is suspended until a redo log file is archived (for example, until you enter the command ARCHIVE LOG NEXT or ARCHIVE LOG ALL).

START

Enables automatic archiving. Starts the background process ARCH, which performs automatic archiving as required. If ARCH is started and a filename is supplied, the filename becomes the new default archive destination.

ARCH automatically starts on instance startup if the initialization parameter LOG_ARCHIVE_START is set to TRUE.

NEXT

Manually archives the next online redo log file group that has been filled but not yet archived.

ALL

Manually archives all filled, but not yet archived, online log file groups.

integer

Causes archival of the online redo log file group with log sequence number n. You can specify any redo log file group that is still online. An error occurs if the log file cannot be found online or the sequence number is not valid. This option can be used to re-archive a log file group.

`destination'

Specifies the destination device or directory in an operating system. Specification of archive destination devices is installation-specific; see your platform-specific Oracle documentation for examples of specifying archive destinations. On many operating systems, multiple log files can be spooled to the same tape.

If not specified in the command line, the archive destination is derived from the initialization parameter LOG_ARCHIVE_DEST. The command ARCHIVE LOG START 'destination' causes the specified device or directory to become the new default archive destination for all future automatic or manual archives. A destination specified with any other option is a temporary destination that is in effect only for the current (manual) archive. It does not change the default archive destination for subsequent automatic archives.

Additional Information:  For information about specifying archive destinations, see your platform-specific Oracle documentation.

Usage Notes

If an online redo log file group fills and none are available for reuse, database operation is suspended. The condition can be resolved by archiving a log file group.

Examples

ARCHIVE LOG START

Starts up the archiver process and begins automatic archiving, using the archive destination specified in LOG_ARCHIVE_DEST.

ARCHIVE LOG STOP

Stops automatic archiving.

ARCHIVE LOG 1001 'DISK9:[TEMPARCH]TEMP'

Archives the log file group with the sequence number 1001 to the destination specified. 'TEMP' specifies the prefix of the filename on the destination device; the remainder of the filename is dependent on the initialization parameter LOG_ARCHIVE_FORMAT, which specifies the filename format for archived redo log files.

Return to the DBA Command List


CONNECT Command

Purpose

Connect to a database using the specified username.

Prerequisites

Only valid username/password combinations can successfully connect. The AS clause allows users to connect to an instance with a default schema of SYS for database administration. Users connecting as SYSOPER or SYSDBA must have the necessary privileges to access the SYS schema.

Syntax

CONNECT command ::=

where:

username

Any valid Oracle username for the current database. It can be a null string. If neither username nor INTERNAL is specified, you are prompted for a username and password.

password

The password corresponding to the specified username. Password can be a null string.

instance-path

A valid specification for an instance/database combination. If an instance is specified, it becomes the current instance for the duration of the connection. It does not become the default instance for subsequent connections.

SYSOPER/SYSDBA

The AS clause allows privileged connections by users who have been granted SYSOPER or SYSDBA system privileges, if using a password file, or their operating system equivalents, if using OS authentication.

/       	Uses operating system authentication.

INTERNAL

Connects as username SYS via keyword INTERNAL. Should be used rarely and only by the DBA for certain maintenance purposes; requires operating system privileges. CONNECT INTERNAL is supported for backwards compatibility only.

Line Mode Behavior

If you omit the password, you are prompted for one. If you omit both the username and password, you are prompted for both.

SQL Worksheet Behavior

If you omit the username argument, the Connect dialog box displays.

Usage Notes

If only the Oracle username is specified, the password is requested using the prompt "Password:". The entered password is not echoed.

CONNECT can be used without a DISCONNECT to connect to another username.

The connect is always accompanied by the opening of a cursor.

You can specify an instance path for a remote instance when connecting. If you attempt a connection to a remote instance, authentication occurs on the remote node, so you must have the appropriate privileges on the remote node.

Connecting as SYSOPER or SYSDBA over a Non-Secure Connection

To connect to Oracle as a privileged user over a non-secure connection, you must satisfy the following conditions:

•	The server to which you are connecting must have a password file.

•	You must be granted the SYSOPER or SYSDBA system privilege.

•	You must connect using a username and password.

Connecting as SYSOPER or SYSDBA over a Local or Secure Connection

To connect to Oracle as a privileged user over a local or a secure connection, you must satisfy either of the following sets of conditions:

•	You can connect using a password file, provided you meet the criteria outlined above.

•	If the server is not using a password file, or you have not been granted SYSOPER or SYSDBA and are therefore not in the password file, your operating system name must be authenticated by the operating system for a privileged connection. This form of authentication is system-specific.

Additional Information:  For information about operating system authentication, see your operating system-specific Oracle documentation.

Examples

To connect to an instance on the current default node, enter:

CONNECT

To connect to an instance on the current node as username SCOTT with password TIGER, enter:

CONNECT scott/tiger

To use a password file to connect to an instance on the current node as a privileged user named SCOTT with password TIGER, enter:

CONNECT scott/tiger AS SYSDBA

Note that your default schema is now SYS, not SCOTT.

To perform the same connection using OS authentication, enter:

CONNECT / AS SYSDBA

To connect to an instance on a different node as username SCOTT with password TIGER, enter:

CONNECT scott/tiger@instance-path

Connecting as INTERNAL

Using Server Manager you can connect as INTERNAL to a release 7.0 database. CONNECT INTERNAL is supported for backwards compatibility only.

Return to the DBA Command List


DESCRIBE Command

Purpose

Describe a function, package, package body, procedure, table, or view.

Prerequisites

You must be currently connected to a database.

Syntax

DESCRIBE command ::=

where:

name

The name of the object to describe.

Usage Notes

If you do not specify an object type, Server Manager attempts to determine the object type. For the statement

DESCRIBE emp

Server Manager describes the table or view if a table or view with the name EMP exists. If no table or view with that name exists in the user's schema, Server Manager will search for a PL/SQL function, procedure, or package with that name and describe it.

The shorthand DESC is now equivalent to the command DESCRIBE. This means that DESC has been added to the list of Server Manager reserved words. If you have a database object named DESC, you need to place quotes around the name to show that it is an object name. For example:

INSERT INTO 'DESC' VALUES('onetwothree', 123); )

Note: Some versions of PL/SQL allow the user to describe a package by giving the package name, and some versions require the user to specify an object in the package to describe. Server Manager supports package description for those versions of PL/SQL which support this functionality.

Example

A command like

DESCRIBE scott.addemp

produces output similar to the following example:

PROCEDURE SCOTT.ADDEMP (EMPNO INTEGER, ENAME VARCHAR2, SAL NUMBER(9,2))

The use of the object type is no longer required. If you do not specify an object type, Server Manager attempts to determine the object type. For the statement

DESCRIBE emp

Server Manager describes the table or view if a table or view with the name EMP exists.

If no table or view with that name exists in the user's schema, Server Manager searches for a PL/SQL function, procedure, or package with that name and describes it. For the statement

DESCRIBE payroll.emp

Server Manager looks for a table or view in schema PAYROLL with the name EMP.

If there is no PAYROLL schema or no EMP table/view in the PAYROLL schema, Server Manager will search the current schema for a package PAYROLL containing a function or procedure EMP.

If both a table EMP in schema PAYROLL and a package PAYROLL with function/procedure EMP in the current schema exist, the statement

DESCRIBE FUNCTION payroll.emp

This allows you to specify the type of the object you want to describe.

Server Manager now has the capability to describe both functions and procedures contained in packages. Previously only functions and procedures not contained in packages could be described.

Note: Some versions of PL/SQL allow the user to describe a package by giving the package name, and some versions require the user to specify an object in the package to describe. Server Manager supports package description for those versions of PL/SQL which support this functionality.

Return to the DBA Command List


DISCONNECT COMMAND

Purpose

Disconnect from an Oracle server.

Prerequisites

You must be currently connected to a database.

Syntax

DISCONNECT command ::=

Usage Notes

Upon disconnection, line mode reverts to the current default host machine after closing all open cursors and committing any uncommitted transactions.

Example

DISCONNECT

Return to the DBA Command List


EXECUTE COMMAND

Purpose

Executes a one-line PL/SQL statement.

Prerequisites

You must be currently connected to a database. You must also have privileges to use any stored procedures, packages, package variables, and functions referenced with this command.

Syntax

EXECUTE command ::=

Usage Notes

You can execute only one line of PL/SQL code with the EXECUTE command. If you wish to execute a PL/SQL block with many lines, you must use the format:

BEGIN

    [PL/SQL BLOCK]

END;

You can reference any command line mode bind variables in PL/SQL statements by preceding the variable name with a colon. The example below illustrates the use of bind variables with the VARIABLE, EXECUTE, and PRINT commands.

Example

VARIABLE balance NUMBER

EXECUTE :balance := get_balance(34056)

PRINT balance

BALANCE

----------

4678.24

Return to the DBA Command List


EXIT Command

Purpose

Exits Server Manager line mode or closes a SQL Worksheet.

Prerequisites

None.

Syntax

EXIT command ::=

Line Mode Behavior

The EXIT command leaves line mode unconditionally, commits the current transaction, and returns to the operating system prompt.

SQL Worksheet Behavior

The EXIT command commits the current transaction and closes the worksheet.

Example

EXIT

Return to the DBA Command List


HELP Command

Purpose

Displays help information.

Prerequisites

None.

Syntax

HELP command ::=

Line Mode Behavior

Displays simplified syntax descriptions for some commands.

SQL Worksheet Behavior

Brings up the Help window.

Example

HELP

Return to the DBA Command List


HOST Command

Purpose

Execute an operating system command without exiting line mode. The HOST command is not available in a SQL Worksheet.

Prerequisites

None.

Syntax

HOST command ::=

If you omit the operating system command and enter simply HOST, you temporarily exit line mode on the assumption you want to run multiple operating system commands.

Additional Information:  To return to line mode after executing a HOST command, you must use an operating system-specific entry. Refer to your operating system-specific Oracle documentation for more information.

Example

For VMS:

HOST TYPE INIT.ORA

For UNIX:

HOST cat INIT.ORA

Return to the DBA Command List


PRINT Command

Purpose

Print the value of a variable defined with the VARIABLE command.

Prerequisites

None.

Syntax

PRINT command ::=

where:

variable

The name of a variable defined by the VARIABLE command.

Usage Notes

Bind variables referenced with the print command do not need to be preceded by a colon. You can use the PRINT command to display variables defined only in the current line mode session. The SET CHARWIDTH and SET NUMWIDTH commands can affect the display of the PRINT command.

If no variable name is specified all currently defined variables are printed.

Examples

PRINT balance

BALANCE

----------

4687.24

SET CHARWIDTH 10

PRINT ename

ENAME

----------

SCOTT

Return to the DBA Command List


RECOVER Command

Purpose

Performs media recovery on one or more tablespaces, one or more datafiles, or the entire database.

Prerequisites

You must be connected to the Oracle server as INTERNAL, SYSOPER, or SYSDBA. You cannot use the RECOVER command when connected via the multi-threaded server.

Syntax

RECOVER command ::=

UNTIL clause ::=

PARALLEL clause ::=

where:

DATABASE

Specifies recovering the entire database.

USING BACKUP CONTROL FILE

Specifies that a backup of the control file is being used instead of the current control file.

TABLESPACE

Specifies recovering a particular tablespace.

 tablespace

Tablespace is the name of a tablespace in the current database. You may recover up to 16 tablespaces in one statement.

DATAFILE filename

Specifies recovering a particular datafile. You can specify any number of datafiles.

UNTIL CANCEL

Specifies an incomplete, cancel-based recovery. Recovery proceeds by prompting you with the suggested filenames of archived redo log files, and recovery completes when you specify CANCEL instead of a filename.

UNTIL CHANGE

Specifies an incomplete, change-based recovery.

integer

The integer is the number of the SCN following the last change to which you wish to recover. For example, if you want to restore your database up to the transaction with an SCN of 9, you would specify UNTIL CHANGE 10.

UNTIL TIME date

Specifies an incomplete, time-based recovery. Use single quotes, and use the following format:

'YYYY-MM-DD:HH24:MI:SS'.

PARALLEL

DEGREE specifies the number of recovery processes used to apply redo entries to datafiles on each instance. An integer specified for DEGREE overrides the initialization parameter RECOVERY_PARALLELISM.

DEGREE DEFAULT indicates that twice the number of datafiles being recovered is the number of recovery processes to use.

INSTANCES specifies the number of instances to use for parallel recovery. The number of recovery processes specified with DEGREE is used on each instance, thus the total number of recovery processes is the integer specified with DEGREE multiplied by the integer specified with INSTANCES. INSTANCES is only pertinent for the Oracle Parallel Server.

INSTANCES DEFAULT or not including the INSTANCES keyword causes has operating system-specific consequences. Consult your Oracle operating system documentation for a description of the default behavior of the INSTANCES DEFAULT specification.

NOPARALLEL

Specifies that recovery is to proceed serially. Note that a specification of PARALLEL(DEGREE 1 INSTANCES 1) is equivalent to specifying the NOPARALLEL keyword.

The PARALLEL keyword overrides the RECOVERY_PARALLELISM initialization parameter. The number specified with the PARALLEL keyword is the number of recovery processes used to apply redo entries to datafiles.

SQL Worksheet Behavior

In a SQL Worksheet, if you issue the RECOVER command without arguments, Server Manager brings up the Recover dialog box.

Usage Notes

To perform media recovery on an entire database (all tablespaces), the database must be mounted EXCLUSIVE and closed.

To perform media recovery on a tablespace, the database must be mounted and open, and the tablespace must be offline.

To perform media recovery on a datafile, the database can remain open and mounted with the damaged datafiles offline (unless the file is part of the SYSTEM tablespace).

Before using the RECOVER command you must have restored good copies of the damaged datafile(s) from a previous backup. Be sure you can access all archived and online redo log files dating back to when that backup was made.

When another log file is required during recovery, a prompt suggests the names of files that are needed. The name is derived from the values specified in the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT. You should restore copies of the archived redo log files needed for recovery to the destination specified in LOG_ARCHIVE_DEST, if necessary. You can override the initialization parameters by setting the LOGSOURCE variable.

During recovery you can accept the suggested log name by hitting return, cancel recovery by entering CANCEL instead of a log name, or enter AUTO for automatic file selection without further prompting.

If you have enabled autorecovery (that is, SET AUTORECOVERY ON), recovery proceeds without prompting you with filenames. Status messages are displayed when each log file is applied.

When normal media recovery is done, a completion status is returned.

Examples

RECOVER DATABASE

RECOVER DATABASE UNTIL TIME 30-AUG-90:04:32:00

RECOVER TABLESPACE ts_one, ts_two

RECOVER DATAFILE 'data1.db'

Return to the DBA Command List


REMARK Command

Purpose

Enter a comment, typically in SQL script files.

Prerequisites

None.

Syntax

REMARK command ::=

Usage Notes

Primarily for batch use of line mode. The comment is ignored by line mode and by Oracle. REMARK can be shortened to REM.

REM must be the first non-blank character string in the line.

Examples

Examples of valid comments embedded in a SQL file follow:

REM    This command file is used to create a

REM    database. Edit it to fill in file names

REM    and sizes, and invoke it from line mode.

REM

REM

CREATE DATABASE dbname ....

    /* This is a SQL comment */ ...

    ...

    ;

REMARKs are recognized by SQL*Plus, as well as by line mode. They are used to put comments between SQL statements, while SQL comments (/*...*/) are used to place comments within statements.

Return to the DBA Command List


SET Command

Purpose

Set or change characteristics of the current command line mode session.

Prerequisites

None.

Syntax

SET command ::=

where:

APPINFO

Registers the Server Manager application through the database's DBMS_APPLICATION_INFO package (Oracle 7.2 or later).  By default, the APPINFO function is set to OFF.

Application registration allows DBAs to see what software is currently running to better monitor resource utilization for database tuning. When APPINFO is turned on, application registration proceeds normally. If a SQL script is not being run, the default registration text string is "Oracle Server Manager." Optionally, you can create a customized registration text string. If a script is being run through Server manager, the script name is used as the registration text string.

•	SET APPINFO ON registers Server Manager using the text string "Oracle Server Manager" , a customized text string, if one has been defined, or a SQL script name. APPINFO is automatically turned OFF if a database or system error occurs.

•	SET APPINFO OFF turns off the function.

•	SET APPINFO usertext replaces the default "Oracle Server Manager" registration string with a customized string (usertext). Note: usertext must be a contiguous string unless it is enclosed within single or double quotation marks.

Examples:

Text String	Registers as:

SET APPINFO abc	abc

SET APPINFO abc def	abc

SET APPINFO "abc def"	abc def

SET APPINFO 'abc def'	abc def

SET APPINFO "abc def	Error

SET APPINFO 'abc def	Error

•	·To set APPINFO so that it is turned ON whenever you start Server Manager, enter the following command string at the operating system prompt:

>svrmgrl command="SET APPINFO ON"

Note: This procedure applies to Server Manager Line Mode only and not the SQL Worksheet.

AUTO- RECOVERY

Specifying ON causes the RECOVER command to automatically apply the default filenames of archived redo log files needed during recovery. No interaction is needed when AUTORECOVERY is set to ON, provided the necessary files are in the expected locations with the expected names. The filenames used when AUTORECOVERY is ON are derived from the values of the initialization parameters LOG_ARCHIVE_DEST and LOG_ARCHIVE_FORMAT.

OFF, the default option, requires that you enter the filenames manually or accept the suggested default filename given.

CHARWIDTH integer

Sets the column display width for CHAR data. If entered with no argument, returns the setting to the default. The default is 80; the range of values is operating system-specific.

Note: CHARWIDTH now has an absolute value rangefrom 1-2000. Previously, the range was 1-999999. The actual range of values is operating system-specific.

COMPATIBILITY

Sets compatibility mode to V6, V7, or NATIVE. The compatibility mode setting affects the specification of character columns, integrity constraints, and rollback segment storage parameters. NATIVE matches the version of the database.

CHAR Columns: When creating tables in Version 6 compatibility mode, CHAR columns are variable length. In Oracle7, such column definitions are fixed length.

Integrity Constraints: In Version 6 compatibility mode, the Version 6 syntax is still recognized, and the Oracle7 syntax is disabled. For V6 mode, table constraints on CREATE TABLE statements are specified with V6 syntax:

CREATE TABLE {UNIQUE | PRIMARY KEY}

CONSTRAINT ....

and specified constraints are disabled by default. For V7 mode, table constraints are specified with Oracle7 syntax:

CREATE TABLE CONSTRAINT ....

{UNIQUE | PRIMARY KEY}

and they are enabled.

Rollback Segment Parameters: Version 6 compatibility mode allows PCTINCREASE and MAXEXTENTS to be specified for rollback segments, as well as for other segments. Although the specifications are ignored, the syntax is allowed. (Use of these parameters is not recommended. They exist only for backward compatibility.)

Bind Variables: Bind variables of type VARCHAR2 are given type CHAR in Version 6 compatibility mode.

DATEWIDTH integer

Sets the column display width for DATE data. If entered with no argument, the setting returns to the default. The default is 9; the range of values is operating system-specific.

ECHO

ON enables echoing of commands entered from command files. OFF, the default, disables echoing of commands.

FETCHROWS integer

Limits the number of rows returned by a query. Useful with ordered queries for finding the "top ten" items in a category, for example. Also used with unordered queries to find the "first n" records that satisfy a given criteria. integer must be in the range 1-999,999.

In a SQL Worksheet the default is ECHO ON.

INSTANCE  instance-path

Changes the default instance for your session to the specified instance path. Does not connect to a database. The default instance is used for commands when no instance is specified.

Any commands preceding the first use of SET INSTANCE communicate with the default instance.

To reset the instance to the default value for your operating system, you can either enter SET INSTANCE with no instance-name or SET INSTANCE LOCAL. See your operating system-specific Oracle documentation for a description of how to set the initial default instance.

This command may only be issued when SQL*Net is running. You can use any valid SQL*Net connect string as the specified instance path. See your operating system-specific Oracle documentation for a complete description of how your operating system specifies SQL*Net connect strings. The maximum length of the instance path is 64 characters.

LOGSOURCE pathname

Specifies the location from which archive logs are retrieved during recovery. The default value is set by the LOG_ARCHIVE_DEST initialization parameter. Issuing the SET LOGSOURCE command without a pathname restores the default location.

LONGWIDTH integer

Sets the column display width for LONG data. If entered with no argument, the setting returns to the default. The default is 80; the range of values is operating system-specific.

Note: LONGWIDTH now has an absolute value rangefrom 1-2000. Previously, the range was 1-999999. The actual range of values is operating system-specific.

MAXDATA integer

Sets the maximum data size. Indicates the maximum data that can be received in a single fetch during a SELECT statement. The default is 20480 bytes (20K). The maximum is operating system-specific.

NUMWIDTH integer

Sets the column display width for NUMBER data. If entered with no argument, the setting returns to the default. The default is 10; the range of values is operating system-specific.

Note: NUMWIDTH now has an absolute value rangefrom 1-2000. Previously, the range was 1-999999. The actual range of values is operating system-specific.

RETRIES integer | INFINITE

Sets the number of tries that are attempted when the RETRY option is used with the STARTUP command (see "STARTUP" on page 329). INFINITE, the default, specifies an infinite number of retries.

SERVEROUTPUT

ON enables debugging output from stored procedures that use DBMS_OUTPUT PUT and PUT_LINE commands. OFF disables output.

You can specify the size in bytes of the message buffer using the syntax SIZE n. That is the total number of bytes of all messages sent that can be accumulated at one time. The minimum is 2,000 bytes. If the buffer fills before calls to the get-message routines make room for additional message bytes, an error is returned to the message-sending program.

STOPONERROR

Specifying ON indicates that if a command file is running and an error occurs, execution should terminate. OFF disables STOPONERROR.

TERMOUT

ON, the default, enables terminal output for SQL commands. OFF disables terminal output. Useful for preventing output to terminal when spooling output to files. Note that nothing appears on the terminal until SET TERMOUT ON is used.

TIMING

ON displays parse, execute, and fetch times (CPU and elapsed) for each SQL statement executed. OFF, the default, does not display timing information.

Examples

SET INSTANCE D:DEV-PROD

SET TIMING ON

SET LONGWIDTH 132

SET NUMWIDTH 20

SET CHARWIDTH 5

Either of the following commands can be used to revert to the initial default host:

SET INSTANCE

SET INSTANCE LOCAL

Return to the DBA Command List


SHOW Command

Purpose

Show settings currently in effect.

Prerequisites

None.

Syntax

SHOW command ::=

where:

ALL

Shows all settings except for ERRORS, PARAMETERS, and SGA.

APPINFO

Shows the current status (ON/OFF) and the application registration text.

AUTORECOVERY

Shows whether or not autorecovery is enabled.

CHARWIDTH

Shows the column display width for CHAR data.

COMPATIBILITY

Shows the sessions compatibility mode: V6, V7, or NATIVE.

DATEWIDTH

Shows the column display width for DATE data.

ECHO

Shows whether or not commands from command files are echoed.

ERRORS

Shows the errors generated from the last compilation of a procedure, package, or function, if any. This option displays the line number, column number, and the error message generated. Use the SHOW ERRORS command if line mode error 72 or 73 is returned after compiling a package.

The SET CHARWIDTH command can be used to expand or truncate the display from the SHOW ERRORS command.

INSTANCE

Shows the connect string for the default instance. SHOW INSTANCE returns the value LOCAL if you have not used SET INSTANCE or if you have used the LOCAL option of the SET INSTANCE command.

LOGSOURCE

Shows the current setting for archive log location. Displays DEFAULT if the default setting is in effect, as specified by the LOG_ARCHIVE_DEST initialization parameter.

LONGWIDTH

Shows the column display width for LONG data.

MAXDATA

Shows the maximum data size.

NUMWIDTH

Shows column display width for NUMBER data.

PARAMETERS

Displays the current values for one or more initialization parameters. You can use a string after the command to see a subset of parameters whose names include that string. For example, if you enter:

SHOW PARAMETERS COUNT

you would see:

NAME                           TYPE      VALUE

-------------------            -------   -----

db_file_multiblock_read_count  integer    12

spin_count                     integer    0

The SHOW PARAMETERS command, without any string following the command, displays all initialization parameters.

RETRIES

Displays the number of retries that will be attempted when restarting an instance in parallel mode. (See the RETRY option in "STARTUP" on page 329.)

SERVEROUTPUT

Displays ON if output from stored procedures and functions is enabled. Otherwise, displays OFF. SERVEROUTPUT is reset to OFF if you issue a CONNECT command.

SGA

Displays information about the current instance's System Global Area.

SPOOL

If spooling is enabled, displays the name of the output spool file. Otherwise, displays OFF.

STOPONERROR

Displays whether or not errors encountered during execution of command files should stop execution of the file.

TERMOUT

Shows if output to the terminal is enabled.

TIMING

Shows whether or not the parse, execute, and fetch times (CPU and elapsed) for each SQL statement executed are shown.

Usage Notes

SHOW with no arguments is the same as SHOW ALL.

Examples

SHOW TIMING

returns a display such as:

Timing             OFF

SHOW ALL

returns a display like:

Instance           local

Spool              OFF

Timing             OFF

Termout            ON

Echo               OFF

Stoponerror        OFF

Autorecovery       OFF

Logsource          <default>

Maxdata            20480

Numwidth           10

Charwidth          80

Longwidth          80

Datewidth          9

Labwidth           32

Compatibility      NATIVE

Retries            infinite

Server Output      OFF

SHOW SGA

returns a display like:

Total Shared Global Area         4612820  bytes

Fixed Size                         36376  bytes

Variable Size                    4445372  bytes

Database Buffers                  122880  bytes

Redo Buffers                        8192  bytes

SHOW ERRORS PACKAGE BODY name

returns a display like:

ERRORS FOR PACKAGE BODY name:

LINE/COL        ERRORS

---------------------------------------------------------------

Return to the DBA Command List


SHUTDOWN Command

Purpose

Shut down a currently running Oracle instance, optionally closing and dismounting a database.

Prerequisites

You must be connected to a database as INTERNAL, SYSOPER, or SYSDBA. You cannot be connected via a multi-threaded server.

Syntax

SHUTDOWN command ::=

where:

ABORT

Proceeds with the fastest possible shutdown. Does not wait for calls to complete or users to disconnect. Does not close or dismount the database, but does shut down the instance. Requires instance recovery on next startup. You must use this option if a background process terminates abnormally.

IMMEDIATE

Does not wait for current calls to complete, prohibits further connects, and closes and dismounts the database. Finally, shuts down the instance. Does not wait for connected users to disconnect. Does not require instance recovery on next startup.

NORMAL

Waits for currently connected users to disconnect from the database, prohibits further connects, and closes and dismounts the database. Finally, shuts down the instance. Does not require instance recovery on next startup. NORMAL is the default option.

Attention: In Server Manager, you can have several separate connections open at any time in multiple windows. If you have any connections open, remember to close them before performing a shutdown in normal mode. Otherwise, the shutdown will not complete.

Usage Notes

SHUTDOWN with no arguments is equivalent to SHUTDOWN NORMAL.

Example

SHUTDOWN

Database closed.

Database dismounted.

Oracle instance shut down.

Return to the DBA Command List


SPOOL Command

Purpose

Enable or disable spooling of output to a specified file.

Prerequisites

None.

Syntax

SPOOL command ::=

where:

filename

Any valid name for a spool file. If not specified, the file type or file extension is LOG. If a file by the specified name exists, an error is generated.

OFF

Closes the previously opened spool file.

SQL Worksheet Behavior

In a SQL Worksheet, if you issue the SPOOL command without specifying a filename, Server Manager brings up the standard file selection dialog box for your system.

Usage Notes

If you do not specify a file, Server Manager prompts you for a filename.

Additional Information:  The default filename is operating system specific. Refer to your operating system-specific Oracle documentation for the default filename on your operating system. To see whether you are currently spooling, enter SHOW SPOOL.

Note: When long lines of text (usually from a table query) are written to a spool file or to a terminal, newline codes are inserted in the text if the lines exceed the maximum line length for the platform.

Example

To create a file named NOV2.LOG, enter:

SPOOL NOV2

Return to the DBA Command List


STARTUP Command

Purpose

Start an Oracle instance with several options, including mounting and opening a database.

Prerequisites

You must be connected to a database as INTERNAL, SYSOPER, or SYSDBA. You cannot be connected via a multi-threaded server.

Syntax

STARTUP command ::=

MOUNT_OPTIONS clause ::=

where:

FORCE

Shuts down the current Oracle instance (if it is running) with SHUTDOWN mode ABORT, before restarting it. If the current instance is running and FORCE is not specified, an error results. FORCE is useful while debugging and under abnormal circumstances. It should not normally be used.

RESTRICT

Only allows Oracle users with the RESTRICTED SESSION system privilege to connect to the database. Later, you can use the ALTER SYSTEM command to disable the restricted session feature.

PFILE=filename

Causes the specified parameter file to be used while starting up the instance.

MOUNT

Mounts a database but does not open it.

OPEN

Mounts and opens the specified database.

NOMOUNT

Causes the database not to be mounted upon instance startup. Cannot be used with SHARED, EXCLUSIVE, PARALLEL, MOUNT, or OPEN.

RECOVER

Specifies that media recovery should be performed, if necessary, before starting the instance. STARTUP RECOVER has the same effect as issuing the RECOVER DATABASE command and starting an instance. Only complete recovery is possible with the RECOVER option.

Recovery proceeds, if necessary, as if AUTORECOVERY is set to ON, regardless of whether or not AUTORECOVERY is enabled. If a redo log file is not found in the expected location, recovery continues as if AUTORECOVERY is disabled, by prompting you with the suggested location and name of the subsequent log files that need to be applied. See "Usage Notes" in "RECOVER" on page 315 for a description of how to proceed with recovery when AUTORECOVERY is disabled.

If recovery fails using the RECOVER option, the database remains mounted and closed.

database

The name of the database to mount or open. If no database name is specified, the database name is taken from the initialization parameter DB_NAME.

EXCLUSIVE

Signifies that the database can only be mounted and opened by the current instance (it cannot be opened simultaneously by multiple instances). Cannot be used with SHARED, PARALLEL, or NOMOUNT. If no mounting option is specified, EXCLUSIVE is assigned by default.

PARALLEL

Must be specified if the database is to be mounted by multiple instances concurrently. Cannot be used with EXCLUSIVE or NOMOUNT. Invalid if the initialization parameter SINGLE_PROCESS is set to TRUE.

SHARED

Synonym for PARALLEL.

RETRY

Specifies that opening the database should be attempted every five seconds if the instance is busy being recovered by another instance. When an instance is being recovered by another instance, the down instance cannot open the database until recovery is complete. If the database cannot be opened for any other reason, RETRY does not attempt to open the database again. This option is only available for instances operating in PARALLEL mode. The number of times RETRY attempts to start the database can be set with the SET RETRIES command (see "RETRIES" in "SET" on page 321).

Examples

To start an instance using the standard parameter file, mount the default database in exclusive mode, and open the database, enter:

STARTUP

or enter:

STARTUP OPEN databasename EXCLUSIVE

To start an instance using the standard parameter file, mount the default database in parallel mode, and open the database, enter:

STARTUP PARALLEL

STARTUP OPEN databasename PARALLEL

To restart an instance that went down in parallel mode and may not yet have been recovered by other instances, use the RETRY option:

STARTUP PARALLEL RETRY

To shut down the current instance, immediately restart it without mounting or opening, and allow only database administrators to connect, enter:

STARTUP FORCE NOMOUNT RESTRICT

To start an instance using the parameter file TESTPARM without mounting the database, enter:

STARTUP PFILE=testparm NOMOUNT

To shut down a particular database, immediately restart and open it in parallel mode, allow access only to database administrators, and use the parameter file MYINIT.ORA. enter:

STARTUP OPEN databasename PFILE=myinit.ora FORCE SHARED RESTRICT

To start up an instance and mount but not open a database, you can use the following sequence of commands (the system's response is also shown):

CONNECT INTERNAL

Connected.

STARTUP NOMOUNT

Oracle instance started.

ALTER DATABASE MOUNT

Statement processed.

At this point, you could run a maintenance command and then open the database, as shown in the following commands:

ALTER DATABASE ARCHIVELOG;

Statement processed.

ALTER DATABASE OPEN;

Statement processed.

Return to the DBA Command List


VARIABLE Command

Purpose

Declare a bind variable for use in the current session with the EXECUTE or PRINT command, or for use with a PL/SQL block.

Prerequisites

None.

Syntax

VARIABLE command ::=

where:

name

The name of the bind variable you wish to define.

type

The datatype of the bind variable. The valid datatypes are NUMBER, CHAR, and VARCHAR2. You can specify a length from 1 to 255 for CHAR, and from 1 to 2,000 for VARCHAR2. If you do not specify a length, CHAR and VARCHAR2 default to the current setting of CHARWIDTH.

Usage Notes

Bind variables defined with the VARIABLE command exist until the end of the session. Variables defined in your session cannot be accessed or changed by a different session.

Warning: CHAR variables are fixed length, padded with blanks. VARCHAR2 variables are variable length. You must use CHAR when passing a character variable to a PL/SQL procedure that defines a CHAR parameter. Otherwise, a conversion error results. A PL/SQL procedure that expects a VARCHAR2 variable, on the other hand, will automatically convert a CHAR parameter to the proper form. (In general, it is a good idea to avoid the use of CHAR variables in PL/SQL procedures unless blank-padding is an absolute requirement.)

Note: In V6 compatibility mode, a CHAR variable is variable length, rather than fixed.

Examples

VARIABLE balance NUMBER

VARIABLE ename CHAR(20)

Return to the DBA Command List


Oracle Parallel Server Support for the Oracle Enterprise Manager Console

Parallel processing divides a large task into many smaller tasks and executes the smaller tasks concurrently on several different nodes.  A parallel database takes advantage of parallel processing by running multiple instances which share a single physical database. In appropriate applications, a parallel server can allow access to a single database by users on multiple nodes with increased performance.

Use the Oracle Enterprise Manager to start up, shut down and monitor the activity of parallel servers. This allows you to handle all of the nodes in a parallel server as a single entity.  For example, you can use  Enterprise Manager to execute a job across all nodes of a parallel server.

 Related Topics

In addition to the Related Topics, for more information on the Enterprise Manager, see Oracle Enterprise Manager: An Overview.

For more information on the Performance Manager, see Monitoring Parallel Server Performance.


Parallel Server Container in the Navigator Window

Oracle Parallel Servers appear as a separate category in the Navigator window.  The parallel server container displays information about the parallel server, such as  instances, datafiles, in-doubt transactions, profiles, redo log groups, roles, rollback segments, schema objects, tablespaces, and users.  A unique feature of parallel servers is that a parallel server’s instances can also contain this same information.

The parallel servers and their instances are arranged in a tree structure. When navigating the tree you can:

•	Click the ”+” to the left of a parallel server folder icon to expand and display the contents of the folder. You can also double-click a collapsed folder icon to expand the folder.

•	Click the ”-“ to the left of a parallel server folder icon to collapse the folder. You can also double-click an expanded folder icon to collapse the folder.

 Related Topics


Starting Up Parallel Servers

You can start all instances or only selected instances belonging to a parallel server that are not already up and available. Starting the instances also starts all of the required services such as the listener, the lock manager, and so on.

Follow these steps to start all instances or only selected instances:

1.	In the Navigator window, click the icon of the parallel server whose instances you want to start.

2.	Right mouse click and select Startup. The Startup Page of the Quick Edit Property Sheet opens.

3.	Click the startup options you want to select.

4.	If you want to start all of the instances, click the Startup button. If you want to start only some of the instances, follow these steps:

a)	Mark the Selected Instances Only checkbox.

b)	Click the Selected Instances button to open the Selected Instances dialog box.

c)	Use the <<(Add) and >>(Remove) buttons to select the instances you want to start up.

d)	Close the Selected Instances dialog box.

e)	Click the Startup button in the Startup page.

The Results dialog box displays the progress of the startup operation.

If the instances start successfully, the Parallel Server Startup Successful dialog box opens. Click the View Details button to see more information in the Results dialog box about the instances that were started.

If the startup fails, the Parallel Server Startup Failed dialog box opens. Click the OK button to see more information in the Results dialog box about why the start up failed.

 Related Topics


Results Dialog Box

The Results dialog box displays information about the progress of the instance start up or shut down operation you selected.

The Results dialog box contains these fields:

Operation

The Operation combo box lists the time stamp and the name of the parallel server the job is submitted on.

Details

The Details status box displays the status of the operation. The status can be “In progress”, “Success” or “Failed”.

Results

The Results edit box lists the progress of the of the start up or shut down operation. If you marked the Show Command checkbox on the Startup or Shutdown page, the first line of the Results box displays the command line issued to the opsctl utility.

In addition to displaying results, you can save or print the results of the operation.

OK

Click OK to dismiss the Results dialog box.

Save

Click Save to save the contents of the Results dialog box.  A Save As dialog box opens where you can choose the filename and path for the results.

Print

Click Print to print the contents of the Results dialog box.

 Related Topics


Shutting Down Parallel Servers

You can shut down all instances or only selected instances belonging to a parallel server which are currently up and available.  Once all of the parallel server’s instances are shut down, the parallel server is considered to be shut down.  When you shut down a parallel server, Oracle Trace (oratrcd)  also shuts down.

Note: Occasionally, a parallel server database will be completely down, but some of its services (such as the database listener or lock manager) will remain running.  If you follow the steps below, the services will also be shut down.

Follow these steps to shut down all instances or only selected instances:

1.	In the Navigator window, click the icon of the parallel server whose instances you want to shut down.

2.	Right mouse click and select Shutdown. The Shutdown Page of the Quick Edit property sheet opens.

3.	Click the shut down options you want to select.

4.	If you want to shut down all of the instances, click the Shutdown button.  If you want to shut down only some of the instances, follow these steps:

a)	Mark the Selected Instances Only checkbox.

b)	Click the Select Instances button to open the Select Instances dialog box.

c)	Use the <<(Add) and >>(Remove) buttons to select the instances you want to shut down.

d)	Close the Select Instances dialog box.

e)	Click the Shutdown button on the Shutdown page.

The Results dialog box displays the progress of the shut down operation.

If the instances shut down successfully, the Parallel Server Shutdown Successful dialog box opens. Click the View Details button to see more information in the Results dialog box about the instances that were shut down.

If the shut down fails, the Parallel Server Shutdown Failed dialog box opens. Click the OK button to see more information in the Results dialog box about why the shut down failed.

 Related Topics


Parallel Server Quick Edit Property Sheet

Use the Quick Edit property sheet to view the status of the parallel server, or to start up or shut down the instances belonging to a specified parallel server.  The Quick Edit property sheet contains these pages:

•	Status page - Use the Status page to view banner information about the server release.  This page also contains connection information.

•	Instances Available page - Use the Instances Available page to display the name of the instances belonging to the parallel server which are currently up and available.

•	Startup page - Use the Startup page to start all instances that are not already up and available.

•	Shutdown page - Use the Shutdown page to shut down all instances that are currently up and available.

 Related Topics


Instances Available Page

The Instances Available page displays information about the parallel server that you highlight in the Navigator window. It displays the names of the instances belonging to the parallel server which are currently up and available.

Instance Number

The number of the instance.

Instance Name

The name of the instance and the node it is running on. This description uses the format node:instance_name.

 Related Topics


Status Page

The Status page displays banner information about the server release.  This page also contains connection information.

 Related Topics


Startup Page

Use the Startup page to start all instances or selected instances that are not already up and available. Starting the instances also starts all of the necessary services such as the listener, the lock manager, and so on.

You can choose any of the following start up options:

Force

Shuts down the currently running Oracle instances with SHUTDOWN mode ABORT, before restarting them. If the instances are  running and FORCE is not specified, an error results. Use FORCE mode while debugging and under abnormal circumstances. It should not normally be used.

Restrict

Makes the started instances accessible only to users with the RESTRICTED SESSION system privilege. Users already connected are not affected.

No Mount

Does not mount the database upon instance start up.

Mount

Mounts a database but does not open it.

Mount and Open

Mounts and opens the specified database (default).

Configuration File

Enter the fully qualified path to the parallel server configuration file that resides in the managed system.  By default, this is the file $ORACLE_HOME/ops/ops_name.conf where ops_name is the name of the parallel server.

Show Command

Mark this checkbox to display the opsctl command line as the first line in the Results field in the Results dialog box.

Selected Instances Only

Mark this checkbox if you want to start only selected instances. The Select Instances button becomes active.

Select Instances

Click the Select Instances button to choose only those instances you want to start.

 Related Topics


Shutdown Page

Use the Shutdown page to shut down all instances or selected instances that are currently up and available.  Shutting down the instances also shuts down Oracle Trace (oratrcd).

You can choose any of the following shut down options:

Normal

Waits for currently connected users to disconnect from the database, prohibits further connects, and closes and dismounts the database. Finally, shuts down the instance. Does not require instance recovery on next start up.

Immediate

Does not wait for current calls to complete, prohibits further connects, and closes and dismounts the database. Finally, shuts down the instance. Does not wait for connected users to disconnect. Does not require instance recovery on next start up.  IMMEDIATE is the default option.

Abort

Proceeds with the fastest possible shut down. Does not wait for calls to complete or users to disconnect. Does not close or dismount the database, but does shut down the instance. Requires instance recovery on next start up. You must use this option if a background process terminates abnormally.

Shutdown Database Only

Shuts down the database only. The services required for an instance, such as the listener, the lock manager, and so on, remain up and available. The option default is “on”.

Show Command

Mark this checkbox to display the opsctl command line as the first line in the Results field in the Results dialog box.

Selected Instances Only

Mark this checkbox if you want to shut down only selected instances. The Select Instances button becomes active.

Select Instances

Click the Select Instances button to choose only those instances you want to shut down.

 Related Topics


Creating a Job for a Parallel Server or Parallel Server Instance

You can create a job with a parallel server or a parallel server instance as the destination. To create a new job follow these steps:

1.	Select Create Job from the Job menu to display the Create Job property sheetParallel_Server_Create_Job_Property_Sheet>refwin.

2.	Complete the pages of the Create Job property sheet.

3.	Determine whether the job is ready to submit. Click the Submit button to submit the job to the agents at the selected destinations. The job appears in the Active Jobs window.

4.	Click the Save button to save the job. The job appears in the Job Library window. You can modify or submit a saved job at a later time.

Note: There is usually a slight delay between submitting the job and notification by the agent.

To modify or view details about a job, see Creating, Modifying, or Viewing a Job.

 Related Topics


Parallel Server Create Job Property Sheet

Use the Create Job property sheet to specify the details of a new job. The Create Job property sheet contains these pages:

•	General page - Use the General page to specify the job name, description, type, and destination.

•	Task page - Use the Task page to choose the tasks that you want the job to perform.

•	Parameters page - Use the Parameters page to set the runtime parameters for the task. The parameters that appear on this page depend on which task you choose on the Task Page.

•	Schedule page - Use the Schedule page to schedule the time and frequency you want Oracle Enterprise Manager to run the job.

 Related Topics


Create Job - General Page

Use the General page to specify the job name, description, type, and destination. The General page contains these parameters:

Job Name

Enter the name of the new job.

Description

Enter a description of the job.

Destination Type

Select a destination type from the drop-down list.  You can choose parallel server, parallel server instance, database, listener, node, or name server.

Destinations

Click the destinations of the job in the Available Destinations list, then click the << (Add) button to move the destination to the Selected Destinations list. To remove a destination from a job, click the destination in the Selected Destination list, then click the >> (Remove) button.

The destinations are determined by your selection of Destination Type. The destinations include parallel servers, parallel server instances, databases, listeners, nodes, name servers, and groups of these objects.

•	For a parallel server task, a list of parallel servers and parallel server groups displays.

•	For a parallel server instance, a list of parallel server instances displays.

•	For a database task, a list of databases and database groups displays.

•	For an operating system task, a list of nodes and node groups displays.

•	For a listener task, a list of listener and listener groups displays

Fixit Job

Check this box if you want to use this job as the fixit job for an event occurrence. The job cannot be scheduled.

 Related Topics


Create Job - Task Page

Use the Task page to choose the tasks that you want the job to perform. The list of tasks that appear are different depending on whether you select a parallel server or a parallel server instance as your Destination Type in the General page.

Move the tasks between the Available and Selected Tasks lists with the <<(Add) and >>(Remove) buttons.

Available Tasks

Click a task, then click the << (Add) button to include the task in the job. You can add multiple tasks to the job from the Available Tasks scrolling list.

Selected Tasks

The tasks you move into this list will be executed. To remove tasks from this list: click the task, then click the >>(Remove) button.

Tasks for Parallel Server Destinations

If your Destination Type is a parallel server, you can choose from these tasks:

Parallel Server Startup	Parallel Server Shutdown
For a description of these tasks and the parameters you need to supply, see Parameters for the  Parallel Server Startup Task and Parameters for the Parallel Server Shutdown Task.

Tasks for Parallel Server Instance Destinations

If your Destination Type is a parallel server instance, you can choose from these tasks:

Backup Tablespace	Broadcast Message
Export	Import
Loader	Run DBA Script
Run OS Command	Run SQL *Plus
Run TCL	Shutdown Database
Startup Database
For a description of these tasks and the parameters you will need to supply, see Predefined Tasks.

 Related Topics


Create Job - Parameters Page

Use the Parameters page to specify parameter settings for the job tasks you selected on the Tasks page. The parameters vary according to the job task.  To find out what parameters you need to supply, go to the Task page and follow the links for the specific task.

Two of the tasks are specific to parallel servers: Parallel Server Startup and Parallel Server Shutdown. For a description of the parameters you need to supply for these tasks, see Parameters for the  Parallel Server Startup Task and Parameters for the Parallel Server Shutdown Task.

 Related Topics


Parameters for the Parallel Server Startup Task

When you select the Parallel Server Startup task on the Task page, you need to enter the following parameters on the Parameters page.

Startup

Select the start up modes for the job from the drop-down list.

Configuration File

Enter the fully qualified path to the parallel server configuration file that resides in the managed system.  By default, this will be the file $ORACLE_HOME/ops/ops_name.conf where ops_name is the name of the parallel server.

Override Preferred Credentials

You can use the preferred credentials that have been set up for the database, or you can enter a Username and Password. If you check the box to override the credentials, you must enter a Username and Password.

Note: the names of parallel servers appear in the Preferred Credentials window but the instances belonging to parallel servers do not. When you set Preferred Credentials for a parallel server, its instances inherit those settings.

Username

Enter the username for accessing the database.

Password

Enter the password corresponding to the specified username. The password can be a null string.

Connect As

Open the drop-down list and click SYSDBA (default) or SYSOPER.

Restrict Connections

Starts a parallel server in restricted mode. Connections are limited to those users who have been granted the RESTRICTED SESSION system privilege.

Force Startup

Forces the parallel server to start regardless of the operating circumstances.

 Related Topics


Parameters for the Parallel Server Shutdown Task

When you select the Parallel Server Shutdown task on the Task page, you need to enter the following parameters on the Parameters page.

Mode

Click the Immediate button (default) or the Abort button.

Connect As

Click the SYSDBA button (default) or the SYSOPER button.

Override Preferred Credentials

You can use the preferred credentials that have been set up for the database, or you can enter a Username and Password. If you check the box to override the credentials, you must enter a Username and Password.

Note: the names of parallel servers appear in the Preferred Credentials window but the instances belonging to parallel servers do not. When you set Preferred Credentials for a parallel server, its instances inherit those settings.

Username

Enter the username for accessing the database.

Password

Enter the password corresponding to the specified username. The password can be a null string.

Shutdown Database Only

Shuts down the database only. The services required for an instance, such as the listener, the lock manager, and so on, remain up and available. The option default is “on”.

 Related Topics


Create Job - Schedule Page

Use the Schedule page to schedule the time, date, and frequency that you want to execute your job. The Schedule page contains these parameters:

Execute

Click the frequency that you want the job executed. The choices are:

•	Immediately - schedules the job as soon as you click the Submit button. The job executes only one time.

•	Once - schedules the job only one time at the date and time you choose.

•	Interval - schedules a specific number of days between job executions. The interval can be a combination of hours and minutes, or number of days. Click  the value you want to change, then click the scroll buttons. You can also type in a new value.

•	On Day of Week - schedules the job on one or multiple days (Sunday, Monday, etc.) of the week. Click the days of the week to select the days you want the job scheduled.

•	On Date of Month - schedules the job on one or more days (1 - 31) of the month. Click the dates of the month to select the dates you want the job scheduled.

Start Execution

Choose the first date and time that you want the job executed. This is the starting time for any job scheduled on an interval.

•	Click the month, day, or year in the Date field, then click the scroll buttons to change the value. You can also type in new values.

•	Click the hour, minute, or AM/PM in the Time field, then click the scroll buttons to change the value. You can also type in new values.

End Execution

Choose the last date and time that you want the job executed. This option does not apply if you chose the Immediately or Once execution options.

•	Click the month, day, or year in the Date field,  then click the scroll buttons to change the value. You can also type in new values.

•	Click the hour, minute, or AM/PM in the Time field, then click the scroll buttons to change the value. You can also type in new values.

Time Zone

Select the time zone from the pull-down list. The choices are;

•	Agent - The agent schedules the job execution at each destination based on the system time of each agent. Jobs are not necessarily run simultaneously.

•	Console - The agent schedules the job execution simultaneously on all destinations based on the system time of the console.

•	GMT - The agent schedules the job execution simultaneously on all destinations based on Greenwich Mean Time.

 Related Topics


Related Tools for Parallel Servers and Parallel Server Instances

From the console, you can execute a number of database administration tools and utilities on parallel servers and parallel server instances. Click a parallel server or parallel server instance in the navigator window, then right mouse click. Select the Related Tools command.  A menu opens with the following choices.

Backup Manager	Lock Manager
Performance Manager	Schema Manager
Security Manager	SQL Worksheet
Storage Manager	Tablespace Manager
Instance Manager  (not available  for parallel servers)	TopSessions  (not available  for parallel servers)
Select the tool or utility you want to run for the parallel server or parallel server instance.

For more information on database tools and utilities, see Database Administration Tools and Utilities.


OEMGR Components
OEMGR Console components include the Event Management, Job Scheduling, Map, and Navigator systems. Related services include the Communication Daemon, Discovery Cache, and Repository.


Network Services
OEMGR manages and monitors services such as databases, listeners, Names Servers, and nodes.


Maps
Maps are custom graphical views of the network that you create with the Map component of the Oracle Enterprise Manager.


Agents
An agent is an intelligent process that manages communication between the Oracle Enterprise Manager Console and the node in the network where the agent resides.


Events
Events continuously monitor network objects, such as databases or nodes, for specific conditions that may occur. These conditions include loss of service or lack of available storage.


Jobs
Jobs consists of one or more tasks that allow you to administer databases or issue operating system commands.


Trademarks

Oracle Enterprise Manager Online Help, Release 1.3.5

Copyright ©1993, 1994, 1995, 1996, 1997 Oracle Corporation

All rights reserved.

This software was not developed for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It is the customer's responsibility to take all appropriate measures to ensure the safe use of such applications if the programs are used for such purposes.

This software/documentation contains proprietary information of Oracle Corporation; it is provided under a license agreement containing restrictions on use and disclosure and is also protected by copyright law. Reverse engineering of the software is prohibited.

If this software/documentation is delivered to a U.S. Government Agency of the Department of Defense, then it is delivered with Restricted Rights and the following legend is applicable:

Restricted Rights Legend Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of DFARS 252.227-7013, Rights in Technical Data and Computer Software (October 1988).

Oracle Corporation, 500 Oracle Parkway, Redwood Shores, CA 94065.

If this software/documentation is delivered to a U.S. Government Agency not within the Department of Defense, then it is delivered with "Restricted Rights", as defined in FAR 52.227-14, Rights in Data - General, including Alternate III (June 1987).

The information in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. Oracle Corporation does not warrant that this document is error-free.

Oracle and SQL*DBA are registered trademarks of Oracle Corporation. Oracle7, Oracle Enterprise Manager, Oracle Server Manager, and PL/SQL are trademarks of Oracle Corporation. Windows is a trademark of Microsoft Corporation.

OraTcl - Copyright ©1993 Tom Poindexter and U S West Advanced Technologies, Inc. Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies. Tom Poindexter and U S WEST make no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty. By use of this software the user agrees to indemnify and hold harmless Tom Poindexter and U S WEST from any claims or liability for loss arising out of such use.

All trade names referenced are the service mark, trademark, or registered trademark of the respective manufacturer. All other products or company names are used for identification purposes only, and may be trademarks of their respective owners.

Contributors:  Robert Abbott, Aravind Balakrishnan, Eric Belden, Jill Bentley, Sachiko Berry, Mark Brewster, Diarmuid Cawley, Larry Chen, Hung Huynh, Stella Jacoby, Shirley Joe, Jacinda Johnson, Valerie Kane, John Kennedy, Greg Krause, Bala Krishna, Keri Kruse, Dennis Lee, Eric Lee, Priscilla Lee, Yong Chwen Liu, Mark Osborn, Thomas Pfaeffle, Bob Purvy, Jay Rossiter, Phil Schwartz, Vipul Shah, Jay Smith, Michael Stern, Dave Stowell, Anatole Wilson, Michael Yao, Kirill Yurchenko, Kim Zabora