Skip Headers

Oracle® Database Installation Guide
10g Release 1 (10.1.0.2.0) for 64-Bit Windows
Part No. B13805-02
  Go To Table Of Contents
Contents
Go To Index
Index

Previous Next  

5 Reviewing Your Installed Starter Database Contents

This chapter describes the contents of the default starter database, including information about Oracle database accounts, passwords, and file locations.

This chapter contains these topics:

5.1 Accessing Enterprise Manager Database Control

Oracle Enterprise Manager Database Control provides a Web-based user interface that you can use to monitor, administer, and maintain an Oracle database.

To display Oracle Enterprise Manager Database Control:

  1. Open your Web browser and enter the following URL

    http://hostname:port/em
    
    
    

    If you are unsure of the correct port number to use, look for the following line in the ORACLE_BASE\ORACLE_HOME\install\portlist.ini file:

    Enterprise Manager Console HTTP Port (db_name) = port
    
    

    For example, if you installed the database on a host computer named mgmt42, and the port number listed in the portlist.ini file is 5500, then enter the following URL

    http://mgmt42:5500/em
    
    
    

    Enterprise Manager displays the Database Control Login Page.

  2. Log in to the database using the SYSMAN database user account. Enterprise Manager displays the Oracle Database home page.

    Use the password you specified for the SYSMAN account during the Oracle Database installation.

5.1.1 Understanding Database Control Login Privileges

When you log in to Oracle Enterprise Manager Database Control using the SYSMAN user account, you are logging in as the Oracle Enterprise Manager super user. The SYSMAN account is automatically granted the roles and privileges required to access all the management functionality provided with Database Control.

You can also use the SYS and SYSTEM accounts to log in to Database Control. In addition, you can grant login privileges to other database users. To grant management access for other database users, use the following procedure:

  1. Log in to Database Control.

  2. Click Setup at the top of the Database Control home page.

  3. Click Administrators in the left navigation bar.

  4. Click Create to create a new Enterprise Manager user.

  5. In the Name field, enter the username of an existing database user or click the flashlight icon and select a user from the pop-up window.

  6. Enter the password for this user, then click Finish.

Enterprise Manager assigns login privileges to the specified user and includes this user in the list of Enterprise Manager users on the Setup Administrators page.

5.2 Reviewing User Accounts and Passwords

All databases created by Database Configuration Assistant include the SYS, SYSTEM, SYSMAN, and DBSNMP database accounts. In addition, Oracle provides several other administrative accounts. Before using these other accounts, you must unlock them and reset their passwords. Table 5-1 describes these accounts, listing their usernames and passwords.


See Also:

  • "Unlocking and Changing Passwords" for information about using Oracle Enterprise Manager Database Control to view a complete list of the user accounts defined for your database

  • "Modifying Oracle Counters for Windows Performance Monitor Parameters" in Oracle Database Platform Guide for Windows for instructions on how to change the password for Oracle Counters for Windows Performance Monitor

  • Oracle Database Administrator's Guide for information about Oracle security procedures and security best practices


5.2.1 Reviewing Administrative Accounts

Table 5-1 describes the administrative usernames.

Table 5-1 Administrative Accounts

Username Description See Also
ANONYMOUS Allows HTTP access to Oracle XML DB. Not applicable
BI Owns the Business Intelligence schema included in the Oracle Sample Schemas. It is only available if you loaded the Sample Schemas. Oracle Database Sample Schemas
CTXSYS The Oracle Text account. Oracle Text Reference
DBSNMP Used by Management Agent of Oracle Enterprise Manager to monitor and manage the database. This account is created only if you configure the database to use Database Control. Oracle Enterprise Manager Grid Control Installation and Basic Configuration
DIP Used by Directory Integration Platform (DIP) to synchronize the changes in Oracle Internet Directory with the applications in the database. Oracle Internet Directory Administrator's Guide
DMSYS Performs data mining operations. Oracle Spatial User's Guide and Reference
EXFSYS Owns the Expression Filter schema. None
HR Owns the Human Resources schema included in the Oracle Sample Schemas. It is available only if you loaded the Sample Schemas. Oracle Database Sample Schemas
IX Owns the Information Transport schema included in the Oracle Sample Schemas. This account is available only if you loaded the Sample Schemas. Oracle Database Sample Schemas
LBACSYS The Oracle Label Security administrator account. Oracle Label Security Administrator's Guide
MDDATA Used by Oracle Spatial for storing Geocoder and router data. Oracle Spatial User's Guide and Reference
MDSYS The Oracle Spatial and Oracle Locator administrator account. Oracle Spatial User's Guide and Reference
MGMT_VIEW Used by Oracle Enterprise Manager Database Control. None
ODM Performs data mining operations. Oracle Data Mining Administrator's Guide

Oracle Data Mining Concepts

ODM_MTR Associated with the data repository for Data Mining sample programs. Oracle Data Mining Administrator's Guide

Oracle Data Mining Concepts

OE Owns the Order Entry schema included in the Oracle Sample Schemas. This account is available only if you loaded the Sample Schemas. Oracle Database Sample Schemas
OLAPSYS Owns the OLAP catalogs Oracle OLAP Application Developer's Guide
ORDPLUGINS The Oracle interMedia Audio and Video account. Plug-ins supplied by Oracle and third party plug-ins are installed in this schema. Oracle interMedia Reference
ORDSYS The Oracle interMedia Audio, Video, Locator, and Image administrator account. Oracle interMedia Reference
OUTLN Centrally manages metadata associated with stored outlines. Supports plan stability, which enables maintenance of the same execution plans for the same SQL statements. Oracle Database Performance Tuning Guide
PM Owns the Product Media schema included in the Oracle Sample Schemas. This account is created only if you loaded the Sample Schemas. Oracle Database Sample Schemas
SCOTT An account used by Oracle sample programs and examples. Oracle Database Administrator's Guide
SH Owns the Sales History schema included in the Oracle Sample Schemas. This account is available only if you loaded the Sample Schemas during an Enterprise Edition installation Oracle Database Sample Schemas
SI_INFORMTN_SCHEMA Stores the information views for the SQL/MM Still Image Standard. Oracle interMedia Reference
SYS Used for performing database administration tasks. Oracle Database Administrator's Guide
SYSMAN The account used to perform Oracle Enterprise Manager database administration tasks.This account is created only if you configure the database to use the Database Control. Oracle Enterprise Manager Grid Control Installation and Basic Configuration
SYSTEM Used for performing database administration tasks. Oracle Database Administrator's Guide
WK_TEST The default Ultra Search instance schema. Oracle Ultra Search User's Guide
WKPROXY The Ultra Search proxy user. Oracle Ultra Search User's Guide
WKSYS Used for storing Ultra Search system dictionaries and PL/SQL packages. Oracle Ultra Search User's Guide
WMSYS The account used to store the metadata information for Oracle Workspace Manager. Oracle Database Application Developer's Guide - Workspace Manager
XDB Used for storing Oracle XML DB data and metadata. Oracle XML DB Developer's Guide


See Also:

  • "Privileges, Roles, and Security Policies" of Oracle Database Concepts

  • "The Oracle Database Administrator" of Oracle Database Administrator's Guide

  • "Administering External Users and Roles on Windows" of Oracle Database Platform Guide for Windows


5.2.2 Unlocking and Changing Passwords

Passwords for all Oracle system administration accounts except SYS, SYSTEM, SYSMAN, and DBSNMP are revoked after installation. Before you use a locked account, you must unlock it and reset its password. If you created a starter database during the installation, Database Configuration Assistant displays a screen with your database information and the Password Management button. Use the Password Management button to unlock only the usernames you will use.

If you created a starter database during the installation, but you did not unlock the required account, unlock the account using one of the following methods:


Note:

To permit unauthenticated access to your data through HTTP, unlock the ANONYMOUS account.


See Also:

Oracle Database Administrator's Guide for more information about:
  • Unlocking and changing passwords after installation

  • Oracle security procedures

  • Security best practices


5.2.2.1 Using SQL*Plus to Unlock and Change Passwords

Use SQL*Plus to unlock accounts and change passwords any time after the installation process.

To change a password after installation:

  1. Start SQL*Plus:

    C:\> sqlplus /NOLOG
    
    
  2. Connect as SYSDBA:

    SQL> CONNECT "SYS/SYS_password AS SYSDBA"
    
    
  3. Enter a command similar to the following, where account is the user account that you want to unlock and password is the new password:

    SQL> ALTER USER account [IDENTIFIED BY password] ACCOUNT UNLOCK;
    
    

    In this example:

    • The ACCOUNT UNLOCK clause unlocks the account.

    • The IDENTIFIED BY password clause resets the password.

5.2.2.2 Using Enterprise Manager Database Control to Unlock and Change Passwords

To unlock and reset user account passwords with Oracle Enterprise Manager Database Control:

  1. Log in to Database Control.

  2. Click Administration.

  3. In the Security section of the Administration page, click Users.

    Enterprise Manager displays a table containing all database accounts. The Account Status column indicates whether the account is locked and whether the password is expired.

  4. Select the user account you want to modify, then click Edit.

  5. Use the General page of the Users property sheet to change the password and lock or unlock the selected account. Click Help for additional information.

5.3 Identifying Databases

The Oracle Database 10g software identifies a database by its global database name. A global database name consists of the database name and database domain. Usually, the database domain is the same as the network domain, but it need not be. The global database name uniquely distinguishes a database from any other database in the same network. You specify the global database name when you create a database during the installation, or using Database Configuration Assistant. For example:

sales.us.mycompany.com

In this example:

The DB_NAME parameter and the DB_DOMAIN name parameter combine to create the global database name value assigned to the SERVICE_NAMES parameter in the initialization parameter file.

The System Identifier (SID) identifies a specific database instance. The SID uniquely distinguishes the instance from any other instance on the same computer. Each database instance requires a unique SID and database name.

For example, if the SID and database name for an Oracle database are ORCL, then each database file is located in the ORACLE_BASE\ORACLE_HOME\orcl directory and the initialization parameter file is located in the ORACLE_BASE\admin\orcl\pfile directory.

5.4 Locating the Server Parameter File

The starter database contains one database initialization parameter file. The initialization parameter file, init.ora.xxxxx, must exist for an instance to start. A parameter file is a text file that contains a list of instance configuration parameters. The starter database init.ora file has preconfigured parameters. You do not need to edit this file to use the starter database.

The server parameter file (SPFILE) is created from the initialization parameter file, then the initialization parameter file is renamed. The SPFILE filename is spfileSID.ora and is located in the ORACLE_BASE\ORACLE_HOME\database directory.

You can use Oracle Enterprise Manager Database Control to view the location of the server parameter file and list all of the initialization parameters, as follows:

  1. Log in to Database Control.

  2. Click Administration.

  3. In the Instance section of the Administration page, click All Initialization Parameters.

    Database Control displays a table listing the current value of each initialization parameter.

  4. Click SPFile.

    Database Control displays a table listing the value of each initialization parameter specified in the server parameter file. The location of the server parameter file is displayed before the table.


See Also:

  • "Oracle Database Specifications for Windows" of Oracle Database Platform Guide for Windows for a list of Oracle Database-specific initialization parameters for Windows and their default values

  • Oracle Database Reference for more information about initialization parameters


5.5 Identifying Tablespaces and Datafiles

An Oracle Database is divided into smaller logical areas of space known as tablespaces. Each tablespace corresponds to one or more physical datafiles. Datafiles contain the contents of logical database structures such as tables and indexes. A datafile can be associated with only one tablespace and database.


Note:

The SYSAUX and SYSTEM tablespaces must be present in all Oracle Database 10g release 1 (10.1.0.2.0) databases.

Table 5-2 list the tablespaces and datafiles in the Oracle Database. By default, the datafiles are located in the ORACLE_BASE\oradata\DB_NAME directory.

Table 5-2 Tablespaces and Datafiles

Tablespace Datafile Description
EXAMPLE EXAMPLE01.DBF Stores the Sample Schemas, if you included them.
SYSAUX SYSAUX01.DBF Serves as an auxiliary tablespace to the SYSTEM tablespace. Some products and options that previously used the SYSTEM tablespace now use the SYSAUX tablespace to reduce the load on the SYSTEM tablespace.
SYSTEM SYSTEM01.DBF Stores the data dictionary, including definitions of tables, views, and stored procedures needed by the Oracle Database. Information in this area is maintained automatically.
TEMP TEMP01.DBF Stores temporary tables and indexes created during the processing of your SQL statement. If you are running a SQL statement that involves a lot of sorting, such as the constructs GROUP BY, ORDER BY, or DISTINCT, then you may need to expand this tablespace.
UNDOTBS UNDOTBS01.DBF Stores undo information. The undo tablespace contains one or more undo segments that maintain transaction history that is used to roll back, or undo, changes to the database.

All starter databases are configured to run in automatic undo management mode.

USERS USERS01.DBF Stores database objects created by database users.

To use Oracle Enterprise Manager Database Control to view the list of tablespaces currently available in your database:

  1. Log in to Database Control.

  2. Click Administration.

  3. In the Storage section of the Administration page, click Tablespaces.

    Enterprise Manager displays a table containing all the tablespaces currently defined for this database instance. For more information about using Database Control to view, modify, and create tablespaces, click Help.


See Also:

  • "Tablespaces, Datafiles, and Control Files" of Oracle Database Concepts

  • "Managing Tablespaces" and "Managing Datafiles and Tempfiles" of Oracle Database Administrator's Guide

  • "Managing the Undo Tablespace" of Oracle Database Administrator's Guide


5.6 Locating Redo Log Files

A redo log can be either an online redo log or an archived redo log. The online redo log is a set of two or more redo log groups that records all changes made to Oracle datafiles and control files. An archived redo log is a copy of an online redo log that has been copied to an offline destination. If the database is in ARCHIVELOG mode and automatic archiving is enabled, then the archive process or processes copy each online redo log to one or more archive log destinations after it is filled.

The starter database and the custom database each contain three redo log files located in the ORACLE_BASE\oradata\DB_NAME directory. Redo log files hold a record of all changes made to data in the database buffer cache. If an instance fails, then Oracle Database uses the redo log files to recover the modified data in memory.

To use Oracle Enterprise Manager Database Control to view or modify the redo log files for your starter database:

  1. Start your Web browser and log in to Database Control.

  2. Click Administration.

  3. In the Storage section of the Administration page, click Redo Log Groups.

    Enterprise Manager displays a table containing the control files currently defined for this database instance.

  4. To view the name and location of the redo log file associated with a particular group, select that group then click View.

    For more information about using Database Control to view, modify, and create tablespaces, click Help.


See Also:

  • Oracle Database Backup and Recovery Basics

  • "Managing Archived Redo Logs" of Oracle Database Administrator's Guide


5.7 Locating Control Files

The starter database and the custom database contain three control files located in the ORACLE_BASE\oradata\DB_NAME directory. Oracle recommends that you keep at least three control files (on separate physical drives) for each database and set the CONTROL_FILES initialization parameter to list each control file.

A control file is an administrative file required to start and run the database. The control file records the physical structure of the database. For example, a control file contains the database name, and the names and locations of the database datafiles and redo log files.

To use Oracle Enterprise Manager Database Control to view or modify the control files for your starter database:

  1. Log in to Database Control.

  2. Click Administration.

  3. In the Storage section of the Administration page, click Controlfiles.

    Enterprise Manager displays a table containing the control files currently defined for this database instance. For more information about using control files and backing up control files, click Help.


See Also:

"Managing Control Files" of Oracle Database Administrator's Guide for information about setting this initialization parameter value

5.8 Understanding Oracle Database Services on Windows

Two main Oracle services are automatically started after installation when you create a database:

If you installed Oracle Enterprise Manager Database Control, then the OracleDBConsoleSID service is automatically started. However, other services for networking or other individual components may not automatically start.