Juan Loaiza, Oracle Executive Vice President, gives a quick overview of Exadata X8 capabilities for OLTP, analytics, cloud, and Autonomous Database.

Exadata has been on the market for over 10 years, and today it is an extremely successful product. It runs many of the most mission-critical applications in the world, including petabyte warehouses, critical financial and e-commerce platforms, complex business applications, and massive database consolidations.

Join Quest, Oracle experts, and your peers at Oracle OpenWorld, September 16 – 19, 2019, in San Francisco, California!

You can attend a Quest education session out of more than 2,000 unique sessions offered, mix and mingle with Oracle Product Team and end-users at a Quest reception, and stop by the Quest Kiosk in Moscone West Level 3, OUG-007 for a chance to win a $500 gift card!

COLLABORATE 20 Call for Presentations is now open!

COLLABORATE 20 will be taking place April 19-23, 2020 at the Mandalay Bay Resort and Casino. It is the largest user-led, user-focused event for Oracle users of all levels. IT decision-makers, super users, Oracle, and Oracle vendors gather to share real-world insights and practical solutions to maximize return on their Oracle investments.

You can expand your Oracle skill set by attending some of the 1,000+ interactive sessions, networking with experienced professionals who have the same challenges as you, and asking questions directly to Oracle and Oracle vendors at the Exhibitor Showcase. The user-focus of COLLABORATE 20 ensures that it will be full of first-hand experiences, real-world scenarios, and honest advice.

The first step to getting COLLABORATE 20 ready for attendees is selecting the presentations that will be showcased at the conference. If you are interested in being considered to present at COLLABORATE 20, submit an abstract any time between now and October 11, 2019. This is your chance to share your stories, insights, and advice with the Quest Oracle Community.

Oracle’s Multitenant Option was introduced in 12c Release as an efficient response to the Cloud technology challenges by reducing costs, streamlining processes and managing resources effectively. The architectural model consists of a Container Database (CDB) that controls the instance-wide maintenance activities and contains zero or more isolated pluggable databases (PDB) independently managed in terms of resources and security.

Initially, Oracle did not enforce the model but kept the legacy structures (the older Non-CDB instances) intact. Recently the non-CDB Option was deprecated, a decision that drives Oracle users to start adopting and converting their infrastructure to the new Option. In turn, this posed several challenges of its own and one of those is changing Pluggable Database level name, Container Database name, or Database ID (DBID). 

One possible use case is when a backup file of a PDB is received from a third-party software vendor whose name needs to change to meet the organization’s naming standards or to better convey the purposes of the database. Another scenario is to change the DBID of a cloned database to maintain its unique backup information repository in recovery catalog. In these, and similar situations, we can follow the methods explained below to achieve the required modifications. 

So, here I will provide detailed steps for three different changes that can be implemented in your Multitenant Architecture CDB environment:
-Changing PDB name
-Changing CDB name
-Changing Oracle DBID for all PDB’s

Please note that these changes might have consequences such as impacting backup & recovery. They should not be deployed in a production environment without proper planning and thorough testing.

Oracle’s Multitenant Option was introduced in 12c Release as an efficient response to the Cloud technology challenges by reducing costs, streamlining processes and managing resources effectively. The architectural model consists of a Container Database (CDB) that controls the instance-wide maintenance activities and contains zero or more isolated pluggable databases (PDB) independently managed in terms of resources and security.

Initially, Oracle did not enforce the model but kept the legacy structures (the older Non-CDB instances) intact. Recently the non-CDB Option was deprecated, a decision that drives Oracle users to start adopting and converting their infrastructure to the new Option. In turn, this posed several challenges of its own and one of those is changing Pluggable Database level name, Container Database name, or Database ID (DBID). 

One possible use case is when a backup file of a PDB is received from a third-party software vendor whose name needs to change to meet the organization’s naming standards or to better convey the purposes of the database. Another scenario is to change the DBID of a cloned database to maintain its unique backup information repository in recovery catalog. In these, and similar situations, we can follow the methods explained below to achieve the required modifications. 

So, here I will provide detailed steps for three different changes that can be implemented in your Multitenant Architecture CDB environment:
-Changing PDB name
-Changing CDB name
-Changing Oracle DBID for all PDB’s

Please note that these changes might have consequences such as impacting backup & recovery. They should not be deployed in a production environment without proper planning and thorough testing.

Oracle’s Multitenant Option was introduced in 12c Release as an efficient response to the Cloud technology challenges by reducing costs, streamlining processes and managing resources effectively. The architectural model consists of a Container Database (CDB) that controls the instance-wide maintenance activities and contains zero or more isolated pluggable databases (PDB) independently managed in terms of resources and security.

Initially, Oracle did not enforce the model but kept the legacy structures (the older Non-CDB instances) intact. Recently the non-CDB Option was deprecated, a decision that drives Oracle users to start adopting and converting their infrastructure to the new Option. In turn, this posed several challenges of its own and one of those is changing Pluggable Database level name, Container Database name, or Database ID (DBID). 

One possible use case is when a backup file of a PDB is received from a third-party software vendor whose name needs to change to meet the organization’s naming standards or to better convey the purposes of the database. Another scenario is to change the DBID of a cloned database to maintain its unique backup information repository in recovery catalog. In these, and similar situations, we can follow the methods explained below to achieve the required modifications. 

So, here I will provide detailed steps for three different changes that can be implemented in your Multitenant Architecture CDB environment:
-Changing PDB name
-Changing CDB name
-Changing Oracle DBID for all PDB’s

Please note that these changes might have consequences such as impacting backup & recovery. They should not be deployed in a production environment without proper planning and thorough testing.

On August 1, Oracle announced the general availability in all commercial regions of Oracle Functions, Oracle Cloud Infrastructure's functions-as-a-service (FaaS) platform.