User`s guide

Note: Both the BS2000/OSD operating system and Oracle Database
perform input and output efficiently in units called blocks. A block is
the basic unit of data storage. An Oracle Database block can be in one
of the following formats:
■ 2K, 4K, 6K, 8K, 16K, 32K when using BS2000 2K pubset format
■ 4K, 8K, 16K, 32K when using BS2000 4K pubset format
Oracle Database and redo log files are BS2000 PAM files, and Oracle
Data
base uses UPAM to access them.
Basic Structures
Architecture and Implementation 2-3
2.2.2 Other Oracle Database Files
The following are the additional Oracle Database files:
■ Initialization File
■ Server Parameter File
■ ORAENV File
■ Control Files
■ Message Files
2.2.2.1 Initialization File
The initialization file, INIT.ORA , contains a set of parameters that are read when an
instance is started.
See Also: Oracle Database Reference and Oracle Database
Administrator's Guide for more information about the initialization file
2.2.2.2 Server Parameter File
The server parameter file ( SPFILE ) is a binary server-side initialization file, which
cannot be edited using a text editor. It is initially built from a traditional text
initialization file using the
CREATE SPFILE statement.
2.2.2.3 ORAENV File
Oracle Database utilities and products running in the native BS2000 environment use
the Oracle Database environment definition file, which is referenced as
ORAENV . This
file contains the Oracle Database environment variables, which are used to describe
the operating environment for each Oracle Database task. The database administrator
also uses the
ORAENV file to define BS2000-specific parameters necessary for database
configuration.
2.2.2.4 Control Files
These files record the physical structure of a database and are specified in the
initialization file.
2.2.2.5 Message Files
Message texts are stored in table modules, which are dynamically loaded from the
ORAMESG library at execution time.