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		  

7 Oracle Database 19c

7.1 Oracle Database Prerequisites 19c


Note:

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

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

7.1.2 UNIX

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

7.1.2.2 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

7.2 Installing Oracle Database Server 19c

This chapter describes the manual installation of the Oracle Database Server.


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

  1. Run the installer from the downloaded Oracle Installation Media

    Windows

    Run setup.exe

    UNIX

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

    ./runInstaller


    Note:

    You must extract the image software (<DB server installer>.zip) into the directory where you want your Oracle Database home to be located, and then run the Oracle Database Setup Wizard to start the Oracle Database installation and configuration. Oracle recommends that the Oracle home directory path you create is in compliance with the Oracle Optimal Flexible Architecture recommendations.

    The Select Configuration Option screen is opened.

  2. Choose "Set up Software Only" and click Next.

  3. In the Database Installation Options, select "Single instance database installation" and click Next


    Note:

    The Real Application Cluster database installation is not covered under this guide.

  4. For the database edition, please choose "Enterprise Edition and click Next


    Note:

    Depending on the installer package, there may be more options under this step but we will only cover Enterprise Edition installation

  5. Windows Only

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

    Specify the Oracle home user and click Next.

  6. Specify the installation location for the Oracle Base directory and click Next

  7. UNIX ONLY. Specify an Inventory directory and the proper Group to handle the orainventory directory and click Next

  8. UNIX ONLY. Set the corresponding group that will be responsible for each item and click Next.

  9. UNIX ONLY. Define the user with root privileges and click Next.

  10. Wait for prerequisite checks and the summary page.

  11. Click Install


    Note:

    UNIX Only

    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.

    For manual fixing of the pre-installation steps, you can refer to this link: https://docs.oracle.com/en/database/oracle/oracle-database/19/ladbi/completing-preinstallation-tasks-manually.html#GUID-54959149-E611-48EC-BDDF-F379E8B35C97

  12. Wait for the installation to be finished and click Close.

7.3 Installing Oracle Database Client


Note:

This chapter describes the manual installation of the Oracle Database client. Keep in mind that only the manual installation can be performed for Oracle 19c Database client.


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

      Run “setup.exe” from the downloaded Oracle Installation Media.

    • UNIX

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

  3. Specify the Oracle home user and click “Next”.

    The “Specify Installation Location” screen is opened.

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

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

  6. Click “Yes” to override the warning.

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

  8. 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 for 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

  9. Upon completion, the “Finish screen” is opened.

  10. Click “Close” to exit the Oracle Client Installer.

7.3.1 Installing Oracle Database Client Patch

The database client of Oracle Database 19c (19.3.0) requires the following patch (32-bit) to be installed:

  • - WINDOWS DATABASE BUNDLE PATCH 19.13.0.0.211019 - 33155330

  • - UNIX DATABASE RELEASE UPDATE 19.13.0.0.0 - 33192793


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.

7.3.1.1 Installation Example for Windows:


Note:

You must use the OPatch utility version 12.2.0.1.27 or later to apply this patch. The readme of the database patch provides the download link for the necessary OPatch update.

unzip p33155330_190000_WINNT.zip cd 33155330 %ORACLE_HOME%\OPatch\opatch.bat apply

7.3.1.2 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 19c Release 19.3.0

$ unzip -d <PATCH_TOP_DIR> p33192793_190000__<UNIX-SYSTEM>.zip $ cd <PATCH_TOP_DIR>/33192793 $ $ORACLE_HOME/OPatch/opatch apply

7.3.2 Post-Installation Configuration

7.3.2.1 NTLM is no longer enabled by default in 19c

Upon using the e6 server deployed in a Windows Server, you may encounter an "Incorrect Username or Password" in e6 Java Client. This indicates that e6 application server is encountering ORA-12638: Credential retrieval failed(visible in the C server logs). This error is introduced due to NTLM being no longer enabled by default in 19c while your Windows Servers are still using NTLM as Authentication Protocol.

The default value for NO_NTLM is now TRUE in 19c. If NTLM is still used, please explicitly add SQLNET.NO_NTLM=FALSE in $ORACLE_HOME/network/admin/sqlnet.ora on both client and server side. DB server requires restart if this parameter is updated (refer to MOS Note DOC ID 2757734.1 for details)

7.4 Post-Installation Modifications for the Oracle Database 19c

7.4.1 Creating the Database


Note:

This chapter describes the manual creation of the Database schema. Keep in mind that only the manual creation can be performed for Oracle Database 19c.

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

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

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

7.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 OraDb19c_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) RUP2 or later.

    • Windows

      1. All the templates are in the addon\db\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

  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 Deployment Type screen is opened.

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

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

    Minimum hardware requirements should be met depending on which configuration you choose.

    The Database Configuration Assistant - Database Identification screen is opened.

  5. Enter the Global database name and database SID. and click Next

    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. Select "Use template file for database storage attributes" and click "File location variables.

  7. Enter the value for the variables and click OK.

    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.


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

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

  10. Enable archive mode parameters Option and change any settings. Click OK

    The "Fast Recovery Option" page is reopened and you can see the listener you created and configured before in the list with the status up.

  11. Select the listener and click Next.

    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.

  12. Review and if experienced adapt the database parameters and 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.0.0.

  13. Select the option Choose Configure Enterprise Manager (EM) database express and choose the port where you will deploy the EM dashboard and click Next.

    EM Database Express Port is the https port to open express console: https://<hostname>:<port>/em//**

    The Database Configuration Assistant - Specify User Credentials is opened.

  14. Set your administrative user passwords.

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

    • We recommended each password to meet the Oracle recommended standards. A password should have minimum of 8 characters in length. In addition, the password must contain at least one upper case character, one lower case character and one digit.

    • If your oracle home user is not the windows built-in account, please give the password of oracle home user for the windows service configuration.

  15. Select "Save as a database template" if you want to save the template currently configured. This will make future installation faster and click on All Initialization Parameters button to review all server parameters.

    The All Initialization Parameters screen is opened.

  16. Click on Show Advanced Parameters and review parameters listed. Select close.


    Note:

    To be sure the value of memory_max_target has to be greater than the value of memory_target.

  17. Click on Customize Storage Locations to review the storage parameters for database creation and click Close.

    The Database Configuration Assistant - Summary screen is opened.

  18. Proceed to the "Summary" window for the final review and Click on "Finish" to start the database creation.

    Wait for the full database setup to finish. Once finished, a summary will pop-up. At this point, installation is now successful and you can now close the DBCA

  19. Test the database connection with the following command:

    sqlplus system@plm62/<SYSTEM password>

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

    .

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

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

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

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

7.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 19c Database documentation.

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

7.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. 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';

7.4.2.5 Gather Statistics

In Oracle 19c, 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 (https://docs.oracle.com/en/database/oracle/oracle-database/19/refrn/OPTIMIZER_MODE.html#GUID-DE448A8A-992F-4BAB-9302-A020039641E5).

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