Oracle8i Personal Edition Installation Guide
Release 2 (8.1.6) for Windows 98
A85314-01

Library
Product
Contents
Index

Prev Next

6
Reviewing Your Installed Starter Database Contents

This chapter describes the contents of your installed Oracle8i starter database.

Specific topics discussed are:

User Names and Passwords

This section describes the user names and passwords included in the starter database. Change the password for user names immediately after installation.

To change a password:

  1. Start SQL*Plus: 

    C:\> SQLPLUS
  2. Connect with the user name and password that you want to change: 

    Enter user-name: SYSTEM/PASSWORD
  3. Change the password: 

    SQL> ALTER USER USERNAME IDENTIFIED BY PASSWORD;

Note:

The SYS, SYSTEM, and DBSNMP user names and INTERNAL alias passwords in the following table are automatically included in all databases created by Oracle Database Configuration Assistant.  

User Name  Password  Description  See Also 

INTERNAL  

ORACLE

 

INTERNAL is used for performing database administration tasks, including starting up and shutting down a database.

Note: INTERNAL is not a true user name; it is an alias for the SYS user name (see below) and SYSDBA privilege.

Note: The password is required only for users who did not install the Oracle8i database. The user who installed the Oracle8i database is not prompted to enter a password when connecting as INTERNAL because the user's Windows NT user name was added to a special Windows NT local group called ORA_DBA.  

  

SYSTEM  

MANAGER 

SYSTEM is used for performing database administration tasks. SYSTEM includes the AQ_ADMINISTRATOR_ROLE and DBA database roles. 

Oracle8i Administrator's Guide 

SYS

 

CHANGE_ON_INSTALL 

SYS is used for performing database administration tasks. SYS includes the following database roles:

  • AQ_ADMINISTRATOR_ROLE

  • AQ_USER_ROLE

  • CONNECT

  • CTXAPP

  • DBA

  • DELETE_CATALOG_ROLE

  • EXECUTE_CATALOG_ROLE

  • EXP_FULL_DATABASE

  • HS_ADMIN_ROLE

  • IMP_FULL_DATABASE

  • JAVA_ADMIN

  • JAVADEBUGPRIV

  • JAVAIDPRIV

  • JAVAUSERPRIV

  • OEM_MONITOR

  • RECOVERY_CATALOG_OWNER

  • RESOURCE

  • SELECT_CATALOG_ROLE

  • SNMPAGENT

  • TIMESERIES_DBA

  • TIMESERIES_DEVELOPER

 

Oracle8i Administrator's Guide 

OUTLN  

OUTLN 

OUTLN includes the CONNECT and RESOURCE database roles, and supports plan stability. Plan stability allows you to maintain the same execution plans for the same SQL statements. OUTLN acts as a place to centrally manage metadata associated with stored outlines. 

 

SCOTT  

TIGER 

SCOTT includes the CONNECT and RESOURCE database roles. 

Oracle8i Administrator's Guide 

COMDEMO  

COMDEMO 

COMDEMO is the Oracle COM Automation feature user name with DBA and RESOURCE database roles. 

Oracle COM Automation Developer's Guide 

PO8 

PO8 

PO8 is the user name used by Oracle8i Navigator to connect to the local database 

Oracle8i Personal Edition Administrator's Guide for Windows 98, Chapter 5 

Database Identification

The Oracle8i database is identified by its global database name, which consists of the database name and network domain in which the database is located. The global database name uniquely distinguishes a database from any other database in the same network domain. You create a global database name when prompted in the Database Identification window during Oracle8i database installation. The global database name takes the form: 

database_name.database_domain

For example: 

sales.us.acme.com

Where...  Is... 

sales 

The name you give your database. The database name portion is a string of no more than 8 characters that can contain alpha, numeric, and additional characters. The database name is also assigned to the DB_NAME parameter in the INIT.ORA file. 

us.acme.com 

The network domain in which the database is located, making the global database name unique. The domain portion is a string of no more than 128 characters that can contain alpha, numeric, period (.), and additional characters. The domain name is also assigned to the DB_DOMAIN parameter in the INIT.ORA file. 

The DB_NAME parameter (value sales) and DB_DOMAIN name parameter (value us.acme.com) combine to create the global database name value assigned to the SERVICE_NAMES parameter (value sales.us.acme.com) in the INIT.ORA file.

The System Identifier (SID) identifies a specific Oracle8i instance that references the database. The SID uniquely distinguishes a database from any other database on the same computer. Multiple Oracle homes enable you to have multiple, active Oracle databases on a single computer. Each database requires a unique SID and database name.

The SID name is taken from the value you entered for the database name in the Database Identification window, although you had the opportunity to change it. The SID can be up to 64 alphanumeric characters in length.

For example, if the SID and database name for an Oracle database are ORCL, each database file is located in the ORACLE_BASE\ORADATA\ORCL directory and the initialization parameter file is located in the ORACLE_BASE\ADMIN\ORCL \PFILE directory. The directory ORCL is named after the DB_NAME parameter value.

Tablespaces and Data Files

An Oracle8i database is divided into smaller logical areas of space known as tablespaces. Each tablespace corresponds to one or more physical data files. Data files contain the contents of logical database structures such as tables and indexes. A data file can be associated with only one tablespace and database.

The tablespaces in the Oracle8i database contain the following types of data files located in the ORACLE_BASE\ORADATA\DB_NAME directory:

Note:

Unless you specified different names with Oracle Database Configuration Assistant, the tablespaces and data files described in the following table are also automatically included in the Custom database. 

Tablespace  Data File  Contains... 

SYSTEM  

SYSTEM01.DBF 

The data dictionary, including definitions of tables, views, and stored procedures needed by the Oracle database. Information in this area is maintained automatically. The SYSTEM tablespace is present in all Oracle databases. 

USERS  

USERS01.DBF 

Your application data. As you create and enter data into tables, you fill this space with your data. 

TEMP  

TEMP01.DBF 

Temporary tables and/or indexes created during the processing of your SQL statement. You may need to expand this tablespace if you are executing a SQL statement that involves a lot of sorting, such as ANALYZE COMPUTE STATISTICS on a very large table, or the constructs GROUP BY, ORDER BY, or DISTINCT. 

RBS  

RBS01.DBF 

Rolled back transactions that fail to complete normally. You may need to expand this tablespace if you have long-running or high-data-volume transactions. 

INDX  

INDX01.DBF 

Indexes associated with the data in the USERS tablespace. 

TOOLS 

TOOLS01.DBF 

Nothing. This data file is created for use if the user wants to install any third-party or Oracle tools/products. 

See Also:

 

Initialization Parameter File

The starter database contains one database initialization parameter file located in the ORACLE_BASE\ADMIN\DB_NAME\PFILE directory:

Initialization Parameter File  Description 

INIT.ORA 

The parameter file INIT.ORA 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. No edits are required to this file in order to use the starter database. 

See Also:

  • Appendix B of Oracle8i Personal Edition Administrator's Guide Release 2 (8.1.6) for Windows 98 for a list of Oracle8i database-specific initialization parameters for Windows 98 and their default values

  • Oracle8i Reference for more information on initialization parameters

 

Redo Log Files

The starter database contains three redo log files located in the ORACLE_BASE\ORADATA\DB_NAME directory:

Note:

The redo logs REDO01.LOG, REDO02.LOG, and REDO03.LOG are also automatically included in the Custom database. 

Database Files  Disk Size  Description 

REDO01.LOG

REDO02.LOG

REDO03.LOG

 

1 MB

1 MB

1 MB 

Redo log files hold a record of all changes made to data in the database buffer cache. If an instance failure occurs, the redo log files are used to recover the modified data that was in memory.

Redo log files are used in a cyclical fashion. For example, if three files constitute the online redo log, the first file is filled, then the second file, and then the third file. The first file is then re-used and filled, the second file is re-used and filled, and so on.  

See Also:

Oracle8i Backup and Recovery Guide 

Control Files

The starter database contains three control files located in the ORACLE_BASE\ ORADATA\DB_NAME directory:

Control Files  Description 

CONTROL01.CTL

CONTROL02.CTL

CONTROL03.CTL 

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's data files and redo log files. 

Note:

The files CONTROL01.CTL, CONTROL02.CTL, and CONTROL03.CTL are also automatically included in the Custom database. 

Note:

Oracle Corporation 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. See Chapter 5 "Managing Control Files" of Oracle8i Administrator's Guide for information on setting this initialization parameter value. 

Rollback Segments

Rollback segments record the old values of data changed by each transaction (whether or not committed). Every database contains one or more rollback segments, which are portions of the database that record the actions of transactions in the event that a transaction is rolled back. Rollback segments are used to provide read consistency, to roll back transactions, and to recover the database.

The starter database contains the following rollback segments:

Rollback Segment  Contained in this Tablespace...   Used by 

SYSTEM 

SYSTEM 

SYS 

RB_TEMP 

SYSTEM (private) 

SYS 

RB1 through RB16 

RBS 

PUBLIC (a pool of rollback segments that any instance requiring a rollback segment can use) 

Data Dictionary

The data dictionary is a protected collection of tables and views containing reference information about the database, its structures, and its users. The data stored in the dictionary includes the following:

Prev Next
Oracle
Copyright © 2000 Oracle Corporation.
All Rights Reserved.

Library
Product
Contents
Index