Skip Headers
Oracle® Database Installation Guide
10g Release 1 (10.1.0.3) for Linux x86-64
Part No. B14399-01
  Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

5 Reviewing Your Preconfigured Database

This chapter provides information about the default preconfigured database, including information about Oracle database accounts, passwords, and file locations. It includes information about the following topics:

Log In to the Oracle Enterprise Manager Database Control

If you configured the Oracle Enterprise Manager Database Control during the installation, you can use it to manage your database. Alternatively, you can also use Oracle Enterprise Manager Grid Control to manager your database. To display the Database Control:

  1. Use a Web browser to access the Database Control URL:

    http://host:port/em
    
    

    In this example:

    • host is the name of the computer on which you installed Oracle Database

    • port is the port number reserved for the Database Control during installation

    If you do not know the correct port number to use, look for the following line in the $ORACLE_HOME/install/portlist.ini file:

    Enterprise Manager Console HTTP Port (db_name) = 5500
    
    

    The installation reserves the first available port from the range 5500 to 5519. For example, if you installed Oracle Database on host mgmt42, and the Database Control uses port 5500, enter the following URL:

    http://mgmt42:5500/em
    
    

    Oracle Enterprise Manager displays the Database Control login page.

  2. Log in to the database using the user name SYS and connect as SYSDBA.

    Use the password that you specified for the SYS account during the installation.


Note:

You can also log in to the Database Control using the SYSTEM or SYSMAN accounts or you can grant login privileges to other database users.

Understanding Database Control Login Privileges

When you log in to the 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 of the management features provided by the Database Control.

You can also use the SYS and SYSTEM accounts to log in to the Database Control. In addition, you can grant login privileges to other database users, as follows:

  1. Log in to the Database Control.


    See Also:

    See "Log In to the Oracle Enterprise Manager Database Control" for information about logging in to the 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 user name 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.

Review Accounts and Passwords

All databases created by the Database Configuration Assistant (DBCA) 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 user names and default passwords.


See Also:

See the "Unlock and Reset User Passwords" section for information about unlocking and resetting passwords.


Note:

You can use the Oracle Enterprise Manager Database Control to view the complete list of database accounts. For more information, see "Unlock and Reset User Passwords".

Table 5-1 Database Accounts

User Name Default Password Description See Also
ANONYMOUS ANONYMOUS Allows HTTP access to Oracle XML DB. None
BI BI The account that owns the Business Intelligence schema included in the Oracle Sample Schemas. It is available only if you loaded the Sample Schemas. Oracle Database Sample Schemas
CTXSYS CTXSYS The Oracle Text account. Oracle Text Reference
DBSNMP Password set during installation or in the DBCA The account used by the Management Agent component of Oracle Enterprise Manager to monitor and manage the database. It is created only if you configure the database to use the Database Control. Oracle Enterprise Manager Grid Control Installation and Basic Configuration
DIP DIP The account used by the 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 DMSYS The data mining account. DMSYS performs data mining operations. Oracle Spatial User's Guide and Reference
EXFSYS EXFSYS The account that owns the Expression Filter schema. None
HR HR The account that 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 IX The account that owns the Information Transport schema included in the Oracle Sample Schemas. It is available only if you loaded the Sample Schemas. Oracle Database Sample Schemas
LBACSYS LBACSYS The Oracle Label Security administrator account. Oracle Label Security Administrator's Guide
MDDATA MDDATA The schema used by Oracle Spatial for storing Geocoder and router data. Oracle Spatial User's Guide and Reference
MDSYS MDSYS The Oracle Spatial and Oracle interMedia Locator administrator account. Oracle Spatial User's Guide and Reference
MGMT_VIEW Randomly generated An account used by Oracle Enterprise Manager Database Control. None
ODM ODM The data mining account. ODM performs data mining operations. Oracle Data Mining Administrator's Guide

Oracle Data Mining Concepts


ODM_MTR MTRPW The account associated with the data repository for data mining sample programs. Oracle Data Mining Administrator's Guide

Oracle Data Mining Concepts


OE OE The account that owns the Order Entry schema included in the Oracle Sample Schemas. It is available only if you loaded the Sample Schemas. Oracle Database Sample Schemas
OLAPSYS MANAGER The account that owns the OLAP catalogs. Oracle OLAP Application Developer's Guide
ORDPLUGINS ORDPLUGINS The Oracle interMedia user. Plugins supplied by Oracle and third-party plugins are installed in this schema. Oracle interMedia Reference
ORDSYS ORDSYS The Oracle interMedia administrator account. Oracle interMedia Reference
OUTLN OUTLN The account that supports plan stability. Plan stability allows you to maintain the same execution plans for the same SQL statements. OUTLN acts as a role to centrally manage metadata associated with stored outlines. Oracle Database Concepts
PM PM The account that owns the Product Media schema included in the Oracle Sample Schemas. It is available only if you loaded the Sample Schemas. Oracle Database Sample Schemas
SCOTT TIGER An account used by Oracle sample programs and examples. Oracle Database Administrator's Guide
SH SH The account that owns the Sales History schema included in the Oracle Sample Schemas. It is available only if you loaded the Sample Schemas during an Enterprise Edition installation. Oracle Database Administrator's Guide
SI_INFORMTN_SCHEMA SI_INFORMTN_SCHEMA The account that stores the information views for the SQL/MM Still Image Standard. Oracle interMedia Reference
SYS Password set during installation or in the DBCA The account used to perform database administration tasks. Oracle Database Administrator's Guide
SYSMAN Password set during installation or in the DBCA The account used to perform Oracle Enterprise Manager database administration tasks.It is created only if you configure the database to use the Database Control. Oracle Enterprise Manager Grid Control Installation and Basic Configuration
SYSTEM Password set during installation or in the DBCA Another account used to perform database administration tasks. Oracle Database Administrator's Guide
WMSYS WMSYS The account used to store the metadata information for Oracle Workspace Manager. Oracle Database Application Developer's Guide - Workspace Manager
WKPROXY WKSYS The Ultra Search proxy user. Oracle Ultra Search User's Guide
WK_TEST WK_TEST The default Ultra Search instance schema. Oracle Ultra Search User's Guide
WKSYS WMSYS The account used to store Ultra Search system dictionaries and PL/SQL packages. Oracle Ultra Search User's Guide
XDB XDB The account used for storing Oracle XML DB data and metadata. Oracle XML DB Developer's Guide

Unlock and Reset User Passwords

Passwords for all Oracle system administration accounts except SYS, SYSTEM, SYSMAN, and DBSMP are revoked after installation. Before you use a locked account, you must unlock it and reset its password. If you created a preconfigured database during the installation, but you did not unlock a required account, you must unlock it now, using one of the following methods:


Note:

If you are creating a new database using DBCA, you can unlock accounts after the database is created by clicking Password Management before you exit from DBCA.

Using Database Control to Unlock Accounts and Reset Passwords

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

  1. Log in to the Database Control.


    See Also:

    See "Log In to the Oracle Enterprise Manager Database Control" for information about logging in to the Database Control.

  2. Click Administration.

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

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

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

  5. Use the General page of the Users property sheet to unlock the account and, optionally, to change the password.


See Also:

Click Help in the Database Control window for more information about using the Database Control.

Using SQL*Plus to Unlock Accounts and Reset Passwords

To unlock and reset user account passwords using SQL*Plus:

  1. Start SQL*Plus and log in as the SYS user, connecting as SYSDBA:

    $ sqlplus /nolog
    SQL> CONNECT SYS/SYS_password AS SYSDBA
    
    
  2. 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 IDENTIFED BY password clause resets the password.


    Note:

    If you unlock an account but do not reset the password, then the password remains expired. The first time someone connects as that user, they must change the user's password.

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



    See Also:

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

    • Oracle security procedures

    • Best security practices


Identify Databases

The Oracle Database 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 the Database Configuration Assistant. For example:

sales.us.acme.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. In most cases, the SID is the same as the database name portion of the global database name.

Locate the Parameter File

By default, the preconfigured database uses a server parameter file named spfilesid.ora, which is stored in the $ORACLE_HOME/dbs directory. However, if you choose ASM or raw device storage for the database, DBCA typically uses the same storage mechanism for the server parameter file.

If the server parameter file is not located in the $ORACLE_HOME/dbs directory, the database uses the SPFILE parameter in an initialization parameter file to locate it. The default initialization parameter file is $ORACLE_HOME/dbs/initsid.ora.

You can use the 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 the Database Control.


    See Also:

    See "Log In to the Oracle Enterprise Manager Database Control" for information about logging in to the Database Control.

  2. Click Administration.

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

    Enterprise Manager displays a table listing the current value of each initialization parameter.

  4. Click SPFile.

    Enterprise Manager 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 above the table.

Review Tablespaces and Datafiles, Redo Log Files, and Control Files

The following sections contain information about tablespaces and datafiles, redo log files, and control files:

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. You can associate each datafile with only one tablespace and database.


Note:

The SYSAUX and SYSTEM tablespaces must be present in all Oracle Database 10g databases.

Table 5-2 describes the tablespaces provided by the default preconfigured database.

Table 5-2 Tablespaces and Description

Tablespace Description
EXAMPLE Stores the sample schemas, if you included them.
SYSAUX Serves as an auxiliary tablespace to the SYSTEM tablespace. Some products and options that previously used the SYSTEM tablespace now use the SYSAUX tablespace, which reduces the load on the SYSTEM tablespace.
SYSTEM Stores the data dictionary, which includes definitions of tables, views, and stored procedures needed by Oracle Database.
TEMP Stores temporary tables and indexes when processing SQL statements.
UNDOTBS1 Stores undo information.
USERS Stores database objects created by database users.


See Also:

See Oracle Database Concepts and the Oracle Database Administrator's Guide for more information about tablespaces and datafiles.

To use the Oracle Enterprise Manager Database Control to view the list of datafiles used by the database and their associated tablespaces:

  1. Log in to the Database Control.


    See Also:

    See "Log In to the Oracle Enterprise Manager Database Control" for information about logging in to the Database Control.

  2. Click Administration.

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

    Enterprise Manager displays a table listing each datafile, and the tablespace with which it is associated.


    See Also:

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

Locating Redo Log Files

The preconfigured database uses three redo log files. Redo log files record 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.

Oracle Database uses redo log files in a cyclical fashion. For example, if three files constitute the online redo log, Oracle Database fills the first file, then the second file, and then the third file. In the next cycle, it reuses and fills the first file, the second file, and so on.


See Also:

See Oracle Database Backup and Recovery Basics for more information about redo log files.

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

  1. Log in to the Database Control.


    See Also:

    See "Log In to the Oracle Enterprise Manager Database Control" for information about logging in to the Database Control.

  2. Click Administration.

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

    Enterprise Manager displays a table listing the redo log groups used by the database.

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


See Also:

For more information about using the Database Control to view, modify, and create redo log files, click Help in the Database Control window.

Locating Control Files

The preconfigured database uses three control files. Oracle recommends that you keep at least three control files for each database and set the CONTROL_FILES initialization parameter to specify the location of each file.

A control file is an administrative file. Oracle Database requires a control file to start and run the database. The control file defines the physical structure of the database. For example, it defines the database name and the names and locations of the database datafiles and redo log files.

To use the Oracle Enterprise Manager Database Control to view information about the control files for your preconfigured database:

  1. Log in to the Database Control.


    See Also:

    See "Log In to the Oracle Enterprise Manager Database Control" for information about logging in to the Database Control.

  2. Click Administration.

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

    Enterprise Manager displays a table listing the control files used by the database.


    See Also:

    For more information about using the Database Control to view information about control files and back them up to trace files, click Help in the Database Control window.

    For more information about setting the CONTROL_FILES initialization parameter value, see the Oracle Database Administrator's Guide.