3
Starter Database Contents

Typical  

A fully configured and ready-to-use starter database with a default name of ORACLE and a SID of ORCL. During installation, you can also choose to include the Oracle8 ConText Cartridge in your starter database.

See the section "Starter Database Contents" for information on the contents of your starter database.  

Custom using Oracle Database Assistant  

The opportunity to create a customized database with the help of Oracle Database Assistant. If you select this option, Oracle Database Assistant automatically starts at the end of the installation process. Oracle Database Assistant offers you two choices of databases to create:

• Typical

Creates a standard database with default INITSID.ORA file parameter settings.

You can also create an extra tablespace called INDEX and an extra control file. Both features are available if you select (when prompted) to create new database files instead of copying the existing database files from your CD-ROM disc. Typical enables you to select whether to include the Oracle8 ConText Cartridge in your database

• Custom

Enables you to customize INITSID.ORA file parameter settings for your database. This option is only for Oracle database administrators (DBAs) experienced with advanced database creation procedures. Custom automatically creates an extra tablespace called INDEX and an extra control file. Custom enables you to select whether to include the Oracle8 ConText Cartridge in your database.  

See Chapter 9, "Creating a Database" for additional information on creating a database.  

INTERNAL  

ORACLE is automatically the password if you installed your Oracle8 database using the Oracle8 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 account; it is an alias for the SYS user account and SYSDBA privilege.

Note: INTERNAL uses the SYS schema, listed below, with additional SYSDBA privileges. See the chapter "The Oracle Database Administrator" of the Oracle8 Server Administrator's Guide for more information.  

SYS  

CHANGE_ON_INSTALL  

DBA user name with the following database roles:

• CONNECT
• RESOURCE
• DBA
• AQ_ADMINISTRATOR_ROLE
• AQ_USER_ROLE
• DELETE_CATALOG_ROLE
• EXECUTE_CATALOG_ROLE
• EXP_FULL_DATABASE
• IMP_FULL_DATABASE
• RECOVERY_CATALOG_OWNER
• SELECT_CATALOG_ROLE
• SNMPAGENT
• CTXADMIN1
• CTXAPP1
• CTXUSER1

SYSTEM  

MANAGER  

DBA user name with the DBA database role.  

SCOTT  

TIGER  

User name with CONNECT and RESOURCE database roles.  

DEMO  

DEMO  

User name with CONNECT and RESOURCE database roles. Oracle recommends that you drop this account if it is not needed.  

DBSNMP  

DBSNMP  

Oracle Enterprise Manager Administrator user name with CONNECT, RESOURCE, and SNMPAGENT database roles.

If you want to drop this role and user, run CATNSNMP.SQL.  

CTXSYS¹  

CTXSYS  

ConText administrator user name with CONNECT, RESOURCE, and DBA roles.  

Change the passwords for the SYS, SYSTEM, and CTXSYS accounts immediately after installation with the following SQL statement from the Server Manager utility:

SVRMGR> ALTER USER USERNAME IDENTIFIED BY PASSWORD;

See Chapter 4, "Database Tools" for information on starting Server Manager.  

See the chapters "The Oracle Database Administrator" and "Managing Users and Resources" of the Oracle8 Server Administrator's Guide.  

SYSTEM  

Consists of 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  

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

TEMPORARY_DATA  

Consists of 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  

Consists of 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.  

See the chapter "Tablespaces and Datafiles" of Oracle8 Server Concepts and the chapter "Managing Tablespaces" of the Oracle8 Server Administrator's Guide.  

SYS1ORCL.ORA  

SYSTEM  

USR1ORCL.ORA  

USER_DATA  

RBS1ORCL.ORA  

ROLLBACK_DATA  

TMP1ORCL.ORA  

TEMPORARY_DATA  

See the chapter "Tablespaces and Datafiles" of Oracle8 Server Concepts and the chapter "Managing Datafiles" of the Oracle8 Server Administrator's Guide.  

INITORCL.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 INITORCL.ORA that has preconfigured parameters. No edits are required to this file in order to use the starter database.  

See Appendix B, "Initialization Parameter Files" of this guide. This appendix lists the Oracle8 database-specific initialization parameters for Windows NT and their default values. See Oracle8 Server Reference for further information on initialization parameters.  

LOG1ORCL.ORA

LOG2ORCL.ORA  

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.  

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

CTL1ORCL.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.  

Oracle Corporation recommends that you keep multiple 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 Server Administrator's Guide for information on setting this initialization parameter value.