The frenetic pace of application development in modern IT organizations means it’s not unusual to demand an application be built with minimal requirements gathering – literally, from a napkin-based sketch – to a working first draft of the app within extremely short time frames – even a weekend! – with production deployment to follow just a few days later. This article – the fourth and final in this series – shows how to take advantage of APEX 18.2’s social login capabilities for improved user security. It also discusses how to leverage #SmartDB concepts to isolate SQL statements where they best belong: inside the database itself. Finally, it demonstrates how to complete a production deployment of the latest version of the APEX applications developed.

Nancy Swanson, Senior Director of Product Marketing for the Oracle Database Appliance portfolio, covered the role of DBAs in the age of Oracle Autonomous Database.

Databases are critical to organizations and represent a significant part of total IT spend. That is why you want to deploy your database on the best-optimized platform and protect your data with backups. The Cloud is transforming the way enterprises do business for the better, and backup is no different. That’s where Oracle Cloud Backup for Oracle Database comes into play.

Alan Zeichick, Director of Strategic Communications for Oracle, wrote in Forbes about Oracle’s expansion of its global data center footprint and the Cloud regions that Oracle has been opening worldwide.

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.

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.