Oracle requires that you use the 64-bit Oracle database software. Download and install Oracle Database for this version of ASAP. See ASAP Compatibility Matrix for the appropriate version of Oracle Database to install.

For information on installing Oracle Database, see the Oracle Database installation documentation.

Oracle requires that you use the 32-bit Oracle Client software, even if ASAP is installed on a 64-bit platform. See ASAP Compatibility Matrix for the appropriate version of Oracle Client software to install.

This section describes the overall workflow for creating and configuring a single database instance or an Oracle Real Application Clusters (RAC) database instance for use with ASAP.

To install, create, and configure Oracle RAC or Single database instance for ASAP:

1. After installing the Oracle database and client, apply any appropriate software patches.

   Note:

   See ASAP Compatibility Matrix 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.

2. 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 an Oracle RAC database, follow the additional database connection recommendations described in "Configuring Oracle RAC Database Connectivity."

3. Ensure that you have determined the database tablespace and Oracle Database Server configuration that you require. See "Configuring the Oracle Database Connection Mode."

4. Start the Oracle Database instance.

5. 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."

6. Switch to an Oracle Database admin account (for example, SYS) and run 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.

7. 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:

1. Start sqlplus.

2. Log in using /as sysdba.

3. 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

To manually edit parameters in the init$ORACLE_SID.ora file, convert it to an spfile.

To convert the INIT.ora file to an spfile:

1. Start sqlplus.

2. 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.

3. 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:

1. Start sqlplus.

2. Log in using as sysdba for the user-name.

   sqlplus sys/password as sysdba
   

3. Enter:

   create pfile from spfile;
   
   File created.
   
   CREATE PFILE [='pfile_name'] FROM SPFILE [='spfile_name'];
   COMMIT;
   

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

To create the tablespaces, tablespace users, and grant permissions in the Oracle Database:

1. Log in to your Oracle database as a sysdba.

2. Start the Oracle database.

3. 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:

1. 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.

2. 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, and replace the *_user_password entities with the actual passwords for the users.

   create user admASAP_envID identified by adm_user_password default tablespace Tablespace_name temporary tablespace $TEMP_TS;
   grant connect, resource, unlimited tablespace to admASAP_envID ;
   create user sarmASAP_envID identified by sarm_user_password default tablespace Tablespace_name temporary tablespace $TEMP_TS;
   grant connect, resource, unlimited tablespace to sarmASAP_envID ;
   create user nepASAP_envID identified by nep_user_password default tablespace Tablespace_name temporary tablespace $TEMP_TS ;
   grant connect, resource, unlimited tablespace to nepASAP_envID;
   create user srpASAP_envID identified by srp_user_password default tablespace Tablespace_name temporary tablespace $TEMP_TS;
   grant connect, resource, unlimited tablespace to srpASAP_envID;
   create user ctrlASAP_envID identified by ctrl_user_password default tablespace Tablespace_name temporary tablespace $TEMP_TS;
   grant connect, resource, unlimited tablespace to ctrlASAP_envID;
   commit;
   

3. 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:

1. Download the ASAP installation software as described in "Downloading the ASAP Installation Files."

2. Using a text editor, open ASAP_src/asap_utils/sample-create-user.ksh.

3. 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.

4. 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.

ASAP uses the availability features of the Oracle RAC system. ASAP supports an active/passive failover Oracle RAC database configuration. If you have installed ASAP in an Oracle 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 Oracle RAC node switchover. If a transaction is in progress when the Oracle 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 Oracle 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 Oracle RAC support:

1. Using a text editor, open TNSNAMES.ora file in the Oracle_home/network/admin/ directory.

2. 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 Oracle 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 Oracle 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 Oracle RAC database configurations.
   ADDRESS	This parameter contains the address information for an Oracle RAC database. Include two instances of this attribute for the primary and secondary Oracle RAC databases. This parameter is embedded in the ADDRESS_LIST parameter in the tnsnames.ora file The ADDRESS parameters includes the following parameters: PROTOCOL: Specifies the protocol used to connect to the Oracle RAC database. For example, TCP. HOST: Specifies the host name or IP address for the RAC database. PORT: Specifies the port number for the Oracle RAC database.
   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 an Oracle 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: TYPE: Set TYPE to session. TYPE=session establishes a new connection to the Oracle active instance, and any work in progress is lost. ASAP will replay all such failed transactions related to the Control Server. METHOD: Specify the method to be used for establishing the connection. METHOD=preconnect directs TAF to create two connections at transaction startup time: one to the primary database and a backup connection to the backup database. METHOD=basic directs TAF to create a connection to the primary database at transaction startup time. Connection to the backup database is established only after the connection to the primary database fails. RETRIES: Specify the number of times you want ASAP to retry the connection when the connection to the database fails. For example, RETRIES=11. DELAY: Specify the interval in seconds between connection retries. For example, DELAY= 6.

   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)
            )
         )
      )
   

3. Install ASAP.

4. Perform the post-installation tasks described in "Configuring ASAP to Support TAF for Oracle RAC."