SESA allows you to install multiple SESA DataStores. Each SESA DataStore is supported by a separate Oracle database. These databases must be created prior to running the SESA installation program.
Create multiple Oracle 9i databases to support multiple SESA DataStores The preparation for installing multiple SESADataStores requires that you create an Oracle 9i database for each SESA DataStore. This means that you must do the following:
■ Create the directory structure for each Oracle database.
■ Create an init<dbname>.ora file for each Oracle database.
■ Add an entry in the oratab, listener.ora, and tnsnames.ora files for each Oracle database.
■ Run a customized create.sql script for each Oracle database. For redo files /u02/oradata/SESA
125 Before you install SESA Preparing third-party software on Solaris platforms
Each database that you create must have a unique ORACLE_SID and directory structure.
Note: The following procedures are only one example of how you could prepare your Solaris 8 computer to use multiple SESA DataStores. The exact procedures depend on your pre-existing hardware and software setup. For example, the following procedures assume that you are creating multiple Oracle databases on a single Solaris computer, but you can create databases on separate computers.
To create the directory structure for each Oracle database 1 Open a Terminal window to the SESA DataStore computer.
2 Change to Oracle user, and then type the following command to create the directories for each of the Oracle databases:
mkdir -p <directory path>
Use the following information as a model:
The directory structure for each database differs only in the database name. Each Oracle database requires six directories and each of these directories use the unique database name in the path. For example, if you were to create the directory structure for databases SESA1, SESA2, and SESA3, you would create 18 directories total, 6 for SESA1, 6 for SESA2, and 6 for SESA3.
To create an init<dbname>.ora file for each Oracle database 1 Open a Terminal window to the SESA DataStore computer.
2 Change to Oracle user, navigate to the location of the initSESA.ora file, and then type the following command:
cp initSESA.ora $ORACLE_HOME/dbs/initSESA1.ora
The default location of the initSESA.ora file is … /<installation staging area>/Solaris.CD1/ORACLE.
3 Navigate to $ORACLE_HOME/dbs.
For admin files /u02/app/oracle/admin/<SESA1, SESA2, … , SESA#>/bdump /u02/app/oracle/admin/<SESA1, SESA2, … , SESA#>/cdump /u02/app/oracle/admin/<SESA1, SESA2, … , SESA#>/udump For data files /u01/oradata/<SESA1, SESA2, … , SESA#>
For redo files /u02/oradata/<SESA1, SESA2, … , SESA#> For arch files /u01/oradata/<SESA1, SESA2, … , SESA#>/arch
4 In a text editor, open the initSESA1.ora file.
5 Change any instance of the default database name (SESA) to SESA1. You may want to use a find and replace tool in your text editor to ensure that all of the required changes are made.
6 Reduce the Sga_max_size (default=500M)and Db_cache_size (default =300M) so that when they are combined and then multiplied by the number of database instances that run at the same time on a single computer, the total is less than half of the physical memory on that computer.
For example, if you use the default values for Sga_max_size and
Db_cache_size, and run three SESA DataStores on a single computer, the following calculation results:
(500M + 300M)*3 = 2400M
In order to comply with the above recommendation, your computer would require 5 GB or more of physical memory. See your Oracle administrator for advice on how much memory to allocate to each database instance.
7 Save and close the initSESA1.ora file.
8 Create an additional copy of initSESA<#>.ora.
SESA<#> should correspond to the ORACLE_SID for the additional database.
9 Type the following command:
cp initSESA1.ora initSESA<#>.ora
10 In a text editor, open the file initSESA<#>.ora, and make the same changes to the file as you did in steps 5-7, except SESA1 should be replaced with SESA<#> to match the ORACLE_SID and the directory structures that you created earlier.
11 Repeat steps 8-10 for each additional database that you create. Remember to increment SESA<#> for each additional database.
To add an entry in the oratab, listener.ora, and tnsnames.ora files for each Oracle database
1 Open a Terminal window to the SESA DataStore computer, and change to Oracle user.
2 In a text editor, open the /var/opt/oracle/oratab file, and then type entries for each database that you create.
Be sure to increment SESA<#> as needed to correspond to the ORACLE_SID of the additional databases that you create. For example, if you want to
127 Before you install SESA Preparing third-party software on Solaris platforms
create three databases on a single Solaris computer, you would add the following lines to the oratab file:
SESA1:/u02/app/oracle/product/9.2.0.1.0:Y SESA2:/u02/app/oracle/product/9.2.0.1.0:Y SESA3:/u02/app/oracle/product/9.2.0.1.0:Y
In this example, SESA<#> is the ORACLE_SID, the path is the Oracle Home directory, and Y ensures that the instance starts when Oracle user issues a dbstart command.
3 Save and close the /var/opt/oracle/oratab file.
4 Navigate to the /u02/app/oracle/product/9.2.0.1.0/network/admin directory.
5 In a text editor, open the listener.ora file, and locate the following section: SID_LIST_LISTENER = (SID_LIST = (SID_DESC = (SID_NAME = PLSExtProc) (ORACLE_HOME = /UO2/APP/ORACLE/PRODUCT/9.2.0.1.0) (PROGRAM = extproc) )
6 Type entries for each database that you create.
Be sure to increment SESA<#> as needed to correspond to the ORACLE_SID of the additional databases that you create. For example, if you want to create two databases on a single Solaris computer, you would add the following lines to the listener.ora file:
(SID_DESC = (GLOBAL_DBNAME = SESA1) (ORACLE_HOME = /u02/app/oracle/product/9.2.0.1.0) (SID_NAME = SESA1) ) (SID_DESC = (GLOBAL_DBNAME = SESA2) (ORACLE_HOME=/u02/app/oracle/product/9.2.0.1.0) (SID_NAME=SESA2) )
7 Save and close the listener.ora file.
8 In a text editor, open the tnsnames.ora file, and type entries for each database that you create.
Be sure to increment SESA<#> as needed to correspond to the ORACLE_SID of the additional databases that you create. For example, if you want to create two databases on a single Solaris computer, you would add the following lines to the tnsnames.ora file:
SESA1 =
(DESCRIPTION = (ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = LOCALHOST)(PORT = 1521)) ) (CONNECT_DATA = (SID = SESA1) (SERVER = DEDICATED)) ) ) SESA2 = (DESCRIPTION = (ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = LOCALHOST)(PORT = 1521)) ) (CONNECT_DATA = (SID = SESA2) (SERVER = DEDICATED)) ) )
9 Save and close the tnsnames.ora file.
10 To register the changes that were made to the listener.ora file, restart the listener by typing the following command:
lsnrctl start
11 If the listener fails to start because it is already running, type the following command:
lsnrctl reload
To run a customized create.sql script for each Oracle database 1 Open a Terminal window to the SESA DataStore computer.
2 Change to Oracle user, navigate to the location of the create.sql file, and then type the following command:
cp create.sql $ORACLE_HOME/dbs
The default location of the create.sql file is … /<installation staging area>/ Solaris.CD1/ORACLE.
3 Navigate to $ORACLE_HOME/dbs.
4 In a text editor, open the create.sql file, and then change the instances of the default database name (SESA) to SESA<#>, where <#> is the number of the database that you are now creating.
You may want to use a find and replace tool in your text editor to ensure that all of the required changes are made.
129 Before you install SESA Preparing third-party software on Solaris platforms
5 Ensure that the value that is specified for ORACLE_HOME is correct and if it is not, change it.
The default is /u02/app/oracle/product/9.2.0.1.0 and the value should match the ORACLE_HOME that was specified in the .profile file that corresponds to Oracle user.
6 Save and close the create.sql file.
7 In the Terminal window to the SESA DataStore computer, as Oracle user, type the following command (make sure to include a space between the period and the oraenv):
. oraenv
8 Type the name of the database that you are creating.
This value should match the database name in the customized create.sql file.
9 Type the following commands:
sqlplus /nolog connect / as sysdba @create.sql
10 After the database is successfully created, type the following command:
exit
11 To create the remaining Oracle databases, repeat steps 3 through 10 for each database that you create.
Ensure that you change all of the instances of the database name in the ORACLE_SID file, file paths, Oracle environment, create.sql script, and so on, to the new database name.