Go to primary content
Oracle Agile Engineering Data Management Server Installation Guide on Windows and UNIX
Release e6.2.1.0
E69109-07
  Go To Table Of Contents
Contents
Previous
Previous 		 Next
Next		  

6 Oracle Database 12c


Note:

This chapter describes prerequisites for installing the Oracle Database client and server on all supported operating systems.

6.1 Oracle Database Prerequisites 12c

6.1.1 Windows

Create the directories/drives for the distribution of the data files depending on the number of disks prepared for the Oracle installation.

For instance, if you have prepared 3 disks -

  • E:\

  • F:\

  • H:\

The drive letters E:\, F:\, and H:\ are just examples. Subdirectories will be created later in these directories by either:

  • Manual installation

    • Installing Oracle Database Server

    • Installing Oracle Database Client

  • Automatic installation

    • Installation with the Agile e6 Installer

6.1.2 UNIX

6.1.2.1 Setting Up an Oracle Operating System User

Several operating system groups and users might have to be installed, depending on:

  • If Oracle software is installed on this system the first time

  • Installed products

For complete information on how to set up an Oracle Operating System User, refer to the Oracle Database Software documentation.

To create an Oracle account:

  1. Create the dba group for the machine on which Oracle is being installed:

    groupadd -g 502 dba


    Note:

    On AIX you have to use the following command instead:

    mkgroup id=502 dba

  2. Create an Oracle user "oracle" with the following parameter and execute the following command.

    • Home directory "/opt/oracle"


    Note:

    This is also value for ORACLE_BASE. The directory must be created first.

    • Login shell "/bin/csh"

    • Member of the group "dba"

    useradd -u 502 -g dba -d /opt/oracle -s /bin/csh oracle

  3. Log into Oracle and create the subdirectories:

    • /opt/oracle/bin

    • /opt/oracle/product

    • /opt/oracle/product/12.0.1


    Note:

    If ORACLE_BASE is not set to /opt/oracle, the above mentioned subdirectories have to be created in the designated directory.

  4. Create the directory, links, and mount points for distribution of the data files, depending on the number of disks prepared for the Oracle installation.

    For instance, if you have prepared 3 disks:

    • …/data1

    • …/data2

    • …/data3

    The names data1, data2, and data3 are just examples.

    Subdirectories will be created later in these directories by the database:

    • Manual installation

      • § Installing Oracle Database Server

      • § Installing Oracle Database Client

    • Automatic installation

      • § Installation with the Agile e6 Installer


      Note:

      For recommended disk layout, please check the Hardware Sizing Guide for Agile e6.2.1.0

6.1.2.2 Setting Up the Shell Environment Variables for Oracle 12c

To set up the shell environment variables, do the following:

  1. Download and uncompress the Oracle Agile Engineering Data Management Application (Release e6.2.1.0) from the Oracle Software Delivery Cloud website.

    Under Oracle Agile Applications > Oracle Agile Engineering Data Management (Release e6.2.1.0) Media Pack.

  2. Copy the script csh_ORA12.1 from the folder addon/db/unix/scripts to /opt/oracle/bin

    If ORACLE_BASE is not set to /opt/oracle, open the script with an editor and change the value for ORACLE_BASE. Then source the script to set the environmental variables.

    chmod 754 csh_ORA12.1

    source $HOME/csh_ORA12.1

  3. Set the file creation permissions with the "umask" command:

    umask 022

  4. Verify the environment.

  5. Log off and log in as the Oracle user to ensure all environment settings are active.

  6. Type env | sort in the UNIX prompt to view all environment variables.

Software Item Requirements
DISPLAY Set it to the machine name and monitor the station from which you are connecting to the server machine (setenv DISPLAY hostname: 0.0).
LD_LIBRARY_PATH

SHLIB_PATH (HP-UX)

LIBPATH (AIX)

 Required for Oracle products using shared libraries. Must include:

$ORACLE_HOME/lib.
ORACLE_BASE Not required, but recommended as part of an OFA-compliant installation.
ORACLE_HOME Must be set to the directory where the Oracle software will be installed.
ORACLE_SID Specifies the instance name, or SID of the Oracle Server. Must be unique for Oracle instances running on the same machine. Oracle Corporation recommends using four characters or less.
ORACLE_TERM Required by all character mode and Motif mode Oracle products. 386 386x 386u 386s dgd2 dgd4 hftc hft hpterm 3151 ncd220 sun sun5 vt100 vt220 wy50 wy150 xsun xsun5.
ORA_NLS10 Required when creating a database with characters set other than US7ASCII. Set to $ORACLE_HOME/nls/data
PATH The search path must include: $ORACLE_HOME/bin, /bin, /usr/bin, and /usr/local/bin.
TMPDIR A directory with free space where the Oracle account has write permission. The default location on UNIX is /usr/tmp.

6.1.2.3 Free Up Disk Space in the /tmp Directory

The Oracle Installer needs some temporary disk space during the installation in /tmp. Check the required space in tmp directory under Hardware Requirements for the relevant operating system.


Note:

For disk space requirements check the specific Quick Installation Guide Section provided with the Operating System.

To determine the amount of free disk space available in the /tmp directory, enter the following command in a command shell:

df /tmp

If the space available in the /tmp directory is less than required, complete one of the following steps:

  1. Delete unnecessary files from the /tmp directory to achieve the required disk space.

  2. Set the TEMP and TMPDIR environment variables when setting the Oracle user's environment (described later).

  3. Extend the file system that contains the /tmp directory. If necessary, contact your system administrator for information about extending file systems.

If you have determined that the /tmp directory had insufficient free disk space when checking the hardware requirements, enter the following commands to set the TEMP and TMPDIR environment variables. Specify a directory on a file system with sufficient free disk space.

  • In a Bourne, Bash, or Korn shell:

    TEMP=/directory

    TMPDIR=/directory

    export TEMP TMPDIR

  • In a command shell:

    setenv TEMP /directory

    setenv TMPDIR /directory

6.1.2.4 Copying the Database Start and Stop Scripts for the Oracle Server

Copy the start and stop scripts from folder addon/db/unix/scripts to the directory /opt/oracle/bin.

  • start_plm62

  • stop_ plm62

  • stop_ plm62_immediate

  • stop_ plm62_transactional

6.2 Installing Oracle Database Server 12c


Note:

This chapter describes the manual installation of the Oracle Database Server. Keep in mind that on UNIX only the manual installation can be performed. For the installation on a Windows operating system with the Agile e6 Installer see chapter Installation with the Agile e6 Installer.


Note:

If you have already installed Oracle database client (32-bit) on the same machine, please restart it before installing the Oracle database server.

Start the Oracle Database installation

  • Windows

    Run setup.exe from the downloaded Oracle Installation Media.

  • UNIX

    Log in as the oracle user and navigate to the database directory. Start the Oracle Universal Installer with the following command:

    ./runInstaller

The Configure Security Updates screen is opened.

You can opt for notifications about security issues and security updates from My Oracle Support.

  1. To receive notifications about the security issues via email, enter your email address in the Email text field.

  2. To receive security updates:

    1. Enter the email address you have provided when registering with My Oracle Support.

    2. Select the I wish to receive security updates via My Oracle Support option and enter your My Oracle Support password.


    Note:

    If you wish not to receive security updates, do not check the I wish to receive security updates via My Oracle Support check box.

    By default, the I wish to receive security updates... option is not selected. If your company's policy requires such updates, then this option should be selected.

  3. Click Next.

    The My Oracle Support Username/Email Address Not Specified warning appears.

  4. Click Yes.

    The Select Installation Option screen is opened.

  5. Select Install database software only and click Next.

    The Grid Installation Options screen is opened.

  6. Select Single instance database installation and click Next.


    Note:

    The Real Application Cluster database installation is not a subject of this guide.

    The Select Product Languages screen is opened.

  7. Select English as the product language.

    If you want the Oracle database to operate in any other language select the required language from the list of the product languages.


    Note:

    The scope of translation for a given component may differ from language to language. For example, some translations may include all the user interface texts, while some may include only the error messages without any help file.

  8. Click Next.

    The Select Database Edition screen is opened.

  9. After your selection, click Next.

    The Specify Oracle Home screen is opened.

    The Oracle Home User is different from an Oracle Installation User. The Oracle Installation User is the user who requires administrative privileges to install Oracle products. The Oracle Home User is used to run the Windows services for the Oracle Home.

    The Oracle home user can be the Windows build-in account or a Windows user account. For enhanced security, Oracle recommends that a standard Windows user account be chosen as the Oracle home user for a database server installation. If a Windows user account is used, it must be a standard Windows user account (not an administrator) and for single instance database installations can be a local user, a domain user, or a managed services account. For Oracle Database RAC installations, the Windows user account must be a domain user.

  10. Specify the Oracle home user and click Next.

    The Specify Installation Location screen is opened.

  11. Specify the installation location for the Oracle Base directory and the Software Location which is the Oracle Home directory (e.g. $ORACLE_BASE/product/12.1.0/dbhome_1).

    If the selected Oracle home location is the same as the user home directory, the following warning message appears:

    [INS-32008] Oracle base location can't be the same as the user home directory.


    Note:

    If possible, avoid having the same directory for the Oracle Base and the Oracle home directory.

    If the selected Oracle home location is outside of Oracle base, the following warning message appears:

    [INS-32018] The selected Oracle home is outside of Oracle base.

    If possible avoid having the Oracle home outside of Oracle base.

  12. To override the warning, click Yes.

    The Perform Prerequisites Checks screen is opened, displaying the verification process.

    Upon completion of the checks, the installer displays the results for review.

    If any of the requirements are not met, the installer displays a list of the failed checks and their actual and expected values.


    Note:

    UNIX

    The Fix & Check Again button, and the function to create a fixup script will only appear on a UNIX operating system.

    You may click the Fix & Check Again button to generate a fixup script.

    The nodes on which the prerequisites failed, are listed in the Execute Fixup Script window. You can run the fixup script as a root user to complete the required pre-installation steps.

    Using the fixup scripts does not ensure that all the prerequisites for installing the Oracle Database are satisfied. You still have to verify that all the pre-installation requirements are met to ensure a successful installation.

    When all of the minimum requirements are met, the Summary screen is opened.

  13. In the Summary screen, review the global settings you have chosen and click Install to start the installation.

    The Installation Progress screen is opened.

  14. When the installation completes, the Finish screen is opened

  15. Click Close to exit.


Note:

For Oracle Database 12cR1 (12.1.0.2), you can install the database server patch (64-bit) if required:

- WINDOWS DB BUNDLE PATCH 12.1.0.2.4 - 20684004

- UNIX - PRO*C METHOD 4 LEAKS MEMORY IN 12.1 - 20051833


Note:

Further information about these database server patches can be found on the Oracle Patches and Updates support website:

- Windows: https://updates.oracle.com/Orion/Services/download?type=readme&aru=18784207

- UNIX example: https://updates.oracle.com/Orion/Services/download?type=readme&aru=18369852

6.3 Installing Oracle Database Client


Note:

This chapter describes the manual installation of the Oracle Database client. Keep in mind that on UNIX only the manual installation can be performed. For the automatic installation on a Windows operating system refer to the chapter Installation with the Agile e6 Installer.


Note:

If you have already installed Oracle database server on the same machine, please restart it before installing the Oracle database client.


Note:

The 32-bit Oracle client must be installed on the same machine where Agile e6.2.1.0 is installed.

  1. The first step of the installation is different for Windows and UNIX.

    • Windows

      1. Run setup.exe from the downloaded Oracle Installation Media.

    • UNIX

      1. Log in as the Oracle user and start the Oracle Universal Installer with the following command:

      ./runInstaller

      The Select Installation Type screen is opened.

  2. Select Custom and click Next.

    The Download Software Updates screen is opened.

  3. Select Skip software updates and click Next.

    Skip software updates is the default selection.

    The Select Product Languages screen is opened.

  4. Select English as the product language and click Next.

    The Specify Oracle Home User screen is opened.

    The Oracle home user is different from an Oracle installation user. The Oracle installation user is the user who requires administrative privileges to install Oracle products. The Oracle home user is used to run the Windows services for the Oracle home.

    The Oracle home user can be the Windows built-in account or a Windows user account. For enhanced security, Oracle recommends that a standard Windows user account has to be chosen as the Oracle home user for a database client installation. If a Windows user account is used, it must be a standard Windows user account (not an administrator) and can be a local user, a domain user, or a managed services account.

  5. Specify the Oracle home user and click Next.

    The Specify Installation Location screen is opened.

  6. Specify the installation location for the Oracle base directory and the Oracle home directory.

  7. Click Next.

    • If the Oracle base location is the same as the user home directory, the following warning message appears:

      [INS-32008] Oracle base location can't be the same as the user home directory.


      Note:

      If possible, avoid having the same directory for the Oracle Base and the Oracle home directory.

    • If the selected Oracle home location is outside of Oracle base, the following warning message appears:

      [INS-32018] The selected Oracle home is outside of Oracle base.


      Note:

      If possible, avoid having the Oracle home outside of Oracle base.

  8. Click Yes to override the warning.

    The Available Product Components screen is opened.

  9. Select the following components to install (as shown in the screen above):

    • Oracle Database Utilities

    • Oracle Java Client

    • SQL*Plus

    • Oracle JDBC/THIN Interfaces

    • Oracle Call Interface (OCI)

    • Oracle Programmer

    • Oracle Net

  10. Click Next.

    The Perform Prerequisites Checks screen is opened, displaying the verification process.

    The Perform Prerequisite Checks screen verifies if your computer meets the minimum system requirements to install the desired product.

    Upon completion of the checks, the installer displays the results for review.

    If any of the requirements are not met, the installer displays a list of the failed checks and their actual and expected values.


    Note:

    UNIX:

    The "Fix & Check Again" button and the function to create a fixup script will only appear on a UNIX operating system.

    You may click the Fix & Check Again button to generate a fixup script.

    The nodes on which the prerequisites failed are listed in the Execute Fixup Script window. You can run the fixup script as a root user to complete the required pre-installation steps.

    Using the fixup scripts does not ensure that all the prerequisites for installing the Oracle database are satisfied. You must still verify that all the pre-installation requirements are met to ensure a successful installation.

  11. Upon completion, the Finish screen is opened.

  12. Click Close to exit the Oracle Client Installer.

6.3.1 Install Database Client Patch


Note:

The database client of Oracle Database 12cR1 (12.1.0.2) requires the following patch (32-bit) to be installed:

- WINDOWS DB BUNDLE PATCH 12.1.0.2.170117 - 25115951

- UNIX Database Patch Set Update 12.1.0.2.170117 - 24732082

Note: If you are on HP-UX platform, please use database client patch 20051833


Note:

Further information and instructions about these database client patches can be found in the respective Readme file from the Oracle Patches and Updates support website:

- Windows: https://updates.oracle.com/Orion/Services/download?type=readme&aru=20996006

- UNIX example: https://updates.oracle.com/Orion/Services/download?type=readme&aru=21238448

Installation Example for Windows:


Note:

You must use the OPatch utility version 12.1.0.1.2 or later to apply this patch.		 

unzip p25115951_121020_WINNT.zip
 cd 25115951
 %ORACLE_HOME%\OPatch\opatch.bat apply

Installation Example for UNIX:


Note:

Ensure that the Oracle home on which you are installing the patch, or from which you are rolling back the patch, is Oracle Database 12c Release 12.1.0.2.0.		 

$ unzip -d <PATCH_TOP_DIR> p24732082_<121020_UNIX-SYSTEM>.zip
$ cd <PATCH_TOP_DIR>/24732082
$ $ORACLE_HOME/OPatch/opatch apply

6.4 Post-Installation Modifications for the Oracle Database 12c

6.4.1 Creating the Database


Note:

This chapter describes the manual creation of the Database schema. Keep in mind that on UNIX, only the manual creation can be performed. For the automatic creation on a Windows operating system see chapter Installation with the Agile e6 Installer.

Before creating the database instance, the database listener needs to be configured.

6.4.1.1 Configure the Listener

  1. Start the Oracle Net Configuration Assistant.

    • Windows

      1. Start the Oracle Net Configuration Assistant.

      2. Click Start > All Programs > Oracle - OraDb192c_home1 >Configuration and Migration Tools > Net Configuration Assistant.

    • UNIX

      1. Open a new terminal and start the Oracle Net Services Configuration Tool with the following command:

      $ORACLE_HOME/bin/netca

    The Oracle Net configuration Assistant - Welcome screen is opened.

  2. Select the Listener configuration and click Next.

    The Oracle Net configuration Assistant - Listener Configuration, Listener screen is opened.

  3. Select Add and click Next.

    The Oracle Net configuration Assistant - Listener Configuration, Listener Name screen is opened.

  4. Enter the Listener name to be created and click Next.

    If you created the Oracle home user with non-Windows-Built-In Account while installing oracle database server, the password for the Oracle home user is here required.

  5. Click Next.

    The Oracle Net configuration Assistant - Listener Configuration, Select Protocols screen is opened.

  6. Make sure TCP is listed in the Selected Protocols list and click Next.

    TCP is the default selection.

    The Oracle Net configuration Assistant - Listener Configuration, TCP/IP Protocol screen is opened.

  7. Select the standard port number of 1521.

    You may choose any port number that has not been used yet.

  8. Click Next.

    The Oracle Net configuration Assistant - Listener Configuration, More Listeners? screen is opened.

  9. Select No and click Next.

    The Oracle Net configuration Assistant - Listener Configuration Done screen is opened.

  10. Click Next and finish to close the Listener Configuration.

    Your database listener is now created and started.

6.4.1.2 Configuring the Database Net Service Name

This section describes the manual configuration of the Database Net Service Name.


Note:

The following instruction is only necessary for the database!


Note:

On UNIX, only the manual configuration can be performed. For the configuration on a Windows operating system see chapter Installation with the Agile e6 Installer.

  1. Start the Oracle Net Services Configuration Assistant.

    • Windows

      Click Start > All Programs > Oracle - OraClient12Home1_32bit > Configuration and Migration Tools > Net Configuration Assistant.

    • UNIX

      Enter the command: $ORACLE_HOME/bin/netca

    The Welcome to the Oracle Net Configuration Assistant screen is opened.

  2. Select the Local Net Service Name configuration and click Next.

  3. Select Add and click Next.

  4. Enter the Service Name.

    This is the global database name you provided by the database creation. In the example it is plm62.example.com.

  5. Click Next.

  6. Select the TCP protocol and click Next.

  7. Enter the fully qualified host name - where the Oracle database is located and click Next.

  8. Select No, do not test and click Next.

  9. Enter the Net Service Name and click Next.

    This is the same name as entered above.

  10. Select No and click Next.

    The Net service name configuration is completed.

  11. Click Next.

  12. Click Finish to quit.

6.4.1.3 Create the Database

The database is created by using the Database Configuration Assistant (DBCA) templates. DBCA templates include database options, initialization parameters, and storage information for data files, table spaces, control files and redo logs.

Five different templates are predefined to meet different requirements according to the purpose, size, and number of users of the Agile e6.2.1.0 database installation.

For additional information on significant database parameters and settings of each template, refer to the Hardware Sizing Guide for Agile e6.2.1.0.


Note:

In all the examples given in this chapter, the name of the Oracle Home for Oracle Database installation is OraDb12c_home1. You may use a different name in your installation.

  1. Refer to the downloaded media pack - Oracle Agile Engineering Data Management Application (Release e6.2.1.0).

    • Windows

      1. All the templates are in the db_addon\axalant\db_util\oracle\windows\templates directory.

      2. Copy the required DBCA template file (e.g. plm_prod_medium.dbt) to the %ORACLE_HOME%\assistants\dbca\templates directory.

      3. Start the Oracle Database Configuration Assistant from the Windows Start menu.

      Search for application Database Configuration Assistant and start it.

    • UNIX

      1. All the templates are in the addon/db/unix/templates directory.

      2. Copy the required DBCA template file (e.g. plm_prod_medium.dbt) to the $ORACLE_HOME/assistants/dbca/templates directory.

      3. Start the Oracle Database Configuration Assistant

      $ORACLE_HOME/bin/dbca

      The Database Configuration Assistant: Welcome screen is opened.

  2. Select Create a Database and click Next.

    The Database Configuration Assistant - Creation Mode screen is opened.

  3. Select Advanced Mode and click Next.

    The Database Configuration Assistant - Database Template screen is opened.

    The template that you have chosen and copied is available in this list.

  4. Select the template you want to use and click Next.

    The Database Configuration Assistant - Database Identification screen is opened.

  5. Enter the Global database name and database SID.

    The default SID is plm62. It is recommended to set the global database name to SID.<domain name>; for example, plm62.example.com. But it can also be left with the same name as the database SID.


    Note:

    Do not leave this field blank.

  6. Click Next.

    The Database Configuration Assistant - Management Options screen is opened.

    With Oracle Database 12c the Enterprise Manager (EM) Database Express can be installed in two ways:

    • EM Database Express

      Oracle Enterprise Manager Database Express is a web-based database management tool that is built inside each Oracle database. All the SQL commands you normally type have been translated into a graphical point-and-click interface. EM Database Express even supports RAC database management.

      EM Express is not a direct replacement for DB Control. EM Express is built inside the database server and there are limitations as to what it can do. EM Express is also focused on providing performance management and monitoring functionality, and is not meant to be an all around database administration tool.

    • EM Cloud Control

      Cloud Control provides Web-based management tools for managing individual database instances, as well as central management tools for managing your entire Oracle environment, including multiple databases, hosts, application servers, and other components of your network. It can even be used to manage non-Oracle databases.

      For more information about centrally managing the databases, application servers, hosts, and other components of your network, see Oracle Enterprise Manager Administration Guide.

  7. Select the option Configure Enterprise Manager (EM) Database Express.

    The Oracle Configuration Assistant - Database Credentials screen is opened.

  8. Enter passwords for SYS, SYSTEM and click Next.


    Note:

    It is highly recommended to use different passwords for these accounts.


    Note:

    Each password needs to meet the Oracle recommended standards. A password should have a minimum of 8 characters. In addition, the password must contain at least one upper and one lower case character, and one digit.


    Note:

    If your Oracle home user is not the Windows built-in account, please use the password of the Oracle home user for the Windows service configuration.

    The Database Configuration Assistant - Network Configuration screen is opened.

  9. Now you can see the listener you created and configured before in the list with the status up. Select it and click Next.

    The Database Configuration Assistant - Storage Locations screen is opened.

  10. Select Use Database File Locations from Template.

  11. Click the File Location Variables… button.

    The File Location Variables screen is opened.

  12. Enter the value for the variables.

    The values that you have to provide are the directories created, as described in chapter Oracle Database Prerequisites (example E:, F:, H:). DBCA will create the subdirectory plm62 in the directories where the database data files will be created.


    Note:

    If missing, please add File Creation Variables as described below.

    Example: Depending on the selected template, the following table provides information on predefined file destination variables.

    Variable Description
    ORADATA1 Directory for data files of tablespaces EDB, EDB_LOB, EDB_TMPIDX
    ORADATA2 Directory for data files of tablespaces EDB_IDX, EDB_TMP
    ORADATA3 Directory for data files of temporary tablespace TEMP
    ORADATA4 Directory for data files of undo tablespace
    ORADATA5 Directory for data files of tablespaces SYSTEM, TOOLS, USERS
    ORAARCH Directory for Archive log files
    REDO1 Directory for redo log files
    REDO2 Directory for redo log files

    The following listing gives values that you can set for the variables when you have different number of disks:

    Number of Disks Contents
    1 There is only one directory - e.g. /data1)

    Disk1: ORADATA1, ORADATA2, ORADATA3, ORADATA4, ORADATA5, REDO1, REDO2, ORAARCH - all variables will be set to /disk1
    2 There are two directories - e.g. /data1, /data2

    Disk1: ORADATA1, ORADATA4, ORADATA5, REDO1 - they get the value of /data1

    Disk2: ORADATA2, ORADATA3, ORAARCH, REDO2 - they get the value of /data2
    3 Disk1: ORADATA1, ORADATA5

    Disk2: ORADATA2, ORADATA4, REDO1

    Disk3: ORADATA3, ORAARCH, REDO2
    4 Disk1: ORADATA1, REDO1

    Disk2: ORADATA2, REDO2

    Disk3: ORADATA3, ORAARCH

    Disk4: ORADATA4, ORADATA5
    5 Disk1: ORADATA1, REDO1

    Disk2: ORADATA2, ORAARCH

    Disk3: ORADATA3, ORADATA5

    Disk4: ORADATA4

    Disk5: REDO2
    6 Disk1: ORADATA1

    Disk2: ORADATA2, ORAARCH

    Disk3: ORADATA3

    Disk4: ORADATA4

    Disk5: ORADATA5, REDO1

    Disk6: REDO2
    7 Disk1: ORADATA1

    Disk2: ORADATA2

    Disk3: ORADATA3

    Disk4: ORADATA4

    Disk5: ORADATA5, ORAARCH

    Disk6: REDO1

    Disk7: REDO2
    8 Disk1: ORADATA1

    Disk2: ORADATA2

    Disk3: ORADATA3

    Disk4: ORADATA4

    Disk5: ORADATA5

    Disk6: ORAARCH

    Disk7: REDO1

    Disk8: REDO2

  13. Click OK.

  14. Deselect the option Specify Flash Recovery Area.

    Depending on your backup strategy and used template, archiving can be enabled.


    Note:

    For a productive database it is highly recommended to archive the database. To specify the destination of the archive directory, click the button Edit Archive Mode Parameters button (predefined by the variable ORAARCH).

    After editing this screen, click OK to return to the Storage Location screen.

  15. Click Next.

    The Database Configuration Assistant - Database Options screen is opened.

    This screen provides database features as well as the possibility to run custom scripts after the database creation.

    We do not recommend changing the settings provided by the template.


    Note:

    If you have selected Oracle Application Express for customer specific installation, you have to change the initialization parameter max_string_size to standard.

    After the initial creation of the database, the parameter needs to be changed back to extended.

    Please follow the guideline in the Oracle Database documentation

  16. Click Next.

    The next screen provides different database parameters. You can navigate to the setting of memory, character sets, database sizing, and connection mode. Usually all parameters are set by the selected template and you don't need to change them. Experienced users can modify some parameters, depending on the database size and number of users.

    For complete information on additional parameters, e.g. memory, refer to the Hardware Sizing guide for Agile e6.2.1.0.

  17. Click All Initialization Parameters button to review all server parameters.

    The All Initialization Parameters screen is opened.

    Click Show Advanced Parameters.


    Note:

    Ensure that the value of memory_max_target is greater than the value of memory_target.

  18. Click Close and then click Next.

    The Database Configuration Assistant - Creation Options screen is opened.

  19. Click the Customize Storage Locations button to review the storage parameters for database creation.

    The Customize Storage screen is opened.

  20. Click Close to return to the Database Configuration Assistant - Creation Options screen.

  21. Select Create Database, Save as a Database Template, and Generate Database Creation Scripts.

  22. Click Next.

    The Database Configuration Assistant - Summary screen is opened.

    A summary of the database parameters is shown.

  23. Click Finish.

    The database creation process is started.

  24. When the database creation is done, the summary screen is shown.

    The EM database Express URL is listed for your access.

    Click Close to finish the process.

  25. Test the database connection with the following command:

    sqlplus system@plm62/<SYSTEM password>

6.4.1.4 Configuring tnsnames.ora and sqlnet.ora

  1. Start the Oracle Net Manager.

    • Windows:

      Click Start > All Programs > Oracle - OraClient12Home1_32bit > Configuration and Migration Tools > Net Manager.

    • UNIX

      Enter the command: $ORACLE_HOME/bin/netmgr

  2. Expand the view for Local and click on Profile.

  3. On the tab Methods, enter your domain name in the field Default Domain.

  4. In the main menu, click File > Save Network Configuration.

  5. Click File > Exit.

    The sqlnet.ora and tnsnames.ora under $ORACLE_HOME/network/admin/ will be created or updated.

    .

6.4.2 Modifying the Oracle Database


Note:

This section describes the manual modification of the Database. Keep in mind that on UNIX only the manual modification can be performed.

6.4.2.1 Create Directories for the Oracle Data Pump Utility

  1. Create a directory which will be used for the Oracle Data Pump Export/Import Utility with two subdirectories - system and user (for instance D:\ora_dmp\system; D:\ora_dmp\user).

  2. Open an SQLplus session and connect as user 'system'.

    sqlplus system/<system password>

  3. Run the script ddl_pump_dir.sql.

    It is located in the addon/db/sql directory of the downloaded Oracle Agile Engineering Data Management Application (Release e6.2.1.0) package.

    SQL>@<full path to the file ddl_pump_dir.sql>

  4. Enter the path to the main directory created under step 1 (for instance d:\ora_dmp).

    The script will create two directory objects - one for system users, and one for normal users and will give rights for the second directory to user PLM.

6.4.2.2 Create a Database User and Role

You will need to create the Agile e6.2.1.0 database user and role and provide the necessary privileges and quotas. You can do this by using the following commands, or by using the Oracle Enterprise Manager Database Control as described in the section below.

You can create AGILE_E_ROLE role and plm schema also by executing the script cre_plm_usr.sql in the directory …/addon/db/sql.

SQL>@<full path to the file cre_plm_usr.sql>

Username (e.g. PLM) and password have to be provided.

6.4.2.2.1 Using SQL to Create a Role

  1. Check if the plm role exists.

    1. Open an SQLplus session

    2. Connect as SYS or SYSTEM.

    3. Execute the following command:

      select role from dba_roles where role='AGILE_E_ROLE';

  2. If string 'AGILE_E_ROLE' is returned, the role exists.

    If it exists, skip the role creation and continue with Using SQL to Create a User.

    Otherwise, the role has to be created.

  3. Use the SQL code below to create the role AGILE_E_ROLE:

    CREATE ROLE AGILE_E_ROLE;
GRANT CONNECT TO AGILE_E_ROLE;
GRANT CREATE TABLE TO AGILE_E_ROLE;
GRANT CREATE VIEW TO AGILE_E_ROLE;
GRANT CREATE SYNONYM TO AGILE_E_ROLE;
GRANT CREATE DATABASE LINK TO AGILE_E_ROLE;
GRANT CREATE SEQUENCE TO AGILE_E_ROLE;
GRANT ALTER SESSION TO AGILE_E_ROLE;
GRANT CREATE PROCEDURE TO AGILE_E_ROLE;
GRANT CREATE TRIGGER TO AGILE_E_ROLE;
GRANT ALL ON DIRECTORY ORA_DMP TO AGILE_E_ROLE;
6.4.2.2.2 Using SQL to Create a User

  1. Use the SQL code below to create the plm schema (e.g. PLM):

    CREATE USER PLM
IDENTIFIED BY <PASSWORD>
DEFAULT TABLESPACE "EDB"
TEMPORARY TABLESPACE "TEMP"
PROFILE DEFAULT
QUOTA UNLIMITED ON "EDB"
QUOTA UNLIMITED ON "EDB_IDX"
QUOTA UNLIMITED ON "EDB_TMP"
QUOTA UNLIMITED ON "EDB_TMPIDX"
QUOTA UNLIMITED ON "EDB_LOB"
ACCOUNT UNLOCK;
GRANT "AGILE_E_ROLE" TO PLM;
ALTER USER PLM DEFAULT ROLE AGILE_E_ROLE;
6.4.2.2.3 Using Enterprise Manager Database Express to Create a User

How to find the port on which EM Express is configured:

  • When dbca completes, it indicates the port on which EM Express is configured.

  • If that information is no longer available, there are two ways to find the HTTP/HTTPS port for EM Express:

    >lsnrctl status | grep HTTP (DESCRIPTION=(ADDRESS=(PROTOCOL=tcps)(HOST=xxx.us.oracle.com)(PORT=5500))(Security=(my_wallet directory=/u01/oracle/app/oracle/admin/plm62/xdb_wallet))(Presentation=HTTP)(Session=RAW))

    or from SQL*Plus:

    SQL>select dbms_xdb.getHttpPort() from dual; 
GETHTTPPORT 
----------- 
8080 
SQL> select dbms_xdb_config.getHttpsPort() from dual; 
GETHTTPSPORT 
------------ 
5500

You can access the Oracle Enterprise Manager Database Express as follows:

  1. Open your browser and enter the following URL:

    https://<hostname>:<port>/em

  2. Enter your user credentials and click Login.

  3. In the top menu bar, click Security and then select Users.

  4. Click Create User on the user list.

  5. Insert a user name and password in the pop-up dialog.

  6. Assign default and temporary table space for this user.

  7. From the list with Available Roles, select the role AGILE_E_ROLE.

    The role AGILE_E_ROLE was created in the previous section "Create a Database User and Role."

  8. Click Move.

    The role is moved to the Selected Roles list.

    Click OK.

  9. Click the newly created user and open the tab Quotas.

  10. Assign unlimited quota to EDB, EDB_IDX, EDB_LOB, EDB_TMP, and EDB_TMPIDX.

    The user creation is finished.

6.4.2.3 Import the Database Dump

Import the Agile e6.2.1.0 dump, using the following commands, and then check the log file for errors.

  • Windows

    Make sure that the variable NLS_LANG is set to AMERICAN_ AMERICA.AL32UTF8.

    Check the registry for the value of the variable NLS_LANG - HKEY_LOCAL_MACHINE\SOFTWARE\ORACLE\KEY_<12c installation>

  • UNIX

    Make sure that the correct value is set for the environment variable NLS_LANG (value from the file csh_ORA12.1.0 - AMERICAN_AMERICA.WE8MSWIN1252).

  1. Start the import.

    imp username/pass@plm61 file=plm62.dmp log=plm61.log buffer=500000 commit=y statistics=none full=y


    Note:

    username/ pass are the name and the password of the user you created in the database.

commit=y Rollback segments cannot get too small
statistics=n No statistics will be created
buffer=500000 Necessary for lobs, better performance
full=y Imports full dump, even if the dump was exported by different users


Note:

You can import only your own e6 dmp files which were created in a database in which the initialization parameter max_string_size =standard. Be aware that the e6 database has set this parameter to extended. Please use data pump utilities (expdp, impdp) instead. For more details, see Oracle 12c Database documentation.

All standard dmp files delivered on Oracle edelivery for e6.2.1.0 can be imported with imp/exp utility.

6.4.2.4 Compile All Invalid Objects in Schema PLM

After importing the Agile e6.2.1.0 dump, some objects might be invalid. This can be verified by the following way:

  1. Open an SQLplus session and connect as 'sys' - as sysdba.

    sqlplus sys/<sys password> as sysdba
SQL> select count(*) from dba_objects where status <> 'VALID' and owner='PLM';

    If the returned message is 'no rows selected', then you have no invalid objects.

  2. 2. Otherwise, execute the script utlrp.sql.

    The script will compile all invalid objects in the database.

    SQL>@?/rdbms/admin/utlrp.sql

  3. Verify that there are no invalid objects:

    SQL>select count(*) from dba_objects where status <> 'VALID' and owner='PLM';

6.4.2.5 Gather Statistics

In Oracle 12c, the default value for the OPTIMIZER_MODE initialization parameter is ALL_ROWS, which means that a cost-based approach will be used for all SQL statements. Oracle highly recommends creating statistics in order to avoid performance losses. This should be done after the dump import and has to be repeated periodically.

  1. Calculate statistics of all tables and indexes in db schema PLM:

    SQL>EXECUTE DBMS_STATS.GATHER_SCHEMA_STATS('PLM',CASCADE =>true);

    Note:

    Statistic information can be viewed, e.g. in user_tables and user_indexes. These views provide information about average width of the row and number of rows.

    For more information about statistics management please refer to the Oracle Database manuals.

6.4.2.6 Problems During Database Creation

When having problems with the database creation, perform the following checks:

  • Database creation logs: ${ORACLE_BASE}/cfgtools/dbca/<db name>

  • Instance Parameter file: ${ORACLE_BASE}/admin/<db name>/pfile/init.ora

  • Instance SPFILE: ${ORACLE_HOME}/dbs/spfile<db name>.ora

  • Database Diagnostics: ${ORACLE_BASE}/diag/rdbms/<db name>/<db name>

  • Network configuration: ${ORACLE_HOME}/network/admin/*.ora

  Previous
Previous 		 Next
Next
  Go To Table Of Contents
Contents