Escolar Documentos
Profissional Documentos
Cultura Documentos
Getting Started
February 1999
Part No. A68694-01
Oracle8i Enterprise Edition Getting Started
Primary Authors: Bronya Feldmann, Herbert Kelly, Mark Kennedy, Helen Slattery, and Jeff Stein
The information contained 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. No part of this document may be reproduced or transmitted in any form or by
any means, electronic or mechanical, for any purpose, without the express written permission of Oracle
Corporation.
Hazardous Applications The Programs are not intended for use in any nuclear, aviation, mass transit,
medical, or other inherently dangerous applications. It shall be licensee's responsibility to take all
appropriate fail-safe, back up, redundancy and other measures to ensure the safe use of such applications
if the Programs are used for such purposes, and Oracle disclaims liability for any damages caused by
such use of the Programs.
If this Program 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 Programs delivered subject to the DOD FAR Supplement are 'commercial
computer software' and use, duplication and disclosure of the Programs shall be subject to the licensing
restrictions set forth in the applicable Oracle license agreement. Otherwise, Programs delivered subject to
the Federal Acquisition Regulations are 'restricted computer software' and use, duplication and
disclosure of the Programs shall be subject to the restrictions in FAR 52..227-14, Rights in Data -- General,
including Alternate III (June 1987). Oracle Corporation, 500 Oracle Parkway, Redwood Shores, CA 94065.
Trademark Notice Some Oracle products require the Java™ Runtime Environment. The Java™ Runtime
Environment (“The Software”) is developed by Sun Microsystems, Inc. 2550 Garcia Avenue, Mountain
View, California 94043 Copyright (c) 1998 Sun Microsystems, Inc. The Software and documentation is the
confidential and proprietary information of Sun Microsystems, Inc. (“Confidential Information”). You
shall not disclose such Confidential Information and shall use it only in accordance with the terms of the
license agreement proved with The Software.
Oracle is a registered trademark, and ConText, Enabling the Information Age, Net8, Oracle ConText,
Oraclemetals, OracleMetaLink, Oracle Names, Oracle Store, Oracle SupportInsite, Oracle SupportNews,
Oracle7, Oracle8i, PL/SQL, Pro*C/C++, Pro*COBOL, Programmer/2000, SQL*Loader, and SQL*Plus are
trademarks or registered trademarks of Oracle Corporation. Other names may be trademarks of their
respective owners.
Contents
i
New Products ................................................................................................................... ............. 2-4
New Features................................................................................................................................. 2-6
List of Oracle8i Enterprise Edition Products ................................................................................. 2-7
Licensing Information .................................................................................................................. 2-7
Oracle Enterprise Manager.......................................................................................................... 2-7
Net8................................................................................................................................................. 2-7
Choosing Which Oracle Products to Install.............................................................................. 2-8
How Server Installation Options Affect Network Configuration and Services........... 2-9
Oracle8i Enterprise Edition ................................................................................................ 2-11
Oracle8i Client...................................................................................................................... 2-25
Programmer/2000 ............................................................................................................... 2-34
Supported Protocol Stack Vendors ................................................................................................ 2-41
Unsupported Features ...................................................................................................................... 2-43
ii
Event Viewer ................................................................................................................... ............ 3-22
What Oracle Database Events Are Monitored? .............................................................. 3-22
Performance Monitor ................................................................................................................. 3-24
What Oracle Database Information is Monitored?......................................................... 3-24
Registry ........................................................................................................................................ 3-26
What Database Parameters Are Configured? ................................................................. 3-26
User Manager .............................................................................................................................. 3-28
What Oracle8i Database Tasks Can User Manager Perform?....................................... 3-28
iii
ORACLE_BASE Directory ......................................................................................................... 4-19
ORACLE_HOME Directory ....................................................................................................... 4-21
ADMIN Directory....................................................................................................................... 4-21
ORADATA Directory................................................................................................................. 4-22
DB_NAME Directory.................................................................................................................. 4-22
OFA and Multiple Oracle Home Configurations ....................................................................... 4-23
Specifying an ORACLE_HOME Directory .............................................................................. 4-23
Default OFA Database ............................................................................................................... 4-24
Non-Default OFA Database, Case 1......................................................................................... 4-26
Non-Default OFA Database, Case 2......................................................................................... 4-28
Increasing Reliability and Performance....................................................................................... 4-30
Disk Mirroring............................................................................................................................. 4-30
Disk Striping................................................................................................................................ 4-30
Using Raw Partitions for Tablespaces ..................................................................................... 4-31
Comparison Between OFA on Windows NT and UNIX ........................................................... 4-32
Directory Naming ....................................................................................................................... 4-32
ORACLE_BASE Directory ......................................................................................................... 4-32
Support for Symbolic Links on Windows NT ........................................................................ 4-32
iv
Oracle8i Client Release 8.1 to Oracle8 Release 8.0/Oracle7 Databases....................... 5-11
Multi-Versioning ........................................................................................................................ 5-12
Install Oracle7 and Oracle8i Databases in Multiple Oracle Homes .................................... 5-13
Install Oracle7 and Oracle8i Databases on Separate Computers ........................................ 5-14
Migrate an Oracle7 Database to an Oracle8i Database ......................................................... 5-15
Upgrade an Oracle8 Database to the Current Oracle8i Database Release ......................... 5-16
Migrate Oracle7 Clients to Oracle8i Clients ........................................................................... 5-17
Installing an Oracle 8.1 Database Where Version 7.x Already Exists ..................................... 5-18
Migrating an Oracle7 Database to Oracle8i................................................................................. 5-21
Ten Issues That Can Affect Oracle7 to Oracle8i Migration .................................................. 5-21
Installing Appropriate Versions of SQL*Net .................................................................. 5-24
Migrating Using Oracle Data Migration Assistant................................................................ 5-25
What To Do Before Using Oracle Data Migration Assistant ........................................ 5-25
Migrating Using MIG................................................................................................................. 5-27
Step 1: What To Do Before Using MIG............................................................................. 5-28
Step 2: Shut Down the Oracle7 Database......................................................................... 5-31
Step 3: Back Up the Oracle7 Database.............................................................................. 5-32
Step 4: Install MIG From Oracle8i Enterprise Edition CD-ROM .................................... 5-34
Step 5: Run MIG................................................................................................................... 5-36
Step 6: Create Oracle8i Services and Database Files ...................................................... 5-39
Step 7: Remove Oracle7 Software (Optional) .................................................................. 5-44
Upgrading an Oracle8 Database Release 8.0.x to 8.1.5............................................................... 5-45
Upgrading Using Oracle Data Migration Assistant .............................................................. 5-45
Upgrading Using SQL Scripts .................................................................................................. 5-47
Step 1: Shut Down the Release 8.0.x Database ................................................................ 5-48
Step 2: Back Up the Release 8.0.x Database ..................................................................... 5-48
Step 3: Edit the COMPATIBLE Parameter in the 8.0.x INITSID.ORA File ................. 5-49
Step 4: Install Oracle8i Enterprise Edition Release 8.1.5 .................................................. 5-50
Step 5: Run the SQL Scripts ............................................................................................... 5-51
Migration Issues for Net8 and SQL*Net ...................................................................................... 5-55
Location of Network Configuration Files ............................................................................... 5-55
Listener Configuration in Multiple Oracle Home Installations........................................... 5-56
Changing Listener.ora for Migrated Databases ..................................................................... 5-57
Changes in Handling of TCP/IP Listening Address ............................................................ 5-57
v
Enabling NT Native Authentication ....................................................................................... 5-58
NT Authenticated Users in the Database ................................................................................ 5-58
Connection using Multi-threaded Server Mode ................................................................... 5-59
Installing Appropriate Versions of SQL*Net.......................................................................... 5-60
Installation of Oracle Names..................................................................................................... 5-60
Moving Database Files to an OFA-Compliant Directory.......................................................... 5-61
8 Creating a Database
Before You Create a Database........................................................................................................... 8-2
Naming Conventions for Oracle Databases ............................................................................. 8-2
Installing Oracle Server (the Database Component) ............................................................... 8-2
Creating Data Files and Log Files on Remote Computers ..................................................... 8-3
Creating a Database Using Tools ..................................................................................................... 8-4
Using Oracle Database Configuration Assistant ..................................................................... 8-4
Creating a Database .............................................................................................................. 8-5
Modifying a Database........................................................................................................... 8-9
Deleting a Database............................................................................................................. 8-10
Using BUILD_DB.SQL ............................................................................................................... 8-10
How to Create a Database.................................................................................................. 8-11
Creating Directories ............................................................................................................ 8-12
Exporting an Existing Database ........................................................................................ 8-12
Deleting Database Files ...................................................................................................... 8-13
Modifying the INIT.ORA File............................................................................................ 8-14
Creating and Starting an Oracle Service .......................................................................... 8-16
Putting the CREATE DATABASE Statement in a Script............................................... 8-17
Creating a Database ............................................................................................................ 8-19
Importing a Database.......................................................................................................... 8-22
Updating the ORACLE_SID in the Registry ................................................................... 8-23
Backing Up the New Database.......................................................................................... 8-25
Storing Database Files on Compressed Drives ............................................................... 8-26
Using ORADIM to Administer an Oracle Instance ................................................................... 8-27
Creating an Instance................................................................................................................... 8-28
vii
Starting an Instance ........................................................................................................... ......... 8-29
Stopping an Instance .................................................................................................................. 8-29
Modifying an Instance ............................................................................................................... 8-30
9 Administering a Database
Managing Oracle Services................................................................................................................. 9-2
Oracle Service Naming Conventions for Multiple Oracle Homes ........................................ 9-2
Available Oracle Services ............................................................................................................ 9-4
Starting Oracle Services ............................................................................................................... 9-5
Stopping Oracle Services ............................................................................................................. 9-6
Auto-starting Oracle Services ..................................................................................................... 9-8
Starting and Shutting Down a Database with SQL*Plus ......................................................... 9-10
Starting and Shutting Down a Database Using Services.......................................................... 9-11
Running Multiple Instances ........................................................................................................... 9-16
Creating Password Files .................................................................................................................. 9-17
Viewing Password Files............................................................................................................. 9-19
Deleting Password Files .................................................................................................................. 9-20
Connecting as INTERNAL with a Password File ....................................................................... 9-20
Changing the INTERNAL Password ............................................................................................ 9-21
Encrypting Database Passwords .................................................................................................... 9-22
Archiving Redo Log Files ................................................................................................................ 9-23
Step 1: Change the Archive Mode to ARCHIVELOG ........................................................... 9-23
Step 2: Enable Automatic Archiving........................................................................................ 9-25
Using the ORADEBUG Utility....................................................................................................... 9-27
11 Monitoring a Database
Database Monitoring Overview .................................................................................................... 11-2
Using Oracle Performance Monitor .............................................................................................. 11-3
Registry Information .................................................................................................................. 11-3
Accessing Oracle Performance Monitor.................................................................................. 11-4
Monitoring Oracle8i Objects ..................................................................................................... 11-5
Understanding Oracle Performance Objects .......................................................................... 11-7
Oracle Performance Monitor Troubleshooting Information.............................................. 11-10
Using the Event Viewer ................................................................................................................. 11-11
Accessing the Event Viewer.................................................................................................... 11-11
Reading the Event Viewer....................................................................................................... 11-12
Using the Event Viewer ........................................................................................................... 11-13
Managing the Event Viewer ................................................................................................... 11-14
Using Trace and Alert Files ........................................................................................................... 11-14
Viewing Threads Using the Oracle Administration Assistant for Windows NT ........... 11-15
ix
13 Developing Applications
Java Products Overview................................................................................................................... 13-2
Oracle Java Option...................................................................................................................... 13-2
Oracle Java Utilities .................................................................................................................... 13-2
Oracle Java Database Connectivity (JDBC) Drivers .............................................................. 13-2
Oracle SQLJ Translator .............................................................................................................. 13-3
Building External Procedures ......................................................................................................... 13-4
External Procedures Overview ................................................................................................. 13-4
Installing and Configuring ........................................................................................................ 13-5
Installing Oracle8i Enterprise Edition .............................................................................. 13-5
Configuring Net8................................................................................................................. 13-5
Writing an External Procedure ................................................................................................. 13-6
Building a DLL ............................................................................................................................ 13-7
Registering an External Procedure........................................................................................... 13-8
Executing an External Procedure ........................................................................................... 13-10
Enabling Multi-Threaded Callout Support........................................................................... 13-10
Additional Documentation ..................................................................................................... 13-11
Accessing Web Data with Intercartridge Exchange.................................................................. 13-12
Configuring Intercartridge Exchange .................................................................................... 13-12
Using Intercartridge Exchange ............................................................................................... 13-13
Packaged Function UTL_HTTP.REQUEST ................................................................... 13-14
Packaged Function UTL_HTTP.REQUEST_PIECES.................................................... 13-14
UTL_HTTP Exception Conditions .................................................................................. 13-16
Exception Conditions and Error Messages.................................................................... 13-16
Troubleshooting................................................................................................................. 13-18
A Directory Structures
Oracle8i Enterprise Edition Directory Structure........................................................................... A-2
ORACLE_HOME........................................................................................................................... A-2
ADMIN........................................................................................................................................... A-7
ORADATA..................................................................................................................................... A-7
Oracle8i Client Directory Structure................................................................................................. A-8
Oracle Programmer Directory Structure....................................................................................... A-11
Net8 Directory Structure.................................................................................................................. A-13
x
B Oracle8i Database Specifications for Windows NT
Initialization Parameter File (INIT.ORA) Overview ................................................................... B-2
Location of the Initialization Parameter File ............................................................................ B-2
Editing the Initialization Parameter File ................................................................................... B-2
Sample File .................................................................................................................................... B-3
Initialization Parameters ................................................................................................................... B-4
Initialization Parameters Without Windows NT-Specific Values......................................... B-6
Displaying Initialization Parameter Values ...................................................................... B-6
Database Initialization Parameters ............................................................................................ B-7
Calculating Database Limits............................................................................................................. B-8
Calculating Index Size ....................................................................................................................... B-9
xi
D Net8 Configuration Parameters, Services, and Port Numbers
Understanding Net8 Registry Parameter and Subkeys ............................................................... D-2
Net8 Parameters............................................................................................................................ D-2
Net8 Service Subkeys ................................................................................................................... D-2
Understanding Optional Configuration Parameters ................................................................... D-3
LOCAL ........................................................................................................................................... D-3
TNS_ADMIN................................................................................................................................. D-4
USE_SHARED_SOCKET ............................................................................................................. D-4
Advanced Network Configuration.................................................................................................. D-5
Configuring Authentication Methods ....................................................................................... D-5
NDS Authentication .............................................................................................................. D-5
Windows NT Native Authentication.................................................................................. D-6
Using the NDS Naming Method ................................................................................................ D-7
NetWare Server Configuration............................................................................................ D-7
Client Configuration ............................................................................................................. D-8
Client Connection .................................................................................................................. D-8
Configuring Security for Named Pipes Protocol ..................................................................... D-8
Net8 Services and Port Numbers .................................................................................................. D-10
Services ........................................................................................................................................ D-10
TCP/IP Port Numbers .............................................................................................................. D-13
xii
Compatibility Issues ............................................................................................................. F-6
Creating an Extended Partition ........................................................................................................ F-7
Creating Logical Partitions in an Extended Partition.............................................................. F-8
Assigning Symbolic Links to Each Logical Partition ........................................................... F-10
Removing or Ignoring Links..................................................................................................... F-11
Creating a Tablespace in a Raw Partition.................................................................................... F-12
G SNMP Support
What Is the Purpose of SNMP?........................................................................................................ G-2
Oracle SNMP Support ....................................................................................................................... G-2
Oracle SNMP Agent for Oracle Services........................................................................................ G-3
Configuring Oracle SNMP Agent ................................................................................................... G-4
Controlling the Master Agent and the Encapsulator ................................................................... G-6
Starting the Master Agent ........................................................................................................... G-6
Starting the Encapsulator ............................................................................................................ G-6
Understanding the MASTER.CFG File .......................................................................................... G-9
Understanding the ENCAPS.CFG File ........................................................................................ G-10
Installing Oracle SNMP Agent with Other Network Management Systems...................... G-12
Glossary
Index
xiii
xiv
Contact Us!
Oracle8i Enterprise Edition, Release 8.1.5 for Windows NT
Part No. A68694-01
This document describes how to contact Oracle Corporation if you have issues with
the documentation or software. It also provides a list of useful resources for Oracle
partners and developers.
xv
How to Contact Oracle Support Services
Please copy this page and distribute within your organization as necessary.
Oracle Support Services can be reached at the following telephone numbers. The
hours of business are detailed in your support contract and the Oracle Customer
Support Guide in your kit.
Oracle Support
Services In... Call...
United States of + (650) 506-1500 for customers with support contracts
America
+ (650) 506-5577 to obtain a support contract
Europe +44 1344 860 160 or the local support center in your country.
All other The telephone number for your country listed at the following Web site:
locations
http://www.oracle.com/support/html/suploc.html
Oracle Support Services telephone numbers are also listed in the Oracle
Customer Support Guide in your kit.
Please complete the following checklist before you call. If you have this information
ready, your call can be processed much quicker.
❏ The operating system name and release number on which your application is
running.
xvi
❏ The release numbers of the Oracle Server and associated products involved in
the current problem. For example, Oracle8i Enterprise Edition release 8.1.5.0.0
and Oracle Enterprise Manager release 2.0.0.0.0.
❏ The exact error codes and messages. Please write these down as they occur.
They are critical in helping Oracle Support Services to quickly resolve your
problem.
xvii
■ When did it happen? For example, during peak system load, or after a
certain command, or after an operating system upgrade.
❏ Keep copies of any trace files, core dumps, and redo log files recorded at or near
the time of the incident. Oracle Support Services may need these to further
investigate your problem.
xviii
Resources for Oracle Partners and Developers
This section provides information on partner programs and resources for Oracle
database administrators and application developers.
xix
Information Source Description
Oracle Support Services’ Support Web Center Oracle Support Services offers a range of programs so you
can select the support services you need and access them in
http://www.oracle.com/support/
the way you prefer: by telephone, electronically, or face to
face. These award-winning programs help you maintain
your investment in Oracle technology and expertise.
Here are some of the resources available in the Support Web
Center:
OracleMetaLink OracleMetaLink is Oracle Support Services' premier Web
support service. It is available to Oraclemetals customers
http://www.oracle.com/support/
(Gold, Silver, Bronze), 24 hours a day, seven days a
elec_sup/index.html
week.
OracleLifecycle OracleLifecycle is designed to deliver customized,
industry-focused, full life-cycle support solutions that
http://www.oracle.com/support/
enable industry leaders to use Oracle technology to
sup_serv/lifecycle/index.html
make smart business decisions, achieve operational
excellence, and succeed in their markets.
ExpertONLINE Oracle Support Services has launched a new line of
services called ExpertONLINE. These services provide
http://www.oracle.com/support/
online database administration for companies looking
sup_serv/online/index.html
to supplement their existing DBA staff or fill a DBA
role. Services range from ExpertDETECT, a monitoring,
diagnostic, and recommendation service, to ExpertDBA,
a full online database administration service.
Virtual Support Analyst (VSA) VSA is Oracle's Internet e-mail service; it is available to
U.S. customers with an Oraclemetals support agreement.
http://www.oracle.com/support/
With VSA, you can initiate a request for assistance
sup_serv/vsa_start.html
through e-mail, bypassing the queues you may
encounter when using telephone support. VSA also
enables you to access Oracle's bug database.
Customer Service This site provides resources to make your interactions
with Oracle as easy as possible. Among the things you
http://www.oracle.com/support/
can do are
cus_serv/index.html
■ Learn what is a CPU Support Identification (CSI)
number
■ Update your technical contact information
■ Find out whom to contact for invoice and collection
issues
■ Request product update shipments
■ Access a glossary of Oracle Support Services terms
xx
Information Source Description
U.S. Customer Visit Program This U.S.-based program has been established to help
our customers understand and obtain maximum benefit
http://www.oracle.com/support/
from the support services they have purchased.
cus_serv/cus_visit.html
The visit typically offers a customized orientation
presentation, a comprehensive overview and
demonstration of Oracle’s electronic services, and
helpful tips on working more effectively with Oracle
Support Services.
Support Web Center Library This site contains articles, guides, and other
documentation to help you leverage the wealth of
http://www.oracle.com/support/
knowledge and reference material that Oracle Support
library/index.html
Services produces.
Product Availability Send an e-mail to request information on future product
releases on Oracle for Windows NT and Windows 95/98.
infowin@us.oracle.com
xxi
xxii
Before You Begin
xxiii
Prerequisites
This guide assumes that you are familiar with the following:
■ Windows NT, and have installed and tested it on your computer system
■ Object-relational database management concepts
Intended Audience
This guide is necessary for anyone installing, configuring, or administering Oracle8i
Enterprise Edition.
xxiv
Chapter 4, "Multiple Oracle Homes and Optimal Flexible Architecture"
Describes how to use multiple Oracle homes and an Optimal Flexible
Architecture (OFA) configuration for placement of database files. Read this
chapter before installing Oracle8i Enterprise Edition.
xxv
Appendix A, "Directory Structures"
Describes the default directory structures created when you install Oracle8i
Enterprise Edition, Oracle8i Client, or Programmer/2000.
Glossary
Provides brief descriptions of terms used throughout this guide.
xxvi
Documentation and Code Conventions
The following conventions are used in this guide:
xxvii
Convention Example Meaning
ORACLE_HOME and Go to the ORACLE_BASE\ORACLE_ In previous releases when you installed
ORACLE_BASE HOME\RDBMS\ADMIN directory Oracle8i Enterprise Edition, all
subdirectories were located under a top
level ORACLE_HOME directory, that by
default was:
■ C:\ORANT for Windows NT
■ C:\ORAWIN95 for Windows 95
■ C:\ORAWIN for Windows 3.1
or whatever you may have called your
Oracle home.
In this Optimal Flexible Architecture
(OFA)-compliant release, all
subdirectories are no longer under a top
level ORACLE_HOME directory. There is
now a new top-level directory called
ORACLE_BASE that by default is
C:\ORACLE. If you install Oracle8i
Enterprise Edition release 8.1.5 on a clean
computer (that is, there is no other Oracle
software on the computer), the default
settings for the first Oracle home
directory is C:\ORACLE\ORA81. If you
run Oracle Universal Installer again and
install release 8.2.x, the second Oracle
home directory is called \ORA82. These
Oracle home directories are located
directly under ORACLE_BASE.
All directory path examples in this guide
follow OFA conventions.
See Chapter 4, "Multiple Oracle Homes
and Optimal Flexible Architecture" for
additional information on OFA
compliances and for information on
installing Oracle products in non-OFA
compliant directories.
%ORACLE_HOME% SVRMGR> @%ORACLE_HOME%\ADMIN\DB_ In Server Manager commands, you may
NAME\ADHOC\CATALOG.SQL see %ORACLE_HOME%. Server Manager is
able to locate your Oracle Home directory
using the %ORACLE_HOME% variable.
This convention can be used in Server
Manager, SQL*Plus, Export Utility, and
Import Utility.
xxviii
Convention Example Meaning
HOME_NAME OracleHOME_NAMETNSListener Represents the Oracle home name.
The home name can be up to sixteen
alphanumeric characters. The only special
character allowed in the home name is the
underscore.
HOMEID HOME0, HOME1, HOME2 Represents a unique registry subkey for
each Oracle home directory in which you
install products. A new HOMEID is
created and incremented each time you
install products to a different Oracle home
directory on one computer. Each
HOMEID contains its own configuration
parameter settings for installed Oracle
products.
Symbols period . Symbols other than brackets and vertical
bars must be entered in commands
comma ,
exactly as shown.
hyphen -
semicolon ;
colon :
equal sign =
backslash \
single quote ’
double quote "
parentheses ()
xxix
xxx
1
Getting Started with Your Documentation
This chapter introduces you to the Oracle8i Enterprise Edition for Windows NT
documentation set. Read this chapter before installing or using Oracle8i Enterprise
Edition.
Specific topics discussed:
■ Documentation Formats
■ What Documentation Did I Receive?
■ What Documentation Do I Read First?
■ Starting Oracle Information Navigator
■ Starting Adobe Acrobat Reader
Documentation Formats
This table describes the format and availability of documents in your Oracle8i
Enterprise Edition kit and the tools required to view them.
Oracle8i Enterprise Edition for Windows NT and Windows 95/98 Release Notes
Release notes and Readme files for Oracle8i Enterprise Edition and additional
Oracle products.
New Products
This table describes the new products of Oracle8i Enterprise Edition release 8.1.5.
New Features
This table describes the new features of Oracle8i Enterprise Edition release 8.1.5
specific to Windows NT.
Licensing Information
Although the Oracle8i Enterprise Edition for Windows NT CD-ROM in your kit
contains many Oracle products, you may install and use only those products for
which you have purchased licenses. For additional licensing information, refer to
the Global License Terms booklet in your kit.
Oracle Support Services does not provide support for products where licenses have
not been purchased.
Net8
Net8, which is included on the Oracle8i Enterprise Edition for Windows NT
CD-ROM, supports very large scale mission-critical environments. It offers a
state-of-the-art security server and simplifies administration and configuration of
both large and small environments. See the Net8 Administrator’s Guide for a description
of Net8 features in general. The features described in the tables beginning on
page 2-11 are specific to the NT and Windows 95/98 platforms.
Listener Configuration
During server installation, the Net8 Configuration Assistant configures the listener
as described below.
If you do not want net service names to reside in the TNSNAMES.ORA, click Cancel
and see Chapter 6, "Configuring the Naming Methods with the Listener" of the Net8
Administrator’s Guide to configure another naming method.
Windows NT Services
The installation options you choose will have different effects on your Windows NT
services, as described below.
Custom Installation
When you install Oracle Connection Manager, using the Custom Installation option,
the following NT services are installed. After configuration, you must start the
service(s) you need:
Oracle8i Client
This table describes the Oracle products that are available when you select the
Oracle8i Client installation option.
Oracle8i Client can be installed on Windows NT, Windows 95, and Windows 98.
Programmer/2000
This table describes the Oracle products that are available when you select the
Programmer/2000 installation option.
Programmer/2000 can be installed on Windows NT, Windows 95, and Windows 98.
Unsupported Features
The following features are currently unsupported on the Microsoft NT and
Windows 95/98 platforms.
Feature Description
TRCROUTE Client application not supported on the NT
and Windows platforms.
SPAWN SPAWN command in the listener control
utility is not supported on the NT and
Windows platforms.
Pre-SPAWNED dedicated Not supported by the listener.
server processes
Oracle Utilities
DBVERIFY (DBVERF) Yes Yes
Export Utility (EXP) Yes Yes
Import Utility (IMP) Yes Yes
Migration Utility (MIG) Yes No
OCOPY Yes Yes
OPERFCFG Yes Yes
ORADIM 2 Yes No
Note: The table above describes tasks that can be performed with
Server Manager or SQL*Plus. In release 8.1.5, all Server Manager
text and examples in this guide have been replaced with SQL*Plus
equivalents. Although Server Manager will continue to be shipped
with 8.1.x releases, Oracle Corporation strongly recommends that
you migrate to SQL*Plus as soon as possible. See your SQL*Plus
documentation for information on using SQL*Plus to perform
database administration tasks.
Starting Tools from Release 8.0.4 and later 8.0.x Multiple Oracle Homes
If you are using multiple Oracle homes functionality, the command to start a tool
includes a [HOME_NAME], where [HOME_NAME] indicates the name of a
different Oracle home. Note that the first Oracle home created on your computer does
not have [HOME_NAME] appended to the group. For example:
To start Oracle Database Assistant from the first Oracle home, choose:
Start > Programs > Oracle for Windows NT > Oracle Database Assistant
To start Oracle Database Assistant from an additional Oracle home, choose:
Start > Programs > Oracle for Windows NT - [HOME_NAME] > Oracle Database
Assistant
2. Choose the login method for the database administration application and enter
the appropriate connect information.
■ Login to the Oracle Management Server.
When a database administration application is connected to the Oracle
Management Server, the DBA application can access all the databases on
discovered nodes in that repository, and all of these databases appear in the
client’s tree list of managed objects. The Oracle Management Server must be
running for a DBA application to connect to it.
■ Connect directly to a single database.
When connected to a single database, the Oracle Management Server does
not need to be running, and that database is the only database that shows in
the client’s tree list. Your tnsnames.ora file must have an entry for the
database. You can also enter the host:port:sid connect string for your
service.
Note: You could also use the LaunchPad.
1. Choose Start > Program > Oracle-HOME_NAME > LaunchPad.
2. Choose DB Administration.
3. Choose the tool you want.
■ Select the database you want to administer in the Navigator tree, then
choose the tool from the Related Tools menu of the context-sensitive menu.
■ Choose the application from the Console Tools menu or from the Launch
Palette, then enter the connect information in the Login Information dialog
box.
Note: When you select a database before starting 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 appears.
This table describes how to start each Oracle Enterprise Manager tool through the
Console, and where to go for further information on using these tools.
Oracle Enterprise Choose Tools > Applications > For More Information, See...
Manager Tool
Instance Manager Oracle Instance Manager Oracle Enterprise Manager
Configuration Guide
Storage Manager Oracle Storage Manager Oracle Enterprise Manager
Configuration Guide
Schema Manager Oracle Schema Manager Oracle Enterprise Manager
Configuration Guide
Security Manager Oracle Security Manager Oracle Enterprise Manager
Configuration Guide
SQL Worksheet Oracle SQL Worksheet Oracle Enterprise Manager
The new worksheet is connected to the database you Configuration Guide
have selected in the Navigator tree list or in the map
window.
You can start the Backup Management wizards using one of the following
methods:
■ From the Console or Storage Manager, select the database, tablespaces, or
datafiles you want to administer in the Navigator tree; then, choose the
application from the Backup Management menu of the context-sensitive menu.
■ From Storage Manager > Tools menu > Backup Management.
You can start the Data Management wizards using one of the following methods:
■ From the Console or Schema Manager, select the database, tables, or datafiles
you want to administer in the Navigator tree; then, choose the application from
the Data Management menu of the context-sensitive menu.
■ From Storage Manager or Schema Manager > Tools menu > Data Management
Assistant Choose Start > Programs > Oracle - HOME_NAME > For More Information, See...
Oracle Data Migration Utilities > Oracle Data Migration Assistant ■ "Migrating Using Oracle
Migration Data Migration Assistant" on
Assistant page 5-25
■ Oracle8i Enterprise Edition
Installation for Windows NT
Oracle Database Oracle Enterprise Management > Database ■ "Using Oracle Database
Configuration Administration Applications > Database Configuration Configuration Assistant" on
Assistant Assistant page 8-4
■ Oracle8i Enterprise Edition
Installation for Windows NT
Net8 Assistant Network Administration > Net8 Assistant Net8 Administrator’s Guide
Net8 Easy Config Network Administration > Net8 Easy Config Net8 Administrator’s Guide
Oracle Web Application Development > Oracle Web Publishing Oracle Web Publishing Assistant
Publishing Assistant Getting Started for Windows NT
Assistant
Oracle Enterprise Management > Database Administration "Granting Database
Administration Applications > Oracle Administration Assistant for Administrator and Database
Assistant Windows NT Operator Privileges Using Oracle
Administration Assistant for
Windows NT" on page 10-6
Starting SQL*Plus
This table describes how to start SQL*Plus, and where to go for further information
on using this product:
Using SQL*Loader
This section describes Windows NT-specific information for using SQL*Loader
(SQLLDR).
""1 Stream record format in which each record is terminated by a newline character. The
maximum record size is 48 KB.
"FIX n" Fixed record format in which each record is exactly n bytes long. If the record is
terminated by a newline character, the newline character must be the nth byte.
"VAR xxxx" Load variable length records. Specify the OSD "VAR recsizehint" in the control file for
this option to take effect. The xxxx gives an estimate of the average record size to
SQL*Loader so that it can approximate buffer sizes accurately and not waste
memory. The default length is eighty characters. The xxxx does not specify how
many leading bytes of length are included in each record. It only acts as a hint to
SQL*Loader. Each record must always be preceded by five ASCII bytes containing
the length of the remainder of the record. For example, a record must look like the
following:
00024This is a 24 byte string
Any whitespace, carriage returns, or linefeeds at the end of the record are ignored
unless specifically included in the byte count in the length field.
1
Two double quote characters with no space in between.
Control Panel
The Control Panel enables you to modify system options such as computer services.
A service is an executable process registered in the registry and administered by
Windows NT. The registry automatically tracks and records security information
for each service you create.
Use the Services dialog box to start, stop, pause, or continue each of the Oracle
services available on the computer.
Oracle services are the same as Windows NT services. In order to connect to and use
an Oracle instance, an Oracle service is created during the database creation process
and associated with the Oracle database.
Once a service is created with your Oracle database, the service can run even while
no user is logged on. This is because your Oracle database starts each instance as a
service. This feature enables you to maintain workstation security while running
your Oracle database.
Event Viewer
Event Viewer enables you to monitor events in your system. An event is an
important occurrence in the system or application (such as your Oracle database)
that requires user notification. While messages for major events can display
on-screen as you work at your computer, events not requiring your immediate
attention are recorded by Windows NT in the Event Viewer log file. You can then
view this information at your convenience.
In addition, the operating system audit trail is logged to Event Viewer. The
following figure shows Event Viewer displaying Oracle database events.
Double-click an entry to find out specific information about an event.
Performance Monitor
Performance Monitor measures computer performance. This tool enables you to
view the 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 in the form of charts, alerts, and reports.
You can use your findings to improve database performance. The following figure
shows Performance Monitor monitoring Oracle database objects listed at the bottom
of the screen:
Counters Objects
Registry
The Oracle database stores its configuration information in a structure known as the
registry. You can view and modify this configuration information through the
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.
The registry editor displays configuration information in a tree-like format
consisting of four keys (or folders). These keys are shown in the tree view in the
left-hand window. In the right-hand window, the parameters and values assigned
to that key are displayed.
The following figure shows some of the Oracle database configuration parameters
in the registry:
User Manager
User Manager enables you to manage Windows NT computer security and create
user accounts.
This chapter describes the concepts of multiple Oracle homes and Optimal Flexible
Architecture (OFA) for Oracle8i Enterprise Edition for Windows NT.
Specific topics discussed:
■ Introduction to Multiple Oracle Homes and OFA
■ Multiple Oracle Homes Overview
■ Which Products Are Multiple Oracle Home-Enabled?
■ Working with Multiple Oracle Homes
■ Optimal Flexible Architecture Overview
■ Differences Between Directory Trees by Release
■ Directory Tree of a Sample OFA-Compliant Database
■ OFA Directory Naming Conventions
■ OFA and Multiple Oracle Home Configurations
■ Increasing Reliability and Performance
■ Comparison Between OFA on Windows NT and UNIX
■ Changing your PATH so that the first entry points to the binary files for the
product release you want to use.
You can change the value of PATH by using one of the following methods:
■ Oracle Home Selector
■ Assigning a new value at the system level. The new value exists until you
change the value of PATH again.
■ Assigning a new value at the at the MS-DOS command prompt. The new value
reverts to its previous value when you quit the session.
Note: The first two methods of changing the value of PATH are
only valid if you are a member of the Administrators group. After
you have changed the value of PATH, you must open a new
MS-DOS window to make it active. The change is not reflected in
already opened MS-DOS windows.
Exiting the Oracle Universal Installer After Entering Name and PATH
If you exit Oracle Universal Installer after you have entered the name and path for
an Oracle home (for example, because there is no more disk space in the path you
specified), you cannot specify a different path until you delete the HOMEID key
and the IDx key corresponding to that Oracle home from the registry. To do this:
1. Read the value of the ORACLE_HOME_NAME parameter for each HOMEID
subkey in the HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE key until
you find the value that matches the name of the Oracle home you need to
delete.
2. Delete the HOMEID subkey you just located.
3. Delete the appropriate IDx subkey in the
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ ALL_HOMES key, where
x has the same value as the ID in HOMEID. For example, if the HOMEID
subkey for the home name you want to delete is HOME1, then the appropriate
IDx subkey is ID1.
For more information on the registry keys and subkeys, see Appendix C, "Oracle 8i
Configuration Parameters and the Registry".
The following figure provides a top-level overview of the old and new database
directory trees:
\...
\ORACLE
\CONTROL01.CTL
\SAMPLE
\CONTROL02.CTL
\...
\SYSTEM01.DBF
\REDO01., ...02, ...03, ...04.LOG
\INDX01.DBF
\ADMIN \.CTL, \.DBF, \.LOG
\DB_NAME1
\ADHOC \ADMIN contains the administration files
\DB_NAME2
\BDUMP including the INIT.ORA file
\...
\PFILE
\...
ORACLE_BASE Directory
ORACLE_BASE is the root of the Oracle directory tree. If you install an
OFA-compliant database using Oracle Universal Installer defaults, ORACLE_BASE
is X:\ORACLE where X is any hard drive (for example, C:\ORACLE).
If you are installing Oracle8i Enterprise Edition on a clean computer, you may want
to change ORACLE_BASE to an appropriate value before running Oracle Universal
Installer. Most users will not need or want to do this.
Before you run Oracle Universal Installer for the first time, change the value of
ORACLE_BASE at the system level. Only change the value of ORACLE_BASE
before you run Oracle Universal Installer for the first time because if there is already
an ORACLE_BASE, and then you change it, there will be a conflict of Oracle base
directories. If you create another ORACLE_BASE when the original ORACLE_BASE
already exists, certain tools and the database will not be able to find previously
created files because they will look for them in the new ORACLE_BASE instead of
the original ORACLE_BASE.
To change the value of ORACLE_BASE at the system level:
On Windows NT:
1. Choose Start > Settings > Control Panel.
The Control Panel window appears.
2. Double-click the System icon.
The System Properties window appears.
3. Click the Environment tab.
The System Variables appear.
4. Type a new value for ORACLE_BASE in the Value text box, then click OK to
quit.
On Windows 95 and Windows 98:
1. Open the AUTOEXEC.BAT file, using a text editor.
2. Edit the value of the ORACLE_BASE statement.
3. Reboot your computer.
ORACLE_HOME Directory
\ORACLE_HOME is located beneath X:\ORACLE_BASE and contains
subdirectories for Oracle software executables and network files.
If you install Oracle8i Enterprise Edition on a clean computer and use the default
settings, the first Oracle home directory that you create is called \ORA81.
ADMIN Directory
Database administration files are stored in subdirectories of ORACLE_BASE
\ADMIN\DB_NAME.
The following table describes the subdirectories for database administration files:
ORADATA Directory
Database files are stored in ORACLE_BASE\ORADATA\DB_NAME.
The following table describes the database files:
DB_NAME Directory
\DB_NAME is the unique name for a particular database and has the same value as
the DB_NAME parameter in the INIT.ORA file. When you name a database,
DB_NAME can be no more than eight characters long and can contain only the
following characters:
■ Alphabetic characters
■ Numbers
■ Underscores (_)
■ Pound sign (#)
■ Dollar sign ($)
C:\ORACLE
C:\ORACLE is ORACLE_BASE for both Oracle homes
\UDUMP
X:\XYZ
X:\XYZ is Oracle home 1 and ORACLE_BASE for Oracle home 1
\... \... \... \.CTL \.DBF \.LOG \.CTL \.DBF \.LOG \.CTL \.DBF \.LOG
Y:\ABC
Y:\ABC is Oracle home 2 and ORACLE_BASE for Oracle home 2
\... \... \... \.CTL \.DBF \.LOG \.CTL \.DBF \.LOG \.CTL \.DBF \.LOG
X:\XYZ X:\PQR
X:\PQR is Oracle home 2
X:\XYZ\ORACLE is
ORACLE_BASE for
both Oracle homes
\NETWORK \BIN
X:\XYZ\ORACLE\ABC is
Oracle home 1
\ORACLE\ABC \ADMIN \ORADATA
\NETWORK \BIN
\DB_NAME1 \DB_NAME2 \DB_NAME3 \DB_NAME1 \DB_NAME2 \DB_NAME3
\... \... \... \...
\ADHOC \CONTROL01.CTL
\CONTROL02.CTL
\ARCH
\SYSTEM01.DBF
\BDUMP
\RBS01.DBF
\CDUMP \INDX01.DBF
\CREATE \TEMP01.DBF
\EXP \USERS01.DBF
\PFILE \OEMREP01.DBF
\UDUMP \REDO01.LOG
\REDO02.LOG
\REDO03.LOG
\REDO04.LOG
Disk Mirroring
Oracle log files and database files can be separated and treated with different levels
of hardware reliability.
Generally, Oracle log files are more highly reliable, because of redundancy. Creating
reliability based on redundancy may require you to duplicate all of your data, using
disk mirrors.
Disk mirroring can be done with the Windows NT Disk Administrator and
commonly with hardware controllers. Two identical drives are usually required to
construct a mirror, the concept being that if one disk fails, the other disk can be used
to recover data that would otherwise be lost. Using one of the disks to recover lost
data may involve "breaking" the mirror. If the mirror breaks, you need to build a
new mirror.
You can achieve a lesser degree of redundancy by configuring the disks, using a
Redundant Array of Inexpensive Disks (RAID) configuration provided by the disk
controller. The RAID level determines the amount of redundancy. Some RAID levels
may use the "hot swapping" feature. Hot swapping means that you can replace a
bad disk with a good one without turning off the computer or losing functionality.
Disk Striping
How you set up disks for use in a database depends on the number of disks and the
type of hard disk controllers available. If the hard disk controllers support both
striping and mirroring, Oracle Corporation recommends you configure the
controllers to support striping.
Some controllers are configured at system startup time by issuing a keyboard
sequence that brings up configuration programs written by the controller
manufacturer. One goal is to stripe as many drives together as possible by
configuring the controllers. Each stripe shows up as one logical device.
Striping provides significant performance advantages. All the space from the
striped drives appears as a single logical drive. Furthermore, the space is used by
interlacing "stripes" of space from all of the disks in the stripe. This means that a
large file uses some space from the first disk, then some from the second disk and so
on to the last disk and then starting back at the first disk again. Each file may be
spread over all of the striped disks. The data in such a file may be accessed
randomly by more than one CPU without contention.
The controllers that support striping usually provide caching as well. This means
that data may be written to the controller and cached and saved for a time in
storage not on the disk. Data that is read can be cached on the controller in a similar
fashion. Read caching is not necessary for Oracle databases since all database reads
are cached already in the System Global Area (SGA). The value of the
DB_BLOCK_BUFFERS parameter in the initialization parameter file (INIT.ORA)
determines the number of buffers that can be used in the SGA. This value also
configures the Oracle database on startup.
Directory Naming
The top-level names of the OFA directory tree differ between Windows NT and
UNIX. However, the main subdirectory and file names are the same on both
operating systems.
ORACLE_BASE Directory
On Windows NT, ORACLE_BASE is associated with an Oracle home directory.
ORACLE_BASE is defined in the registry (for example, in
HKEY_LOCAL_MACHINE \SOFTWARE\ORACLE \HOME0).
On UNIX, ORACLE_BASE is associated with a UNIX user’s environment.
Oracle Corporation recommends that you use one logical drive to store your
database administration files and that you place other files, as needed, on other
logical drives in an ORADATA\DB_NAME directory.
In the following example, there are four logical drives for a database named PROD:
■ C:\ contains an Oracle home and the database administration files
■ F:\ contains the redo log files. (The F:\ drive could also represent two
physical drives that have been striped to increase performance.)
■ G:\ contains one of the control files and all of the tablespace files.(The G:\
drive could also use a RAID Level-5 configuration to increase reliability.)
■ H:\ contains the second control file.
This chapter describes the options available to you when you have existing databases
on your computer and want to install the latest release of Oracle8i Enterprise Edition.
In particular, it describes how to coexist different database releases using multiple
Oracle homes on your computer, and how to migrate an Oracle7 database or
upgrade an earlier Oracle8 database release to the current release of Oracle8i
Enterprise Edition.
Specific topics discussed are:
■ Intended Audience
■ What To Do With Previous Oracle Database Releases
■ Multiple Oracle Homes Overview
■ Migrating, Upgrading, and Downgrading Overview
■ Export/Import Overview
■ Version 8 and Version 7 Client/Server Configurations
■ Installing an Oracle 8.1 Database Where Version 7.x Already Exists
■ Migrating an Oracle7 Database to Oracle8i
■ Upgrading an Oracle8 Database Release 8.0.x to 8.1.5
■ Migration Issues for Net 8 and SQL*Net
■ Moving Database Files to an OFA-Compliant Directory
Intended Audience
Read this chapter if you have existing Oracle7 and/or Oracle8 databases on your
computer and you want to install Oracle8i Enterprise Edition release 8.1.5. If you are
installing Oracle8i Enterprise Edition on a computer that has no other Oracle
database releases, you do not have to read this chapter.
Additional Information: See Oracle8i Enterprise Edition Installation
for Windows NT if you want to install Oracle8i Enterprise Edition on a
computer containing no other databases.
What Is Migrating?
Migrating is the process of transforming an installed version of an Oracle database into
a later version. For example, transforming an Oracle7 database to an Oracle8i
database is migrating the database system.
What Is Upgrading?
Upgrading is the process of transforming an installed version of an Oracle database
release into another release of the same version. For example, transforming an Oracle8
database release 8.0.4 to release 8.1.5 is upgrading the database system.
What Is Downgrading?
Downgrading is the process of transforming an installed version of an Oracle database
from a later release back into an earlier release. For example, transforming an Oracle
database from release 8.1.5 back into release 8.0.3 is downgrading, and transforming
an Oracle database from version 8 back into version 7 is downgrading.
Export/Import Overview
An alternative method of migrating or upgrading is to:
1. Export your data from the source database using the Export Utility (EXP). The
export physically copies the data to the export dump file.
2. Create the Oracle8i database into which you will import the exported data.
3. Import the exported data into the new Oracle8i database using the Import
Utility (IMP).
The Export Utility puts all of the data in one large binary file that can require large
amounts of disk space.
Consider the following database coexistence issues before you decide which of the
above options is most suitable for your requirements:
■ Oracle7 Database Applications
■ Different Client and Database Release Considerations
■ Multi-Versioning
Oracle8i
Database
8.1.5
Oracle8 Client Application release 8.1
The Oracle8 Client release 8.1 and clients must be configured with a service name,
as described in “Using the Local Naming Method” in Chapter 5, "Configuring the
Network" of Net8 Administrator’s Guide.
Oracle8i
Database
Oracle7 Client Application 8.1.5
While it is not necessary to reconfigure release 8.0 and release 7.x clients with a
service name, Oracle Corporation recommends doing so to take advantage of new
functionality. For example, in the TNSNAMES.ORA file:
net_service_name =
(DESCRIPTION=
(ADDRESS =...)
(ADDRESS =...)
)
(CONNECT_DATA=
(SERVICE_NAME=SALES)
)
Oracle7 Oracle8
Database Database
8.0
The release 8.1 clients must be configured with the SID of the database. For
example, the TNSNAMES.ORA would have the following effect:
net_service_name =
(DESCRIPTION=
(ADDRESS =...)
(ADDRESS =...)
)
(CONNECT_DATA=
(SID=SALES)
)
This effect may be accomplished by manually editing the TNSNAMES.ORA file or
using the Net8 Assistant’s compatibility mode. See "Using Release 8.0/7.x Features
and Connecting To a Release 8.0/7.x Service" in Chapter 3, "Upgrading and
Migrating" of Net8 Administrator’s Guide.
Additionally, the LISTENER.ORA on the database server must still be configured
with the description of the SID, as described in "Statically Configuring a Listener" in
Chapter 5, "Configuring the Network" of Net8 Administrator’s Guide.
Consider the following questions for an environment with Oracle8 clients release
8.1 connecting to an Oracle7 database.
■ Do my Oracle8 clients require SQL*Net Client release 2.x to connect to a remote
Oracle7 database?
No. If an Oracle8 client needs to connect to a remote Oracle7 database, only Net8
Client needs to be configured on the Oracle8 client. SQL*Net release 2.x is
upwards compatible with Net8. The only limitation is that the new network
features available with Net8 are unavailable with this connection type.
■ Do my Oracle8 clients require SQL*Net release 2.x to connect to a local Oracle7
database?
Yes. If the Oracle8 client needs to connect to a local Oracle7 database, you need
both SQL*Net Server release 2.x and Net8 Client on the same system.
Multi-Versioning
You can run different versions of Oracle databases on the same computer system at
the same time. However, each version can only access a database that is consistent
with its version. For example, if you have version 7 and version 8 of Oracle installed
on the same computer system, the version 7 server can access version 7 databases,
but not version 8 databases, and the version 8 server can access version 8 databases
but not version 7 databases. The only way for a version 8 database to read version 7
database files is to perform a migration. You should be aware that after migration,
the version 7 database will no longer be able to read the files.
You can install Oracle7 and Oracle8i databases in multiple (separate) Oracle homes
and have both Oracle7 and Oracle8i clients connecting to Oracle7 and Oracle8i
databases. Multiple Oracle homes functionality currently only works with releases 8.0.4
and later releases. If you have, for example, release 7.3.3 products already installed,
you cannot install any other release 7.x products in a separate Oracle home. Also, if
you have release 8.0.3 or earlier 8.0.x products already installed, you cannot install
any other of these products in a separate Oracle home. The following figure gives
an example of this network configuration:
Oracle7 client Oracle8 client Oracle7 client Oracle8 client Oracle8 client
Old style
Oracle7 Oracle7 Oracle8
Oracle 7.2.x and
Database Database Database
Oracle 8.0.x
7.2.2 7.3.3 8.0.5
Oracle home
Oracle7 client Oracle8 client Oracle7 client Oracle8 client Oracle8 client
Oracle7 Oracle8i
Database Database
7.3.3 Migrate Oracle7 database 8.1.5
to an Oracle8i database
in a different Oracle home
Oracle7 Oracle8i
Database Database
Migrate Oracle7 database
7.3.3 8.1.5
to an Oracle8i database
in the same Oracle home
Oracle8 Oracle8i
Database Database
8.0.3 Upgrade Oracle8 database 8.1.5
to current Oracle8i database
release across different Oracle homes
Oracle8 Oracle8i
Database Database
Upgrade Oracle8 database
8.0.3 8.1.5
to current Oracle8i database
release in the same Oracle home
Oracle7 Oracle8
Database Database
7.3.3 8.0.5
Migrate
Oracle7 client
to Oracle8 client
Oracle7 client release 7.x Oracle8i client Oracle7 client Oracle8 client
configured with release 8.1.5
SQL*Net Client release 2.x configured with
Net8 Client
b. Enter the location of the Oracle home directory where you want to install
release 8.1.5. In this example, enter C:\ORACLE\ORA81 in the Path: field.
You must install the release 8.1 software into a directory that is separate
from your release 8.0 Oracle home. Installing the release 8.1 software into
the same Oracle home as the release 8.0 software is not supported in release
8.1.
c. Click Next.
The Available Products dialog box appears.
7. Select Oracle8i Enterprise Edition, then click Next.
The Installation Types dialog box appears.
8. Select Minimal to install a standard set of components for an Oracle database
server, then click Next.
The Available Product Components dialog box appears.
9. Select the Oracle products you want to install.
10. Click Next.
The Migrating an Existing Database dialog box appears indicating that Oracle
Universal Installer has detected an earlier version of the database. You are
asked if you want to migrate your Oracle7 database ORCL database to release
8.1.5 using Oracle Data Migration Assistant.
11. Click None. Then click Next to continue installation of the 8.1.5 database.
If you click ORCL or any other database that resides on your computer, Oracle
Data Migration Assistant is launched at the end of installation and migrates the
Oracle7 database to release 8.1.5.
The Starter Database dialog box appears and prompts you to create a starter
database.
12. Choose No, then click Next.
The Summary window appears.
13. Click Install.
database is an earlier version (for example, version 6), migrate it to at least Oracle7
release 7.1.3.3.6 before migrating it to an Oracle8i database.
The character set value is returned by the database. If the character sets are
identical, then you can proceed to run MIG.
If the character sets are different, before you run MIG, you must set the NLS_
LANG environment variable at the MS-DOS command prompt as follows:
AMERICAN_AMERICA.database character set
where database character set is substituted with the character set of your Oracle7
database. For example, if the character set of your Oracle7 database is JA16EUC,
set the NLS_LANG environment variable as follows:
C:\> SET NLS_LANG=AMERICAN_AMERICA.JA16EUC
Messages output from MIG will now be in English. After MIG finishes, reset the
NLS_LANG environment variable to its original value.
Ensure the database was cleanly shut down before you back up. Ensure you
back up the database files in the following list (and any other database files you
may have created). Also, back up any scripts you may have created.
See "Backing Up and Recovering Database Files" on page 12-1, Oracle8 Concepts,
Oracle8 Backup and Recovery Guide, and Oracle8 Administrator’s Guide for
information on how to back up a database.
MIG runs and displays the operations being performed. MIG can take
considerable time to run. Please wait until it has finished running.
Check the results after running MIG. If there are error messages, see Appendix
A, "Troubleshooting Migration Problems" of Oracle8i Migration for more
information before going to Step 9.
9. Stop the Oracle7 service at the MS-DOS command prompt when MIG has
completed successfully:
C:\> NET STOP OracleServiceSID
10. Delete the Oracle7 services at the MS-DOS command prompt using
ORADIM7x.
Note: You can receive the error "failed to open service", when
attempting to delete services. To avoid this error, reboot your
Windows NT computer.
MIG creates a convert file that contains the information of the version 7 control
file. Later in the migration process, the convert file is used when you execute
the ALTER DATABASE CONVERT command to create a new control file for
version 8.
The default location of the convert file is ORACLE_BASE\ORACLE_
HOME\RDBMS where ORACLE_HOME is the version 8 Oracle home. The
default filename is CONVERT.ORA.
After successfully running MIG, perform a cold backup of the Oracle7 database.
This backup serves the following purposes:
■ If you want to return to the Oracle7 database after executing the ALTER
DATABASE CONVERT command, you can restore the backup and start the
version 7 database.
■ It can be used as the first version 8 backup for a version 8 recovery.
■ If an error occurs at version 8 database convert time (ALTER DATABASE
CONVERT or ALTER DATABASE OPEN RESETLOGS), you can restore this
backup, fix the problem(s), and continue the conversion process. However,
if you restore a backup performed before you ran MIG, you must rerun
MIG.
Additional Information: See Chapter 12, "Backing Up and
Recovering Database Files", Oracle8 Concepts, Oracle8 Backup and
Recovery Guide, and Oracle8 Administrator’s Guide for information on
how to back up a database.
3. Either delete or rename the database’s control files, or use the CONTROL_FILES
parameter in the INITSID.ORA file to specify new control file names. The
ALTER DATABASE CONVERT command automatically creates new control
files in Step 8. If you do not use the CONTROL_FILES parameter, this
command uses the control file names of your pre-migration database and
returns an error if the control files already exist. Therefore, in this case, you must
delete or rename the control file(s). However, if you use the CONTROL_FILES
parameter in the INITSID.ORA file, the ALTER DATABASE CONVERT
command creates the new control file(s) with the names you specify, and you
do not need to remove the old control files. Check the file V7DBFILES.LOG that
you created in "Step 3: Back Up the Oracle7 Database" for the complete list and
location of control files you must delete.
This command uses the MIGSID.ORA file that was created earlier when you
ran MIG. All data files that are online are converted to Oracle8i Enterprise
Edition format, and new control files are built. Control files are considerably
larger in version 8 than in version 7. Control files in the tens of kilobytes size
range in version 7 could be expanded into the range of tens of megabytes
automatically during migration to version 8. This size increase could be
important if a control file is on a raw device or if its available disk space is
restricted.
9. Open the Oracle8i database:
SQL> ALTER DATABASE OPEN RESETLOGS;
All rollback segments that are online when the Oracle8i database is opened are
also opened and converted to the Oracle8i database format.
10. Create a spool file called CATOUT.LOG by entering the following at the
SQL*Plus prompt:
SQL> SPOOL CATOUT.LOG
11. Run the following scripts in sequence:
Oracle Corporation supplies other scripts with Oracle8i Enterprise Edition that
create additional structures you can use in managing your database and
creating database applications. These scripts are also located in ORACLE_
HOME\RDBMS\ADMIN. See the chapter "SQL*Scripts" in Oracle8 Reference for
a complete list and descriptions of available scripts.
12. Turn off the SPOOL command:
SQL> SPOOL OFF
13. Check the spool file CATOUT.LOG and verify that the scripts you ran compiled
every package and procedure successfully. Correct any problems you find in
this file.
14. Shut down the Oracle8i database in NORMAL mode to perform a clean
database shutdown. Do not use SHUTDOWN IMMEDIATE or SHUTDOWN
ABORT. Note that NORMAL is the default parameter.
SQL> SHUTDOWN
Performing a clean database shutdown flushes all caches, clears buffers, and
performs other Relational Database Management System (RDBMS)
housekeeping activities. These measures are an important final step to ensure
the integrity and consistency of the newly migrated release 8.1.5 database.
15. Back up the Oracle8i database. See Appendix 12, "Backing Up and Recovering
Database Files" for a list of tools to back up the database.
The Oracle7 database has now been migrated to the Oracle8i database and is
ready for use.
WARNING: If you retain the old version 7 software, never start the
migrated database with the old version 7 software. Only start the
database with the executables in the new version 8 installation
directory.
Before you use this assistant, ensure the Oracle8 database to be upgraded meets
these requirements:
■ the database you want to upgrade is at least release 8.0.3.0.0
■ the service for the database instance is present in the Services window of the
Control Panel
To upgrade a database using Oracle Data Migration Assistant:
1. Choose Start > Programs > Oracle - HOME_NAME > Migration Utilities >
Oracle Data Migration Assistant.
The Oracle Data Migration Assistant welcome window appears:
Ensure the database is cleanly shutdown before you back up. Ensure you back
up the database files in the following list (and any other database files you may
have created). Also, back up any scripts you may have created.
9. Click No.
The Summary window appears.
10. Click Install.
The Configuration Tools window appears.
11. Click Next.
The End of Installation window appears.
12. After installation is complete, copy the release 8.0.x INITSID.ORA file from the
release 8.0.x ORACLE_HOME\DATABASE directory to the release 8.1.5
ORACLE_BASE\ORACLE_HOME\DATABASE directory.
13. Shut down and restart the computer.
14. Certain release 8.0 initialization parameters are obsolete in release 8.1. Remove
all obsolete parameters from any initialization parameter file that will start a
release 8.1 instance; obsolete parameters may cause errors in release 8.1. Also,
alter any parameter whose syntax has changed in release 8.1. See Appendix B,
"Changes to Initialization Parameters" of Oracle8i Migration for lists of new,
renamed, and obsolete parameters.
15. If you are updating snapshots automatically by using the JOB_QUEUE_
PROCESSES initialization parameter, comment out this parameter in the
INITSID.ORA file. After upgrading your database, you can remove the
comments to use the parameter normally.
1
When you run any of these U*.SQL scripts, the CATALOG.SQL and CATPROC.SQL scripts, which create the system catalog
views and all the necessary packages for using PL/SQL, are also run.
Note:
■ You must use the version of the script supplied with the release
8.1.5 installation.
■ You must run the script in the release 8.1.5 environment.
■ You only need to run one script, even if your upgrade spans
several releases. For example, if your current release is 8.0.3.0.0,
then you only need to run U0800030.SQL.
■ If the old release you had installed prior to upgrading was
higher than release 8.0.5.0, see the READMEMIG.doc file in the
new installation for the correct upgrade script to run.
■ If the upgrade script runs for an inordinately long time, it may
be caused by a setting for LARGE_POOL_SIZE that is too large
for your installation. Use the V$PARAMETER view to check
the setting for LARGE_POOL_SIZE, and if it is too large, set it
to a smaller value in your INIT.ORA file.
8. If you have Advanced Replication installed, run the CATREP.SQL script. If you
have Oracle Parallel Server installed, run the CATPARR.SQL script. Otherwise,
go to Step 9.
Oracle Corporation supplies other scripts with Oracle8i Enterprise Edition that
create additional structures you can use in managing your database and
creating database applications. These scripts are also located in ORACLE_
HOME\RDBMS\ADMIN. See Oracle8 Reference for a complete list and
descriptions of available scripts.
9. Run the UTLRP.SQL script. This is a script that Oracle Corporation recommends
you run to compile all existing PL/SQL modules that were previously in an
INVALID state, such as packages, procedures, types, and so on. Doing this at
this stage is optional; however, it will ensure that the cost of recompilation is
incurred during installation time rather than later on. Enter at the SQL*Plus
prompt:
SQL> @%ORACLE_HOME%\RDBMS\ADMIN\UTLRP.SQL
10. Turn off the SPOOL command.
SQL> SPOOL OFF
Check the spool file UPGRADE.LOG you created in Step 6. and verify that
every package and procedure compiled successfully. Correct any problems you
find in the file. If you are upgrading from release 8.0.2, also check the
UPGRADE2.LOG spool file.
11. Run ALTER SYSTEM DISABLE RESTRICTED SESSION:
SQL> ALTER SYSTEM DISABLE RESTRICTED SESSION
12. Run UTLCONST.SQL to check for bad date constraints. If you already ran
UTLCONST.SQL after you migrated or upgraded to a previous version 8
release, you do not need to run it again. However, running the script many
times will not damage your system; therefore, if you are unsure about whether
it has been run on your system, run it now.
SQL> SPOOL UTLRESULT.LOG
SQL> @%ORACLE_HOME%\RDBMS\ADMIN\UTLCONST.SQL
SQL> SPOOL OFF
A bad date constraint involves invalid date manipulation. An invalid date
manipulation is one that implicitly assumes the century in the date, causing
problems at the year 2000. The UTLCONST.SQL script runs through all of the
check constraints in the database and sets constraints as bad if they include any
invalid date manipulation. UTLCONST.SQL selects all the bad constraints at the
end. After you run the script, the UTLRESULT.LOG file includes all the
constraints that have invalid date constraints. UTLCONST.SQL does not correct
bad date constraints, but it does disable them. Either drop the bad constraints or
recreate them after you make the necessary changes.
This chapter describes some of the configuration tasks you must perform before
using products like interMedia, Net8, and Oracle options.Where appropriate, the
chapter provides references to other guides for those configuration tasks.
The chapter focuses on the post-installation configuration of a variety of Oracle
products.
■ What Products Must You Configure?
Oracle interMedia
Oracle enables file management in a variety of media, from text, to audio, to video.
Files in each medium are managed through a specific "option" such as Oracle
interMedia. This section describes interMedia configuration and describes each
medium management component.
Audio
interMedia Audio manages audio data in multiple file formats in an Oracle
database.
Types of audio data supported include conversations, songs, and other sounds in
popular audio file formats. This makes it possible to integrate audio data with other
application-specific object-relational data.
Video
interMedia Video manages video data in multiple video file formats. This makes it
possible to integrate video data with other application-specific object-relational
data.
Image
interMedia Image provides image storage, retrieval, and format conversion
capabilities through an object data type (ODT). It also supports image storage, using
Binary Large Objects (BLOBs) and references to image data residing in external files
(BFILEs).
The Image component of interMedia also comes with a sample demonstration that
shows how an image is extracted from an Oracle database.
Locator
interMedia Locator enables Oracle8i to support online internet-based geocoding
facilities for locator applications and proximity queries.
If you... Then...
Installed the Oracle interMedia No manual configuration is required. All tasks described page 6-5 are
through the Oracle8i Enterprise automatically performed.
Edition Typical installation type path,
Installed both Oracle interMedia and Oracle Database Configuration Assistant starts at the end of installation.
Oracle Server together through the If you select either of the following options:
Oracle8i Enterprise Edition Custom
■ Custom
installation type path,
■ Typical, and then select the Create new database files suboption
Oracle Database Configuration Assistant asks if you want interMedia to
be automatically configured.
If you... Then...
Installed Oracle interMedia during a You must manually configure Oracle interMedia by either:
separate installation from Oracle8i
■ Performing the tasks page 6-5.
Enterprise Edition
■ Starting Oracle Database Configuration Assistant and selecting
Modify a database. Then following the on-screen instructions.
Manually copy your Oracle7 You must modify the TNSNAMES.ORA and LISTENER.ORA network
LISTENER.ORA and TNSNAMES.ORA configuration files on your server to enable external procedure calls to
files into your Oracle8i network work and interMedia to function properly. Follow the tasks in
directory "Configuring Net8 for External Procedures" in Chapter 6 of Oracle Net8
Administrator’s Guide.
Want multi-threaded external callout Perform the tasks in "Enabling Multi-Threaded Callout Support" page
functionality 13-10.
Want to use the demos Perform the tasks described for the configuration of interMedia sample
demos below.
Want to build the interMedia Image Install a C compiler.
sample demonstration
Want to use Oracle Visual Install Oracle interMedia first. If you selected both options for
Information Retrieval with Oracle installation at the same time, Oracle interMedia was installed first.
interMedia
If you... Then...
Installed Oracle interMedia Text from See description below this table.
the Oracle8i Enterprise Edition CD-ROM
and you do not have a previous release
of interMedia Text installed (formerly
called ConText)
Installed Oracle interMedia Text from See Oracle8i interMedia Text Migration.
the Oracle8i Enterprise Edition CD-ROM
and you do have a previous release of
interMedia Text installed (formerly
called ConText)
Migrated your database, you may need See the guides Oracle8i interMedia Text Migration and Oracle8i
to configure Net8 for external interMedia Text Reference.
procedures. Otherwise Oracle
interMedia Text may not work. In any
case other than migration, Net8 should
be configured correctly by default to
work with Oracle interMedia Text.
If you are indexing formatted You must set your environment to use the INSO filter before you can
documents such as Microsoft Word... index your documentation set. For more information on setting
up your environment for INSO filtering, see Appendix-C of
the Oracle8i interMedia Text Reference.
If one of the following is true, the Oracle database is already configured for use with
Oracle interMedia Text:
■ The database is a starter database that you created by installing Oracle8i
Enterprise Edition with the Typical installation type.
■ The database is a starter database that you created by installing Oracle8i
Enterprise Edition with the Minimal installation type and selecting Yes in the
Select Starter Database dialog box.
■ The database is a starter database that you created by performing the following
sequence of steps:
1. Install Oracle8i Enterprise Edition with the Custom installation type.
2. In the Available Product Components dialog box, select Oracle Server.
To configure... Do this...
At the time you create Select interMedia Text in the Database Cartridges and Options
the database page.
At a later time 1. Select Modify a database in the Welcome page.
2. Select the database that you want to modify in the Modify
Instance page.
3. Select interMedia Text in the Modify Database Cartridges and
Options page.
Configuring Manually
Manually configuring an Oracle database for use with Oracle interMedia Text
consists of creating a tablespace for the interMedia Text data dictionary tables and
then creating the CTXSYS user name and the interMedia Text data dictionary tables
themselves.
To create a tablespace for the interMedia Text data dictionary tables:
1. Start SQL*Plus:
C:\> SQLPLUS
2. Connect as SYS:
Enter user-name: SYS/PASSWORD
3. Create a tablespace for the interMedia Text data dictionary tables:
SQL> CREATE TABLESPACE TABLESPACE_NAME DATAFILE ’ORACLE_BASE\ORADATA\DB_
NAME\DR01.DBF’ SIZE 80M;
To create the CTXSYS user name and the interMedia Text data dictionary tables:
1. Connect as INTERNAL:
SQL> CONNECT INTERNAL/PASSWORD
2. Run the DR0CSYS.SQL script to create the CTXSYS user name:
SQL> @ORACLE_BASE\ORACLE_HOME\CTX\ADMIN\DR0CSYS.SQL PASSWORD DEFAULT_
TABLESPACE_NAME TEMPORARY_TABLESPACE_NAME;
where:
■ PASSWORD is the password that you want to use for the CTXSYS user
name.
Oracle Options
Oracle Spatial
Oracle Spatial makes the storage, retrieval, and manipulation of spatial data easier
and more intuitive to users.
One example of spatial data is a road map. A road map is a two-dimensional object
that contains points, lines, and polygons representing cities, roads, and political
boundaries such as states. A road map represents geographic information. The
locations of cities, roads, and political boundaries are projected onto a
two-dimensional display or piece of paper, preserving the relative positions and
relative distances of the objects.
If you... Then...
Installed Oracle Spatial through the No manual configuration is required. All Oracle Spatial configuration
Oracle8i Enterprise Edition Typical tasks described under "Configuring Oracle Spatial:" are automatically
installation type path performed.
Installed both Oracle Spatial and Oracle Database Configuration Assistant starts at the end of installation.
Oracle Server together through the If you select either of the following options:
Oracle8i Enterprise Edition Custom
■ Custom
installation type path
■ Typical, and then select the Create new database files suboption
Oracle Database Configuration Assistant prompts you about whether or
not you want Oracle Spatial to be automatically configured.
Installed Oracle Spatialduring a You must manually configure Oracle Spatialby either:
separate installation from Oracle8i
■ Performing the Oracle Spatial configuration tasks described under
Enterprise Edition
"Configuring Oracle Spatial:"
■ Starting Oracle Database Configuration Assistant and selecting
Modify a database. Then following the onscreen instructions
SQL> @ORACLE_BASE\ORACLE_HOME\MD\ADMIN\MDINST.SQL
7. Exit SQL*Plus:
SQL> EXIT
If you... Then...
Installed Oracle Time Series through No manual configuration is required. All configuration tasks described
the Oracle8i Enterprise Edition page 6-13 are automatically performed.
Typical installation type path
Installed both Oracle Time Series and Oracle Database Configuration Assistant starts at the end of installation.
Oracle Server together through the If you select either of the following options:
Oracle8i Enterprise Edition Custom
■ Custom
installation type path
■ Typical, and then select the Create new database files suboption
Oracle Database Configuration Assistant prompts you about whether or
not you want Oracle Time Seriesto be automatically configured.
Installed Oracle Time Series during a You must manually configure Oracle Time Series by either:
separate installation from Oracle8i
■ Performing the tasks on page 6-13.
Enterprise Edition
■ Starting Oracle Database Configuration Assistant and selecting
Modify a database. Then following the onscreen instructions.
Want to use the demos Perform the tasks described page 6-14.
Manually copy your Oracle7 You must modify the TNSNAMES.ORA and LISTENER.ORA network
LISTENER.ORA and configuration files on your server to enable external procedure calls to
TNSNAMES.ORA files into your work and Oracle Time Series to function properly. Follow the tasks in
Oracle8i network directory "Configuring Net8 for External Procedures" in Chapter 6 of Oracle Net8
Administrator’s Guide.
Want multi-threaded external callout Perform the tasks in "Enabling Multi-Threaded Callout Support" page
functionality 13-10.
If you... Then...
Installed Oracle Visual Information No manual configuration is required. All configuration tasks described
Retrieval through the Oracle8i under "To configure Oracle Visual Information Retrieval:" are
Enterprise Edition Typical installation automatically performed.
type path
Installed both Oracle Visual Oracle Database Configuration Assistant starts at the end of installation.
Information Retrieval and Oracle If you select either of the following options:
Server together through the Oracle8i
■ Custom
Enterprise Edition Custom
installation type path ■ Typical, and then select the Create new database files suboption
Oracle Database Configuration Assistant asks if you want Oracle Visual
Information Retrieval to be automatically configured.
If you... Then...
Installed Oracle Visual Information You must manually configure Oracle Visual Information Retrieval by
Retrieval during a separate either:
installation from Oracle8i Enterprise
■ Performing the configuration tasks described page 6-16.
Edition
■ Starting Oracle Database Configuration Assistant and selecting
"Modify a database". Then, follow the on-screen instructions.
Want to use the demonstration Perform the configuration tasks described under "To configure the
Oracle Visual Information Retrieval demonstration:".
Want to build an Oracle Visual Install a C compiler.
Information Retrieval sample
demonstration.
Manually copy your Oracle7 You must modify the TNSNAMES.ORA and LISTENER.ORA network
LISTENER.ORA and configuration files on your server to enable external procedure calls to
TNSNAMES.ORA files into your work and Oracle Visual Information Retrieval to function properly.
Oracle8i network directory Follow the tasks in "Configuring Net8 for External Procedures" in
Chapter 6 of Oracle Net8 Administrator’s Guide.
Want multi-threaded external callout Perform the tasks in "Enabling Multi-Threaded Callout Support" page
functionality 13-10.
7. Exit SVRMGRL:
SVRMGRL> EXIT
To configure the Oracle Visual Information Retrieval demonstration:
1. Go to the ORACLE_BASE\ORACLE_HOME\ORD\VIR\ADMIN directory.
2. Read the README file in this directory for instructions on configuring the
demonstration.
3. Make the Oracle Visual Information Retrieval demonstration for a Microsoft C
compiler by entering:
C:\> MAKE
Mode Description
Dedicated server mode The Oracle database allocates a resource dedicated to serving only that one client
connection.
This mode is best used in the following environments:
■ Decision support system (DSS) environment.
■ A small number of users will connect to your Oracle database.
Mode Description
Multi-threaded server Enables many client user processes to share a small number of server processes.
mode (also called
Many client users can connect to a dispatcher process. The dispatcher process then
shared server mode)
routes client requests to the next available shared server process. No dedicated server
process exists for each client user process for the duration of the connection. Instead,
inactive server processes are recycled and used as needed. This reduces system
overhead and enables you to increase the number of supported users.
This mode is best used in the following environments:
■ Online transaction processing (OLTP) environment
■ A large number of users will simultaneously connect to your database
■ You want to use Net8 features such as connection pooling, connection
multiplexing, and load balancing
■ Managing and using system resources to a high degree is important
■ Predictable and fast database connection times are very important. (This may be a
very important criterion for Web applications.)
Note: This mode is required for Oracle Java option to function properly.
The current configuration of your Oracle database depends on how the database
was installed.
A dialog box prompts you to select the initialization parameter file to use.
6. Select the appropriate file and click OK.
Your initialization parameter file is modified.
7. Shut down and restart your Oracle database for the changes to take effect.
Advanced Replication
This section describes how to manually configure Advanced Replication in your
Oracle database.
Typically, Advanced Replication is automatically configured during installation.
The following figure describes the situations under which Advanced Replication is
configured or not configured.
If Advanced Replication is automatically configured, do not follow the instructions
in this section. Follow the instructions only if you want to add Advanced
Replication to an Oracle database that was not previously configured with this
feature.
If you select the Oracle8i Enterprise Edition installation option and select...
Advanced replication is Advanced replication is The Available Product Components dialog box
automatically configured. automatically configured if appears.
you installed the starter 1. Select Oracle Server and click Install.
database when prompted by
the Select Starter Database 2. Click Yes when prompted to run Oracle Database
dialog box. Configuration Assistant.
Oracle Database Configuration Assistant starts at
the end of installation and prompts you to select
either of two database installation types:
■ Typical
■ Custom
If you select Typical, the installer prompts you If you select Custom, one of the Oracle Database
about how to create your database: Configuration Assistant pages prompts you to
■ Copy existing database files from the CD configure Advanced Replication.
■ Create new database files If you select the Advanced Replication check box,
advanced replication is automatically configured.
If you do not select the Advanced Replication
check box, advanced replication is not configured.
If you select Copy existing database files from If you select Create new database files, one of the
the CD, advanced replication is automatically Oracle Database Configuration Assistant pages
configured. prompts you to configure Advanced Replication.
If you select the Advanced Replication check box,
advanced replication is automatically configured.
If you do not select the Advanced Replication check
box, advanced replication is not configured.
Tablespace Requirement
SYSTEM At least 20 MB of free space is required for replication
packages. Replication triggers and procedures are stored here.
ROLLBACK SEGMENTS ■ Rollback Initial Extent = 50 KB
■ Rollback Next Extent = 50 KB
ROLLBACK At least 5 MB of free space.
TEMPORARY At least 10 MB of free space.
USER No specific requirement.
Master Site
Add these initialization parameters to the master site.
Snapshot Sites
Add these initialization parameters for snapshot sites.
Note: Run the following statement on the master site when setting
up updatable snapshot sites:
SVRMGR> GRANT EXECUTE ON DBMSOBJGWRAPPER TO PUBLIC;
Audio
interMedia Audio manages audio data in multiple file formats in an Oracle
database.
Types of audio data supported include conversations, songs, and other sounds in
popular audio file formats. This makes it possible to integrate audio data with other
application-specific object-relational data.
Video
interMedia Video manages video data in multiple video file formats. This makes it
possible to integrate video data with other application-specific object-relational
data.
Image
interMedia Image provides image storage, retrieval, and format conversion
capabilities through an object data type (ODT). It also supports image storage, using
Binary Large Objects (BLOBs) and references to image data residing in external files
(BFILEs).
The Image component of interMedia also comes with a sample demonstration that
shows how an image is extracted from an Oracle database.
Locator
interMedia Locator enables Oracle8i to support online internet-based geocoding
facilities for locator applications and proximity queries.
If you... Then...
Installed the Oracle interMedia No manual configuration is required. All tasks described page 6-5 are
through the Oracle8i Enterprise automatically performed.
Edition Typical installation type path,
Installed both Oracle interMedia and Oracle Database Configuration Assistant starts at the end of installation.
Oracle Server together through the If you select either of the following options:
Oracle8i Enterprise Edition Custom
■ Custom
installation type path,
■ Typical, and then select the Create new database files suboption
Oracle Database Configuration Assistant asks if you want interMedia to
be automatically configured.
Installed Oracle interMedia during a You must manually configure Oracle interMedia by either:
separate installation from Oracle8i
■ Performing the tasks under "To configure Oracle interMediaAudio,
Enterprise Edition
Video, Image, and Locator:Start SVRMGR:".
■ Starting Oracle Database Configuration Assistant and selecting
"Modify a Database". Then following the on-screen instructions.
Manually copy your Oracle7 You must modify the TNSNAMES.ORA and LISTENER.ORA network
LISTENER.ORA and TNSNAMES.ORA configuration files on your server to enable external procedure calls to
files into your Oracle8i network work and interMedia to function properly. Follow the tasks in
directory "Configuring Net8 for External Procedures" in Chapter 6 of Oracle Net8
Administrator’s Guide.
Want multi-threaded external callout Perform the tasks in "Enabling Multi-Threaded Callout Support" page
functionality 13-10.
Want to use the demos Perform the tasks described for the configuration of interMedia sample
demos below.
Want to build the interMedia Image Install a C compiler.
sample demonstration
Want to use Oracle Visual Install Oracle interMedia first. If you selected both options for
Information Retrieval with Oracle installation at the same time, Oracle interMedia was installed first.
interMedia
Oracle interMedia Text manages textual data in concert with traditional data types
in an Oracle database. When text is inserted, updated, or deleted, interMedia Text
automatically manages the change.
If you... Then...
Installed Oracle interMedia Text from See description below this table.
the Oracle8i Enterprise Edition CD-ROM
and you do not have a previous release
of interMedia Text installed (formerly
called ConText)
Installed Oracle interMedia Text from See the guide Oracle8i interMedia Text Migration
the Oracle8i Enterprise Edition CD-ROM
and you do have a previous release of
interMedia Text installed (formerly
called ConText)
Migrated your database, you may need See the guides Oracle8i interMedia Text Migration and Oracle8i
to configure Net8 for external interMedia Text Reference.
procedures. Otherwise Oracle
interMedia Text may not work. In any
case other than migration, Net8 should
be configured correctly by default to
work with Oracle interMedia Text.
If you are indexing formatted You must set your environment to use the INSO filter before you can
documents such as Microsoft Word... index your documentation set. For more information on setting
up your environment for INSO filtering, see Appendix-C of
the Oracle8i interMedia Text Reference.
If one of the following is true, the Oracle database is already configured for use with
Oracle interMedia Text:
■ The database is a starter database that you created by installing Oracle8i
Enterprise Edition with the Typical installation type.
■ The database is a starter database that you created by installing Oracle8i
Enterprise Edition with the Minimal installation type and selecting Yes in the
Select Starter Database dialog box.
■ The database is a starter database that you created by performing the following
sequence of steps:
1. Install Oracle8i Enterprise Edition with the Custom installation type.
2. In the Available Product Components dialog box, select Oracle Server.
3. When prompted to run Oracle Database Configuration Assistant, click Yes.
4. Select the Typical database creation type.
5. Select "Copy existing database files from the CD".
To configure... Do this...
At the time you create Select interMedia Text in the Database Cartridges and Options
the database page.
At a later time 1. Select Modify a database in the Welcome page.
2. Select the database that you want to modify in the Modify
Instance page.
3. Select interMedia Text in the Modify Database Cartridges and
Options page.
Configuring Manually
Manually configuring an Oracle database for use with Oracle interMedia Text
consists of creating a tablespace for the interMedia Text data dictionary tables and
then creating the CTXSYS user name and the interMedia Text data dictionary tables
themselves.
To create a tablespace for the interMedia Text data dictionary tables:
1. Start SQL*Plus:
C:\> SQLPLUS
2. Connect as SYS:
Enter user-name: SYS/PASSWORD
3. Create a tablespace for the interMedia Text data dictionary tables:
SQL> CREATE TABLESPACE TABLESPACE_NAME DATAFILE ’ORACLE_BASE\ORADATA\DB_
NAME\DR01.DBF’ SIZE 80M;
To create the CTXSYS user name and the interMedia Text data dictionary tables:
1. Connect as INTERNAL:
SQL> CONNECT INTERNAL/PASSWORD
2. Run the DR0CSYS.SQL script to create the CTXSYS user name:
SQL> @ORACLE_BASE\ORACLE_HOME\CTX\ADMIN\DR0CSYS.SQL PASSWORD DEFAULT_
TABLESPACE_NAME TEMPORARY_TABLESPACE_NAME;
where:
■ PASSWORD is the password that you want to use for the CTXSYS user
name.
Oracle Options
Oracle Spatial
Oracle Spatial makes the storage, retrieval, and manipulation of spatial data easier
and more intuitive to users.
One example of spatial data is a road map. A road map is a two-dimensional object
that contains points, lines, and polygons representing cities, roads, and political
boundaries such as states. A road map represents geographic information. The
locations of cities, roads, and political boundaries are projected onto a
two-dimensional display or piece of paper, preserving the relative positions and
relative distances of the objects.
If you... Then...
Installed Oracle Spatial through the No manual configuration is required. All Oracle Spatial configuration
Oracle8i Enterprise Edition Typical tasks described page 6-11 are automatically performed.
installation type path
Installed both Oracle Spatial and Oracle Database Configuration Assistant starts at the end of installation.
Oracle Server together through the If you select either of the following options:
Oracle8i Enterprise Edition Custom
■ Custom
installation type path
■ Typical, and then select the Create new database files suboption
Oracle Database Configuration Assistant prompts you about whether or
not you want Oracle Spatial to be automatically configured.
Installed Oracle Spatialduring a You must manually configure Oracle Spatialby either:
separate installation from Oracle8i
■ Performing the Oracle Spatial configuration tasks described under
Enterprise Edition
"Configuring Oracle Spatial:"
■ Starting Oracle Database Configuration Assistant and selecting
Modify a database. Then following the onscreen instructions
SQL> @ORACLE_BASE\ORACLE_HOME\MD\ADMIN\MDINST.SQL
7. Exit SQL*Plus:
SQL> EXIT
If you... Then...
Installed Oracle Time Series through No manual configuration is required. All configuration tasks described
the Oracle8i Enterprise Edition under "To configure Oracle Time Series:" are automatically performed.
Typical installation type path
Installed both Oracle Time Series and Oracle Database Configuration Assistant starts at the end of installation.
Oracle Server together through the If you select either of the following options:
Oracle8i Enterprise Edition Custom
■ Custom
installation type path
■ Typical, and then select the Create new database files suboption
Oracle Database Configuration Assistant prompts you about whether or
not you want Oracle Time Seriesto be automatically configured.
Installed Oracle Time Series during a You must manually configure Oracle Time Series by either:
separate installation from Oracle8i
■ Performing the tasks under "To configure Oracle Time Series:".
Enterprise Edition
■ Starting Oracle Database Configuration Assistant and selecting
Modify a database. Then following the onscreen instructions.
Want to use the demonstration Perform the tasks described in the table illustrating the demonstration.
Manually copy your Oracle7 You must modify the TNSNAMES.ORA and LISTENER.ORA network
LISTENER.ORA and configuration files on your server to enable external procedure calls to
TNSNAMES.ORA files into your work and Oracle Time Series to function properly. Follow the tasks in
Oracle8i network directory "Configuring Net8 for External Procedures" in Chapter 6 of Oracle Net8
Administrator’s Guide.
Want multi-threaded external callout Perform the tasks in "Enabling Multi-Threaded Callout Support" page
functionality 13-10.
If you... Then...
Installed Oracle Visual Information No manual configuration is required. All configuration tasks described
Retrieval through the Oracle8i under "To configure Oracle Visual Information Retrieval:" are
Enterprise Edition Typical installation automatically performed.
type path
Installed both Oracle Visual Oracle Database Configuration Assistant starts at the end of installation.
Information Retrieval and Oracle If you select either of the following options:
Server together through the Oracle8i
■ Custom
Enterprise Edition Custom
installation type path ■ Typical, and then select the Create new database files suboption
Oracle Database Configuration Assistant asks if you want Oracle Visual
Information Retrieval to be automatically configured.
If you... Then...
Installed Oracle Visual Information You must manually configure Oracle Visual Information Retrieval by
Retrieval during a separate either:
installation from Oracle8i Enterprise
■ Performing the configuration tasks described page 6-16.
Edition
■ Starting Oracle Database Configuration Assistant and selecting
"Modify a database". Then, follow the on-screen instructions.
Want to use the demonstrations Perform the configuration tasks described under "To configure the
Oracle Visual Information Retrieval demonstration:".
Want to build an Oracle Visual Install a C compiler.
Information Retrieval sample
demonstration.
Manually copy your Oracle7 You must modify the TNSNAMES.ORA and LISTENER.ORA network
LISTENER.ORA and configuration files on your server to enable external procedure calls to
TNSNAMES.ORA files into your work and Oracle Visual Information Retrieval to function properly.
Oracle8i network directory Follow the tasks in "Configuring Net8 for External Procedures" in
Chapter 6 of Oracle Net8 Administrator’s Guide.
Want multi-threaded external callout Perform the tasks in "Enabling Multi-Threaded Callout Support" page
functionality 13-10.
7. Exit SVRMGRL:
SVRMGRL> EXIT
To configure the Oracle Visual Information Retrieval demonstration:
1. Go to the ORACLE_BASE\ORACLE_HOME\ORD\VIR\ADMIN directory.
2. Read the README file in this directory for instructions on configuring the
demonstration.
3. Make the Oracle Visual Information Retrieval demonstration for a Microsoft C
compiler by entering:
C:\> MAKE
Mode Description
Dedicated server mode The Oracle database allocates a resource dedicated to serving only that one client
connection.
This mode is best used in the following environments:
■ Decision support system (DSS) environment.
■ A small number of users will connect to your Oracle database.
Mode Description
Multi-threaded server Enables many client user processes to share a small number of server processes.
mode (also called
Many client users can connect to a dispatcher process. The dispatcher process then
shared server mode)
routes client requests to the next available shared server process. No dedicated server
process exists for each client user process for the duration of the connection. Instead,
inactive server processes are recycled and used as needed. This reduces system
overhead and enables you to increase the number of supported users.
This mode is best used in the following environments:
■ Online transaction processing (OLTP) environment
■ A large number of users will simultaneously connect to your database
■ You want to use Net8 features such as connection pooling, connection
multiplexing, and load balancing
■ Managing and using system resources to a high degree is important
■ Predictable and fast database connection times are very important. (This may be a
very important criterion for Web applications.)
Note: This mode is required for Oracle Java option to function properly.
The current configuration of your Oracle database depends on how the database
was installed.
A dialog box prompts you to select the initialization parameter file to use.
6. Select the appropriate file and click OK.
Your initialization parameter file is modified.
7. Shut down and restart your Oracle database for the changes to take effect.
Advanced Replication
This section describes how to manually configure Advanced Replication in your
Oracle database.
Typically, Advanced Replication is automatically configured during installation.
The following figure describes the situations under which Advanced Replication is
configured or not configured.
If Advanced Replication is automatically configured, do not follow the instructions
in this section. Follow the instructions only if you want to add Advanced
Replication to an Oracle database that was not previously configured with this
feature.
If you select the Oracle8i Enterprise Edition installation option and select...
Advanced replication is Advanced replication is The Available Product Components dialog box
automatically configured. automatically configured if appears.
you installed the starter 1. Select Oracle Server and click Install.
database when prompted by
the Select Starter Database 2. Click Yes when prompted to run Oracle Database
dialog box. Configuration Assistant.
Oracle Database Configuration Assistant starts at
the end of installation and prompts you to select
either of two database installation types:
■ Typical
■ Custom
If you select Typical, the installer prompts you If you select Custom, one of the Oracle Database
about how to create your database: Configuration Assistant pages prompts you to
■ Copy existing database files from the CD configure Advanced Replication.
■ Create new database files If you select the Advanced Replication check box,
advanced replication is automatically configured.
If you do not select the Advanced Replication
check box, advanced replication is not configured.
If you select Copy existing database files from If you select Create new database files, one of the
the CD, advanced replication is automatically Oracle Database Configuration Assistant pages
configured. prompts you to configure Advanced Replication.
If you select the Advanced Replication check box,
advanced replication is automatically configured.
If you do not select the Advanced Replication check
box, advanced replication is not configured.
Tablespace Requirement
SYSTEM At least 20 MB of free space is required for replication
packages. Replication triggers and procedures are stored here.
ROLLBACK SEGMENTS ■ Rollback Initial Extent = 50 KB
■ Rollback Next Extent = 50 KB
ROLLBACK At least 5 MB of free space.
TEMPORARY At least 10 MB of free space.
USER No specific requirement.
Master Site
Add these initialization parameters to the master site.
Snapshot Sites
Add these initialization parameters for snapshot sites.
Note: Run the following statement on the master site when setting
up updatable snapshot sites:
SVRMGR> GRANT EXECUTE ON DBMSOBJGWRAPPER TO PUBLIC;
This chapter describes how to install either a starter or custom Oracle database,
including the contents of the starter database.
Specific topics discussed:
■ Starter and Custom Database Overview
■ Starter Database Contents
Type Description
Starter Preconfigured, ready-to-use database that requires minimal user input to
create
Custom Database that you create to match your environment, with guidance from
Oracle Database Configuration Assistant
When you run Oracle Universal Installer and select Oracle8i Enterprise Edition as
the installation option, the Installation Types dialog box presents you with the
following three selections.
The types of databases available with each selection are shown below:
If You Select...
The starter database is The Select Starter Database The Available Product Components dialog box
automatically installed. dialog box appears during appears.
installation and prompts you
to install the starter database. 1. Select Oracle Server and click Install.
If you select Typical, the installer prompts you If you select Custom, Oracle Database
about how to create your database: Configuration Assistant guides you through the
creation of a database fully customized to match
■ Copy existing database files from the CD.
your environment.
■ Create new database
If you select "Copy existing database files from If you select Create new database files, the
the CD", the starter database is automatically installer prompts you for answers to several
installed. database environment questions before a
partially customized database is created.
This table describes some of the starter and custom database features available with
each Oracle Universal Installer and Oracle Database Configuration Assistant
installation type:
Options4 The Typical type installs and The Partitioning and Objects The Partitioning and Objects
automatically configures options are automatically options are automatically
these Oracle options: configured when installed configured when installed
with Oracle Universal with Oracle Universal
■ Partitioning
Installer. Installer.
■ Objects
Depending on how Oracle Depending on how Oracle
■ Parallel Server Parallel Server option was Parallel Server option was
installed, it may also be installed, it may also be
No options are installed
automatically configured. automatically configured.
through the Minimal type.
See Oracle Parallel Server See Oracle Parallel Server
Getting Started for Windows Getting Started for Windows
NT for information. NT for information.
Advanced Automatically configured Automatically configured Your choice.
replication through the Typical type. with the Copy existing
database files from CD
Automatically configured
suboption.
through the Minimal type if
you select the starter The Create new database
database for installation files suboption offers you
when prompted. the choice.
4
Oracle Advanced Networking option is also available for installation. This option can be installed through the Oracle8i
Enterprise Edition and Oracle8i Client Custom installation types of Oracle Universal Installer.
5
See "Automatically Enabling Operating System Authentication During Installation" on page 10-3 for more information.
6
See "Using Oracle Database Configuration Assistant" on page 8-4 for definitions of these database environments.
Note: Change the password for each user name immediately after
installation:
C:\> SQLPLUS
Enter user-name: INTERNAL/PASSWORD
SQL> ALTER USER USERNAME IDENTIFIED BY PASSWORD;
See Chapter 9, "Administering a Database" for instructions on how
to change the password for INTERNAL.
Tablespaces
An Oracle database is divided into smaller logical areas of space known as
tablespaces. Each tablespace corresponds to one or more physical data files.
The tablespaces in the Oracle database contain the following types of data:
Tablespace Contains...
Data Files
Data files contain the contents of logical database structures such as tables and
indexes. One or more data files form a logical unit of storage called a tablespace. A
data file can be associated with only one tablespace, and only one database.
The starter database contains the following data files located in the ORACLE_
BASE\ORADATA\DB_NAME directory:
Control File
The starter database contains two control files located in the ORACLE_BASE\
ORADATA\DB_NAME directory:
Rollback Segments
Rollback segments record the old values of data changed by each transaction
(whether or not committed). Every database contains one or more rollback
segments, which are portions of the database that record the actions of transactions
in the event that a transaction is rolled back. Rollback segments are used to provide
read consistency, to roll back transactions, and to recover the database.
The starter database contains the following rollback segments:
Data Dictionary
The data dictionary is a protected collection of tables and views containing
reference information about the database, its structures, and its users. The data
stored in the dictionary includes the following:
■ Names of the Oracle database users
■ Privileges and roles granted to each user
■ Names and definitions of schema objects (including tables, views, snapshots,
indexes, clusters, synonyms, sequences, procedures, functions, and packages)
■ Integrity constraints
■ Space allocation for database objects
■ Auditing information, such as who accessed or updated various objects
\\server-name\shared-resource-pathname
For example, to access the file SYSTEM01.DBF in the directory
C:\ORACLE\ORA81\ORADATA\ORCL on the shared server ARGON, you
reference the file as:
\\ARGON\ORACLE\ORA81\ORADATA\ORCL\SYSTEM01.DBF
Note that the location of archive log files cannot be specified using UNC. If you set
the LOG_ARCHIVE_DEST initialization parameter to a UNC specification, the
database does not start and you receive the following errors:
ORA-00256: error occurred in translating archive text string ’\meldell\rmdrive’
ORA-09291: sksachk: invalid device specified for archive destination
OSD-04018: Unable to access the specified directory or device
O/S-Error: (OS 2) The system cannot find the file specified
Ensure that you set the LOG_ARCHIVE_DEST initialization parameter to a mapped
drive.
Creating a Database
During installation of Oracle8i Enterprise Edition, you can select any of the
following options to install Oracle Database Configuration Assistant.
There are slight differences between each option:
■ Typical
Oracle Database Configuration Assistant is installed as part of your Oracle8i
Enterprise Edition software package. During this installation, Oracle Database
Configuration Assistant is automatically started without user intervention to
create a starter database. After installation is finished, you can use the assistant
to create additional databases as described here.
■ Minimal
Oracle Database Configuration Assistant is installed as part of your Oracle8i
Enterprise Edition software package. During this installation, you are prompted
to install a starter database. If you select Yes, Oracle Database Configuration
Assistant is automatically started without user intervention to create a starter
database. After installation is finished, you can use the assistant to create
additional databases as described in here.
■ Custom
Oracle Database Configuration Assistant is installed and immediately launched
at the end of the installation process if you select Yes when prompted. You can
create a database at this time, or you can exit the assistant and create a database
at a later date.
To create a database, using Oracle Database Configuration Assistant:
1. Choose Start > Programs > Oracle - HOME_NAME > Oracle Enterprise
Management > Database Administration Applications > Oracle Database
Configuration Assistant.
The Oracle Database Configuration Assistant welcome page appears.
2. Select Create a database, then click Next.
The following page appears:
Option Description
Typical Consists of two suboptions:
■ Copy existing database files from the CD
Automatically installs a standard database with default
INIT.ORA file initialization parameter settings
■ Create new database files
Asks you several database environment questions
before dynamically creating a database
Custom Enables you to customize the creation of your database.
This option is only for Oracle database administrators
(DBAs) experienced with advanced database creation
procedures, such as customizing:
■ Data, control, and redo log file settings
■ Tablespace sizes
■ Extent sizes
■ Database memory parameters
■ Archiving formats and destinations
■ Trace file destinations
■ Character set values
Both the Typical option (through its Create new database files suboption) and
the Custom option enable you to specify the type of environment in which to
operate your Oracle database:
Environment Description
Online Transaction Databases in OLTP environments must process thousands
Processing (OLTP) or even millions of transactions from many concurrent
(simultaneously connected) users each day. These
transactions consist of reading (SELECT statements),
writing (INSERT and UPDATE statements), and deleting
(DELETE statements) data in database tables. Users must
have quick access to the most current data. Therefore,
database performance is defined in terms of throughput
(speed) and availability of data.
Decision Support System Databases in DSS environments must process a variety of
(DSS) queries (typically read-only), ranging from a simple fetch
of a few records to numerous complex queries that sort
thousands of records from many different tables.
Therefore, database performance is defined in terms of
response time.
Environment Description
Hybrid Hybrid databases support both OLTP and DSS
environments.
Importing Sample Schemas. Sample OLTP and DSS database schemas are available on
the Oracle8i Enterprise Edition for Windows NT CD-ROM. After you finish creating
your Oracle database with Oracle Database Configuration Assistant, you can
import the appropriate sample schema.
If you selected Hybrid, you do not need to import a sample schema; one is already
provided with your database.
To import an OLTP or DSS sample schema into your Oracle database:
1. Start SQL*Plus:
C:\> SQLPLUS
2. Connect with the SYSTEM account:
Enter user-name: SYSTEM/PASSWORD
3. Create a special user account for importing the appropriate schema:
SQL> CREATE USER SAMPLE_USER IDENTIFIED BY PASSWORD;
SQL> GRANT RESOURCE TO SAMPLE_USER;
SQL> GRANT CONNECT TO SAMPLE_USER;
where SAMPLE_USER is SAMPLEOLTP for the OLTP sample schema or
SAMPLESTAR for the DSS sample schema.
4. Exit SQL*Plus:
SQL> EXIT;
5. Go to the ORACLE_BASE\ORACLE_HOME\ASSISTANTS\DBCA\SAMPLES
directory on your hard drive.
where:
C:\ORACLE is the ORACLE_BASE directory
ORA81 is the ORACLE_HOME directory
SAMPLE_USER is SAMPLEOLTP for the OLTP sample schema or
SAMPLESTAR for the DSS sample schema
SAMPLE.DMP is SOURCE80.DMP for the OLTP sample schema or
TARGET80.DMP for the DSS sample schema
Modifying a Database
The Modify a Database option enables you to perform the following procedures:
■ Configuring Advanced Replication and Oracle options
■ Enabling and Disabling Multi-Threaded Support.
Enabling and Disabling Multi-Threaded Support. This lets you choose whether to enable
or disable multi-threaded server support in your Oracle database.
Multi-threaded server (MTS) support lets multiple client user processes to share a
small number of server processes. Many client users can connect to a dispatcher
process. The dispatcher process then routes client requests to the next available
shared server process. No dedicated server process exists for each remaining user
process associated with the client user process for the duration of the connection.
Instead, inactive server processes are "recycled" and used as needed. This reduces
system overhead and enables you to increase the number of supported users.
Deleting a Database
The Delete a Database option of Oracle Database Configuration Assistant lets you
quickly and easily delete all database files, with the exception of the initialization
parameter file.
Using BUILD_DB.SQL
This section describes how to create a new database manually using a SQL script.
There are a number of ways to create a database depending on if you want to:
■ Copy an existing database to a new database and remove the old database.
■ Copy an existing database to a new database and keep the old database.
■ Create a new database when no other database exists on your system that you
can copy.
The following table summarizes the steps involved in creating a new database for
each of these database creation scenarios. Each step is explained in detail in the
following subsections.
Creating Directories
Create the following directories in which to put the administration and database
files for the new database PROD:
■ C:\ORACLE\ADMIN\PROD
■ C:\ORACLE\ADMIN\PROD\BDUMP
■ C:\ORACLE\ADMIN\PROD\PFILE
■ C:\ORACLE\ADMIN\PROD\UDUMP
■ C:\ORACLE\ORADATA\PROD
Note: If you use parameter mode, the Export Utility considers file names
and directory names to be invalid if a blank space is present. Enclose the
full path in the FILE= parameter in triple quotes. For example:
FILE="""C:\PROGRAM FILES\EXPORT.DMP"""
or
FILE="""C:\PROGRAM FILES\EXPORT FILE.DMP"""
If the Export Utility is used in interactive mode, the file name or directory
name can contain a space without quotes.
If you use INITSMPL.ORA as the basis for the INIT.ORA file, you must modify the
following initialization parameters in the INIT.ORA file, or you will not be able to
start the PROD database:
■ DB_NAME
■ INSTANCE_NAME
■ SERVICE_NAMES
■ CONTROL_FILES
■ BACKGROUND_DUMP_DEST
■ USER_DUMP_DEST
Modifying the DB_FILES initialization parameter is recommended to optimize
performance.
2. Set ORACLE_SID to equal PROD. Note that there are no spaces around the
equal sign (=) character:
C:\> SET ORACLE_SID=PROD
-- Create database
create rollback segment rb_temp storage (initial 100 k next 250 k);
tablespace rbs;
create public rollback segment rb3 storage(initial 50K next 250K)
tablespace rbs;
create public rollback segment rb4 storage(initial 50K next 250K)
tablespace rbs;
create public rollback segment rb5 storage(initial 50K next 250K)
tablespace rbs;
create public rollback segment rb6 storage(initial 50K next 250K)
tablespace rbs;
create public rollback segment rb7 storage(initial 50K next 250K)
tablespace rbs;
create public rollback segment rb8 storage(initial 50K next 250K)
tablespace rbs;
create public rollback segment rb9 storage(initial 50K next 250K)
tablespace rbs;
create public rollback segment rb10 storage(initial 50K next 250K)
tablespace rbs;
create public rollback segment rb11 storage(initial 50K next 250K)
tablespace rbs;
create public rollback segment rb12 storage(initial 50K next 250K)
tablespace rbs;
create public rollback segment rb13 storage(initial 50K next 250K)
tablespace rbs;
create public rollback segment rb14 storage(initial 50K next 250K)
tablespace rbs;
create public rollback segment rb15 storage(initial 50K next 250K)
tablespace rbs;
create public rollback segment rb16 storage(initial 50K next 250K)
tablespace rbs;
You will run this script at the Server Manager prompt in "Creating a Database" on
page 8-19.
Creating a Database
To use the BUILD_PROD.SQL script to create a database:
1. Verify that the service is started in the Windows NT Control Panel. In this
example, the service name is OracleServicePROD, and its status column must
display Started. If not, select the service name and click Start.
You can also check the status of the service by entering the following at the
MS-DOS command prompt:
C:\> NET START
If you receive any errors, there are three possible causes, as illustrated below.
Cause Solution
The BUILD_PROD.SQL script Correct them.
contains syntax errors.
Some of the files to be created by Make sure you are not using any file names already used by another
the BUILD_PROD.SQL script database on the system.
already exist in the file system.
An error occurred at the operating You should have received a series of errors in Server Manager, the last one
system level, such as a file or of which should have the OSD- prefix. At the end of the OSD error, you
directory permission problem. typically see an operating system error number in parentheses.
To see what the error means, do either of the following.
From the MS-DOS command prompt, enter:
C:\> NET HELPMSG n
or
From the Server Manager prompt, enter:
SVRMGR> HOST NET HELPMSG n
where n is the operating system error number.
7. Run the CATPROC.SQL script to install the objects used by the Oracle
database’s PL/SQL functionality:
SVRMGR> @C:\ORACLE\ORA81\RDBMS\ADMIN\CATPROC.SQL;
Importing a Database
You can import the full export created in "Exporting an Existing Database" on
page 8-12 into the new database.
You can also invoke the Import Utility, using parameter mode or interactive mode.
Parameter mode is recommended, because interactive mode provides less
functionality. Interactive mode exists solely for backward compatibility.
Note: If you use parameter mode, the Import Utility considers file names
and directory names to be invalid if there is a blank space. Enclose the full
path in the FILE= parameter in triple quotes. For example:
FILE="""C:\PROGRAM FILES\EXPORT.DMP"""
or
FILE="""C:\PROGRAM FILES\EXPORT FILE.DMP"""
If you use the Import Utility in interactive mode, the file name or directory
name can contain a space without quotes.
To import a database:
■ Run the Import Utility:
C:\> IMP SYSTEM/PASSWORD FILE=MYEXP.DMP FULL=Y LOG=MYIMP.LOG
\HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID,
where ID is the unique number identifying the Oracle home.
3. Locate the ORACLE_SID parameter on the right side of the registry editor
window.
4. Double-click the parameter name and change the data to the new SID, which is
PROD in this example.
If you do not yet have the ORACLE_SID,because this is the first database on your
system, you must create the ORACLE_SID, parameter.
To create the ORACLE_SID parameter:
1. From the Edit menu, choose Add Value....
The Add Value dialog box appears:
ORADIM and Oracle Database Configuration Assistant perform similar tasks. The
following table compares what you can do with these tools.
When you use ORADIM, a log file called ORADIM.LOG opens in ORACLE_
BASE\ORACLE_HOME\DATABASE, or in the directory specified by the ORA_
CWD registry parameter. All operations, whether successful and failed, are logged
in this file. You must check this file to verify the success of an operation.
The following sections describe the ORADIM commands and parameters. Note that
each command is preceded by a dash (-).
Creating an Instance
To create an instance...
Use this syntax: ORADIM -NEW -SID SID | -SRVC SERVICE_NAME [-INTPWD INTERNAL_PWD] -
SHUTTYPE SRVC | INST | SRVC, INST
[-MAXUSERS NUMBER][-STARTMODE AUTO | MANUAL][-PFILE FILENAME]
Example to create C:\> ORADIM -NEW -SID PROD -INTPWD MYPASSWORD1 -STARTMODE AUTO
an instance called -PFILE C:\ORACLE\ADMIN\PROD\PFILE\INIT.ORA
PROD:
Syntax ■ -NEW Indicates that you want to create a new instance. This is a
description: mandatory parameter.
■ -SID SID The name of the instance you want to create. You must specify
either this parameter or the -SRVC parameter described below.
■ -SRVC The name of the service you want to create (OracleServiceSID).
SERVICE_NAME You must specify either this parameter or the -SID parameter
described above.
■ -INTPWD The password for the INTERNAL account. The -INTPWD option
INTERNAL_PWD is not required. If you do not specify it, operating system
authentication is used, and no password is required. See
"Automatically Enabling Operating System Authentication
During Installation" on page 10-3 for a description of features.
■ -MAXUSERS The number of users defined in the password file. The default is
NUMBER 5.
■ -STARTMODE Indicates whether to start the instance automatically or
AUTO, MANUAL manually at startup. The default setting is MANUAL.
■ -PFILE The INIT.ORA file to be used with this instance. Ensure that you
FILENAME specify the complete pathname of this file, including drive letter.
■ -SHUTTYPE Indicates whether to stop the service or the instance. Both can be
SRVC, INST specified. This is a mandatory parameter.
Starting an Instance
To start an instance...
Use this syntax: ORADIM -STARTUP -SID SID [-USRPWD USER_PWD] [-STARTTYPE SRVC | INST | SRVC,
INST] [-PFILE FILENAME]
Example to start C:\> ORADIM -STARTUP -SID PUMA -STARTTYPE SRVC -PFILE
an instance called C:\ORACLE\ADMIN\PROD\PFILE\INIT.ORA
PUMA:
Syntax ■ -STARTUP Indicates that you want to start an instance that already
description: exists. This is a mandatory parameter.
■ -SID SID The name of the instance you want to start. This is a
mandatory parameter.
■ -USERPWD USER_ The password.
PWD
■ -STARTTYPE SRVC, Indicates whether to start the service or the instance. One or
INST both values can be specified. If not specified, the registry is
checked for the current setting.
Stopping an Instance
To stop an instance:
Use this syntax: ORADIM -SHUTDOWN -SID SID [-USRPWD USER_PWD] [-SHUTTYPE SRVC | INST | SRVC,
INST] [-SHUTMODE A | I | N]
Example to stop C:\> ORADIM -SHUTDOWN -SID PUMA -SHUTTYPE SRVC INST
an instance called
PUMA:
Syntax ■ -SHUTDOWN Indicates that you want to stop an instance. This is a
description: mandatory parameter.
■ -SID SID The name of the instance you want to stop. This is a
mandatory parameter.
■ -USERPWD USER_ The password.
PWD
■ -SHUTTYPE SRVC, Indicates whether to stop the service or the instance. One or
INST both values can be specified. If not specified, the registry is
checked for the current setting.
■ -SHUTMODE A, I, N Specifications on how to stop an instance; A indicates abort
mode, I indicates immediate mode, and N indicates normal
mode. This is an optional parameter. If you do not specify
how to stop an instance, normal is the default mode.
Modifying an Instance
To modify an instance...
Use this syntax: ORADIM -EDIT -SID SID [-NEWSID NEWSID] [-INTPWD INTERNAL_PWD]
[-STARTMODE AUTO | MANUAL][-PFILE FILENAME]
Example to modify C:\> ORADIM -EDIT -SID PROD -NEWSID LYNX -INTPWD MYCAT123 -STARTMODE
an instance called AUTO -PFILE C:\ORACLE\ADMIN\LYNX\PFILE\INIT.ORA
PROD:
Note: You can modify an existing instance, in this example PROD, to change such values as the
instance name, the password, the startup mode, and the number of users.
Syntax ■ -EDIT Indicates that you want to modify an instance. This is a
description: mandatory parameter.
■ -SID SID The name of the instance you want to modify. This is a
mandatory parameter.
■ -NEWSID The new instance name. This is an optional parameter.
NEWSID
■ -INTPWD The password for the INTERNAL account.
INTERNAL_PWD
Note: This parameter cannot be used to change the password, as
it does not overwrite the existing password file. It can only
create a new password file when none already exists. To create a
new password file, use ORAPWD, or delete the Oracle8i services
(this action implicitly deletes the associated password file) and
then recreate the Oracle8i services (this action implicitly creates
the associated password file). See "Password Utility (ORAPWD)"
in Chapter 3, "Database Tools Overview".
■ -STARTMODE Indicates whether to start the instance automatically or
AUTO, MANUAL manually at startup. The default setting is MANUAL.
■ -PFILE The INIT.ORA file to be used with this instance. Ensure that you
FILENAME specify the complete pathname of this file, including drive letter.
Additional Oracle services related to specific products or database features are also
available:
Services for network products are also available. See Net8 Administrator’s Guide for
information on Oracle network services.
Note: You can start the Oracle8i database when you start
OracleServiceSID. See section "Starting and Shutting Down a
Database Using Services" for information on registry parameters
that enable you to do this.
If either is set to FALSE (the default setting), you cannot shut down the
database by stopping OracleServiceSID.
The exact location in which to set these parameters is determined by the
number of Oracle home directories on your computer:
Parameter Description
ORA_SID_ Set to A (abort), I (immediate), or N (normal) to indicate the
SHUTDOWNTYPE database shutdown mode. The default mode is I (immediate) if
you do not set this parameter.
ORA_SID_ Sets the maximum time to wait before the service for a particular
SHUTDOWN_ SID stops.
TIMEOUT
To start or stop a Database using Oracle Services from the Oracle Administration
Assistant for Windows NT:
1. Choose Start > Programs > Oracle - HOME_NAME > Enterprise Management >
Database Administration Applications > Oracle Administration Assistant for
Windows NT.
2. Right-click the SID
where SID is a specific instance name, such as ORCL.
3. Choose Startup/Shutdown Options...
4. Click the Oracle Instance tab.
5. Select Start up instance when service is started or select Shut down instance
when service is stopped.
Element Description
SID Identifies the database instance.
FILE Specifies the password file name.
PASSWORD Sets the password for the INTERNAL and SYS accounts.
ENTRIES Sets the maximum number of entries in the password file. This
corresponds to the maximum number of distinct users allowed to
connect to the database with the SYSDBA and SYSOPER DBA
privileges simultaneously.
Element Description
EXCLUSIVE Specifies that only one instance can use the password file and that the
password file contains names other than SYS and INTERNAL. Oracle8i
looks in the registry for the value of the ORA_SID_PWFILE parameter.
If a value is unspecified, it looks in the registry for the value of the
ORA_PWFILE parameter, which points to a file containing the
INTERNAL password as well as user names, passwords, and
privileges. If that is not set, it uses the default of ORACLE_
BASE\ORACLE_HOME\DATABASE\PWDSID.ORA.
Element Description
SHARED Specifies that multiple instances can use the password file (for example,
a parallel server environment). However, the only users recognized by
the password file are SYS and INTERNAL. You cannot log in with
SYSOPER or SYSDBA privileges even if those privileges are granted in
the password file. The SHARED value of this parameter affords
backward compatibility with earlier releases. The Oracle8i database
looks for the same files as it does when the value is EXCLUSIVE, but
only the INTERNAL account is available for privileged access. This is
the default value.
NONE Specifies that the Oracle8i database ignores the password file and that
privileged users are authenticated by the Windows NT operating
system. NONE is the default setting.
3. Start SQL*Plus:
C:\> SQLPLUS
4. Connect as INTERNAL:
SQL> CONNECT INTERNAL
5. Start the Oracle8i database:
SQL> STARTUP
6. Grant appropriate privileges to each user who needs to perform database
administration. For example:
SQL> GRANT SYSDBA TO SCOTT;
If successful, the following message displays:
Statement Processed.
This adds SCOTT to the password file and enables SCOTT to connect to the
database with SYSDBA privileges. Use SQL*Plus to add or delete user names,
user passwords, and user privileges in password files.
7. Connect to the Oracle8i database with DBA privileges for SCOTT:
SQL> CONNECT SCOTT/TIGER AS SYSDBA
You are connected to the Oracle8i database.
To... Enter...
See the password file C:\ORACLE\ORA81\DATABASE> ATTRIB
The password file displays:
A H C:\ORACLE\ORA81\DATABASE\PWDSID.ORA
Make the password file visible C:\ORACLE\ORA81\DATABASE> ATTRIB -H
PWDSID.ORA
Note: The password file must be visible before you can
move or copy it.
Hide the password file again C:\ORACLE\ORA81\DATABASE> ATTRIB +H
PWDSID.ORA
To... Click...
See the password file Show all files.
Hide the password file Do not show hidden files.
In NOARCHIVELOG mode, redo logs are not archived. This protects the database
from instance failure, but not from disk failure. Setting your archive mode to
ARCHIVELOG and enabling automatic archiving causes redo log files to be
archived. This protects the database from both instance and disk failure.
This section describes how to change the archive mode to ARCHIVELOG and
enable automatic archiving. See the chapter "Archiving Redo Information" of the
Oracle8i Administrator’s Guide for complete descriptions of the ARCHIVELOG and
NOARCHIVELOG modes.
This chapter describes how to authenticate Oracle8i database users with Windows
NT. Specific topics discussed are:
■ Authentication Overview
■ Automatically Enabling Operating System Authentication During Installation
■ Oracle Administration Assistant for Windows NT
Authentication Using the Oracle Administration Assistant for Windows NT
■ Adding a Computer
■ Granting Database Administrator and Database Operator Privileges Using Oracle
Administration Assistant for Windows NT
■ Connecting to a Database
■ Create a Nonprivileged Database User using Oracle Administration Assistant
for Windows NT
■ Create a Local Database Role
■ Create an External OS Role
Manual Authentication Using Windows NT
■ Connecting Without a Password as a Nonprivileged Database User
■ Connecting as SYSDBA and SYSOPER Without a Password
■ Connecting as INTERNAL Without a Password
■ Granting Database Roles through Windows NT
Authentication Overview
The Oracle8i database can use information maintained by Windows NT to
authenticate database users. The benefits of Windows NT authentication include:
■ Enabling users to connect to an Oracle8i database without supplying a user
name or password
■ Centralizing Oracle8i database user authorization information in Windows NT,
which frees Oracle8i from storing or managing user passwords
■ Allowing Oracle8i and Windows NT user names to be the same
Windows NT Native authentication methods (automatically installed with Net8
Server and Net8 Client) enable database user authentication through Windows NT.
This enables client computers to make secure connections to an Oracle8i database
on a Windows NT server. A secure connection is when a Windows NT client user
name is retrieved on a Windows NT server through Windows NT Native
authentication methods. The Windows NT server then permits the user name to
perform the database actions on the server.
In Oracle 8.1.5, by default, external users created in the database must be prefixed
with the domain name. For example, for an NT user DOMAIN1\NTUSER1, the
Oracle user created in the database must be DOMAIN1\NTUSER1. If you wish to
create the Oracle user in the database without prefixing with the domain name, you
first need to set the registry value OSAUTH_PREFIX_DOMAIN in
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID to FALSE.
Adding a Computer
When you use Oracle Administration Assistant for Windows NT for the first time, it
will automatically add the local computer in the navigation tree. You may then add
another computer by following steps:
1. Choose Start > Programs > Oracle - HOME_NAME > Enterprise Management >
Database Administration Applications > Oracle Administration Assistant for
Windows NT.
2. Right Click Computer.
3. Choose New > Computer
4. Specify the domain and hostname of the computer on which your Oracle
database is installed, and click OK.
5. Double-click Computers to display the computer you added.
6. Double-click the computer you added. Several Oracle Administration Assistant
for Windows NT nodes appear.
7. In the appropriate pull down menu select the domain location and name of the
computer on which the Oracle database is installed.
8. Click OK. You can now access the Oracle database to perform authentication
tasks.
Save your configuration in a console file by clicking Save on the Console pull-
down menu.
4. Highlight the name of a user or from the NT Domain Users and Groups box to
grant SYSDBA privileges.
5. Click the Add button. The user will now appear in the OS Database Operators
window.
6. Click OK.
To grant the SYSDBA privileges using the Oracle Administration Assistant for
Windows NT snap-in in the Microsoft Management Console:
3. Highlight the name of a user or from the NT Domain Users and Groups box to
grant SYSDBA privileges.
4. Click the Add button. The user will now appear in the OS Database
Administrators window.
5. Click OK.
Connecting to a Database
1. Right-click the database instance to access (for example, ORCL) in the Microsoft
Management Console scope pane.
The Windows NT domain user with which you are attempting to connect to the
Oracle database is not recognized as an authenticated user with SYSDBA privilege.
Therefore, you must enter an Oracle user name and password to access the
database. To avoid being prompted with this dialog box again, configure your
domain user to be a database administrator authenticated by the Windows NT
operating system.
The dialog box shown above appeared because you are not using the TCP/IP
networking protocol to connect to a remote Oracle database. Using SPX or Named
Pipes causes this dialog box to appear each time you attempt a remote connection.
To avoid having to respond to this dialog box, change to the TCP/IP networking
protocol and use default port 1521 or 1526.
The dialog box shown above may also appear because the Oracle database is not
running. Start the Oracle database.
Database Authenticated
Select this option if you want to access the database with an Oracle user name and
password. This user name and password must exist in the Oracle database. This
user name must also have the SYSDBA privilege.
■ Enter an Oracle database user name.
■ Enter the password for the Oracle database user name.
OS Authenticated Connection as SYSDBA
Select this option if you want to access the database with the Windows NT domain
user with which you are currently logged in. This Windows NT domain user must
already be recognized by Windows NT as an authenticated user with SYSDBA
privileges. Otherwise, your logon attempt will fail.
Database Properties
To view database properties right click the database, choose Properties.
4. Choose the domain from the Domain pull down menu then from the NT
Domain Users and Groups box select the name of the user or group you want to
grant access to the database.
5. Click the Add button. The user will now appear in the New NT Authenticated
Users window.
6. Click Next.
The Step2 page allows you to choose which profile and tablespace information to
assign to the user or group.
7. Select a profile for the new External OS users. A profile is a named set of
resource limits. If resource limits are enabled, Oracle limits database usage and
instance resources to whatever is defined in the user’s profile. You can assign a
profile to each user, and a default profile to all users who do not have specific
profiles.
8. In the Tablespace Quota window double-click the tablespace to assign a
tablespace quota. It assigns profile and tablespace information to them, and
grants database roles.
9. Click Next.
10. In the Step 3 page highlight the database role to the selected NT users and
groups.
11. Click the Grant button.
To view the properties of an external OS user click on External OS Users in the
Microsoft Management Console scope pane. Right click the external OS user for
which you wish to view the properties and select Properties.
OS_ROLES
OS_ROLES is a parameter in the INIT.ORA file that, if set to TRUE, enables the
Windows NT operating system to manage the authorization of external OS roles for
database users. If OS_ROLES is set to TRUE only external OS roles will be displayed
in the field Granted External OS Roles. By default, OS_ROLES is set to FALSE and
only local roles will be displayed in the field Granted Roles. You must set
OS_ROLES to TRUE and restart your Oracle database before you can create external
OS roles.
If OS_ROLES is set to FALSE, the Oracle database manages the granting and
revoking of roles for database users.
If OS_ROLES is set to TRUE and you assign an external OS role to an NT global
group, it is granted only at the global group level, and not at the level of the
individual user in this global group. This means that you cannot revoke or edit the
external OS role assigned to an individual user in this global group through the
Roles tab of the Domain\User Name Properties dialog box at a later time. Instead,
you must use the Assign External OS Roles to an NT Global Group in the dialog box
to revoke the external OS role from this global group (and therefore all its
individual users).
External OS roles assigned to an individual domain user or local roles (with
OS_ROLES set to FALSE) assigned to an individual domain user or NT global
group are not affected by this issue, and can be edited or revoked.
If OS_ROLES is set to TRUE, you can not grant local roles in the database to any
database user. You must grant the roles through Windows NT.
3. Enter a Local Role name to use. A Local Role is a role that is managed by the
Oracle database.
4. Select None if you want a user to be able to use this local role without being
required to enter a password.
5. Select Password if you want the use of this role to be protected by a password.
These roles can only be used by supplying an associated password with the SET
ROLE command. See the Oracle8 Administrator’s Guide for additional information.
6. Enter the password to use with this role.
7. Confirm the password by entering it a second time.
8. Click Next.
Available Roles
Select appropriate roles to assign to the local role. Both local roles and External OS
roles appear in this list.
13. Click Revoke to revoke the selected roles from the role.
14. The Granted Roles Displays the list of roles granted to the role. Both local roles
and external OS roles can appear in this list. To revoke roles, make appropriate
selections, then click Revoke.
15. Click Back to go to the previous step in this wizard.
11. Click Grant to grant the selected roles to the External OS role. Both Local roles
and external OS roles appear in this list.
Click Revoke to revoke the selected roles from the External OS role.
The Granted Roles box displays the list of roles granted to the External OS role.
Both Local roles and External OS roles can appear in this list.
12. Click Finish.
The local and domain user name FRANK and the domain SALES are used in the
steps below. Substitute the appropriate local and domain user name and domain
name for your environment.
Follow the steps below to connect without a password as a nonprivileged database
user:
■ Step 1: Perform Authentication Tasks on the Oracle8i Database Server
■ Step 2: Perform Authentication Tasks on the Client Computer
The parameter value XYZ is used in the steps below. Substitute XYZ with the
value you set for OS_AUTHENT_PREFIX.
3. Use User Manager to create a Windows NT local or domain user name for
FRANK (if the appropriate name does not currently exist). See your Windows
NT documentation or your network administrator if you do not know how to
do this.
4. Ensure that you have the following line in your
ORACLE_BASE\ORACLE_HOME\NETWORK\ADMIN\SQLNET.ORA file:
SQLNET.AUTHENTICATION_SERVICES = (NTS)
5. Start SQL*Plus:
C:\> SQLPLUS
6. Connect to the database with the SYSTEM database administrator (DBA) name:
SQL> CONNECT
Enter user-name: SYSTEM/PASSWORD
Unless you have changed it, the SYSTEM password is MANAGER by default.
7. Create an operating system-authenticated user by entering the following:
Where: Is the...
XYZ Value set for the OS_AUTHENT_PREFIX initialization parameter.
FRANK Windows NT local user name.
SALES\FRANK Domain name and Windows NT domain user name. The double
quotes are required and the entire syntax must be in uppercase.
8. Grant the Windows NT local user FRANK or domain user FRANK appropriate
database roles:
SQL> SHUTDOWN
11. Restart the database:
SQL> STARTUP
This causes the change to the OS_AUTHENT_PREFIX parameter value to take
affect.
The SYSOPER and SYSDBA privileges are mapped to the following Windows NT
local groups:
4. Click Add.
5. Select an appropriate Windows NT user from the Names field and click Add.
6. Click OK.
Your selection is added to the Members field of the New Local Group dialog box:
7. Click OK.
8. Exit User Manager.
9. Ensure that you have the following line in your ORACLE_BASE
\ORACLE_HOME\NETWORK\ADMIN\SQLNET.ORA file:
SQLNET.AUTHENTICATION_SERVICES = (NTS)
10. In the registry in
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID set the
parameter OSAUTH_PREFIX_DOMAIN to TRUE.
6. Connect as SYSOPER or SYSDBA based on the local group you specified in step
3 of "Step 1: Perform Authentication Tasks on the Oracle8i Database Server":
":
You are connected to the Windows NT server. If you connect with SYSDBA, you
are given DBA privileges.
This enables you to log into a local computer or a Windows NT domain. In the
domain, your Oracle8i database is just one of many resources to which you have
access. Once you access this domain, you are automatically validated as an
authorized DBA who can access the Oracle8i database without a password.
Follow the steps below to connect as INTERNAL without a password:
■ Step 1: Perform Authentication Tasks on the Oracle8i Database Server
■ Step 2: Perform Authentication Tasks on the Client Computer
6. Click Add.
7. Select an appropriate Windows NT local or domain user from the Names field
and click Add.
8. Click OK.
Your selection is added to the Members field of the New Local Group dialog box:
9. Click OK.
10. Exit User Manager.
If You... Then...
1. Enable operating system roles. You only receive the roles granted to
DTMSDOM\FRANK, and not the
2. Log onto a Windows NT domain with your
roles granted to SCOTT.
domain user name; for example,
SALES\FRANK, where SALES is the domain
name and FRANK is the domain user name.
3. Connect to the Oracle8i database as Oracle
database user SCOTT.
Follow the steps below to grant database roles with Windows NT:
■ Step 1: Perform Authentication Tasks on the Oracle8i Database Server
■ Step 2: Perform Authentication Tasks on the Client Computer
4. Start SQL*Plus:
C:\> SQLPLUS
5. Connect to your Windows NT server:
SQL> CONNECT INTERNAL
6. Create a new database role:
SQL> CREATE ROLE DBSALES3 IDENTIFIED EXTERNALLY;
where DBSALES3 is the name of the role for these steps. Substitute a role name
appropriate to your database environment.
7. Grant Oracle roles to DBSALES3 that are appropriate to your database
environment:
SQL> GRANT DBA TO DBSALES3 WITH ADMIN OPTION;
SQL> GRANT RESOURCE TO DBSALES3 WITH ADMIN OPTION;
SQL> GRANT CONNECT TO DBSALES3 WITH ADMIN OPTION;
8. Connect to the database with the INTERNAL DBA name:
SQL> CONNECT INTERNAL
9. Shut down the database:
SQL> SHUTDOWN
10. Restart the database:
SQL> STARTUP
11. Open the Windows NT User Manager.
13. Enter the Windows NT local group name corresponding to the database role in
the Group Name field with the following syntax:
ORA_SID_ROLENAME [_D] [_A]
where:
15. Select the appropriate Windows NT local or domain user name and click Add.
Registry Information
When you install Oracle Performance Monitor, values are automatically set in the
registry as described in Appendix C, "Oracle 8i Configuration Parameters and the
Registry".
The Oracle Performance Monitor allows you to monitor only one database instance
at a time. For this reason, the registry contains the following values:
■ Hostname
■ Username
■ Password
Use OPERFCFG to change these values. See section "Modifying Oracle for Windows
NT Performance Monitor Parameters" on page C-18.
To use Oracle Performance Monitor for another database instance on the same
computer or a UNIX computer, change the values appropriately in the registry. You
can also monitor non-NT Oracle databases by changing the Hostname registry
value so it points to another computer specified in the TNSNAMES.ORA file.
counters objects
The Oracle Performance Monitor has four views you can choose from the View
menu:
View Description
Chart View Displays database activity in real-time.
Alert View Lets you know when certain minimum performance criteria are
not being met, or maximum criteria are being exceeded.
Log View Maintains continuous records on performance.
Report View Saves information about specific criteria.
Below is the Add to Chart dialog box. Note the corresponding dialog boxes for
the other views are different.
Element Description
Computer list box Specify the computer you want to monitor.
Object drop-down list Select an object to monitor.
box
Note: If no data or Oracle8i objects appear, either the database
is not running, or an invalid host string or password has been
entered. If the database is not started, exit Oracle Performance
Monitor, start the database, and restart Oracle Performance
Monitor.
Counter list box Select a counter (or multiple counters) for the object you have
selected. Note that the contents of the Counter box change
depending upon your selection in the Object box.
If you want details on how a counter works, highlight the
counter and choose Explain.
Instance box Select an instance for this counter.
Color box Choose a color for the display of the selected counter.
Scale box Choose the scale at which you want to display the counter.
Element Description
Width box Specify the width of the line on the graph.
Style box Choose a different style for your graph line.
Note: You can only monitor one instance at a time using Oracle
Performance Monitor on a given computer.
Event ID Description
IDs other than 34 Specifies general database activities, such as an instance being
started or stopped.
34 Specifies an audit trail event. These events are recorded if the
AUDIT_TRAIL parameter is set to DB (TRUE) or OS in the
INIT.ORA file.
The OS option enables system-wide auditing and causes
audited records to be written to the Event Viewer.
The DB option enables system-wide auditing and causes
audited records to be written to the database audit trail (the
SYS.AUD$ table). Some records, however, are written to the
Event Viewer.
The alert file contains important information about error messages and exceptions
that occur during database operations. Each Oracle8i Enterprise Edition instance
has one alert file; information is appended to the file each time you start the
instance. All threads can write to the alert file.
For example, when automatic archiving of redo logs is halted because no disk space
is available, a message is placed in the alert file. The alert file is the first place to
check if something goes wrong with the database and the cause is not immediately
obvious.
The alert file is named SIDALRT.LOG and is found in the directory specified by the
BACKGROUND_DUMP_DEST parameter in the INIT.ORA initialization parameter
file. If the BACKGROUND_DUMP_DEST parameter is not set, the SIDALRT.LOG
file is generated in ORACLE_BASE\ADMIN\DB_NAME\BDUMP.
File Description
File Allocation Table (FAT) or NT File allocation table (FAT) or NT file system (NTFS) files
File System (NTFS) files you want to back up.
Logical raw files A logical drive (accessed with the direct I/O) identified
by the name:
\\.\x:
where x: is the logical drive designator.
Physical raw files A physical hard drive (accessed with direct I/O)
identified by a device name of the form:
\\.\physicaldriveN
where N is 0, 1, 2, and so on, representing each of the
physical drives in the system.
This table describes the two copy modes in which to use OCOPY:
This table describes the syntax to use when backing up all file types to hard disk or
multiple diskettes:
Note: Always use a fresh diskette for each OCOPY procedure; do not use
OCOPY to back up a file onto a diskette that contains part or all of another
file backed up using OCOPY.
Restore
From... File Type to Restore Syntax
Hard Disk1 FAT or NTFS files Use the Windows NT COPY command.
Configuring Net8
If you install Net8 Server from your Oracle8i Enterprise Edition CD-ROM, your
server network files are automatically configured to use external procedures.
When PL/SQL calls an external procedure, the Net8 listener launches a
session-specific process called EXTPROC. Through Net8, PL/SQL passes the
following information to EXTPROC:
■ DLL name
■ External procedure name
■ Parameters (if necessary)
EXTPROC then loads the DLL and invokes the external procedure.
If you copy your Oracle7 server network files into your Oracle8i network files
directory, you must manually configure the following files for the external
procedure behavior described previously to occur:
■ ORACLE_BASE\ORACLE_HOME\NETWORK\ADMIN\LISTENER.ORA
■ ORACLE_BASE\ORACLE_HOME\NETWORK\ADMIN\TNSNAMES.ORA
See Chapter 6 of the Oracle Net8 Administrator’s Guide for instructions.
.
Note: Since external procedures are built into DLLs, they must be
explicitly exported. In this example, the dllexport storage class
modifier exports the function find_max from a dynamic link library.
#include <windows.h>
#define NullValue -1
/*
This function simply returns the larger of x and y.
*/
long __declspec(dllexport) find_max(long x,
short x_indicator,
long y,
short y_indicator,
short *ret_indicator)
{
/* It can be tricky to debug DLL’s that are being called by a process
that is spawned only when needed, as in this case.
Therefore try using the DebugBreak(); command.
This will start your debugger. Uncomment the line with DebugBreak();
in it and you can step right into your code.
*/
/* DebugBreak(); */
if ( x_indicator==NullValue || y_indicator==NullValue) {
*ret_indicator = NullValue;
return(0);
} else {
*ret_indicator = 0; /* Signify that return value is not null */
if (x >= y) return x;
else return y;
}
}
Building a DLL
After writing your external procedure(s) in a 3GL programming language, use the
appropriate compiler and linker to build a DLL, making sure to export the external
procedures, as noted above. See your compiler and linker documentation for
instructions on building a DLL and exporting its functions.
After building the DLL, you can move it to any directory on your system. For the
example above, you can build the external procedure find_max into a DLL called
EXTERN.DLL. To build the above example, go to ORACLE_BASE\ORACLE_
HOME\RDBMS\EXTPROC and type MAKE.
Example 13–1
Additional Documentation
See the following documents for more information on external procedures:
■ Oracle8 Administrator’s Guide
■ PL/SQL User’s Guide and Reference
■ The following files in ORACLE_BASE\ORACLE_HOME\RDBMS\EXTPROC:
– EXTERN.C (code example shown in "Writing an External Procedure")
– MAKE.BAT (batch file that builds the dynamic link library)
– EXTERN.SQL (automates the instructions described in "Registering an
External Procedure" and "Executing an External Procedure")
– README.DOC (explains how to run the sample and provides debugging
advice)
4. Type HTTP_PROXY in the Value Name text box and REG_SZ in the Data Type
text box.
5. Click OK.
6. Type www-proxy.your-site in the String text box,
A call to REQUEST_PIECES can look like the example below. Note the use of the
PL/SQL table method COUNT to discover the number of pieces returned; this may
be zero or more:
declare pieces utl_http.html_pieces;
begin
pieces := utl_http.request_pieces(’http://www.oracle.com/’);
for i in 1 .. pieces.count loop
.... -- process each piece
end loop;
end;
The second argument to UTL_HTTP.REQUEST_PIECES, (MAX_PIECES) is
optional. MAX_PIECES is the maximum number of pieces (each 2000 characters in
length, except for the last, which may be shorter) that UTL_HTTP.REQUEST_
PIECES returns. If provided, that argument is usually a positive integer.
For example, the following block retrieves up to 100 pieces of data (each 2000 bytes,
except perhaps the last) from the URL. The block prints the number of pieces
retrieved and the total length, in bytes, of the data retrieved.
set serveroutput on
/
declare
x utl_http.html_pieces;
begin
x := utl_http.request_pieces(’http://www.oracle.com/’, 100);
dbms_output.put_line(x.count || ’ pieces were retrieved.’);
dbms_output.put_line(’with total length ’);
if x.count < 1
then dbms_output.put_line(’0’);
else dbms_output.put_line
((2000 * (x.count - 1)) + length(x(x.count)));
end if;
end;
/
which outputs:
Statement processed.
4 pieces were retrieved.
with total length
7687
The elements of the PL/SQL table returned by UTL_HTTP.REQUEST_PIECES are
successive pieces of data obtained from the HTTP request to that URL.
UTL_HTTP.REQUEST
PRAGMA RESTRICT_REFERENCES enables the display of exceptions:
create or replace package utl_http is
function request (url in varchar2) return varchar2;
pragma restrict_references (request, wnds, rnds, wnps, rnps);
UTL_HTTP.REQUEST_PIECES
PRAGMA RESTRICT_REFERENCES enables exceptions to be displayed:
create or replace package utl_http is
type html_pieces is table of varchar2(2000) index by binary_integer;
function request_pieces (url in varchar2,
max_pieces natural default 32767)
return html_pieces;
pragma restrict_references (request_pieces, wnds, rnds, wnps, rnps);
If... Then...
Initialization of the HTTP callout subsystem fails Exception UTL_HTTP.INIT_FAILED is raised:
for environmental reasons such as lack of
init_failed exception;
available memory
If... Then...
The HTTP call fails due to failure of the HTTP Exception UTL_HTTP.REQUEST_FAILED is raised:
daemon or because the argument to REQUEST or
request_failed exception;
REQUEST_PIECES cannot be interpreted as a
URL, because it is NULL or has non-HTTP syntax
No response is received from a request to the A formatted HTML error message may be returned:
given URL, because the function made no contact
<HTML>
with a site corresponding to that URL
<HEAD>
<TITLE>Error Message</TITLE>
</HEAD>
<BODY>
<H1>Fatal Error 500</H1>
Can’t Access Document:
http://home.nothing.comm.
<P>
<B>Reason:</B> Can’t locate remote host:
home.nothing.comm.
<P>
<P><HR>
<ADDRESS><A HREF="http://www.w3.org">
CERN-HTTPD3.0A</A></ADDRESS>
</BODY>
</HTML>
Troubleshooting
Do not expect UTL_HTTP.REQUEST or UTL_HTTP.REQUEST_PIECES to succeed
in contacting a URL unless you can contact that URL by using a browser on the
same computer (and with the same privileges, environment variables, and so on).
If UTL_HTTP.REQUEST or UTL_HTTP.REQUEST_PIECES fails (that is, if it raises
an exception or returns an HTML-formatted error message, yet you believe that the
URL argument is correct), try contacting that same URL with a browser to verify
network availability from your computer.
This appendix describes the default directory structures created when you install
Oracle8i Enterprise Edition, Oracle8i Client, or Oracle Programmer, and Net8.
Specific topics discussed:
■ Oracle8i Enterprise Edition Directory Structure
■ Oracle8i Client Directory Structure
■ Oracle Programmer Directory Structure
■ Net8 Directory Structure
ORACLE_HOME
If you install Oracle8i Enterprise Edition with the Typical installation type, the
following directories are created. If you install additional Oracle products, other
directories are also created.
Directory Contents
\A2OWIZ Oracle Migration Assistant for Microsoft Access files
\ASSISTANTS Oracle assistants. \ASSISTANTS contains the following
subdirectories:
\DBCA ■ Oracle Database Configuration Assistant files
\DBMA ■ Oracle Data Migration Assistant files
\IFA ■ Oracle INTYPE File Assistant files
\JLIB ■ Java files used by the assistants
\OWAST ■ Oracle Web Publishing Assistant files
Directory Contents
\BIN Executable files
\COM Oracle COM Automation feature files
\CTX Oracle interMedia Text files. \CTX contains the
following subdirectories:
\ADMIN ■ SQL scripts for installation and configuration, and
header and body files for PL/SQL packages
\BIN ■ Executable files
\DEMO ■ Empty
\DOC ■ Release notes
\LIB ■ Library files
\MESG ■ Message files
\DATA ■ Data files
\LOG ■ Log file default directory
\MIGRATE ■ Migration scripts
\SAMPLE ■ Sample thesauri
\DATABASE This is a legacy directory from previous releases. It
contains an initialization parameter file that points to the
new directory location for initialization parameter files.
\DBS Oracle for Windows NT Performance Monitor files and
other utility files
\DOC HTML documentation library
\JAVAVM Java Virtual Machine files. \JAVAVM contains the
following subdirectories:
\DEMO ■ Sample programs
\INSTALL ■ SQL scripts
\JDBC Java Database Connectivity (JDBC) drivers files. \JDBC
contains the following subdirectories:
\ADMIN ■ Class files
\DEMO ■ Sample programs
\JLIB Java files used by various applications
Directory Contents
\MD Oracle Spatial files. \MD contains the following
subdirectories:
\ADMIN ■ SQL scripts
\DOC ■ Release notes
\LIB ■ Library files
\MSHELP Help files
\NETWORK Net8 files. \NETWORK contains the following
subdirectories:
\ADMIN ■ Configuration files
\AGENT ■ Oracle Intelligent Agent files
\DOCS ■ Release notes
\JLIB ■ Java files used by Net8 assistants
\LOG ■ Log files (default location)
\MESG ■ Message files
\TNSAPI ■ Net8 Open API-related files
\TOOLS ■ Net8 assistant files
\TRACE ■ Trace files (default location)
\OCI Oracle Call Interface files. \OCI contains the following
subdirectories:
\INCLUDE ■ Header files
\LIB ■ Library files
\SAMPLES ■ Sample files
\OCOMMON NLS files
\ODBORA32 Oracle ODBC files
\OO4O Oracle Objects for OLE files. \OO4O contains the
following subdirectories:
\CPP ■ Header files, library files, and sample files
\EXCEL ■ Microsoft Excel sample files
\IIS ■ Internet Information Server sample files
\MESG ■ Message files
Directory Contents
\VB ■ Visual Basic sample files
\OPSM Oracle Parallel Server option files
\ORACORE Message files
\ORD Data option files. \ORD contains the following
subdirectories:
\ADMIN ■ SQL scripts
\AUD ■ Oracle interMedia Audio files
\IMG ■ Oracle interMedia Image files
\MESG ■ Message files
\TS ■ Oracle Time Series files
\VID ■ Oracle interMedia Video files
\VIR ■ Oracle Visual Information Retrieval files
\OTRACE Oracle Trace files. \OTRACE contains the following
subdirectories:
\ADMIN ■ Administration files, including SQL scripts
\LIB ■ Library files
\MESG ■ Message files
\PUBLIC ■ Header files
\PLSQL SQL scripts, sample files, and message files for PL/SQL
\PRECOMP Precompiler files. \PRECOMP contains the following
subdirectories:
\ADMIN ■ Configuration files
\DOC ■ Release notes
\MESG ■ Message files
\RDBMS Oracle Server files. \RDBMS contains the following
subdirectories:
Directory Contents
\ADMIN Oracle database SQL scripts (including
CATALOG.SQL and CATPROC.SQL). Use SQL
scripts to create data dictionary tables and views,
and other views used by Oracle software.
Additional Information: See Chapter 5, "SQL
Scripts" in Oracle8 Reference.
\AQ Advanced Queuing sample files
\EXTPROC External procedure sample files
\LOADER SQL*Loader sample files
\MESG Message files
\XA Oracle XA files
\SQLJ Oracle SQLJ Translator files. \SQLJ contains the
following subdirectories:
\DEMO ■ Sample programs
\DOC ■ Release notes, white papers, package descriptions,
the SQLJ specification, and the Oracle SQLJ
Developer’s Guide and Reference
\LIB ■ Class files and a SQL script
\SQLPLUS SQL*Plus files. \SQLPLUS contains the following
subdirectories:
\ADMIN ■ SQL scripts for administering SQL*Plus
\DEMO ■ SQL scripts for sample tables
\DOC ■ Release notes
\MESG ■ Message files
\WMT Oracle Wallet Manager files
ADMIN
Database administration files are stored in subdirectories of ORACLE_
BASE\ADMIN\DB_NAME.
The following table describes these subdirectories.
Directory Contents
\ADHOC Ad hoc SQL scripts
\BDUMP Background process trace files (default location)
\CDUMP Core dump files
\CREATE Database creation files
\EXP Database export files
\PFILE Initialization parameter files
\UDUMP User process trace files (default location)
ORADATA
Database files are stored in ORACLE_BASE\ORADATA\DB_NAME.
The following table describes the database files.
File Description
CONTROL01.CTL Control file 1
CONTROL02.CTL Control file 2
INDX01.DBF INDX tablespace data file
OEMREP01.DBF Repository for Oracle Enterprise Manager
RBS01.DBF RBS tablespace data file
SYSTEM01.DBF SYSTEM tablespace data file
TEMP01.DBF TEMP tablespace data file
USERS01.DBF USERS tablespace data file
REDO01.LOG Redo log file group 1, member 1
REDO02.LOG Redo log file group 2, member 1
REDO03.LOG Redo log file group 3, member 1
File Description
REDO04.LOG Redo log file group 4, member 1
Directory Contents
\A2OWIZ Oracle Migration Assistant for Microsoft Access files
\ASSISTANTS Oracle assistants. \ASSISTANTS contains the
following subdirectories:
\IFA ■ Oracle INTYPE File Assistant files
\JLIB ■ Java files used by the assistants
\OWAST ■ Oracle Web Publishing Assistant files
\BIN Executable files
\DBS Message files and SQL scripts
\DOC HTML documentation library
\JDBC Java Database Connectivity (JDBC) drivers files.
\JDBC contains the following subdirectory:
\ADMIN ■ Class files
\JLIB Java files used by various applications
\NETWORK Net8 files. \NETWORK contains the following
subdirectories:
\ADMIN ■ Configuration files
\DOCS ■ Release notes
\JLIB ■ Java files used by Net8 assistants
\LOG ■ Log files (default location)
Directory Contents
\MESG ■ Message files
\TNSAPI ■ TNS API files
\TOOLS ■ Net8 assistant files
\TRACE ■ Trace files (default location)
\OCI Oracle Call Interface files. \OCI contains the
following subdirectories:
\INCLUDE ■ Header files
\LIB ■ Library files
\SAMPLES ■ Sample files
\OCOMMON NLS files
\ODBORA32 Oracle ODBC files
\OO4O Oracle Objects for OLE files. \OO4O contains the
following subdirectories:
\CPP ■ Header files, library files, and sample files
\EXCEL ■ Microsoft Excel sample files
\IIS ■ Internet Information Server sample files
\MESG ■ Message files
\VB ■ Visual Basic sample files
\ORACORE Message files
\OTRACE Oracle Trace files. \OTRACE contains the following
subdirectories:
\ADMIN ■ Administration files, including SQL scripts
\LIB ■ Library files
\MESG ■ Message files
\PUBLIC ■ Header files
\PLSQL Message files for PL/SQL
\PRECOMP Precompiler files. \PRECOMP contains the following
subdirectories:
\ADMIN ■ Configuration files
Directory Contents
\DOC ■ Release notes
\MESG ■ Message files
\RDBMS Oracle Server files. \RDBMS contains the following
subdirectories:
\ADMIN ■ Administration files
\MESG ■ Message files
\SQLPLUS SQL*Plus files. \SQLPLUS contains the following
subdirectories:
\ADMIN ■ SQL scripts for administering SQL*Plus
\DEMO ■ SQL scripts for sample tables
\DOC ■ Release notes
\MESG ■ Message files
Directory Contents
\ASSISTANTS Oracle assistants. \ASSISTANTS contains the
following subdirectories:
\IFA ■ Oracle INTYPE File Assistant files
\JLIB ■ Java files used by the assistants
\BIN Executable files
\DBS Message files and SQL scripts
\DOC HTML documentation library
\JDBC Java Database Connectivity (JDBC) drivers files.
\JDBC contains the following subdirectory:
\ADMIN ■ Class files
\JLIB Java files used by various applications
\NETWORK Net8 files. \NETWORK contains the following
subdirectories:
\ADMIN ■ Configuration files
\DOCS ■ Release notes
\JLIB ■ Java files used by Net8 assistants
\LOG ■ Log files (default location)
\MESG ■ Message files
\TNSAPI ■ TNS API files
\TOOLS ■ Net8 assistant files
\TRACE ■ Trace files (default location)
\OCI Oracle Call Interface files. \OCI contains the
following subdirectories:
Directory Contents
\INCLUDE ■ Header files
\LIB ■ Library files
\SAMPLES ■ Sample files
\OCOMMON NLS files
\ODBORA32 Oracle ODBC files
\OO4O Oracle Objects for OLE files. \OO4O contains the
following subdirectories:
\CPP ■ Header files, library files, and sample files
\EXCEL ■ Microsoft Excel sample files
\IIS ■ Internet Information Server sample files
\MESG ■ Message files
\VB ■ Visual Basic sample files
\ORACORE Message files
\OTRACE Oracle Trace files. \OTRACE contains the following
subdirectories:
\ADMIN ■ Administration files, including SQL scripts
\LIB ■ Library files
\MESG ■ Message files
\PUBLIC ■ Header files
\PLSQL Message files for PL/SQL
\PRECOMP Precompiler files. \PRECOMP contains the following
subdirectories:
\ADMIN ■ Configuration files
\DEMO ■ Sample programs
\DOC ■ Release notes
\LIB ■ Library files
\MESG ■ Message files
\PUBLIC ■ Header files
Directory Contents
\RDBMS Oracle Server files. \RDBMS contains the following
subdirectories:
\ADMIN ■ Administration files
\MESG ■ Message files
\SQLPLUS SQL*Plus files. \SQLPLUS contains the following
subdirectories:
\ADMIN ■ SQL scripts for administering SQL*Plus
\DEMO ■ SQL scripts for sample tables
\DOC ■ Release notes
\MESG ■ Message files
Sample File
A sample file called INITSMPL.ORA is located in the ORACLE_HOME
\DATABASE directory.
If you want to use the sample INITSMPL.ORA file as part of database creation:
1. Rename the file INIT.ORA.
2. Edit this file to reflect the correct location of your database files and the name of
your database.
If you installed a starter database, the initialization parameter file INIT.ORA used
by the starter database is located in ORACLE_BASE\ADMIN\DB_NAME\PFILE.
You can use either INITSMPL.ORA or the starter database INIT.ORA as a basis for
creating a new Oracle8 database initialization parameter file.
The annotated, sample initialization parameter file contains alternative values for
the initialization parameters. These values and the annotations are preceded by
comment signs (#), which prevent them from being processed. To activate a
particular parameter, remove the preceding # sign. When you no longer want to use
a particular parameter, edit the initialization parameter file to add a comment sign.
For example, several initialization parameters are specified with three different
values to create small, medium, or large System Global Areas (SGAs), respectively.
The parameter that creates a small SGA is active in the following example:
db_block_buffers = 200 # SMALL
# db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
To create a medium-sized SGA, comment out the small parameter definition and
activate the medium parameter definition. Edit the initialization parameter file as
follows:
# db_block_buffers = 200 # SMALL
db_block_buffers = 550 # MEDIUM
# db_block_buffers = 3200 # LARGE
Initialization Parameters
Oracle8i Reference includes descriptions of all initialization parameters and
instructions for setting and displaying their values. The following table describes
initialization parameters and default values for Oracle8i Enterprise Edition for
Windows NT.
Initialization Parameter Name Default Value Range of Values
COMMIT_POINT_STRENGTH 1 0 - 255
JOB_QUEUE_INTERVAL 60 1 - 3600
JOB_QUEUE_PROCESSES 2 0 - 36
MAX_DUMP_FILE_SIZE 10240 0 to 5 MB
OPEN_CURSORS 50 1 - Unlimited
OPEN_LINKS 4 0 - 255
PROCESSES 59 6 - Unlimited
TRANSACTIONS_PER_ROLLBACK_SEGMENT 5 1 - 255
Parameter Description
COMPATIBLE_NO_RECOVERY Uses default value set in Oracle8i kernel (no Windows NT-specific value).
CPU_COUNT Oracle8i automatically sets value to number of CPUs available for your
Oracle instance.
LOG_BUFFER Starter database uses value set in Oracle8i kernel (no Windows NT-specific
value). The Custom option of the Oracle Database Assistant enables you to
customize the value for this parameter.
ORACLE_TRACE_COLLECTION_PATH Uses default value set in Oracle8i kernel (no Windows NT-specific value)
ORACLE_TRACE_FACILITY_NAME Uses default value set in Oracle8i kernel (no Windows NT-specific value)
ORACLE_TRACE_FACILITY_PATH Uses default value set in Oracle8i kernel (no Windows NT-specific value)
SPIN_COUNT Uses default value set in Oracle8i kernel (no Windows NT-specific value)
Parameter Description
Type Size
Maximum block size 16,384 bytes or 16 kilobytes (KB)
Maximum blocks per file 4,194,304 blocks (4 million blocks)
Maximum possible file size with 16 K 64 Gigabytes (GB)
sized blocks (4,194,304 * 16,384) = 64 gigabytes (GB)
Maximum number of files per
database (depends on block size):
2 K sized blocks 20,000 files
4 K sized blocks 40,000 files
8 K sized blocks 65,536 files
16 K sized blocks 65,536 files
Maximum file size for a FAT file 4 GB
Maximum file size in NTFS 16 Exabytes (EB)
Maximum database size 65,536 * 64 GB equals approximately 4 Petabytes
(PB)
Shadow Process Memory:
Release 8.1.3 265 K
Release 8.0.5 233 K
Release 8.0.4 254 K
Type Size
Fixed header size 113 bytes
Variable transaction header 24*INITRANS value for the index
Entry header 5 bytes
This appendix describes use of the registry for various Oracle8i Enterprise Edition
components. It also lists the recommended values and ranges for configuration
parameters.
Specific topics discussed:
■ About Configuration Parameters
■ Registry Overview
■ Registry Parameters
■ Modifying a Registry Value with REGEDT32
■ Adding a Registry Parameter with REGEDT32
■ Adding and Modifying Oracle Home Parameters
■ Modifying Oracle for Windows NT Performance Monitor Parameters
Registry Overview
Oracle8i Enterprise Edition stores its configuration information in a database (the
registry) that is organized in a tree format. The tree format consists of keys in the
registry and parameter values for the keys. Keys and parameter values can be
viewed and modified in the Registry Editor.
Keys are folders that appear in the left pane of a Registry Editor window. A key
contains subkeys or parameters.
Registry Parameters
This section describes the Oracle8i Enterprise Edition registry parameters for the
following keys. Other products, such as Oracle Enterprise Manager, have additional
keys and parameters not described in this appendix.
■ HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID
■ HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE
■ HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ALL_HOMES
■ HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
To modify the registry values described below, see "Modifying a Registry Value
with REGEDT32" on page C-12.
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID
Each time you install Oracle products into a new Oracle home on your computer,
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID is created and
HOMEID is incremented. This subkey contains parameter values for most Oracle
products.
This figure shows the parameter subkeys created with two Oracle home directories
on the same computer.
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE
This subkey contains the following parameters:
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ALL_HOMES
This subkey provides general information on each Oracle home directory on a
computer.
This subkey contains the IDx subkey(s) and its parameters, described below, as well
as other parameters listed on page C-9.
IDx
This subkey corresponds to the HOMEID of the same number (for example,
HOME0 for the first installation, HOME1 for the second installation, and so on). IDx
contains the following parameters. The values that display are determined by what
you enter during installation in the File Locations dialog box of Oracle Universal
Installer.
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\ALL_HOMES Parameters
This subkey contains the following parameters.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services
This subkey contains the following:
■ Parameters for Oracle for Windows NT Performance Monitor
■ Parameters for Oracle Services
For Oracle for Windows NT Performance Monitor to display information for Oracle
performance objects, it must log onto the database. Modify the following
parameters if the default information is not applicable or if you want to access
another database:
The following parameters specify the Oracle for Windows NT Performance Monitor
log file and object configuration files.
4. In the Value Name text box, type the name that you want to assign to the
currently selected key.
5. In the Data Type list, select the value class that you want to assign to the added
value:
■ REG_SZ, REG_EXPAND_SZ (for an expandable string), or REG_MULTI_SZ
(for multiple strings) for a data string
■ Binary value with a REG_DWORD prefix to identify a value entry as a
DWORD (hexadecimal data) entry
6. Click OK.
A String Editor dialog box appropriate for the data type appears:
Using OPERFCFG
OPERFCFG is an Oracle tool that you run from the MS-DOS command prompt.
This table describes OPERFCFG command line syntax and provides examples of its
use.
The -U, -P, and -D commands are all optional.
Use this syntax: OPERFCFG [-U USERNAME] [-P PASSWORD] [-D DATABASE_NAME]
Syntax description: ■ -U USERNAME Username registry parameter value that Oracle for
Windows NT Performance Monitor uses to log into
the database. You must have DBA privileges on this
database.
■ -P PASSWORD Password registry parameter value for the user name.
■ -D DATABASE_NAME Net service name that Oracle for Windows NT
Performance Monitor uses to connect to the database.
Affects the Hostname registry parameter. The net
service name corresponds to the SID of the database
that you want to monitor. The -D command can be
specified without providing a database name value.
Example 1 C:\> OPERFCFG -U DBA_ADMIN -P FRANK
Changing the Username This changes the user name to DBA_ADMIN and the password to FRANK and
and Password leaves the database name at its current value.
Example 2 C:\> OPERFCFG -U DBA_ADMIN -P FRANK -D PROD
Changing the Username, This changes the username to DBA_ADMIN, the password to FRANK, and the
Password, and Database database name to PROD.
Name
Example 3 C:\> OPERFCFG -P FRANK
Changing the Password This changes the password to FRANK for the current user name and database
name.
Net8 Parameters
The location of the Oracle Net8 directory is
KEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID
where ID is incremented for each additional Oracle home directory on your computer (for
example, HOME0 is for a first directory, HOME1 is for a second directory, and so forth).
Parameter Description
DisplayName Specifies the service name.
ImagePath Specifies the fully qualified path name of the
executable invoked by the service and any
command line arguments passed to the executable
at runtime.
ObjectName Specifies the logon user account and computer to
which the service should log on.
LOCAL
You can add the LOCAL parameter to make a connection without specifying a
connect string service name. The value for LOCAL is the service name in the
TNSNAMES.ORA file located in the ORACLE_HOME\NETWORK\ADMIN directory.
For example, if the LOCAL parameter is specified as finance, you connect to a
database from Server Manager with the following command:
SVRMGRL> CONNECT SCOTT/TIGER
Net8 checks if LOCAL is defined as an environment variable or as a parameter in the
registry, and uses finance as the service name. If it exists, Net8 connects.
TNS_ADMIN
You can add the TNS_ADMIN parameter to change the directory name for
configuration files from the default location. For example, if you set TNS_ADMIN to
ORACLE_HOME\TEST\ADMIN, the configuration files are used from ORACLE_
HOME\TEST\ADMIN.
USE_SHARED_SOCKET
You can set the USE_SHARED_SOCKET parameter to TRUE to enable the use of
shared sockets. If this parameter is set to TRUE, the network listener passes the
socket descriptor for client connections to the database thread. As a result, the client
does not need to establish a new connection to the database thread and database
connection time improves. Also, all database connections share the port number
used by the network listener, which can be useful if you are setting up third-party
proxy servers.
On Windows NT 4.0 Service Pack3 or earlier, enabling this option precludes
bringing the network listener up or down in a case where a database connection
spawned by the network listener is active. Therefore, you may need to shut down
all of the databases serviced by a network listener before you can bring down and
restart a network listener. This results from the way shared sockets have been
implemented in WINSOCK2. WINSOCK2 does not allow a reliable thread to a
network listener on any port on which other connections are also active. This is not
an issue on Windows NT 4.0 Service Pack 4 or later. Oracle recommends that you
upgrade to Windows NT 4.0 Service Pack 4 if you intend to set this parameter.
This parameter only works in dedicated server mode in a TCP/IP environment. If
this parameter is set, you cannot use the 8.1.5 listener to spawn Oracle 7.x
databases. To spawn an Oracle 8.0.x database from an 8.1.5 listener with the shared
socket enabled, you must also set the variable USE_SHARED_SOCKET for the 8.0.x
Oracle home.
NDS Authentication
The automatically installed Netware Directory Service (NDS) authentication
method allows client applications and users to access a NetWare server running
Oracle through NDS. Following NDS authentication, a user logged into an NDS
directory tree can use an Oracle database on a NetWare server in the same tree. This
avoids the user having to enter an additional user name and password.
Note
If you also use NDS External Naming, you can view the entire network under a
single NDS directory tree.
Additional Information:
■ Novell NetWare documentation for more information about
NDS
■ Oracle NetWare documentation
SQLNET.AUTHENTICATION_SERVICES = (NDS)
Configuring a Client
To configure a client:
1. Install and configure the Net8 on a client.
2. Add the following entry to the SQLNET.ORA file:
SQLNET.AUTHENTICATION_SERVICES = (NDS)
The NDS Native Naming Adapter for Windows NT and Windows 95/98 clients
uses the NDS naming environment to store service names and addresses of Oracle8
NetWare Servers. This lets an NDS user view the entire network under a single NDS
directory tree. You can use native name services in addition to, or instead of, Oracle
Names or the TNSNAMES.ORA file.
If the NDS Authentication Adapter is used as well, a single log on can access a
multi-server and multi-database network.
Client Configuration
To configure the client:
1. Install and configure the NDS Native Naming Adapter and Net8 on your client.
2. When you configure the NDS Native Naming Adapter, add NOVELL to the
NAMES.DIRECTORY_PATH parameter in the SQLNET.ORA file:
NAMES.DIRECTORY_PATH = (NOVELL, TNSNAMES, ONAMES)
Client Connection
To connect from a client with the NDS Native Naming Adapter:
Enter the following command to access an Oracle8 database for NetWare database:
SVRMGR30
SVRMGR> CONNECT USERNAME/PASSWORD@DATABASE_OBJECT_NAME
where DATABASE_OBJECT_NAME identifies the Oracle8 database in NDS.
Services
LSNRCTL START LSNR 4. In the Services window, click The Services confirmation
the Close button. dialog box appears and
prompts you as to whether or
not it is OK to stop the
service.
4. Click Yes to acknowledge the
message, and click Close to
exit the Services window.
NLS_LANG Parameters
Oracle8i Enterprise Edition provides NLS that enables users to interact with a
database in their own language defined by the NLS_LANG parameter. When you
install Oracle8i Enterprise Edition, the NLS_LANG parameter is registered by the
Net8 Client installation script.
The default value of the NLS_LANG parameter at installation is either that of the
existing NLS_LANG parameter of the currently selected Oracle home, or of the
default language of the operating system.The default language and NLS_LANG
value mappings are listed under "Commonly Used Values for NLS_LANG" below.
The NLS_LANG parameter is stored in the registry under the HKEY_LOCAL_
MACHINE\SOFTWARE\ORACLE\HOMEID\NLS_LANG subkey, where ID is
the unique number identifying the Oracle home. See Appendix C, "Oracle 8i
Configuration Parameters and the Registry" for more information on the subkey
locations for multiple Oracle homes.
The NLS_LANG parameter uses the following format:
NLS_LANG = LANGUAGE_TERRITORY.CHARACTER_SET
where:
This appendix describes how to configure your system to store data files for
tablespaces on raw partitions.
Specific topics discussed:
■ Raw Partition Overview
■ Creating an Extended Partition
■ Creating a Tablespace in a Raw Partition
primary partition
2 extended
partitions,
1 per disk
Disk Definition
Windows NT defines each disk drive found at startup with the following naming
convention:
\Device\Harddiskm\Partitionn
where Harddiskm is the number of the physical drive, and Partitionn is a logical
partition number, as shown in the Disk Administrator window (in the above figure).
Harddiskm starts at 0, and Partitionn starts at 1.
Partition0 has a special meaning in that it has access to the whole disk. For example,
the first logical partition (E:) on the second physical drive in the above figure has
the following entry:
\Device\Harddisk1\Partition1
The first logical partition on a system (normally the C drive) has the following
entry:
\Device\Harddisk0\Partition1
Physical Disk
A physical disk represents the entire disk and points to
\Device\Harddiskx\Partition0.
Windows NT automatically creates a symbolic link name of \\.\PhysicalDrivex,
where x is the number corresponding to your hard disk drive number in the Disk
Administrator. The x matches the x in \Device\Harddiskx\Partition0.
\\.\PhysicalDrivex is automatically defined by Windows NT for every hard disk in
the machine. For example, a machine with three hard disks:
\\.\PhysicalDrive0
\\.\PhysicalDrive1
\\.\PhysicalDrive2
Internally, these names expand to
\\.\PhysicalDrive0 = \Device\Harddisk0\Partition0
\\.\PhysicalDrive1 =\Device\Harddisk1\Partition0
\\.\PhysicalDrive2 =\Device\Harddisk2\Partition0
Partition0 is special, because it represents the entire physical disk regardless of any
partitioning scheme on that disk. On all disks recognized by Windows NT, the Disk
Administrator writes a signature on the first block of all disks. To avoid overwriting
that block, Oracle skips the first block of a physical raw partition that is used for an
Oracle data file.
Logical Partition
A logical partition is a partition created by the Disk Administrator that points to a
drive other than \Device\Harddiskx\Partition0.
Logical partitions are initially assigned names with drive letters (\\.\DRIVE_
LETTER:) and typically re-assigned symbolic link names (\\.\SYMBOLIC LINK
NAME). For example, \\.\D: may be assigned a symbolic link name of
\\.\ACCOUNTING_1. Regardless of whether a drive letter or symbolic link name
is used, logical partitions are defined to represent a specific partition in a disk rather
than the entire disk. Internally, these names may expand to:
\\.\D:= \Device\Harddisk2\Partition1
\\.\ACCOUNTING_1= \Device\Harddisk3\Partition2
Drive letters can be assigned to specific partitions, using the Disk Administrator.
Symbolic link names can, on the other hand, be assigned using a utility such as
DOSDEV.EXE, which is available with the Windows NT Resource Kit, or the
SETLINKS utility.
Note: Oracle does not skip the first block of a logical raw partition
used for an Oracle data file.
Answer: The Oracle database handles the data file using the physical disk
convention even though it really is a logical partition. This will not cause any
data corruption or loss as long as you continue to use the physical disk naming
conventions. Oracle Corporation recommends that you convert to the logical
partition at your earliest convenience. See "Compatibility Issues" on page F-6.
Question: What is the impact if I have created logical names representing Partition0?
For example:
\\.\ACCOUNTING_1 = \Device\Harddisk1\Partition0
Answer: This poses severe problems, because the Disk Administrator typically
writes a signature into the first block of every disk, and consequently may
overwrite a portion of the data file header.
This can also cause data loss. Never use Partition0 with the logical partition
convention. See "Compatibility Issues" below for information on rebuilding
your Oracle database with the proper conventions.
Question: How do I transfer the contents of any raw partition to a standard file system
for backup purposes?
Answer: Use the Oracle-provided OCOPY tool to copy data to/from a raw
partition for both physical and logical raw conventions. See "Compatibility
Issues" below for further information.
Compatibility Issues
The physical and logical partition conventions are not compatible with one another
because of the extra block that is skipped for physical raw conventions. This also
means you cannot simply do an OCOPY from a physical disk to a logical partition,
because the contents of these partitions are incompatible.
To convert from a physical convention to a logical convention, you must:
1. Perform a full database export to a (local) file system.
2. Create logical partitions and define logical names for these partitions.
3. Re-create the database by using the new logical partitions.
4. Perform the full database import to the newly created database.
If your database installation uses physical disk conventions with logical partitions,
Oracle Corporation recommends converting to the logical partition conventions at
your earliest convenience, using the preceding steps.
Note that the lines display diagonally from top right to the bottom left,
indicating unpartitioned devices.
2. Select an area of free space in an extended partition on a disk that is on the
shared disk subsystem by clicking the mouse.
Oracle Corporation recommends that you use the entire disk.
3. Choose Create Extended... from the Partition menu.
Disk Administrator displays the minimum and maximum sizes for the
extended partition:
Note: Changes that you have made are not saved until you choose
Commit Changes Now from the Partition menu or quit Disk
Administrator.
The Disk Administrator window displays the minimum and maximum sizes for
the logical partition:
3. Enter the size of the logical partition for the data file, then click OK.
The size depends on how large you want your data files to be. Add 2MB to this
size for overhead.
4. Repeat Steps 1-3 for each additional data file that you plan to store in a raw
partition.
5. Choose Commit Changes Now from the Partition menu.
A confirmation dialog appears, informing you that changes have been made to
the disk.
6. Click Yes.
A dialog box appears, informing you that the disks have been updated
successfully.
7. Click OK.
8. Write down the hard disk number(s) and the number of the partition (starting
at 1) for that drive. Oracle Corporation recommends using a worksheet similar
to the one below.
partition number
ACCOUNTING_1 \Device\Harddisk1\Partition1
ACCOUNTING_2 \Device\Harddisk1\Partition2
ACCOUNTING_1
ACCOUNTING_2 \Device\Harddisk1\Partition2
This removes the ACCOUNTING_1 link and creates the other links specified.
To ignore links:
■ Insert a "#" at the beginning of a line to denote a comment, which is ignored by
SETLINKS.
This appendix describes how to use Oracle SNMP Agent in Net8 for Windows NT
and Windows 95/98.
Specific topics discussed:
■ What Is the Purpose of SNMP?
■ Oracle SNMP Support
■ Oracle SNMP Agent for Oracle Services
■ Configuring Oracle SNMP Agent
■ Controlling the Master Agent and the Encapsulator
■ Understanding the MASTER.CFG File
■ Understanding the ENCAPS.CFG File
Note: Oracle Corporation recommends the use port 161 for Ora-
cleSNMPPeerMasterAgent since it is the default port for SNMP
communication. However, you may specify a different port as long
as the management application on your NMS can be configured to
send SNMP requests to the master agent listening on this port.:
3. Specify an unused port where the encapsulated agent, Microsoft SNMP Service,
should be listening.
The port is specified in SERVICES file located at NT_
HOME\SYSTEM32\DRIVERS\ETC.
For example, make sure you have the following line in the file:
snmp 1161/udp snmp
Note: If there has already been an entry for SNMP in the file,
change the port from 161 (default number) to something else that
is available (1161 in this example).
1.3.6.1.2.1.1,
1.3.6.1.2.1.2,
1.3.6.1.2.1.3,
1.3.6.1.2.1.4,
1.3.6.1.2.1.5,
1.3.6.1.2.1.6,
1.3.6.1.2.1.7,
1.3.6.1.2.1.8,
1.3.6.1.2.1.77
Note: The port (1161 in this example) must match the one you
specified in Step 3.
- time-out Incompatible
Master Agent - Encapsulator Master Agent
- traps
Master Agent host
Encapsulator Configuration -
There are six command line options as shown below. The options are:
-T PORT Specifies the incoming trap port where the encapsulator listens to
receive SNMP traps sent by encapsulated master agents.
Default: no traps forwarded
-S PORT Specifies the port from which the encapsulator sends SNMP requests
to encapsulated agents, and to which the encapsulated agents send
their responses.
Default: assigned by the host
-H HOST Specifies the master agent’s host address, that is, the host where the
master agent resides. This may or may not be the host of the
encapsulated agent, specified in the ENCAPS.CFG file.
Default: localhost
-P PORT Specifies the master agent’s listening SMUX port, that is, the port to
which the encapsulator sends its SMUX traffic.
Default: 199
-W WAIT Specifies the SNMP response time-out (in seconds) from the
encapsulated master agent.
Default: 2 s
-C FILE Specifies the encapsulator’s configuration file. This file is defaulted
to ENCAPS.CFG.
TRANSPORT Defines an interface over which the master agent listens for SMUX
connections from subagents or SNMP requests.
COMMUNITY Provides a form of authentication for access to information.
Note: This parameter is not the same as the COMMUNITY
parameter in the TNSNAMES.ORA file.
1.3.6.1.2.1.1,
1.3.6.1.2.1.2,
1.3.6.1.2.1.3,
1.3.6.1.2.1.4,
1.3.6.1.2.1.5,
1.3.6.1.2.1.6,
1.3.6.1.2.1.7,
1.3.6.1.2.1.8,
1.3.6.1.4.1.77
alert file
A file that contains important information about error messages and exceptions that
occur during database operations.
authenticate
To verify the identity of a user, device, or other entity in a computer system, often as
a prerequisite for allowing access to resources in a system.
authorization
Permission given to a user, program, or process to access an Oracle database.
backup
A representative copy of data. This copy includes important parts of your database
such as the control file, redo log files, and data files.
A backup is a safeguard against unexpected data loss; if you lose your original data,
you can use the backup to make the data available again. A backup is also a
safeguard against an application error; if an application makes incorrect changes,
you can restore the backup.
connect string
See "net service name".
control file
A file that records the physical structure of a database and contains the database
name, the names and locations of associated databases and online redo log files, the
timestamp of the database creation, the current log sequence number, and
checkpoint information.
Glossary-1
Common Object Request Broker Architecture (CORBA)
A standard that enables distributed objects to communicate with each other,
independent of programming language, operating system, and location.
data dictionary
A set of read-only tables that provide information about a database.
database alias
See "net service name".
downgrade
To transform an installed version of an Oracle database from a later release back
into an earlier release.
Enterprise JavaBeans
A server-side component model for Java.
external procedure
A function written in a third-generation language (3GL), such as C, and callable
from within PL/SQL or SQL as if it were a PL/SQL function or procedure.
HOMEID
Represents a unique registry subkey for each Oracle home directory in which you
install products. A new HOMEID is created and incremented each time you install
products to a different Oracle home directory on one computer. Each HOMEID
contains its own configuration parameter settings for installed Oracle products.
HOME_NAME
Represents the name of an Oracle home. In release 8.1.5, all Oracle homes have a
unique HOME_NAME.
Glossary-2
instance
Every running Oracle database is associated with an Oracle instance. When a
database is started on a database server (regardless of the type of computer), Oracle
allocates a memory area called the System Global Area (SGA) and starts one or
more Oracle processes. This combination of the SGA and the Oracle processes is
called an instance. The memory and processes of an instance manage the associated
database’s data efficiently and serve the one or more users of the database.
instantiate, instantiation
Producing a more defined version of some object by replacing variables with values
(or other variables).
In object-oriented programming, producing a particular object from its class
template. This involves allocation of a structure with the types specified by the
template, and initialization of instance variables with either default values or those
provided by the constructor function of the class.
listener
The server process that listens for and accepts incoming connection requests from
client applications. Oracle listener processes start up Oracle database processes to
handle subsequent communications with the client.
LISTENER.ORA
A configuration file that describes one or more Transparent Network Substrate
(TNS) listeners on a server.
Glossary-3
migrate
To transform an installed version of an Oracle database into a later version. The
term is also used in this guide to refer to the transformation of a Microsoft Access
database to an Oracle database. Compare with "upgrade".
mount
To associate an instance with a database that has been started.
Net8
The Oracle network interface that enables Oracle tools running on network
workstations and servers to access, modify, share, and store data on other servers.
network listener
A listener on a server that listens for connection requests for one or more databases
on one or more protocols. See "listener".
network service
In an Oracle application network, a service performs tasks for its service consumers.
For example, a Names Server provides name resolution services for clients.
NLS
See "National Language Support (NLS)".
Glossary-4
Object Request Broker (ORB)
A software component that serves as the middleware between distributed objects.
The distributed objects must comply with the Common Object Request Broker
Architecture (CORBA) standard.
Oracle home
Corresponds to the environment in which Oracle products run. This environment
includes the location of installed product files, the PATH variable pointing to the
products’ binary files, registry entries, net service names, and program groups.
If you install an OFA-compliant database, using Oracle Universal Installer defaults,
Oracle home (known as \ORACLE_HOME in this guide) is located beneath
X:\ORACLE_BASE. It contains subdirectories for Oracle software executables and
network files. If you install Oracle8i Enterprise Edition on a clean computer and use
the default settings, the first Oracle home directory you create is called \ORA81.
Oracle service
A service that is associated with an Oracle database.
ORACLE_BASE
Oracle base, known as ORACLE_BASE in this guide, is the root of the Oracle
directory tree.
If you install an OFA-compliant database using Oracle Universal Installer defaults,
ORACLE_BASE is X:\ORACLE where X is any hard drive (for example,
C:\ORACLE).
Glossary-5
PL/SQL
Oracle Corporation’s procedural language extension to SQL.
PL/SQL enables you to mix SQL statements with procedural constructs. You can
define and execute PL/SQL program units such as procedures, functions, and
packages.
precompiler
A programming tool that enables you to embed SQL statements in a high-level
source program.
privilege
A right to execute a particular type of SQL statement or to access another user’s
object.
process
A "thread of control" or a mechanism in an operating system that can execute a
series of steps. (Some operating systems use the terms job or task.) A process
normally has its own private memory area in which it runs.
quota
A limit on a resource, such as a limit on the amount of database storage used by a
database user. A database administrator can set tablespace quotas for each Oracle
user name.
raw partition
A portion of a physical disk that is accessed at the lowest possible level.
recovery
To restore a physical backup is to reconstruct it and make it available to the Oracle
server. To recover a restored backup is to update it using redo records (that is,
records of changes made to the database after the backup was taken). Recovering a
backup involves two distinct operations: rolling forward the backup to a more
current time by applying redo data, and rolling back all changes made in
uncommitted transactions to their original state.
Glossary-6
redo log buffer
A circular buffer in the System Global Area (SGA) that contains information about
changes made to the database.
registry
A Windows repository that stores configuration information for a computer.
remote computer
A computer on a network other than the local computer.
remote database
A database on a computer other than the local database. The computer is usually on
the same network, but on a different node.
replication
The process of copying and maintaining database objects in multiple databases that
make up a distributed database system.
role
A named group of related privileges. You can grant a role to users or other roles.
schema
A named collection of objects, such as tables, views, clusters, procedures, and
packages, associated with a particular user.
service
An executable process installed in the Windows NT registry and administered by
Windows NT. Once a service is created and started, it can run even when no user is
logged on to the computer.
service name
See "net service name".
SID
See "system identifier (SID)".
snap-in
An administrative tool that runs within Microsoft Management Console.
Glossary-7
snapshot
(1) Information stored in rollback segments to provide transaction recovery and
read consistency. Rollback segment information can be used to recreate a snapshot
of a row before an update.
(2) A read-only copy of a master table located on a remote node. Snapshots can be
queried, but not updated; only the master table can be updated. Snapshots are
periodically refreshed to reflect changes made to the master table.
starter database
A preconfigured, ready-to-use database that requires minimal user input to create.
synonym
An alias for a table, view, sequence, or program unit. A synonym is not actually an
object itself; rather, it is a direct reference to its base object.
SYSDBA
A special database administration role that contains all system privileges with the
ADMIN OPTION, and the SYSOPER system privilege. SYSDBA also permits
CREATE DATABASE actions and time-based recovery.
SYSOPER
A special database administration role that permits a database administrator to
perform STARTUP, SHUTDOWN, ALTER DATABASE OPEN/MOUNT, ALTER
DATABASE BACKUP, ARCHIVE LOG, and RECOVER, and includes the
RESTRICTED SESSION privilege.
Glossary-8
MANAGER. The SYSTEM user name is the preferred user name for DBAs to use for
database maintenance.
tablespace
A database is divided into one or more logical storage units called tablespaces.
Tablespaces are divided into logical units of storage called segments, which are
further divided into extents.
thread
A path of execution within a process.
TNSNAMES.ORA
A file that contains connect descriptors mapped to net service names. The file may
be maintained centrally or locally, for use by all or individual clients.
trace file
Each server and background process can write to an associated trace file. When a
process detects an internal error, it dumps information about the error to its trace
file. Some of the information written to a trace file is intended for the database
administrator, while other information is intended for Oracle Support Services.
Trace file information is also used to tune applications and instances.
upgrade
To transform an installed version of an Oracle database release into another release
of the same version. Compare with "migrate".
user name
A name that can connect to and access objects in a database.
view
A tailored presentation of the data in one or more tables (or other views).
Glossary-9
Glossary-10
Index
Symbols using, 11-14
alert view, 11-5
"", SQL*Loader parameter, 3-19 ALL_HOMES, registry subkey for multiple Oracle
"FIX n", SQL*Loader parameter, 3-19
homes, C-8
"VAR xxxx", SQL*Loader parameter, 3-19
ALTER DATABASE ARCHIVELOG command, 9-
\\.\PhysicalDrivex, F-4 24
ALTER DATABASE CONVERT command, 5-40
Numerics ALTER DATABASE OPEN RESETLOGS
command, 5-41
1521 port, D-13
ALTER PACKAGE command, 6-25
1526 port, D-13
APPC architecture, 2-15, 2-28, 2-36
1575 port, D-13
ARCHIVE LOG LIST command, 9-23
1610 port, D-13
ARCHIVELOG mode, 7-5, 9-23
1620 port, D-13
archiving mode, 7-5
4GB RAM Tuning, 2-3
custom database, 9-23
starter database, 9-23
A archiving procedures, 9-25
adapters for redo log files, 9-23
supported vendors, 2-41 specifying an archive destination, 9-25
ADMIN directory, explained, 4-21 UNC not allowed, 7-16, 8-3
Adobe Acrobat Reader, starting, 1-9 assistant common files, 2-11, 2-25, 2-34
Advanced Program-to-Program Communication assistants
(APPC), 2-15, 2-28, 2-36 operating system compatibility, 3-4
Advanced Replication support, 7-6 Oracle Data Migration Assistant, 2-20
additional documentation, 6-26 Oracle Database Configuration Assistant, 2-20,
configuration requirements, 6-3 2-23, 2-31
configuration tasks, 6-24 Oracle Web Publishing Assistant, 2-23, 2-32
creating a SPOOL file, 6-25, 6-26 starting, 3-17
data dictionary ATTRIB command, 3-10
tables, 6-26 audit trail
initialization parameter requirements, 6-24 managing, 11-14
tablespace requirements, 6-23, 6-26 operating system, 3-23
alert files, 11-14 AUDIT_FILE_DEST parameter, 11-14
for monitoring a database, 11-2 AUDIT_TRAIL parameter, 11-12
auditing, 11-12
Index-1
authentication browsers
automatically enabling during installation, 10-3 Java-enabled, 1-8
connecting as INTERNAL without a Microsoft Internet Explorer, 1-8
password, 10-35 Netscape Navigator, 1-8
connecting as SYSOPER or SYSDBA without a BUILD_DB.SQL script, 8-10, 8-17
password, 10-30 location of, 8-4
connecting without a password as a BUILDALL.SQL script, 8-17
nonprivileged database user, 10-25
creating an operating system-authenticated
C
user, 10-27
granting database roles through Windows C:\>, defined, xxvii
NT, 10-40 C:\ORACLE, defined, 4-16
of DBA users, 2-6 C:\ORANT, defined, xxviii, 4-16
overview, 10-2 C:\ORAWIN, defined, xxviii
setting OS_AUTHENT_PREFIX, 10-26 C:\ORAWIN95, defined, xxviii
SQLNET.ORA file, 10-2 cartridges, 7-6
using a password file, 9-17 CAT8004.SQL, 5-47
using Windows NT Native authentication CATALOG.SQL script, 5-53, 8-21
methods, 10-2 location of, A-6
Authentication Adapters CATEXP.SQL script
using, D-5 location of, A-6
auto-starting CATNSNMP.SQL, capabilities, 7-9
Oracle Services, 9-8 CATOUT.LOG file, 5-41
CATPARR.SQL, 5-42
CATPROC.SQL script, 5-53, 8-21
B location of, A-6
BACKGROUND_DUMP_DEST parameter, 8-16 CATREP.SQL, 5-42, 6-25, 8-22
using with trace files, 11-14 chart view, 11-5
backslash (\), defined, xxvii Choose Start >, defined, xxvii
backup code conventions, used in this guide, xxvii
databases, 8-25 cold backups, performing, 12-3
OCOPY file types, 12-4 COMDEMO user name, 7-10
stopping services to perform cold backups, 12-3 database roles, 7-10
backup and recovery tools password, 7-10
Backup Manager, 12-2 COMMIT_POINT_ STRENGTH parameter, B-4
OCOPY, 12-3 Common Object Request Broker Architecture. See
Recovery Manager (RMAN.EXE), 12-3 CORBA
selecting, 12-2 COMPATIBLE parameter, 5-40, 5-49, 5-54, B-4
third-party backup and recovery vendors, 12-3 configuration files
Backup Manager TNSNAMES.ORA
capabilities, 12-2 ENCAPS.CFG, G-10
Bequeath MASTER.CFG, G-9
defined, 2-14, 2-28 configuration parameter
block size, maximum, B-8 NAMES.DIRECTORY_PATH, D-7
blocks per file, maximum, B-8 configuration parameters
Index-2
defined, C-2 LOCAL parameter, D-3
LOCAL, D-3 Oracle7 connections to Oracle8 databases, 5-9
registry, C-1 Oracle8 Client r. 8.0/SQL*Net to Oracle8
REMOTE, D-4 database r. 8.1, 5-9
SQLNET.AUTHENTICATION_SERVICES, D-6 Oracle8 Client r. 8.1 to Oracle database v. 7 and r.
TNS_ADMIN, D-4 8.0, 5-11
USE_SHARED_SOCKET, D-4 Oracle8 Client r. 8.1 to Oracle8 database r.
configuration requirements 8.1, 5-8
Advanced Replication support, 6-3 to a database, 9-10, 9-23
for Oracle products, 6-2 with NDS Native Naming Adapter, D-7
multi-threaded external callouts, 6-3 Connecting to the database from a remote
multi-threaded server, 6-3 machine, 7-11
Net8, 6-2 contact information
Oracle Spatial cartridge, 6-2 documentation sales, 1-2
Oracle Time Series cartridge, 6-2 Legato, 2-11, 2-25
Oracle Visual Information Retrieval control files
cartridge, 6-2 additional backslashes in r. 8.0.4, 7-16, 8-3
PL/SQL external procedures, 6-3 description, 7-14
configuration responsibilities starter database, 7-14
Oracle Audio Data cartridge, 6-4 Control Panel
Oracle ConText cartridge, 6-7 defined, 3-21
Oracle Spatial cartridge, 6-11 integration with Oracle8 database, 9-3
Oracle Time Series cartridge, 6-13 integration with Oracle8i database, 3-21
Oracle Visual Information Retrieval starting, 3-11
cartridge, 6-15 CONTROL_FILES parameter, 8-15, B-4
configuration tasks copy modes, for OCOPY, 12-4
Advanced Replication support, 6-24 CORBA, 2-21, 2-39, 13-2
Oracle Spatial cartridge, 6-11 CREATE DATABASE command, 8-17
configuring CREATE LIBRARY command, 13-8
Authentication Adapters, D-5 CREATE USER command, 10-27
External Naming, D-7 CTXSYS user name, 7-10
Named Pipes Protocol Adapter, D-8 database roles, 7-10
NDS Authentication Adapter, D-5 password, 7-10
Windows NT Native Authentication custom database
Adapter, D-6 advanced replication, 7-6
Connect archiving mode, 9-23
INTERNAL, from a remote machine, 7-11 available installation types, 7-4
CONNECT INTERNAL, 9-20 cartridges, 7-6
changing the INTERNAL password, 9-21 configuration mode created, 7-5
connecting without a password, 7-11, 10-3, 10- database environment, 7-7
35 database name created, 7-4
password, 9-20 initial archiving mode, 7-5
using, 9-10, 9-20, 9-23 operating system authentication, 7-6, 7-7
connecting options, 7-6
External Naming, D-8 overview, 7-2
Index-3
schema created, 7-7 MDSYS user name, 7-10
system identifier created, 7-4 MTSSYS user name, 7-9
ORDSYS user name, 7-10
OUTLN user name, 7-9
D
SCOTT user name, 7-9
data dictionary SYS user name, 7-9
Advanced Replication tables, 6-26 SYSTEM user name, 7-9
contents, 7-15 database tools
description, 7-15 operating system support, 3-2
starter database, 7-15 starting, 3-7
data files database user, connecting without a password, 10-
description, 7-12 25
INDX01.DBF, 7-13 databases
OEMREP01.DBF, 7-13 available installation types, 7-3
RBS01.DBF, 7-13 backing up, 8-25
starter database, 7-12 BUILD_DB.SQL script, 8-10
SYSTEM01.DBF, 7-13 BUILDALL.SQL, 8-17
TEMP01.DBF, 7-13 changing passwords, 8-22
USERS01.DBF, 7-13 coexistence, 5-3
database backup and recovery tools connecting to, 9-10, 9-23
Backup Manager, 12-2 control files in starter database, 7-14
OCOPY, 12-3 creating, 8-1
Recovery Manager (RMAN), 12-3 data dictionary in starter database, 7-15
third-party vendors, 12-3 data files in starter database, 7-12
database coexistence deleting, 8-13
issues, 5-7 exporting, 8-12
overview, 5-3 file names, 4-16
database environment, 7-7 importing, 8-22
database files installation in multiple homes, 5-13, 5-18
deleting, 8-13 installation on separate computers, 5-14
database monitoring maximum size possible, B-8
using Performance Monitor, 11-3 migration, 5-4, 5-15
with alert files, 11-14 monitoring, 11-1, 11-2
with Event Viewer, 11-11 multi-versioning, 5-12
with trace files, 11-14 naming conventions, 8-2
database privileges Optimal Flexible Architecture, 4-24, 4-26, 4-28
in Windows NT local groups, 10-30, 10-35, 10- Oracle Database Configuration Assistant, 8-4
42, 10-44 parameters for a new database, B-4
database release coexistence issues, 5-8 password encryption, 9-22
database roles redo log files in starter database, 7-13
COMDEMO user name, 7-10 rollback segments in starter database, 7-14
CTXSYS user name, 7-10 shutting down, 9-10, 9-11
DBSNMP user name, 7-9 starting, 9-10
DEMO user name, 7-10 system identifier, 7-11
granting through Windows NT, 10-40 tablespaces in starter database, 7-12
Index-4
upgrading, 5-4, 5-16, 5-45 DFS. See Distributed File System
user names in starter database, 7-8 directory names, convention used, xxvii
what to do with existing databases, 5-3 directory structure, ??–A-13
DB_BLOCK_BUFFERS parameter, B-4 directory structures
DB_BLOCK_SIZE parameter, B-4 OFA-compliant directory tree, 4-18
DB_FILE_MULTIBLOCK_ READ_ COUNT Oracle8i Client, A-8
parameter, B-4 Oracle8i Enterprise Edition, A-2
DB_FILES parameter, 8-16, B-4 Programmer/2000, A-11
DB_NAME directory, explained, 4-22 disk definition, F-3
DB_NAME parameter, 8-15, B-4 disks
DBLINK_ENCRYPT_LOGIN parameter, 9-22 striping, 4-30
DBSNMP user name, 7-9 DisplayName parameter, C-11, D-3
database roles, 7-9 DISTRIBUTED_TRANSACTIONS parameter, B-4
dropping with CATNSNMP.SQL, 7-9 DLL, external procedures, 13-7
password, 7-9 DML_LOCKS parameter, B-4
DBVERIFY documentation
operating system compatibility, 3-3 Adobe Acrobat Reader, 1-9
starting, 3-9 availability, 2-20
Decision Support System. See DSS formats supplied, 1-2
dedicated server mode, 7-5 generic, 1-3
disabling, 6-17 how to find specific information (online), 1-8
enabling, 6-17 HTML, 1-2
default control files, CTL1SID.ORA, 7-14 list of included manuals, 1-4
default data files Oracle Information Navigator, 1-2
INDX01.DBF, 7-13 ordering printed guides, 1-2
OEMREP01.DBF, 7-13 PDF, 1-2
RBS01.DBF, 7-13 printed, 1-2
SYSTEM01.DBF, 7-13 documentation conventions, used in this
TEMP01.DBF, 7-13 guide, xxvii
USERS01.DBF, 7-13 DSS
default initialization parameter file, INIT.ORA, 7- database environment, 7-7, 8-7
13 importing a sample schema, 8-8
default redo log files
REDO01.LOG, 7-14
E
REDO02.LOG, 7-14
REDO03.LOG, 7-14 encrypting, database passwords, 9-22
REDO04.LOG, 7-14 Enterprise JavaBeans, 2-21, 2-39, 13-2
default tablespaces, 7-12 error messages
default user names, 7-8 Intercartridge Exchange, 13-16
DEFAULT_HOME parameter, C-9 ORA-01102, 8-2
deleting Event Viewer, 11-11
password file, 9-20 34 ID, 11-12
DEMO user name, 7-10 auditing, 11-12
database roles, 7-10 blue (informational) icon, 11-12
passwords, 7-10 defined, 3-22
Index-5
for monitoring a database, 11-2 writing, 13-6
IDs other than 34, 11-12 EXTPROC, responsibilities, 13-5
integration with Oracle8 database, 3-22
logging operating system audit trail, 3-23
F
managing, 11-14
overview, 3-22 file names, convention used, xxvii
reading, 11-12 file size, maximum possible, B-8
red (stop sign) icon, 11-12 files
starting, 3-11 alert, 11-14
using, 11-11 assistant common, 2-11, 2-25, 2-34
yellow (exclamation point) icon, 11-12 database file names, 4-16
exception conditions, Intercartridge Exchange, 13- LISTENER.ORA, 13-5
16 maximum number per database, B-8
EXECUTE privileges, on a PL/SQL library, 13-8 maximum size possible, B-8
existing databases, installation types, 5-3 sample INIT.ORA, B-3
EXP. See Export Utility trace, 11-14
Export Utility
databases, 8-12 G
interactive mode, 8-12
operating system compatibility, 3-3 generic documentation references
parameter mode, 8-12 calculating index size, B-9
starting, 3-9 CREATE DATABASE, 8-17
extended partition custom database archiving mode, 9-23
create logical partitions, F-8 earliest releases that can be migrated, 5-5
creating, F-7 install test databases in a separate Oracle
defined, F-2 home, 4-3
EXTERNAL clause, 13-9 location of initialization parameter file, B-2
External Naming, D-7 managing the Event Viewer, 11-14
client configuration, D-8 maximum number of data files, 8-16
connecting with Server Manager, D-8 Microsoft operating systems certified on version
NDS Native Naming Adapter, D-7 8, 2-2
using, D-7 multi-versioning, 5-12
external procedures name and location of convert file, 5-40
additional documentation, 13-11 PL/SQL sample programs, location of, A-5
building, 13-4 product versions certified on version 8, 2-8
building a DLL, 13-7 running CATPROC.SQL, 8-21
creating, 13-4 SORT_AREA_SIZE default value, B-5
creating a PL/SQL library, 13-8 specifying archive destinations, B-4
defined, 13-4 starter database archiving mode, 9-23
enabling multi-threaded callout support, 13-10 starting Server Manager (SVRMGRL), 3-10
EXTERNAL clause, 13-9 supported operating systems, 2-2
features, 13-4 Windows NT-specific archiving procedures, 9-
granting EXECUTE privileges, 13-8 25
registering with Oracle database, 13-8 Windows NT-specific audit trail
using EXTPROC, 13-5 availability, 11-12
Index-6
Windows NT-specific audit trail facility, 11-12 Windows NT-specific role granting, 10-40
Windows NT-specific authentication Windows NT-specific role syntax, 10-44
methods, 10-2 Windows NT-specific trace file names, 11-14
Windows NT-specific automatic database startup Windows NT-specific upgrading
after reboot, 9-8 instructions, 5-1
Windows NT-specific control file GRANT EXECUTE ON command, 6-26
specifications, 8-14
Windows NT-specific CONTROL_FILE
H
parameter value, B-4
Windows NT-specific database creation HOME_COUNTER parameter, C-9
procedures, 8-4 HOME_NAME, defined, xxix
Windows NT-specific database migration HOMEID
instructions, 5-21 defined, xxix
Windows NT-specific initialization parameter Host Naming
file, B-2 supported vendors, 2-41
Windows NT-specific instance startup file Hostname parameter, 11-3, C-10
names, 9-10 hostname value, 11-3
Windows NT-specific local groups use, 10-30 hybrid database environment, 7-7
Windows NT-specific location of SQL creating, 8-8
scripts, A-6
Windows NT-specific LOG_ARCHIVE_DEST I
format, B-4
Windows NT-specific LOG_ARCHIVE_DEST ICX. See Intercartridge Exchange
value, B-4 IMAGECFG utility, 2-3
Windows NT-specific ImagePath parameter, C-11, D-3
LOG_ARCHIVE_FORMAT format, B-4 IMP. See Import Utility
Windows NT-specific migration instructions, 5- Import Utility
1 databases, 8-22
Windows NT-specific NLS_LANG values, E-3 interactive mode, 8-22
Windows NT-specific NLS_TERRITORY operating system compatibility, 3-3
values, E-3 parameter mode, 8-22
Windows NT-specific Oracle Enterprise Manager starting, 3-9
startup, 3-12 index size, calculating, B-9
Windows NT-specific OS_AUTHENT_PREFIX INDX tablespace, description, 7-12
case insensitivity, 10-26 INDX01.DBF
Windows NT-specific parameter file name and data file, 7-13
location, 7-13, B-2 tablespace contained in, 7-13
Windows NT-specific parameter file values, B-4 initialization parameter file
Windows NT-specific password file name and defined, B-2
location, 9-17 description, 7-13
Windows NT-specific Password Utility editing, B-2
installation, 2-23, 2-32 INIT.ORA, 7-13
Windows NT-specific redo log file location, 7- location, B-2
13 modifying, 8-14
Windows NT-specific redo log file size, 7-13 starter database, 7-13
Index-7
using PFILE option for database startup, 9-10 INST_LOC parameter, C-8
using the default file for database startup, 9-10 installation
initialization parameter requirements Net8 Client, 2-9, 2-10
Advanced Replication Support, 6-24 Net8 Server, 2-9
initialization parameters Instance Manager
AUDIT_TRAIL, B-4 starting, 3-16
BACKGROUND_DUMP_DEST, B-4 INSTANCE_NAME parameter, 8-15
COMMIT_POINT_ STRENGTH, B-4 instances
COMPATIBLE, B-4 creating, 8-27, 8-28
CONTROL_FILES, B-4 defined, 9-4
DB_BLOCK_BUFFERS, B-4 modifying, 8-30
DB_BLOCK_SIZE, B-4 running multiple instances, 9-16
DB_FILE_MULTIBLOCK_ READ_ COUNT, B-4 starting, 8-29
DB_FILES, B-4 stopping, 8-29
DB_NAME, B-4 interactive mode
DISTRIBUTED_TRANSACTIONS, B-4 Export Utility, 8-12
DML_LOCKS, B-4 Import Utility, 8-22
JOB_QUEUE_INTERVAL, B-4 Intercartridge Exchange
JOB_QUEUE_PROCESSES, B-4 accessing Web data, 13-12
LOG_ARCHIVE_DEST, B-4 configuring, 13-12
LOG_ARCHIVE_FORMAT, B-4 error messages, 13-16
LOG_ARCHIVE_START, B-4 exception conditions, 13-16
LOG_BUFFER, B-4 packaged functions, 13-13
LOG_CHECKPOINT_ INTERVAL, B-4 stored packages, 13-13
LOG_CHECKPOINT_ TIMEOUT, B-4 troubleshooting, 13-18
LOG_FILES, B-4 using, 13-13
MAX_DUMP_FILE_SIZE, B-5 INTERNAL, 10-40
MTS_DISPATCHERS, B-5 alias for SYS and SYSDBA, 7-9
MTS_MAX_DISPATCHERS, B-5 changing the INTERNAL password, 9-21
MTS_MAX_SERVERS, B-5 connecting as, 9-20
MTS_SERVERS, B-5 connecting without a password, 7-7, 7-9, 7-11,
NLS_LANGUAGE, B-5 10-35
NLS_SORT, B-5 password, 7-9, 9-20
NLS_TERRITORY, B-5 user name, 7-9
OPEN_CURSORS, B-5 italic letters, defined, xxvii
OPEN_LINKS, B-5
OS_AUTHENT_PREFIX, 10-26, B-5
J
PROCESSES, B-5
REMOTE_LOGIN_PASSWORDFILE, B-5 Java products
SHARED_POOL_SIZE, B-5 overview, 13-2
TEXT_ENABLE, B-5 Java stored procedures, 2-21, 13-2
TIMED_STATISTICS, B-5 Java Virtual Machine, 2-21, 2-39, 13-2
TRANSACTIONS_PER_ Java-enabled browsers, 1-8
ROLLBACK_SEGMENT, B-5 JOB_QUEUE_INTERVAL parameter, B-4
USER_DUMP_DEST, B-5 JOB_QUEUE_PROCESSES parameter, B-4
Index-8
K LU6.2 Protocol Adapter, 2-42
supporting networks, 2-15, 2-28, 2-36
Kerberos Authentication Adapter supporting topologies, 2-15, 2-28, 2-36
supported vendors, 2-42
Kerberos authentication method
see Oracle Advanced Networking Option M
management, G-2
L managing, Oracle Services, 9-2
mapped drives, 7-16, 8-3
LAST_HOME parameter, C-9 MAX_DUMP_FILE_SIZE parameter, B-5
Legato NetWorker, defined, 2-11, 2-25 MAX_IO_SIZE, B-5
Legato Storage Manager
MDSYS user name, 7-10
adding BIN directory to PATH, 12-7 database roles, 7-10
defined, 2-11, 2-25 password, 7-10
listener
Microsoft Internet Explorer, 1-8
1521 port, D-13 Microsoft SNMP, G-3
1526 port, D-13 MIG. See Migration Utility
OracleHOME_NAMETNSListener80 service, D-
migration
10 instructions, 5-27
OracleHOME_NAMETNSListener80LSNR multiple Oracle homes, 5-5
service, D-10
Optimal Flexible Architecture, 5-61
local groups overview, 5-4
with database privileges, 10-30, 10-35, 10-42, 10- SQL*Net, 5-24, 5-60
44
U0703040.SQL script, 5-42
LOCAL parameter, D-3
using appropriate tool versions, 5-28
log view, 11-5 Migration Utility
LOG_ARCHIVE_DEST parameter, 7-16, 8-3, 9-25,
operating system compatibility, 3-3
B-4
starting, 3-10
LOG_ARCHIVE_FORMAT parameter, 9-25, B-4 using, 5-27
LOG_ARCHIVE_START parameter, 9-25, B-4
MIGSID.ORA file, 5-36, 5-41
LOG_BUFFER parameter, B-4
monitoring
LOG_CHECKPOINT_ INTERVAL parameter, B-4 alert files, 11-2
LOG_CHECKPOINT_ TIMEOUT parameter, B-4
databases, 11-1
LOG_FILES parameter, B-4
Event Viewer, 11-2
LOGFILE parameter, C-11 Oracle events, 3-22, 3-24
logical partitions
Oracle8 Objects, 11-5
assigning symbolic links, F-10
Performance Monitor, 11-2
creating, F-8 Performance Pack, 11-2
Logical Unit Type 6.2 Protocol Adapter, 2-15, 2-28,
trace files, 11-2
2-36
MSHELP_TOOLS parameter, C-5
LSNRCTL80 utility MTS_DISPATCHERS parameter, B-5
starting from the Control Panel, G-6, G-8
specifying a value, B-5
LU6.2
MTS_MAX_DISPATCHERS parameter, B-5
See Logical Unit Type 6.2 Protocol Adapter, 2- MTS_MAX_SERVERS parameter, B-5
15, 2-28, 2-36
MTS_SERVERS parameter, B-5
Index-9
MTSSYS user name, 7-9 defined, 2-13
database roles, 7-9 Named Pipes Protocol Adapter
password, 7-9 supported vendors, 2-41
multiple instances, running, 9-16 with an Oracle Names Server, D-8
multiple Oracle home products, 4-7 NAMES.DIRECTORY_PATH parameter, D-7
Multiple Oracle Homes naming conventions for multiple Oracle homes, 9-
use of one listener for spawning, 4-5 2
multiple Oracle homes naming method
ALL_HOMES registry subkey, C-8 External Naming, D-7
before release 8.0.4, 4-3 NDS Authentication Adapter
benefits, 4-3 client configuration, D-6
classification of products, 4-7 NetWare Server configuration, D-5, D-6
defined, xxviii supported vendors, 2-41
environment, 4-5 using, D-5
for releases 8.0.4 to 8.0.5, 4-3 NDS Native Naming Adapter
for releases 8.1.3 and 8.1.4, 4-3 establishing connections with, D-7
functionality in different releases, 4-3 supported vendors, 2-41
introduction, 4-2 using, D-7
migration, 5-5 NET START command, 8-19
overview, 4-2 Net8
program groups, 4-5, 4-6 configuration requirements, 6-2
registry entries, 4-5, 4-6 configuring for external procedures, 13-5
service names, 4-5, 4-6 Net8 Assistant
service naming conventions, 9-2, 9-4 defined, 2-12, 2-26
system identifier, 4-5, 4-6, 7-11 starting, 3-17
upgrading, 5-5 Net8 Client, defined, 2-11, 2-25, 2-34
working with, 4-8 Net8 Easy Config
multi-threaded callout support defined, 2-12, 2-26, 2-34
configuration requirements, 6-3 starting, 3-17
enabling, 13-10 Net8 Server, defined, 2-12
setting OracleExtprocAgent, 13-11 NET80 parameter, D-2
multi-threaded server Netscape Navigator, 1-8
configuration requirements, 6-3 network
configuring with Oracle Database Configuration topologies supporting LU6.2 protocol, 2-15, 2-
Assistant, 2-20, 6-17 28, 2-36
disabling, 6-17 Network Security, described, 2-16, 2-29, 2-37
enabling, 6-17 NLS support, E-3
specifying MTS_DISPATCHERS, B-5 NLS_LANG environment variable, 5-29
multi-threaded server mode NLS_LANG parameter, C-5, E-2
same as shared server mode, 7-5 territory and character set defaults, E-3
multi-versioning, 5-12 NLS_LANGUAGE parameter, B-5
NLS_SORT parameter, B-5
NLS_TERRITORY parameter, B-5
N
NOARCHIVELOG mode, 7-5, 9-23
NAME parameter, C-8 Non-multiple Oracle home products, 4-8
Named Pipes non-multiple Oracle home products, 4-8
Index-10
Non-Oracle Home Products, 4-8 NT, 10-40
Non-Oracle home products, 4-8 setting OS_AUTHENT_PREFIX, 10-26
SQLNET.ORA file, 10-2
operating systems
O
audit trail, 3-23
Object Request Broker (ORB), 2-21, 13-2 authentication overview, 10-2
Object Type Translator (OTT), defined, 2-18, 2-30, supported, 2-2
2-38 OPERF.LOG file, 11-10
ObjectName parameter, C-11, D-3 viewing Performance Monitor status, 11-10
OCOPY OPERFCFG
backup file types, 12-4 defined, 2-4
capabilities, 12-3 operating system compatibility, 3-3
copy modes, 12-4 starting, 3-10
operating system compatibility, 3-3 syntax examples, C-18
recovery file types, 12-6 OPS$, 10-26
starting, 3-10 Optimal Flexible Architecture
syntax for backing up files, 12-5 benefits, 4-14
syntax for recovering files, 12-6 characteristics of a database, 4-14
ODBC. See Oracle Open Database Connectivity default OFA database, 4-24
Driver defined, 2-6
OEMREP01.DBF differences since previous releases, 4-16
data file, 7-13 introduction, 4-2
tablespace contained in, 7-13 moving database files, 5-61
OFA. See Optimal Flexible Architecture non-default OFA database 1, 4-26
OLTP non-default OFA database 2, 4-28
database environment, 7-7, 8-7 NT and UNIX differences, 4-32
importing a sample schema, 8-8 OFA-compliant directory tree, 4-18
One, 4-5 Oracle Parallel Server option, 4-19
Online Transaction Processing. See OLTP overview, 4-13
OO4O parameter, C-8 ORA_AFFINITY parameter, C-6
Open Systems Interconnect (OSI) model, 2-15, 2- ORA_CWD parameter, C-5
28, 2-36 ORA_ENCRYPT_LOGIN parameter, 9-22
OPEN_CURSORS parameter, B-5 ORA_SHUTDOWN parameter, 9-12
OPEN_LINKS parameter, B-5 ORA_SID_AUTOSTART parameter, 9-11, C-5
operating system authentication, 7-6, 7-7 ORA_SID_PFILE parameter, 9-11, C-5
automatically enabling during installation, 10-3 ORA_SID_SHUTDOWN parameter, 9-12, C-5
connecting as INTERNAL without a ORA_SID_SHUTDOWN_TIMEOUT parameter, 9-
password, 10-35 13, C-5
connecting as SYSOPER or SYSDBA without a ORA_SID_SHUTDOWNTYPE parameter, 9-13, C-
password, 10-30 5
connecting without a password as a ORA-00256 error, 7-16, 8-3
nonprivileged database user, 10-25 ORA-09291 error, 7-16, 8-3
creating an authenticated user Oracle, 2-42
creating, 10-27 Oracle Administration Assistant for Windows NT
granting database roles through Windows defined, 2-4, 2-18
Index-11
using, C-16, C-19 database environment, 7-7
Oracle Administration Assistant snap-in database name created, 7-4
defined, 2-18 database types created, 7-4
Oracle Advanced Networking Option initial archiving mode, 7-5
Kerberos authentication method, 2-17, 2-29, 2- Minimal installation type, 7-3
37 operating system authentication, 7-7
RADIUS authentication method, 2-17, 2-29, 2-37 options, 7-6
Oracle Advanced Networking option - Export Edi- sample DSS schema, 8-8
tion sample OLTP schema, 8-8
defined, 2-5 schema created, 7-7
Oracle Advanced Security Administrator’s starter database control file, 7-14
Guide, 2-42 starter database data dictionary, 7-15
Oracle Application Wizards for Microsoft Visual starter database data files, 7-12
Studio starter database initialization parameter file, 7-
defined, 2-18 13
Oracle AppWizard for Microsoft Visual C++ starter database overview, 7-2
defined, 2-5, 2-18, 2-30 starter database redo log files, 7-13
Oracle Audio Data cartridge starter database rollback segments, 7-14
configuration responsibilities, 6-4 starter database tablespaces, 7-12
Oracle Call Interface starter database user names, 7-8
defined, 2-18, 2-30, 2-38 system identifier, 7-11
Oracle COM Automation option system identifier created, 7-4
defined, 2-5, 2-19 Typical installation type, 7-3
Oracle Connection Manager Oracle Database Configuration Assistant
1610 port, D-13 advanced replication, 7-6
1620 port, D-13 available database installation types, 7-4
defined, 2-19 cartridges, 7-6
OracleHOME_NAMECManService service, D- configuration mode created, 7-5
12 configuring cartridges, 8-9
Oracle ConText cartridge creating a DSS database environment, 8-7
configuration responsibilities, 6-7 creating a hybrid database environment, 8-8
Oracle Data Migration Assistant creating an OLTP database environment, 8-7
defined, 2-20 database environment, 7-7
starting, 3-17 database name created, 7-4
using, 5-25, 5-45 defined, 2-20
Oracle database deleting databases, 8-10
advanced replication, 7-6 importing a sample DSS schema, 8-8
available types, 7-3 importing a sample OLTP schema, 8-8
cartridges, 7-6 initial archiving mode, 7-5
configuration mode created, 7-5 multi-threaded support, 8-10
creating for a DSS environment, 8-7 operating system authentication, 7-7
creating for a hybrid environment, 8-8 options, 7-6
creating for an OLTP environment, 8-7 schema created, 7-7
custom database overview, 7-2 starting, 3-17
Custom installation type, 7-3 system identifier created, 7-4
Index-12
Oracle Enterprise Manager defined, 2-21
Backup Manager, 12-2 Oracle Open Database Connectivity Driver
operating system compatibility, 3-4 defined, 2-22, 2-32, 2-39
Performance Pack, 11-2 single Oracle home product, 4-7
single Oracle home product, 4-8 Oracle Parallel Server option
starting, 3-12 configuration requirements, 6-3
status for release 8.1.4, 3-2 defined, 2-22
Oracle for Windows NT Performance Monitor Optimal Flexible Architecture, 4-19
defined, 2-20 single Oracle home product, 4-7
parameters, C-9, C-18 Oracle Partitioning option
single Oracle home product, 4-7 configuration requirements, 6-2
Oracle Home Configuration snap-in defined, 2-22
defined, 2-18 Oracle Performance Monitoring snap-in
using, C-16 using, C-19
Oracle Home Selector Oracle products
changing PATH value, 4-10 configuration guidelines, 6-2
installation, 2-32 for Windows NT and Windows 95/98, 2-8
Oracle Image cartridge Oracle Server
defined, 2-19 defined, 2-22
Oracle Information Navigator, starting, 1-8 Oracle Services
Oracle Intelligent Agent auto-starting, 9-8
defined, 2-20 for Oracle8 database, 3-21
Oracle Java option naming conventions for multiple Oracle
defined, 2-21 homes, 9-2
Oracle Java Tools OracleAgent, 9-4
defined, 2-21, 2-31, 2-39 OracleConTextService, 9-4
Oracle JDBC Drivers OracleExtprocAgent, 9-4
defined, 2-20, 2-23, 2-31, 2-39 OracleServiceSID, 9-4
Oracle Migration Assistant for Microsoft Access OracleTNSListener, 9-4
single Oracle home product, 4-7 OracleWebAssistant, 9-5
Oracle Names shutting down a database by stopping a
1575 port, D-13 service, 9-11
defined, 2-21 starting, 9-5
Named Pipes Protocol Adapter, D-8 stopping, 9-6
OracleHOME_NAMEClientCache80, D-11 viewing in the Control Panel, 3-21
OracleHOME_NAMEClientCache80 service, D- Oracle Services for MTS
11 configuration requirements, 6-3
OracleHOME_NAMENamesService80, D-11 defined, 2-6, 2-22, 2-32
OracleHOME_NAMENamesService80 Oracle SNMP Agent
service, D-11 configuring, G-4
Oracle Objects for OLE Oracle SNMP Encapsulator
defined, 2-21, 2-31, 2-39 starting, G-6
single Oracle home product, 4-7 Oracle SNMP Master Agent
Oracle Objects option starting, G-6
configuration requirements, 6-2 Oracle SNMP Master Agent and Encapsulator
Index-13
controlling, G-6 ORACLE_HOME_KEY parameter, C-6
Oracle Spatial cartridge ORACLE_HOME_NAME parameter, C-6
configuration requirements, 6-2 ORACLE_PRIORITY parameter, C-7
configuration responsibilities, 6-11 ORACLE_SID parameter, C-7
configuration tasks, 6-11 ORACLE_SID parameter, 8-23, 9-4, 9-16
Oracle SQLJ Translator Oracle7 applications, database coexistence, 5-7
defined, 2-23, 2-39 Oracle7 Clients
directory structure, A-6 migration to Oracle8, 5-17
documentation, 13-3 Oracle7 database, migrating, 5-21
Oracle Time Series cartridge Oracle8 Buffer Cache, 11-7
configuration requirements, 6-2 Oracle8 Data Dictionary Cache, 11-7
configuration responsibilities, 6-13 Oracle8 Data Files object, 11-8
Oracle Universal Installer Oracle8 database
advanced replication, 7-6 available Oracle Services, 3-21
available database installation types, 7-4 connecting to, 9-10, 9-23
cartridges, 7-6 password encryption, 9-22
configuration mode created, 7-5 selecting a backup and recovery tool, 12-2
database environment, 7-7 shutting down, 9-10, 9-11
database name created, 7-4 shutting down a database with a service, 9-12
defined, 2-23, 2-32, 2-39 specifications, B-8
initial archiving mode, 7-5 starting, 9-10
operating system authentication, 7-7 using Event Viewer, 3-22
options, 7-6 using Performance Monitor, 3-24
schema created, 7-7 using User Manager, 3-28
system identifier created, 7-4 Oracle8 database backup and recovery tools
Oracle Utilities Backup Manager, 12-2
defined, 2-23, 2-32 OCOPY, 12-3
Oracle Visual Information Retrieval cartridge Recovery Manager (RMAN.EXE), 12-3
configuration requirements, 6-2 third-party vendors, 12-3
configuration responsibilities, 6-15 Oracle8 Free List, 11-9
Oracle Web Publishing Assistant Oracle8 Library Cache, 11-9
defined, 2-23, 2-32 Oracle8 Objects, monitoring, 11-5
starting, 3-17 Oracle8 Performance Monitor
ORACLE_BASE accessing, 11-4
changing the value, 4-19 alert view, 11-5
explained, xxviii, 4-16, 4-19 chart view, 11-5
ORACLE_BASE parameter, C-6 for monitoring a database, 11-2
ORACLE_GROUP_NAME parameter, C-6 Hostname parameter, 11-3
ORACLE_HOME log view, 11-5
explained, xxviii monitoring Oracle8 Objects, 11-5
ORACLE_HOME directory OPERF.LOG, 11-10
explained, 4-21 Oracle8 Buffer Cache, 11-7
specifying, 4-23 Oracle8 Data Dictionary Cache, 11-7
ORACLE_HOME parameter, C-6 Oracle8 Data Files, 11-8
ORACLE_HOME, explained, xxviii Oracle8 Free List, 11-9
Index-14
Oracle8 Library Cache, 11-9 service, D-10
Oracle8 Redo Log Buffer, 11-8 OracleServiceSID, 9-4
password, 11-3 starting the database, 9-11
registry information, 11-3 stopping the database, 9-11
Report View, 11-5 OracleSNMPPeerMasterAgent
troubleshooting information, 11-10 MASTER.CFG file, G-9
Username parameter, 11-3 OracleTNSListener
using, 11-3 defined, 9-4
Oracle8 Redo Log Buffer, 11-8 OracleWebAssistant service, defined, 9-5
Oracle8 Sorts, 11-9 ORADATA directory, explained, 4-22
Oracle8 Utilities ORADEBUG
operating system compatibility, 3-3 debugging utility, 9-27
Oracle8i starting, 9-27
new features, 2-4 ORADIM
new products, 2-4 changing the INTERNAL password, 9-21
Oracle8i Client creating an instance, 8-27
directory structure, A-8 modifying an instance, 8-30
installation option explained, 2-8 moving or copying password files, 9-18
Oracle8i database operating system compatibility, 3-3
using Control Panel, 3-21 starting, 3-10
Oracle8i Enterprise Edition starting an instance, 8-29
defined, 2-2 stopping an instance, 8-29
directory structure, A-2 ORAPWD
installable products, 2-7 creating password files, 9-17
installation option explained, 2-8 operating system compatibility, 3-3
OracleAgent, defined, 9-4 starting, 3-10
OracleConTextService, defined, 9-4 ORB (Object Request Broker), 2-21, 13-2
OracleExtprocAgent, defined, 9-4 ORDSYS user name, 7-10
OracleHOME_NAMEClientCache service, 2-10 database roles, 7-10
OracleHOME_NAMEClientCache80 key, D-2 password, 7-10
OracleHOME_NAMEClientCache80 service, D-11 OS_AUTHENT_PREFIX parameter, 10-26, B-5
OracleHOME_NAMECMAdminService80 key, D- OS_ROLES parameter, 10-40
2 OSD-04018 error, 7-16, 8-3
OracleHOME_NAMECMAdminService80 OUTLN user name, 7-9
service, 2-10, D-2 database roles of, 7-9
OracleHOME_NAMECManService service, D-12 password of, 7-9
OracleHOME_NAMECManService80 key, D-2 overview
OracleHOME_NAMECManService80 service, 2-10 of TNSNAMES.ORA file, G-9, G-10
OracleHOME_NAMENamesService80 service, D- OWAST parameter, C-7
11 OWAST_HOME parameter, C-7
OracleHOME_NAMETNSListener service, D-8 OWASTDBS parameter, C-7
OracleHOME_NAMETNSListener80 key, D-2
OracleHOME_NAMETNSListener80 service, 2-10,
P
D-10
OracleHOME_NAMETNSListener80LSNR packaged functions
Intercartridge Exchange, 13-13
Index-15
UTL_HTTP.REQUEST, 13-14 defined, 3-24
UTL_HTTP.REQUEST_PIECES, 13-14 integration with Oracle8 database, 3-24
parameter mode monitoring specific Oracle events, 3-24
Export Utility, 8-12 starting, 3-11
Import Utility, 8-22 viewing OPERF.LOG file status, 11-10
partition Performance Pack, monitoring a database, 11-2
extended, F-2 performance, increasing, 4-30
logical partition, F-4 PFILE option, 9-10
physical disk, F-4 PhysicalDrive, F-4
raw, 4-31, F-2 PL/SQL
password file configuring external procedures, 6-3
authenticating database administrators, 9-17 external procedures, 13-4
connecting as INTERNAL, 9-20 sample programs, location of, A-5
creating, 9-17 PRAGMA RESTRICT_REFERENCES, with Intercar-
deleting, 9-20 tridge Exchange, 13-16
hiding, 9-17 privileges
viewing, 9-19 in Windows NT local groups, 10-30, 10-35, 10-
Password parameter, C-10 42, 10-44
Password Utility. See ORAPWD Pro*C/C++
passwords defined, 2-40
changing, 7-8 Pro*COBOL
changing for SYS user name, 7-8, 9-21 defined, 2-40
changing for SYSTEM user name, 7-8, 9-21 PROCESSES parameter, B-5
changing the INTERNAL password, 9-21 products
connecting without a password with multiple Oracle home products, 4-7
INTERNAL, 7-9, 7-11, 10-35 non-multiple Oracle home products, 4-8
encryption, 9-22 single Oracle home products, 4-7
for COMDEMO user name, 7-10 Products supporting multiple Oracle homes, 4-7
for CTXSYS user name, 7-10 program groups
for databases, 8-22 multiple Oracle homes, 4-5, 4-6
for DBSNMP user name, 7-9 Programmer/2000
for DEMO user name, 7-10 directory structure, A-11
for INTERNAL user name, 7-9, 9-20 installation option explained, 2-8
for MDSYS user name, 7-10 protocol stack vendors, 2-41
for MTSSYS user name, 7-9 PWDSID.ORA file, 9-17
for ORDSYS user name, 7-10
for OUTLN user name, 7-9
R
for SCOTT user name, 7-9
for SYS user name, 7-9 R0703040.SQL, 5-42
for SYSTEM user name, 7-9 RADIUS authentication method
PATH parameter, C-8 see Oracle Advanced Networking Option
PATH, changing the value of, 4-10 RAID (Redundant Array of Inexpensive Disks), 4-
PERF_FILE_NAME parameter, C-11 33
PERFORMANCE key, C-9 RAID configuration, 4-30
Performance Monitor, 11-3 raw partition
Index-16
defined, 4-31, F-2 NET80 parameter, D-2
logical partition, F-4 NLS_LANG, C-5
overview, F-2 ObjectName, C-11, D-3
physical disk, F-4 OO4O, C-8
RBS tablespace, description, 7-12 ORA_AFFINITY, C-6
RBS01.DBF ORA_CWD, C-5
data file, 7-13 ORA_SHUTDOWN, 9-12
tablespace contained in, 7-13 ORA_SID_AUTOSTART, 9-11, C-5
RDBMS_ARCHIVE parameter, C-7 ORA_SID_PFILE, 9-11, C-5
RDBMS_CONTROL parameter, C-7 ORA_SID_SHUTDOWN, 9-12, C-5
recovering, an Oracle8 database, 12-2 ORA_SID_SHUTDOWN_TIMEOUT, 9-13, C-5
recovery file types, OCOPY, 12-6 ORA_SID_SHUTDOWNTYPE, 9-13, C-5
Recovery Manager, 12-3 ORACLE_BASE, C-6
capabilities, 12-3 ORACLE_GROUP_NAME, C-6
operating system compatibility, 3-3 ORACLE_HOME, C-6
starting, 3-10 ORACLE_HOME_KEY, C-6
redo log files ORACLE_HOME_NAME, C-6
archiving, 9-23 ORACLE_PRIORITY, C-7
REDO01.LOG, 7-14 ORACLE_SID, C-7
REDO02.LOG, 7-14 OracleHOME_NAMEClientCache80 key, D-2
REDO03.LOG, 7-14 OracleHOME_NAMECMAdminService80
REDO04.LOG, 7-14 key, D-2
starter database, 7-13 OracleHOME_NAMECManService80 key, D-2
REDO01.LOG file, 7-14 OracleHOME_NAMETNSListener80 key, D-2
REDO02.LOG file, 7-14 OWAST, C-7
REDO03.LOG file, 7-14 OWAST_HOME, C-7
REDO04.LOG file, 7-14 OWASTDBS, C-7
REGEDT32 command, 8-23 parameter values, C-2
registering, an external procedure, 13-8 Password, C-10
registry password value, 11-3
adding parameters, C-14 PATH, C-8
ALL_HOMES subkey, C-8 PERF_FILE_NAME, C-11
configuration parameters, C-1 PERFORMANCE key, C-9
DEFAULT_HOME, C-9 RDBMS_ARCHIVE, C-7
DisplayName, C-11, D-3 RDBMS_CONTROL, C-7
HOME_COUNTER, C-9 REG_DWORD, C-3, C-15
Hostname, 11-3, C-10 REG_EXPAND_SZ, C-2, C-15
ImagePath, C-11, D-3 REG_MULTI_SZ, C-2, C-15
INST_LOC, C-8 REG_SZ, C-2, C-15
keys, C-2 REGEDT32, C-12, C-14
LAST_HOME, C-9 starting, 3-12
LOGFILE, C-11 update ORACLE_SID, 8-23
modifying values, C-12 Username, 11-3, C-10
MSHELP_TOOLS, C-5 using OPERFCFG, C-18
NAME, C-8 Registry Editor, C-2
Index-17
registry entries Server Manager
multiple Oracle homes, 4-5, 4-6 operating system compatibility, 3-3
reliability, increasing, 4-30 running multiple instances, 9-16
remote computers, accessing database files, 7-15 shutting down the database, 9-10
REMOTE parameter, D-4 starting, 3-10, 9-10
REMOTE_LOGIN_PASSWORDFILE parameter, 9- starting the database, 9-10
17, 9-20, B-5 status for release 8.1.4, 3-2
replication, configuration tasks, 6-24 using appropriate version, 5-28
Report View, 11-5 using ORADEBUG, 9-27
RMAN. See Recovery Manager using SQL*Plus as an alternative, 3-2
roles service
granting through Windows NT, 10-40 how to start and stop, D-10
of COMDEMO user name, 7-10 listed, D-10
of CTXSYS user name, 7-10 service names
of DBSNMP user name, 7-9 multiple Oracle homes, 4-5, 4-6
of DEMO user name, 7-10 SERVICE_NAME parameter, 8-15
of MDSYS user name, 7-10 services, 9-2
of MTSSYS user name, 7-9 auto-starting, 9-8
of ORDSYS user name, 7-10 available with Oracle8 database, 3-21
of OUTLN user name, 7-9 managing, 9-2
of SCOTT user name, 7-9 OracleAgent, 9-4
of SYS user name, 7-9 OracleConTextService, 9-4
of SYSTEM user name, 7-9 OracleExtprocAgent, 9-4, 13-11
rollback segments OracleServiceSID, 9-4
contents, 7-14 OracleTNSListener, 9-4
starter database, 7-14 OracleWebAssistant, 9-5
shutting down a database by stopping a
service, 9-11
S
starting, 8-16, 9-5
Schema Manager stopping, 9-6
starting, 3-16 viewing in the Control Panel, 3-21
schema, INTERNAL user name, 7-9 SET INSTANCE command, 10-33, 10-39, 10-45
schemas SET ORACLE_SID=SID, 9-16
importing an DSS sample schema, 8-8 SETLINKS utility, F-10
importing an OLTP sample schema, 8-8 create symbolic links, F-10, F-12
SCOTT user name, 7-9 ignoring links, F-11
database roles of, 7-9 removing links, F-11
password of, 7-9 shared server mode, 6-18, 7-5
scripts same as multi-threaded server mode, 7-5
location of, A-6 SHARED_POOL_SIZE parameter, B-5
SecurID Authentication Adapter SHUTDOWN command
supported vendors, 2-41, 2-42 options, 9-10
Security Manager using, 9-10
starting, 3-16 shutting down
SELECT * FROM ALL_OBJECTS query, 6-25 databases, 9-10, 9-11
Index-18
SID. See system identifier SQLJ. See Oracle SQLJ Translator
single log on SQLNET.AUTHENTICATION_SERVICES
for accessing servers and databases, D-7 parameter, D-6
single Oracle home products, 4-7 SQLNET.ORA file, operating system
Single Sign-On, described, 2-17, 2-29, 2-37 authentication, 10-2
SNA, 2-15, 2-28, 2-36 square brackets, defined, xxvii
snap-ins starter database
Oracle Home Configuration, C-16 advanced replication, 7-6
Oracle Performance Monitoring, C-19 archiving mode, 9-23
SNMP, G-2 available installation types, 7-4
description of support for Oracle products, G-2 cartridges, 7-6
in a TCIP/IP network, G-2 configuration mode created, 7-5
managed elements, G-2 control file, 7-14
management framework, G-2 data dictionary, 7-15
management station, G-2 data files, 7-12
master agent, G-2 database environment, 7-7
Oracle SNMPPeerMasterAgent, G-3 database name created, 7-4
OracleSNMPPeerEncapsulator, G-3 initial archiving mode, 7-5
subagents, G-2 initialization parameter file, 7-13
specifying an archiving file format, 9-25 operating system authentication, 7-6, 7-7
SPOOL command, using, 6-25, 6-26 options, 7-6
SPX overview, 7-2
defined, 2-13, 2-27 redo log files, 7-13
SPX Protocol Adapter rollback segments, 7-14
supported vendors, 2-41 schema created, 7-7
SQL scripts system identifier created, 7-4
location of, A-6 tablespaces, 7-12
SQL Worksheet user names, 7-8
starting, 3-16 starting
SQL*DBA, using appropriate version, 5-28 databases, 9-10
SQL*Loader Oracle Services, 9-5
control file conventions, 3-20 Oracle8 Performance Monitor, 11-4
direct path option, 3-19 Server Manager, 9-10
operating system compatibility, 3-3 STARTUP command, 9-10
starting, 3-11 stopping, Oracle Services, 9-6
using, 3-19 stored packages, Intercartridge Exchange, 13-13
SQL*Net striping disks, 4-30
appropriate versions, 5-24, 5-60 SVRMGR versions, 5-28
SQL*Plus SVRMGRL. See Server Manager
defined, 2-24, 2-33, 2-40 symbolic links, 4-32
functionality enhancements, 3-2 creating, F-10, F-12
operating system compatibility, 3-4 ignoring, F-11
starting, 3-18 removing, F-11
status for release 8.1.4, 3-2 symbols, list of, xxix
SQL, external procedures, 13-4 syntax
Index-19
for backing up files with OCOPY, 12-5 supported vendors, 2-41
for recovering files with OCOPY, 12-6 TEMP tablespace, description, 7-12
SYS user name, 7-9 TEMP01.DBF
changing the password, 7-8, 9-21 data file, 7-13
database roles of, 7-9 tablespace contained in, 7-13
password of, 7-9 TEXT_ENABLE parameter, B-5
SYSDBA third party applications, 5-10
connecting without a password, 10-30 third-party backup and recovery vendors, 12-3
SYSOPER TIMED_STATISTICS parameter, B-5
connecting without a password, 10-30 TKPROF
system identifier operating system compatibility, 3-3
defined, 9-4 starting, 3-11
for Oracle database, 7-11 TNS_ADMIN parameter, D-4
multiple Oracle homes, 4-5, 4-6, 7-11 TNSNAMES.ORA file, 13-5
System Network Architecture (SNA), 2-15, 2-28, 2- overview, G-9, G-10
36 top-level directory, explained, 4-16
SYSTEM tablespace, description, 7-12 trace files, 11-14
SYSTEM user name, 7-9 creating with ORADEBUG, 9-27
changing the password, 7-8, 9-21 for monitoring a database, 11-2
database roles of, 7-9 using, 11-14
password of, 7-9 using BACKGROUND_DUMP_DEST
SYSTEM01.DBF parameter, 11-14
data file, 7-13 using USER_DUMP_DEST, 11-14
tablespace contained in, 7-13 TRANSACTIONS_PER_ ROLLBACK_ SEGMENT
parameter, B-5
troubleshooting
T
Intercartridge Exchange, 13-18
tablespaces with ORADEBUG, 9-27
Advanced Replication support, 6-23, 6-26
containing INDX01.DBF, 7-13
containing OEMREP01.DBF, 7-13
U
containing RBS01.DBF, 7-13 U0703040.SQL script, 5-42
containing SYSTEM01.DBF, 7-13 U0800030.SQL script, 5-52
containing TEMP01.DBF, 7-13 U0800040.SQL script, 5-52
containing USERS01.DBF, 7-13 U0800050.SQL script, 5-52
expanding for large sorts, 7-12 UNC, 7-15, 8-3
INDX, 7-12 Universal Naming Convention, 7-15, 8-3
RBS, 7-12 UNIX
starter database, 7-12 Optimal Flexible Architecture, 4-32
SYSTEM, 7-12 upgrading
TEMP, 7-12 multiple Oracle homes, 5-5
USERS, 7-12 Optimal Flexible Architecture, 5-61
TCP/IP overview, 5-4
defined, 2-13, 2-27 tools, 5-45
TCP/IP Protocol Adapter U0800020.SQL script, 5-52
Index-20
U0800030.SQL script, 5-52 Windows NT
U0800040.SQL script, 5-52 directory structure for database, A-2
U0800050.SQL script, 5-52 tools, 3-3
USE_SHARED_SOCKET parameter, D-4 Windows NT local groups
User Manager with database privileges, 10-3, 10-30, 10-35, 10-
defined, 3-28 42, 10-44
integration with Oracle8 database, 3-28 Windows NT Native Authentication Adapter
starting, 3-12 supported vendors, 2-41
user names using, D-6
changing passwords for SYS and SYSTEM, 7-8 Windows NT Native authentication methods, use
COMDEMO, 7-10 of, 10-2
CTXSYS, 7-10 WINSOCK2 support, D-4
DBSNMP, 7-9
DEMO, 7-10
X
INTERNAL, 7-9
MDSYS, 7-10 XAVIEW.SQL script
MTSSYS, 7-9 location of, A-6
ORDSYS, 7-10
OUTLN, 7-9
SCOTT, 7-9
starter database, 7-8
SYS, 7-9
SYSTEM, 7-9
USER_DUMP_DEST parameter, 8-16, 11-14, B-5
Username parameter, C-10
USERS tablespace, description, 7-12
USERS01.DBF
data file, 7-13
tablespace contained in, 7-13
UTL_HTTP.REQUEST, Intercartridge
Exchange, 13-14
UTL_HTTP.REQUEST_PIECES, Intercartridge
Exchange, 13-14
UTLXPLAN.SQL script
location of, A-6
V
variables, convention used, xxvii
viewing
password file, 9-19
W
Web data, Intercartridge Exchange, 13-12
Index-21
Index-22