2 Database Tools on Windows

Database Tools and Operating System Compatibility

Almost all database tools are available on all supported versions of Windows. The following are not supported on Oracle Database for 64-bit Windows:

• Pro*COBOL

• Oracle Portal

• Oracle Migration Workbench

• Oracle Objects for OLE

• Oracle Open Gateways

• Oracle Transparent Gateways

• SQL*Plus Worksheet

• Database Upgrade Assistant

Oracle Enterprise Manager and its optional management packs have additional integrated tools to assist in managing databases. See Oracle Enterprise Manager Concepts for more information.

Preferred Database Tools

Table 2-1 lists various database tools you can use to perform common database administration tasks. Oracle recommends you use tools listed in the "Preferred Database Tool" column of the table. After choosing a tool to perform a task, go to Table 2-2, for instructions on how to start the tool.

D:\> exp system/manager full=y volsize=100m;
LRM-00101: unknown parameter name 'volsize'
EXP-00019: failed to process parameters, type 'EXP HELP=Y' for help
EXP-00000: Export terminated unsuccessfully

The following points refer to tools listed in Table 2-1, "Preferred Database Tools":

• ORADIM can only set a password when none was previously set. If a password has been previously set, then ORADIM can change it only by deleting and re-creating Oracle Database services.

• User Migration Utility can migrate local or external users to enterprise users. For more information, see "Using the User Migration Utility" in Oracle Database Advanced Security Administrator's Guide.

• Data Pump Export and Data Pump Import are preferred for Oracle Database 10g Release 1 (10.1) and later data; Export and Import are preferred for earlier data.

• If you back up files while you are shutting down the database, then your backup will be invalid. You cannot use an invalid backup to restore files at a later date.

• Oracle Database for 64-bit Windows supports enterprise users and roles stored in Oracle Internet Directory, but administration tools must be run from a 32-bit computer.

• You cannot use earlier versions of Oracle Wallet Manager to manage Oracle Database 10g Release 1 (10.1) or later wallets that contain password-based credentials for authentication to Oracle Internet Directory. These credentials are placed in the wallet when an Oracle Database server is registered in Oracle Internet Directory.

  The database wallet that Database Configuration Assistant automatically generates during database registration can only be used with an Oracle Database 10g Release 1 (10.1) or later server. You cannot use this database wallet for earlier versions of the database, nor can you use it for Oracle Internet Directory Release 9.0.4 or earlier.

• For guidelines on creating database objects, see Oracle Database Administrator's Guide.

• Oracle Enterprise Manager Grid Control can manage a 64-bit Windows database from a remote Linux or Windows 32-bit computer.

• Oracle Enterprise Manager Console is not supported in Oracle Database for 64-bit Windows.

Starting Database Tools in Multiple Oracle Homes

If you have multiple Oracle homes on your computer from previous releases, then see Appendix B, "Optimal Flexible Architecture", in Oracle Database Installation Guide for Microsoft Windows (x64) for a description of differences between Oracle homes in different releases.

Starting Database Tools from the Start Menu

Table 2-2 describes how to start assistants and other tools from the Start Menu. It also tells where to go for further information on using these products.

Starting Database Tools from the Command Line

Table 2-3 describes how to start Oracle Database tools from the command line, and where to go for further information on using these products.

Starting Windows Tools

Table 2-4 describes how to start each Windows tool and where to go for more information on using these products.

C:\> regedt

^Footnote 1 MMC is started whenever Oracle Administration Assistant for Windows is started.

Windows Processing Options

This section discusses possible values for the operating system dependent file processing specifications string option (os_file_proc_clause), referred to in "Specifying Datafile Format and Buffering" in Chapter 8, "SQL*Loader Control File Reference", in Oracle Database Utilities.

INFILE mydata.dat "str '\n'"

INFILE mydata.dat "str x'0a'"

RECORDS DELIMITED BY '\n'

RECORDS DELIMITED BY 0x'0a'

INFILE "mydata.dat" "var n"

Case Study Files

The distribution media for SQL*Loader contains case study files for control files, datafiles, and setup files in ulcase1,...ulcase11 in the following directory: Oracle_Home\rdbms\demo.

Specifying the Bad File

When SQL*Loader executes, it can create a file called a bad file or reject file in which it places records that were rejected because of formatting errors or because they caused Oracle Database errors. If you have specified that a bad file is to be created, it overwrites any existing file with the same name; ensure that you do not overwrite a file you wish to retain.

Control File Conventions

When preparing SQL*Loader control files (.ctl), you must follow certain syntax and notational conventions.

In full path descriptions, backslashes do not require escape characters or other special treatment. When embedding a single or double quotation mark inside a string delimited by double quotation marks, place a backslash escape character before the embedded quotation mark.

When specifying datatypes in the SQL*Loader control file, note that the default sizes of native datatypes shown in Table 2-5 are specific to Windows. These datatypes can be loaded with correct results only between systems where they have the same length in bytes. You cannot override these defaults in the control file. If the byte order is different between the systems, you can indicate the byte order of the data with the BYTEORDER parameter, or you can place a byte-order mark (BOM) in the file.

^Footnote 1 The default listed is correct if INTEGER is specified without a size. But INTEGER(n) is also allowed. In that case, n specifies the size of the INTEGER field in bytes.

Using Event Viewer to Monitor a Database

Event Viewer lets you monitor events in your system. An event is an important occurrence in the system or application (such as Oracle Database) that requires user notification. While messages for major events can appear on-screen as you work at your computer, events not requiring your immediate attention are recorded by Windows in the Event Viewer log file. You can then view this information at your convenience.

Event Viewer can be used to monitor Oracle Database events, such as:

• Initialization of System Global Area for active instance

• Initialization of Program Global Area (PGA) for background processes of active instance

• Connection to Oracle Database using AS SYSDBA

In addition, the operating system audit trail is logged to Event Viewer.

Using Microsoft Management Console to Administer a Database

Microsoft Management Console provides a central location for network administration. Microsoft Management Console hosts applications (called snap-ins) that administrators can use to manage their networks. Oracle snap-ins enable database administrators to:

• Configure Oracle Database administrators, operators, users, and roles so the Windows operating system can authenticate them

• Configure OracleServiceSID

• Modify registry parameters for all Oracle homes on the computer

• Modify the computer hostname, username, and password for the database being monitored by Oracle Counters for Windows Performance Monitor

• View and terminate an Oracle Database thread

Using Oracle Counters for Windows Performance Monitor

Oracle Counters for Windows Performance Monitor is integrated into Windows Performance Monitor. This tool enables you to view performance of processors, memory, cache, threads, and processes. Performance information provided includes device usage, queue lengths, delays, throughput measurements, and internal congestion measurements. This information is provided as charts, alerts, and reports.

You can use Oracle Counters for Windows Performance Monitor to monitor key Oracle Database information, such as:

• Library cache

• Buffer cache

• Data dictionary cache

• Redo log buffer cache

• Thread activity

You can use your findings to improve database performance.

Using Registry Editor to Modify Configuration Information

Oracle Database stores its configuration information in a structure known as the registry. You can view and modify this configuration information through Registry Editor. The registry contains configuration information for your computer and must not be accessible for editing by inexperienced users. Only experienced administrators should view and change this information.

Registry Editor displays configuration information in a format similar to Windows Explorer. In the left-hand window is a tree-like format consisting of keys (or folders). When one of these keys is highlighted, parameters and values assigned to that key are displayed in the right-hand window.

When you install products from your CD-ROM, configuration parameters are automatically entered in the registry. These parameters are read each time your Windows computer is started and whenever an Oracle Database product is started. These parameters include settings for:

• Oracle home directory

• Language

• Company name

• Oracle home subdirectories for individual products

• Individual products such as SQL*Plus

• Services

  See Also:

  Chapter 14, "Configuration Parameters and the Registry" for definitions of Oracle Database configuration parameters and specific instructions on using the registry to modify Oracle Database configuration parameters

Using Task Manager to Monitor Applications and Processes

Task Manager has three tabs:

• Applications tab displays what applications are running. This is useful for identifying and ending unresponsive tasks. (Oracle Database does not appear as an application because it runs as a service.)

• Processes tab displays details of currently running processes and their resource usage. Columns are customizable.

• Performance tab graphically displays real-time CPU and memory usage, which is useful for spotting sudden changes.

Using Local Users and Groups to Manage Users and Groups

Local Users and Groups enables you to manage users and groups on Windows 2000 and Windows XP. Specifically, you can:

• Create and modify local user accounts

• Create and modify user profiles

• Create, add, and delete local groups