Oracle Database Platform Guide For Windows

User Manual:

Open the PDF directly: View PDF .
Page Count: 272

Download
Open PDF In Browser	View PDF

[1]
Oracle®
Database

Platform Guide
11g Release 2 (11.2) for Microsoft Windows
E10845-13

December 2014

Oracle Database Platform Guide, 11g Release 2 (11.2) for Microsoft Windows
E10845-13
Copyright © 1996, 2014, Oracle and/or its affiliates. All rights reserved.
Primary Author: Reema Khosla
Contributing Author: Ashmita Bose, Lance Ashdown
Contributors: Beldalker Anand, Adam Bentley, Ricky Chen, David Collelo, David Friedman, Janelle
Simmons, Sue K. Lee, Rich Long, Satish Panchumarthy, Ravi Thammaiah, Michael Verheij
This software and related documentation are provided under a license agreement containing restrictions on
use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your
license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license,
transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse
engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is
prohibited.
The information contained herein is subject to change without notice and is not warranted to be error-free. If
you find any errors, please report them to us in writing.
If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it
on behalf of the U.S. Government, the following notice is applicable:
U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software,
any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users
are "commercial computer software" pursuant to the applicable Federal Acquisition Regulation and
agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and
adaptation of the programs, including any operating system, integrated software, any programs installed on
the hardware, and/or documentation, shall be subject to license terms and license restrictions applicable to
the programs. No other rights are granted to the U.S. Government.
This software or hardware is developed for general use in a variety of information management
applications. It is not developed or intended for use in any inherently dangerous applications, including
applications that may create a risk of personal injury. If you use this software or hardware in dangerous
applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other
measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages
caused by use of this software or hardware in dangerous applications.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of
their respective owners.
Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks
are used under license and are trademarks or registered trademarks of SPARC International, Inc. AMD,
Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced
Micro Devices. UNIX is a registered trademark of The Open Group.
This software or hardware and documentation may provide access to or information on content, products,
and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly
disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle
Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your
access to or use of third-party content, products, or services.

Contents
Preface ............................................................................................................................................................... xiii
Audience.....................................................................................................................................................
Documentation Accessibility ...................................................................................................................
Related Documents ...................................................................................................................................
Conventions ...............................................................................................................................................

xiii
xiv
xiv
xiv

What's New in Oracle Database for Windows ........................................................................... xv
1

Oracle Database Architecture on Windows
1.1
1.1.1
1.1.2
1.1.3
1.1.4
1.2
1.2.1
1.2.2
1.2.3
1.3
1.3.1
1.3.2
1.3.3
1.4

Oracle Database on Windows Architecture............................................................................
Automatic Storage Management.......................................................................................
Thread-Based Architecture.................................................................................................
File I/O Enhancements .......................................................................................................
Raw File Support .................................................................................................................
Oracle Database Scalability on Windows................................................................................
Support for Very Large Memory (VLM) Configurations ..............................................
Windows 4 GB RAM Tuning (4GT) ..................................................................................
Large User Populations.......................................................................................................
Oracle Database Integration with Windows...........................................................................
Oracle PKI Integration with Windows .............................................................................
Oracle Services for Microsoft Transaction Server ...........................................................
Oracle Fail Safe Integration with Windows.....................................................................
Other Sources of Information....................................................................................................

1-1
1-1
1-1
1-4
1-4
1-5
1-5
1-7
1-8
1-8
1-8
1-8
1-9
1-9

Database Tools on Windows
2.1
Choosing a Database Tool .........................................................................................................
2.1.1
Database Tools and Operating System Compatibility ...................................................
2.1.2
Preferred Database Tools....................................................................................................
2.2
Starting Database Tools..............................................................................................................
2.2.1
Starting Database Tools in Multiple Oracle Homes .......................................................
2.2.1.1
Starting Tools from Oracle8i Release 8.1.3 and Later Multiple Oracle Homes ...
2.2.2
Running Tools with Windows User Account Control ...................................................
2.2.3
Starting Database Tools from the Start Menu .................................................................
2.2.4
Starting Database Tools from the Command Line .........................................................
2.2.5
Starting Windows Tools .....................................................................................................

2-1
2-2
2-2
2-4
2-4
2-4
2-4
2-5
2-7
2-9

iii

2.3
Using SQL*Loader ................................................................................................................... 2-10
2.3.1
Windows Processing Options ......................................................................................... 2-10
2.3.1.1
Default (No Processing Option) or "str terminator_string"................................. 2-10
2.3.2
Control File Conventions................................................................................................. 2-11
2.4
Using Windows Tools ............................................................................................................. 2-11
2.4.1
Using Event Viewer to Monitor a Database ................................................................. 2-11
2.4.2
Using Microsoft Management Console to Administer a Database ........................... 2-12
2.4.3
Using Oracle Counters for Windows Performance Monitor...................................... 2-12
2.4.4
Using Registry Editor to Modify Configuration Information .................................... 2-13
2.4.5
Using Task Manager to Monitor Applications and Processes ................................... 2-13
2.4.6
Using Local Users and Groups to Manage Users and Groups .................................. 2-13
2.5
Optional Windows Diagnostic and Tuning Utilities .......................................................... 2-14

Postinstallation Database Creation on Windows
3.1
3.2
3.3
3.3.1
3.3.2
3.3.3
3.3.4
3.3.5
3.3.6
3.3.7
3.3.8
3.3.9
3.3.10
3.4
3.4.1
3.4.2
3.4.3
3.4.4
3.4.5
3.5
3.5.1
3.5.2
3.5.3

Naming Conventions for Oracle Database ............................................................................. 3-1
Creating a Database on Windows Using Database Configuration Assistant .................... 3-1
Creating a Database on Windows Using Command-Line Tools ......................................... 3-2
Exporting an Existing Database......................................................................................... 3-3
Deleting Database Files....................................................................................................... 3-5
Modifying the Initialization Parameter File..................................................................... 3-5
Creating and Starting an Oracle Database Service ......................................................... 3-6
Starting an Oracle Database Instance ............................................................................... 3-7
Putting the CREATE DATABASE Statement in a Script ............................................... 3-7
the CREATE DATABASE Script....................................................................................... 3-8
Importing a Database .......................................................................................................... 3-8
Updating ORACLE_SID in the Registry .......................................................................... 3-9
Backing Up the New Database ....................................................................................... 3-10
Using ORADIM to Administer an Oracle Database Instance ........................................... 3-11
Creating an Instance......................................................................................................... 3-12
Starting an Instance and Services ................................................................................... 3-13
Stopping an Instance and Services ................................................................................. 3-14
Editing an Instance ........................................................................................................... 3-14
Deleting an Instance ......................................................................................................... 3-15
Database Migration from a 32-bit Windows Computer..................................................... 3-15
Backing Up a 32-Bit Oracle Database............................................................................. 3-15
Migrating an Oracle Database 11g Release 2 (11.2) ..................................................... 3-16
Migrating an Oracle Database 10g Release 2 (10.2) or Earlier Database................... 3-19

Postinstallation Configuration Tasks on Windows
4.1
Windows Firewall.......................................................................................................................
4.1.1
Oracle Executables Requiring Firewall Exceptions ........................................................
4.1.1.1
Firewall Exceptions for Oracle Database .................................................................
4.1.1.2
Firewall Exceptions for Oracle Database Examples ................................................
4.1.1.3
Firewall Exceptions for Oracle Gateways .................................................................
4.1.1.4
Firewall Exceptions for Oracle Clusterware and Oracle ASM ..............................
4.1.1.5
Firewall Exceptions for Other Oracle Products .......................................................
4.1.2
Configuring the Windows Firewall ..................................................................................

4-1
4-2
4-3
4-3
4-3
4-4
4-4
4-4

4.1.3
4.2
4.3
4.3.1
4.3.1.1
4.3.1.2
4.3.1.3
4.3.2
4.3.3
4.4
4.5
4.6
4.7
4.8
4.8.1
4.8.2
4.8.3

Administering a Database on Windows
5.1
5.1.1
5.1.2
5.1.3
5.1.4
5.2
5.3
5.4
5.5
5.5.1
5.6
5.7
5.8

Troubleshooting Windows Firewall Exceptions ............................................................. 4-5
Resetting Passwords for Default Accounts ............................................................................. 4-6
NTFS File System and Windows Registry Permissions ........................................................ 4-6
File Permissions ................................................................................................................... 4-6
File Permissions Set by Oracle Universal Installer .................................................. 4-6
File Permissions Set by Database Configuration Assistant .................................... 4-7
File Permissions Set by Database Upgrade Assistant ............................................ 4-7
Setting NTFS File System Security .................................................................................... 4-8
Setting Windows Registry Security................................................................................... 4-8
Configuring External Job Support for the Scheduler on Windows..................................... 4-9
Configuring Oracle Multimedia on Windows........................................................................ 4-9
Configuring Oracle Text on Windows.................................................................................. 4-10
Configuring Oracle Spatial on Windows ............................................................................. 4-11
Configuring Advanced Replication on Windows............................................................... 4-12
Checking Tablespace and Rollback Segment Requirements...................................... 4-12
Adding and Modifying Initialization Parameters ....................................................... 4-13
Monitoring Data Dictionary Tables ............................................................................... 4-13

Managing Oracle Database Services ........................................................................................ 5-1
Oracle Database Service Naming Conventions for Multiple Oracle Homes .............. 5-1
Starting Oracle Database Services ..................................................................................... 5-2
Stopping Oracle Database Services ................................................................................... 5-2
Auto-starting Oracle Database Services ........................................................................... 5-3
Starting and Shutting Down a Database with SQL*Plus ...................................................... 5-4
Starting and Shutting Down a Database Using Services ...................................................... 5-6
Starting Multiple Instances........................................................................................................ 5-8
Creating and Populating Password Files ................................................................................ 5-9
Viewing and Hiding the Password File ........................................................................ 5-10
Connecting Remotely to the Database as SYS .................................................................... 5-11
Automatically Encrypted Database Passwords ................................................................. 5-11
Archiving Redo Log Files ....................................................................................................... 5-12

Monitoring a Database on Windows
6.1
6.2
6.2.1
6.2.2
6.2.3
6.2.4
6.2.5
6.3
6.3.1
6.3.2
6.4
6.5

Database Monitoring Overview ...............................................................................................
Using Oracle Counters for Windows Performance Monitor ...............................................
Registry Information ...........................................................................................................
Accessing Oracle Counters for Windows Performance Monitor .................................
Modifying Views .................................................................................................................
Understanding Oracle Database Performance Objects ..................................................
Oracle Counters for Windows Performance Monitor Troubleshooting Information
Using Event Viewer....................................................................................................................
Reading Event Viewer ........................................................................................................
Managing Event Viewer .....................................................................................................
Trace Files.....................................................................................................................................
Alert Logs.....................................................................................................................................

6-1
6-2
6-2
6-3
6-3
6-4
6-5
6-6
6-7
6-8
6-8
6-9

Viewing Threads ......................................................................................................................... 6-9

6.6

Tuning Windows to Optimize Oracle Database
7.1
7.2
7.3
7.4
7.5
7.6
7.7
7.8
7.9
7.10
7.10.1
7.11
7.12

7-1
7-2
7-4
7-4
7-5
7-5
7-5
7-6
7-6
7-7
7-8
7-8
7-9

Performing Database Backup and Recovery with VSS
8.1
8.1.1
8.1.2
8.1.3
8.1.3.1
8.1.3.2
8.1.3.3
8.1.4
8.2
8.3
8.3.1
8.3.2
8.3.2.1
8.3.2.2
8.3.3
8.3.3.1
8.3.3.2
8.4
8.4.1
8.4.1.1
8.4.1.2
8.4.1.3
8.4.1.4
8.4.1.5
8.4.2
8.4.2.1
8.4.2.2
8.5
8.5.1

Windows Tuning Overview......................................................................................................
Large Page Support ....................................................................................................................
Reduce Priority of Foreground Applications on Server Console ........................................
Configure Windows Server to Be an Application Server .....................................................
Disable Unnecessary Services ...................................................................................................
Remove Unused Network Protocols .......................................................................................
Reset Network Protocol Bind Order ........................................................................................
Setting the Order of Multiple Network Interface Cards .......................................................
Apply Latest Reliable Windows Server Service Pack............................................................
Use Hardware or Operating System Striping.........................................................................
Multiple Striped Volumes for Sequential and Random Access....................................
Multiplex Windows Server Virtual Memory Paging File .....................................................
Close All Unnecessary Foreground Applications ..................................................................

Overview of Database Backup and Recovery with VSS ....................................................... 8-1
Purpose of Database Backup and Recovery with VSS ................................................... 8-1
Scope of This Chapter ......................................................................................................... 8-1
Basic Concepts of Database Backup and Recovery with VSS ....................................... 8-2
Component-Based Shadow Copies............................................................................ 8-2
Volume-Based Shadow Copies................................................................................... 8-2
Oracle VSS Backup Types ........................................................................................... 8-3
Basic Steps of Backup and Recovery with VSS ............................................................... 8-3
Installing and Uninstalling the Oracle VSS Writer Service................................................... 8-4
Backing Up a Database............................................................................................................... 8-5
About Component-Based Backups ................................................................................... 8-5
Backing Up a Database in ARCHIVELOG Mode ........................................................... 8-7
Making Component-Based Backups of an ARCHIVELOG Database .................. 8-7
Making Volume-Based Backups of an ARCHIVELOG Database ......................... 8-7
Backing Up a Database in NOARCHIVELOG Mode..................................................... 8-7
Making Component-Based Backups of a NOARCHIVELOG Database .............. 8-8
Making Volume-Based Backups of a NOARCHIVELOG Database ..................... 8-8
Restoring and Recovering a Database ..................................................................................... 8-8
Restoring and Recovering a Database in ARCHIVELOG Mode .................................. 8-8
Restoring the Server Parameter File .......................................................................... 8-9
Recovering from the Loss of All Control Files ...................................................... 8-10
Recovering Tablespaces or Datafiles ...................................................................... 8-10
Recovering All Tablespaces ..................................................................................... 8-10
Performing Disaster Recovery................................................................................. 8-11
Restoring a Database in NOARCHIVELOG Mode ..................................................... 8-11
Restoring Component-Based Backups of a NOARCHIVELOG Database........ 8-11
Restoring Volume-Based Backups of a NOARCHIVELOG Database............... 8-11
Integrating VSS with Third-Party Requester Applications ............................................... 8-11
Writer Control Commands.............................................................................................. 8-12

8.5.2
8.6
8.6.1
8.6.2

8-12
8-12
8-13
8-13

Authenticating Database Users with Windows
9.1
9.2
9.3
9.3.1
9.4

Control Commands for Database or All Tablespaces Component ...........................
Duplicating a Database ...........................................................................................................
Creating a Nonstandby Database from Shadow Copies ............................................
Creating a Standby Database From Shadow Copies ...................................................

Windows Native Authentication Overview ...........................................................................
Windows Authentication Protocols .........................................................................................
User Authentication and Role Authorization Methods ........................................................
Authentication and Authorization Methods To Use......................................................
Operating System Authentication Enabled at Installation ...................................................

9-1
9-2
9-2
9-3
9-3

Administering External Users and Roles on Windows
10.1
Oracle Administration Assistant for Windows ................................................................... 10-1
10.1.1
Managing a Remote Computer....................................................................................... 10-2
10.1.2
Adding a Computer and Saving Your Configuration................................................. 10-2
10.1.3
Granting Administrator Privileges for All Databases on a Computer ..................... 10-3
10.1.4
Granting Operator Privileges for All Databases on a Computer............................... 10-4
10.1.5
Connecting to a Database ................................................................................................ 10-5
10.1.5.1
Troubleshooting Connection Problems.................................................................. 10-6
10.1.6
Viewing Database Authentication Parameter Settings ............................................... 10-8
10.1.7
Creating an External Operating System User............................................................... 10-9
10.1.8
Creating a Local Database Role .................................................................................... 10-13
10.1.9
Creating an External Operating System Role ............................................................. 10-15
10.1.10
Granting Administrator Privileges for a Single Database ........................................ 10-18
10.1.11
Granting Operator Privileges for a Single Database ................................................. 10-19
10.2
Manually Administering External Users and Roles ......................................................... 10-20
10.2.1
Manually Creating an External Operating System User........................................... 10-21
10.2.1.1
External User Authentication Tasks on the Oracle Database Server ............... 10-21
10.2.1.2
External User Authentication Tasks on the Client Computer .......................... 10-24
10.2.2
Manually Granting Administrator and Operator Privileges for Databases .......... 10-25
10.2.2.1
SYSDBA/SYSOPER/SYSASM Authentication Tasks on the Oracle Database
Server 10-25
10.2.2.2
SYSDBA/SYSOPER/SYSASM Authentication Tasks on the Client Computer..........
10-26
10.2.3
Manually Creating an External Role............................................................................ 10-26
10.2.3.1
External Role Authorization Tasks on the Oracle Database Server ................. 10-27
10.2.3.2
External Role Authorization Tasks on the Client Computer ............................ 10-28
10.2.4
Manually Migrating Users ............................................................................................ 10-29

Storing Oracle Wallets in the Windows Registry
11.1
Storing Private Keys and Trust Points ..................................................................................
11.2
Storing User's Profile ...............................................................................................................
11.3
Registry Parameters for Wallet Storage................................................................................
11.3.1
Oracle Wallet Manager ....................................................................................................
11.3.1.1
Sharing Wallets and sqlnet.ora Files Among Multiple Databases .....................

11-1
11-1
11-1
11-2
11-2

vii

Oracle PKI Integration with Windows
12.1
Oracle Public Key Infrastructure ...........................................................................................
12.2
Windows Public Key Infrastructure......................................................................................
12.2.1
Microsoft Certificate Stores .............................................................................................
12.2.2
Microsoft Certificate Services..........................................................................................
12.2.3
Using Microsoft Certificate Stores with Oracle PKI Applications.............................

Using Oracle Database with Microsoft Active Directory
13.1
Microsoft Active Directory Support .....................................................................................
13.1.1
About Microsoft Active Directory..................................................................................
13.1.2
Accessing Active Directory ............................................................................................
13.2
Oracle Components That Integrate with Active Directory................................................
13.2.1
Directory Naming .............................................................................................................
13.2.2
Automatic Discovery of Directory Servers ...................................................................
13.2.3
Integration with Windows Tools....................................................................................
13.2.4
User Interface Extensions for Oracle Net Directory Naming.....................................
13.2.5
Enhancement of Directory Object Type Descriptions .................................................
13.2.6
Integration with Windows Login Credentials..............................................................
13.2.7
Oracle Directory Objects in Active Directory ...............................................................
13.3
Requirements for Using Oracle Database with Active Directory .....................................
13.3.1
Directory Naming Software Requirements ..................................................................
13.3.2
Creating an OracleContext ..............................................................................................
13.3.2.1
Network Configuration Assistant (NetCA)...........................................................
13.3.3
Oracle Schema Objects Creation.....................................................................................
13.4
Configuring Oracle Database to Use Active Directory ......................................................
13.5
Testing Connectivity................................................................................................................
13.5.1
Testing Connectivity from Client Computers ..............................................................
13.5.2
Testing Connectivity from Microsoft Tools ................................................................
13.6
Access Control List Management for Oracle Directory Objects .....................................
13.6.1
Security Groups ..............................................................................................................
13.6.1.1
OracleDBCreators....................................................................................................
13.6.1.2
OracleNetAdmins....................................................................................................
13.6.1.3
NetService Objects ..................................................................................................
13.6.2
Setting ACLs on NetService Entries.............................................................................
13.6.3
Adding and Deleting Security Group Members ........................................................

13-1
13-1
13-1
13-2
13-2
13-2
13-2
13-3
13-3
13-3
13-4
13-5
13-5
13-5
13-6
13-7
13-8
13-9
13-9
13-10
13-12
13-12
13-13
13-13
13-13
13-13
13-14

Oracle Database Specifications for Windows
14.1
14.1.1
14.1.2
14.1.3
14.2
14.3
14.4
14.5
14.6

viii

12-1
12-1
12-2
12-2
12-2

Initialization Parameter File Overview.................................................................................
Location of the Initialization Parameter File ................................................................
Editing The Initialization Parameter File ......................................................................
Database Configuration Assistant Renames init.ora ...................................................
Sample File................................................................................................................................
SGA_MAX_SIZE Parameter...................................................................................................
Initialization Parameters Without Windows-Specific Values ...........................................
Displaying Initialization Parameter Values .........................................................................
Uneditable Database Initialization Parameters ...................................................................

14-1
14-2
14-2
14-2
14-2
14-3
14-3
14-4
14-4

14.7

Calculating Database Limits................................................................................................... 14-5

Configuration Parameters and the Registry
15.1
About Configuration Parameters ..........................................................................................
15.2
Registry Overview ...................................................................................................................
15.3
Registry Parameters.................................................................................................................
15.3.1
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_HOME_NAME ........
15.3.1.1
MSHELP_TOOLS ......................................................................................................
15.3.1.2
NLS_LANG and Other Globalization Parameters ...............................................
15.3.1.3
ORA_CWD .................................................................................................................
15.3.1.4
ORA_SID_AUTOSTART ..........................................................................................
15.3.1.5
ORA_SID_PFILE........................................................................................................
15.3.1.6
ORA_SID_SHUTDOWN ..........................................................................................
15.3.1.7
ORA_SID_SHUTDOWN_TIMEOUT .....................................................................
15.3.1.8
ORA_SID_SHUTDOWNTYPE ................................................................................
15.3.1.9
ORA_TZFILE..............................................................................................................
15.3.1.10
ORACLE_AFFINITY.................................................................................................
15.3.1.11
ORACLE_BASE .........................................................................................................
15.3.1.12
ORACLE_GROUP_NAME ......................................................................................
15.3.1.13
ORACLE_HOME.......................................................................................................
15.3.1.14
ORACLE_HOME_KEY.............................................................................................
15.3.1.15
ORACLE_HOME_NAME ........................................................................................
15.3.1.16
ORACLE_PRIORITY ................................................................................................
15.3.1.17
ORACLE_SID.............................................................................................................
15.3.1.18
OSAUTH_PREFIX_DOMAIN .................................................................................
15.3.1.19
RDBMS_ARCHIVE ...................................................................................................
15.3.1.20
RDBMS_CONTROL ..................................................................................................
15.3.1.21
SQLPATH ...................................................................................................................
15.3.2
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE ................................................
15.3.2.1
INST_LOC ..................................................................................................................
15.3.2.2
OO4O...........................................................................................................................
15.3.3
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services......................
15.3.3.1
Parameters for Oracle Counters for Windows Performance Monitor...............
15.3.3.2
Parameters for Oracle Database Services...............................................................
15.4
Oracle RAC Registry Parameters...........................................................................................
15.4.1
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\OCR .....................................
15.5
Managing Registry Parameters with regedit .......................................................................
15.5.1
Modifying a Parameter Value with regedit ..................................................................
15.5.2
Adding a Registry Parameter with regedit...................................................................
15.6
Managing Registry Parameters with Oracle Administration Assistant for Windows
15.6.1
Starting Oracle Administration Assistant for Windows...........................................
15.6.2
Adding Oracle Home Parameters ................................................................................
15.6.3
Editing Oracle Home Parameters.................................................................................
15.6.4
Deleting Oracle Home Parameters...............................................................................
15.7
Modifying Oracle Counters for Windows Performance Monitor Parameters..............
15.7.1
Using operfcfg ................................................................................................................
15.7.2
Using Oracle Administration Assistant for Windows ..............................................

15-1
15-1
15-2
15-2
15-2
15-3
15-3
15-3
15-3
15-3
15-4
15-4
15-4
15-4
15-4
15-5
15-5
15-5
15-5
15-5
15-5
15-5
15-6
15-6
15-6
15-6
15-6
15-6
15-6
15-6
15-8
15-8
15-8
15-8
15-8
15-9
15-10
15-10
15-12
15-12
15-13
15-14
15-14
15-14

Developing Applications for Windows
16.1
Finding Information on Application Development for Windows ...................................
16.1.1
Java Enhancements...........................................................................................................
16.1.2
ODP.NET ...........................................................................................................................
16.1.3
Oracle Developer Tools for Visual Studio.....................................................................
16.1.4
Oracle Providers for ASP.NET........................................................................................
16.1.5
XML Support .....................................................................................................................
16.1.6
Support for Internet Applications ..................................................................................
16.1.7
Oracle Services For Microsoft Transaction Server .......................................................
16.1.8
Oracle Objects for OLE.....................................................................................................
16.1.9
Oracle Provider for OLE DB ...........................................................................................
16.1.10
Oracle ODBC Driver.........................................................................................................
16.1.11
Oracle COM Automation Feature ..................................................................................
16.1.12
Pro*C/C++ and Pro*COBOL Applications ..................................................................
16.2
Building External Procedures ................................................................................................
16.2.1
External Procedures Overview .......................................................................................
16.2.2
Installing and Configuring ..............................................................................................
16.2.2.1
Installing Oracle Database........................................................................................
16.2.2.2
Configuring Oracle Net Services.............................................................................
16.2.3
Writing an External Procedure .......................................................................................
16.2.4
Building a DLL ..................................................................................................................
16.2.5
Registering an External Procedure.................................................................................
16.2.6
Restricting Library-Related Privileges to Trusted Users Only...................................
16.2.7
Executing an External Procedure ...................................................................................
16.3
Multithreaded Agent Architecture........................................................................................
16.4
Debugging External Procedures ............................................................................................
16.4.1
Using Package DEBUG_EXTPROC .............................................................................
16.5
Accessing Text Files with UTL_FILE ..................................................................................
16.6
Accessing Web Data with Intercartridge Exchange..........................................................
16.6.1
Configuring Intercartridge Exchange ..........................................................................
16.6.2
Using Intercartridge Exchange .....................................................................................
16.6.2.1
Packaged Function UTL_HTTP.REQUEST .........................................................
16.6.2.2
Packaged Function UTL_HTTP.REQUEST_PIECES..........................................
16.6.3
UTL_HTTP Exception Conditions ...............................................................................
16.6.3.1
UTL_HTTP.REQUEST ............................................................................................
16.6.3.2
UTL_HTTP.REQUEST_PIECES ............................................................................
16.6.4
Exception Conditions and Error Messages .................................................................

Getting Started with Your Documentation

Storing Tablespaces on Raw Partitions
B.1
B.1.1
B.1.2
B.1.3
B.1.4

16-1
16-1
16-1
16-1
16-2
16-2
16-2
16-2
16-3
16-3
16-3
16-3
16-3
16-4
16-4
16-5
16-5
16-5
16-6
16-6
16-7
16-8
16-8
16-9
16-9
16-10
16-10
16-10
16-11
16-12
16-12
16-12
16-13
16-13
16-13
16-14

Raw Partition Overview ...........................................................................................................
Physical Disk .......................................................................................................................
Logical Partition..................................................................................................................
Physical Disk and Logical Partition Considerations .....................................................
Compatibility Issues...........................................................................................................

B-1
B-1
B-2
B-2
B-3

B.2
B.3
B.4

Oracle Net Services Configuration on Windows
C.1
C.2
C.2.1
C.3
C.4
C.4.1
C.4.2
C.4.3
C.5
C.5.1
C.5.2
C.5.3

Configuring Oracle Database to Communicate with ASM .................................................
Understanding Oracle Net Services Registry Parameters and Subkeys............................
Oracle Net Service Subkeys...............................................................................................
Listener Requirements ..............................................................................................................
Understanding Optional Configuration Parameters ............................................................
LOCAL .................................................................................................................................
TNS_ADMIN.......................................................................................................................
USE_SHARED_SOCKET ...................................................................................................
Advanced Network Configuration .........................................................................................
Configuring Authentication Method ...............................................................................
Configuring Security for Named Pipes Protocol ...........................................................
Modifying Configuration of External Procedures for Higher Security ......................

C-1
C-1
C-1
C-2
C-2
C-2
C-3
C-3
C-3
C-3
C-3
C-4

Error Messages on Windows
D.1
D.2
D.2.1
D.2.2
D.2.3
D.2.4
D.2.5
D.2.6
D.3
D.4

Creating a Raw Partition and a Mount Point ........................................................................ B-3
Creating a Tablespace in a Raw Partition............................................................................... B-4
Configuring Disks for Automatic Storage Management ..................................................... B-4

ORA-09275: CONNECT INTERNAL No Longer Supported..............................................
OSD-04000 to OSD-04599: Windows-Specific Oracle Database Messages .......................
File I/O Errors: OSD-04000 to OSD-04099 ......................................................................
Memory Errors: OSD-04100 to OSD-04199 .....................................................................
Process Errors: OSD-04200 to OSD-04299 .......................................................................
Loader Errors: OSD-04300 to OSD-04399......................................................................
Semaphore Errors: OSD-04400 to OSD-04499 ..............................................................
Miscellaneous Errors: OSD-04500 to OSD-04599 .........................................................
DIM-00000 to DIM-00039: ORADIM Command Syntax Errors........................................
Database Connection Issues ...................................................................................................

D-1
D-1
D-4
D-7
D-8
D-10
D-11
D-11
D-12
D-19

Oracle Database Windows/UNIX Differences
E.1
E.2
E.3
E.4
E.5
E.6
E.7
E.8
E.9
E.10
E.11
E.12
E.13
E.14
E.15

Automatic Startup and Shutdown ..........................................................................................
Background Processing and Batch Jobs..................................................................................
Diagnostic and Tuning Utilities...............................................................................................
Direct Writes to Disk .................................................................................................................
Dynamic Link Libraries (DLLs) ...............................................................................................
Hot Backups................................................................................................................................
Initialization Parameters: Multiple Database Writers ..........................................................
Install Accounts and Groups....................................................................................................
Installation ..................................................................................................................................
Memory Resources ....................................................................................................................
Microsoft Transaction Server ...................................................................................................
Multiple Oracle Homes and OFA............................................................................................
Processes and Threads ..............................................................................................................
Raw Partitions ............................................................................................................................
Services ........................................................................................................................................

E-1
E-2
E-2
E-2
E-3
E-3
E-3
E-3
E-3
E-4
E-4
E-4
E-5
E-5
E-6

Glossary
Index

xii

Preface
This guide provides platform-specific information about administering and
configuring Oracle Database 11g Release 2 (11.2) on the Microsoft Windows 32-Bit and
64-bit platforms:
■

Windows XP Professional

■

Windows Server 2003 - all editions

■

Windows Server 2003 R2 - all editions

■

Windows Vista - Business, Enterprise, and Ultimate editions

■

Windows Server 2008 - Standard, Enterprise, Datacenter, Web, and Foundation
editions. The specific operating system components that are not supported are
Hyper-V and Server Core.
Windows Server 2008 R2 (64-bit) - Standard, Enterprise, Datacenter, Web, and
Foundation editions. The specific operating system components that are not
supported are Hyper-V and Server Core.

■

Windows 7 - Professional, Enterprise, and Ultimate editions

■

Windows 8 - Pro and Enterprise editions

■

Windows 8.1 - Pro and Enterprise editions

■

Windows Server 2012 - Standard, Datacenter, Essentials, and Foundation editions

■

Windows Server 2012 R2 - Standard, Datacenter, Essentials, and Foundation
editions
Windows Multilingual User Interface Pack is supported on all
Windows operating systems.

Note:

This Preface contains these topics:
■

Audience

■

Documentation Accessibility

■

See Also:

2.4 Using Windows Tools
You can use Windows tools in various ways to manage Oracle Database:
■

Using Event Viewer to Monitor a Database

■

Using Microsoft Management Console to Administer a Database

■

Using Oracle Counters for Windows Performance Monitor

■

Using Registry Editor to Modify Configuration Information

■

Using Task Manager to Monitor Applications and Processes

■

Using Local Users and Groups to Manage Users and Groups

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

Database Tools on Windows 2-11

Using Windows Tools

Use Event Viewer to monitor Oracle Database events, such as:
■
■

■

Initialization of System Global Area for active instance
Initialization of Program Global Area (PGA) for background processes of active
instance
Connection to Oracle Database using AS SYSDBA

In addition, the operating system audit trail is logged in the Event Log, which is
viewable with the Event Viewer.
Chapter 6, "Monitoring a Database on Windows" for
specific instructions on accessing and using Event Viewer to monitor
Oracle Database events
See Also:

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

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

■

Configure OracleServiceSID

■

Modify registry parameters for all Oracle homes on the computer

■

Modify the computer host name, username, and password for the database being
monitored by Oracle Counters for Windows Performance Monitor
View and terminate an Oracle Database thread

2.4.3 Using Oracle Counters for Windows Performance Monitor
Oracle Counters for Windows Performance Monitor is integrated into Windows
Performance Monitor. This tool enables you to view performance of processors,
memory, cache, threads, and processes. Performance information provided includes
device usage, queue lengths, delays, throughput measurements, and internal
congestion measurements. This information is provided as charts, alerts, and reports.
You can use Oracle Counters for Windows Performance Monitor to monitor key Oracle
Database information, such as:
■

Library cache

■

Buffer cache

■

Data dictionary cache

■

Redo log buffer cache

■

Thread activity

You can use your findings to improve database performance.
"Using Oracle Counters for Windows Performance
Monitor" on page 6-2 for specific instructions on accessing and using
Oracle Counters for Windows Performance Monitor to monitor Oracle
Database performance
See Also:

2-12 Oracle Database Platform Guide

Using Windows Tools

2.4.4 Using Registry Editor to Modify Configuration Information
Oracle Database stores its configuration information in a structure known as the
registry. You can view and modify this configuration information through Registry
Editor. The registry contains configuration information for your computer and must
not be accessible for editing by inexperienced users. Only experienced administrators
should view and change this information.
Registry Editor displays configuration information in a format similar to Windows
Explorer. In the left-hand window is a tree-like format consisting of keys (or folders).
When one of these keys is highlighted, parameters and values assigned to that key are
displayed in the right-hand window.
When you install products from your media, configuration parameters are
automatically entered in the registry. These parameters are read each time your
Windows computer is started and whenever an Oracle Database product is started.
These parameters include settings for:
■

Oracle home directory

■

Language

■

Company name

■

Oracle home subdirectories for individual products

■

Individual products such as SQL*Plus

■

Services
Chapter 15, "Configuration Parameters and the Registry"
for definitions of Oracle Database configuration parameters and
specific instructions on using the registry to modify Oracle Database
configuration parameters
See Also:

2.4.5 Using Task Manager to Monitor Applications and Processes
Task Manager has four tabs:
■

■

Applications tab displays what applications run. This is useful for identifying and
ending unresponsive tasks. (Oracle Database does not appear as an application
because it runs as a service.)
Processes tab displays details of currently running processes and their resource
usage. Columns are customizable.
Performance tab graphically displays real-time CPU and memory usage, which is
useful for spotting sudden changes.
Networking tab graphically displays the network traffic taking place over the
computer’s network connections.

2.4.6 Using Local Users and Groups to Manage Users and Groups
Local Users and Groups enables you to manage users and groups on Windows.
Specifically, you can:
■

Create and modify local user accounts

■

Create and modify user profiles

■

Create, add, and delete local groups

Database Tools on Windows 2-13

Optional Windows Diagnostic and Tuning Utilities

2.5 Optional Windows Diagnostic and Tuning Utilities
Windows Resource Kit includes several diagnostic and tuning utilities.
Process Viewer summarizes resource usage by a process.
Process Monitor displays real-time file systems, registry and process-thread activity. It
combines Filemon and Regmon utilities and provides reliable process information.
Process Explorer provides a detailed display of resource usage by a process.
Task List displays resource usage and other details of a process when its processor
identifier or process name is given as an argument. This tool also displays a list of
executables and DLLs associated with a process.

2-14 Oracle Database Platform Guide

3
3

Postinstallation Database Creation on
Windows

This chapter describes how to create a database after installing Oracle Database, using
either Database Configuration Assistant or command-line tools.
This chapter contains these topics:
■

Naming Conventions for Oracle Database

■

Creating a Database on Windows Using Database Configuration Assistant

■

Creating a Database on Windows Using Command-Line Tools

■

Using ORADIM to Administer an Oracle Database Instance

■

Database Migration from a 32-bit Windows Computer

3.1 Naming Conventions for Oracle Database
All mounted Oracle Database servers in a network must have unique database names.
When a database is created, a name is associated with it and stored in its control files.
If you provide the database keyword, either in the CREATE DATABASE statement or
when prompted by Database Configuration Assistant, then that value becomes the
name for that database.
If you attempt to mount two Oracle Database servers with the same database name,
then you receive the following error during mounting of the second server:
ORA-01102: cannot mount database in EXCLUSIVE mode

If there are two or more Oracle Database servers on the same computer, but located in
different Oracle homes, then the following rules apply:
■

Each database name must be unique

■

Each SID must be unique

To change the name of an existing database, you must use the CREATE CONTROLFILE
statement to re-create your control files and specify a new database name.

3.2 Creating a Database on Windows Using Database Configuration
Assistant
Oracle recommends you use Database Configuration Assistant to create a database,
because it is easier. It offers the same interface and operates the same way on all
supported platforms, so no step-by-step procedures or screen shots are included here.

Postinstallation Database Creation on Windows 3-1

Creating a Database on Windows Using Command-Line Tools

Oracle Database 2 Day DBA for instructions on using
Database Configuration Assistant

See Also:

Database Configuration Assistant enables you to:
■

Create a Database

■

Configure Database Options in a database

■

Delete a Database

■

Manage Templates

An initialization parameter file is an ASCII text file containing parameters. Use this
file to create and modify a database using command-line tools. When you create a
database using Database Configuration Assistant, a server parameter file (SPFILE) is
created from the initialization parameter file, and the initialization parameter file is
renamed. Oracle does not recognize the renamed file as an initialization parameter file,
and it is not used after the instance is started.
If you want to modify an instance created with Database Configuration Assistant after
it starts, you must use ALTER SYSTEM statements. You cannot change the Server
Parameter File itself, because it is a binary file that cannot be browsed or edited using a
text editor. The location of the newly-created Server Parameter File is ORACLE_
HOME\database. The Server Parameter File file name is spfileSID.ora.
See Also: "Managing Initialization Parameters Using a Server
Parameter File" in Oracle Database Administrator's Guide

3.3 Creating a Database on Windows Using Command-Line Tools
This section describes how to create a new database manually. As part of its database
software files, Oracle Database provides a sample initialization parameter file, which
can be edited to suit your needs. You can choose to create database creation scripts
using DBCA.
Database creations are of three types:
■

Copy an existing database and delete the old database.

■

Copy an existing database and keep the old database.

■

Create a new database when no database exists on your system.

Table 3–1 summarizes tasks involved in creating a new database for each of these
database creation categories. Each step is explained in detail in the following
subsections.
Table 3–1

Manual Database Creation Tasks
Copy existing
database and delete
old database

Copy existing
database and keep
old database

Create new database when
no database exists on
system

Exporting an Existing
Database

Yes

Note 1

Not applicable

Deleting Database Files

Yes

Not applicable

Modifying the Initialization
Parameter File

Yes

Starting an Oracle Database
Instance

Yes

Task

3-2 Oracle Database Platform Guide

Creating a Database on Windows Using Command-Line Tools

Table 3–1 (Cont.) Manual Database Creation Tasks
Copy existing
database and delete
old database

Copy existing
database and keep
old database

Create new database when
no database exists on
system

Creating and Starting an
Oracle Database Service

Yes

Putting the CREATE
DATABASE Statement in a
Script

Yes

the CREATE DATABASE
Script

Yes

Importing a Database

Yes

Note 2

Not applicable

Task

Updating ORACLE_SID in the No
Registry

Only if you change the Yes
default SID

Backing Up the New Database Yes

Yes

Note 1
Yes if you copy data from the existing database to the new database; no otherwise.
Note 2
Yes if you import tables and other objects exported from the existing database; not
otherwise.
We use an example in the following sections to demonstrate how to create a database.
In this example, the existing database is the starter database with a SID of orcl located
in directory C:\app\username\product\11.2.0\oradata\orcl. You will copy orcl to
a new database with a database name and SID of prod located in directory
C:\app\username\product\11.2.0\oradata\prod. You will then delete starter
database orcl.

3.3.1 Exporting an Existing Database
You are required to export an existing database only if you intend to copy its contents
to a new database. If you are working with data from an earlier Oracle release, then
you can use Export for this task. If you are using Oracle Database 10g Release 1 (10.1)
or later data, then Oracle recommends that you use Data Pump Export because it
supports new Oracle Database 10g Release 1 (10.1) or later features, such as floating
points.
Although you can start Data Pump Export or Export in either parameter mode or
interactive mode, Oracle recommends parameter mode. Interactive mode provides less
functionality than parameter mode and exists for backward compatibility only.
The syntax for Data Pump Export parameter mode is:
C:\> expdp SYSTEM DUMPFILE=myexp.dmp FULL=y LOGFILE=myexp.log
Password: password

The syntax for Data Pump Export interactive mode is:
C:\> expdp SYSTEM
Password: password

Enter only the command expdp SYSTEM to begin an interactive session and let Data
Pump Export prompt you for information it needs.

Postinstallation Database Creation on Windows 3-3

Creating a Database on Windows Using Command-Line Tools

If you use parameter mode, then Data Pump Export considers
file names and directory names to be invalid if they contain one or
more blank spaces. The workaround is to enclose the full path in the
DUMPFILE= parameter in triple quotation marks. For example:
Note:

DUMPFILE="""C:\program files\export.dmp"""
If Data Pump Export is used in interactive mode, then the file name or
directory name can contain a space without quotation marks.
The syntax for Export parameter mode is:
C:\> exp SYSTEM FILE=myexp.dmp FULL=y LOG=myexp.log
Password: password

The syntax for Export interactive mode is:
C:\> exp SYSTEM
Password: password

Enter only the command exp SYSTEM to begin an interactive session and let Export
prompt you for information it needs.
Note: If you use parameter mode, then Export considers file names
and directory names to be invalid if they contain one or more blank
spaces. The workaround is to enclose the full path in the FILE=
parameter in triple quotation marks. For example:

FILE="""C:\program files\export.dmp"""
If Export is used in interactive mode, then the file name or directory
name can contain a space without quotation marks.
Oracle Database Utilities for more information on using
Data Pump Export or Export

See Also:

To export all data from an existing database to a new database:
1.

Set ORACLE_SID to the database service of the database whose contents you intend
to export. For example, if the database you intend to export is starter database
orcl, then enter the following at the command prompt. Note that there are no
spaces around the equal sign (=) character.
C:\> set ORACLE_SID=orcl

If the existing database is Oracle Database 10g Release 1 (10.1) or later, then start
Data Pump Export from the command prompt:
C:\> expdp SYSTEM DUMPFILE=myexp.dmp FULL=y LOG=myexp.log
Password: password

You now have a full database export of starter database orcl in file myexp.dmp. All
messages from Data Pump Export are logged in file myexp.log.
3.

If the existing database is before Oracle Database 10g Release 1 (10.1), then start
Export from the command prompt:
C:\> exp SYSTEM FILE=myexp.dmp FULL=y LOG=myexp.log
Password: password

3-4 Oracle Database Platform Guide

Creating a Database on Windows Using Command-Line Tools

You now have a full database export of starter database orcl in file myexp.dmp. All
messages from Export are logged in file myexp.log.

3.3.2 Deleting Database Files
Deleting database files is required only when you copy an existing database to a new
database to replace the old database. In the following example, you delete the database
files of starter database orcl.
To delete database files:
1.

Shut down starter database orcl at the command prompt:
C:\> oradim -SHUTDOWN -SID orcl -SHUTTYPE inst -SHUTMODE immediate

Delete the following files from directory
C:\app\username\product\11.2.0\oradata\orcl:

File Name

control01.ctl

drsys01.dbf

temp01.dbf

xdb01.dbf

control02.ctl

cwmlite01.dbf

tools01.dbf

redo01.log

control03.ctl

example01.dbf

undotbs01.dbf

redo02.log

index01.dbf

system01.dbf

user01.dbf

redo03.log

3.3.3 Modifying the Initialization Parameter File
To use starter database orcl as the basis for your new database, first copy ORACLE_
BASE\admin\orcl\pfile\init.ora. Second, put the copy in ORACLE_
BASE\admin\prod\pfile\init.ora. Third, modify the file as described in this section.
Beginning with Oracle9i Release 2 (9.2), nesting of quotation
marks using the backslash (\) escape character is no longer supported.
This may affect how Oracle Database interprets parameter values in
your initialization parameter file. For example, if you specified
CONTROL_FILES = "ctlfile\'1.ora" in releases before release 9.2, the
file name would be interpreted as ctlfile'1.ora. Starting with
release 9.2, the file name would be interpreted as ctlfile\'1.ora.
Note:

Oracle highly recommends modifying your parameter files to remove
such references. See Oracle Database Reference for other methods of
nesting quotation marks in initialization parameter values.
If you do not have an existing database on your system, then you cannot copy an
existing initialization parameter file to use as the basis for your new initialization
parameter file. However, you can use the sample initialization parameter file
initsmpl.ora provided in
ORACLE_HOME\admin\sample\pfile

as the basis for the initialization parameter file for database prod.
If you use initsmpl.ora as the basis for the initialization parameter file, then you
must set the following parameters to the indicated values, or you will not be able to
start database prod:

Postinstallation Database Creation on Windows 3-5

Creating a Database on Windows Using Command-Line Tools

■

DB_NAME=prod.domain
Parameter DB_NAME indicates the database name and must match the name used in
the CREATE DATABASE statement in "Putting the CREATE DATABASE Statement in
a Script" on page 3-7. You give a unique database name to each database. You can
use up to eight characters for a database name. The name is not required to match
the SID of the database service.

■

INSTANCE_NAME=prod.domain

■

SERVICE_NAMES=prod.domain

■

CONTROL_FILES = (
"C:\app\username\product\11.2.0\oradata\prod\control01.ctl",
"C:\app\username\product\11.2.0\oradata\prod\control02.ctl",
"C:\app\username\product\11.2.0\oradata\prod\control03.ctl")
Parameter CONTROL_FILES lists database control files. You do not have control files
on your file system at this point, because control files are created when you run
the CREATE DATABASE statement. Ensure that you specify the complete path and
file name, including drive letter.

■

DB_FILES=100
Modifying initialization parameter DB_FILES is not required, but it is
recommended to optimize performance. Set this parameter to the same number as
the value of the MAXDATAFILES option of the CREATE DATABASE statement. The value
of 100 is used for this example.
Oracle Database Reference for information on other
initialization parameters that you can add or modify

See Also:

The DIAGNOSTIC_DEST initialization parameter sets the location of the Automatic
Diagnostic Repository (ADR), which is a directory structure stored outside of the
database. The ADR is used in problem diagnostics.
DIAGNOSTIC_DEST = ORACLE_HOME\log if the environment variable ORACLE_BASE is not
set.
DIAGNOSTIC_DEST = ORACLE_BASE variable if the environment variable ORACLE_BASE is
set.
See Also: Oracle Database Installation Guide for Microsoft Windows for
information on ADR

3.3.4 Creating and Starting an Oracle Database Service
You are required to create and start an Oracle Database service only if you do one of
the following:
■

Copy an existing database to a new database and keep the old database

■

Create a new database when you have no other database to copy

Before you create the database, first create a Windows service to run the database. This
service is the Oracle Database process, oracle.exe, installed in the form of a Windows
service.
Use ORADIM to create the service. After it has been created, the service starts
automatically. See "Using ORADIM to Administer an Oracle Database Instance" on
page 3-11 for information on how to use ORADIM.
To create and start an Oracle Database service:
3-6 Oracle Database Platform Guide

Creating a Database on Windows Using Command-Line Tools

Run ORADIM from the command prompt:
C:\> oradim -NEW -SID prod -STARTMODE manual
-PFILE "C:\app\oracle\product\11.2.0\admin\prod\pfile\init.ora"

Note that the previously created initialization parameter file is specified, with
complete path, including drive name. You can check if the service is started in the
Services window of the Control Panel.
2.

Set ORACLE_SID to equal prod. Note that there are no spaces around the equal sign
(=) character:
C:\> set ORACLE_SID=prod

3.3.5 Starting an Oracle Database Instance
Start an instance without mounting a database.
SQL> STARTUP NOMOUNT

You are not required to specify the PFILE clause in this example, because the
initialization parameter file is stored in the default location. At this point, there is no
database. Only the SGA is created and background processes are started in
preparation for the creation of a new database.

3.3.6 Putting the CREATE DATABASE Statement in a Script
The CREATE DATABASE statement is a SQL statement that creates the database. A script
containing this statement can be used anytime you create a database.
The CREATE DATABASE statement may have the following parameters:
■

MAXDATAFILES - default value: 32, maximum value: 65534

■

MAXLOGFILES - default value: 32, maximum value: 255

When you run a CREATE DATABASE statement, Oracle Database performs several
operations depending upon clauses that you specified in the CREATE DATABASE
statement or initialization parameters that you have set.
Oracle Managed Files is a feature that works with the CREATE
DATABASE statement to simplify administration of Oracle Database.
Oracle Managed Files eliminates the requirement to directly manage
operating system files comprising an Oracle Database server, because
you specify operations in terms of database objects rather than file
names. For more information on using Oracle Managed Files see
Oracle Database Administrator's Guide.

Note:

To create database prod, copy and save the following statement in a file named
script_name.sql:
CREATE DATABASE prod
USER SYS IDENTIFIED BY sys_password
USER SYSTEM IDENTIFIED BY system_password
MAXLOGFILES 5
MAXDATAFILES 100
DATAFILE 'C:\app\oracle\product\11.2.0\oradata\prod\system01.dbf' SIZE 325M REUSE
AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
UNDO TABLESPACE "UNDOTBS" DATAFILE
'app\oracle\product\11.2.0\oradata\prod\undotbs01.dbf'

Postinstallation Database Creation on Windows 3-7

Creating a Database on Windows Using Command-Line Tools

SIZE 200M REUSE AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
CHARACTER SET WE8MSWIN1252
logfile 'C:\app\username\product\11.2.0\oradata\prod\redo01.log' size 100M reuse,
'C:\app\username\product\11.2.0\oradata\prod\redo02.log' size 100M reuse,
'C:\app\username\product\11.2.0\oradata\prod\redo03.log' size 100M reuse
EXTENT MANAGEMENT LOCAL;

3.3.7 the CREATE DATABASE Script
To use the SQL script to create a database:
1.

Verify that the service is started in the Control Panel. In this example, the service
name is OracleServicePROD, and its status column must display Started. If not,
then select the service name and choose Start.
You can also check the status of the service by entering the following at the
command prompt:
C:\> net START

A list of all Windows services currently on the system appears. If
OracleServicePROD is missing from the list, then enter:
C:\> net START OracleServicePROD
2.

Make PROD the current SID:
C:\> set ORACLE_SID=PROD

Add ORACLE_HOME\bin to your PATH environment variable:
set PATH=ORACLE_BASE\ORACLE_HOME\bin;%PATH%

Start SQL*Plus from the command prompt, and connect to the database as
SYSDBA:
C:\> sqlplus /NOLOG
SQL> CONNECT / AS SYSDBA

The message connected appears.
5.

Turn on spooling to save messages:
SQL> SPOOL script_name.log

Run script script_name.sql that you created in "Putting the CREATE DATABASE
Statement in a Script" on page 3-7:
SQL> C:\app\oracle\product\11.2.0\dbhome_1\rdbms\admin\script_name.sql;

If the database is successfully created, then the instance is started and the
following message appears numerous times: Statement processed

3.3.8 Importing a Database
You can use Data Pump Import (for Oracle Database 10g Release 1 (10.1) or later data)
or Import (for earlier data) to import the full export created in "Exporting an Existing
Database" on page 3-3 into the new database. Although you can start Data Pump
Import or Import using either parameter mode or interactive mode, Oracle
recommends parameter mode because it provides more functionality. Interactive mode
exists solely for backward compatibility.

3-8 Oracle Database Platform Guide

Creating a Database on Windows Using Command-Line Tools

The syntax for Data Pump Import parameter mode is:
C:\> impdp SYSTEM DUMPFILE=myexp.dmp FULL=y LOG=myexp.log
Password: password

The syntax for Data Pump Import interactive mode is:
C:\> impdp SYSTEM
Password: password

Enter only impdp SYSTEM to begin an interactive session and let Data Pump Import
prompt you for information it needs.
Note:
■

If you use parameter mode, then Data Pump Import considers file
names and directory names to be invalid if they contain one or
more blank spaces. The workaround is to enclose the full path in
the DUMPFILE= parameter in triple quotation marks. For example:
DUMPFILE="""C:\program files\export.dmp"""
If you use Data Pump Import in interactive mode, then the file
name or directory name can contain a space without quotation
marks.

■

If the original database from which the export file was generated
contains a tablespace that is not in the new database, then Import
tries to create that tablespace with associated datafiles.
The easy solution is to ensure that both databases contain the
same tablespaces. Datafiles are not required to be identical. Only
tablespace names are important.

Oracle Database Utilities for more information on using
Data Pump Import or Import

See Also:

3.3.9 Updating ORACLE_SID in the Registry
If this is the first database on the system or if you intend to make the new database the
default database, then you must make a change in the registry.
1.

Start Registry Editor at the command prompt:
C:\> regedit

The Registry Editor window appears.
2.

Choose subkey \HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME0 for the first Oracle
home on your computer. For subsequent installations to different Oracle homes on
the same computer, the path is \HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID
where ID is the unique number identifying the Oracle home.
Chapter 15, "Configuration Parameters and the Registry"
for more information on subkey locations for multiple Oracle homes
See Also:

Locate parameter ORACLE_SID on the right side of the Registry Editor window.

Double-click the parameter name and change the data to the new SID, which is
prod in this example.

Postinstallation Database Creation on Windows 3-9

Creating a Database on Windows Using Command-Line Tools

If you do not yet have parameter ORACLE_SID, because this is the first database on your
system, then you must create it.
To create parameter ORACLE_SID:
1.

Choose Add Value from the Edit menu.
The Add Value dialog appears:

Enter ORACLE_SID in the Value Name field.

Select REG_EXPAND_SZ (for an expandable string) in the Data Type list.

Click OK.
A string editor dialog appropriate for the data type appears:

Enter prod in the String field.

Click OK.
Registry Editor adds parameter ORACLE_SID.

Choose Exit from the Registry menu.
Registry Editor exits.

3.3.10 Backing Up the New Database
Caution: If anything goes wrong while operating the new database
without a backup, then you must repeat the database creation
procedure. Back up your database now to prevent loss of data.

To back up the new database:
1.

Shut down the database instance and stop the service:
C:\> oradim -SHUTDOWN -SID prod -SHUTTYPE srvc,inst -SHUTMODE immediate

3-10 Oracle Database Platform Guide

Using ORADIM to Administer an Oracle Database Instance

Although ORADIM returns the prompt immediately, you
must wait for the database and the service to stop completely before
continuing to Step 2. Wait until the Control Panel indicates service
OracleServicePROD has stopped. If you do not do this, then the
backup may be useless because it was taken while data was being
written to datafiles.
Caution:

Using the tool of your choice, back up database files.
Database files consist of the initialization parameter file, control files, online redo
log files, and datafiles.
When the backup is complete, you can start the database again, create users and
objects, if necessary, make any other changes, and use the database.
Be sure to back up the database after making any significant changes, such as
switching archiving mode or adding a tablespace or datafile.
See Also:

For more information on archiving, backup, and recovery

■

Oracle Database Concepts

■

Oracle Database Backup and Recovery User's Guide

■

Oracle Database 2 Day DBA

Caution: Do not store database files on a compressed drive. This can
result in write errors and decreased performance.

3.4 Using ORADIM to Administer an Oracle Database Instance
ORADIM is a command-line tool that is available with Oracle Database. You are
required to use ORADIM only if you are manually creating, deleting, or modifying
databases. Database Configuration Assistant is an easier tool to use for this purpose.
The following sections describe ORADIM commands and parameters. Note that each
command is preceded by a dash (-). To get a list of ORADIM parameters, enter:
oradim -? | -h | -help

Note: Specifying oradim without any options also returns a list of
ORADIM parameters and descriptions.

When you use ORADIM, a log file called oradim.log opens in ORACLE_HOME\database,
or in the directory specified by registry parameter ORA_CWD. All operations, whether
successful or failed, are logged in this file. You must check this file to verify success of
an operation.
If you have installed an Oracle Database service on Windows, then when logging in as
SYSTEM user (LocalSystem), with startup mode set to Automatic, it is possible that the
Oracle Database service starts but the database does not start automatically. The
following error message is written to file ORADIM.LOG in directory ORACLE_
HOME\database:
ORA-12640: Authentication adapter initialization failed

Postinstallation Database Creation on Windows 3-11

Using ORADIM to Administer an Oracle Database Instance

Oracle Enterprise Management Agent, Oracle Enterprise Manager Management Server
and Oracle Internet Directory may also fail, because they cannot connect to the
database for the same reason. The workarounds are:
■

Modify SQLNET.ORA
You can modify SQLNET.ORA, either by removing the line
sqlnet.authentication_services=(NTS)

or by changing it to
sqlnet.authentication_services=(NONE)
■

Start the database after the service starts
You can start the database manually after the Oracle Database service has started,
using SQL*Plus and connecting as SYSDBA.

■

Start the service as a specific user
See Also: Your operating system documentation for instructions on
starting services

where
■

-NEW indicates that you are creating a new instance. This is a mandatory
parameter.

■

-SID SID is the name of the instance to create.

■

-SRVC service_name is the name of the service to create (OracleServiceSID).

■

-ASMSID SID is the name of the Automatic Storage Management instance to create.

■

■
■

■

-ASMSRVC service_name is the name of the Automatic Storage Management
service to create.
-SYSPWD password is the system password.
-STARTMODE auto | manual indicates whether to start the instance when the Oracle
Database service is started. Default is manual.
-SRVCSTART system | demand indicates whether to start the Oracle Database
service on computer restart. Default is demand. Here, system specifies that the
service be configured to automatically start when the system boots or reboots.
Demand specifies that the user has to explicitly start the service.
-PFILE filename is the initialization parameter file to be used with this instance.
Ensure that you specify the complete path name of this file, including drive letter.
-SPFILE indicates that a server parameter file (SPFILE) be used during startup
instead of a PFILE.

3-12 Oracle Database Platform Guide

Using ORADIM to Administer an Oracle Database Instance

■

-SHUTMODE specifies how to stop an instance. It requires an argument and the
default is immediate. If SHUTMODE is omitted, then there is no attempt made to
shutdown the instance when the service is shutdown.
-TIMEOUT secs sets the maximum time to wait (in seconds) before the service for a
particular SID stops. The default is 90 seconds. It cannot be used without the
SHUTDOWN argument.
-RUNAS osusr/ospass ("run as") sets the operating system user with which the
Oracle service logs on to the system. You supply an operating system user name
and password, and the service logs on and runs with the privileges of that user. If
omitted, the service logs on to the system using the Local system account, which is
a privileged user.

For simplicity in demonstrating this feature, this example does
not perform the password management techniques that a deployed
system normally uses. In a production environment, follow the Oracle
Database password management guidelines, and disable any sample
accounts. See Oracle Database Security Guide for password management
guidelines and other security recommendations.

Note:

To create an instance called PROD, for example, you can enter:
C:\> oradim -NEW -SID prod -STARTMODE auto -PFILE
C:\app\oracle\product\11.2.0\admin\prod\pfile\init.ora

3.4.2 Starting an Instance and Services
To use ORADIM to start an instance and services, enter:
oradim -STARTUP -SID SID | -ASMSID SID [-SYSPWD password] [-STARTTYPE srvc |
inst | srvc,inst] [-PFILE filename | -SPFILE]

where
■

-STARTUP indicates that you are starting an instance that already exists. This is a
mandatory parameter.

■

-SID SID is the name of the instance to start.

■

-ASMSID SID is the name of the Automatic Storage Management instance to start.

■

-STARTTYPE srvc, inst indicates whether to start the service or the instance. One
or both values can be specified. If it is not specified, then the registry is checked for
the current setting.
-STARTTYPE srvc is equivalent to net start oracleservice from the
command line.
-STARTTYPE inst is equivalent of startup within SQL*Plus.

■

-PFILE filename is the initialization parameter file to be used with this instance.
Ensure that you specify the complete path name of this file, including drive letter.
-SPFILE indicates that a server parameter file (SPFILE) be used during startup
instead of a PFILE.

To start an instance called puma, for example, you can enter:
C:\> oradim -STARTUP -SID puma -STARTTYPE inst -PFILE
C:\app\oracle\product\11.2.0\admin\prod\pfile\init.ora
Postinstallation Database Creation on Windows 3-13

Using ORADIM to Administer an Oracle Database Instance

3.4.3 Stopping an Instance and Services
The Enterprise Database Control service (OracleDBConsoleSID) is dependent on the
Oracle Database service (OracleServiceSID). You must stop the dependent Enterprise
Database Control service (if installed) before ORADIM to stop the database instance
service.
To use ORADIM to stop an instance, enter:
oradim -SHUTDOWN -SID SID | -ASMSID SID [-SYSPWD password]
[-SHUTTYPE srvc | inst | srvc,inst] [-SHUTMODE normal | immediate | abort]

where
■

-SHUTDOWN indicates that you are stopping an instance. This is a mandatory
parameter.

■

-SID SID specifies the name of the instance to stop.

■

-ASMSID SID is the name of the Automatic Storage Management instance to stop.

■

-SHUTTYPE srvc, inst indicates whether to stop the service or the instance. One or
both values can be specified. If it is not specified, then the registry is checked for
the current setting.
-SHUTMODE specifies how to stop an instance. This is an optional parameter. If you
do not specify how to stop an instance, then immediate is the default mode.

To stop an instance called puma, for example, you can enter:
C:\> oradim -SHUTDOWN -SID puma -SHUTTYPE srvc,inst

3.4.4 Editing an Instance
You can edit an existing instance to change such values as instance name, startup
mode, shutdown mode, and shutdown type. To use ORADIM to modify an instance,
enter:
oradim -EDIT -SID SID | -ASMSID SID [-SYSPWD password] [-STARTMODE auto |
manual] [-SRVCSTART system | demand] [-PFILE filename | -SPFILE][SHUTMODE normal
| immediate | abort] [SHUTTYPE srvc | inst | srvc,inst]

where
■

■

-EDIT indicates that you are modifying an instance. This is a mandatory
parameter.
-SID SID specifies the name of the instance to modify. This is a mandatory
parameter.
-ASMSID SID is the name of the Automatic Storage Management instance to
modify.
-STARTMODE indicates whether to start the instance when the Oracle Database
service is started. Default is manual.
-SRVCSTART system | demand indicates whether to start the Oracle Database
service on computer restart. Default is demand.
-PFILE filename specifies the initialization parameter file to be used with this
instance. Ensure that you specify the complete path name of this file, including
drive letter.
-SPFILE indicates that a server parameter file (SPFILE) be used during startup
instead of a PFILE.

3-14 Oracle Database Platform Guide

Database Migration from a 32-bit Windows Computer

■

-SHUTMODE specifies how to stop an instance. This is an optional parameter. If you
do not specify how to stop an instance, then immediate is the default mode.
-SHUTTYPE indicates whether to stop the service or the instance. One or both values
can be specified. If it is not specified, then the registry is checked for the current
setting.

To specify a new initialization parameter file for the instance prod, for example, you
can enter:
C:\> oradim -EDIT -SID prod -PFILE
C:\app\oracle\product\11.2.0\admin\lynx\pfile\init.ora

3.4.5 Deleting an Instance
The Enterprise Database Control service (OracleDBConsoleSID) is dependent on the
Oracle Database service (OracleServiceSID). You must stop the dependent Enterprise
Database Control service (if installed) before ORADIM to delete the database instance.
To use ORADIM to delete an instance, enter:
oradim -DELETE -SID SID | -ASMSID SID | -SRVC service_name | -ASMSRVC service_name

where
■

■
■

-DELETE indicates that you are deleting an instance or service. This is a mandatory
parameter.
-SID SID specifies the name of the SID to delete.
-SRVC service_name specifies the name of the service to delete (OracleServiceSID).
User should specify either SID or SRVC.
-ASMSID SID is the name of the Automatic Storage Management instance to delete.
-ASMSRVC service_name is the name of the Automatic Storage Management
service to delete.

To delete an instance called prod, for example, you can enter:
C:\> oradim -DELETE -SID prod

3.5 Database Migration from a 32-bit Windows Computer
This section contains these topics:
■

Backing Up a 32-Bit Oracle Database

■

Migrating an Oracle Database 11g Release 2 (11.2)

■

Migrating an Oracle Database 10g Release 2 (10.2) or Earlier Database
See Also: Oracle Database Upgrade Guide for information about
upgrading an earlier release of Oracle Database to Oracle Database
11g Release 2 (11.2)

3.5.1 Backing Up a 32-Bit Oracle Database
To back up a 32-bit Oracle home database:
1.

Start SQL*Plus:
C:\> sqlplus /NOLOG

Postinstallation Database Creation on Windows 3-15

Database Migration from a 32-bit Windows Computer

Connect to the database instance as SYSDBA:
SQL> CONNECT / AS SYSDBA;

Create a.trc file to use as a template to re-create the control files on the 64-bit
computer:
SQL> ALTER DATABASE BACKUP CONTROLFILE TO TRACE;

Shut down the database:
SQL> SHUTDOWN IMMEDIATE;

Perform a full offline backup of the database.
See Also: Oracle Database Backup and Recovery User's Guide for an
overview of backup and recovery solutions

3.5.2 Migrating an Oracle Database 11g Release 2 (11.2)
To migrate an Oracle Database 11g Release 2 (11.2) for 32-bit Windows to an Oracle
Database 11g Release 2 (11.2) for 64-bit Windows:
1.

Install Oracle Database 11g Release 2 (11.2) for 64-bit Windows.
See Also:

Oracle Database Installation Guide for Microsoft Windows

Create the new Oracle Database 11g Release 2 (11.2) service at the command
prompt:
C:\> ORADIM -NEW -SID SID [-INTPWD PASSWORD ]-MAXUSERS USERS
-STARTMODE AUTO -PFILE ORACLE_HOME\DATABASE\INITSID.ORA

The following table provides more information on the values you must supply.
Parameter

Description

SID

SID of the database you are migrating

PASSWORD

Password for the new Oracle Database 11g Release 2 (11.2) for 64-bit
Windows database. This is the password for the user connected with
SYSDBA privileges. The -INTPWD option is not required. If you do not
specify it, then operating system authentication is used, and no
password is required.

USERS

Maximum number of users who can be granted SYSDBA and SYSOPER
privileges

ORACLE_HOME

Oracle home directory. Ensure that you specify the full path name with
the -PFILE option, including drive letter of the Oracle home directory.

Copy the 32-bit datafiles to the new 64-bit Oracle home.

Copy the 32-bit configuration files to the 64-bit Oracle home.
a.

If your 32-bit initialization parameter file has an IFILE (include file) entry, then
copy the file specified by the IFILE entry to the 64-bit Oracle home and edit
the IFILE entry in the initialization parameter file to point to its new location.

If you have a password file that resides in the 32-bit Oracle home, then copy
the password file to the 64-bit Oracle home. The default 32-bit password file is
located in ORACLE_HOME\database\pwdSID.ora., where SID is your Oracle
instance ID.

3-16 Oracle Database Platform Guide

Database Migration from a 32-bit Windows Computer

In the 64-bit Oracle home, add the _SYSTEM_TRIG_ENABLED = false parameter to
the ORACLE_HOME\database\ORACLE_SID \init.ora file before changing the word
size.

Remove this parameter from the initialization file after the word size change is
complete.
See Also: Oracle Database Upgrade Guide for more information on
changing word size

Go to the 64-bit ORACLE_HOME\rdbms\admin directory from the command prompt.

Start SQL*Plus:
C:\> sqlplus /NOLOG

Connect to the database instance as SYSDBA:
SQL> CONNECT / AS SYSDBA;

10. Re-create the 64-bit control files using the CREATE CONTROLFILE command. Edit the

trace file created in "Backing Up a 32-Bit Oracle Database" on page 3-15 to change
the paths to the datafiles, log files and control files to point to the Oracle home on
the 64-bit computer. This creates the new control file in ORACLE_HOME\database.
Here is an example of a database named orcl32 on a 32-bit computer migrating to
orcl64 on a 64-bit computer:
CREATE CONTROLFILE REUSE DATABASE "T1" NORESETLOGS NOARCHIVELOG
MAXLOGFILES 32
MAXLOGMEMBERS 2
MAXDATAFILES 32
MAXINSTANCES 16
MAXLOGHISTORY 1815
LOGFILE
GROUP 1 'C:\app\oracle\product\11.2.0\oradata\orcl64\REDO03.LOG'
# was
'C:\app\oracle\product\11.2.0\oradata\orcl32\...LOG'
# on the 32-bit computer
GROUP 2 'C:\app\oracle\product\11.2.0\oradata\orcl64\REDO02.LOG'
GROUP 3 'C:\app\oracle\product\11.2.0\oradata\orcl64\REDO01.LOG'
DATAFILE
'C:\app\oracle\product\11.2.0\oradata\orcl64\SYSTEM01.DBF',
# was 'C:\app\oracle\product\11.2.0\oradata\orcl32\...DBF'
# on the 32-bit computer
'C:\app\oracle\product\11.2.0\oradata\orcl64\RBS01.DBF',
'C:\app\oracle\product\11.2.0\oradata\orcl64\USERS01.DBF',
'C:\app\oracle\product\11.2.0\oradata\orcl64\TEMP01.DBF',
'C:\app\oracle\product\11.2.0\oradata\orcl64\TOOLS01.DBF',
'C:\app\oracle\product\11.2.0\oradata\orcl64\INDX01.DBF',
'C:\app\oracle\product\11.2.0\oradata\orcl64\DR01.DBF'
CHARACTER SET WE8ISO8859P1;

SIZE 1M,

SIZE 1M,
SIZE 1M

11. Alter the init file from the 32-bit computer to include the new control file

generated in the preceding step.
12. Shut down the database:
SQL> SHUTDOWN IMMEDIATE;
13. Start the database in UPGRADE mode to run utlirp.sql:
SQL> STARTUP UPGRADE;

Postinstallation Database Creation on Windows 3-17

Database Migration from a 32-bit Windows Computer

You must use the PFILE option to specify the location of your initialization
parameter file.
14. Set the system to spool results to a log file for later verification of success. For

example:
SQL> SPOOL mig32-64.log;
15. Enter the following command to view the output of the script on-screen:
SQL> SET ECHO ON;
16. Recompile existing PL/SQL modules in the format required by the 64-bit Oracle

Database:
SQL> @utlirp.sql;
17. Turn off the spooling of script results to the log file:
SQL> SPOOL OFF;
18. Check the spool file and verify that the packages and procedures compiled

successfully. Correct any problems you find in this file.
19. Shut down the database:
SQL> SHUTDOWN IMMEDIATE;
20. Start the database:
SQL> STARTUP;
21. If the JServer JAVA Virtual Machine component is installed, perform the following

steps after connecting as SYS:
begin
update obj$ set status=5 where obj#=(select obj# from obj$,javasnm$
where owner#=0 and type#=29 and short(+)=name and
nvl(longdbcs,name)='oracle/aurora/rdbms/Compiler');
commit;
declare
cursor C1 is select
'DROP JAVA DATA "' || u.name || '"."' || o.name || '"'
from obj$ o,user$ u where o.type#=56 and u.user#=o.owner#;
ddl_statement varchar2(200);
iterations number;
previous_iterations number;
loop_count number;
my_err
number;
begin
previous_iterations := 10000000;
loop
-- To make sure we eventually stop, pick a max number of iterations
select count(*) into iterations from obj$ where type#=56;
exit when iterations=0 or iterations >= previous_iterations;
previous_iterations := iterations;
loop_count := 0;
open C1;
loop
begin
fetch C1 into ddl_statement;

3-18 Oracle Database Platform Guide

Database Migration from a 32-bit Windows Computer

exit when C1%NOTFOUND or loop_count > iterations;
exception when others then
my_err := sqlcode;
if my_err = -1555 then -- snapshot too old, re-execute fetch query
exit;
else
raise;
end if;
end;
initjvmaux.exec(ddl_statement);
loop_count := loop_count + 1;
end loop;
close C1;
end loop;
end;
commit;
initjvmaux.drp('delete from java$policy$shared$table');
update obj$ set status=1 where obj#=(select obj# from obj$,javasnm$
where owner#=0 and type#=29 and short(+)=name and
nvl(longdbcs,name)='oracle/aurora/rdbms/Compiler');
commit;
end;
/
create or replace java system;
/
22. Recompile existing PL/SQL modules in the format required by the 64-bit Oracle

Database:
SQL> @utlrp.sql;

3.5.3 Migrating an Oracle Database 10g Release 2 (10.2) or Earlier Database
To migrate an Oracle Database 10g Release 2 (10.2) to an Oracle Database 11g Release 2
(11.2) for 64-bit Windows:
1.

Perform steps 1 - 11 in "Migrating an Oracle Database 11g Release 2 (11.2)" on
page 3-16.

Shut down the database on the 64-bit computer:
SQL> SHUTDOWN IMMEDIATE;

Start the database migration:
SQL> STARTUP MIGRATE;

Migrate the database as described in Chapter 3, "Upgrading to the New Release"
in Oracle Database Upgrade Guide.

Shut down the database:
SQL> SHUTDOWN IMMEDIATE;

Restart the database:
SQL> STARTUP OPEN;

Postinstallation Database Creation on Windows 3-19

Database Migration from a 32-bit Windows Computer

3-20 Oracle Database Platform Guide

4
4

Postinstallation Configuration Tasks on
Windows
This chapter describes configuration tasks you can perform to increase security and
other configuration tasks you must perform before using Oracle Multimedia and other
Oracle options. Where appropriate, the chapter provides references to other guides for
those configuration tasks.
This chapter contains these topics:
■

Windows Firewall

■

Resetting Passwords for Default Accounts

■

NTFS File System and Windows Registry Permissions

■

Configuring External Job Support for the Scheduler on Windows

■

Configuring Oracle Multimedia on Windows

■

Configuring Oracle Text on Windows

■

Configuring Oracle Spatial on Windows

■

Configuring Advanced Replication on Windows
Directory path examples in this chapter follow Optimal
Flexible Architecture (OFA) guidelines. If you specified non-OFA
compliant directories during installation, then your directory paths
will differ. See Appendix B, "Optimal Flexible Architecture", in Oracle
Database Installation Guide for Microsoft Windows for more information.
Note:

4.1 Windows Firewall
By default, all newer Windows operating systems enable the Windows Firewall to
block virtually all TCP network ports to incoming connections. As a result, any Oracle
products that listen for incoming connections on a TCP port will not receive any of
those connection requests, and the clients making those connections will report errors.
Depending upon which Oracle products are installed and how they are used, some
postinstallation configuration of the Windows Firewall might be required for the
products to be functional on these operating systems.
This section contains these topics:
■

Oracle Executables Requiring Firewall Exceptions

■

Configuring the Windows Firewall

Postinstallation Configuration Tasks on Windows 4-1

Windows Firewall

■

Troubleshooting Windows Firewall Exceptions

4.1.1 Oracle Executables Requiring Firewall Exceptions
Table 4–1 lists the Oracle Database 10g Release 1 (10.1) or later executables that listen
on TCP ports on Windows. If they are in use and accepting connections from a remote
client computer, then Oracle recommends that you add them to the Windows Firewall
exceptions list to ensure correct operation. Except as noted, they can be found in
ORACLE_HOME\bin.
If multiple Oracle homes are in use, then several firewall
exceptions may be needed for the same executable: one for each home
from which that executable loads.

Note:

You must configure exceptions for the Windows Firewall if your system meets all of
the following conditions:
■

■

Oracle server-side components are installed on a Windows Server 2003, Windows
Server 2003 R2, Windows Server 2008, Windows 2008 R2, Windows Server 2012 or
Windows Server 2012 R2 system. The list of components includes the Oracle
Database, Oracle Grid Infrastructure, network listeners, or any Web servers or
services.
The Windows system in question accepts connections from other machines over
the network. If no other machines will be connecting to the Windows system to
access the Oracle software, then no postinstallation configuration steps are
required and the Oracle software will function as expected.
The Windows system in question is configured to run the Windows Firewall. If the
Windows Firewall is not enabled, then no postinstallation configuration steps are
required.

If all of the above conditions are met, then the Windows Firewall must be configured
to allow successful incoming connections to the Oracle software. To enable Oracle
software to accept connection requests, Windows Firewall needs to be configured by
either opening up specific static TCP ports in the firewall or by creating exceptions for
specific executables so they can receive connection requests on any ports they choose.
This firewall configuration can be done by one of the following methods:
■

■
■

From the Control Panel, select Windows Firewall. In the Windows Firewall
application, select the Exceptions tab and then click either Add Program or Add
Port to create exceptions for the Oracle software.
From the command prompt, use the netsh firewall add... command.
When Windows notifies you that a foreground application is attempting to listen
on a port, and gives you the opportunity to create an exception for that executable.
If you choose the create the exception in this way, the effect is the same as creating
an exception for the executable either through Control Panel or from the command
line.

The following sections list the Oracle Database 11g Release 2 executables that listen on
TCP ports on Windows, along with a brief description of the executable. It is
recommended that these executables (if in use and accepting connections from a
remote, client computer) be added to the exceptions list for the Windows Firewall to
ensure correct operation. In addition, if multiple Oracle homes are in use, firewall
exceptions may need to be created for the same executable, for example, oracle.exe,
multiple times, once for each Oracle home from which that executable loads.

4-2 Oracle Database Platform Guide

Windows Firewall

■

Firewall Exceptions for Oracle Database

■

Firewall Exceptions for Oracle Database Examples

■

Firewall Exceptions for Oracle Gateways

■

Firewall Exceptions for Oracle Clusterware and Oracle ASM

■

Firewall Exceptions for Other Oracle Products

4.1.1.1 Firewall Exceptions for Oracle Database
For basic database operation and connectivity from remote clients (SQL*Plus, OCI,
ODBC, OLE DB applications, and so on), the following executables must be added to
the Windows Firewall exception list:
■

Oracle_home\bin\oracle.exe - Oracle Database executable

■

Oracle_home\bin\tnslsnr.exe - Oracle Listener

For remote monitoring capabilities to be available for a database on Windows, the
following executables must be added to the Windows Firewall exception list:
■

Oracle_home\bin\emagent.exe - Oracle Database Control

■

Oracle_home\jdk\bin\java.exe- Java Virtual Machine

4.1.1.2 Firewall Exceptions for Oracle Database Examples
After installing the Oracle Database Examples, the following executables must be
added to the Windows Firewall exception list:
■

Oracle_home\opmn\bin\opmn.exe - Oracle Process Manager

■

Oracle_home\jdk\bin\java.exe - Java Virtual Machine

4.1.1.3 Firewall Exceptions for Oracle Gateways
If your Oracle database interacts with non-Oracle software through a gateway, then
you must add the gateway executable to the Windows Firewall exception list.
Table 4–1 table lists the gateway executables used to access non-Oracle software.
Table 4–1

Oracle Executables Requiring Windows Firewall Exceptions

File Name

Executable Name

omtsreco.exe

Oracle Services for Microsoft Transaction
Server

dg4sybs.exe

Oracle Database Gateway for Sybase

dg4tera.exe

Oracle Database Gateway for Teradata

dg4msql.exe

Oracle Database Gateway for SQL Server

dg4db2.exe

Oracle Database Gateway for DRDA

pg4arv.exe

Oracle Database Gateway for APPC

pg4t4ic.exe

Oracle Database Gateway for APPC

dg4mqs.exe

Oracle Database Gateway for WebSphere
MQ

dg4mqc.exe

Oracle Database Gateway for WebSphere
MQ

dg4odbc.exe

Oracle Database Gateway for ODBC

Postinstallation Configuration Tasks on Windows 4-3

Windows Firewall

4.1.1.4 Firewall Exceptions for Oracle Clusterware and Oracle ASM
If you installed the Oracle grid infrastructure software on the nodes in your cluster,
then you can enable the Windows Firewall only after adding the following executables
and ports to the Firewall exception list. The Firewall Exception list must be updated on
each node.
■
■

Grid_home\bin\gpnpd.exe - Grid Plug and Play daemon
Grid_home\bin\oracle.exe - Oracle ASM executable (if using Oracle ASM for
storage)

■

Grid_home\bin\racgvip.exe - Virtual Internet Protocol Configuration Assistant

■

Grid_home\bin\evmd.exe - OracleEVMService

■

Grid_home\bin\crsd.exe - OracleCRService

■

Grid_home\bin\ocssd.exe - OracleCSService

■

Grid_home\bin\octssd.exe - Cluster Time Synchronization Service daemon

■

Grid_home\bin\mDNSResponder.exe - multicast-DNS Responder Daemon

■

Grid_home\bin\gipcd.exe - Grid IPC daemon

■

Grid_home\bin\gnsd.exe - Grid Naming Service daemon

■

Grid_home\bin\ohasd.exe - OracleOHService

■

Grid_home\bin\TNSLSNR.EXE - SCAN listener and local listener for Oracle
Database and Oracle ASM

■

Grid_home\opmn\bin\ons.exe - Oracle Notification Service

■

Grid_home\jdk\jre\bin\java.exe - Java Virtual Machine

4.1.1.5 Firewall Exceptions for Other Oracle Products
In additional to all the previously listed exceptions, if you use any of the Oracle
software listed in, then you must create an exception for Windows Firewall for the
associated executable.
Table 4–2

Other Oracle Software Products Requiring Windows Firewall Exceptions

Oracle Software Product

Executable Name

Data Guard Manager

dgmgrl.exe

Oracle Internet Directory LDAP Server

oidldapd.exe

External Procedural Calls

extproc.exe

4.1.2 Configuring the Windows Firewall
Postinstallation configuration for the Windows Firewall must be undertaken if all of
the following conditions are met:
■

Oracle server-side components are installed.
These components include the Oracle Database, network listeners, and any Web
servers or services.

■

The computer services connections from other computers over a network.
If no other computers connect to the computer with the Oracle software, then no
postinstallation configuration steps are required and the Oracle software will
function as expected.

4-4 Oracle Database Platform Guide

Windows Firewall

■

The Windows Firewall is enabled.
If the Windows Firewall is not enabled, then no postinstallation configuration
steps are required.

You can configure Windows Firewall by opening specific static TCP ports in the
firewall or by creating exceptions for specific executables so that they are able to
receive connection requests on any ports they choose. To configure the firewall, from
the Control Panel, select Windows Firewall and then select Exceptions or enter netsh
firewall add... at the command line.
Alternatively, Windows will inform you if a foreground application is attempting to
listen on a port, and it will ask you if you want to create an exception for that
executable. If you choose to do so, then the effect is the same as creating an exception
for the executable either in the Control Panel or from the command line.
Windows 2008 and later operating systems do not provide
any information on applications attempting to listen on a port.
Instead, a security audit event is logged to signal that an application is
blocked.

Note:

4.1.3 Troubleshooting Windows Firewall Exceptions
If you cannot establish certain connections even after granting exceptions to the
executables listed in Table 4–1, then follow these steps to troubleshoot the installation:
1.

Examine Oracle configuration files (such as *.conf files), the Oracle key in the
Windows registry, and network configuration files in ORACLE_
HOME\network\admin.

Pay particular attention to any executable listed in ORACLE_
HOME\network\admin\listener.ora in a PROGRAM= clause. Each of these must be
granted an exception in the Windows Firewall, because a connection can be made
through the TNS Listener to that executable.

Examine Oracle trace files, log files, and other sources of diagnostic information
for details on failed connection attempts. Log and trace files on the database client
computer may contain useful error codes or troubleshooting information for failed
connection attempts. The Windows Firewall log file on the server may contain
useful information as well.

If the preceding troubleshooting steps do not resolve a specific configuration issue
on Windows XP Service Pack 2, then provide the output from command netsh
firewall show state verbose=enable to Oracle Support for diagnosis and
problem resolution.
See Also:
■

http://www.microsoft.com/downloads/details.aspx?FamilyID=a7
628646-131d-4617-bf68-f0532d8db131&displaylang=en
for information on Windows Firewall troubleshooting

■

http://support.microsoft.com/kb/875357 for more information
on Windows Firewall configuration

Postinstallation Configuration Tasks on Windows 4-5

Resetting Passwords for Default Accounts

4.2 Resetting Passwords for Default Accounts
Oracle Database installs with many default accounts. Database Configuration
Assistant locks and expires most default database accounts upon successful
installation. Oracle recommends changing all user passwords immediately after
installation.
See Also: Oracle Database Administrator's Guide for more information
on default database accounts and passwords

4.3 NTFS File System and Windows Registry Permissions
Oracle recommends that you configure Oracle Database files, directories, and registry
settings to allow only authorized database administrators (DBAs) to have full control.
If you created a database using Database Configuration Assistant or upgraded a
database using Oracle Database Upgrade Assistant, then no further action is required.
This section describes the permissions automatically set by Oracle Universal Installer,
Database Configuration Assistant, and Oracle Database Upgrade Assistant and the
steps to set these permissions manually.
This section contains these topics:
■

File Permissions

■

Setting NTFS File System Security

■

Setting Windows Registry Security
See Also: Your operating system documentation for more
information about modifying NTFS file system and Windows registry
settings

4.3.1 File Permissions
Beginning with Oracle9i Release 2 (9.2), Oracle Universal Installer, Database
Configuration Assistant, and Database Upgrade Assistant set file permissions when
Oracle Database software is installed or upgraded.
This section contains these topics:
■

File Permissions Set by Oracle Universal Installer

■

File Permissions Set by Database Configuration Assistant

■

File Permissions Set by Database Upgrade Assistant

4.3.1.1 File Permissions Set by Oracle Universal Installer
During Oracle Database installation, by default Oracle Universal Installer installs
software in ORACLE_HOME. Oracle Universal Installer sets the following permissions to
this directory, and all files and directories under this directory:
■

Administrators - Full control

■

System - Full control

■

Authenticated Users - Read, Execute, and List Contents

4-6 Oracle Database Platform Guide

NTFS File System and Windows Registry Permissions

Important: If these accounts already exist and possess more

restrictive permissions, then the most restrictive permissions are
retained. If accounts other than Administrators, System, and
Authenticated Users already exist, then the permissions for these
accounts are removed.

4.3.1.2 File Permissions Set by Database Configuration Assistant
During database configuration, Database Configuration Assistant installs files and
directories in the following default locations, where database_name is the database
name or SID:
■

ORACLE_BASE\admin\database_name (administration file directories)

■

ORACLE_BASE\oradata\database_name (database file directories)

■

ORACLE_BASE\oradata\database_name (redo log files and control files)

■

ORACLE_HOME\database (SPFILESID.ORA)

Database Configuration Assistant sets the following permissions to these directories,
and all files and directories under these directories:
■

Administrators - Full Control

■

System - Full Control
Important: If these accounts already exist and possess more

restrictive permissions, then the most restrictive permissions are
retained. If accounts other than Administrators and System already
exist, then the permissions for these accounts are removed.

4.3.1.3 File Permissions Set by Database Upgrade Assistant
When an older version of the database is upgraded to Oracle Database 10g Release 1
(10.1) or later, Database Upgrade Assistant installs software in the following
directories, where database_name is the database name or SID:
■

ORACLE_BASE\admin\database_name (administration files)

■

ORACLE_BASE\oradata\database_name (database file directories)

■

ORACLE_BASE\oradata\database_name (redo log files and control files)

■

ORACLE_BASE\ORACLE_HOME\database (SPFILESID.ORA)

Database Upgrade Assistant sets the following permissions to these directories, and all
files and directories under these directories:
■

Administrators - Full Control

■

System - Full Control
Important: If these accounts already exist and possess more

restrictive permissions, then the most restrictive permissions are
retained. If accounts other than Administrators and System already
exist, then the permissions for these accounts are removed.
Beginning with Oracle Database 11g Release 2 (11.2), Database Upgrade Assistant can
also configure Enterprise Manager. If the "Enable daily backup" option is selected
Postinstallation Configuration Tasks on Windows 4-7

NTFS File System and Windows Registry Permissions

while configuring Enterprise Manager, then Database Upgrade Assistant shows a
separate screen asking for Fast Recovery Area. Database Upgrade Assistant will try to
create the directory structure in whatever file system location is specified if it does not
exist. It will put the same set of file permissions to this location. The default location
shown by DBUA for fast recovery area is:
■

ORACLE_BASE\recovery_area
See Also: "Oracle ACFS and File Access and Administration
Security" section of Oracle Automatic Storage Management
Administrator's Guide for more information about using Oracle ACFS
and administration security

4.3.2 Setting NTFS File System Security
To ensure that only authorized users have full file system permissions:
1.

Go to Windows Explorer.

Set the following permissions for each directory or file:

See Also:

Oracle Text Application Developer's Guide

Configuring Oracle Text Using Database Configuration Assistant
To use Database Configuration Assistant to configure Oracle Database for use with
Oracle Text at the time you create the database, simply select Oracle Text as the option
to configure when prompted.
To configure the database at a later time:
1.

Start Database Configuration Assistant.
From the Start menu, select Programs, then select Oracle - HOME_NAME, then
select Configuration and Migration Tools and then select Database
Configuration Assistant.

Select Configure database options in a database.

Select the database to modify when prompted.

Select Oracle Text as the option to configure when prompted.

4.7 Configuring Oracle Spatial on Windows
Oracle Spatial makes 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. Locations of
cities, roads, and political boundaries are projected onto a two-dimensional display or
piece of paper, preserving relative positions and relative distances of objects.
If you install Oracle Spatial through Enterprise Edition, then no manual configuration
is required. All Oracle Spatial configuration tasks are performed automatically.
If you install both Oracle Spatial and Oracle Database together through Enterprise
Edition or Standard Edition Custom installation, then Database Configuration
Assistant starts automatically at the end of installation. If you choose Custom
installation and select Create new database, then the assistant asks if Oracle Spatial is
to be configured automatically.
If you install Oracle Spatial during a separate installation from Enterprise Edition, then
you must either start Database Configuration Assistant and select Configure database
options in a database or configure Oracle Spatial manually.
To configure Oracle Spatial manually:
1.

Start SQL*Plus at the command prompt:
C:\> sqlplus /NOLOG

Postinstallation Configuration Tasks on Windows 4-11

Configuring Advanced Replication on Windows

Connect to Oracle Database with account SYSDBA:
SQL> CONNECT / AS SYSDBA

Start the database (if necessary):
SQL> STARTUP

Run script ordinst.sql:
SQL> ORACLE_HOME\ord\admin\ordinst.sql SYSAUX SYSAUX

Connect to the database as user SYSTEM:
SQL> CONNECT SYSTEM
Enter password: system_password

Run script mdinst.sql:
SQL> ORACLE_HOME\md\admin\mdinst.sql

Exit SQL*Plus:
SQL> EXIT

Script mdinst.sql has a variable %MD_SYS_PASSWORD% that
Oracle Universal Installer will instantiate at installation time.
Therefore, if you have changed the mdsys user's password, then
during a manual installation remember to update script mdinst.sql
with that password.
Note:

4.8 Configuring Advanced Replication on Windows
Oracle Database installs replication packages and procedures automatically rather
than as a separate manual process. There are many configuration and usage
possibilities with Advanced Replication.
This section describes how to manually configure Advanced Replication in Oracle
Database. Follow the instructions only if you add Advanced Replication to an
installation of Oracle Database that was not previously configured with this feature.
See Also: Oracle Database Advanced Replication for more information
about Advanced Replication and for definitions of master sites and
materialized view sites

Configuring Advanced Replication consists of the following steps:
■

Checking Tablespace and Rollback Segment Requirements

■

Adding and Modifying Initialization Parameters

■

Monitoring Data Dictionary Tables

4.8.1 Checking Tablespace and Rollback Segment Requirements
Recommended tablespace and rollback segment requirements for Advanced
Replication are shown in Table 4–3.

4-12 Oracle Database Platform Guide

Configuring Advanced Replication on Windows

Table 4–3

Advanced Replication Tablespace/Rollback Segment Requirements

Tablespace/Rollback Segment

Minimum Free Space

SYSTEM

20 MB

UNDO TABLESPACE

10 MB

RBS

5 MB

TEMP

10 MB

USERS

No specific requirement

Note:

Replication triggers and procedures are stored here.

4.8.2 Adding and Modifying Initialization Parameters
If you use Advanced Replication, then certain parameter values must be added to the
initialization parameter file, and others must be set to recommended values. Parameter
names and values for the master site and materialized view sites are shown in
Table 4–4.
Table 4–4

Advanced Replication Initialization Parameters

Parameter Name

Recommended Value

Site

JAVA_POOL_SIZE

50 MB

master

DISTRIBUTED_LOCK_TIMEOUT

300 seconds

master

GLOBAL_NAMES

TRUE

master

OPEN_LINKS

master

PROCESSES

Add 9 to current value

master

JOB_QUEUE-PROCESSES

2 Note

master

JOB_QUEUE_PROCESSES

materialized view

Note
Depends on number of n-way sites.

4.8.3 Monitoring Data Dictionary Tables
If you use Advanced Replication and intend to set up a large number of replicated
objects, then you are required to monitor the following data dictionary tables with the
SQL SELECT command:
■

ARGUMENT$

■

IDL_CHAR$

■

IDL_UB1$

■

IDL_UB2$

■

IDL_SB4$

■

I_ARGUMENT1

■

I_SOURCE1I$

■

SOURCE$

Postinstallation Configuration Tasks on Windows 4-13

Configuring Advanced Replication on Windows

■

TRIGGER

If necessary, increase storage parameters to accommodate storage requirements of
large numbers of replicated objects.

4-14 Oracle Database Platform Guide

5
5

Administering a Database on Windows
This chapter describes how to administer Oracle Database for Windows.
This chapter contains these topics:
■

Managing Oracle Database Services

■

Starting and Shutting Down a Database with SQL*Plus

■

Starting and Shutting Down a Database Using Services

■

Starting Multiple Instances

■

Creating and Populating Password Files

■

Connecting Remotely to the Database as SYS

■

Automatically Encrypted Database Passwords

■

Archiving Redo Log Files

5.1 Managing Oracle Database Services
This section tells you how to manage the services that Oracle Database installs on your
computer.
This section provides information on the following:
■

Oracle Database Service Naming Conventions for Multiple Oracle Homes

■

Starting Oracle Database Services

■

Stopping Oracle Database Services

■

Auto-starting Oracle Database Services

5.1.1 Oracle Database Service Naming Conventions for Multiple Oracle Homes
Oracle Database for Windows lets you have multiple Oracle homes on a single
computer. This feature, described in Appendix B, "Optimal Flexible Architecture", in
Oracle Database Installation Guide for Microsoft Windows, affects Oracle services naming
conventions. As you perform installations into Oracle home directories:
■

■

You must accept default Oracle home name provided or specify a different name
for each Oracle home directory.
You are prompted to give a system identifier and global database name for each
database installation.

Administering a Database on Windows 5-1

Managing Oracle Database Services

5.1.2 Starting Oracle Database Services
Oracle Database services must be started for you to use Oracle Database and its
products. You can start Oracle Database services from three different locations:
■

Control Panel

■

Command Prompt

■

Oracle Administration Assistant for Windows
You can start Oracle Database when you start
OracleServiceSID. See "Starting and Shutting Down a Database
Using Services" on page 5-6 for information on registry parameters
that enable you to do this.
Note:

Control Panel
To start Oracle Database services from the Control Panel:
1.

Access your Windows Services dialog.
See Also:

Your operating system documentation for instructions

Find the service to start in the list, select it, and click Start.
If you cannot find OracleServiceSID in the list, then use ORADIM to create it.

Click Close to exit the Services dialog.

Command Prompt
To start Oracle Database services from the command prompt, enter:
C:\> NET START service

where service is a specific service name, such as OracleServiceORCL.

Oracle Administration Assistant for Windows
To start Oracle Database services from Oracle Administration Assistant for Windows:
1.

From the Start menu, select Programs, then select Oracle - HOME_NAME, then
select Configuration and Migration Tools and then select Administration
Assistant for Windows.

Right-click the SID.
where SID is a specific instance name, such as orcl.

Click Start Service.
This starts service OracleServiceORCL.

5.1.3 Stopping Oracle Database Services
On occasion (for example, when re-installing Oracle Database), you must stop Oracle
Database services. You can stop Oracle Database services from three different
locations:
■

Control Panel

■

Command Prompt

5-2 Oracle Database Platform Guide

Managing Oracle Database Services

■

Oracle Administration Assistant for Windows
You can stop Oracle Database in normal, immediate, or abort
mode when you stop OracleServiceSID. See "Starting and Shutting
Down a Database Using Services" on page 5-6 for information on
registry parameters that enable you to do this.
Note:

Control Panel
To stop Oracle Database services from the Control Panel:
1.

Access your Windows Services dialog.
See Also:

Your operating system documentation for instructions

Select OracleHOME_NAMETNSListener and click Stop.
OracleHOME_NAMETNSListener is stopped.

Select OracleServiceSID and click Stop.

Click OK.
OracleServiceSID is stopped.

Command Prompt
To stop Oracle Database services from the command prompt, enter:
C:\> net STOP service

where service is a specific service name, such as OracleServiceORCL.

Oracle Administration Assistant for Windows
To stop Oracle Database services from Oracle Administration Assistant for Windows:
1.

From the Start menu, select Programs, then select Oracle - HOME_NAME, then
select Configuration and Migration Tools and then select Administration
Assistant for Windows.

Right-click the SID.
where SID is a specific instance name, such as orcl.

Click Stop Service.
This stops service OracleServiceORCL.

5.1.4 Auto-starting Oracle Database Services
Oracle Database services can be set to start automatically whenever the Windows
computer is restarted. You can turn auto-start on or off from two different locations:
■

Control Panel

■

Oracle Administration Assistant for Windows

Control Panel
To use the Control Panel to configure when and how Oracle Database is started:
1.

Access your Windows Services dialog.

Administering a Database on Windows 5-3

Starting and Shutting Down a Database with SQL*Plus

See Also:

Your operating system documentation for instructions

Select service OracleServiceSID and click Startup.

Choose Automatic from the Startup Type field.

Click OK.

Click Close to exit the Services dialog.

Oracle Administration Assistant for Windows
To automatically start Oracle Database services from Oracle Administration Assistant
for Windows:
1.

From the Start menu, select Programs, then select Oracle - HOME_NAME, then
select Configuration and Migration Tools and then select Administration
Assistant for Windows.

Right-click the SID.
where SID is a specific instance name, such as orcl.

Choose Startup/Shutdown Options.

Choose the Oracle Service tab.

Choose Automatic in Oracle Service Startup Type.

Click Apply.

Click OK.

5.2 Starting and Shutting Down a Database with SQL*Plus
These instructions assume that a database instance has been created.

5-4 Oracle Database Platform Guide

Starting and Shutting Down a Database with SQL*Plus

Directory path examples in this chapter follow Optimal
Flexible Architecture (OFA) guidelines. If you specified non-OFA
compliant directories during installation, then your directory paths
will differ. See Appendix B, "Optimal Flexible Architecture", in Oracle
Database Installation Guide for Microsoft Windows for more information.
Note:

To start or shut down Oracle Database:
1.

Go to your Oracle Database server.

Start SQL*Plus at the command prompt:
C:\> sqlplus /NOLOG

Connect to Oracle Database with username SYSDBA:
SQL> CONNECT / AS SYSDBA

To start a database, enter:
SQL> STARTUP [PFILE=path\filename]

This command uses the initialization parameter file specified in path\filename.
To start a database using a file named init2.ora located in
C:\app\oracle\product\11.2.0\admin\orcl\pfile

you would enter:
SQL> STARTUP PFILE=C:\app\oracle\product\11.2.0\admin\orcl\pfile\init2.ora

If no PFILE is specified, then the command looks for an SPFILE in ORACLE_
HOME\database. If the command finds one, then the command uses it to start the
database. If it does not find an SPFILE, then it uses the default initialization
parameter file located in ORACLE_BASE\ADMIN\db_name\pfile.
5.

To stop a database, enter:
SQL> SHUTDOWN [mode]

where mode is normal, immediate, or abort.
In a normal shutdown, Oracle Database waits for all currently-connected users to
disconnect and disallows any new connections before shutting down. This is the
default mode.
In an immediate shutdown, Oracle Database terminates and rolls back active
transactions, disconnects clients, and shuts down.
In an abort shutdown, Oracle Database terminates active transactions and
disconnects users; it does not roll back transactions. The database performs
automatic recovery and rollback the next time it is started. Use this mode only in
emergencies.
Chapter 2, "Database Tools on Windows" for a list of other
tools that can start Oracle Database and this guide for information on
options you can specify when starting your database.
See Also:

Administering a Database on Windows 5-5

Starting and Shutting Down a Database Using Services

5.3 Starting and Shutting Down a Database Using Services
You can start or shut down Oracle Database by starting or stopping service
OracleServiceSID in the Control Panel. Starting OracleServiceSID is equivalent to
using the STARTUP command or manually entering:
C:\> oradim -STARTUP -SID SID [-STARTTYPE srvc | inst | srvc,inst] [-PFILE
filename | -SPFILE]

Stopping OracleServiceSID is equivalent to using the SHUTDOWN command or
manually entering:
C:\> oradim -SHUTDOWN -SID SID [-SHUTTYPE srvc | inst | srvc,inst] [-SHUTMODE
normal | immediate | abort]

You can enable starting and stopping Oracle Database through OracleServiceSID two
different ways:
■

Oracle Administration Assistant for Windows

■

Setting Registry Parameters

Oracle Administration Assistant for Windows
To start or stop a database using Oracle Database services from Oracle Administration
Assistant for Windows:
1.

From the Start menu, select Programs, then select Oracle - HOME_NAME, then
select Configuration and Migration Tools and then select Administration
Assistant for Windows.

Right-click the SID.
where SID is a specific instance name, such as ORCL.

Choose Startup/Shutdown Options.

Choose the Oracle Instance tab.

Select Start up instance when service is started, Shut down instance when
service is stopped, or both.

5-6 Oracle Database Platform Guide

Starting and Shutting Down a Database Using Services

Setting Registry Parameters
To start or stop Oracle Database through Oracle Database Services, set the following
registry parameters to the indicated values:
■

ORA_SID_AUTOSTART
When set to true, the default value, this parameter causes Oracle Database to start
when OracleServiceSID is started.

■

ORA_SID_PFILE
This parameter sets the full path to the initialization parameter file. If this entry is
not present, then oradim will try to start the database with an SPFILE or PFILE
from ORACLE_HOME\database.

■

ORA_SHUTDOWN
When set to true, this parameter enables the selected instance of Oracle Database
to be shut down when OracleServiceSID is stopped. This includes any database
in the current Oracle home. Default value is false.

■

ORA_SID_SHUTDOWN
When set to true, the default value, this parameter causes the instance of Oracle
Database identified by the SID value to shut down when OracleServiceSID is
stopped manually‚Äîusing either the Control Panel or Net stop command.
Caution: If ORA_SHUTDOWN or ORA_SID_SHUTDOWN is set to false, then
manually shutting down OracleServiceSID will still shut down Oracle
Database. But it will be an abnormal shutdown, and Oracle does not
recommend it.

The following two registry parameters are optional:
■

ORA_SID_SHUTDOWNTYPE

Administering a Database on Windows 5-7

Starting Multiple Instances

This parameter controls database shutdown mode. Set it to a (abort), i
(immediate), or n (normal). Default mode is i (immediate) if you do not set this
parameter.
■

ORA_SID_SHUTDOWN_TIMEOUT
This parameter sets maximum time to wait before the service for a particular SID
stops.

The registry location of these required and optional parameters is determined by the
number of Oracle home directories on your computer. If you have only one Oracle
home directory, then these parameters belong in:
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOME0

If you have multiple Oracle home directories, then these parameters belong in:
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID

where ID is incremented for each additional Oracle home directory on your computer.
If you use ORADIM to create or edit instances, then it
automatically sets the relevant registry parameters to their
appropriate values.

Note:

Chapter 15, "Configuration Parameters and the Registry"
for instructions on adding and editing registry parameters
See Also:

Starting or Stopping OracleServiceSID from the Control Panel
1.

To start the database, start OracleServiceSID.
This automatically starts ORADIM and issues the -STARTUP command using the
initialization parameter file identified by ORA_SID_PFILE.

To stop the database, stop OracleServiceSID.
This automatically starts ORADIM, which issues the -SHUTDOWN command in the
mode indicated by ORA_SID_SHUTDOWNTYPE, and shuts down Oracle Database.
See Also: Your operating system documentation for instructions on
starting and stopping services.

5.4 Starting Multiple Instances
1.

Start the service for each instance using ORADIM or the Services dialog of the
Control Panel.

At the command prompt set the ORACLE_SID configuration parameter to the SID
for the first instance to run:
C:\> SET ORACLE_SID=SID

where SID is the name of the Oracle Database instance.
3.

Start SQL*Plus:
C:\> sqlplus /NOLOG

Connect AS SYSDBA:
SQL> CONNECT / AS SYSDBA

5-8 Oracle Database Platform Guide

Creating and Populating Password Files

Start up the first instance:
SQL> STARTUP PFILE=ORACLE_BASE\admin\db_name\pfile\init.ora

where ORACLE_BASE is c:\app\oracle\product\11.2.0 (unless you changed it
during installation) and db_name is the name of the instance.
6.

Repeat Steps 2-5 for the other instances to run.

5.5 Creating and Populating Password Files
Use Password Utility to create password files. Password Utility is automatically
installed with Oracle Database utilities. Password files are located in directory ORACLE_
HOME\database and are named PWDsid.ora, where SID identifies the Oracle Database
instance. Password files can be used for local or remote connections to Oracle
Database.
To create and populate a password file:
1.

Create a password file with the Password Utility:
C:\> orapwd FILE=PWDsid.ora ENTRIES=max_users

where
■

FILE specifies the password file name.

■

SID identifies the database instance.

■

ENTRIES sets maximum number of entries in password file. This corresponds
to maximum number of distinct users allowed to connect to the database
simultaneously with either the SYSDBA or the SYSOPER DBA privilege.

Set initialization parameter file parameter REMOTE_LOGIN_PASSWORDFILE to
exclusive, shared, or none.
The value exclusive specifies that only one instance can use the password file and
that the password file contains names other than SYS. In search of the password
file, Oracle Database looks in the registry for the value of parameter ORA_SID_
PWFILE. If no value is specified, then it looks in the registry for the value of
parameter ORA_PWFILE, which points to a file containing usernames, passwords,
and privileges. If that is not set, then it uses the default:
ORACLE_HOME\DATABASE\PWDsid.ORA.

The default value is shared. It specifies that multiple instances (for example, an
Oracle RAC environment) can use the password file. However, the only user
recognized by the password file is SYS. Other users 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 Oracle
releases. Oracle Database looks for the same files as it does when the value is
exclusive.
The value none specifies that Oracle Database ignores the password file and that
authentication of privileged users is handled by the Windows operating system.
3.

Start SQL*Plus:
C:\> sqlplus /NOLOG

Connect AS SYSDBA:

Administering a Database on Windows 5-9

Creating and Populating Password Files

SQL> CONNECT / AS SYSDBA

For an ASM instance, connect AS SYSASM:
SQL> CONNECT / AS SYSASM
5.

Start Oracle Database:
SQL> STARTUP

Grant appropriate privileges to each user. Users who must perform database
administration, for example, would be granted privilege SYSDBA:
SQL> GRANT SYSDBA TO db_administrator;

For an ASM instance:
SQL> GRANT SYSASM TO SYS;

If the grant is successful, then 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 usernames, user passwords,
and user privileges in password files.
Caution: Copying or manually moving password files may result in
ORADIM being unable to find a password to start an instance.

5.5.1 Viewing and Hiding the Password File
The password file is not automatically hidden. It can be made invisible and visible
again from two different locations:
■

Command Prompt

■

Windows Explorer
The password file must be visible before it can be moved,
copied, or deleted.

Note:

Command Prompt
1.

To see the password file, enter:
ORACLE_BASE\ORACLE_HOME\database> attrib

The password file is displayed as PWDsid.ora:
A
A
A
A
2.

ORACLE_HOME\database\oradba.exe
ORACLE_HOME\database\oradim.log
ORACLE_HOME\database\PWDsid.ora
ORACLE_HOME\database\SPFILEsid.ora

To make the password file invisible, enter:
ORACLE_HOME\database> attrib +H PWDsid.ora

To see the effect of the change, enter:

5-10 Oracle Database Platform Guide

Automatically Encrypted Database Passwords

ORACLE_HOME\database> attrib

The password file is now hidden:
A
A
A
A
4.

ORACLE_HOME\database\oradba.exe
ORACLE_HOME\database\oradim.log
ORACLE_HOME\database\PWDsid.ora
ORACLE_HOME\database\SPFILEsid.ora

To make the password file visible again, enter:
ORACLE_HOME\database> attrib -H PWDsid.ora

Windows Explorer
To make the password file invisible or visible again:
1.

Navigate to directory ORACLE_HOME\database.

Right-click PWDsid.ora.

Choose Properties.
The PWDsid.ora Properties dialog opens.

In Attributes, check or clear the checkbox next to Hidden.

Click OK.

To view or hide an invisible password file:
1.

Navigate to directory ORACLE_BASE\ORACLE_HOME\database.

Choose Folder Options from the View main menu.

Choose the View tab.

To view an invisible password file, choose Show hidden files and folders.

To hide a visible password file, choose Do not show hidden files and folders.

Click OK.

5.6 Connecting Remotely to the Database as SYS
When connecting to the starter database from a remote computer as SYS, you must
use a different password from the one described in Oracle Database Installation Guide for
Microsoft Windows when logging on with SYSDBA privileges. This is because the
password file enables database access in this situation and it requires the password
oracle for this purpose.

5.7 Automatically Encrypted Database Passwords
With Oracle Database, the password used to verify a remote database connection is
automatically encrypted. Whenever a user attempts a remote login, Oracle Database
encrypts the password before sending it to the remote database. If the connection fails,
then the failure is noted in the operating system audit log.
Note: Configuration parameter ORA_ENCRYPT_LOGIN is retained for
backward compatibility and is set to true by default. See Chapter 15,
"Configuration Parameters and the Registry" for instructions on
adding and setting configuration parameters in the registry.

Administering a Database on Windows 5-11

Archiving Redo Log Files

5.8 Archiving Redo Log Files
If you installed Oracle Database through the Typical installation, then it is created in
NOARCHIVELOG mode. If you created your database through the Custom option of
Database Configuration Assistant, then you had the choice of either ARCHIVELOG or
NOARCHIVELOG.
In NOARCHIVELOG mode, redo logs are not archived. Setting your archive mode to
ARCHIVELOG and enabling automatic archiving causes redo log files to be archived.
This protects Oracle Database from both instance and disk failure.
See Also: "Managing Archived Redo Logs" in Oracle Database
Administrator's Guide for more information about the archiving modes
and the archiving process.

5-12 Oracle Database Platform Guide

6
6

Monitoring a Database on Windows

This chapter describes how to monitor Oracle Database for Windows.
This chapter contains these topics:
■

Database Monitoring Overview

■

Using Oracle Counters for Windows Performance Monitor

■

Using Event Viewer

■

Trace Files

■

Alert Logs

■

Viewing Threads

6.1 Database Monitoring Overview
Table 6–1 describes tools that enable you to monitor Oracle Database.
Table 6–1

Database Monitoring Tools

Tool

Functionality

Oracle Counters for
Windows Performance
Monitor

Monitor database objects, such as CPU usage, buffer cache, or a
background process.

Event Viewer

Monitor database events.

Trace Files

Record occurrences and exceptions of database operations

Alert Logs

Record important information about error messages and
exceptions during database operations.

Oracle Enterprise Manager
Database Management
Packs

Monitor and tune using tools with real-time graphical
performance information.

Oracle Administration
Assistant for Windows

See Also: Your Oracle Enterprise Manager documentation set for
more information
View information on or terminate any Oracle thread.

See Also: Oracle Database Performance Tuning Guide for general
tuning information

Monitoring a Database on Windows 6-1

Using Oracle Counters for Windows Performance Monitor

6.2 Using Oracle Counters for Windows Performance Monitor
Oracle Counters for Windows Performance Monitor is a graphical tool for measuring
the performance of Oracle Database for Windows objects on a local server or other
servers on a network. This tool is the same in appearance and operation as Windows
Performance Monitor, except it has been loaded with Oracle Database performance
elements.
On each computer, you can view behavior of objects, such as buffer cache, data
dictionary cache, datafiles, threads, and processes. An object is a graphical
representation of an element in your system. Every element, resource, and device in
your system can be represented as an object.
Before using Oracle Counters for Windows Performance
Monitor to view Oracle-specific counters, you must specify the SYSTEM
password using operfcfg.exe or Oracle Administration Assistant for
Windows. See "Using operfcfg" on page 15-14 or "Using Oracle
Administration Assistant for Windows" on page 15-14 for instructions.
Note:

A set of counters is associated with each object. A counter is a unit of measurement
used by Performance Monitor to display activity. The type of activity the counter
measures depends on the type of object.
Certain types of objects and their respective counters are present on all systems. Other
counters, such as application-specific counters, appear only if the computer is the
associated software.
Each of these objects has an associated set of counters that provide information about
device usage, queue lengths, delays, and information used to measure throughput and
internal congestion.

6.2.1 Registry Information
When you install Oracle Counters for Windows Performance Monitor, values are
automatically set in the registry as described in Chapter 15, "Configuration Parameters
and the Registry".
Oracle Counters for Windows Performance Monitor lets you 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. Oracle recommends setting the security level on
each of these registry values.
Chapter 15, "Configuration Parameters and the Registry"
for instructions on how to use operfcfg
See Also:

To use Oracle Counters for Windows 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-Windows installations of Oracle Database by
changing Hostname registry value so it points to another computer specified in file
tnsnames.ora.

6-2 Oracle Database Platform Guide

Using Oracle Counters for Windows Performance Monitor

6.2.2 Accessing Oracle Counters for Windows Performance Monitor
To access Oracle Counters for Windows Performance Monitor:
From the Start menu, select Programs, then select Oracle - HOME_NAME, then select
Configuration and Migration Tools and then select Oracle Counters for Windows
Performance Monitor.
Oracle Counters for Windows Performance Monitor has four views you can choose
from the View menu:
■
■

Chart view displays database activity as it occurs.
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.
See Also: Your operating system documentation for complete
information about the four views

6.2.3 Modifying Views
For each view you can decide objects to monitor, what counters to use for each object,
and graphical attributes of the view. When an object is chosen, it is assigned a counter,
a color, and added to the status bar at the bottom of Oracle Counters for Windows
Performance Monitor.
To add objects to a view:
1.

Choose Add To (Chart, Alert, Log, Report) from the Edit menu. (This example
uses Add to Chart, but other dialogs are similar.)
The Add to Chart dialog appears.

In the Computer list, select the computer to monitor.

In the Object list, select the object or objects to monitor, then click Add.
If no data or Oracle Database objects appear, then either Oracle Database is not or
an invalid host string or password has been entered. If the database is not started,
then exit Oracle Counters for Windows Performance Monitor, start the database,
and restart Oracle Counters for Windows Performance Monitor.

In the Counter list, select one or more counters for each object you have selected.
Note that the contents of the Counter list change depending upon your selection in
the Object list. For details on how a counter works, highlight the counter and click
Explain.

In the Instance list, select an instance for this counter.

In the Color list, choose a color for the display of the selected counter.

In the Scale list, choose the scale at which to display the counter.

In the Width list, specify the width of the line on the graph.

In the Style list, choose a style for your graph line.

10. Click Done when you are finished.

The selections you have chosen to monitor are displayed.

Monitoring a Database on Windows 6-3

Using Oracle Counters for Windows Performance Monitor

6.2.4 Understanding Oracle Database Performance Objects
All Oracle Database system resources that can be monitored through Oracle Counters
for Windows Performance Monitor begin with 'Oracle Database'. This section lists
Oracle Database objects and describes their associated counters. These measures are
defined in:
ORACLE_HOME\dbs\PERFver.ora

See Also: Oracle Database Performance Tuning Guide for additional
information on these objects

You can monitor only one instance at a time using Oracle
Counters for Windows Performance Monitor on a given computer.

Note:

Oracle Database Buffer Cache
The counter is phyrds/gets %. The percentage of phyrds/gets is calculated as a Miss
ratio. The lower the Miss counter, the better. To improve performance, increase the
number of buffers in the buffer cache, if memory is available on the computer. This
value is not time-derived.
Oracle Database Redo Log Buffer
The counter is redo log space requests. The value of this counter must be near zero. If
this value increments consistently, then processes have had to wait for space in the
redo log buffer. In this case, it may be necessary to increase the size of the redo log
buffer.
Oracle Database Data Dictionary Cache
The counter is getmisses/gets %. The value of this counter must be less than 10 or 15%
for frequently accessed data dictionary caches. If the ratio continues to increase over
this threshold while your application is, then increase the amount of memory available
to the data dictionary cache.
To increase the memory available to the cache, increase the value of initialization
parameter SHARED_POOL_SIZE. This value is not time-derived.
See Also: Oracle Database Performance Tuning Guide for more detailed
information on tuning memory allocation in Oracle Database

Oracle Database Library Cache
The counter is reloads/pins %. This is the percentage of SQL statements, PL/SQL
blocks, and object definitions that required reparsing. Total Reloads must be near zero.
If the ratio of Reloads to Pins is greater than 1%, then reduce the library cache misses.
This value is not time-derived.
Oracle Database Datafiles
The counters are phyrds/sec and phywrts/sec. These values are time-derived. Disk
contention occurs when multiple processes try to access the same disk simultaneously.
Depending on results from monitoring disk activity, corrective actions could include:
■

Distributing I/O

■

Separating datafiles and redo log files

6-4 Oracle Database Platform Guide

Using Oracle Counters for Windows Performance Monitor

■

Separating tables and indexes

■

Striping table data

Oracle Database DBWR stats1
The two counters available, buffers scanned/sec and LRU scans/sec, are helpful in
tuning Buffer Cache. Buffers scanned/sec is the number of buffers DBWR scanned in
each second. The buffers scanned are on the LRU (Least Recently Used) list. LRU
scans/sec is the number of times DBWR scanned the (Least Recently Used) buffer list
in each second.
Oracle Database DBWR stats2
The two counters available, timeouts/sec and checkpoints/sec, are helpful in
determining how much work DBWR has been requested to perform. Timeouts/sec is
the number of times DBWR timed-out in each second. DBWR is on a three second
timeout interval. If DBWR has not been posted within a three second interval, then it
times out.
Checkpoints/sec is the number of checkpoint messages processed by database writer
in each second. Whenever a checkpoint occurs, DBWR must be messaged (posted) to
"write dirty buffers to disk".
Oracle Database Dynamic Space Management
The counter is recursive calls/sec. Dynamic extension causes Oracle Database to
execute SQL statements in addition to those SQL statements issued by user processes.
These SQL statements are called recursive calls.
If Oracle Database makes excessive recursive calls while an application is, then it may
be necessary to determine the cause. Examine the recursive calls statistic through
dynamic performance table V$SYSSTAT.
Oracle Database Free List
The counter is free list waits/requests %. Contention for free lists is reflected by
contention for free data blocks in buffer cache. You can determine if contention for free
lists is reducing performance by querying V$WAITSTAT.
If the number of free list waits for free blocks is greater than 1% of the total number of
requests, then consider adding more free lists to reduce contention.
Oracle Database Sorts
The available counters are sorts in memory/sec and sorts on disk/sec. The default sort
area size is adequate to hold all data for most sorts. However, if your application often
performs large sorts on data that does not fit into the sort area, then you may increase
sort area size.

6.2.5 Oracle Counters for Windows Performance Monitor Troubleshooting Information
If no data or Oracle Database objects appear in the Objects list of the Add to (Chart,
Alert, Log, Report) dialog, then:
1.

Ensure that Oracle Database instance is up. If it is not, then exit Oracle Counters
for Windows Performance Monitor, and start the database.

If the database instance is up but no data or Oracle Database objects appear, then
check the error file for Oracle Counters for Windows Performance Monitor:
ORACLE_HOME\dbs\OPERFver.log

Monitoring a Database on Windows 6-5

Using Event Viewer

If the log file indicates an invalid host string or password, then check the registry
for correct values for Hostname, Password, and Username. See "HKEY_LOCAL_
MACHINE\SYSTEM\CurrentControlSet\Services" on page 15-6 for further
information about these values.
3.

Restart Oracle Counters for Windows Performance Monitor.

6.3 Using Event Viewer
Oracle Database for Windows problems and other significant occurrences are recorded
as events in an application event log. View and manage these recorded events in Event
Viewer.
To access Event Viewer:
1.

From the Start menu, select Programs, then select Administrative Tools and then
select Event Viewer.
The Event Viewer window appears.

Choose Application from the Log menu.

Figure 6–1 displays the Application view window, Table 6–2 shows what is recorded in
each column, and Table 6–3 interprets icons that appear at the left edge of the viewer.
Figure 6–1 Application View Window

Table 6–2

Application View Definitions

Column Name

Definition

Date

Date event took place

Time

Time event took place

Source

Application that recorded event

See Also:

This chapter contains these topics:
■

Oracle Administration Assistant for Windows

■

Manually Administering External Users and Roles

10.1 Oracle Administration Assistant for Windows
Oracle Administration Assistant for Windows runs from Microsoft Management
Console and enables you to configure the following Oracle Database users and roles
so that the Windows operating system can authenticate them, and they can access
Oracle Database without a password:
■

Regular Windows domain users and global groups as external users

■

Windows database administrators (with the SYSDBA privilege)

■

Windows database operators (with the SYSOPER privilege)

In addition, Oracle Administration Assistant for Windows can create and grant local
and external database roles to Windows domain users and global groups.
With Oracle Administration Assistant for Windows, none of the following need be
done manually:
■

Create local groups that match the database system identifier and role

■

Assign domain users to these local groups

■

Authenticate users in SQL*Plus with
SQL> CREATE USER username IDENTIFIED EXTERNALLY

This section describes how to perform the following tasks with Oracle Administration
Assistant for Windows:
Administering External Users and Roles on Windows 10-1

Oracle Administration Assistant for Windows

■

Managing a Remote Computer

■

Adding a Computer and Saving Your Configuration

■

Granting Administrator Privileges for All Databases on a Computer

■

Granting Operator Privileges for All Databases on a Computer

■

Connecting to a Database

■

Viewing Database Authentication Parameter Settings

■

Creating an External Operating System User

■

Creating a Local Database Role

■

Creating an External Operating System Role

■

Granting Administrator Privileges for a Single Database

■

Granting Operator Privileges for a Single Database

10.1.1 Managing a Remote Computer
If you want to use Oracle Administration Assistant for Windows to manage a remote
computer, you must have administrator privileges for the remote computer. Oracle
Administration Assistant for Windows always creates users in Oracle Database with
the domain name as the prefix. If you are managing Oracle7 release 7.x or later
databases remotely, you must set registry parameter OSAUTH_PREFIX_DOMAIN to true on
the remote computer. This parameter is located in
HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_HOME_NAME

If a computer is not identified with a Domain Name System (DNS) domain name, you
will receive the following error message:
Calling query w32RegQueries1.7.0.17.0 RegGetValue
Key = HKEY_LOCAL_MACHINE
SubKey = SYSTEM\CurrentControlSet\Services\Tcpip\Parameters
Value = Domain
Query Exception: GetValueKeyNotFoundException
Query Exception Class: class oracle.sysman.oii.oiil.OiilQueryException
...

To assign a DNS name or change the primary DNS suffix, refer to your Microsoft
documentation.

10.1.2 Adding a Computer and Saving Your Configuration
When you use Oracle Administration Assistant for Windows for the first time, it adds
the local computer to its navigation tree. You can then add other computers.
To add a computer to the Microsoft Management Console tree:
1.

From the Start, select Programs, then select Oracle - HOME_NAME, then select
Configuration and Migration Tools and then select Administration Assistant for
Windows.
Microsoft Management Console starts.

Double-click Oracle Managed Objects.
The Computer icon appears.

Right-click Computers.

10-2 Oracle Database Platform Guide

Oracle Administration Assistant for Windows

Select New and then select Computer.
The Add Computer dialog appears.

Specify the domain and computer name for the computer on which Oracle
Database is installed.

Click OK.

Double-click Computers to display the computer you added.

Double-click the computer you added. Several nodes for authenticating database
administrators and operators appear.
The OS Database Administrators - Computer node creates an operating
system-authenticated database administrator with SYSDBA privileges for every
database instance on the computer. The OS Database Operators - Computer node
creates an operating system-authenticated database operator with SYSOPER
privileges for every database instance on the computer.

Save your configuration in a console file by choosing Save in the Console main
menu. You can now authenticate database administrators and operators for all
instances on the computer.

10.1.3 Granting Administrator Privileges for All Databases on a Computer
To grant database administrator (SYSDBA) privileges to database administrators (DBAs)
for all databases on a computer:
If you use a domain account for database installation, then the
domain user must be granted local administrative privileges. It is not
sufficient for the domain user to inherit membership privileges from
another group. You must ensure that the user performing the
installation is in the same domain, if not it results in an NTS
authentication failure.

Note:

From the Start, select Programs, then select Oracle - HOME_NAME, then select
Configuration and Migration Tools, and then select Administration Assistant for
Windows.
Oracle Administration Assistant for Windows starts.

Right-click OS Database Administrators - Computer.

Click Add/Remove.

Administering External Users and Roles on Windows 10-3

Oracle Administration Assistant for Windows

The OS Database Administrators - Computer for hostname dialog appears.

Select the domain of the user to which to grant SYSDBA privileges from the Domain
list.

Select the user.

Click Add.
The user now appears in the OS Database Administrators - Computer window.

Click OK.

10.1.4 Granting Operator Privileges for All Databases on a Computer
To grant database operator (SYSOPER) privileges to DBAs for all databases on a
computer:
1.

From the Start, select Programs, then select Oracle - HOME_NAME, then select
Configuration and Migration Tools and then select Administration Assistant for
Windows.
Oracle Administration Assistant for Windows starts.

Right-click OS Database Operators - Computer.

Click Add/Remove.
The OS Database Operators - Computer for hostname dialog appears.

10-4 Oracle Database Platform Guide

Oracle Administration Assistant for Windows

Select the domain of the user to which to grant SYSOPER privileges from the
Domain list.

Select the user.

Click Add.
The user now appears in the OS Database Operators - Computer window.

Click OK.

10.1.5 Connecting to a Database
To enable Secure Sockets Layer (SSL) when connecting to Oracle Database, start the
Oracle Database service and the listener service in the same user account as the wallet
created in Oracle Wallet Manager. Do not use the default user account in the Windows
Services dialog. If the Oracle Database service and the listener service are started in the
default user accounts, then SSL does not work, and the listener does not start. Support
for SSL is an Oracle Advanced Security feature. Oracle Wallet Manager is also an
Oracle Advanced Security feature.
See Also:

Oracle Database Security Guide for more information on SSL

support
To connect to a database:
1.

Right-click the database instance you want to access in the Microsoft Management
Console scope pane. In the example here, a connection is to be made to ORCL:

Administering External Users and Roles on Windows 10-5

Oracle Administration Assistant for Windows

Choose Connect Database.
If you connect to Oracle Database, the following Windows nodes appear beneath
the instance. If these nodes do not appear, double-click the instance.
■

External OS Users

■

Local Roles

■

External OS Roles

■

OS Database Administrators

■

OS Database Operators

10.1.5.1 Troubleshooting Connection Problems
When connecting to a local computer, Oracle Administration Assistant for Windows
first tries to connect to the database as a SYSDBA, using the Bequeath networking
protocol. When connecting to a remote computer, Oracle Administration Assistant for
Windows first tries to connect to the database using Windows native authentication as
a SYSDBA, using the TCP/IP networking protocol (port 1521 or the deprecated 1526). If
it is unsuccessful, one or more dialogs appear and prompt you to enter information to
connect to the database.
The dialog shown here appears because the Windows domain user with which you are
attempting to connect to Oracle Database is not recognized as an authenticated user

10-6 Oracle Database Platform Guide

Oracle Administration Assistant for Windows

with SYSDBA privileges. Enter an Oracle Database username and password to access
the database. To avoid being prompted with this dialog again, configure your domain
user to be a database administrator authenticated by the Windows operating system.

The next dialog appears either because you are not using the TCP/IP networking
protocol to connect to a remote installation of Oracle Database or because Oracle
Database is not. Using a protocol other than TCP/IP (Named Pipes for example)
causes this dialog to appear each time you attempt a remote connection.

If you do not want this dialog to appear each time, then change to the TCP/IP protocol
and make sure the Oracle Net Services listener for the database is listening on the
default port 1521 (or the deprecated default port 1526). Otherwise, this dialog appears
every time. Ensure also that Oracle Database is started.
1.

Enter the net service name with which to connect to Oracle Database. You must
enter a net service name regardless of the authentication method you select.

If you want to access the database with an Oracle Database user name and
password, select the Database Authenticated option. This user name and
password must exist in Oracle Database and have the SYSDBA privilege.

Administering External Users and Roles on Windows 10-7

Oracle Administration Assistant for Windows

If you want to access the database with the Windows domain user with which you
are currently logged in, select the OS Authenticated Connection as SYSDBA
option. This domain user must already be recognized by Windows as an
authenticated user with SYSDBA privileges. Otherwise, your logon fails.
Oracle Net Services provides a Trace Assistant tool that helps
diagnose connection problems by converting existing trace file text
into a more readable format. See "Using the Trace Assistant to
Examine Trace Files" in Oracle Database Net Services Administrator's
Guide.

Note:

10.1.6 Viewing Database Authentication Parameter Settings
To view database authentication parameter settings:
1.

Right-click the database.

Choose Properties.

The Properties dialog appears displaying the following parameter values:
■

OS_AUTHENT_PREFIX

■

OS_ROLES

OS_AUTHENT_PREFIX is an init.ora file parameter that authenticates external users
attempting to connect to Oracle Database with the user's Windows user name and
password. The value of this parameter is attached to the beginning of every user's
Windows username.
By default, the parameter is set to none ("") during Oracle Database creation.
Therefore, a Windows domain user name of frank is authenticated as user name
frank. If you set this parameter to xyz, then Windows domain user frank is
authenticated as user xyzfrank.
OS_ROLES is an init.ora file parameter that, if set to true, enables the Windows
operating system to manage authorization of an external role for a database user. By
default, OS_ROLES is set to false. You must set OS_ROLES to true and restart Oracle
Database before you can create external roles. If OS_ROLES is set to false, Oracle
Database manages granting and revoking of roles for database users.
If OS_ROLES is set to true, and you assign an external role to a Windows global group,
then it is granted only at the Windows 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 role assigned to an individual user in this global group through the Roles tab
of the User Name Properties dialog at a later time. Instead, you must use the field in
the Assign External OS Roles to a Global Group dialog to revoke the external role from
this global group (and therefore all its individual users).
External roles assigned to an individual domain user or local roles (with OS_ROLES set
to false) assigned to an individual domain user or Windows global group are not
affected by this issue. They can be edited or revoked.
If OS_ROLES is set to true, you cannot grant local roles in the database to any database
user. You must grant roles through Windows. See "Creating a Local Database Role" on
page 10-13 and "Creating an External Operating System Role" on page 10-15 for more
information.

10-8 Oracle Database Platform Guide

Oracle Administration Assistant for Windows

10.1.7 Creating an External Operating System User
The External OS Users node of Oracle Administration Assistant for Windows enables
you to authenticate a Windows user to access Oracle Database as an external user
without being prompted for a password. External users are typically regular database
users (not database administrators) to which you assign standard database roles (such
as DBA), but do not want to assign SYSDBA (database administrator) or SYSOPER
(database operator) privileges.
To create an external operating system user:
1.

Follow the steps in "Connecting to a Database" on page 10-5 to connect to a
database.

Right-click External OS Users. A contextual menu appears.

Choose Create.
Create External OS User Wizard starts, and the first of three wizard dialogs
appears. The first dialog is for Windows Users and Groups.

Administering External Users and Roles on Windows 10-9

Oracle Administration Assistant for Windows

In Domain Users and Groups select the domain in which your Windows domain
users and global groups are located.

Select the Windows domain users and global groups to which to grant access to
the database.

Click Add. The selected users and groups now appear in the New External OS
Users list.

Click Next. The Profile and Tablespace dialog appears.

10-10 Oracle Database Platform Guide

Oracle Administration Assistant for Windows

In the Assigned Profile list, select a profile for the new external users. A profile is
a named set of resource limits. If resource limits are enabled, Oracle Database
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.

In Tablespace Quota double-click the tablespace to assign a tablespace quota.

10. Click Next. The Roles dialog appears.

Administering External Users and Roles on Windows

10-11

Oracle Administration Assistant for Windows

11. In Available Roles select the database roles to grant to the new external users.
12. Click Grant.
13. Click Finish.
14. Right-click the external user for which you want to view information and select

Properties.
The assigned properties appear.
If you select a Windows global group for authentication when
using Oracle Administration Assistant for Windows, all users
currently in the group are added to Oracle Database. If at a later time,
you use a Windows tool to add or remove users in this Windows
global group, these updates are not reflected in Oracle Database. The
newly added or removed users must be explicitly added or removed
in Oracle Database with Oracle Administration Assistant for
Windows.

Note:

10-12 Oracle Database Platform Guide

Oracle Administration Assistant for Windows

10.1.8 Creating a Local Database Role
The Local Roles node of Oracle Administration Assistant for Windows enables you to
create a role and have it managed by the database. Once a local role is created, you can
grant or revoke that role to a database user. To create a local database role:
1.

Follow the steps in "Connecting to a Database" on page 10-5 to connect to a
database.

Right-click Local Roles for the database for which you want to create a local role.

Choose Create.
Create Local Role Wizard starts, and the first of three wizard dialogs appears. The
first dialog is for Name and Authentication.

Enter a local role name to use.

In Authentication select None if you want a user to use this local role without
being required to enter a password.
Select Password if you want 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 Oracle Database 2 Day DBA for additional information.
Enter the password to use with this role.
Confirm the password by entering it a second time.
Administering External Users and Roles on Windows

10-13

Oracle Administration Assistant for Windows

Click Next. The System Privileges dialog appears.

In Available System Privileges select the system privileges you want to assign to
the local role.

Click Grant to grant the selected system privileges to the local role.
The Granted System Privileges field displays the list of system privileges granted
to the local role. To revoke a system privilege, make an appropriate selection, then
choose Revoke.

If you want to grant Admin Option to this role, click the value in the Admin
Option column to display a list. This enables you to select Yes.

10. Click Next. The Roles dialog appears.

10-14 Oracle Database Platform Guide

Oracle Administration Assistant for Windows

11. In Available Roles select the roles you want to assign to the local role. Both local

roles and external roles appear in this list.
12. Click Grant to grant the selected roles to the role.

The Granted Roles field displays the list of roles granted to the role. Both local
roles and external roles can appear in this list. To revoke roles, make appropriate
selections, then choose Revoke.
13. Click Finish.

10.1.9 Creating an External Operating System Role
The External OS Roles node of Oracle Administration Assistant for Windows enables
you to create an external role and have it managed by the Windows operating system.
Once an external role is created, you can grant or revoke that role to a database user.
To create an external role:
1.

Follow the steps in "Connecting to a Database" on page 10-5 to connect to a
database.

Right-click External OS Roles for the database for which to create an external role.

Choose Create.

Administering External Users and Roles on Windows

10-15

Oracle Administration Assistant for Windows

Create External OS Role Wizard starts, and the first of three wizard dialogs
appears. The first dialog is for Name. Authentication: External appears in this
dialog to indicate that only external roles can be created.
Create External OS Role Wizard is available only if init.ora
parameter OS_ROLES is set to true. If it is set to false, then you must
first change it to true and then restart Oracle Database.

Note:

Enter an external role name to use. An external role is a role that is managed by
the Windows operating system.

Click Next.
The System Privileges dialog appears.

10-16 Oracle Database Platform Guide

Oracle Administration Assistant for Windows

In Available System Privileges select the system privileges you want to assign to
the external role.

Choose Grant to grant the selected system privileges to the external role.

The Granted System Privileges field displays the list of system privileges granted
to the external role. To revoke a system privilege, make an appropriate selection,
then click Revoke.

If you want to grant Admin Option to this role, choose the value in the Admin
Option column to display a list. This enables you to select Yes.

10. Click Next.

The Roles dialog appears.

Administering External Users and Roles on Windows

10-17

Oracle Administration Assistant for Windows

11. In Available Roles select the roles you want to assign to the external role. Both

local roles and external roles appear in this list.
12. Click Grant to grant the selected roles to the external role.

The Granted Roles field displays the list of roles granted to the external role.
13. Click Finish.

10.1.10 Granting Administrator Privileges for a Single Database
The OS Database Administrators node of Oracle Administration Assistant for
Windows enables you to authorize a Windows user with SYSDBA privileges for a
specific instance on a computer. To grant administrator (SYSDBA) privileges for a single
database:
1.

Follow the steps in "Connecting to a Database" on page 10-5 to connect to a
database.

Right-click OS Database Administrators.

Choose Add/Remove.
The OS Database Administrators for instance dialog appears. In the example
shown here, the instance is MARK:

10-18 Oracle Database Platform Guide

Oracle Administration Assistant for Windows

In Domain Users and Groups select the domain of the user to which to grant
SYSDBA privileges from the Domain list.

Select the user.
The user now appears in OS Database Administrators.

Click OK.

10.1.11 Granting Operator Privileges for a Single Database
The OS Database Operators node of Oracle Administration Assistant for Windows
enables you to authorize a Windows user with SYSOPER privileges for a specific
instance on a computer. To grant operator (SYSOPER) privileges for a single database:
1.

Follow the steps in "Connecting to a Database" on page 10-5 to connect to a
database.

Right-click OS Database Operators.

Choose Add/Remove.
The OS Database Operators for instance dialog appears. In the example shown
here, the instance is MARK:

Administering External Users and Roles on Windows

10-19

Manually Administering External Users and Roles

In Domain Users and Groups select the domain of the user to which to grant
SYSOPER privileges from the Domain list.

Select the user.

Click Add.
The user now appears in OS Database Operators.

Click OK.

10.2 Manually Administering External Users and Roles
Instead of using Oracle Administration Assistant for Windows, you can manually
configure administrators, operators, users, and roles to be authenticated by the
operating system. Manual configuration involves using Oracle Database command
line tools, editing the registry, and creating local groups in Active Directory Users and
Computers.
All of the following can be manually configured to access Oracle Database without a
password:
■

External operating system users

■

Windows database administrators (with SYSDBA privilege)

■

Windows database operators (with SYSOPER privilege)

In addition, you can manually create and grant local and external database roles to
Windows domain users and global groups.
This section describes:

10-20 Oracle Database Platform Guide

Manually Administering External Users and Roles

■

Manually Creating an External Operating System User

■

Manually Granting Administrator and Operator Privileges for Databases

■

Manually Creating an External Role

■

Manually Migrating Users
Note: Use extreme care when manually configuring administrators,
operators, users, and roles to be authenticated by the operating
system. If possible, use Oracle Administration Assistant for Windows
to perform configuration procedures.

10.2.1 Manually Creating an External Operating System User
This section describes how to authenticate external operating system users (not
database administrators) using Windows, so that a password is not required when
accessing the database. When you use Windows to authenticate external operating
system users, your database relies solely on the operating system to restrict access to
database usernames.
In the following procedure, two Windows usernames are authenticated:
■

Local user frank

■

Domain user frank on domain sales

Local user frank logs into its local Windows client computer to access an Oracle
Database server, which can be on a different computer. To access other databases and
resources on other computers, the local user must provide a user name and password
each time.
Domain user frank on domain sales logs into a sales domain that includes many
other Windows computers and resources, one of which contains an Oracle Database
server. The domain user can access all the resources the domain provides with a single
user name and password.
The procedure is divided into two sets of tasks performed on different computers:
■

External User Authentication Tasks on the Oracle Database Server

■

External User Authentication Tasks on the Client Computer

10.2.1.1 External User Authentication Tasks on the Oracle Database Server
Perform the following external user authentication tasks on the Oracle Database
server:
1.

Add parameter OS_AUTHENT_PREFIX to your init.ora file.
The OS_AUTHENT_PREFIX value is prefixed to local or domain usernames
attempting to connect to the server with the user's operating system name and
password. The prefixed user name is compared with Oracle Database usernames
in the database when a connection request is attempted. Using parameter OS_
AUTHENT_PREFIX with Windows native authentication methods is the
recommended method for performing secure, trusted client connections to your
server.

Set a value for OS_AUTHENT_PREFIX. Your choices are:
■

Any character string

Administering External Users and Roles on Windows

10-21

Manually Administering External Users and Roles

If you specify xyz, as in this procedure's example, then xyz is prefixed to the
beginning of the Windows user name (for example, xyzfrank for local user
frank or xyzsales\frank for domain user frank on domain sales). String
values are case insensitive.
■

"" (two double quotes with no space between)
This option is recommended, because it eliminates the need for any prefix to
Windows usernames (for example, frank for local user frank or sales\frank
for domain user frank on domain sales).

■

No value specified
If you do not specify a value for OS_AUTHENT_PREFIX, it defaults to OPS$ (for
example, OPS$frank for local user frank or OPS$sales\frank for domain user
frank on domain sales).

Create a Windows local user name for frank with the Computer Management
tool, or create a domain user name for frank with Active Directory Users and
Computers (if the appropriate name does not currently exist). See your operating
system documentation for detailed instructions.

Do this step only if you are not authenticating a domain name with a user (for
example, just frank instead of frank on domain sales). Otherwise, go to step 8.
a.

Start Registry Editor from the command prompt:
C:\> regedit

Go to HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID, where ID is the Oracle
home directory you want to edit.

Select Edit and then select Add Value.
The Add Value dialog appears:

Enter OSAUTH_PREFIX_DOMAIN in the Value Name field.

Choose REG_EXPAND_SZ from the Data Type list.

Click OK.
The String Editor dialog appears:

10-22 Oracle Database Platform Guide

Manually Administering External Users and Roles

Enter true in the String field to enable authentication at the domain level.
There may be multiple frank usernames on your network, including local user
frank, domain user frank on sales, and possibly several domain users frank on
other domains. Entering true enables the server to differentiate among them.
Entering false causes the domain to be ignored and local user frank to become
the default value of the operating system user returned to the server.

Click OK.
Registry Editor adds the parameter.

Choose Exit from the Registry menu.
Registry Editor exits.

Ensure that parameter SQLNET.AUTHENTICATION_SERVICES in file sqlnet.ora
contains nts.

Start SQL*Plus:
C:\> sqlplus /NOLOG

10. Connect to the database with the SYSTEM database administrator (DBA) name:
SQL> CONNECT SYSTEM
Enter password: system_password

Unless you have changed it, the SYSTEM password is MANAGER by default.
11. Create a local external user by entering:
SQL> CREATE USER xyzfrank IDENTIFIED EXTERNALLY;

where xyz is the value you chose for initialization parameter OS_AUTHENT_PREFIX,
and frank is the Windows local username.
12. Grant a local external user database roles by entering:
SQL> GRANT DBA TO xyzfrank;
13. Create a domain external user by entering:
SQL> CREATE USER "XYZSALES\FRANK" IDENTIFIED EXTERNALLY;

where XYZ is the value you chose for initialization parameter OS_AUTHENT_PREFIX,
and SALES\FRANK is the domain name and Windows domain username. Double
quotes are required and the entire syntax must be in uppercase.
14. Grant a domain external user database roles by entering:
SQL> GRANT DBA TO "XYZSALES\FRANK";

Double quotes are required and the entire syntax must be in uppercase.
15. Connect to the database with the SYSDBA name:
SQL> CONNECT / AS SYSDBA
16. Shut down the database:
SQL> SHUTDOWN
17. Restart the database:
SQL> STARTUP

Administering External Users and Roles on Windows

10-23

Manually Administering External Users and Roles

This causes the change to parameter OS_AUTHENT_PREFIX to take effect.

10.2.1.2 External User Authentication Tasks on the Client Computer
Perform the following external user authentication tasks on the client computer:
1.

Create Windows local or domain user name frank with the same user name and
password that exist on the Windows server (if the appropriate name does not
currently exist).

Ensure that parameter SQLNET.AUTHENTICATION_SERVICES in file sqlnet.ora
contains nts.

Use Oracle Net Configuration Assistant to configure a network connection from
your client computer to the Windows server on which Oracle Database is installed.
See Oracle Database Net Services Administrator's Guide for instructions.

Start SQL*Plus:
C:\> sqlplus /NOLOG

Connect to your Windows server:
SQL> CONNECT /@connect_identifier

where connect_identifier is the net service name for Oracle Database.
Oracle Database searches the data dictionary for an automatic login user name
corresponding to the Windows local or domain username, verifies it, and enables
connection as xyzfrank or xyzsales\frank.
6.

Verify that you have connected to Oracle Database as local or domain user frank
by viewing the roles assigned in steps 12 or 14 of "External User Authentication
Tasks on the Oracle Database Server".
SQL> SELECT * FROM USER_ROLE_PRIVS;

which outputs for local user frank:
USERNAME
GRANTED_ROLE
ADM DEF OS_
------------------------------ ------------------------------ --- --- --XYZFRANK
DBA
NO YES NO
1 row selected.

or, for domain user frank:
USERNAME
GRANTED_ROLE
ADM DEF OS_
------------------------------ ------------------------------ --- --- --XYZSALES\FRANK
DBA
NO YES NO
1 row selected.

Because the Oracle Database user name is the whole name xyzfrank or
xyzsales\frank, each object created by xyzfrank or xyzsales\frank (that is, table,
view, index, and so on) is prefixed by this name. For another user to reference the
table shark owned by xyzfrank, for example, the user must enter:
SQL> SELECT * FROM xyzfrank.shark

Automatic authorization is supported for all Oracle Net
protocols.
Note:

10-24 Oracle Database Platform Guide

Manually Administering External Users and Roles

10.2.2 Manually Granting Administrator and Operator Privileges for Databases
This section describes how to enable Windows to grant the database administrator
(SYSDBA), database operator (SYSOPER) and database administrator for ASM (SYSASM)
privileges to database administrators. With this privilege, database administrators can
issue the following commands from a client computer and connect to Oracle Database
without entering a password:
SQL> CONNECT / AS SYSOPER
SQL> CONNECT / AS SYSDBA
SQL> CONNECT / AS SYSASM

To enable this feature, the Windows local or domain user name of the database
administrator must belong to one of the Windows local groups listed in Table 10–1.
Table 10–1

Windows Local Groups with SYSDBA, SYSOPER, and SYSASM Privileges

Local Group

Privileges

ORA_OPER

SYSOPER privileges for all databases on a computer

ORA_DBANote

SYSDBA privileges for all databases on a computer

ORA_DBA

SYSASM privileges for all databases on a computer

ORA_SID_OPER

SYSOPER privileges for a single database (identified by SID)

ORA_SID_DBA

SYSDBA privileges for a single database (identified by SID)

ORA_SID_DBA

SYSASM privileges for a single database (identified by SID)

Note
ORA_DBA is automatically created during installation. See section "Operating System
Authentication Enabled at Installation" on on page 9-3 for information.
The manual procedure for enabling database administrators to connect as SYSOPER or
SYSDBA or SYSASM without a password is divided into two sets of tasks performed on
different computers:
■

SYSDBA/SYSOPER/SYSASM Authentication Tasks on the Oracle Database Server

■

SYSDBA/SYSOPER/SYSASM Authentication Tasks on the Client Computer

10.2.2.1 SYSDBA/SYSOPER/SYSASM Authentication Tasks on the Oracle Database
Server
1.

Create a Windows local group corresponding to the privileges you want Windows
to grant (see Table 10–1).

Add your database administrator usernames to this group.
See Also: Your operating system documentation for instructions on
managing users and groups

Ensure that parameter SQLNET.AUTHENTICATION_SERVICES in file sqlnet.ora
contains nts.

Start Registry Editor from the command prompt:
C:\>regedit

Go to HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\HOMEID
where ID is the Oracle home that you want to edit.
Administering External Users and Roles on Windows

10-25

Manually Administering External Users and Roles

Set parameter OSAUTH_PREFIX_DOMAIN to true.

10.2.2.2 SYSDBA/SYSOPER/SYSASM Authentication Tasks on the Client Computer
1.

Create a Windows local or domain user name with the same user name and
password that exist on the Windows server (if the appropriate user name does not
currently exist).

Ensure that parameter SQLNET.AUTHENTICATION_SERVICES in file sqlnet.ora
contains nts.

Start SQL*Plus:
C:\> sqlplus /NOLOG

Connect to Oracle Database:
SQL> SET INSTANCE net_service_name

where net_service_name is the Oracle Net net service name for Oracle Database.
6.

If you specified ORA_DBA or ORA_SID_DBA in step 1 of
"SYSDBA/SYSOPER/SYSASM Authentication Tasks on the Oracle Database
Server", then enter either of the following:
SQL> CONNECT / AS SYSOPER
SQL> CONNECT / AS SYSDBA
SQL> CONNECT / AS SYSASM

If you specified ORA_OPER or ORA_SID_OPER in step 1, then enter:
SQL> CONNECT / AS SYSOPER

You are now connected to the Windows server. If you connect with SYSDBA, you
are given DBA privileges.

10.2.3 Manually Creating an External Role
This section describes how to grant Oracle Database roles to users directly through
Windows (known as external roles). When you use Windows to authenticate users,
Windows local groups can grant these users external roles.
All privileges for these roles are active when the user connects. When using external
roles, all roles are granted and managed through the operating system. You cannot use
both external roles and Oracle Database roles at the same time.
Consider the following example. With external roles enabled, you log on to a Windows
domain with domain user name sales\frank (sales is the domain name and frank is
the domain username). You then connect to Oracle Database as Oracle Database user
scott. In this case, you receive the roles granted to sales\frank but not the roles
granted to scott.
The procedure for manually creating an external role is divided into two sets of
authorization tasks performed on different computers:
■

External Role Authorization Tasks on the Oracle Database Server

■

External Role Authorization Tasks on the Client Computer

10-26 Oracle Database Platform Guide

Manually Administering External Users and Roles

10.2.3.1 External Role Authorization Tasks on the Oracle Database Server
1.

Add initialization parameter OS_ROLES to the init.ora file.

Set OS_ROLES to true.
The default setting for this parameter is false.

Ensure that parameter SQLNET.AUTHENTICATION_SERVICES in file sqlnet.ora
contains nts.

Start SQL*Plus:
C:\> sqlplus /NOLOG

Connect to your Windows server:
SQL> CONNECT / AS SYSDBA

Create a new database role. You can give this new role whatever name you want.
In this example the role is named DBSALES3:
SQL> CREATE ROLE DBSALES3 IDENTIFIED EXTERNALLY;

Grant to DBSALES3 whatever Oracle Database roles are appropriate to your
database environment:
SQL> GRANT DBA TO DBSALES3 WITH ADMIN OPTION;

Connect to the database as SYSDBA:
SQL> CONNECT / AS SYSDBA

Shut down the database:
SQL> SHUTDOWN

10. Restart the database:
SQL> STARTUP
11. Create a Windows local group with the following syntax:
ORA_sid_rolename[_D][_A]

where
■

sid identifies the database instance

■

rolename identifies the database role granted

■

D indicates that this database role is to be a default role of the database user

■

A indicates that this database role includes ADMIN OPTION

Characters D and A are optional. If specified, they must be preceded by an
underscore.
For this example, ORA_orcl_dbsales3_D is created.
12. Add one or more Windows local or domain usernames to this group.

See Also: Your operating system documentation for instructions on
managing users and groups

You can create multiple database roles and grant them to several possible
Windows groups with differing options, as shown in the following table. Users
Administering External Users and Roles on Windows

10-27

Manually Administering External Users and Roles

connecting to the ORCL instance and authenticated by Windows as members of all
four of these Windows local groups will have the privileges associated with
dbsales3 and dbsales4 by default (because of option _D). If these users first
connect as members of dbsales3 or dbsales4 and use the SET ROLE command,
then they can also gain access to database roles dbsales1 and dbsales2. But if
these users try to connect with dbsales1 or dbsales2 without first connecting with
a default role, they are unable to connect. Finally, these users can grant dbsales2
and dbsales4 to other roles (because of option _A).
Database Roles

Windows Groups

dbsales1

ORA_ORCL_dbsales1

dbsales2

ORA_ORCL_dbsales2_a

dbsales3

ORA_ORCL_dbsales3_d

dbsales4

ORA_ORCL_dbsales4_da

When Oracle Database converts the group name to a role
name, it changes the name to uppercase.

Note:

10.2.3.2 External Role Authorization Tasks on the Client Computer
1.

Create a Windows local or domain user name with the same user name and
password that exist on the Windows server (if the appropriate user name does not
currently exist).

Ensure that parameter SQLNET.AUTHENTICATION_SERVICES in file sqlnet.ora
contains nts.

Use Oracle Net Configuration Assistant to configure a network connection from
your client computer to Oracle Database. See Oracle Database Net Services
Administrator's Guide for instructions.

Start SQL*Plus:
C:\> sqlplus /NOLOG

Connect to the correct instance:
SQL> SET INSTANCE connect_identifier

where connect_identifier is the net service name for the Oracle Database
connection that you created in Step 3.
6.

Connect to Oracle Database:
SQL> CONNECT SCOTT
Enter password: password

You are connected to the Windows server over net service with Oracle Database
user name scott. Roles applied to Oracle Database user name scott consist of all
roles defined for the Windows user name that were previously mapped to the
database roles (in this case, ORA_DBSALES3_D). All roles available under an
authenticated connection are determined by the Windows user name and the
Oracle-specific Windows local groups to which the user belongs (for example,
ORA_SID_DBSALES1 or ORA_SID_DBSALES4_DA).

10-28 Oracle Database Platform Guide

Manually Administering External Users and Roles

OSDBA and OSOPER are generic names for two special
operating system groups that control database administrator logins
when using operating system authentication. Windows-specific names
for OSDBA and OSOPER are described in "Manually Granting
Administrator and Operator Privileges for Databases" on page 10-25.
See Oracle Database Administrator's Guide for more information on
OSDBA and OSOPER.
Note:

10.2.4 Manually Migrating Users
You can migrate local or external users to enterprise users with User Migration Utility.
Migrating from a database user model to an enterprise user model provides solutions
to administrative, security, and usability challenges in an enterprise environment. In
an enterprise user model, all user information is moved to an LDAP directory service,
which provides the following benefits:
■

Centralized storage and management of user information

■

Centralized user authentication

■

Enhanced security

User Migration Utility is a command-line tool. Its syntax is of the form:
C:\ umu parameters

To get a list of User Migration Utility parameters, enter:
C:\ umu help=yes

See Also: "Using the User Migration Utility" in Oracle Database
Enterprise User Security Administrator's Guide

Administering External Users and Roles on Windows

10-29

Manually Administering External Users and Roles

10-30 Oracle Database Platform Guide

11
1

Storing Oracle Wallets in the Windows
Registry

This chapter describes storing and retrieving of Oracle Wallets in the Windows
registry.

11.1 Storing Private Keys and Trust Points
Oracle Wallets store private keys, trust points, and digital certificates used in public
key applications for authentication and encryption. Oracle Wallet Manager creates and
manages Oracle Wallets. Oracle public key applications use obfuscated Oracle Wallets
for authentication and encryption.
Oracle Wallet Manager is a feature of Oracle Advanced
Security, a separately licensable option to Oracle Database.

Note:

11.2 Storing User's Profile
In Windows domain, a user's profile is stored on the local computer. When a local user
logs on to that computer, that user's profile on the local computer is uploaded into the
user profile in that computer's registry. When a user logs out, that user's profile stored
on the local file system is updated, ensuring that the domain user or local user always
has the most recent user profile version.

11.3 Registry Parameters for Wallet Storage
Parameter WALLET_LOCATION in file sqlnet.ora specifies the location of the obfuscated
Oracle Wallet for use by Oracle PKI applications. For example, the WALLET_LOCATION
parameter for storing an Oracle Wallet in the registry in:
\\HKEY_CURRENT_USER\SOFTWARE\ORACLE\WALLETS\SALESAPP

would be:
WALLET_LOCATION =

(SOURCE= (METHOD=REG) (METHOD_DATA= (KEY=SALESAPP)))

Continuing the example, the encrypted Oracle Wallet would be stored in the registry
in:
\\HKEY_CURRENT_USER\SOFTWARE\ORACLE\WALLETS\SALESAPP\EWALLET.P12

and the obfuscated Oracle Wallet would be stored in:
\\HKEY_CURRENT_USER\SOFTWARE\ORACLE\WALLETS\SALESAPP\CWALLET.SSO
Storing Oracle Wallets in the Windows Registry 11-1

Registry Parameters for Wallet Storage

On Windows operating systems, if there is no value specified for parameter WALLET_
LOCATION, then Oracle PKI applications first look for the obfuscated wallet in registry
key:
\\HKEY_CURRENT_USER\SOFTWARE\ORACLE\WALLETS\DEFAULT

If no obfuscated wallet is found there, Oracle PKI applications look for it in the file
system of the local computer at location:
%USERPROFILE%\ORACLE\WALLETS

Regardless of location, wallets are always stored in the same format. All functionality
is the same except for the location of the wallets.

11.3.1 Oracle Wallet Manager
Oracle Wallet Manager creates and manages Oracle Wallets. If you want to use the
Windows registry for Oracle Wallets, then you must select the Use Windows System
Registry check box. If Windows System Registry is selected, then the tool shows a list
of existing keys when it opens a wallet or saves a new wallet. The list appears in:
\\HKEY_CURRENT_USER\SOFTWARE\ORACLE\WALLETS

You can select one of the existing locations or enter the name for a new location
(registry key). If you enter a new key called key1, for example, then the tool creates the
following registry key:
\\HKEY_CURRENT_USER\SOFTWARE\ORACLE\WALLETS\KEY1

The encrypted wallet will be stored in:
\\HKEY_CURRENT_USER\SOFTWARE\ORACLE\WALLETS\KEY1\EWALLET.P12

The obfuscated wallet will be stored in:
\\HKEY_CURRENT_USER\SOFTWARE\ORACLE\WALLETS\KEY1\CWALLET.SSO

If you do not select the Use Windows System Registry check box, then the tool
displays all the available drives and directories on the local computer. You can select
one of the existing directories or enter a new directory. The tool stores the encrypted or
obfuscated wallet in the selected directory or creates the directory if it does not exist.

11.3.1.1 Sharing Wallets and sqlnet.ora Files Among Multiple Databases
Multiple nonreplicated databases cannot share wallets. If sqlnet.ora files contain
wallet location information, then databases also cannot share sqlnet.ora files.
The only exception to this rule is password-authenticated or Kerberos-authenticated
enterprise user security with default database-to-directory connection configuration
that uses passwords. This configuration keeps database wallets in the default location,
where Database Configuration Assistant creates them. In this situation, no wallet
location information is stored in the sqlnet.ora file, and the wallet can be shared
among multiple databases.
Note: If SSL is used for enterprise user authentication, then the
wallet location must be specified in the sqlnet.ora file. So,
sqlnet.ora files cannot be shared by multiple databases for
SSL-authenticated enterprise users.

11-2 Oracle Database Platform Guide

12
12

Oracle PKI Integration with Windows

This chapter describes integration of Oracle public key infrastructure (PKI) with public
key infrastructure (Windows PKI) on Windows operating systems.
This chapter contains the following topics:
■

Oracle Public Key Infrastructure

■

Windows Public Key Infrastructure

12.1 Oracle Public Key Infrastructure
Oracle public key infrastructure (PKI) is used by Oracle Enterprise Security Manager,
LDAP-enabled Oracle Enterprise Manager, Oracle's Secure Socket Layer (SSL)
authentication, Oracle Database, and Oracle Application Server.

Oracle Security Manager is installed only with Oracle
Database Client.

Note:

Oracle PKI includes the following components:
■

Oracle Wallets

■

Oracle Wallet Manager (OWM)

Oracle Wallets store digital certificates, trust points, and private keys used in public
key applications for encryption, decryption, digital signature, and verification.

12.2 Windows Public Key Infrastructure
This section describes Windows public key infrastructure.
This section contains these topics:
■

Microsoft Certificate Stores

■

Microsoft Certificate Services

■

Using Microsoft Certificate Stores with Oracle PKI Applications

Oracle PKI Integration with Windows 12-1

Windows Public Key Infrastructure

Microsoft Certificate Store integration works only with digital
certificates that use Microsoft Enhanced Cryptographic Provider. To
create these certificates, you must install Windows High Encryption
Pack and select Microsoft Enhanced Cryptographic Provider. Also,
when there are multiple certificates available for the same key usage
(signature/key exchange), the first certificate retrieved will be used
for Oracle SSL.

Note:

12.2.1 Microsoft Certificate Stores
Microsoft Certificate Stores are repositories for storing digital certificates and their
associated properties. Windows operating systems store digital certificates and
certificate revocation lists in logical and physical stores. Logical stores contain pointers
to public key objects in physical stores. Logical stores enable public key objects to be
shared between users, computers, and services without requiring storage of duplicates
of objects for each user, computer, or services. Public key objects are physically stored
in the registry of the local computer or, for some user certificates, in Active Directory.
Standard system certificate stores defined by Microsoft include:
■

MY or Personal

■

ROOT

MY or Personal holds a user's certificates for which the associated private key is
available. The MY certificate store maintains certificate properties that indicate the
Cryptographic Service Provider (CSP) associated with the private key. An application
uses this information to obtain the private key from the CSP for the associated
certificate. CA holds issuing or intermediate certificate authority (CA) certificates.
ROOT holds only self-signed CA certificates for trusted root CAs.

12.2.2 Microsoft Certificate Services
Microsoft Certificate Services (MCS) consists of the following modules:
■

Server Engine

■

Intermediary

■

Policy

Server Engine handles all certificate requests. It interacts with other modules at each
processing stage to ensure that the proper action is taken based on the state of the
request. The Intermediary module receives requests for new certificate from clients
and then submits them to Server Engine. The Policy module contains the set of rules
controlling the issuance of certificates. This module may be upgraded or customized
as needed.

12.2.3 Using Microsoft Certificate Stores with Oracle PKI Applications
Wallet Resource Locator (WRL) specifies that parameter WALLET_LOCATION in file
sqlnet.ora identifies a particular PKI. You can choose between using Oracle Wallet or
Microsoft Certificate Stores by setting parameter WALLET_LOCATION in sqlnet.ora. To
use credentials from Microsoft Certificate Stores, set parameter WALLET_LOCATION in
sqlnet.ora to:
WALLET_LOCATION = (SOURCE = (METHOD=MCS))

12-2 Oracle Database Platform Guide

Windows Public Key Infrastructure

The Oracle application uses Oracle's TCP/IP with SSL protocol (TCPS) to connect to
Oracle Server. The SSL protocol uses X.509 certificates and trust points from the user's
Microsoft Certificate Store for SSL authentication.

Oracle PKI Integration with Windows 12-3

Windows Public Key Infrastructure

12-4 Oracle Database Platform Guide

13
Using Oracle Database with Microsoft
Active Directory
13

This chapter describes how to configure and use Microsoft Active Directory as the
LDAP directory.
This chapter contains these topics:
■

Microsoft Active Directory Support

■

Oracle Components That Integrate with Active Directory

■

Requirements for Using Oracle Database with Active Directory

■

Configuring Oracle Database to Use Active Directory

■

Testing Connectivity

■

Access Control List Management for Oracle Directory Objects

13.1 Microsoft Active Directory Support
This section describes how Microsoft Active Directory is used as an LDAP directory
server by Oracle Database.
This section contains these topics:
■

About Microsoft Active Directory

■

Accessing Active Directory

13.1.1 About Microsoft Active Directory
Active Directory is the LDAP-compliant directory server included with Windows
server operating systems. Active Directory stores all Windows operating system
information, including users, groups, and policies. Active Directory also stores
information about network resources (such as databases) and makes this information
available to application users and network administrators. Active Directory enables
users to access network resources with a single login. The scope of Active Directory
can range from storing all the resources of a small computer network to storing all the
resources of several wide areas networks (WANs).

13.1.2 Accessing Active Directory
When using Oracle features that support Active Directory, ensure that the Active
Directory computer can be successfully reached using all possible TCP/IP host name
forms to reach the domain controller. For example, if the host name of the domain

Using Oracle Database with Microsoft Active Directory 13-1

Oracle Components That Integrate with Active Directory

controller is server1 in the domain example.com, then ensure that you can ping that
computer using all of the following:
■

server1.example.com

■

example.com

■

server1

Active Directory often issues referrals back to itself in one or more of these forms,
depending upon the operation being performed. If any of the forms cannot reach the
Active Directory computer, then some LDAP operations may fail.

13.2 Oracle Components That Integrate with Active Directory
The following Oracle Database features support or have been specifically designed to
integrate with Active Directory:
■

Directory Naming

■

Automatic Discovery of Directory Servers

■

Integration with Windows Tools

■

User Interface Extensions for Oracle Net Directory Naming

■

Enhancement of Directory Object Type Descriptions

■

Integration with Windows Login Credentials

■

Oracle Directory Objects in Active Directory

13.2.1 Directory Naming
Oracle Database provides Oracle Net Services directory naming, which makes use of a
directory server. This feature has been enabled to work with Microsoft Active
Directory. Directory Naming enables clients to connect to the database making use of
information stored centrally in an LDAP-compliant directory server such as Active
Directory. For example, any net service name previously stored in the tnsnames.ora
file can now be stored in Active Directory.

13.2.2 Automatic Discovery of Directory Servers
Oracle Net Configuration Assistant provides automatic discovery of directory servers.
When you select Active Directory as the directory server type, Oracle Net
Configuration Assistant automatically discovers the directory server location and
performs related tasks.
"Configuring Oracle Database to Use Active Directory" on
page 13-8 for more information on Active Directory configuration
See Also:

13.2.3 Integration with Windows Tools
Oracle Database services, net service names, and enterprise role entries in Active
Directory can be displayed and tested in two Windows tools:
■

Windows Explorer

■

Active Directory Users and Computers

13-2 Oracle Database Platform Guide

Oracle Components That Integrate with Active Directory

Windows Explorer displays the hierarchical structure of files, directories, and local and
network drives on your computer. It can display and test Oracle Database service and
net service name objects.
Active Directory Users and Computers is an administrative tool installed on Windows
servers configured as domain controllers. This tool enables you to add, modify, delete,
and organize Windows accounts and groups, and publish resources in the directory of
your organization. Like Windows Explorer, it can display and test Oracle Database
service and net service name objects. Additionally, it can manage access control.
See Also:
■
■

"Testing Connectivity from Microsoft Tools" on page 13-10
"Access Control List Management for Oracle Directory Objects" on
page 13-12

13.2.4 User Interface Extensions for Oracle Net Directory Naming
The property menus of Oracle Database service and net service name objects in
Windows Explorer and Active Directory Users and Computers have been enhanced.
When you right-click these Oracle directory objects, you now see two new options for
testing connectivity:
■

Test

■

Connect with SQL*Plus

The Test option tests whether the username, password, and net service name you
initially entered can actually connect to Oracle Database. The Connect with SQL*Plus
option starts SQL*Plus, which enables you to perform database administration, run
scripts, and so on.
See Also:

"Testing Connectivity from Microsoft Tools" on page 13-10

13.2.5 Enhancement of Directory Object Type Descriptions
Oracle directory object type descriptions in Active Directory have been enhanced to
make them easier to understand. In the right pane of Figure 13–1 on page 13-4, for
example, the Type column reveals that sales is an Oracle Net Service name.

13.2.6 Integration with Windows Login Credentials
Oracle database and configuration tools can use the login credentials of the Windows
user currently logged on to connect to Active Directory without having to re-enter the
login credentials. This feature has the following benefits:
■

■

Oracle clients and databases can securely connect to Active Directory and retrieve
the net service name.
Oracle configuration tools can connect automatically to Active Directory and
configure Oracle Database and net service name objects. The enabled tools include
Oracle Net Configuration Assistant and Database Configuration Assistant.
In Oracle Database 11g, enhancements are made to make secure access over the
internet to avoid anonymous binds to the directory. The enhanced security enables
the sites to restrict access to Database Service by setting access control (ACL) on
Database Service DN in Directory Server. The enhancement gives clients the
option to use authenticated binds for LDAP name lookup. Clients will have access

Using Oracle Database with Microsoft Active Directory 13-3

Oracle Components That Integrate with Active Directory

to Database Service object if the object (DN of Database Service Entry) has been
configured with restrictive access control.
Configuration on machines that require authenticated name lookups
Add the following entry in sqlnet.ora to enable authenticated name lookup:
names.ldap_authenticate_bind = TRUE

13.2.7 Oracle Directory Objects in Active Directory
If Oracle Database and Oracle Net Services are installed and configured to access
Active Directory, then Active Directory Users and Computers displays Oracle
directory objects, as illustrated in Figure 13–1:
Figure 13–1

Oracle Directory Objects in Active Directory Users and Computers

Table 13–1 describes the Oracle directory objects appearing in Figure 13–1.
Table 13–1

Oracle Directory Objects

Object

Description

oranet.dev

The domain in which you created your Oracle Context. This domain (also
known as the administrative context) contains various Oracle entries to
support directory naming. Oracle Net Configuration Assistant
automatically discovers this information during Oracle Database
integration with Active Directory.

OracleContext

The top-level Oracle entry in the Active Directory tree. It contains Oracle
Database service and net service name object information. All Oracle
software information is placed in this folder.

orcl

The Oracle Database service name used in this example.

Products

Folder for Oracle product information.

sales

The net service name object used in this example.

13-4 Oracle Database Platform Guide

Requirements for Using Oracle Database with Active Directory

Table 13–1 (Cont.) Oracle Directory Objects
Object

Description

Users

Folder for the Oracle security groups. See "Access Control List
Management for Oracle Directory Objects" on page 13-12 for more
information. Enterprise users and roles created with Oracle Enterprise
Security Manager also appear in this folder.

13.3 Requirements for Using Oracle Database with Active Directory
To use Net Directory Naming with Active Directory, you must have certain Microsoft
and Oracle software releases, and you must create Oracle schema objects and an
Oracle Context. These requirements are discussed in the following sections:
■

Directory Naming Software Requirements

■

Creating an OracleContext

■

Oracle Schema Objects Creation
Note:
■

■

The Oracle schema objects and Oracle Context can both be created
by Oracle Net Configuration Assistant.
Regardless of the Oracle Database Client and Oracle Database
releases you are using, you must be in a Windows Server 2003,
Windows Server 2008, Windows Server 2008 R2 x64, Windows
Server 2012, or Windows Server 2012 R2 x64 domain to integrate
Net Directory Naming with Active Directory.

13.3.1 Directory Naming Software Requirements
For client computers from which you want to manage Oracle Database enterprise
users, roles and domains, you must have Oracle8i Client release 8.1.6 or later and one
of the supported Windows operating systems.
For the database, you must have Oracle8i Database release 8.1.6 or later. This is
required for registering the database service as an object in Active Directory. The
database can use any of the supported Windows operating systems.
Both the client computers and the database must be members of a Windows server
domain.
Directory Naming adaptor connects anonymously to directory by default.

13.3.2 Creating an OracleContext
You must create an Oracle Context to use net directory naming features with Active
Directory. Oracle Context is the top-level Oracle entry in the Active Directory tree. It
contains Oracle Database service and Oracle Net service name object information.
■

■

You can create only one Oracle Context for each Windows server domain
(administrative context).
You must have the right to create domain and enterprise objects to create the
Oracle Context in Active Directory with Oracle Net Configuration Assistant.
Use Oracle Net Configuration Assistant to create your Oracle Context. You can
create the Oracle Context during or after Oracle Database Custom installation.

Using Oracle Database with Microsoft Active Directory 13-5

Requirements for Using Oracle Database with Active Directory

Oracle Database Platform Guide For Windows

Navigation menu

Versions of this User Manual:

Views

Navigation