Skip Headers

Agile Product Lifecycle Management Database Install Guide Release 9.3.3 E39281-01 |
| Contents

Previous | Next |

# 5 Installing the Agile Database on UNIX

## 5.1 Preparing the Host Computer

This section describes how to prepare the installation environment on UNIX.

Preparation of the installation environment involves copying the Agile database utilities.:

To copy the Agile database utilities:

1. Log in as the user that was used to install the Oracle database software and create a temporary directory named "agile9330db:"

   $ mkdir /home/oracle/agile9330db [Enter]

2. 2. Download the appropriate Agile PLM media pack for your operating system to the agile9330db directory. For more information on obtaining the media pack, see Obtaining Software from Oracle Support on page 2 (for a Patchset/Minipack), or Obtaining Software from Oracle Software Delivery Cloud on page 1 (for a major release).

3. 3. Change to the agile9330db directory, and extract the files from the agile9330db_oracle.tar.gz file:

   $ cd /home/oracle/agile9330db [Enter]

   $ gunzip -c agile9330db_oracle.tar.gz|tar xvf - [Enter]

   The agile9330db_oracle.tar file contains the following files:

   - agile9database.sh - shell script for creating the database instance and generating the database maintenance scripts

   - agile9schema.dmp - agile schema dump file

   - dbora - setup for the database automatic shutdown and startup

   - pdqplm_plsql.jar - Java stored procedures for the Enterprise Data Quality Product integration

   - profile.txt - oracle user .profile template

   - Readme.txt - readme file

   - system.txt - Solaris kernel parameters

## 5.2 Creating the Agile Database on UNIX

This section describes how to set up Oracle environment variables and create the default database instance and schema used by Agile using the Agile database creation utility.

To set up Oracle environment variables:

1. Log in as the user that was used to install the Oracle database software..

2. Create the environment parameter file .profile to include:

       PATH=$PATH:/usr/local/bin:/usr/ccs/bin:/usr/openwin/bin:/usr/bin/X11
       export PATH
       ORACLE_HOME=<Location where you installed Oracle Database Server>
       export ORACLE_HOME

   For example:

       (Oracle11g)ORACLE_HOME=/u01/app/oracle/product/11.1.0/db_1;export ORACLE_HOME
       ORACLE_BASE=<Oracle base folder location:;export ORACLE_BASE

   For example:

       ORACLE_BASE=/u01/app/oracle;export ORACLE_BASE
       PATH=$PATH:$ORACLE_HOME/bin;export PATH
       ORACLE_SID=agile9;export ORACLE_SID
       NLS_LANG=AMERICAN_AMERICA.AL32UTF8;export NLS_LANG

3. 3. The environment variables settings above are stored in the file profile.txt included with the Agile database utilities. If this is the first time you are configuring the host computer as a database server, copy the profile.txt file to .profile:

   $ cat agile9330db/profile.txt > .profile [Enter]

4. 4. Set environment variables:

   $ . ./.profile [Enter]

To start the installation:

1. Log in to the computer as the user you created while preparing the installation environment. For example, Oracle.

   a. If necessary, edit the .profile file to change Oracle SID. By default, Agile uses agile9 as the Oracle SID:

   $ vi .profile [Enter]

   b. Modify the value where ORACLE_SID=agile9 by replacing agile9 with the SID you want to use.

   Important: Check the /var/opt/oracle/oratab file and make sure that the specified Oracle SID has not been used. Specifying an existing Oracle SID can corrupt that database instance.

   Note: The recommended SID length is 4-8 alphanumeric characters. (The default SID 'agile9' is six characters.)

   c. Source .profile to make the SID changes take effect:

   . ./.profile [Enter]

2. In a second terminal session, log in to the computer as the root user.

3. Create a directory named "oradata."

   Note: The agile9database.sh file uses a placeholder mount point /mpt. You must change /mpt to match your mount points.

   For example, if you have mount points at /u01 and /u02, you can create an oradata folder on each mount point.

   # mkdir -p /u01/oradata

   # chown oracle:dba /u01/oradata

4. In the session where you are logged in as the Oracle user, create a $ORACLE_BASE/admin directory:

   $ mkdir -p /u01/app/oracle/admin [Enter]

   (Assuming ORACLE_BASE is set to /u01/app/oracle.)

   chown -R oracle:dba /u01/app/oracle

   You must now run the agile9database.sh script.

5. Change to the /home/oracle/agile9330db directory.

6. Modify the agile9database.sh script to match the mount points on your computer.

   Note: Make sure ORACLE_SID matches the one you set for .profile, which should have taken effect after you ran . ./.profile.

   Note: The agile9database.sh file uses a placeholder mount point /mpt. You must change /mpt to match your mount points.

   The values in the script that can be modified appear in bold. You should limit your editing only to these bold values.

   The following code lists variables in bold that you may want to revise besides placeholder mount point /mpt:

   #!/bin/sh

   .

   .

   .

   # AGILE9DB_BASE is the base directory for the OFA directories and maintenance scripts

   # (create the directory before running this script)

   # (default is $ORACLE_BASE/admin/$ORACLE_SID)

   #

   AGILE9DB_BASE=$ORACLE_BASE/admin/$ORACLE_SID

   # Parameters determine location of datafiles, # controlfiles and logfiles

   #

   DATABASE_SYSTEM=/mpt/oradata/${ORACLE_SID} # SYSTEM tablespace mount point

   DATABASE_SYSAUX=/mpt/oradata/${ORACLE_SID} # SYSAUX tablespace mount point

   DATABASE_TOOLS=/mpt/oradata/${ORACLE_SID} # TOOLS tablespace mount point

   DATABASE_UNDO=/mpt/oradata/${ORACLE_SID} # RBS tablespace mount point

   DATABASE_TEMP=/mpt/oradata/${ORACLE_SID} # TEMP tablespace mount point

   DATABASE_USERS=/mpt/oradata/${ORACLE_SID} # USERS tablespace mount point

   DATABASE_INDX=/mpt/oradata/${ORACLE_SID} # INDX tablespace mount point

   DATABASE_AGILE_DATA1=/mpt/oradata/${ORACLE_SID} # AGILE_DATA1 tablespace mount point

   DATABASE_AGILE_INDX1=/mpt/oradata/${ORACLE_SID} # AGILE_INDX1 tablespace mount point

   DATABASE_AGILE_DATA2=/mpt/oradata/${ORACLE_SID} # AGILE_DATA2 tablespace mount point

   DATABASE_AGILE_INDX2=/mpt/oradata/${ORACLE_SID} # AGILE_INDX2 tablespace mount point

   DATABASE_AGILE_DATA3=/mpt/oradata/${ORACLE_SID} # AGILE_DATA3 tablespace mount point

   DATABASE_AGILE_INDX3=/mpt/oradata/${ORACLE_SID} # AGILE_INDX3 tablespace mount point

   DATABASE_AGILE_DATA4=/mpt/oradata/${ORACLE_SID} # AGILE_DATA4 tablespace mount point

   DATABASE_AGILE_INDX4=/mpt/oradata/${ORACLE_SID} # AGILE_INDX4 tablespace mount point

   DATABASE_AGILE_DATA5=/mpt/oradata/${ORACLE_SID} # AGILE_DATA5 tablespace mount point

   DATABASE_AGILE_INDX5=/mpt/oradata/${ORACLE_SID} # AGILE_INDX5 tablespace mount point

   DATABASE_LOGFILES1=/mpt/oradata/${ORACLE_SID} # REDOLOG file 1 mount point

   DATABASE_LOGFILES2=/mpt/oradata/${ORACLE_SID} # REDOLOG file 2 mount point

   DATABASE_LOGFILES3=/mpt/oradata/${ORACLE_SID} # REDOLOG file 3 mount point

   DATABASE_LOGFILES4=/mpt/oradata/${ORACLE_SID} # REDOLOG file 4 mount point

   DATABASE_CONTROL1=/mpt/oradata/${ORACLE_SID} # CONTROL file 1 mount point

   DATABASE_CONTROL2=/mpt/oradata/${ORACLE_SID} # CONTROL file 2 mount point

   DATABASE_CONTROL3=/mpt/oradata/${ORACLE_SID} # CONTROL file 3 mount point

   DATABASE_ARCHIVE=/mpt/oradata/${ORACLE_SID}/arch # ARCHIVELOGS

   #

   # Parameters determining: Character Set

   #

   CHARACTER_SET=AL32UTF8

   NATIONAL_CHARACTER_SET=AL16UTF16

   NLS_LANG=American_America.AL32UTF8

   #

7. 7. Run the agile9database.sh script from the current directory:

   $ ./agile9database.sh [Enter]

8. You are prompted to choose the Install Mode. Enter I to create the database instance, S to only generate maintenance scripts, or q to quit the installation. [Enter]

9. Enter the Agile PLM Instance name (ORACLE_SID). The default is agile9. If you want to change the SID, you must use an ID that is 4 to 8 characters in length to uniquely identify the Oracle SID. [Enter]

10. Enter the Agile PLM Schema Name. The default is agile.[Enter]

11. The next four prompts allow you to add passwords for the Agile PLM, SYS, SYSTEM, and CTXSYS schemas. Each password must be at least 6 characters in length. [Enter]

12. You are prompted about the database size that you want to install.

    You should use the small database size unless you have consulted with an Agile Solutions Consultant or database administrator to ensure that the computer meets the minimum requirements for the specified database size.

13. Choose the NLS_LENGTH_SEMANTICS parameter to determine datatype storage allocation by the database server. The default value is CHAR. [Enter]

14. Verify the values you have entered. Enter I to install.

    Note: If you are unable to create files, make sure that all Oracle environment variables are set correctly and that the 'oracle' user has full (read, write, and execute) privileges on all directories referenced by agile9database.sh.

    The script will run for a while.

    Note: Oracle recommends that you change all Oracle database user passwords after you have created the Agile database. It is recommended to change these passwords periodically for security purposes