Scribd
Upload
35 views18 pages

4 - Section 6 Create A Database Instance On The Oracle Cloud Infrastructure DB System

This document provides detailed steps for creating a Database Instance on the Oracle Cloud Infrastructure (OCI) DB System, including logging in, configuring various settings such as storage, network, and database options, and creating administrator credentials. It also outlines the process for deleting a dummy pluggable database and validating the time zone settings. Finally, it emphasizes the importance of applying relevant patches to the OCI DB System instance post-creation.

Uploaded by

Kishore Adikar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
35 views18 pages

4 - Section 6 Create A Database Instance On The Oracle Cloud Infrastructure DB System

This document provides detailed steps for creating a Database Instance on the Oracle Cloud Infrastructure (OCI) DB System, including logging in, configuring various settings such as storage, network, and database options, and creating administrator credentials. It also outlines the process for deleting a dummy pluggable database and validating the time zone settings. Finally, it emphasizes the importance of applying relevant patches to the OCI DB System instance post-creation.

Uploaded by

Kishore Adikar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 18

Section 6: Create a Database Instance on the Oracle Cloud Infrastructure DB

System

Perform the steps in this section to create an OCI DB System instance.


Ensure that the service name matches the database name that you want to
keep. For example, use the database instance name of your on-premises
instance.

1. Log in to Oracle Cloud My Services using your Oracle Cloud credentials.

2. Select the menu at the upper left corner of the page. Then under
Oracle Database, select Oracle Base Database Service to display
the Database Cloud Service Console.

3. Click Create DB System to create a DB system with the values


indicated as follows. Refer to Creating a DB System for more details on
each of the fields:

a. Select a compartment: By default, the DB system is created in


your current compartment, and you can use the network
resources in that compartment.
b. Name your DB system: A non-unique, display name for the DB
system. An Oracle Cloud Identifier (OCID) uniquely identifies the
DB system.
c. Select an availability domain: The availability domain in
which the DB system resides.

d. Select a shape type: The shape type you select sets the
default shape and filters the shape options in the next
field. Select "Virtual Machine".
e. Configure Shape: The shape determines the type of DB system
created and the resources allocated to the system. To specify a
shape other than the default, click Change Shape, and select an
available shape from the list. The recommendation for Oracle E-
Business Suite is to use a minimum of VM.Standard2.x shape for
the OCI DB System.

f. Configure Storage:
i. Choose Storage Management Software: Select Oracle
Grid Infrastructure to use Oracle Automatic Storage
Management (ASM), which is recommended for production
workloads.
ii. Available storage (GB): The amount of Block Storage in
GB to allocate to the DB system. Available storage can be
scaled up or down as needed after provisioning your DB
system.

g. Configure the DB system:


i. Total node count: The number of nodes in the DB
system, which depends on the shape you select. For DB
systems, you can specify either one or two nodes, except
for VM.Standard2.1 and VM.Standard1.1, which are single-
node DB systems.
ii. Oracle Database software edition: The database
edition supported by the DB system. Choose Enterprise
Edition, Enterprise Edition High Performance, or Enterprise
Edition Extreme Performance, as appropriate.

Note: The Oracle OLAP, Partitioning, and Spatial features


required by Oracle E-Business Suite are automatically
installed when you choose Enterprise Edition High
Performance or Enterprise Edition Extreme Performance.

When deploying a 1-Node DB System, you can choose


"Enterprise Edition" as the Oracle Database software
edition. However, if you do so you then you must manually
enable OLAP, Partitioning, and Spatial features, using the
following instructions:

 Oracle OLAP and Partitioning: See Enabling and


Disabling Database Options After Installation in
the Oracle Database Installation Guide for Linux.
 Oracle Spatial: See Document 270588.1, Steps for
Manual Installation / Verification of Spatial 10g /
11g /12c / 19c.

iii. Total Storage (GB): Read-only field showing the total


Block Storage in GB used by the DB system. The amount of
available storage you selected determines this value.
Oracle charges for the total storage used.

h. Add SSH keys: The public key portion of each key pair you want
to use for SSH access to the DB system. You can browse or drag
and drop .pub files or paste in individual public keys. To paste
multiple keys, click + Another SSH Key, and supply a single key
for each entry.
i. Choose a license type: The type of license you want to use for
the DB system. Your choice affects metering for billing.
i. License Included means the cost of this Oracle Cloud
Infrastructure Database service resource will include both
the Oracle Database software licenses and the service.
ii. Bring Your Own License (BYOL) means you will use your
organization's Oracle Database software licenses for
this Oracle Cloud Infrastructure Database service resource.
See Bring Your Own License for more information.

j. Specify the network information.


i. Virtual cloud network: The VCN in which to create the
DB system. Click Change Compartment to select a VCN in a
different compartment.
ii. Client Subnet: The subnet to which the DB system should
attach. For 1- and 2-node RAC DB systems: Do not use a
subnet that overlaps with 192.168.16.16/28, which is used
by the Oracle Clusterware private interconnect on the
database instance. Specifying an overlapping subnet
causes the private interconnect to malfunction.
iii. Hostname prefix: Your choice of hostname for the bare
metal or DB system. The hostname must begin with an
alphabetic character, and can contain only alphanumeric
characters and hyphens (-). The maximum number of
characters allowed for bare metal and DB systems is 16.
iv. Host domain name: The domain name for the DB system.
If the selected subnet uses the Oracle-provided Internet
and VCN Resolver for DNS name resolution, then this field
displays the domain name for the subnet, and it can't be
changed. Otherwise, you can provide your choice of a
domain name. Hyphens (-) are not permitted.
v. Host and domain URL: Combines the host and domain
names to display the fully qualified domain name (FQDN)
for the database. The maximum length is 64 characters.

k. Click Show Advanced Options to specify the time zone for


your DB system.

Note: The DB system time zone (operating system time zone)


should be set thoughtfully, based on your on-premises settings
derived in Section 5, step 6 of this document, as well as on the
guidance provided in "Section 5: Setting the Time Zone Manually
When Migrating to Oracle Cloud Infrastructure" in Document
2774525.1, Setting Oracle E-Business Suite Time Zones When
Migrating to Oracle Cloud Infrastructure.
l. Database Name: The name for the database. The database
name must begin with an alphabetic character and can contain a
maximum of eight alphanumeric characters. Special characters
are not permitted.

m. Database image: This controls the version of the initial


database created on the DB system. By default, the latest
available Oracle Database version is selected. You can also
choose an older Oracle Database version, or choose a
customized database software image that you have previously
created in your current region with your choice of updates and
one-off (interim) patches. See Oracle Database Software
Images for information on creating and working with database
software images. Select Oracle Database 19c.

n. PDB name: (Required) The name of the default pluggable


database (PDB). As part of an Oracle Database 19c deployment,
a PDB name is mandatory, but the actual pluggable database
created at this point will not be used by Oracle E-Business Suite.
Therefore, enter a dummy value such as "DUMMYPDB." It will be
removed later in this section.

o. Create administrator credentials: Create a database


administrator, SYS user, with the password you supply.
i. Username: SYS
ii. Password: A strong password for SYS, SYSTEM, TDE
wallet, and PDB administrator. The password must be 9 to
30 characters and contain at least two uppercase, two
lowercase, two numeric, and two special characters. The
special characters must be _, #, or -. The password must
not contain the username (SYS, SYSTEM, and so on) or the
word "oracle" either in forward or reversed order and
regardless of casing.
iii. Confirm password: Re-enter the SYS password you
specified.

p. Configure database backups: Optionally, specify the settings


for backing up the database to Object Storage.

q. Click on Show Advanced Options to specify advanced options


for the initial database:
i. Character Set: The character set for the database. This
value must match the value of the on-premises Oracle E-
Business Suite database.
ii. National Character Set: The national character set for
the database. This value must match the value of the on-
premises Oracle E-Business Suite database.

r. Click Create DB System.

4. Wait for service creation, and note the public and private IP address of
the services created. These values are needed later. This process may
take some time.

The ORACLE_HOME is located


at /u01/app/oracle/product/19.0.0.0/dbhome_1 on both nodes. The storage is
ASM.

5. Ensure the TZ environment variable is not set in the current shell using
unset TZ on the command line and remove this entry from any
environment files sourced to set the environment when starting the
database or TNS listener. You must use the OS time zone settings (not
TZ) for the database time zone.

6. During the 19c service creation, you entered a dummy value for the
PDB name "DUMMYPDB". As this pluggable database is not needed,
perform the following steps to delete the PDB using the OCI Console:

a. Open the navigation menu. Select Oracle Database, then


select Oracle Base Database Service.

b. Select your Compartment. A list of DB systems is displayed.

c. In the list of databases, find the database containing the PDB you
want to delete. Click the database name to display the database
details.

d. In the Resources section of the page, click Pluggable


Databases.

e. In the list of PDBs, find the PDB you want to delete:


"DUMMYPDB". Click the PDB name to display the PDB details.

f. From the PDB details page, click More actions, and then
click Delete.

g. In the Delete PDB dialog, click Delete PDB to confirm.

7. Run the following query to validate the time zone on the Oracle Cloud
Infrastructure database tier:
$ sqlplus / as sysdba
SQL> select dbtimezone from dual;

Note: The time zone value returned by the above query on the Oracle
Cloud Infrastructure database tier must match the time zone settings
on the on-premises database tier, as described in Section 5.

8. Refer to Appendix A: Database Patches to verify the OCI DB System


PSU/Bundle level and apply the relevant Oracle E-Business Suite
patches listed in the appendix to your OCI DB System instance. For a 2-
Node DB System, the patches must be applied on both nodes,
individually. Post-patch steps should not be executed at this point.
They will be run after the database is restored.
select * from nls_database_parameters where parameter in ('LS_LANGUAGE', 'NLS_TERRITORY',
'NLS_CHARACTERSET', 'NLS_NCHAR_CHARACTERSET');

SQL> select dbtimezone from dual;

DBTIME

------

+00:00

select name from v$database;

NAME

---------

UATCDB
Unable to find 19.16, click Custom Database Software images
First we need to create 19.16 home, open an duplicate session
Select the image while creation of the database

oraCA##1c2O8_4A
Create DB System
Take a backup of spfile

create pfile from spfile;

initUATCDB.ora

You might also like