Wednesday, November 6, 2019

Oracle Database 19c (19.3) Now Certified With EBS 12.2


https://blogs.oracle.com/ebstech/oracle-database-193-now-certified-with-ebs-122

Elke Phelps
PRODUCT MANAGEMENT DIRECTOR
[Contributing Author: Nirzari Raichura]
[04-Nov-2019 Update:  Corrected minimum requirements for RHEL as reflected in certification information in MOS and per MOS Note 2605726.1]

We are pleased to announce that Oracle Database 19.3 is now certified with Oracle E-Business Suite Release 12.2 on-premises. As an Oracle E-Business Suite 12.2 on-premises customer, you may now start planning your upgrade to Oracle Database 19c.
Database support implications may also be reviewed in this database patching and support article.  The latest support information for Oracle E-Business Suite Release 12.2 and Release 12.1 with Database 12.1.0.2 or Database 11.2.0.4 may be reviewed in this extended support article.

What's New for EBS with Oracle Database 19c

There are several mandatory architecture updates when you upgrade your Oracle E-Business Suite database to Oracle Database 19c.  The following is a summary of the key required architectural changes:

Container Database (CDB) Architecture

With the Database 19c certification EBS 12.2 on-premises databases are now certified with the CDB architecture (multitenant architecture).
As part of the upgrade to Database 19c, you will convert your EBS database to the CDB architecture with a single pluggable database (PDB). The steps required to perform the conversion to the CDB architecture are provided in the following document:
It is important for you to pay particular attention to the following points:
  • A CDB with one PDB (single tenant) is currently the only certified deployment for Oracle E-Business Suite with Database 19c.
  • A CDB with multiple PDBs (multitenant) is not currently certified for Oracle E-Business Suite.
  • A non-CDB architecture is not planned to be certified or supported for EBS with Database 19c. 

PL/SQL File Input/Output Directories

With Database 19c, the UTL_FILE_DIR database initialization parameter has been desupported. As part of the upgrade to Database 19c, you must migrate all UTL_FILE_DIR database initialization parameters to database directory objects.  EBS development has created a utility to migrate and manage your defined PL/SQL file input/output directories. For more information, refer to the following document:

What is Included in this Announcement?

1. Certified Platforms

The Certified Platforms list includes items that have been explicitly certified by EBS development.
Linux x86-64
  • Oracle Linux 7.4 Update 4 (7.4) or later
  • Red Hat Enterprise Linux 7.5 Update 5 (7.5) or later
  • SUSE Linux Enterprise Server 12 SP3 or later
Oracle Solaris (SPARC systems, 64-bit)
  • Oracle Solaris 11.4 or later
  • Oracle Solaris 11.3  or later

2. Supported Database Features and Options

The Supported Database Features and Options list includes items that are supported but not explicitly certified by EBS. Our general policy is that the Oracle Database generic documentation applies to these features and options, even if we haven't certified them specifically.
  • Advanced Compression
  • Database In-Memory
  • Database Partitioning
  • Native PL/SQL Compilation
  • Oracle Application Express (APEX)
  • SecureFiles
  • Virtual Private Database (VPD)*
*Note: When deploying VPD there are special considerations with Oracle E-Business Suite 12.2 and edition-based redefinition. 

3. Certified Database Features and Options

The Certified Database Features and Options list includes items that have been explicitly certified by EBS development.
  • Container Database (CDB) Architecture (multitenant architecture) with a single Pluggable Database (PDB) (single tenant)
  • Export/Import
  • Oracle Real Application Clusters (Oracle RAC)
  • Transparent Data Encryption (TDE) with Online Tablespace Encryption Conversion

4. Certified Integrations

The Certified Integrations list includes items that have been explicitly certified by EBS development. 
  • Oracle E-Business Suite 12.2 with Database 19c Integrated with Oracle Access Manager for Single Sign-on

What Remains to be Certified?

This section includes all items that are pending certification.  You may subscribe to this blog for the latest in certification announcements. 

1. Pending Certifications - Deployments

The Pending Certifications - Deployments list includes items that require explicit certification and that we currently plan to certify in the future. 
  • Oracle E-Business Suite Integrated SOA Gateway (ISG) is not currently certified with E-Business Suite Release 12.2 on Database 19c. If you are using or planning to use ISG, you should not perform an upgrade to Database 19c until the certification of Oracle E-Business Suite 12.2 with Database 19c for ISG is announced.
  • Oracle Application Management Pack for Oracle E-Business Suite, Release 13.1.1.1.0 with Oracle Enterprise Manager 13c Release 3

2. Pending Certifications - Platforms

The Pending Certifications - Platforms list includes items that require explicit certification and that we currently plan to certify in the future. 
  • IBM AIX on Power Systems
  • HP-UX Itanium
  • IBM:  Linux on System z
  • Microsoft Windows x64 (64-bit)

3. Pending Certifications - Database Features and Options

The Pending Certifications - Database Features and Options list includes items that require explicit certification and that we currently plan to certify in the future. 
  • Active Data Guard
  • Data Guard
  • Data Masking
  • Database Vault
  • Oracle Label Security (OLS)
  • Transportable Database and Transportable Tablespaces for data migration processes

4. Pending Certifications - Integrations

The Pending Certifications - Integrations list includes items that require explicit certification and that we currently plan to certify in the future. 
  • EBS 12.2 with Database 19c Integrated with GoldenGate
References

Related Articles

Join the discussion

Comments ( 31 )
at No comments:

Using Fast Online Conversion to Enable Transparent Data Encryption (TDE) for Oracle E-Business Suite (Doc ID 2559570.1)

This document describes how to enable TDE TablespaceOnline Encryption of Oracle E-Business Suite Release 12.1 and 12.2 databases.
The most current version of this document can be obtained from My Oracle Support Knowledge Document 2559570.1.

Section 1: Introduction

This document summarizes the procedure to enable TDE Tablespace Online Encryption for an Oracle E-Business Suite database. It is referred to as the Fast online Conversion method to convert existing clear data to TDE encrypted tablespaces. In order to use this feature, Oracle E-Business Suite database does not require downtime. As the encryption is transparent to the application, code does not have to be rewritten, and existing SQL statements work as they are. Transparent also means that any authorized database session can read the encrypted data without any problem: the encryption only applies to data-at-rest, i.e. the database datafiles and any backups of them.
This process is the recommended Oracle Maximum Availability Architecture best practice for converting to TDE with no downtime and least complexity. It supersedes previous methods for converting to TDE, as described in the References documents.

Section 2: Prerequisites

  • Understand TDE implications and restrictions and develop a process for maintaining wallets and keys. Refer to the Oracle Database Advanced Security Administrator's Guide 19.0.0) for further details
  • Ensure the COMPATIBLE database parameter is set to the appropriate database version,19.0.0
  • Take a full backup of your database before starting the procedure

Section 3: TDE Online Datafile Encryption Restrictions

The following restrictions apply to implementing Tablespace Encryption using Fast Online Conversion:
  • TEMP tablespaces cannot be encrypted.
  • External Large Objects (BFILEs) cannot be encrypted using TDE tablespace encryption. because these files reside outside the database.

Section 4: Procedure to Perform TDE Tablespace Online Encryption

This section describes the steps needed to perform TDE Tablespace Online Encryption for an Oracle E-Business Suite database.
  1. Source your Oracle E-Business Suite Database Oracle Home.
  2. Create the required wallet by specifying the wallet location in the pfile or spfile file:

    Refer to "Configure the Software Keystore Location and Type" in the Oracle Database Advanced Security Guide 19c for more information.

    1. Create the corresponding directory manually:
      $ mkdir -p $ORACLE_BASE/admin/<db_unique_name>/wallet
    2. Add the following entry to the parameter file:
      alter system set WALLET_ROOT='$ORACLE_BASE/admin/<db_unique_name>/wallet' scope=spfile sid='*';

Restart the database
    3. Set the TDE_CONFIGURATION dynamic initialization parameter to specify the keystore type.

      ALTER SYSTEM SET TDE_CONFIGURATION="KEYSTORE_CONFIGURATION=FILE" scope=both;
    4. Restart the database.
    5. Check the wallet location and status:
      $ sqlplus / as sysdba;
      SQL>select * from V$encryption_wallet;
  3. Set the master encryption key from SQL*Plus:
    Source the container database environment:
    $ sqlplus / as sysdba;

    ADMINISTER KEY MANAGEMENT CREATE KEYSTORE 'keystore_location' IDENTIFIED BY software_keystore_password;
ADMINISTER KEY MANAGEMENT SET KEYSTORE OPEN IDENTIFIED BY software_keystore_password;
ADMINISTER KEY MANAGEMENT SET KEY IDENTIFIED BY software_keystore_password WITH BACKUP;
Connect to PDB <PDB_NAME> 
alter session set container="<PDB_NAME>";
ADMINISTER KEY MANAGEMENT SET KEYSTORE OPEN IDENTIFIED BY software_keystore_password;
ADMINISTER KEY MANAGEMENT SET KEY IDENTIFIED BY software_keystore_password WITH BACKUP;
To create an Auto-Login or a Local Auto-Login Software Keystore:
Source the container database environment 
ADMINISTER KEY MANAGEMENT CREATE [LOCAL] AUTO_LOGIN KEYSTORE FROM   KEYSTORE 'keystore_location' IDENTIFIED BY software_keystore_password;

    Note: The keystore location is $ORACLE_BASE/admin/<db_unique_name>/wallet/tde
  4. Bounce the database:
    SQL> shutdown normal;
    SQL> exit;
  5. Startup the database normally, ensuring that the wallet is open:
    Source the container database environment
    sqlplus "/ as sysdba"

    For Autologin    SQL> startup

    For Password based
    SQL> startup mount;
    SQL> ADMINISTER KEY MANAGEMENT SET KEYSTORE OPEN IDENTIFIED BY software_keystore_password;
    SQL> alter database open;

    Check the wallet location and status
    SQL> select * from V$encryption_wallet;
  6. Identify all the temporary and undo tablespaces in the CDB and PDB:
    SQL>select tablespace_name from dba_tablespaces where contents='TEMPORARY' and STATUS='ONLINE';
    SQL>select tablespace_name from dba_tablespaces where contents='UNDO' and STATUS='ONLINE';
  7. Encryption Conversions for Existing Online Tablespaces other than temp:
    Source the container database environment
    $ sqlplus / as sysdba;
    The following steps can be performed in the CDB or PDB as per your requirement:
    Connect to PDB <PDB_NAME>
    alter session set container="<PDB_NAME>";
    SQL> ALTER TABLESPACE users ENCRYPTION ONLINE USING 'AES192' ENCRYPT FILE_NAME_CONVERT = ('users1.dbf', 'users1_enc.dbf', 'users2.dbf', 'users2_enc.dbf');

    Repeat the command above, as required for the other tablespaces that you wish to encrypt. If any tablespace datafile was missed,you can complete the conversion by performing the steps as documented in     Finishing an Interrupted Online Encryption Conversion in the Oracle Database Advanced Security Guide 19c.
    Note: Ensure that there is sufficient space in the file system. If your datafile is 5Gb then 6Gb free space is required to perform the encryption of that datafile.

  8. Check the status of tablespace encryption by connecting to SQL*Plus / as sysdba and running the query shown:
    $ sqlplus / as sysdba
    The following steps can be performed in the CDB or PDB as per your requirement:
    Connect to PDB <PDB_NAME>
    alter session set container="<PDB_NAME>";
    SQL>select tablespace_name, encrypted from dba_tablespaces;

Section 5: Procedure for Decryption

Online Tablespace Encryption is a reversible procedure. This section lists the steps you can use to decrypt an encrypted database.
  1. Source the Oracle E-Business Suite Container Database Oracle Home.
  2. Decrypt the datafiles by running below "sqlplus / as sysdba"
    The following steps can be performed in the CDB or PDB as per your requirement:
    Connect to PDB <PDB_NAME>
    alter session set container="<PDB_NAME>";
    SQL> ALTER TABLESPACE users ENCRYPTION ONLINE DECRYPT FILE_NAME_CONVERT = ('users1_enc.dbf', 'users1.dbf', 'users2_enc.dbf', 'users2.dbf');Repeat the command above, as required for the other tablespaces that you wish to decrypt.
    If any tablespace datafile was missed,you can complete the conversion by performing the steps as documented in     Finishing an Interrupted Online Encryption Conversion in the Oracle Database Advanced Security Guide 19c.
  3. Check the status of encryption using the query in Step 8 above. It should show the tablespaces as NO for ENCRYPTED COLUMN.
  4. Close the wallet
  5. Shut down the container or pluggable database from SQL*Plus:
    Source the container database environment or PDB that you want to stop:
    export ORACLE_PDB_SID="<PDB_NAME>"
    $ sqlplus / as sysdba
    SQL>shutdown
  6. Start up the container or pluggable database from SQL*Plus:
    Source the container database environment or PDB that you want to start: set below
    export ORACLE_PDB_SID="PDB_NAME"
    $ sqlplus / as sysdba
    SQL>startup

References

The following My Oracle Support knowledge documents describe earlier methods for converting Oracle E-Business Suite databases to use TDE:
  • Document 828229.1, Using TDE Tablespace Encryption with Oracle E-Business Suite Release 12
  • Document 1584458.1, Using TDE Tablespace Encryption with Oracle E-Business Suite Release 12 (Database 12c)
  • Document 1585296.1, Using TDE Tablespace Encryption with Oracle E-Business Suite Release 12.2

Change Record

at No comments:
Subscribe to: Posts (Atom)

Database Options/Management Packs Usage Reporting for Oracle Databases 11.2 and later (Doc ID 1317265.1)

  Database Options/Management Packs Usage Report You can determine whether an option is currently in use in a database by running options_pa...