Oracle DBA Quick Notes

Benefits of Cloning PDB in Oracle Container Database

2024-05-12T21:42:00.005+05:30

Benefits of Cloning PDB in Oracle Container Database

1. Reduced Downtime

+ Cloning PDB allows administrators to create a copy of the database while the original one remains fully operational.

+ This eliminates the need for downtime during the cloning process, ensuring continuous access to data and minimal disruption to business operations.

2. Testing and Development

+ Cloning PDB provides a safe environment for testing new applications, making changes, and running experiments without impacting the production database.

+ Developers can work on clones of the database, ensuring that any changes made will not affect the live system until they are thoroughly tested and approved.

3. Backup and Recovery

+ Cloning PDB serves as a reliable backup strategy, allowing administrators to quickly restore data in case of any database failures.

+ By creating clones regularly, organizations can ensure they have up-to-date backups that can be easily recovered in times of need.

4. Resource Optimization

+ Cloning PDB enables efficient utilization of resources by allowing administrators to create multiple copies of the database without duplicating data.

+ This helps in resource allocation, capacity planning, and overall optimization of database performance.

5. Scalability

+ With Cloning PDB, organizations can easily scale their databases by cloning existing PDBs and adding them to the Oracle Container Database.

+ This flexibility in scaling up or down based on business requirements ensures optimal performance and resource management.

Conclusion

Understanding the benefits of Cloning PDB in Oracle Container Database is crucial for database administrators seeking to improve efficiency and productivity. By leveraging the advantages of this process, organizations can enhance data management, reduce downtime, and optimize resource allocation. Embracing Cloning PDB as a part of database administration practices can lead to a more resilient and agile IT infrastructure.

Why is Cloning PDB important in database management?

2024-05-12T21:36:00.005+05:30

Cloning Pluggable Databases (PDBs) within an Oracle Container Database (CDB) is a crucial aspect of database management that offers numerous benefits and plays a pivotal role in ensuring smooth operations and disaster recovery processes. Let's delve deeper into why cloning PDB is essential in the realm of database management.

1. Facilitates testing and development

Cloning PDB allows for the creation of identical copies of a database, providing a safe environment for testing new applications or implementing changes without impacting the production database.
Development teams can work on cloned PDBs to test upgrades, patches, or new functionalities before deploying them to the live environment, ensuring minimal disruptions and errors.

2. Streamlines disaster recovery

In the event of a database failure or data corruption, cloned PDBs serve as valuable backups that can be quickly activated to restore critical information and minimize downtime.
By regularly cloning PDBs and keeping them updated, organizations can enhance their disaster recovery strategies and ensure business continuity in the face of unexpected disasters.

3. Enhances scalability and flexibility

Cloning PDBs enables organizations to easily scale their database infrastructure by creating additional copies of existing databases to cater to increased workload demands.
With cloned PDBs, enterprises have the flexibility to quickly provision new databases for specific projects or departments, optimizing resource allocation and improving efficiency.

4. Optimizes resource utilization

By cloning PDBs instead of creating new databases from scratch, organizations can save time and resources by leveraging existing configurations, data, and structures.
This efficient utilization of resources not only reduces costs but also enhances productivity by eliminating repetitive setup tasks and ensuring consistency across databases.

In conclusion,

Cloning PDB in Oracle Container Database is a valuable practice that offers a myriad of benefits, including facilitating testing and development, streamlining disaster recovery, enhancing scalability and flexibility, and optimizing resource utilization. By incorporating cloning PDB into their database management strategies, organizations can improve operational efficiency, mitigate risks, and bolster their overall resilience in the face of challenges. Embracing this practice is not just a best practice but a necessity in the ever-evolving landscape of database management.

What is Cloning PDB in Oracle Container Database?

2024-05-12T21:35:00.000+05:30

What is Cloning PDB in Oracle Container Database?

Cloning Pluggable Database (PDB) in an Oracle Container Database (CDB) involves creating an identical copy of a specific PDB within the same CDB or on a different CDB. This process allows for easy replication of data, testing of changes, and backup purposes without affecting the original database. Let's dive into the details of cloning PDB in Oracle Container Database:

Benefits of Cloning PDB

Facilitates Testing: Cloning a PDB enables developers to test new applications or features without impacting the production environment.
Disaster Recovery: In case of data loss or corruption, a cloned PDB serves as a backup to quickly restore the database.
Resource Optimization: Cloning helps in distributing workloads across multiple PDBs, optimizing resource utilization.
Time Efficiency: Instead of setting up a new database from scratch, cloning saves time by replicating an existing PDB.

Steps to Clone PDB

Connect to CDB: Log in to the CDB as a privileged user using SQL Developer or SQL*Plus.
Ensure Resource Availability: Check for sufficient space, memory, and CPU resources for the cloning process.
Create a New PDB: Use the CREATE PLUGGABLE DATABASE command to create a new PDB where the cloned data will reside.
Open Source PDB in Read-Only Mode: Ensure the source PDB is in read-only mode to avoid data inconsistency during cloning.
Clone PDB: Execute the CREATE PLUGGABLE DATABASE...FROM command to clone the source PDB to the target PDB.
Modify the Cloned PDB: Make any necessary alterations to the cloned PDB configuration, such as tablespace allocation or user roles.

Best Practices for Cloning PDB

Regular Backups: Before initiating the cloning process, ensure regular backups of the source PDB to avoid data loss.
Monitor Cloning Progress: Keep track of the cloning progress and resolve any errors or issues promptly.
Test Cloned PDB: After cloning, perform thorough testing to ensure data integrity and application functionality.
Security Measures: Implement security measures such as encryption and access controls for the cloned PDB.

Conclusion

Cloning PDB in Oracle Container Database is a valuable tool for database administrators and developers to streamline processes, enhance disaster recovery capabilities, and improve resource management. By following the outlined steps and best practices, users can effectively clone PDBs while maintaining data integrity and security. Embrace the power of cloning to unlock new possibilities in your Oracle database management journey!

Configure Quorum Disk in Exadata

2020-09-04T11:25:00.000+05:30

In last article[click here] - we learnt how to remove quorum disk from the Exadata system, now here we would see it we add and configure that.

Before we are adding quorum disk configuration in the system, you need to have IB switches interface names, ASM binary owner and group handy as that is required to create the config.

[root@exa01dbadm01 oracle.SupportTools]# /opt/oracle.SupportTools/quorumdiskmgr --create --config --owner=oragrid --group=asmadmin --network-iface-list="ib0, ib1"
[Info] Successfully created iface exadata_ib0 with iface.net_ifacename ib0
[Info] Successfully created iface exadata_ib1 with iface.net_ifacename ib1
[Success] Successfully created quorum disk configurations

[root@exa01dbadm01 oracle.SupportTools]#

Do the same as above on node2 as well.

[root@exa01dbadm02 oracle.SupportTools]# /opt/oracle.SupportTools/quorumdiskmgr --create --config --owner=oragrid --group=asmadmin --network-iface-list="ib0, ib1"
[Info] Successfully created iface exadata_ib0 with iface.net_ifacename ib0
[Info] Successfully created iface exadata_ib1 with iface.net_ifacename ib1
[Success] Successfully created quorum disk configurations

[root@exa01dbadm02 oracle.SupportTools]#

Check if the quoum disk configuration is created as below from node1 and node2.

[root@exa01dbadm01 oracle.SupportTools]# /opt/oracle.SupportTools/quorumdiskmgr --list --config
Owner: oragrid
Group: asmadmin
ifaces: exadata_ib1 exadata_ib0
Initiatior name: iqn.1988-12.com.oracle:192.168.10.1

[root@exa01dbadm01 oracle.SupportTools]#

[root@exa01dbadm02 oracle.SupportTools]# /opt/oracle.SupportTools/quorumdiskmgr --list --config
Owner: oragrid
Group: asmadmin
ifaces: exadata_ib1 exadata_ib0
Initiatior name: iqn.1988-12.com.oracle:192.168.10.3

[root@exa01dbadm02 oracle.SupportTools]#

Now, create quorum disk target for DATAC1 diskgroup which is visible to both compute nodes, before it you need to identify IB interface IPs of both nodes as that is required here.

Run the command on node1 and node2.

[root@exa01dbadm01 oracle.SupportTools]# /opt/oracle.SupportTools/quorumdiskmgr --create --target --asm-disk-group=datac1 --visible-to="192.168.10.1, 192.168.10.2, 192.168.10.3, 192.168.10.4"
[Success] Created logical volume /dev/VGExaDb/LVDbVdexa01dbadm01DATAC1.
[Success] Created backstore QD_DATAC1_exa01dbadm01.
[Success] Created target iqn.2015-05.com.oracle:qd--datac1--exa01dbadm01.

[root@exa01dbadm01 oracle.SupportTools]#

[root@exa01dbadm02 oracle.SupportTools]# /opt/oracle.SupportTools/quorumdiskmgr --create --target --asm-disk-group=datac1 --visible-to="192.168.10.1, 192.168.10.2, 192.168.10.3, 192.168.10.4"
[Success] Created logical volume /dev/VGExaDb/LVDbVdexa01dbadm02DATAC1.
[Success] Created backstore QD_DATAC1_exa01dbadm02.
[Success] Created target iqn.2015-05.com.oracle:qd--datac1--exa01dbadm02.

[root@exa01dbadm02 oracle.SupportTools]#

Now you can list the quorum disk targets on node1 and node2 as below to validate.

[root@exa01dbadm01 oracle.SupportTools]# /opt/oracle.SupportTools/quorumdiskmgr --list --target
Name: iqn.2015-05.com.oracle:qd--datac1--exa01dbadm01
Host name: exa01dbadm01
ASM disk group name: DATAC1
Visible to: iqn.1988-12.com.oracle:192.168.10.1, iqn.1988-12.com.oracle:192.168.10.2, iqn.1988-12.com.oracle:192.168.10.3, iqn.1988-12.com.oracle:192.168.10.4
Discovered by:


[root@exa01dbadm01 oracle.SupportTools]#

[root@exa01dbadm02 oracle.SupportTools]# /opt/oracle.SupportTools/quorumdiskmgr --list --target
Name: iqn.2015-05.com.oracle:qd--datac1--exa01dbadm02
Host name: exa01dbadm02
ASM disk group name: DATAC1
Visible to: iqn.1988-12.com.oracle:192.168.10.1, iqn.1988-12.com.oracle:192.168.10.2, iqn.1988-12.com.oracle:192.168.10.3, iqn.1988-12.com.oracle:192.168.10.4
Discovered by:


[root@exa01dbadm02 oracle.SupportTools]#

Create quorum disk device as below on node1 and node2.

[root@exa01dbadm01 oracle.SupportTools]# /opt/oracle.SupportTools/quorumdiskmgr --create --device --target-ip-list="192.168.10.1, 192.168.10.2, 192.168.10.3, 192.168.10.4"
[Success] Successfully created all device(s) from target(s) on machine with IP address 192.168.10.1

[Success] Successfully created all device(s) from target(s) on machine with IP address 192.168.10.2

[Success] Successfully created all device(s) from target(s) on machine with IP address 192.168.10.3

[Success] Successfully created all device(s) from target(s) on machine with IP address 192.168.10.4

[root@exa01dbadm01 oracle.SupportTools]#

[root@exa01dbadm02 oracle.SupportTools]# /opt/oracle.SupportTools/quorumdiskmgr --create --device --target-ip-list="192.168.10.1, 192.168.10.2, 192.168.10.3, 192.168.10.4"
[Success] Successfully created all device(s) from target(s) on machine with IP address 192.168.10.1

[Success] Successfully created all device(s) from target(s) on machine with IP address 192.168.10.2

[Success] Successfully created all device(s) from target(s) on machine with IP address 192.168.10.3

[Success] Successfully created all device(s) from target(s) on machine with IP address 192.168.10.4

[root@exa01dbadm02 oracle.SupportTools]#

Now you can list the quorum disk device on node1 and node2 to validate.

[root@exa01dbadm01 oracle.SupportTools]# /opt/oracle.SupportTools/quorumdiskmgr --list --device
Device path: /dev/exadata_quorum/QD_DATAC1_exa01dbadm01
Host name: exa01dbadm01
ASM disk group name: DATAC1
Size: 128 MB

Device path: /dev/exadata_quorum/QD_DATAC1_exa01dbadm02
Host name: exa01dbadm02
ASM disk group name: DATAC1
Size: 128 MB


[root@exa01dbadm01 oracle.SupportTools]#

[root@exa01dbadm02 oracle.SupportTools]# /opt/oracle.SupportTools/quorumdiskmgr --list --device
Device path: /dev/exadata_quorum/QD_DATAC1_exa01dbadm02
Host name: exa01dbadm02
ASM disk group name: DATAC1
Size: 128 MB

Device path: /dev/exadata_quorum/QD_DATAC1_exa01dbadm01
Host name: exa01dbadm01
ASM disk group name: DATAC1
Size: 128 MB


[root@exa01dbadm02 oracle.SupportTools]#

Now, check in the ASM instance if quorum disk devices are visible to ASM to be used for the DATAC1 diskgroup as below, we can see that quorum disk devices are available as CANDIDATE disks that we can add in to the diskgroup.

SQL> l
  1* SELECT inst_id, label, path, mode_status, header_status FROM gv$asm_disk WHERE path LIKE '/dev/exadata_quorum/%'
SQL> /

   INST_ID LABEL                           PATH                                                                   MODE_ST HEADER_STATU
---------- ------------------------------- ---------------------------------------------------------------------- ------- ------------
         1 QD_DATAC1_exa01dbadm02      /dev/exadata_quorum/QD_DATAC1_exa01dbadm02                         ONLINE  CANDIDATE
         1 QD_DATAC1_exa01dbadm01      /dev/exadata_quorum/QD_DATAC1_exa01dbadm01                         ONLINE  CANDIDATE
         2 QD_DATAC1_exa01dbadm02      /dev/exadata_quorum/QD_DATAC1_exa01dbadm02                         ONLINE  CANDIDATE
         2 QD_DATAC1_exa01dbadm01      /dev/exadata_quorum/QD_DATAC1_exa01dbadm01                         ONLINE  CANDIDATE

SQL>

Add the quorum devices in to the diskgroup as below.

SQL> ALTER DISKGROUP datac1 ADD QUORUM FAILGROUP exa01dbadm01 DISK '/dev/exadata_quorum/QD_DATAC1_exa01dbadm01'
QUORUM FAILGROUP exa01dbadm02 DISK '/dev/exadata_quorum/QD_DATAC1_exa01dbadm02';  2

Diskgroup altered.

SQL>

After disk addition, we can see that now these are parts of diskgroup and status is MEMBER.

SQL> SELECT inst_id, label, path, mode_status, header_status
FROM gv$asm_disk WHERE path LIKE '/dev/exadata_quorum/%';  2

   INST_ID LABEL                           PATH                                                                   MODE_ST HEADER_STATU
---------- ------------------------------- ---------------------------------------------------------------------- ------- ------------
         1 QD_DATAC1_exa01dbadm02      /dev/exadata_quorum/QD_DATAC1_exa01dbadm02                         ONLINE  MEMBER
         1 QD_DATAC1_exa01dbadm01      /dev/exadata_quorum/QD_DATAC1_exa01dbadm01                         ONLINE  MEMBER
         2 QD_DATAC1_exa01dbadm02      /dev/exadata_quorum/QD_DATAC1_exa01dbadm02                         ONLINE  MEMBER
         2 QD_DATAC1_exa01dbadm01      /dev/exadata_quorum/QD_DATAC1_exa01dbadm01                         ONLINE  MEMBER

SQL>

Finally, replaced/moved the voting disks back to DATAC1 diskgroup and five copies of files are now available.

[root@exa01dbadm02 oracle.SupportTools]# crsctl query css votedisk
##  STATE    File Universal Id                File Name Disk group
--  -----    -----------------                --------- ---------
 1. ONLINE   cf9c32d1c0c34fafbf47caa1b77821b0 (o/10.0.0.5;10.0.0.6/DATAC1_CD_02_exad02cel01) [DATAC1]
 2. ONLINE   e2e61cd646224f08bf2c4c47e719e8fd (o/10.0.0.3;10.0.0.4/DATAC1_CD_05_exad02cel02) [DATAC1]
 3. ONLINE   7691da5101a34f95bfc56c3bec4e681b (o/10.0.0.1;10.0.0.2/DATAC1_CD_03_exad02cel03) [DATAC1]
 4. ONLINE   3dea97bdc5aa4f61bf0355abe31c1361 (/dev/exadata_quorum/QD_DATAC1_exa01dbadm02) [DATAC1]
 5. ONLINE   cc5671a086eb4f38bf5c690666099d66 (/dev/exadata_quorum/QD_DATAC1_exa01dbadm01) [DATAC1]
Located 5 voting disk(s).
[root@exa01dbadm02 oracle.SupportTools]#

After CRS restart : I bounced the CRS on both nodes to check if things are coming up normally.

[root@exa01dbadm02 oracle.SupportTools]# crsctl query css votedisk
##  STATE    File Universal Id                File Name Disk group
--  -----    -----------------                --------- ---------
 1. ONLINE   cf9c32d1c0c34fafbf47caa1b77821b0 (o/10.0.0.5;10.0.0.6/DATAC1_CD_02_exad02cel01) [DATAC1]
 2. ONLINE   e2e61cd646224f08bf2c4c47e719e8fd (o/10.0.0.3;10.0.0.4/DATAC1_CD_05_exad02cel02) [DATAC1]
 3. ONLINE   7691da5101a34f95bfc56c3bec4e681b (o/10.0.0.1;10.0.0.2/DATAC1_CD_03_exad02cel03) [DATAC1]
 4. ONLINE   3dea97bdc5aa4f61bf0355abe31c1361 (/dev/exadata_quorum/QD_DATAC1_exa01dbadm02) [DATAC1]
 5. ONLINE   cc5671a086eb4f38bf5c690666099d66 (/dev/exadata_quorum/QD_DATAC1_exa01dbadm01) [DATAC1]
Located 5 voting disk(s).
[root@exa01dbadm02 oracle.SupportTools]#

Our missing quorum disk issue stands fixed here......!!

Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Cloud Infrastructure and Oracle Autonomous Database Cloud Services and new articles.

Twitter : https://twitter.com/rajsoft8899

Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/

Facebook : https://www.facebook.com/rkushawaha

Removing the Quorum Disk Configuration in Exadata

2020-08-31T09:02:00.005+05:30

In this blog post, we would see how to remove quorum disks in Exadata machine. We have one 1/8th Rack Exadata machine for Lab activity where ran into missing quorum disks for Voting Disk and I had to fix that in order to get the system patched in Rolling fashion to maintain high availability.

To patch the Exadata system in rolling fashion, it requires voting disks to reside on HIGH redundancy diskgroup which is not possible in 1/8th Rack Exadata system since there is only 3 cell nodes in there, and for High redundancy it requires five copies of voting disk.

So, in this scenario - we add a separate HDD drive on both compute nodes and share that between the nodes to be used for High redundancy diskgroup creation - there it comes the term "Quorum Disk"

We have +DATAC1 diskgroup configured with HIGH redundancy where our voting disk resides but two of the quorum disks being used in there went missing so our voting disks had only three copies available and CRS was not coming up.

I had to remove the quorum disks from both compute nodes and then configure it back to fix the issue.

SQL> l 
  1* select disk_number, GROUP_NUMBER, MOUNT_STATUS, HEADER_STATUS, MODE_STATUS, STATE, path from v$asm_disk where GROUP_NUMBER=1
SQL> / 

DISK_NUMBER GROUP_NUMBER MOUNT_S HEADER_STATU MODE_ST STATE    PATH 
----------- ------------ ------- ------------ ------- -------- ---------------------------------------------------------------------- 
          2            1 MISSING UNKNOWN      OFFLINE NORMAL 
          3            1 MISSING UNKNOWN      OFFLINE NORMAL 
         14            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.1;10.0.0.2/DATAC1_CD_05_exad02cel03
         13            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.1;10.0.0.2/DATAC1_CD_00_exad02cel03
         15            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.1;10.0.0.2/DATAC1_CD_02_exad02cel03
          7            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.1;10.0.0.2/DATAC1_CD_03_exad02cel03
          8            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.1;10.0.0.2/DATAC1_CD_04_exad02cel03
          0            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.1;10.0.0.2/DATAC1_CD_01_exad02cel03
          4            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.3;10.0.0.4/DATAC1_CD_05_exad02cel02
         16            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.3;10.0.0.4/DATAC1_CD_02_exad02cel02
         17            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.3;10.0.0.4/DATAC1_CD_01_exad02cel02
          5            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.3;10.0.0.4/DATAC1_CD_00_exad02cel02
          6            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.3;10.0.0.4/DATAC1_CD_03_exad02cel02
         11            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.3;10.0.0.4/DATAC1_CD_04_exad02cel02
         19            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.5;10.0.0.6/DATAC1_CD_04_exad02cel01
          1            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.5;10.0.0.6/DATAC1_CD_02_exad02cel01
         18            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.5;10.0.0.6/DATAC1_CD_00_exad02cel01
          9            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.5;10.0.0.6/DATAC1_CD_03_exad02cel01
         12            1 CACHED  MEMBER       ONLINE  NORMAL   o/10.0.0.5;10.0.0.6/DATAC1_CD_01_exad02cel01

Due to missing quorum disk in the DATAC1 diskgroup, we have only three copies of voting disks available as of now.

[root@exa01dbadm02 ~]# crsctl query css votedisk
##  STATE    File Universal Id                File Name Disk group
--  -----    -----------------                --------- ---------
 1. ONLINE   94acaa401bd34fe0bf261af4437fc75e (o/10.0.0.5;10.0.0.6/DATAC1_CD_02_exad02cel01) [DATAC1]
 2. ONLINE   7680d9f206544ff1bf27661bf8cc3250 (o/10.0.0.3;10.0.0.4/DATAC1_CD_05_exad02cel02) [DATAC1]
 3. ONLINE   b632f75fe4884f5cbf3627faa6bbbe07 (o/10.0.0.1;10.0.0.2/DATAC1_CD_03_exad02cel03) [DATAC1]
Located 3 voting disk(s).
[root@exa01dbadm02 ~]#

I moved the voting disks to +RECOC1 diskgroup which was configured with NORMAL REDUNDANCY.

[oragrid@exa01dbadm01 ~]$ crsctl replace votedisk +RECOC1
Successful addition of voting disk 783e7633ea934fd0bff78c8b8dbe5a66.
Successful addition of voting disk a5cf9e2d99134f69bf6bb15c98044623.
Successful addition of voting disk d5d20cd6ff3e4fcdbf68df28cb18d030.
Successful deletion of voting disk 94acaa401bd34fe0bf261af4437fc75e.
Successful deletion of voting disk 7680d9f206544ff1bf27661bf8cc3250.
Successful deletion of voting disk b632f75fe4884f5cbf3627faa6bbbe07.
Successful deletion of voting disk e47d60407b054f3bbf5dc07df8080ee6.
Successfully replaced voting disk group with +RECOC1.
CRS-4266: Voting file(s) successfully replaced


[oragrid@exa01dbadm01 ~]$ crsctl query css votedisk
##  STATE    File Universal Id                File Name Disk group
--  -----    -----------------                --------- ---------
 1. ONLINE   783e7633ea934fd0bff78c8b8dbe5a66 (o/10.0.0.5;10.0.0.6/RECOC1_CD_02_exad02cel01) [RECOC1]
 2. ONLINE   a5cf9e2d99134f69bf6bb15c98044623 (o/10.0.0.3;10.0.0.4/RECOC1_CD_02_exad02cel02) [RECOC1]
 3. ONLINE   d5d20cd6ff3e4fcdbf68df28cb18d030 (o/10.0.0.1;10.0.0.2/RECOC1_CD_02_exad02cel03) [RECOC1]
Located 3 voting disk(s).
[oragrid@exa01dbadm01 ~]$

Now we can go ahead and drop the missing quorum disks from the DATAC1 diskgroup forcefully.

[oragrid@exa01dbadm01 ~]$ sqlplus "/as sysasm"

SQL*Plus: Release 12.2.0.1.0 Production on Thu Jul 30 12:06:27 2020

Copyright (c) 1982, 2016, Oracle.  All rights reserved.


Connected to:
Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production

SQL>
SQL> set lines 300
SQL> ALTER DISKGROUP DATAC1 DROP QUORUM DISK QD_DATAC1_exa01dbadm01 FORCE;

Diskgroup altered.

SQL> ALTER DISKGROUP DATAC1 DROP QUORUM DISK QD_DATAC1_exa01dbadm02 FORCE;

Diskgroup altered.

SQL>

Delete the quorum disk device from the node1 using quorumdiskmgr utility.

[root@exa01dbadm01 ~]# cd /opt/oracle.SupportTools/
[root@exa01dbadm01 oracle.SupportTools]# ./quorumdiskmgr --delete --device
[Success] Successfully deleted device /dev/exadata_quorum/QD_DATAC1_exa01dbadm01.
[Success] Successfully deleted device /dev/exadata_quorum/QD_DATAC1_exa01dbadm02.

Delete the quorum disk target from the node1 using quorumdiskmgr utility.

[root@exa01dbadm01 oracle.SupportTools]# ./quorumdiskmgr --delete --target
[Success] Successfully removed target iqn.2015-05.com.oracle:qd--datac1--exa01dbadm01
[Success] Successfully removed backstore QD_DATAC1_exa01dbadm01
[Success] Successfully removed logical volume /dev/VGExaDb/LVDbVdexa01dbadm01DATAC1

Now delete quorum disk configuration from the node1.

[root@exa01dbadm01 oracle.SupportTools]# ./quorumdiskmgr --delete --config

[Success] Successfully deleted quorum disk configurations

[root@exa01dbadm01 oracle.SupportTools]#

Now, delete the quorum disk device from node2.

[root@exa01dbadm02 ~]# cd /opt/oracle.SupportTools/
[root@exa01dbadm02 oracle.SupportTools]# ./quorumdiskmgr --delete --device
[Success] Successfully deleted device /dev/exadata_quorum/QD_DATAC1_exa01dbadm01.
[Success] Successfully deleted device /dev/exadata_quorum/QD_DATAC1_exa01dbadm02.

Delete quorum disk target from node2.

[root@exa01dbadm02 oracle.SupportTools]# ./quorumdiskmgr --delete --target
[Success] Successfully removed target iqn.2015-05.com.oracle:qd--datac1--exa01dbadm02
[Success] Successfully removed backstore QD_DATAC1_exa01dbadm02
[Success] Successfully removed logical volume /dev/VGExaDb/LVDbVdexa01dbadm02DATAC1

Delete quorum disk configuration from node 2.

[root@exa01dbadm02 oracle.SupportTools]#  ./quorumdiskmgr --delete --config
[Success] Successfully deleted quorum disk configurations

[root@exa01dbadm02 oracle.SupportTools]#

At this point, we are done with removing the quorum disk configuration from our Exadata System, in next post, I would detail how we configure it in the system.

Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Cloud Infrastructure and Oracle Autonomous Database Cloud Services and new articles.

Twitter : https://twitter.com/rajsoft8899

Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/

Facebook : https://www.facebook.com/rkushawaha

1Z0-1072 : Oracle Cloud Infrastructure 2019 Architect Associate

2020-05-31T21:36:00.002+05:30

Pleased to inform you all that I passed 1Z0-1072 : Oracle Cloud Infrastructure 2019 Architect Associate.

It's generosity of Oracle that it made its official training videos of "Cloud Infrastructure 2019 Architect Associate" public and also offered to appear for the exam at free of cost in this time of pandemic crisis around the globe, it given us an opportunity to learn and scale our skills to enhance our career as well as expanding our area of expertise.

At this time of writing, Oracle has offered multiple Oracle cloud related training and certifications at free of cost, click here to know all those which is available in the list as of now - or you can

Click here to directly go to the OCI Associate training videos and start learning the new.

Click here for the practice exam.

Click here for Oracle Cloud Infrastructure (OCI) Architect Associate exam 2019 (1Z0-1072) StudyGuide

Certification Details
Certification name: 1Z0-1072 - Oracle Cloud Infrastructure 2019 Architect Associate
Target audience: Designed for professionals responsible for designing infrastructure solutions using Oracle Cloud Infrastructure services
Exam price: $150
Format: Multiple choice
Duration: 105 minutes
Number of questions: 66
Passing score: 65%

I encourage you to utilize this opportunity and learn and add new skills in your professional profile.

Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Cloud Infrastructure and Oracle Autonomous Database Cloud Services and new articles.

Twitter : https://twitter.com/rajsoft8899

Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/

Facebook : https://www.facebook.com/rkushawaha

Oracle Cloud Infrastructure vs. AWS

2020-05-13T23:49:00.002+05:30

Oracle Cloud Infrastructure vs. AWS

Read here to know great insights on how Oracle Cloud Infrastructure services price are much cheaper with greater performance as compared to AWS Cloud services.

Read here - https://www.oracle.com/cloud/economics/

Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Cloud Infrastructure and Oracle Autonomous Database Cloud Services and new articles.

Twitter : https://twitter.com/rajsoft8899

Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/

Facebook : https://www.facebook.com/rkushawaha

Free Oracle OCI and Autonomous Database training & Certification

2020-04-25T20:46:00.000+05:30

As most of the Oracle enthusiasts are aware of free Oracle Cloud Infrastructure and Autonomous database training and certifications being offered by Oracle until 15th May 2020, you must start your learning today and don't miss your train.

Oracle has given one of the best gift to all Oracle aspirants to learn new skills and earn the valuable certificate for free of cost - it is BIG gift.

Make a target, when you come out of this pandemic lock-down, you have new skills to show to your employer.

Below are the list of free Oracle cloud training one would be interested to learn.

It is just weeks away when you would miss this wonderful opportunity since the offer is only valid till 15th May 2020, just login to your oracle account, click on one of the training listed above and it would direct you to the training videos page.

Once finished with all the videos, you should have good understanding of the subject, do complete exam practice questionnaire and book for your certification slot from the next section on the training videos page itself - this way you get to PearsonVue site get your exam booked for free.

Please make a note that you need to book your exam through the training site, and don't go directly to pearsonvue, otherwise you won't get it for free.

Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Cloud Infrastructure and Oracle Autonomous Database Cloud Services and new articles.

Twitter : https://twitter.com/rajsoft8899
Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/
Facebook : https://www.facebook.com/rkushawaha

Oracle Critical Patch Update for April 2020 is out today

2020-04-15T03:34:00.000+05:30

Oracle Critical Patch Update for April 2020
===============================

Critical Patch Update Advisories are available at the following location:

Oracle Technology Network: https://www.oracle.com/security-alerts/

Oracle Cloud Customers should review:
https://www.oracle.com/security-alerts/#cloud

The Critical Patch Update Advisory for April 2020 is available at the following location:

Oracle Technology Network:
https://www.oracle.com/security-alerts/cpuapr2020.html

Important information can also be found at:
https://blogs.oracle.com/security/

Oracle's Security Fixing Policies are available at the following location:

https://www.oracle.com/corporate/security-practices/assurance/vulnerability/security-fixing.html

The next four dates for Critical Patch Updates are:

July 14, 2020
October 20, 2020
January 19, 2021
April 20, 2021

Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Cloud Infrastructure and Oracle Autonomous Database Cloud Services and new articles.

Twitter : https://twitter.com/rajsoft8899
Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/
Facebook : https://www.facebook.com/rkushawaha

Creating Pluggable Database using OEM

2020-03-07T10:23:00.002+05:30

Here in this article, I would demonstrate how we can create a new Pluggable Database using Oracle Enterprise Manager 13c.

1 - Login to the Oracle Enterprise Manager to go the Container Database target Home Page in which you want to create the new Pluggable Database.

2 - From the drop-down Menu of Cluster Database, Navigate to Provisioning > Provision Pluggable Databases.

3 - Create Pluggable Database : Creation Options page opens, Select "Create a new PDB" and provide oracle software owner credentials in the "Host Credentials" property. Click Next.

Click Next.

It validates the /tmp directory space on the nodes being provisioned.

You can schedule the provision date/time or you can just start the job right away with immediate option.

You can monitor the CreatePluggableDatabase job progress - Click on "View Execution Details" tab to monitor the progress.

Provisioning job's status now "Succeeded" and you are done with provisioning. You can validate the PDB status in OEM or by logging to the Container CDB at the host.

Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Cloud Infrastructure and Oracle Autonomous Database Cloud Services and new articles.

Twitter : https://twitter.com/rajsoft8899
Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/
Facebook : https://www.facebook.com/rkushawaha

DBCS - Database Cloud Service Patching

2020-03-06T20:32:00.002+05:30

Here in this article, I would summarize how easily we can do the "Database Cloud Service" patching online just via few clicks from the "Oracle Cloud Service Console".

Login to the Cloud Console and go to the DBCS instance page.

Click on the DBCS instance you want to patch, Instance Overview page opens. In my below example, there is a primary and standby Cloud instances.

At left side, click on the "Administration" tab, Patching page opens up which has list of all Available Patches for the underline DBCS instance.

Choose the right PSU Update and click on the right side hamburger sign, and click on Patch prechecks. Once you click on the pre-checks, it confirms if the patch is downloadable and /u01 mount on the DBCS instance host has enough free space available.

You can navigate through "Activity" tab to see the pre-check detail steps.

Once the pre-check completes, then initiates the actual patching job, it asks for the Patching Notes and choose whether you want to patch with "Switch-over" so there is no down-time.

The node hosting the standby database is patched first. A switchover operation is performed after patching is complete on the standby and then the patch is applied to the node hosting the new
standby.

If you want errors to be ignored during the patching operation, select the Force apply patch option. Then, click Patch.

Oracle Cloud Infrastructure Cloud Shell

2020-03-05T19:52:00.000+05:30

One of the most awaited feature every Oracle Cloud Admin, developers were waiting for is now released by Oracle - Oracle Cloud Infrastructure "Cloud Shell". Cloud Shell is a web based browser terminal accessible from the Oracle Cloud console.

Cloud Shell provides Linux shell with a pre-authenticated OCI CLI. This feature is available for all Oracle Cloud users and accessible from console.

Cloud Shell provides:

* An ephemeral machine to use as a host for a Linux shell, pre-configured with the latest version of the OCI Command Line Interface (CLI) and a number of useful tools

* 5GB of storage for your home directory

* A persistent frame of the Console which stays active as you navigate to different pages of the console

Following are the Tools Included With Cloud Shell:

Cloud Shell is a small Linux virtual machine. In addition to the OCI CLI, the Cloud Shell VM comes with current versions of several useful tools and utilities pre-installed, including:

> Git

> Java

> Python (2 and 3)

> SQL Plus

> kubectl

> helm

> maven

> gradle

> terraform

TO start the OCI Cloud Shell, you just have to click on Cloud Shell icon just left to the console notification bell icon at the right top.

Once you click on the Cloud Shell, a small Linux virtual machine gets created that is equipped with latest oci cli and other various tools listed above and finally you are ready to interact with Oracle Cloud resources from the web-based terminal.

To allow a group of users to use the Cloud Shell, you need to create an IAM policy for this so that all users in that group can use it.

allow group group_name to use cloud-shell in tenancy

Oracle Cloud Infrastructure OS Management

2020-03-05T10:18:00.000+05:30

Oracle Cloud Infrastructure OS Management service provides simple and very robust tool for general operation system maintenance activities for the compute instances running on Oracle Cloud OCI.

Using this OS management service, you can monitor the packages installed on compute instances, you can do the linux packages maintenance works i.e. adding/installing new packages, removing the existing packages or updating the existing one when that becomes available to its public yum repository.

OS management service is not enabled by default. It is an agent based service that you have to enable by installing osms-agent agent on the underline compute node.

All compute instances which has enabled osms-agent installed is called managed instance. You can manage the managed instances individually or you can group the managed instances and do the bulk maintenance but all the managed instances in the group must have same OS and version.

For detailed learning and understanding of the OS Management service - click here.

Oracle Database 20c Documents available now !!

2020-02-17T14:01:00.003+05:30

Here is the great news arrived that we had been waiting for.

Oracle Database 20c documentation available now here

- https://docs.oracle.com/en/database/oracle/oracle-database/20/install-and-upgrade.html

Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Cloud Infrastructure and Oracle Autonomous Database Cloud Services and new articles coming up for Oracle 20c new features series.

Twitter : https://twitter.com/rajsoft8899
Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/
Facebook : https://www.facebook.com/rkushawaha

Moving datafile online in Oracle 12c (12.1.0.2)

2019-12-27T20:00:00.000+05:30

Starting from Oracle database 12c release 1 (12.1.0.2), you can move a data file from one location/filesystem to another/ASM diskgroup while database is open and being used by the application users.

Taking an example of ASM storage where mistakenly a datafile was added to a tablespace without plus(+) shine before the diskgroup name and new file got added inside the $ORACLE_HOME on the filesystem.

In this situation, DBA should quickly try to reduce the newly added file size to smallest size possible and turn off the datafile autoextend so no much data could be written and datafile size remain small which gives us a luxury to move it to proper location in minimum time.

Below highlighted data file was added mistakenly which was placed into ORACLE_HOME.

FILE_NAME                                                                                GB AUT     MAX_GB
-------------------------------------------------------------------------------- ---------- --- ----------
+DATA/TESTDB/DATAFILE/users.4513.1027281799                                10 YES 31.9999847
+DATA/TESTDB/DATAFILE/users.4813.1027281809                                 4 YES 31.9999847
/u01/app/oracle/product/12.1.0.2/dbhome_1/dbs/DATA                                      2 YES         31
+DATA/TESTDB/DATAFILE/users.8520.1027282145                                 2 YES         31

Let's move the datafile created inside the /u01 mount to our +DATA ASM Diskgroup with following command.

SQL> ALTER DATABASE MOVE DATAFILE '/u01/app/oracle/product/12.1.0.2/dbhome_1/dbs/DATA' TO '+DATA';

Database altered.

Now, let's validate the datafile list if that is moved.

SQL> select file_name, bytes/1024/1024/1024 as GB ,autoextensible,MAXBYTES/1024/1024/1024 MAX_GB from dba_data_files where tablespace_name='users' order by GB desc;

FILE_NAME                                                                                GB AUT     MAX_GB
-------------------------------------------------------------------------------- ---------- --- ----------
+DATA/TESTDB/DATAFILE/users.4513.1027281799                                10 YES 31.9999847
+DATA/TESTDB/DATAFILE/users.4813.1027281809                                 4 YES 31.9999847
+DATA/TESTDB/DATAFILE/users.8520.1027282145                                 2 YES         31
+DATA/TESTDB/DATAFILE/users.4194.1027284059                        .001953125 NO           0

Data file moved successfully as you can see in the above output.

Now once datafile is moved to the appropriate location, you can resize and turn autoextend on for its auto growth.

SQL> alter database datafile '+DATA/TESTDB/DATAFILE/users.4194.1027284059' resize 1g;

Database altered.

SQL> alter database datafile '+DATA/TESTDB/DATAFILE/users.4194.1027284059' autoextend on maxsize 32767m;

Database altered.

SQL>

Let's validate the data file which we moved if that has no any corrupt blocks.

RMAN> validate datafile 68;

Starting validate at 17-DEC-19
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=112 instance=TESTDB1 device type=DISK
channel ORA_DISK_1: starting validation of datafile
channel ORA_DISK_1: specifying datafile(s) for validation
input datafile file number=00068 name=+DATA/TESTDB/DATAFILE/users.4194.1027284059
channel ORA_DISK_1: validation complete, elapsed time: 00:00:03
List of Datafiles
=================
File Status Marked Corrupt Empty Blocks Blocks Examined High SCN
---- ------ -------------- ------------ --------------- ----------
68   OK     0              130945       131072          15464094246834
  File Name: +DATA/TESTDB/DATAFILE/users.4194.1027284059
  Block Type Blocks Failing Blocks Processed
  ---------- -------------- ----------------
  Data       0              0
  Index      0              0
  Other      0              127

Finished validate at 17-DEC-19

RMAN>

Datafile validation is successful.

Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Cloud Infrastructure and Oracle Autonomous Database Cloud Services and new articles.

Twitter : https://twitter.com/rajsoft8899
Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/

Oracle Cloud Infrastructure(OCI) Service Health Dashboard

2019-10-17T09:21:00.002+05:30

While you configure lots of Oracle Cloud Infrastructure resources across different cloud tenancy/region, you may be interested to keep track of health-checks status of all resources/services in your region to make sure everything is healthy in the cloud region where your important cloud services are hosted.

Oracle provides you a very convenient way to monitor the health of all OCI resources/services for all regions in one place.

In order to access the OCI health, you can directly go to the "https://ocistatus.oraclecloud.com/" URL where all OCI services health status is available for you to keep track of or if you are already logged in to your tenancy, click on the "View Health Dashboard" at right top corner and it would take you to the OCI Health Dashboard page automatically.

From this dashboard you can get current status information about the services in your region.

Customers can self register by clicking on the 'Subscribe to Updates' link which offers email, SMS, Webhook, RSS, and other channels.

Notifications are delivered whenever OCI creates or resolves an incident.

There are four colored notations on the "OCI Health Dashboard" for you to identify whether a particular cloud service in a specific region is healthy or has some issues as following, if all cloud services are green then that has "Normal Performance" and everything is healthy and optimal.

Similarly, there is "Degraded Performance" , "Partial Outage" and "Major Outage" notations to identify the resource glitch.

Currently, you can see that everything is in "Normal Performance" range as below.

You can subscribe to incident notifications to your email address as when when there is an incident created in any regions or you can opt-in for your own region only where all your cloud services are running.

ORA-46269: Conflicting operation on audit files

2019-10-17T09:07:00.001+05:30

The DBMS_AUDIT_MGMT package provides subprograms to manage audit trail records. These subprograms enable audit administrators to manage the audit trail. In a mixed-mode environment, these audit trails comprise the database, operating system (OS), and XML audit trails. In a unified auditing environment, this comprises the unified audit trail.

One of the daily maintenance system job fails with ORA-46269 error as below.

-bash-4.1$ oerr ora 46269
46269, 00000, "Conflicting operation on audit files"
// *Cause: Audit files were being operated by more than one DBMS_AUDIT_MGMT
//         API from different sessions. The simultaneous execution of the
//         CLEAN_AUDIT_TRAIL API with itself can cause the conflict.
// *Action: Wait until the execution of one of the API's complete and try
//          executing the API again.
-bash-4.1$

From the database instance alert log:

Tue Oct 15 19:38:53 2019
Errors in file /u01/app/oracle/diag/rdbms/orcldb/orcldb1/trace/orcldb1_j002_247077.trc:
ORA-12012: error on auto execute of job "SYS"."STANDARD_OS_AUDIT_TRAIL_PURGE"
ORA-46269: Conflicting operation on audit files
ORA-06512: at "SYS.DBMS_AUDIT_MGMT", line 61
ORA-06512: at "SYS.DBMS_AUDIT_MGMT", line 2447
ORA-06512: at line 1
Tue Oct 15 19:46:18 2019

From the incident trace file:

Trace file /u01/app/oracle/diag/rdbms/orcldb/orcldb1/trace/orcldb1_j002_247077.trc
Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production
With the Partitioning, Real Application Clusters, Automatic Storage Management, Oracle Label Security,
OLAP, Data Mining and Real Application Testing options
ORACLE_HOME = /u01/app/oracle/product/11.2.0.4/dbhome_2
System name:    Linux
Node name:      dbadm02.example.com
Release:        4.1.12-124.24.3.el6uek.x86_64
Version:        #2 SMP Mon Jan 14 15:08:09 PST 2019
Machine:        x86_64
Instance name: orcldb1
Redo thread mounted by this instance: 1
Oracle process number: 115
Unix process pid: 247077, image: oracle@dbadm02.example.com (J002)

*** 2019-10-15 19:38:53.665
*** SESSION ID:(1195.35311) 2019-10-15 19:38:53.665
*** CLIENT ID:() 2019-10-15 19:38:53.665
*** SERVICE NAME:(SYS$USERS) 2019-10-15 19:38:53.665
*** MODULE NAME:(DBMS_SCHEDULER) 2019-10-15 19:38:53.665
*** ACTION NAME:(STANDARD_OS_AUDIT_TRAIL_PURGE) 2019-10-15 19:38:53.665

Current audit management cleanup jobs list, I could see two audit clean-up jobs scheduled at same time and if first one that starts few seconds before the 2nd job, runs longer then 2nd job conflicts with the processing of first one and fails with the subjected error.

SQL> select * from DBA_AUDIT_MGMT_CLEANUP_JOBS

JOB_NAME                                 JOB_STAT AUDIT_TRAIL                  JOB_FREQUENCY
---------------------------------------- -------- ---------------------------- -----------------------------------
STANDARD_OS_AUDIT_TRAIL_PURGE            ENABLED  OS AUDIT TRAIL               FREQ=HOURLY;INTERVAL=1
CLEAN_OS_DB_AUDIT_RECORD                 ENABLED  OS AUDIT TRAIL               FREQ=HOURLY;INTERVAL=1

SQL>

SQL> select OWNER,JOB_NAME,to_char(last_start_date,'DD-MM-YY HH24:MI:SS') Last_date_time, to_char(next_run_date,'DD-MM-YY HH24:MI:SS') Next_Date_Time, JOB_ACTION from DBA_SCHEDULER_JOBS

OWNER                          JOB_NAME                       LAST_DATE_TIME    NEXT_DATE_TIME    JOB_ACTION
------------------------------ ------------------------------ ----------------- ----------------- -------------------------------------------------------
SYS                            CLEAN_OS_DB_AUDIT_RECORD       16-10-19 03:38:13 16-10-19 04:38:13 BEGIN DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL(4, TRUE);  END;
SYS                            STANDARD_OS_AUDIT_TRAIL_PURGE  16-10-19 03:38:53 16-10-19 04:38:53 BEGIN DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL(4, TRUE);  END;

SQL>

Scheduler details:

OWNER           JOB_NAME                            START_DATE                     ENABL STATE           FAILURE_COUNT LAST_START_DATE            NEXT_RUN_DATE               MAX_RUN_DURATIO SOURCE
--------------- ----------------------------------- ------------------------------ ----- --------------- ------------- -------------------------- ------------------------------ --------------- ---------------
SYS             STANDARD_OS_AUDIT_TRAIL_PURGE       16-jan-2016 02:38:53           TRUE  SCHEDULED                9731 16-oct-2019 01:38:53       16-oct-2019 02:38:53
SYS             CLEAN_OS_DB_AUDIT_RECORD            19-jan-2017 15:38:13           TRUE  SCHEDULED                 619 16-oct-2019 01:38:13       16-oct-2019 02:38:13
SYS             PURGE_LOG                           10-oct-2014 03:00:00           TRUE  SCHEDULED                   0 15-oct-2019 03:00:00       16-oct-2019 03:00:00

SQL> select * from DBA_AUDIT_MGMT_CONFIG_PARAMS

PARAMETER_NAME                 PARAMETER_VALUE                     AUDIT_TRAIL
------------------------------ ----------------------------------- ----------------------------
DB AUDIT TABLESPACE            SYSAUX                              STANDARD AUDIT TRAIL
DB AUDIT TABLESPACE            SYSAUX                              FGA AUDIT TRAIL
AUDIT FILE MAX SIZE            10000                               OS AUDIT TRAIL
AUDIT FILE MAX SIZE            10000                               XML AUDIT TRAIL
AUDIT FILE MAX AGE             5                                   OS AUDIT TRAIL
AUDIT FILE MAX AGE             5                                   XML AUDIT TRAIL
DB AUDIT CLEAN BATCH SIZE      10000                               STANDARD AUDIT TRAIL
DB AUDIT CLEAN BATCH SIZE      10000                               FGA AUDIT TRAIL
OS FILE CLEAN BATCH SIZE       1000                                OS AUDIT TRAIL
OS FILE CLEAN BATCH SIZE       1000                                XML AUDIT TRAIL
DEFAULT CLEAN UP INTERVAL      1                                   OS AUDIT TRAIL

11 rows selected.

SQL>

I don't want duplicate job schedules in place for the same purpose so I disabled and drop the one job schedule to fix the conflict and avoid the noise tickets.

SQL> begin
dbms_scheduler.disable( '"SYS"."CLEAN_OS_DB_AUDIT_RECORD"' );
END;
/

PL/SQL procedure successfully completed.

SQL>

SQL> EXEC DBMS_AUDIT_MGMT.DROP_PURGE_JOB('CLEAN_OS_DB_AUDIT_RECORD');

PL/SQL procedure successfully completed.

SQL>

Now, only one job is left in the schedule and it should work fine without any conflict in future.

SQL> select * from DBA_AUDIT_MGMT_CLEANUP_JOBS;

JOB_NAME                                                                                             JOB_STAT AUDIT_TRAIL                  JOB_FREQUENCY
---------------------------------------------------------------------------------------------------- -------- ---------------------------- ----------------------------------------------------------------------------------------------------
STANDARD_OS_AUDIT_TRAIL_PURGE                                                                        ENABLED  OS AUDIT TRAIL               FREQ=HOURLY;INTERVAL=1

OWNER                          JOB_NAME                       LAST_DATE_TIME    NEXT_DATE_TIME    JOB_ACTION
------------------------------ ------------------------------ ----------------- ----------------- -------------------------------------------------------
SYS                            STANDARD_OS_AUDIT_TRAIL_PURGE  16-10-19 04:38:53 16-10-19 05:38:53 BEGIN DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL(4, TRUE);  END;











Tested the manual job run once, and it worked fine.







SQL> BEGIN DBMS_AUDIT_MGMT.CLEAN_AUDIT_TRAIL(4, TRUE);  END;
  2  /

PL/SQL procedure successfully completed.

SQL>
















Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Cloud Infrastructure and Oracle Autonomous Database Cloud Services and new articles.




Twitter : https://twitter.com/rajsoft8899

Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/

Facebook : https://www.facebook.com/rkushawaha

Critical Patch Update released for October 2019

2019-10-16T21:14:00.001+05:30

Critical Patch Update for October 2019 is out now.

Oracle strongly recommends to review the product patches and apply if applicable.

Review the details at below link.

https://www.oracle.com/technetwork/topics/security/alerts-086861.html?source=:em:gbc:ie:cpo:RC_SPPT190829P00039:SEV400002054&elq_mid=147614&sh=0926171606142609160608192604261926311429291121&cmid=SPPT190829P00039

Always Free ATP instance stops automatically

2019-10-15T09:52:00.000+05:30

SMART Oracle Cloud Feature !!

To save the unnecessary cloud infrastructure cost and utilization, Oracle Autonomous Database instances provisioned leveraging the Always Free tier subscription, stops automatically after 7 days when there is no recent activities to the ATP cloud instance.

YUM install of Oracle 18c XE database in Oracle Cloud Infrastructure

2019-10-15T09:09:00.002+05:30

In this post, I would show you how you can deploy Oracle 18c XE database in Oracle Cloud Infrastructure Gen 2, in just one command.

Login to your OCI compute node where you want to deploy the Oracle 18c XE, please make a note that you have created the compute VM with Oracle Linx 7, Oracle Linux 8 still, at time of writing this post, doesn't have OCI included image for the 18c XE.

Since we are on OEL7.7 and OCI image already includes the Oracle 18c XE database rpm in there so doing pre-check is optional and we can directly install it using below one line command, it would automatically find the dependencies and do that job for you.

Let's initiate the installation now as below.

[root@oci02 ~]# yum install oracle-database-xe-18c.x86_64  
 Loaded plugins: langpacks, ulninfo  
 Resolving Dependencies  
 --> Running transaction check  
 ---> Package oracle-database-xe-18c.x86_64 0:1.0-1 will be installed  
 --> Processing Dependency: oracle-database-preinstall-18c for package: oracle-database-xe-18c-1.0-1.x86_64  
 --> Running transaction check  
 ---> Package oracle-database-preinstall-18c.x86_64 0:1.0-1.el7 will be installed  
 --> Finished Dependency Resolution  
 Dependencies Resolved  
 =============================================================================================================================================================================================  
  Package                           Arch                Version                 Repository                   Size  
 =============================================================================================================================================================================================  
 Installing:  
  oracle-database-xe-18c                   x86_64               1.0-1                  ol7_oci_included               2.4 G  
 Installing for dependencies:  
  oracle-database-preinstall-18c               x86_64               1.0-1.el7                ol7_latest                   18 k  
 Transaction Summary  
 =============================================================================================================================================================================================  
 Install 1 Package (+1 Dependent package)  
 Total download size: 2.4 G  
 Installed size: 5.2 G  
 Is this ok [y/d/N]: y  
 Downloading packages:  
 (1/2): oracle-database-preinstall-18c-1.0-1.el7.x86_64.rpm                                                      | 18 kB 00:00:00  
 (2/2): oracle-database-xe-18c-1.0-1.x86_64.rpm                                                            | 2.4 GB 00:01:11  
 ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------  
 Total                                                                             34 MB/s | 2.4 GB 00:01:11  
 Running transaction check  
 Running transaction test  
 Transaction test succeeded  
 Running transaction  
  Installing : oracle-database-preinstall-18c-1.0-1.el7.x86_64                                                              1/2  
  Installing : oracle-database-xe-18c-1.0-1.x86_64                                                                    2/2  
 [INFO] Executing post installation scripts...  
 [INFO] Oracle home installed successfully and ready to be configured.  
 To configure Oracle Database XE, optionally modify the parameters in '/etc/sysconfig/oracle-xe-18c.conf' and then execute '/etc/init.d/oracle-xe-18c configure' as root.  
  Verifying : oracle-database-xe-18c-1.0-1.x86_64                                                                    1/2  
  Verifying : oracle-database-preinstall-18c-1.0-1.el7.x86_64                                                              2/2  
 Installed:  
  oracle-database-xe-18c.x86_64 0:1.0-1  
 Dependency Installed:  
  oracle-database-preinstall-18c.x86_64 0:1.0-1.el7  
 Complete!  
 [root@oci02 ~]#

Above you see, it installed the 18c XE HOME and it points you to the configuration file that you can modify per your needs and run the /etc/init.d/oracle-xe-18c configure to create the XE container database for you, as below.

Default, sample configuration file that would be used to created the database.

 [root@oci02 ~]# cat /etc/sysconfig/oracle-xe-18c.conf  
 #This is a configuration file to setup the Oracle Database.  
 #It is used when running '/etc/init.d/oracle-xe-18c configure'.  
 # LISTENER PORT used Database listener, Leave empty for automatic port assignment  
 LISTENER_PORT=  
 # EM_EXPRESS_PORT Oracle EM Express URL port  
 EM_EXPRESS_PORT=5500  
 # Character set of the database  
 CHARSET=AL32UTF8  
 # Database file directory  
 # If not specified, database files are stored under Oracle base/oradata  
 DBFILE_DEST=  
 # SKIP Validations, memory, space  
 SKIP_VALIDATIONS=false  
 [root@oci02 ~]#

Let's create the database as below. You need to provide a complex password that will be used for SYS, SYSTEM and PDBADMIN accounts commonly, later you may change it which is different to each other once database instance created successfully.

 [root@oci02 ~]# /etc/init.d/oracle-xe-18c configure  
 Specify a password to be used for database accounts. Oracle recommends that the password entered should be at least 8 characters in length, contain at least 1 uppercase character, 1 lower case character and 1 digit [0-9]. Note that the same password will be used for SYS, SYSTEM and PDBADMIN accounts:  
 Confirm the password:  
 Configuring Oracle Listener.  
 Listener configuration succeeded.  
 Configuring Oracle Database XE.  
 Enter SYS user password:  
 ********  
 Enter SYSTEM user password:  
 *******  
 Enter PDBADMIN User Password:  
 **********  
 Prepare for db operation  
 7% complete  
 Copying database files  
 29% complete  
 Creating and starting Oracle instance  
 30% complete  
 31% complete  
 34% complete  
 38% complete  
 41% complete  
 43% complete  
 Completing Database Creation  
 47% complete  
 50% complete  
 Creating Pluggable Databases  
 54% complete  
 71% complete  
 Executing Post Configuration Actions  
 93% complete  
 Running Custom Scripts  
 100% complete  
 Database creation complete. For details check the logfiles at:  
  /opt/oracle/cfgtoollogs/dbca/XE.  
 Database Information:  
 Global Database Name:XE  
 System Identifier(SID):XE  
 Look at the log file "/opt/oracle/cfgtoollogs/dbca/XE/XE.log" for further details.  
 Connect to Oracle Database using one of the connect strings:  
    Pluggable database: oci02/XEPDB1  
    Multitenant container database: oci02  
 Use https://localhost:5500/em to access Oracle Enterprise Manager for Oracle Database XE  
 [root@oci02 ~]#

Once database instance gets configured, you are provided "Database Information" and connect string for the Pluggable database, dbca log file location that you can review and finally Enterprise Manager URL to use for the database monitoring purpose.

Finally you may spare few mins and validate the container database information.

 [root@oci02 ~]# ps -ef | grep pmon  
 oracle  23387   1 0 19:00 ?    00:00:00 xe_pmon_XE  
 root   23902 11789 0 19:02 pts/0  00:00:00 grep --color=auto pmon  
 [root@oci02 ~]#  
 [root@oci02 ~]# su - oracle  
 Last login: Mon Oct 14 18:51:07 GMT 2019 on pts/0  
 [oracle@oci02 ~]$  
 [oracle@oci02 ~]$ . oraenv  
 ORACLE_SID = [oracle] ? XE  
 The Oracle base has been set to /opt/oracle  
 [oracle@oci02 ~]$  
 [oracle@oci02 ~]$ sqlplus "/as sysdba"  
 SQL*Plus: Release 18.0.0.0.0 - Production on Mon Oct 14 19:03:09 2019  
 Version 18.4.0.0.0  
 Copyright (c) 1982, 2018, Oracle. All rights reserved.  
 Connected to:  
 Oracle Database 18c Express Edition Release 18.0.0.0.0 - Production  
 Version 18.4.0.0.0  
 SQL>

 SQL> select name, open_mode, database_role, cdb from v$database;  
 NAME   OPEN_MODE      DATABASE_ROLE  CDB  
 --------- -------------------- ---------------- ---  
 XE    READ WRITE      PRIMARY     YES  
 SQL> show pdbs  
   CON_ID CON_NAME            OPEN MODE RESTRICTED  
 ---------- ------------------------------ ---------- ----------  
      2 PDB$SEED            READ ONLY NO  
      3 XEPDB1             READ WRITE NO  
 SQL>

Hope it helps, thanks for reading, please subscribe to this blog to stay tuned with latest news on Oracle Cloud Infrastructure and Oracle Autonomous Database Cloud Services and other new articles.

Twitter : https://twitter.com/rajsoft8899
Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/
Facebook : https://www.facebook.com/rkushawaha

Add or Remove or List TFA Users and Groups

2019-10-08T09:57:00.003+05:30

Image Source

Sometimes you may need to collect srdc diagnostic data requested by Oracle Support Engineer for an Oracle Internal Error or problem evaluation and analysis.

You don't want loads of unnecessary diagnostics traces and logs to be collected and need only relevant traces/logs for a specific Oracle incident/problem so srdc needs to be run by Oracle software binary owner which may be different from Oracle cluster-ware owner and that may not have permission to run the TFA to collect diagnostics data.

You won't be able to run the TFA if you are not a TFA user and get an error like depicted below since oracle user is not allowed to run the TFA diag collection.

[root@dbadm01 bin]#su - oracle


$ ./tfactl diagcollect -srdc ORA-00700
User oracle does not have keys to run TFA. Please check with TFA Admin(root)

$ exit
[root@dbadm01 bin]#

TFA administrator or root user can add Oracle software binary owner to TFA group so that he/she can run the TFA srdc diagnostics collection when needed.

Let's see how we can add oracle user to the TFA administrator group and run the srdc data collection and finally we would see how to remove oracle user from the TFA administration group.

You can view the list of TFA users currently allowed to run it as below. We can see that only oragrid user is allowed to run the TFA.

[root@dbadm01 bin]# ./tfactl access lsusers
.---------------------------------.
|  TFA Users in dbadm01  |
+-----------+-----------+---------+
| User Name | User Type | Status  |
+-----------+-----------+---------+
| oragrid   | USER      | Allowed |
'-----------+-----------+---------'

.---------------------------------.
|          TFA Users in           |
+-----------+-----------+---------+
| User Name | User Type | Status  |
+-----------+-----------+---------+
| oragrid   | USER      | Allowed |
| oragrid   | USER      | Allowed |
| oragrid   | USER      | Allowed |
'-----------+-----------+---------'

[root@dbadm01 bin]#

Let's now add oracle user in the TFA group now so that it can also be part of it and run the tfa.

[root@dbadm01 bin]# ./tfactl access add -user oracle -local

Successfully added 'oracle' to TFA Access list.

.---------------------------------.
|  TFA Users in dbadm01  |
+-----------+-----------+---------+
| User Name | User Type | Status  |
+-----------+-----------+---------+
| oracle   | USER      | Allowed |
| oragrid   | USER      | Allowed |
'-----------+-----------+---------'

[root@dbadm01 bin]#

Since oracle user is now added to TFA group, let's switch to oracle user and try to collect the TFA srdc diagnostics data.

[root@dbadm01 bin]# su - oracle
[oracle@dbadm01 ~]$

[oracle@dbadm01 ~]$ /u01/app/12.2.0.1/grid/bin/tfactl diagcollect -srdc ORA-00700
Enter the time of the ORA-00700 [YYYY-MM-DD HH24:MI:SS,<RETURN>=ALL] :
Enter the Database Name [<RETURN>=ALL] : PROD1

1. Sep/27/2019 17:21:00 : [prod1] ORA-00700: soft internal error, arguments: [kdt_bseg_srch_cbk PITL5], [3], [148630702], [276915], [], [], [], [], [], [], [], []
2. Sep/27/2019 15:05:30 : [prod1] ORA-00700: soft internal error, arguments: [kdt_bseg_srch_cbk PITL5], [2], [148630736], [276915], [], [], [], [], [], [], [], []
3. Sep/27/2019 15:05:30 : [prod1] ORA-00700: soft internal error, arguments: [PITL6], [276915], [148630736], [], [], [], [], [], [], [], [], []
4. Sep/27/2019 07:16:44 : [prod1] ORA-00700: soft internal error, arguments: [kdt_bseg_srch_cbk PITL5], [2], [156338726], [276915], [], [], [], [], [], [], [], []
5. Sep/24/2019 09:51:00 : [prod1] ORA-00700: soft internal error, arguments: [PITL6], [276915], [156338560], [], [], [], [], [], [], [], [], []
6. Sep/24/2019 09:50:56 : [prod1] ORA-00700: soft internal error, arguments: [kdt_bseg_srch_cbk PITL5], [2], [156338560], [276915], [], [], [], [], [], [], [], []

Please choose the event : 1-6 [1] 6
Selected value is : 6 ( Sep/24/2019 09:50:56 )
Scripts to be run by this srdc: ipspack rdahcve1210 rdahcve1120 rdahcve1110
Components included in this srdc: OS CRS DATABASE NOCHMOS
Collecting data for local node(s)
Scanning files from Sep/24/2019 03:50:56 to Sep/24/2019 15:50:56

Collection Id : 20191008033306dbadm01

Detailed Logging at : /u01/app/grid/tfa/repository/srdc_ora700_collection_Tue_Oct_08_03_33_07_UTC_2019_node_local/diagcollect_20191008033306_dbadm01.log
2019/10/08 03:33:10 UTC : NOTE : Any file or directory name containing the string .com will be renamed to replace .com with dotcom
2019/10/08 03:33:10 UTC : Collection Name : tfa_srdc_ora700_Tue_Oct_08_03_33_07_UTC_2019.zip
2019/10/08 03:33:11 UTC : Scanning of files for Collection in progress...
2019/10/08 03:33:11 UTC : Collecting additional diagnostic information...

2019/10/08 03:33:41 UTC : Getting list of files satisfying time range [09/24/2019 03:50:56 UTC, 09/24/2019 15:50:56 UTC]
2019/10/08 03:34:45 UTC : Completed collection of additional diagnostic information...
2019/10/08 03:36:29 UTC : Collecting ADR incident files...
2019/10/08 03:36:30 UTC : Completed Local Collection
.---------------------------------------------.
|              Collection Summary             |
+------------------+-----------+-------+------+
| Host             | Status    | Size  | Time |
+------------------+-----------+-------+------+
| dbadm01 | Completed | 249MB | 200s |
'------------------+-----------+-------+------'

Logs are being collected to: /u01/app/grid/tfa/repository/srdc_ora700_collection_Tue_Oct_08_03_33_07_UTC_2019_node_local
/u01/app/grid/tfa/repository/srdc_ora700_collection_Tue_Oct_08_03_33_07_UTC_2019_node_local/dbadm01.tfa_srdc_ora700_Tue_Oct_08_03_33_07_UTC_2019.zip
[oracle@dbadm01 ~]$

TFA srdc collection went successful now !

If you want to remove the oracle user from the TFA group, you can do so using below command.

[root@dbadm01 bin]# ./tfactl access remove -user oracle -local

Successfully removed 'oracle' from TFA Access list.

.---------------------------------.
|  TFA Users in dbadm01  |
+-----------+-----------+---------+
| User Name | User Type | Status  |
+-----------+-----------+---------+
| oragrid   | USER      | Allowed |
'-----------+-----------+---------'

[root@dbadm01 bin]#

Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Cloud Infrastructure, Oracle Autonomous Database Cloud Services and other new articles.

Twitter : https://twitter.com/rajsoft8899
Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/

Oracle Cloud Infrastructure - Resources Monitoring | Email Notifications

2019-09-28T01:28:00.000+05:30

In this article, we would see how to monitor the all Oracle Cloud Infrastructure(OCI) resources at one place and would see how to define alarm notifications for a kind of metric and metrics dimension.

You won't have access to the autonomous database compute nodes in the cloud but you have the luxury to monitor OS level statistics and can monitor the health, capacity, and performance of your Oracle Cloud Infrastructure resources when needed using queries or on a passive basis using alarms. Queries and alarms rely on metrics emitted by your resource to the Monitoring service.

An Administrator has super privilege to manage and monitoring all Oracle Cloud Infrastructure resources it has in its Identity domain/Tenancy.

If you want a different user to only monitor all the OCI resources then a new user can be created and assigned appropriate IAM policies to monitor the resources.

Monitoring is possible only for resources that is enabled for monitoring or which emits the metrics. Queries and Alarms used these emitted metrics for its notification rules and methods. The Monitoring service works with the Notifications service to notify you when metrics breach.

Lets' get started:

Login to your Oracle Cloud Infrastructure Service Console and click on the navigation menu and click on Monitoring > Service Metrics - to open the "Monitoring" page for all OCI resources.

"Service Metrics" page opens, The Service Metrics page displays the default charts for metrics in the first accessible Compartment and Metric Namespace. Very small or large values are indicated by International System of Units (SI units), such as M for mega (10 to the sixth power).

You can select any COMPARTMENT and appropriate METRICS NAMESPACE and adjust the "START TIME" and "END TIME" to narrow down the metrics graphic visualization for the metric namespaces and review its trend to predict the underline hardware/resource health.

For any Metrics type, you can click on its "Options" and Copy Chart URL - a direct URL to view this metrics graph in web browser.

Select any metrics namespace you want to see the metrics trend.

Metrics Explorer:

Write and edit queries in Monitoring Query Language (MQL), using metrics from either your application or an Oracle Cloud Infrastructure service.

By default, Metrics Explorer has no graph, you can write MQL query or construct one automatically using the selection criteria.

Below I am adding an MQL(Monitoring Query Language) Query 1:

COMPARTMENT : comp01
Metrics Namespace : oci_autonomous_database
Metric name : cpuUtilization
Interval : 1m - 1 minute
Statistic : Mean
Metrics Dimension : AutonomousDBType
Dimension Value : ATP

and Click on Update Chart >

Once you clicked on the "Update Chart" above, it populates the "Metrics Explorer" chart metrics with graph for for the autonomous database.

Similarly, we can add another MQL query for the OCI compute agent for the metric name = DiskBytesWritten as below.

Alarm Status:

If you want to "Create Alarm" for any query, you can click on the "Create Alarm" button instead of "Update Chart" from the "Metric Explorer" or click on the "Alarm Definition" at left side and create alarm page opens up for some details to be filled up before finishing it.

In "Define Alarm" section, Provide relevant "Alarm Name" and its Severity and Alarm description. Optionally you can give resource tags as well.

In the "Metric Description" section, Select the appropriate compartment, metric namespace, metric name to you to be alerted for, dimension name and its value. Most important, put the right trigger rule(it is the threshold value for the metric name you are enabling the alarming notification). In my case, I am creating this alarm for the CPU utilization, so I give trigger value 1 for the demonstration.

In the "Notification" section, select the right TOPIC in which you have defined the email subscription and click on "Save alarm".

If you don't have an Alarm Topic created then you can click on the "Create a Topic" and provide email details- Alarm Topic an email subscription where alarm notifications would be sent out. In my case, I am creating an alarm for the CPU utilization for my autonomous database dimensions. Provide "NOTIFICATION FREQUENCY" to re-evaluate the alarm status to make sure if that is still above it defined threshold or cleared, If alarm remains above its defined threshold then Alarm would fire and email alert at the subscribed email. Make sure alarm is checked as enabled in the end and click on "Save Alarm".

You should check the "REPEAT NOTIFICATION" option to provide the frequency to repeat the alarm notification if the event is not resolved/cleared.

Once you save, alarm gets create and available for the monitoring.

A while ago, you subscribed to an alarm topic that you created, you would receive an email confirmation once you subscribe to confirm for the destination email where alerts would be dispatched.

You get an email as below.

Alarm Definition:

Once you create the alarm, then you can go back to Alarm Definition to see the list of alarms you have created for the different OCI resource/dimensions monitoring.

To view the MQL for an alarm definition, you open an alarm and go to its Query section and expand it.

CpuUtilization[1m]{AutonomousDBType = "ATP"}.mean()



OCID1.AUTONOMOUSDATABASE.OC1.AP-MUMBAI-1.ABRG6LJRBEWFTBLJTRMG74GA6BJ3CBHXH6SQB3ESXDBYO2C3M2OKBGJ3OFUA

You can click on the Alarm Name to view its alarming history.

Once alert criteria meets then it fires and you get an email alert like below. If you don't want to receive any further email notification or a user wants to exclude himself from the email alert subscription then he/she can click on the "unsubscribe" link in the email alert body to stop receiving the alerts further.

Similarly, you define the alarming notifications for all metrics available for "METRIC NAMESPACE" in a compartment.

Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Cloud Infrastructure and Oracle Autonomous Database Cloud Services and new articles.

Twitter : https://twitter.com/rajsoft8899
Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/

Creating a Block Volume in Oracle Cloud Infrastructure

2019-09-27T02:16:00.001+05:30

In this article, let's see how to create a new Block Volume in Oracle Cloud Infrastructure Services.

Network-attached storage volumes, attachable to compute instances. The Oracle Cloud Infrastructure Block Volumes service provides persistent storage that can be attached to compute instances using the iSCSI protocol. The volumes are stored in high performance network storage and support automated backup and snapshot capabilities. Volumes and their backups are accessible only from within a customer's VCN and are encrypted at rest using unique keys. For additional security, iSCSI CHAP authentication can be required on a per-volume basis.

The Oracle Cloud Infrastructure Block Volume service lets you dynamically provision and manage block storage volumes . You can create, attach, connect, and move volumes as needed to meet your storage and application requirements. After you attach and connect a volume to an instance, you can use the volume like a regular hard drive. You can also disconnect a volume and attach it to another instance without the loss of data.

Login to your Oracle Cloud account and go to the Infrastructure Menu and under the "Core Infrastructure"and click on the Block Storage > Block Volumes .

Create Block Volumes page opens, provide the its Name, compartment name where you want to put this resource, select appropriate AD and its size (size should be greater than or equals to 50GB). You can select the backup policy(Gold, Silver, Bronze) for the block volume getting created. If you already have your own encryption key stored in the Cloud Vault then you should select its option and provide the key or just let it be the default and let OCI create/handle one for you.

You can give a Tag for this resource and click on "Create Block Volume" to start its provision.

In few seconds, Block Volume is created and ready to be attached in any of the compute instance.

Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle OCI, Oracle Autonomous Database Cloud Services and new articles.

Twitter : https://twitter.com/rajsoft8899

Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/

out of host capacity : Oracle Cloud Infrastructure

2019-09-27T01:49:00.003+05:30

While requesting a new compute resource to provision, your request may end up saying "out of host capacity" while clicking on the "Create" button for the compute. For example, I tried to provision a compute instance in Mumbai region and it ends with "out of host capacity".

Note : The selected shape does not have any available servers in the selected region and Availability Domain (AD). Virtual Machines (VM) are dynamically provisioned. If an AD has reached a minimum threshold, new hypervisors (physical servers) will be automatically provisioned. There may be some occasions where the additional capacity has not finished provisioning before the existing capacity is exhausted, but when retrying in 15 minutes the customer may find the shape they want is available. Alternatively, selecting a different shape, AD or region will almost certainly have the capacity needed.

So, let's try to provision the compute instance in some other region, I tried in Sydney and it went well since there was free VMs available for the request.

Click on the region drop down menu at right top, and select the other region that you may have already subscribed. In my case, I changed it to Sydney.

and finally click on the "Create" button.

In Sydney region, compute instance provision started means there was VM resources available for the request.

Compute instance is created and running now there.

Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Autonomous Database Cloud Services and new articles.

Twitter : https://twitter.com/rajsoft8899

Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/

Terminate an Oracle Autonomous Database Cloud

2019-09-26T01:56:00.006+05:30

In this article, I would step you through the process to terminate an Oracle autonomous transaction processing database service.

Terminating an Autonomous Transaction Processing database permanently deletes the instance and removes all automatic backups. You cannot recover a terminated database.

Login your Oracle Cloud Infrastructure Service console and navigate to Autonomous Transaction Processing database.

You get to the Autonomous Databases list, move your cursor to three dots at right side against the ATP instance your want to terminate/delete.

Click on the "Terminate" from the drop down list.

Once you click on the "Terminate", it asks for the confirmation, to enter your Autonomous Database name you wanted to terminate and click on the "Terminate Autonomous Database" to initiate the termination job.

ATP Instance terminated:

Hope it helps, thanks for reading, please subscribe to this blog to stay updated with latest news on Oracle Autonomous Database Cloud Services and new articles.

Twitter : https://twitter.com/rajsoft8899
Linkedin : https://www.linkedin.com/in/raj-kumar-kushwaha-5a289219/