User`s guide

See Also: Refer to "Using Oracle Managed Files" in Oracle Database
Administrator's Guide for more information about file name formats
Address Space Planning
Architecture and Implementation 2-5
2.2.4 Bigfile Tablespaces
Oracle Database 11g Release 2 on BS2000/OSD supports bigfile tablespaces. The single
data file of a bigfile tablespace must reside on a BS2000 pubset with the following
attributes
LARGE_VOLUMES=*ALLOWED and LARGE_FILES=*ALLOWED
See Also: Refer to "Files and Volumes Larger than 32 GB" for more
information about handling large objects on BS2000/OSD at
http://manuals.ts.fujitsu.com/file/9118/dv32.pdf
2.3 Two-Task Mode
In two-task mode, a user task connects to a server task, which runs Oracle Database
code on behalf of the user task. The user task does not have access to the SGA.
Communication between a user task and a server task is through Oracle Net Services.
2.4 Address Space Planning
Oracle Database uses a number of data and code areas, which must be at the same
virtual addresses in all server and background tasks. Typically, the default values
provided with Oracle Database are sufficient. Address space planning (explicit
placement of Oracle Database data areas) may be required in some special situations,
when you encounter address space conflicts. For example, dynamic subsystems may
occupy the default address ranges, which may require you to relocate Oracle Database
areas.
2.4.1 Oracle Database Data Area Placement
The following ORAENV variables control explicit placement of Oracle Database data
areas:
■ COM_BASE
■ KNL_BASE
■ PGA_BASE
■ SGA_BASE
The order of the areas in the address space is not significant. The
xxx_BASE variable is
evaluated only during STARTUP processing.
After the database is started, users attaching to it
do not need to specify the values in
the
ORAENV files, as they are automatically supplied with the common values during
connection. This means that the settings in the user’s
ORAENV file are ignored.
Figure 2–1 gives an example of the placement of data areas.