Setting Up the Compute Oracle Database Server

This section shows you how to set up the Compute Oracle Database Server in the Oracle Cloud Infrastructure.

Prerequisites

You must have created a Microsoft Windows VM for the Compute Oracle Database Server.
You must have performed the steps described in the module "Performing Common Setup for All Microsoft Windows Servers"of this Learning Path.

Prerequisite Configuration for the Oracle Compute Database Server

The Oracle database that is deployed on the Oracle Cloud Infrastructure by the JD Edwards EnterpriseOne One-Click Provisioning, supports both the Oracle Enterprise Edition and the Standard Edition 2 for the current supported release of the Oracle Database. Refer to the Oracle Certifications for JD Edwards EnterpriseOne One-Click Provisioning on Oracle Cloud Infrastructure for current updates on supported software versions and software prerequisites.

Important: If you choose to use your own Oracle database for the Compute Database Server, you should have an Oracle DBA monitor the database for performance of subsequent JD Edwards functions, such as Package Build. Database functionalities such as archive logging can adversely affect disk space usage and could potentially cause database failures.

The following prerequisite configuration settings are applicable to both a customer-installed Oracle database and an Oracle Database Service. These prerequisite settings must be complete before the One-Click Provisioning Server installs a JD Edwards EnterpriseOne Database Server running on the Oracle Cloud Infrastructure:

You must have an Oracle Compute Database Server instance installed on the Oracle Cloud Infrastructure.
Important: The password for the users of an Oracle database in an Oracle Cloud Infrastructure Compute instance can only include these special characters:
```
Underscore(_)
Number sign(#)
Hyphen (-)
```
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, and 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; neither the character sets OR the parameters cannot be changed after installation.
Minimum storage requirement for the 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: The best practice is to use different mount points for creating these directories. Otherwise, you may encounter database deployment issues.
You must set the DB processes to provision the JD Edwards EnterpriseOne Database Server to a minimum value of 1500.
You must ensure that the Files System IO option is SETALL
You must ensure that the database is running with Pluggable Database (PDB) named JDEORCL set to OPEN_MODE.
Set environment variables for Oracle Database on Compute 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 running in the Oracle Cloud Infrastructure for use with JD Edwards EnterpriseOne One-Click Provisioning.

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

Connect to the database using this command:

sqlplus / 'as sysdba';
Verify the code page setting of the Oracle database using this command:

SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER = 'NLS_CHARACTERSET';
If the character set is not AL32UTF8, you will have to reinstall the database using the correct parameter to set it.
Verify the Unicode page setting of the Oracle database by executing this command:

SELECT VALUE FROM NLS_DATABASE_PARAMETERS WHERE PARAMETER = 'NLS_NCHAR_CHARACTERSET';
If the setting is not AL16UTF16, you will have to reinstall the database using the correct parameter to set the character set.
Determine the number of DB processes available using this command:

select limit_value from v$resource_limit where resource_name='processes';
If the value is less than 1500 (which is the minimum recommended for use with JD Edwards EnterpriseOne, run this command to set the minimum recommended value:

alter system set processes=1500 scope=spfile;
Check the value of the filesystemio_option parameter using this command:

show parameter filesystemio_options;
If the value of the filesystemio_option parameter is not SETALL (which is required), use this command to set the value:

alter system set filesystemio_options=setall scope=spfile;
Shut down the database using this command:

shutdown immediate;
Start the database using this command:

startup;
Assuming that your pluggable database is named JDEORCL, verify that the database 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 use this command to find the names of the available PDBs (ignore PDF$SEED) and substitute one name with JDEORCL in the command above):

NAME, OPEN_MODE from v$pdbs;
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.
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;

In the above command, if your database is not named JDEORCL, substitute the database name with JDEORCL.
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;
Set the recovery space using this command:

sql> ALTER SYSTEM SET db_recovery_file_dest_size=50G SCOPE=BOTH;
Check whether the temporary tablespace with name ‘TEMP’ is available by running following sequence of commands:
- Use this command to log in to sqlplus as the system user at the PDB Level:
  
  sqlplus system/<db_adm_pwd>@JDEORCL
- Run the following query to check temporary for the existence of a tablespace with name ‘TEMP’:
  SELECT TABLESPACE_NAME from DBA_TABLESPACES
  where TABLESPACE_NAME='TEMP'
- If the tablespace query does not output results that a temporary tablespace exists with name ‘TEMP’, run the following command as a single contiguous line with no returns:
  CREATE TEMPORARY TABLESPACE TEMP TEMPFILE 'jdetemp.dbf' SIZE 500m autoextend on next 10m maxsize unlimited
  If the command executes correctly, it should output results like "Tablespace Created".

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