1. Deploying JD Edwards EnterpriseOne on Microsoft Windows with Oracle Database Learning Path
  2. Setting Up the Oracle Database Server

Setting Up the Oracle Database Server

This section shows you how to setup the Oracle Database Server.

Prerequisites

  • You must a Microsoft Windows VM or server for the Oracle Database Server.
  • You must have performed the functions described in the module of this Learning Path entitled: Performing Common Setup for All Microsoft Window Servers.

Prerequisite Configuration for the Oracle Database Server

The JD Edwards EnterpriseOne One-Click deployment of the Oracle database supports both Oracle Enterprise Edition and Standard Edition 2 for the current supported release of Oracle Database.

Important:

If you choose to use your own Oracle Database for the Database Server, you should have an Oracle DBA monitor the database relative to subsequent JD Edwards functions, such as Package Build. Database aspects such as Archive Logging can adversely affect disk space usage and could potentially cause database failures.

The following prerequisite configuration settings are applicable to a customer-installed Oracle database. These prerequisites must be met before the One-Click Provisioning Server can install a JD Edwards EnterpriseOne Database Server:

  • You must have an Oracle Database Server instance installed.

    Important:

    The password for the database users of an Oracle database in an Oracle Cloud Infrastructure Compute instance can only include these special characters: _ # -

  • You must make TNS entry of the pluggable database in the tnsnames.ora file on the Database Server instance (do not use a variable for ORACLE_HOME; you must use an absolute value for the entry). The hostname field should be updated with the hostname of the Database Server machine.

    Important:

    For the shared schema, the TNS Alias must be JDEORCL and for non-shared schema it must be an alias value other than JDEORCL.

  • You must install the Oracle database as the oracle user -- not as any other user such as opc.
  • You must set the database character set to AL32UTF8
  • You must set the database national character set for the Unicode page setting to AL16UTF16
    Important: The character set parameters are critical and must be set when the database is installed; they cannot be changed after installation.
  • Minimum storage requirement for JD Edwards Shared Database is 10 GB
  • Minimum storage requirement per pathcode is 20GB (Including demo data)
  • Above mentioned storage should be made available for:
    • OraDB install directory
    • OraDB index directory
    • OraDB table directory
  • These are the directories that you will specify during Orchestration.
    Important: Best practice is to use different mount points for creating these directories. Otherwise you may encounter database deployment issues.
  • Customer must set the minimum required DB processes to provision the JD Edwards EnterpriseOne Database Server to a minimum value of 1500
  • Customer must ensure the Files System IO option is SETALL
  • Database must be running with PDB (JDEORCL) set to OPEN_MODE
  • Set environment variables for both Oracle Database because by default environment variables for the oracle user are not set.

The following is a detailed list of commands necessary to set up the prerequisites for the Oracle Database for use with JD Edwards EnterpriseOne One-Click Provisioning.

  1. You must make a TNS entry of the pluggable database in the listener.ora and tnsnames.ora files of the Database Server machine, where hostname is the hostname of the Compute Database Server machine. Ensure the same port is also specified in each file. For example:

    ----------------
listener.ora
----------------
LISTENER_ORCL =
(ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = 1521))

ORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = jdeorcl)
)
)
-------------------
tnsnames.ora
-------------------
JDEORCL =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = hostname)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = jdeorcl)
)
)

  2. Connect to the database using this command:

    sqlplus '/as sysdba';

  3. Verify the code page setting of the Oracle database using this command:

    SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER = 'NLS_CHARACTERSET';

  4. If the character set is not AL32UTF8, you will have to reinstall the database using the correct parameter to set it.

  5. Verify the Unicode code page setting of the Oracle database by executing this command:

    SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER = 'NLS_NCHAR_CHARACTERSET';

  6. If the setting is not AL16UTF16, you will have to reinstall the database using the correct parameter to set it.

  7. Determine the number of DB processes available using this command:

    select limit_value from v$resource_limit where resource_name='processes';

  8. If the value is less than 1500 (which is the minimum recommended for use with JD Edwards EnterpriseOne, run this command to set to the minimum recommended value:

    alter system set processes=1500 scope=spfile;

  9. Check the value of the filesystemio_option parameter using this command:

    show parameter filesystemio_options;

  10. If the value of the filesystemio_option parameter is not SETALL (which is required), use this command to set it:

    alter system set filesystemio_options=setall scope=spfile;

  11. Shutdown the database using this command:

    shutdown immediate;

  12. Start the database using this command:

    startup;

  13. Assuming your pluggable database is named JDEORCL, verify it is open using this command:

    select OPEN_MODE from v$pdbs where NAME = 'JDEORCL';

    If the pluggable database you want to use is not named JDEORCL, you can issue this command to find the name of available PDBs (ignore PDF$SEED) and substitute that name for JDEORCL in the command above):

    NAME, OPEN_MODE from v$pdbs;

  14. If the OPEN_MODE is set to READ WRITE then the PDB is ready to be provisioned by the JD Edwards EnterpriseOne One-Click Provisioning Server.

  15. If the OPEN_MODE is not READ WRITE then the PDB is not open. Open the PDB using this command:

    alter pluggable database JDEORCL open;

    where you if your database is named not JDEORCL, substitute that name in the above command.

  16. Log in to the database using this command:

    sqlplus sys/<DB_ADM_PWD>@<CONTAINER_SID>as sysdba;

    For example,

    sqlplus sys/Jde_Admin1@orcl as sysdba;

  17. Set the recovery space using this command:

    sql> ALTER SYSTEM SET db_recovery_file_dest_size=50G SCOPE=BOTH;

    The PDB is ready to be provisioned by the JD Edwards EnterpriseOne One-Click Provisioning Server.