5
Starter Database Contents

This chapter describes the contents of the Oracle8 Enterprise Edition starter database.

Specific topics discussed are:

• Starter Database Guide

• Starter Database Contents

Starter Database Guide

Oracle8 Enterprise Edition is installed when you select the:

• Oracle8 Enterprise Edition installation option

• Custom installation option, then select Oracle8 Enterprise Edition in the Software Asset Manager window

  Note: Oracle8 Enterprise Edition cannot be installed through the Oracle8 Client option.

Both these installation processes prompt you to install either of three types of database configurations:

• Typical Configuration (installs the starter database)

• Custom Configuration, which starts Oracle Database Assistant at the end of installation and enables you to create a custom database

• None, which means you must manually create a database by following the instructions in "Using BUILD_DB.SQL"

This table describes some of the features available with each configuration:

Database Feature	Typical Configuration	Custom Configuration
Type of Database Created	Automatically creates a fully preconfigured and ready-to-use starter database with default INITSID.ORA file parameter settings.	Enables you to create your own database with customized INITSID.ORA parameter settings. This option is only for Oracle database administrators (DBAs) experienced with advanced database creation procedures.
Database Name	Automatically named ORCx1.	Your choice.
System Identifier (SID) Name	Automatically named ORCx1.	Your choice.
Cartridges and Options	Both configuration types allow you to select the following cartridges and options for installation: Oracle8 ConText Cartridge Oracle8 Spatial Cartridge Oracle8 Image Cartridge Oracle8 Time Series Cartridge Oracle8 Visual Image Retrieval Cartridge Oracle Parallel Server Option Oracle8 Partitioning Option Oracle8 Objects Option
Advanced replication (updatable snapshots)	Automatically installed.	Your choice.
User names, database files, and tablespaces	Automatically creates the user names, database files, and tablespaces described in "Starter Database Contents".	Automatically creates the SYS, SYSTEM, SCOTT, DEMO, and DBSNMP user names and INTERNAL alias described in "Starter Database Contents", but enables you to customize tablespace and database file settings and create an extra control file and extra tablespace named INDEX. An Oracle8 Cartridge user name is only created if you select that specific cartridge for installation when running Oracle Database Assistant.
Initial archiving mode	Set to NOARCHIVELOG	Your choice.

1 When you install the Oracle8 database for the first time on a computer, your SID and database name are typically named ORCL. For each additional Oracle8 database installation on the same computer, the last letter of ORCL is replaced by a number and automatically incremented (that is, for a second Oracle8 database installation, the SID and database name are ORC1, for a third Oracle8 database installation, the SID and database name are ORC2, etc.).

Additional Information: You can still create a custom database manually. See Chapter 9, "Creating a Database" for additional information.

Starter Database Contents

The starter database you receive if you select the Typical Configuration database option contains the following features:

• User Names

• System Identifier

• Tablespaces

• Data Files

• Initialization Parameter File

• Redo Log Files

• Control File

• Data Dictionary

• Rollback Segments

User Names

Your starter database contains these user names:

User Name	Passwords	Description
INTERNAL	ORACLE is automatically the password if you installed your Oracle8 database using the Oracle8 Enterprise Edition option. If you installed your Oracle8 database using the Custom option, the password is whatever you entered when prompted during installation.	DBA user name with which to perform 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 and SYSDBA privilege. Note: INTERNAL uses the SYS schema, listed below, with additional SYSDBA privileges. See the chapter "The Oracle Database Administrator" in Oracle8 Administrator's Guide for more information.
SYS	CHANGE_ON_INSTALL	DBA user name with the following database roles: AQ_ADMINISTRATOR_ROLE AQ_USER_ROLE CONNECT DBA DELETE_CATALOG_ROLE EXECUTE_CATALOG_ROLE EXP_FULL_DATABASE HS_ADMIN_ROLE IMP_FULL_DATABASE RECOVERY_CATALOG_OWNER RESOURCE SELECT_CATALOG_ROLE SNMPAGENT
SYSTEM	MANAGER	DBA user name with DBA database role.
SCOTT	TIGER	User name with CONNECT and RESOURCE database roles.
DEMO	DEMO	User name with CONNECT and RESOURCE database roles. Oracle Corporation recommends that you drop this account if it is not needed.
DBSNMP	DBSNMP	User name with CONNECT, RESOURCE, and SNMPAGENT database roles. If you want to drop this role and user, run CATNSNMP.SQL.
MDSYS1	MDSYS	Oracle8 Spatial Cartridge administrator user name.
ORDSYS1	ORDSYS	Oracle8 Image, Time Series, and Visual Information Retrieval Cartridges administrator user name with CONNECT and RESOURCE database roles.

1 If you install the starter database through the Oracle8 Enterprise Edition option, MDSYS and ORDSYS are automatically created even if you do not select their Oracle8 Cartridges for installation.

Note: Change the passwords for the SYS, SYSTEM, MDSYS, and ORDSYS user names immediately after installation with the following SQL statement at the Server Manager prompt: SVRMGR> ALTER USER USERNAME IDENTIFIED BY PASSWORD; See Chapter 3, "Database Tools Overview" for information on starting Server Manager.

Note: If you create an Oracle8 database through the Custom Configuration option, the Oracle8 Cartridge user names described in the previous table are only created if you select the cartridges for installation with which each are used.

System Identifier

Each Oracle8 database has a SID. A SID is a unique name for an Oracle database instance that can be up to four alphanumeric characters in length.

For example, if the SID for an Oracle8 database is ORCL, each database file in the ORACLE_HOME\DATABASE directory has ORCL as part of its name (for example, CTL1ORCL.ORA, LOG1ORCL.ORA, and INITORCL.ORA). The multiple Oracle homes feature enables you to have multiple, active Oracle8 databases installed on a single computer. Each database requires a unique SID. To ensure that each SID is unique, the last letter of ORCL is automatically replaced by a number and incremented each time you install Oracle products into a different home (that is, for a second Oracle8 database installation, the SID is ORC1, for a third Oracle8 database installation, the SID is ORC2, etc.). See Chapter 6, "Using Multiple Oracle Homes" for further information. Because of this, the data files, initialization files, redo log files, and control files described below use a variable of SID in their names. When you see SID, substitute it with the SID for your Oracle8 database.

Tablespaces

An Oracle8 database is subdivided into smaller logical areas of space known as tablespaces. Each tablespace corresponds to one or more physical data files. The four tablespaces in the Oracle8 database contain the following types of data:

Tablespace	Consists of This Type of Data...
SYSTEM	The data dictionary, including definitions of tables, views, and stored procedures needed by the Oracle8 database. Information in this area is maintained automatically. The SYSTEM tablespace is present in all Oracle8 databases.
USER_DATA	Your application data. As you create and enter data into tables, you fill this space with your data.
TEMPORARY_DATA	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.
ROLLBACK_DATA	Rolling back transactions that fail to complete normally. You may need to expand this tablespace if you have long-running or high-data-volume transactions.

Additional Information: See the chapter "Tablespaces and Datafiles" of Oracle8 Concepts and the chapter "Managing Tablespaces" in Oracle8 Administrator's Guide.

Data Files

Data files contain the contents of logical database structures such as tables and indexes. One or more data files form a logical unit of storage called a tablespace. A data file can be associated with only one tablespace, and only one database. The starter database contains the following four data files located in the ORACLE_HOME\DATABASE directory:

This Data File...	Is Contained in the Tablespace...
SYS1SID.ORA	SYSTEM
USR1SID.ORA	USER_DATA
TMP1SID.ORA	TEMPORARY_DATA
RBS1SID.ORA	ROLLBACK_DATA

Additional Information: See the chapter "Tablespaces and Datafiles" of Oracle8 Concepts and the chapter "Managing Datafiles" in Oracle8 Administrator's Guide.

Initialization Parameter File

The starter database contains one initialization parameter file located in the ORACLE_HOME\DATABASE directory:

Initialization Parameter File	Description
INITSID.ORA	The parameter file INITSID.ORA must exist for an instance to start. A parameter file is a text file containing a list of instance configuration parameters. The starter database includes a file called INITSID.ORA that has preconfigured parameters. No edits are required to this file in order to use the starter database.

Additional Information: See Appendix B, "Oracle8 Database Specifications for Windows NT" of this guide. This appendix lists the Oracle8 database-specific initialization parameters for Windows NT and their default values. See Oracle8 Reference for further information on initialization parameters.

Redo Log Files

The starter database contains four redo log files located in the ORACLE_HOME\DATABASE directory, each 1 MB in size:

Database Files	Disk Size	Group	Description
LOG1SID.ORA LOG2SID.ORA LOG3SID.ORA LOG4SID.ORA	1 MB 1 MB 1 MB 1 MB	4 3 2 1	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 four files constitute the online redo log, the first file is filled, then the second file, then the third file, and then the forth file. The first file is then re-used and filled, the second file is re-used and filled, and so on.

Additional Information: See the chapters "Managing the Online Redo Log" in Oracle8 Administrator's Guide and "Recovering a Database" of Oracle8 Backup and Recovery.

Control File

The starter database contains one control file located in the ORACLE_HOME\ DATABASE directory:

Control Files	Description
CTL1SID.ORA	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: Oracle Corporation recommends that you keep at least two control files (on separate physical drives) for each database and set the CONTROL_FILES initialization parameter to list each control file. See the chapter "Managing Control Files" of the Oracle8 Administrator's Guide for information on setting this initialization parameter value.

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:

• Names of the Oracle8 database users

• Privileges and roles granted to each user

• Names and definitions of schema objects (including tables, views, snapshots, indexes, clusters, synonyms, sequences, procedures, functions, and packages)

• Integrity constraints

• Space allocation for database objects

• Auditing information, such as who accessed or updated various objects

  Additional Information: See the chapter "The Data Dictionary" of Oracle8 Concepts and "Static Data Dictionary Views" in Oracle8 Reference.

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)

Creating Control, Data, and Log Files on Remote Computers

Although it is possible for Oracle to access database files on remote computers using Universal Naming Convention (UNC), it is not recommended because of performance and network reliability concerns.

UNC is a PC format for specifying the location of resources on a local area network. UNC uses the following format:

\\server-name\shared-resource-pathname

For example, to access the file SYSTEM01.DBF in the directory C:\ORACLE\ORA81\ORADATA\ORCL on the shared server ARGON, you reference the file as:

\\ARGON\ORACLE\ORA81\ORADATA\ORCL\SYSTEM01.DBF

Note that the location of archive log files cannot be specified using UNC. If you set the LOG_ARCHIVE_DEST initialization parameter to a UNC specification, the database does not start and you receive the following errors:

ORA-00256: error occurred in translating archive text string '\meldell\rmdrive'
ORA-09291: sksachk: invalid device specified for archive destination 
OSD-04018: Unable to access the specified directory or device
O/S-Error: (OS 2) The system cannot find the file specified

Ensure that you set the LOG_ARCHIVE_DEST initialization parameter to a mapped drive.

Note: An ORA-00256 error also occurs if you enter: \\\meldell\rmdrive or \\\meldell\\rmdrive Control files required the additional backslashes for release 8.0.4, but redo files and data files did not.