| Oracle® Communications ASAP Installation Guide Release 7.2 E18878-04 |
|
 Previous |
 Next |
This chapter describes the tasks that you perform before installing Oracle Communications ASAP.
The ASAP Installer checks for a database to connect to during the installation process. Ensure that a database is up and running before you start installing ASAP. If you already have a database up and running, create one or more tablespaces for the ASAP schemas data and index segments.
For information about installing Oracle database, see the Oracle Database installation documentation.
Oracle recommends that the installation and configuration of Oracle Database be performed by an experienced Oracle Database Administrator (DBA). In addition, some UNIX administrative skills are required to uncompress software, create users and groups, and similar tasks.
Oracle requires that you use the 64-bit Oracle database software.
To download and install the 64-bit Oracle database software:
Sign on to the My Oracle Support web site:
https://support.oracle.com/CSP/ui/flash.html
Click the Patches and Updates link.
The Patch Search screen appears.
In the Patch Name or Number field, enter 13390677 and click Search.
The patchset list appears.
Select Patch 13390677: 11.2.0.4.0 PATCH SET FOR ORACLE DATABASE SERVER for the 64-bit version of your platform.
Click Download.
The File Download screen appears.
Click p10404530_112030_platform_1of7.zip and p10404530_112030_platform_2of7.zip for the database (where platform is the 64-bit version of the operating system).
A download progress screen appears.
Install the database according to an Oracle database installation guide applicable to your installation requirements.
Oracle requires that you use the 32-bit Oracle Client software, even if ASAP is installed on a 64-bit platform.
To download and install the 32-bit Oracle Client software:
Sign on to the My Oracle Support web site:
https://support.oracle.com/CSP/ui/flash.html
Click the Patches and Updates link.
The Patch Search screen appears.
In the Patch Name or Number field, enter 13390677 and click Search.
The patchset list appears.
Select Patch 13390677: 11.2.0.4.0 PATCH SET FOR ORACLE DATABASE SERVER for the 32-bit version of your platform (even if your platform is 64-bit).
Click Download.
The File Download screen appears.
Click one of the following files for the Oracle database client:
For Linux platform (64-bit): p13390677_112040_platform_4of7.zip
where platform is the name of the platform that you are using.
For other supported platforms (32-bit) (for example, AIX or Solaris): p13390677_112040_platform_1of2.zip
where platform is the name of the platform that you are using.
A download progress screen appears.
Install the client according to the installation instructions in the downloaded ZIP file.
|
Note: Oracle recommends using the Administrator Installation Type for your client. |
|
Note: Oracle Database defines NLS (National Language Support) values to set up language-specific databases. Ensure that the Oracle Database server and the Oracle Database client use the same NLS_LANG settings. This improves performance because there is no translation of character sets. |
This section describes the overall workflow for creating and configuring a single database instance or a RAC database instance for use with ASAP.
To install, create, and configure Oracle RAC or Single database instance for ASAP:
After installing the Oracle database and client, apply any appropriate software patches.
|
Note: See "Patch Requirements" for the required software patches.Some of the scripts that run with Oracle Database patch installation can take several hours to complete. Plan accordingly, and ensure that all patch scripts run correctly to completion and return to the UNIX prompt. |
Create a database instance.
|
Note: Review and apply recommended database instance initialization parameters listed in "Configuring the Oracle Database Initialization Parameters". Some default database initialization parameters must be configured for ASAP to run.For a RAC database, follow the additional database connection recommendations described in "Configuring Oracle Real Application Clusters Database Connectivity". |
Ensure that you have determined the database tablespace and Oracle Database Server configuration that you require. See "Configuring the Oracle Database Connection Mode".
Start the Oracle Database instance.
Create one or more ASAP tablespaces and redo log files. (Oracle recommends that your Oracle DBA create the ASAP tablespaces.)
For more information, see "Recommended Tablespace and Redo Log Sizes for ASAP" and "Creating Oracle Database Tablespaces, Tablespace User, and Granting Permissions".
Switch to an Oracle Database admin account (for example, SYS) and execute the ora_system_procs.sh script to populate the common PL/SQL functions used by multiple instances of ASAP.
|
Note: The ASAP_src/asap_utils/ora_system_procs.sh script should not be run more than once against a single Oracle Database server. |
Verify the Oracle Database installation and configuration.
Configure your Oracle database to accept connections from ASAP using the dedicated connection mode. For each Oracle database connection, a dedicated server process is created which does work on behalf of the ASAP user session. All interactions with the Oracle Shared Global Area (SGA) and data files are done through this dedicated server processes. A server process is started for every user session connecting to the database.
Table 5-1 provides the recommended Oracle database maximum memory target for the automatic memory manager (AMM). You can set this value when you create your database using the dbca utility.
In Oracle Database instance installations, you can use either init$ORACLE_SID.ora or spfile$ORACLE_SID.ora.to specify initialization parameters.
The most secure way of modifying Oracle Database parameters, is to specify them on the SQL*PLUS command line, storing them in the spfile. This way, each modification is parsed as you enter it and the parameters are correctly entered.
To show the value of a parameter in the spfile, and then change it, use the following procedure:
Start sqlplus.
Log in using /as sysdba.
Enter:
SHOW PARAMETER PROCESSES ALTER SYSTEM SET PROCESSES='200' SCOPE=spfile;
To show all parameters that start with certain characters, use a common abbreviation. For example, the following command shows all parameters that start with 'DB'.
SQL> SHOW PARAMETER DB
|
Note: Some parameters will not take effect until the database instance is stopped, and then restarted. The command startup force can accomplish this. |
To manually edit parameters in the init$ORACLE_SID.ora file, convert it to an spfile.
|
Note: Do not manually edit the spfile$ORACLE_SID.ora. Editing an spfile corrupts it. This can prevent you from starting an instance, or cause an active instance to fail. |
To convert the INIT.ora file to an spfile:
Start sqlplus.
Log in using as sysdba for the user-name.
sqlplus sys/password as sysdba
Where password is the password for your sys database user account.
Enter:
create spfile from pfile; File created. CREATE SPFILE [='spfile_name'] FROM PFILE [='pfile_name']; COMMIT;
To return parameters to the INIT.ORA type parameter file from an spfile:
Start sqlplus.
Log in using as sysdba for the user-name.
sqlplus sys/password as sysdba
Enter:
create pfile from spfile; File created. CREATE PFILE [='pfile_name'] FROM SPFILE [='spfile_name']; COMMIT;
This section provides recommended Oracle Database initialization parameter values for use with ASAP in a production system. The suggested values are guidelines only. The optimum values for your system will depend on the particulars of your installation, and your processing requirements.
Table 5-2 lists suggested Oracle Database initialization parameter values.
|
Note: You must configure the following parameters. However, the particular values you implement will depend on your chosen configuration. |
Table 5-2 Database Initialization (init$ORACLE_SID.ora) Parameters
| Parameter and Value | Description |
|---|---|
|
PROCESSES =500 (small) 1000 (medium), 3000 (large with under 14 NEP server), and 5000 (large with over 14 NEP servers) |
PROCESSES specifies the maximum number of operating system user processes that can simultaneously connect to Oracle Database. Its value should allow for all background processes such as locks, job queue processes, and parallel execution processes. The default values of the SESSIONS and TRANSACTIONS parameters are derived from this parameter. Therefore, if you change the value of PROCESSES, you should evaluate whether to adjust the values of those derived parameters. For more information on Configuration Variables, see the ASAP System Administrator's Guide. |
|
SESSIONS = 1600 or up to 600 per online instance (production) 100 - 120 per online instance (development) |
This parameter sets the maximum number of connections to the Oracle Database. |
|
COMMIT_WAIT = 'WAIT' |
This parameter controls when the redo for a commit is flushed to the redo logs. |
|
FILESYSTEMIO_OPTION = 'SETALL' |
Specifies I/O operations for file system files. |
In "ASAP Oracle Database Tablespace Sizing Requirements" you determine how you will map ASAP server schemas to tablespaces, what the tablespaces will be named, and what their size requirements are.
Typically, all environments for testing can share the tablespaces. However, in Oracle Database you can distribute the ASAP components by specifying different default tablespaces for each environment before installing the ASAP database definitions.
Some ASAP implementations may require a tablespace layout that differs from the layout recommended here. The ASAP administrator, in conjunction with the Oracle DBA, can create any tablespace layout that is required.
Oracle recommends that tablespaces be created with the following default properties:
Size – as determined using the sizing information provided in "Recommended Tablespace and Redo Log Sizes for ASAP".
Storage Clause:
Initial 256 GB
Next 256 KB
Percent increase 0
Maxextents Unlimited
|
Note: In development systems, a database can remains idle for longer than the default database connection time-out setting. This can cause the database to terminate the connections to the ASAP servers generating the ORA-02396 event. This scenario can be avoided by setting the database connection time-out parameter to a higher value.This scenario is unlikely to occur in a production system. |
To create the tablespaces, tablespace users, and grant permissions in the Oracle Database:
Log in to your Oracle database as a sysdba.
Start the Oracle database.
Create the tablespaces.
For example:
create tablespace "ASAPDATA_TS" logging datafile '/u01/app/oracle/oradata/ASAP72/ASAPDATA_TS1.dbf' size 31999M reuse autoextend on next 5120K maxsize unlimited default storage (initial 256K next 256K minextents 1 maxextents 2147483645 pctincrease 0); create tablespace "ASAPINDEX_TS" logging datafile '/u01/app/oracle/oradata/ASAP72/ASAPINDEX_TS1.dbf' size 31999M reuse autoextend on next 5120K maxsize unlimited default storage (initial 256K next 256K minextents 1 maxextents 2147483645 pctincrease 0); CREATE USER "ASAP_SYS" PROFILE "DEFAULT" IDENTIFIED BY "ASAP_SYS" DEFAULT TABLESPACE "ASAPDATA_TS" TEMPORARY TABLESPACE "TEMP" ACCOUNT UNLOCK; GRANT CREATE ANY CONTEXT TO "ASAP_SYS" WITH ADMIN OPTION; GRANT CREATE ANY TABLE TO "ASAP_SYS" WITH ADMIN OPTION; GRANT CREATE ANY VIEW TO "ASAP_SYS" WITH ADMIN OPTION; GRANT CREATE SNAPSHOT TO "ASAP_SYS" WITH ADMIN OPTION; GRANT CREATE SYNONYM TO "ASAP_SYS" WITH ADMIN OPTION; GRANT CREATE TABLE TO "ASAP_SYS" WITH ADMIN OPTION; GRANT CREATE USER TO "ASAP_SYS" WITH ADMIN OPTION; GRANT CREATE VIEW TO "ASAP_SYS" WITH ADMIN OPTION; GRANT GRANT ANY PRIVILEGE TO "ASAP_SYS" WITH ADMIN OPTION; GRANT QUERY REWRITE TO "ASAP_SYS" WITH ADMIN OPTION; GRANT UNLIMITED TABLESPACE TO "ASAP_SYS" WITH ADMIN OPTION; GRANT SELECT ON "SYS"."V_$PARAMETER" TO "ASAP_SYS" WITH GRANT OPTION; GRANT "CONNECT" TO "ASAP_SYS" WITH ADMIN OPTION; GRANT "DBA" TO "ASAP_SYS" WITH ADMIN OPTION; GRANT "EXP_FULL_DATABASE" TO "ASAP_SYS" WITH ADMIN OPTION; GRANT "IMP_FULL_DATABASE" TO "ASAP_SYS" WITH ADMIN OPTION; GRANT "RESOURCE" TO "ASAP_SYS" WITH ADMIN OPTION; GRANT EXECUTE ON SYS.DBMS_LOCK TO "ASAP_SYS" WITH GRANT OPTION; GRANT SELECT ON DBA_TABLESPACES TO "ASAP_SYS" WITH GRANT OPTION;
Each ASAP server schema requires an Oracle user name and password. You can pre-configure these accounts and supply the needed information during the installation; however, this step is optional. The ASAP installation will automatically create the needed users unless you indicate they have already been created.
To create the Oracle Database users using SQL Plus commands:
Start SQL Plus and log in as the Oracle admin user.
sqlplus -s Oracle_admin/Oracle_admin_pw@Oracle_SID
Where Oracle_admin and Oracle_admin_pw is an Oracle Database administration account and password and Oracle_SID is the Oracle Database SID.
Create the users. In the example below, you would replace the ASAP_envID tags with the actual ASAP environment ID you want to use when you install ASAP.
create user admASAP_envID identified by admASAP_envID default tablespace Tablespace_name temporary tablespace $TEMP_TS; grant connect, resource to admASAP_envID ; create user sarmASAP_envID identified by sarmASAP_envID default tablespace Tablespace_name temporary tablespace $TEMP_TS; grant connect, resource to sarmASAP_envID ; create user nepASAP_envID identified by nepASAP_envID default tablespace Tablespace_name temporary tablespace $TEMP_TS ; grant connect, resource to nepASAP_envID; create user srpASAP_envID identified by srpASAP_envID default tablespace Tablespace_name temporary tablespace $TEMP_TS; grant connect, resource to srpASAP_envID; create user ctrlASAP_envID identified by ctrlASAP_envID default tablespace Tablespace_name temporary tablespace $TEMP_TS; grant connect, resource to ctrlASAP_envID; commit;
Record the actual names used in the table "Installing ASAP Using the GUI Installer".
To create the Oracle Database users using the ASAP sample create users script:
Download the ASAP installation software as described in "Downloading the ASAP Installation Files".
Using a text editor, open ASAP_src/asap_utils/sample-create-user.ksh.
Edit the following variables:
ENV_ID=env_id: Where env_id is the environment ID that you will use for your ASAP installation.
USER=db_user: Where db_user is database user with sufficient privileges to create new tablespace users.
PASSWORD=db_pw: Where db_pw is database password for the database user with sufficient privileges to create new tablespace users.
ORACLE_SID=sid: Where sid is the database SID value.
TEMP_TS=temp_ts: Where temp_ts is the temporary tablespace associated to each user.
Run the ASAP_src/asap_utils/sample-create-user.ksh script.
If you use different user names, ensure that you supply the same names during the ASAP server installation.
You may need to apply a patch to the Oracle Database Server software after installation. For details, see "Patch Requirements".
ASAP uses the availability features of Oracle Real Application Clusters (RAC) system. ASAP supports an active/passive failover RAC database configuration. If you have installed ASAP in a RAC system, ASAP automatically connects to the active secondary database node when the primary database node fails over to the secondary. ASAP Control Server remains running during the RAC node switchover. If a transaction is in progress when the RAC node fails over and, as a result, if any ASAP server shuts down, ASAP Control Server automatically restarts the failed ASAP processes.
Follow the recommendations in the Oracle RAC documentation and use cluster node Virtual IP Addresses (VIP) when configuring Oracle LOCAL listeners (LOCAL_LISTENER). For more information on listener configuration and RAC installation, refer to the Oracle Real Application Clusters Installation Guide and the Oracle Database Net Services Administrator's Guide.
To configure the TNSNAMES.ora file for RAC support:
Using a text editor, open TNSNAMES.ora file in the Oracle_Home/network/admin/ directory, where Oracle_Home is the directory in which the Oracle database is installed.
Configure the TNSNAMES.ora file entries listed in Table 5-3.
Table 5-3 TNSNAMES.ora Entries
| Entry | Description |
|---|---|
|
LOAD_BALANCE |
This parameter specifies whether load balancing is enabled between RAC databases. This parameter is embedded in the ADDRESS_LIST parameter in the tnsnames.ora file. Set this attribute to NO. ASAP does not support active/active RAC databases configuration. |
|
FAILOVER |
This parameter specifies whether connect-time failover is enabled between primary and secondary RAC databases. This parameter is embedded in the ADDRESS_LIST parameter in the tnsnames.ora file Set this attribute to TRUE. ASAP supports the active/passive RAC database configurations. |
|
ADDRESS |
This parameter contains the address information for a RAC database. Include two instances of this attribute for the primary and secondary RAC databases. This parameter is embedded in the ADDRESS_LIST parameter in the tnsnames.ora file The ADDRESS parameters includes the following parameters:
|
|
SERVER |
This parameter directs the listener to connect the client to a specific service handler. Set this parameter to DEDICATED. |
|
SERVICE_NAME |
This parameter identifies the Oracle Database database service to access. Set the value to a value specified by the SERVICE_NAMES parameter in the initialization parameter file. |
|
FAILOVER_MODE |
This parameter contains the connection information required for a RAC active/passive failover database configuration and transparent application failover (TAF). It instructs Oracle Net to fail over to a different listener if the first listener fails during run time. Do not confused this parameter with the connect-time failover FAILOVER parameter. This parameter is embedded in the CONNECT_DATA parameter in the tnsnames.ora file. The FAILOVER_MODE parameter includes the following parameters:
|
For example:
DB_CONNECT=
(DESCRIPTION =
(ADDRESS_LIST =
(LOAD_BALANCE=NO)
(FAILOVER=TRUE)
(ADDRESS =
(PROTOCOL = TCP)
(HOST = test.system.com)
(PORT = 1521)
)
(ADDRESS =
(PROTOCOL = TCP)
(HOST = test.system.com)
(PORT = 1521)
)
)
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = TEST)
(FAILOVER_MODE=
(TYPE=select)
(METHOD=basic)
(RETRIES=30)
(DELAY=15)
)
)
)
Install ASAP.
Perform the post installation tasks described in "Configuring ASAP to Support TAF for RAC".
|
 Copyright © 2005, 2014, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|