置。 3.2.2 Maximum of 10 dispatchers
SQL> alter system set max_dispatchers=10 scope=both;
3.3.Configure the PROD database to support: 3.3.1 Minimum of 10 shared server processes
SQL> alter system set shared_servers=10 scope=both;
3.3.2 Maximum of 30 shared server processes
SQL> alter system set max_shared_servers=30 scope=both;
4. Client-side Network configuartion
4.1. Create the client-side network configuration files providing connect descriptors to your databases using local naming and easy connect methods. 4.1.1 The prod alias should connect to the PROD instance using the default listener and always use a dedicated server connection.
prod =
(DESCRIPTION = (ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = test)(PORT = 1521)) )
(CONNECT_DATA =
(SERVER = DEDICATED) (SERVICE_NAME = PROD) ) )
4.1.2 The prod_s alias should connect to the PROD instance using LSNR2 and use a shared server connection.
prod_s =
(DESCRIPTION = (ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = test)(PORT = 1526)) )
(CONNECT_DATA = (SERVER = SHARED)
(SERVICE_NAME = PROD) ) )
*******************************************
用户通过prod_s连接上来后，查询session目前连接的结果如下： SYS>select sid, server from v$session;
SID SERVER ---------- ---------
277 DEDICATED 278 NONE
279 DEDICATED 281 DEDICATED
NONE就代表了通过dispatcher连接上来的session,当前没有执行会话，如果执行了
会话，就会变为shared。
4.2. The racdb alias should connect to the RACDB service (created later) with a dedicated server connection. 4.2.1 The RACDB service will be running on your RAC Cluster.
racdb =
(DESCRIPTION = (ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = rac1)(PORT = 1521)) (ADDRESS = (PROTOCOL = TCP)(HOST = rac2)(PORT = 1521)) )
(CONNECT_DATA =
(SERVICE_NAME = RACDB) ) )
4.3. The emrep alias should connect to the EMREP instance instance (created later) with a dedicated server connection.
emrep =
(DESCRIPTION = (ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = test)(PORT = 1521)) )
(CONNECT_DATA =
(SERVICE_NAME = EMREP) ) )
5. Tablespace Creation and Configuration
Note:Tablespaces must be named as specified in each task to receive credit .
5.1 Create a temporary tablespace group that contains two(2) temporary tablespaces to support batch processing.the creation of large indexes, and analyzing tables.Use the following specifications: 5.1.1Temporary tablespace group named TEMP_GRP containing temporary tablespaces TEMP1 and TEMP2.
create temporary tablespace temp1
tempfile '/oracle/oradata/temp1_01_grp.dbf' size 20m AUTOEXTEND ON MAXSIZE UNLIMITED tablespace group TEMP_GRP ;
create temporary tablespace temp2
tempfile '/oracle/oradata/temp2_01_grp.dbf' size 20m AUTOEXTEND ON MAXSIZE UNLIMITED tablespace group TEMP_GRP ;
5.1.2 Make TEMP_GRP the default temporary tablespace for all new users.
alter database default temporary tablespace TEMP_GRP; (SQL> select * from dba_tablespace_groups;)
5.2 Create a permanent tablespace to store sample test data.Use the following specifications: 5.2.1 Tablespace name of EXAMPLE 5.2.2 Inital datafile size of 400MB with the file expected to grow to 4TB. 5.2.3 Initial extent size of 1MB 5.2.4 Next extent size of 1MB
-- drop tablespace EXAMPLE including contents and datafiles ; CREATE BIGFILE TABLESPACE example
DATAFILE '/oracle/oradata/example01.dbf' SIZE 400M AUTOEXTEND ON NEXT 1M MAXSIZE 4T
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1M SEGMENT SPACE MANAGEMENT AUTO ;
5.3 Create a permanent tablespace to store indexes.Use the following specifications: 5.3.1 Tablespace name of INDX 5.3.2 File size of 40MB
create tablespace INDX
datafile '/oracle/oradata/index01.dbf' size 40m AUTOEXTEND ON ;
5.4 Create a permanent tablespace to store data collected from various Oracle tools.Use the following specifications: 5.4.1 Tablespace name of TOOLS 5.4.2 File size of 10MB
-- drop tablespace TOOLS including contents and datafiles ; create tablespace TOOLS
datafile '/oracle/oradata/tools01.dbf' size 10m AUTOEXTEND ON ;
5.5 Create a default permanent tablespace using the following specifications: 5.5.1 Tablespace name of USERS 5.5.2 File size of 48MB 5.5.3 Initial extent size of 4MB 5.5.4 Next extent size of 4MB
-- drop tablespace USERS including contents and datafiles ; create tablespace USERS
datafile '/oracle/oradata/users01.dbf' size 48m AUTOEXTEND ON NEXT 4m
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 4M SEGMENT SPACE MANAGEMENT AUTO ; alter database default tablespace USERS ;
5.6 Create a permanent tablespace for storing segments associated with online transaction processing high insert rates.Due to the potential high volume of concurrent inserts,every effort should be taken to reduce contention for each of the tables that will be stored in this tablespace.Use the following specifications: 5.6.1 Tablespace name of OLTP 5.6.2 File size of 48MB 5.6.3 Initial extent size of 2MB 5.6.4 Next extent size of 2MB
-- drop tablespace OLTP including contents and datafiles ; create tablespace OLTP
datafile '/oracle/oradata/oltp01.dbf' size 48m AUTOEXTEND ON NEXT 2M
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 2M SEGMENT SPACE MANAGEMENT AUTO ;
6. Log File Management
6.1. Due to the expected high volume of transactions,the database should have the following configuration: 6.1.1 A minimum of 5 redo log groups. 6.1.2 Each redo log group should not be a single point of failure 6.1.3 File size of 100MB 6.1.4 Specify the location such that it minimizes contention and reduces the risk of a single point of failure in case of disk drive failure.
--alter database drop logfile group 1; --alter database drop logfile group 2; --alter database drop logfile group 3; --alter database add logfile group 1 ('
/oracle/oradata/redo11.log','/oracle/oradata/redo12.log') size 100m; --alter database add logfile group 2 (
'/oracle/oradata/redo21.log','/oracle/oradata/redo22.log') size 100m; --alter database add logfile group 3 ('
/oracle/oradata/redo31.log','/oracle/oradata/redo32.log') size 100m;
Alter database add logfile member ?/oracle/oradata/redo12.log? to group 1; Alter database add logfile member ?/oracle/oradata/redo22.log? to group 2; Alter database add logfile member ?/oracle/oradata/redo32.log? to group 3; alter database add logfile group 4 (
'/oracle/oradata/redo41.log','/oracle/oradata/redo42.log') size 100m; alter database add logfile group 5 (
'/oracle/oradata/redo51.log','/oracle/oradata/redo52.log') size 100m; 6.2. Triplex the controlfile to minimize recovery in case of disk drive failure.
Alter database backup controlfile to trace;
7. Schema Creation
7.1. As user SYS,run the script /home/oracle/scripts/create_bishhr.sql,Ignore any errors concerning OE.But do not ignore any other errors.
@/home/oracle/scripts/create_bishhr.sql Hr/users/temp/oracle/ ?/rdbms/log/
Conn system/oracle
@?/sqlplus/admin/pupbld.sql
8. Schema Statistics and Parameter File Configuration
8.1. Compute statistics for the various schemas in the database as necessary for use with cost based optimization.
8.2. Investigate the parameter file for reasonable sizes for each parameter listed.Add additional parameters as you deem necessary to support an optimal database environment.In addition,modify or add the following listed parameters:
UTL_FILE_DIR=('/home/oracle','/home/oracle/temp','/home/oracle/scripts')
Note: Appalications that use Oracle 10g features will be running therefore,ensure the database and instance are appropriately configured.
exec dbms_stats.gather_database_stats(degree=>5);
alter system set utl_file_dir='/home/oracle','/home/oracle/temp','/home/oracle/scripts' scope=spfile ;
9. Database Backup and Availability
9.1. Backup the database to prepare for complete recovery under all circumstances. 9.2. OPEN the database . rman target / run {
backup full database format '/oracle/bak/full_%U.bak'; backup archivelog all format '/oracle/bak/arc_%U.bak'; copy current controlfile to '/oracle/bak/control_bak'; }
至此，数据库与网络配置部分完成
Section 2: Grid Control安装配置
1.Grid Control Installation
1.1 Create a database for your repository
1.1.1 Use EMREP for database name and instance name 1.1.2 on your even machine