Upgrade Pluggable Database to Oracle Database 23ai

 

Here’s a simplified way to upgrade your Oracle Database in OCI to Oracle Database 23c AI using a refreshable clone PDB and AutoUpgrade.

Benefits of This Approach:

  • Reduced Downtime: It minimizes downtime compared to an in-place upgrade.
  • New Base Database System: You’ll get a new system with an updated OS and Oracle Grid Infrastructure version.

You can use this approach for a Base Database Service, Exadata Database Service, Exadata Cloud@Customer, or any Oracle Database option.

My Environment

  • PDB to Upgrade: SALES

Source:

  • Version: 19.23.0
  • Name: DBS19

Target:

  • Version: 23.4.0
  • Name: DBS23

Steps to Upgrade:

1. Prepare AutoUpgrade

  • Download the latest version of AutoUpgrade from My Oracle Support.
  • Copy it to both source and target systems, optionally placing it in $ORACLE_HOME/rdbms/admin.
  • Create an AutoUpgrade config file (sales.cfg), and save it on both servers:
  • global.autoupg_log_dir=/u01/app/oracle/cfgtoollogs/autoupgrade
  • global.keystore=/u01/app/oracle/cfgtoollogs/keystore
  • upg1.source_home=/u01/app/oracle/product/19.0.0.0/dbhome_1
  • upg1.target_home=/u01/app/oracle/product/23.0.0.0/dbhome_1
  • upg1.sid=CDB19
  • upg1.pdbs=SALES
  • upg1.target_cdb=CDB23
  • upg1.source_dblink.SALES=CLONEPDB 600
  • upg1.target_pdb_copy_option.SALES=file_name_convert=none
  • upg1.target_version=23
  • upg1.start_time=12/05/2024 02:00:00

  • Important Settings:
    • global.keystore allows AutoUpgrade to handle your encrypted PDB.
    • source_home and target_home point to the Oracle Home for the respective databases.
    • source_dblink.SALES configures a database link with a 10-minute (600s) refresh interval.
    • target_version specifies the version since the systems are remote.
    • start_time defines when downtime starts, initiating the final PDB refresh and upgrade.

    • 2. Prepare the Source PDB

    • Create a user for the database link:--
    • CREATE USER dblinkuser IDENTIFIED BY password;
    • GRANT create session, create pluggable database, select_catalog_role TO dblinkuser;
    • GRANT read ON sys.enc$ TO dblinkuser;

Comments

Post a Comment

Popular posts from this blog

Key points on Read-Only Instance and Read-Only Database

 In Oracle, both Read-Only Instance and Read-Only Database provide mechanisms to limit data modifications, but they are used in different contexts and for different purposes. Here's a comparison: 1. Read-Only Instance Definition : A read-only instance is a configuration in Oracle Real Application Clusters (RAC) where one or more instances of a multi-instance database are set up to operate in read-only mode. This is typically done in environments with high concurrency for both read and write operations. Key Features : Allows real-time query scaling by dedicating specific instances to read-only operations. Write operations are not allowed on the designated read-only instance, but other instances in the cluster can still handle write operations. Useful in RAC configurations for load balancing , where read workloads can be distributed across multiple read-only instances. Instance-specific: The database remains fully functional (read-write) when accessed through other instances. Us...
Read more

Steps to create database link between Oracle database and SQL Server

 Creating a database link between SQL Server and Oracle allows seamless data exchange between the two systems. Here’s a step-by-step guide: Step 1: Install the Required Drivers Install Oracle Database Gateway for SQL Server (ODG4MS). This acts as a bridge between Oracle and SQL Server. Ensure the Oracle Client is installed on the Oracle database server or the server acting as the gateway. Step 2: Configure the Oracle Database Gateway Locate Configuration Files: Navigate to the $ORACLE_HOME/network/admin directory on the Oracle Gateway server. Edit tnsnames.ora: Add an entry for the database link pointing to the SQL Server database: dg4msql =   (DESCRIPTION =     (ADDRESS = (PROTOCOL = TCP)(HOST = <SQL_SERVER_HOSTNAME>)(PORT = 1521))     (CONNECT_DATA = (SID = dg4msql))     (HS=OK)  -- Required for heterogeneous services   )   Edit listener.ora: Update the Oracle listener configuration to recognize the gateway: SID_LIST_LISTENE...
Read more

How to Configure Logging for EM 12c Management Agent

The goal of this article is to provide instruction on how to enable logging for the Enterprise Manager 12c Management Agent.. ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- The logging properties for the agent are stored in $EMSTATE/sysman/config/emd.properties file, same as in 11.1. But the properties that control logging follow the log4j configuration syntax instead of the syntax supported by the 11.1 agent. To active changes to the logging parameters, you can use either of the emctl commands: emctl reload agent emctl setproperty agent Overview Agent logging entries look similar to the standard log4j logging, with the only significant difference being the prefix 'Logger.' that you will see on each line. For example: # logging properties Logger.log4j.appender.Rolling=org.apache.log4j.RollingFileAppender Logger.lo...
Read more