Planning
for Database Creation
Specifying
Database Block Sizes
Select
the database character set
Develop
a backup and recovery strategy
Plan the database tables and indexes and estimate the amount of space they will require.
can improve database performance dramatically by distributing the I/O during file access. You can distribute I/O in several ways when you install Oracle software and create your database. For example, you can place redo log files on separate disks or use striping. You can situate datafiles to reduce contention.
Consider using Oracle-managed files and Automatic Storage Management
By including any of the initialization parameters DB_CREATE_FILE_DEST, DB_CREATE_ONLINE_LOG_DEST_n, or DB_RECOVERY_FILE_DEST in your initialization parameter file,
you instruct Oracle Database to create and manage the underlying operating system files of your database.
select name, value, con_id from v$parameter where name like
'db_create_file_dest' --initialization
parameters in current session.
select name, value, con_id from V$SYSTEM_PARAMETER where name like
'db_create_file_dest' --
initialization
parameters in effect for the instance
NAME |
VALUE |
CON_ID |
db_create_file_dest |
|
0 |
db_create_file_dest |
D:\APP\DARKOJ\ORADATA\ORCLD\PDB3\ |
5 |
(Parametri pluggable baza nisu u spfile datoteci vec u dictionary tabeli - Initialization parameters for pluggable databases are not kept in the spfile – if they are not inherited from the container database, that is. Instead, they are stored in a dictionary table of the container database. The documented view V$SYSTEM_PARAMETER displays them. But only if the pluggable database is opened.)
Select the global database name, which is the name and location of the database within the network structure. Create the global database name by setting both the DB_NAME and DB_DOMAIN initialization parameters.
DB_NAME = MCDB, DB_DOMAIN = DATA-GLOB.CO.YU (Important for distributed DB)
The CONTROL_FILES initialization parameter specifies one or more control filenames for the database. When you execute the CREATE DATABASE statement, the control files listed in the CONTROL_FILES parameter are created.
The DB_BLOCK_SIZE initialization parameter specifies the standard block size for the database. This block size is used for the SYSTEM tablespace and by default in other tablespaces. Oracle Database can support up to four additional nonstandard block sizes.
*.db_block_size=8192
DB_BLOCK_SIZE=4096
Caution: AL32UTF8 is the Oracle Database character set that is appropriate for XMLType data.
SQL> select * from
nls_database_parameters;
Plan to use a default tablespace for non-SYSTEM users to prevent inadvertent saving of database objects in the SYSTEM tablespace.
select * from database_properties where property_name like 'DEFAULT%TABLESPACE'; --primer za pluggable pdb3
PROPERTY_NAME |
PROPERTY_VALUE |
DESCRIPTION |
DEFAULT_TEMP_TABLESPACE |
TEMP |
Name of default temporary tablespace |
DEFAULT_PERMANENT_TABLESPACE |
SYSTEM |
Name of default permanent tablespace |
Develop a backup and recovery strategy to protect the database from failure. It is important to protect the control file by multiplexing, to choose the appropriate backup mode, and to manage the online and archived redo logs.