6 Working with the Platform Pack in Silent Mode for a Non-Virtualized Database Server

This chapter describes using the Oracle Universal Installer for the Platform Pack in silent mode to install the JD Edwards EnterpriseOne Database Server components on a non-virtualized database server such as Oracle Exadata or Oracle Database Appliance (ODA).

Note:

If your non-virtualized database is not an Oracle Exadata or ODA machine, you can use the OUI in GUI mode as described in the appendix of this guide entitled: Appendix C, "Installing an OVM Database to a Non-Virtualized Database using OUI in GUI Mode".

This method assumes you are not installing the VM template for the JD Edwards EnterpriseOne database server, and that the installation of these components on a non-virtualized database server will be used with the Oracle VM templates for JD Edwards EnterpriseOne that utilizes the complementary components described in this guide.

Note:

This method can also be used on a Linux box with or without ASM, as desired.

This chapter discusses these topics:

6.1 Understanding the Platform Pack for a Non-Virtualized Database Server

When setting up the JD Edwards EnterpriseOne Database Server components on non-virtualized database servers that are to be used with JD Edwards EnterpriseOne Oracle VM templates, the connect string must match across all instances of the templates. The standard value is ovsorcl. If you change this value, you must make the corresponding change when instantiating database connectivity for every OVM template using the JD Edwards OVM Tools described in the section of this document entitled: Section 4.4, "Working with JD Edwards OVM Tools (config.sh Configuration Script)".

Note:

The Platform Pack installs artifacts for the DV910, PS910, and PY910 environments. It does not install the PD910 environment.

6.2 Understanding the Connect String

You must know the name of the Oracle instance on the server on which you are running the Platform Pack installer. To determine this name, run the following command:

srvctl status database -d ovsorcl

For example, the output will look similar to this:

Instance ovsorcl1 is running on node mymachine1
Instance ovsorcl2 is running on node mymachine2

In this example, if you are running on mymachine1, you need to set your environment variable ORACLE_SID to ovsorcl1. Otherwise the data pump commands (impdp) in the database load scripts will fail. However, when you are editing the Silent Install response file, you should supply the connect string ovsorcl (or the value you have definied to be used across all VM Templates for JD Edwards EnterpriseOne) so that EnterpriseOne Services can use the RAC performance.

Caution:

To ensure you have your environment variable set correctly, run this command before proceeding (substitute your password for system in place of xxx):

sqlplus system/xxx (do not supply the @connectstring)

If you cannot successfully connect to your local database without supplying the connect string, your load scripts will fail. Review the preceding notes.

6.3 Working with the Platform Pack Installer for a Non-Virtualized Database Server

This section discusses:

6.3.1 Working with the zip File for the Platform Pack Installer

The zip file for the Platform Pack Installer for a non-virtualized database server is included in the Media Pack for JD Edwards EnterpriseOne VM Templates, which is available from the Oracle Software Delivery Cloud:

https://edelivery.oracle.com/

Create a directory on the non-virtualized database server (which is a machine such as Oracle Exadata or ODA) that the oracle user can update. For example:

/u01/Exadata

Then run this command to set appropriate permissions on the created directory:

chmod -R 775 /u01/Exadata

6.3.2 Working with the Response File for the Platform Pack Installer

An interactive install of the database using the Oracle Universal Installer (OUI) is not supported on non-virtualized database servers such as Oracle Exadata or ODA. Therefore, you must run the OUI installer in silent mode, which is driven by parameters that you set in a response (.rsp) file. This section describes the appropriate settings that you must set within this file.

Note:

If your non-virtualized database is not an Oracle Exadata or ODA machine, you can use the OUI in GUI mode as described in the appendix of this guide entitled: Appendix C, "Installing an OVM Database to a Non-Virtualized Database using OUI in GUI Mode"

  1. Use an editor such as vi to open the OVMDB.rsp file that is located inside the \Exadata directory that is created when the installer zip file is unzipped.

  2. Edit the OVMDB.rsp response file to set valid parameters for your installation. Each section of the response file has comments to describe valid values. The entries that must be changed are at the top of the response file before the ###*###*### eye catcher.

    The following figures contain the Pre-Install Worksheet for Database Installation in Silent Mode -- Response File. This Worksheet describes each section that you must modify or verify to be valid for your installation on a non-virtualized database server. Use the Worksheet to enter valid values for your installation.

  3. Once edit, you should save and close the OVMDB.rsp response file.

Pre-Install Worksheet

Database Installation in Silent Mode - OVMDB.rsp Response File

Section Name Value Comment
ACCEPT_LICENSE_AGREEMENT   Valid values are true or false.

The shipped version of the OVMDB.rsp has this value set to false.

You must change this to true in order for the installation to be able to proceed.
UNIX_GROUP_NAME   Specify the UNIX group to be set for the inventory directory. Set this to the group name for the oracle user.

The default value is oinstall.
ORACLE_HOME   Specify the path where you want the installer to place the scripts and dump files.

For example, a valid home name might be:

/u01/app/oracle/JDEOVM/e910

Important: When setting ORACLE_HOME ensure the folder is empty and there is not another Oracle product installed in that folder.

ODA Considerations. For ODA you can put the scripts and dump files onto the shared disk space. For example:

/cloudfs/JDEOVM/e910

If using the shared disk space you can specify ovsorcl as your ORACLE_SID environment variable.
ORACLE_HOME_NAME   Specify the name of the Oracle Home.

The installer uses this name to create folders and services.

For example, a valid ORACLE_HOME_NAME might be:

JDEOVM_E910_1

Important: This name must be unique. Ensure you do not use an ORACLE_HOME_NAME that has already been defined on the server you are using.
connectString   Specify the Oracle connect string.

The standard Oracle connect string for the OVM templates is ovsorcl. If you enter a different value here, you must make the corresponding change when instantiating the OVM templates using the JD Edwards EnterpriseOne OVM Tools described in the chapter of this guide entitled: Chapter 4, "Working with Oracle VM Templates for JD Edwards EnterpriseOne".
JDEMODEN   Specify the mode as Install (0) or Upgrade (1).

You must choose Install mode (0) so that the installer will create and load the Business Data and Control Tables.

Do not choose Upgrade mode because in this mode the installer does not create or load the Business Data and Control Tables.

The default value is Install (0).
sysadmUser   Specify the name of the Oracle sysadmin.

You cannot specify sys as the user.
sysadmPwd   Specify the password for the Oracle sysadmin. This is a required value.
slOVMvalues   Specify a string list of location, machine names, and values that are required for use with JD Edwards EnterpriseOne VM templates.

The machine names should not be qualified.

The syntax for the string is:

slOVMvalues={"Location","deployment_server","html_ server","enterprise_server","ASM_YES_NO","BIP_YES_NO", ,"BIP_server","sys_password"}

where

Location is the location name for Package Deployment. For example, Corporate.

deployment_server is the machine name of the Deployment Server. This name must be specified in Upper Case. For example, CUSTVMDEP.

html_server is the machine name of the HTML Server. For example, custvmhtml.

enterprise_server is the machine name of the Enterprise Server. For example, custent.

ASM YES or NO is used to specify whether your database server is using Oracle Automatic Store Management (Oracle ASM). Valid values are YES or NO.

BIP YES or NO determines if you want to load the repository for Oracle BI Publisher. Valid values are YES or NO.

BIP_server is the machine name of your BIP server. This is only required if you specified YES to BIP YES or NO.

sys_password is the password for the sys user. This is only required if you specified YES to BIP YES or NO.

Caution: The import of the SQL procedures in the BI Publisher Repository will fail if you do not supply the correct sys password.

Here is an example of a valid command string, which must be contiguous with no spaces or line feeds:
slOVMvalues={"Corporate","CUSTVMDEP","custvmhtml","custvment","YES","YES","custvmbip","mypassword"}
orclTblDir   ASM Considerations. If you are using ASM, this value specifies the ASM disk group for the tables. The default value is: DATA.

Non-ASM. Specify the path to the directory where the Oracle tablespaces are to be created. You should change the default value to a valid value for your environment. For example:

/u01/jdedwardsppack/ORCL/Tables
orclIdxDir   ASM Considerations. If you are using ASM, this value specifies the ASM disk group for the indexes. The default value is DATA.

Non-ASM. Specifies the path to the directory where the Oracle indexes are to be created. You should change the default value to a valid value for your environment. For example:

/u01/jdedwardsppack/ORCL/Indexes
iRunScripts   Specify whether to deploy the scripts for the user to run later, or to run the scripts as part of the installation.

0 = Edit and deploy the scripts; you must run the scripts manually after the installer completes.

1 = Edit and deploy the scripts and dump files; the scripts are run automatically by the installer.

The default value is 1.
dbMach   Specify the SCAN listener or host name for the database server. You should change the default value to a valid value for your environment.
gbl_secure_Password   Specify the complex password to be used for all accounts created by the installer.

You should leave this value as DEFAULT until you bring up all servers in the JD Edwards EnterpriseOne system. You can then change the passwords in your database and in your JD Edwards EnterpriseOne administration.

Important: For all versions of Oracle VM Templates for JD Edwards EnterpriseOne prior to and including the GA release of the Oracle VM Templates for JD Edwards EnterpriseOne Tools Release 9.1.4.4 and Applications Release 9.1.2, you must manually edit this response file to rename this setting:

From: gbl_secure_Password="DEFAULT"

To: securePwd="DEFAULT"
bPrecreateTbsp   Specify whether you are precreating tablespaces where valid values are:

  • true

    Use this value if you want to precreate the tablespaces before running the install scripts.

  • false

    Use this value if you do not want to precreate the tablespaces. In this case, the installer scripts will create the tablespaces.

The default value is false.

6.3.3 Running the Platform Pack Installer for Non-Virtualized Database Servers

To run the Platform Pack installer for non-virtualized database servers (such as Oracle Exadata and ODA):

  1. Verify these values are set:

    • ORACLE_SID

    • ORACLE_HOME

    • ORACLE_BASE

  2. Ensure the value $ORACLE_HOME/bin is in the PATH environment variable.

  3. Change directory to the Exadata/install folder.

  4. Use this command syntax to run the installer. For the response file, you must specify the full path to the location of the Platform Pack installer image for non-virtualized database servers. For example:

    ./runInstaller -silent -responseFile /u01/Exadata/OVMDB.rsp

Caution:

You will not be able to start services until you have run the TLOVM001 Tools Accelerator on the Deployment Server. This is previously documented in the section of this guide entitled: Section 3.5.7.3, "Mandatory Post Installation Tools Accelerator".

6.3.4 Working with Installer Log Files

Upon completion, the installer reports success or failure for the Oracle database scripts. To verify the status of the install, you should:

  1. Check the logs in your install location in this directory:

    ORCL/logs

    Tip:

    It especially important that you check and verify the Import* logs.

  2. Check the logs in the Oracle inventory location, which by default is:

    /u01/app/oraInventory/logs

    This directory contains these log files:

    • silentInstallxxx.log

    • oraInstallxx

    • installActionsxxx

Note:

The following error will appear in the install logs: 
update PD910.F983051 set vrmkey='UNIT9057' where vrmkey = 'DEPLOYMSTR'
             *
ERROR at line 1:
ORA-00942: table or view does not exist

Ignore this error. The PD environment is no longer deployed, and this statement should not have been run. This error will not impact the success of the install.

6.3.5 Deinstalling the Platform Pack for Non-Virtualized Database Servers

Use this procedure to deinstall the Platform Pack for non-virtualized databases servers (such as Oracle Exadata and ODA).

  1. Navigate to your install location.

  2. Change directory to ORCL.

  3. Run this script:

    drop_db.sh

  4. Navigate to the oui folder within your install location.

  5. Change directory to bin.

  6. Use this command to run the OUI installer in silent mode to deinstall the Platform Pack for non-virtualized database servers.

    ./runInstaller -deinstall -silent REMOVE_HOMES={"/u01/JDEOVM/e910"} ORACLE_HOME_NAME="JDEOVM_E910"