| Oracle9i Database Installation Guide Release 2 (9.2.0.2.1) for 64-Bit Windows Part Number B10546-01 |
|
This chapter provides overviews of the contents of the default starter database created through Database Configuration Assistant for the Enterprise Edition, Standard Edition, Personal Edition, or Oracle Internet Directory. Where possible, references to information applicable to the custom database creation method are provided.
This chapter contains these topics:
Oracle9i installs with a number of default database accounts. Database Configuration Assistant locks and expires all default database accounts upon successful installation with the following exceptions:
You must unlock all other accounts before using them. Oracle Corporation recommends changing all user passwords immediately after installation.
At a minimum, Database Configuration Assistant creates the SYS, SYSTEM, and DBSNMP accounts in all databases. At the end of the database creation process, you are required to change the SYS and SYSTEM passwords. Additional accounts are created depending on the components installed. Unlock accounts and change passwords before using these accounts. Table 6-2 describes the accounts and passwords.
At the end of installation, several configuration assistants automatically start to create and configure your database and Oracle Net Services environments. One such assistant is the Database Configuration Assistant. When Database Configuration Assistant finishes your database configuration, it displays a screen with your database information and the Password Management button. You are required to change the SYS and SYSTEM passwords on this screen. Use the Password Management button to unlock only the usernames you will use. Oracle Corporation strongly recommends changing the default password immediately after unlocking the username.
To change a password during the database installation and configuration process:
Alternatively, use SQL*Plus to unlock accounts and change passwords any time after the installation process.
To change a password after installation:
C:\> sqlplus /NOLOG
SYSDBA:
SQL> CONNECT / AS SYSDBA
Table 6-1 SQL Commands for Administering Accounts and Passwords
Table 6-2 describes the administrative usernames and passwords.
| Username | Password | Description | See Also |
|---|---|---|---|
|
|
User assignedFoot 1
|
Used for performing database administration tasks. |
Oracle9i Database Administrator's Guide |
|
|
|
Used for performing database administration tasks.Foot 3 |
Oracle9i Database Administrator's Guide |
|
|
|
Allows HTTP access to Oracle XML DB. |
Not applicable |
|
|
|
The Oracle Text username with |
Oracle Text Reference |
|
|
|
Includes the |
Oracle Intelligent Agent User's Guide |
|
|
|
The Oracle Label Security administrator username. |
Oracle Label Security Administrator's Guide |
|
|
|
The Oracle Spatial and Oracle Locator administrator username. |
Oracle Spatial User's Guide and Reference |
|
|
ODM |
|
|
|
|
MTRPW |
|
|
|
|
|
|
Oracle9i OLAP Application Developer's Guide |
|
|
|
The Oracle interMedia Audio and Video username with |
Oracle interMedia Reference |
|
|
|
The Oracle interMedia Audio, Video, Locator, and Image administrator username with |
Oracle interMedia Reference |
|
|
|
Includes |
Oracle9i Database Platform Guide for Windows |
|
|
|
Used for storing Ultra Search system dictionaries and PL/SQL packages. |
Oracle Ultra Search Online Documentation |
|
|
|
The |
Oracle9i Application Developer's Guide - Workspace Manager |
|
|
|
Used for storing Oracle XML DB data and metadata. Includes |
Not applicable |
The Oracle9i 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. You create a global database name when prompted in the Oracle Universal Installer Database Identification window during database installation. The global database name takes the form:
database_name.database_domain
For example:
sales.us.acme.com
where sales is the name you have give your database, and us.acme.com is the network domain in which the database is located. The database name portion is a string of no more than eight characters that can contain alpha, numeric, and additional characters. The database name is assigned to the DB_NAME parameter in the init.ora file
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 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).
The system identifier (SID) identifies a specific Oracle9i instance that references the database. The SID uniquely distinguishes a database instance from any other database instance on the same computer. Multiple Oracle homes enable you to have multiple, active Oracle databases on a single computer. Each database requires a unique global database name, and each database instance on the same computer requires a unique SID.
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 8 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.
Two main Oracle services are automatically started after a installation when you create a database:
OracleServiceSID (the Oracle9i database service)
OracleHOME_NAMETNSListener (the Oracle9i database listener service)
If you installed Oracle Enterprise Manager components, additional services automatically start:
However, other services for networking or other individual components may not automatically start.
|
See Also:
|
An Oracle9i 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.
Table 6-3 list the tablespaces and datafiles in the Oracle9i database. Datafiles are located in the ORACLE_BASE\oradata\DB_NAME directory.
| Tablespace | Datafile | Contains... |
|---|---|---|
|
|
|
OLAP tablespace |
|
|
|
Oracle Text-related Schema objects. |
|
|
|
Sample Schema |
|
|
|
Indexes associated with the data in the |
|
|
|
|
|
|
|
Temporary tables and 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 the constructs |
|
|
|
Nothing. This datafile is created for use if the user wants to install any third-party or Oracle tools/components. |
|
|
|
The data dictionary, including definitions of tables, views, and stored procedures needed by the Oracle9i database. Information in this area is maintained automatically. The |
|
|
|
A dedicated tablespaces that stores only undo information when the database is run in automatic undo management mode. An undo tablespace contains one or more undo segments. Undo segments 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. |
|
|
|
Your application data. As you create and enter data into tables, you fill this space with your data. |
|
|
|
Used for storing Oracle XML DB data and metadata. |
The starter database contains one database initialization parameter file located in the ORACLE_BASE\admin\DB_NAME\pfile directory.
The initialization 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.
The starter database contains three redo log files located in the ORACLE_BASE\oradata\DB_NAME directory.
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 contains three control files located in the ORACLE_BASE\ oradata\DB_NAME directory.
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.
Oracle9i databases are capable of managing their own undo (rollback) segments. Administrators no longer need to carefully plan and tune the number and sizes of rollback segments or decide how to strategically assign transactions to a particular rollback segment. Oracle9i also allows administrators to allocate their undo space in a single undo tablespace with the database taking care of issues such as undo block contention, consistent read retention, and space utilization.
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:
|
|
![]() Copyright © 2003 Oracle Corporation. All Rights Reserved. |
|