Thursday, August 17, 2017

Oracle Database Cloud 'How To' Webcast Series - YouTube Videos


Following is a link for a very good YouTube how to video on Oracle Cloud:


It includes following videos:

  • Choosing the Right Oracle Database Cloud Service


  • Oracle Database Cloud Service Deployment Choices



  • Oracle RAC on Oracle Database Cloud Services


  • Oracle RAC on Oracle Database Cloud Bare Metal Services


  • Oracle Database Cloud Services Security (Part 1)


  • Oracle Database Cloud Services Security (Part 2)


  • Service Management using the Cloud Console


  • Enterprise Manager Cloud Control


  • Application and Database Migration to Oracle Cloud


  • Database Creation from Cloud Backup


  • Oracle Database Backup Service Overview


  • Pluggable Databases on Oracle Cloud


  • Multitenant Application Containers





Friday, August 11, 2017

Don't wait for 12.2.0.2 anymore, but Oracle 18

According the latest Oracle note - Release Schedule of Current Database Releases (Doc ID 742060.1), Oracle has changed its release schedule/name since 12.2.0.2.

It means:

Oracle 12.2.0.2 = Oracle 18
Oracle 12.2.0.3 = Oracle 19

But it does say  "This may change in the future to Oracle 20 as the last release for 12.2. "

You can read 2 blogs from Mike about the change:



Friday, August 04, 2017

DBCA fails to create 12.1.0.2 RAC database over 12.2 GI/ASM

When creating 12.1.0.2 RAC CDB on newly created 12.2.0.1 GI/ASM by using DBCA, the database creation failed with errors ORA-19504/.ORA-17502

By checking Oracle metalink, it is an Oracle bug (#21626377)  - RDBMS instance fails to identify the required disks to mount a disk group if compatible.asm of the diskgroup is higher than version of the software.

You can refer to the metalink note (Doc ID 21626377.8) for details. There are 2 ways to fix the issue:

1. Apply the BP 12.1.0.2.170418 (or later BPs) - 12.1.0.2.170718 (Jul 2017) Database Patch Set Update (DB PSU) - on Oracle 12.1.0.2 RDBMS home, so DBCA can create 12.1.0.2 database using the ASM diskgroup with compatible.asm set to 12.2.
2. Workaround 
- Create an ASM diskgroup with compatible.asm set to 12.1 and then try to create the 12.1 database.