Install JDE Platform Pack on PDB

-
With Oracle 12C, we have concept of Multitenant DB where we have a CDB and multiple PDBs
What is a PDB and CDB?
Below are the high level details for PDB and CDB, please check on Google for more information on CDB and PDBs.

A Container database (CDB) is made up of the following containers:

There is one root container which stores the Oracle supplied metadata like the PL/SQL data dictionary packages and the common users. This root container is referred to as CDB$ROOT.

One seed Pluggable Database (PDB) which is a system supplied template which can be used to create new PDB’s. This seed PDB is called PDB$SEED.

Some of the characteristics of a CDB


  • There is a separate SYSTEM and SYSAUX tablespace for the root container of the CDB and each PDB
  • Thee is only one UNDO tablespace for the entire CDB
  • There is only one set of control files and online redo logs files for the entire CDB. Individual PDB’s have their own data files (which contain the user data), but do not have distinct redo log or control files.
  • We can create on default temporary tablespace for the entire CDB or each PDB can have its own additional temporary tablespaces
  • There is single network administration files like listener.ora, tnsnames.ora, and sqlnet.ora file for an entire CDB. All of the PDBs in the CDB use the same files.
  • There is only one set of background processes shared by the root and all PDBs
  • There is a single SGA shared by all  PDB’s
  • When the CDB is shut down then all PDB’s are also automatically shut down
  • When the CDB is open then we can change the open mode of individual PDBs via the ALTER PLUGGABLE DATABASE SQL statement.


PDB is a portable collection of schemas, schema objects, and non schema objects that appears to an Oracle client as a non-CDB.

The following steps are required for installation of EnterpriseOne into pluggable database in Oracle 12cR1 and higher:

Before starting to install JDE Platform Pack the following steps are required in order Oracle Database creation scripts to work. In the below steps "jdepdb" is the PDB db we created during the Oracle DB install.


  1. Have the CDB and PDB entries in all instances of tnsnames.ora files (located in the 12C client and 12 database install paths). 
  2. Connect using SQLPlus to Oracle database issuing the "sqlplus /nolog" command. Then the SQL> prompt will appear.
  3. Connect as sysdba to Oracle Database issuing "connect / as sysdba" command
  4. Check if jdepdb database is mounted by issuing "select name, open_mode from v$pdbs;" 
  5. If the pluggable database is not mounted then issue "STARTUP MOUNT" 
  6. Open the jdepdb instance by issuing "alter pluggable database jdepdb open;"
  7. Check if the pdborcl pluggable database is open in read write status by issuing again "select name, open_mode from v$pdbs;" 
  8. Now the jdepdb pluggable database is accepting standard sql commands, but it will not be open automatically after an Oracle database service restart. In order pdborcl pluggable database to be automatically opened after the Oracle database start, we need to define a trigger to open the pluggable database. The following lines will define a trigger to open the pluggable database every time the Oracle database service is started (the trigger will be defined at the consolidated database level):


        create or replace trigger Sys.After_Startup after startup on database
        begin
            execute immediate 'alter pluggable database pdborcl open';
        end;
         /

Note: Please pay attention to the slash sign ("/") which is terminating long line input at the SQL prompt.

     8. After this step, you may continue to install the JDE Platform Pack in the same manner as with Oracle Database 11g.


Reference: Oracle Documentation

Comments

Post a Comment

Popular posts from this blog

Oracle Cloud Infrastructure(OCI) - Part2

-
Image
In my earlier post (OCI -Part1 ), we have gone through OCI basic details, let's dive deep more into it. Before that, we need to u nderstand the following concepts and terminology to help you get started with Oracle Cloud Infrastructure.  Note: OCI is re-branding of Bare Metal Cloud Service (BMCS) BARE METAL HOST Oracle Cloud Infrastructure provides you control of the physical host (“bare metal”) machine. Bare metal compute instances run directly on bare metal servers without a hypervisor. When you provision a bare metal compute instance, you maintain sole control of the physical CPU, memory, and network interface card (NIC). You can configure and utilize the full capabilities of each physical machine as if it were hardware running in your own data center. You do not share the physical machine with any other tenants. REGIONS AND AVAILABILITY DOMAINS  Oracle Cloud Infrastructure is physically hosted in regions and availability domains. A region is a localized geographic area, an...
Read more

Script to display the SQL text for a specific SQL_ID

-
--> Purpose:    Script to display the SQL text  for a specific SQL_ID. -->             It returns the SQL_TEXT. --> Parameters: sql_id --> To Run:     @sqltext.sql sql_id --> Example:    @sqltext.sql 27b3qfm5x89xn --> --> Copyright 2020@The Ultimate SQL Tuning Formula set echo off set define '&' set verify off define _sql_id=&1 set verify off set feedback off set linesize 200 set heading on set termout on col sqltext format a100 word_wrapped select  sql_text as sqltext from gv$sqltext where sql_id = '&_sql_id' order by piece; **************************************************************************************** --> Purpose:    Script to display the SQL text  for a specific SQL_ID. -->             It returns the SQL_TEXT. --> Caution:  ...
Read more

How to Change Your EnterpriseOne Environment Color

-
Image
Sometimes users start working and then forget which EnterpriseOne environment they are logged into. Can you tell which environment you are logged into? Luckily, there is a new UDC that allows you to change your EnterpriseOne environment color. You can now set up environments to be color-coded for when you need a clear visual distinction as to which environment you are logged into. This enables you to quickly identify the non-production environments by color. The new UDC is 98/CO and is available in EnterpriseOne Tools Release 9.2.4 with Applications Release 9.1 and 9.2. The image below shows the default EnterpriseOne environment color. However, you can easily change the color to reflect different environments. For example, DV could be red, PY could be green, and PD could be yellow, as shown below. To do so, just add a new row in the User Defined Codes section, enter the EnterpriseOne environment name and the HEX value of the color you want the environment to be, and ...
Read more