Oracle world 2024 - AI

 

Intro 

The world is transitioning from the data era to the age of artificial intelligence. Many organizations are leveraging AI features to gain a competitive edge and expand their market share. Oracle 23c AI introduces a wide array of AI-driven features to support this shift. With Oracle CloudWorld just around the corner, the event will be a key platform to showcase the power and potential of AI in transforming businesses.

Oracle CloudWorld 2024 is set to take place from September 9 to 12 in Las Vegas at the Caesars Forum Convention Center. This major event will bring together Oracle customers, partners, and industry experts to explore the latest innovations in cloud technology, AI, databases, and more.

Oracle 23ai : True Cache

 

Intro

In today’s fast-paced digital landscape, speed is paramount. Users expect instant responses, and applications must seamlessly handle high traffic and demanding workloads. Oracle databases, often the backbone of critical systems, bear the weight of these performance demands. Fortunately, Oracle Database has a powerful solution: True Cache, an advanced in-memory caching technology designed to optimize database performance and enhance application efficiency.

What is Oracle True Cache? 

True Cache is a fast storage layer that temporarily holds frequently accessed data from an Oracle database to speed up read operations. It's like a quick-access memory that helps retrieve data faster without repeatedly querying the main database.

Simple terms: True Cache is an in-memory, read-only caching layer positioned in front of an Oracle database.

General Architecture 

                                                     Figure 1: True Cache Architecture

The benefits of True Cache in Oracle 23c AI include:

Faster Data Access: By storing frequently accessed data in memory, True Cache reduces the time needed to retrieve data from the database, leading to quicker response times for applications

Improved Performance: With data readily available in memory, the overall performance of the database engine is enhanced, allowing for more efficient processing of queries and transactions.

Reduced Database Load: True Cache minimizes the number of direct queries to the database, thereby reducing the workload on the database engine and freeing up resources for other tasks.

Enhanced User Experience: Applications that rely on quick data retrieval will see significant improvements, providing a smoother and more responsive user experience.

Scalability: As demand for data grows, True Cache can help maintain performance levels by efficiently managing and accessing frequently used data.

If you need more detail, refer to Oracle's main blog for true cache.

https://blogs.oracle.com/database/post/introducing-oracle-true-cache

In this article, I will elaborate on how you can set up Oracle's true cache instance.

Pre-requisites for True cache testing

• Create two DBCS instances with 23ai. (Both instances should be in the same subnet).
• Make sure connective is there for two VMs. (default ports 22 and 1521 need to be enabled for the subnet ).
• Make sure to add the IP address of both nodes to the host file.

Below is my machine hostname :

Primary :

Cache instance :

Prepare instance 

Using the DBCA utility, I create a BLOB file, which I then transfer to the True Cache instance. Upon inspecting the contents of the BLOB file, you'll find both the password file and the wallet stored within it.

  $ORACLE_HOME/bin/dbca -configureDatabase -prepareTrueCacheConfigFile \
 -sourceDB P23AI \
 -trueCacheBlobLocation /home/oracle/scripts/ \
 -silent 
  

Expected output

  
[oracle@dbsdpl24 admin]$ $ORACLE_HOME/bin/dbca -configureDatabase -prepareTrueCacheConfigFile \
-sourceDB P23AI \
-trueCacheBlobLocation /home/oracle/scripts/ \
-silent

Enter password for the TDE wallet:

Enter password for the TDE wallet:
Session ID of the current execution is: 1
Log file location: /u01/app/oracle/cfgtoollogs/dbca/P23AI_jt7_yyz/trace.log_2024-08-20_04-35-42PM_53669
-----------------
Running Initialization job
Completed Initialization job
33% complete
-----------------
Running Validate_dataguard job
Skipping. Job is detected as not applicable.
40% complete
-----------------
Running Validate_db_version job
Completed Validate_db_version job
47% complete
-----------------
Running Validate_tde_credentials job
Completed Validate_tde_credentials job
53% complete
-----------------
Running Validate_true_cache_instance job
Completed Validate_true_cache_instance job
60% complete
-----------------
Running Validate_archive_log_mode job
Completed Validate_archive_log_mode job
67% complete
-----------------
Running Prepare_blob job
Completed Prepare_blob job
100% complete
---------- PLUGIN NOTES ----------
Successfully created blob file: /home/oracle/scripts/blob_2024-08-20_04-35-42PM.tar.gz
---------- END OF PLUGIN NOTES ----------
Look at the log file "/u01/app/oracle/cfgtoollogs/dbca/P23AI_jt7_yyz/P23AI_jt7_yyz0.log" for further details.
[oracle@dbsdpl24 admin]$
  
  

Note: Make sure to transfer: the blob_2024-08-20_04-35-42PM.tar.gz file to the true cache instance. 

Configure Listener on the primary instance 

Add the required entries to the listener configuration and then restart the listener.

REGISTRATION_INVITED_NODES_Listener = (10.0.1.6,10.0.1.240)
VALID_NODE_CHECKING_REGISTRATION_LISTENER=OFF

Drop DBCS-created database

Using DBCA to delete a database on a True Cache instance.

$ORACLE_HOME/bin/dbca -deleteDatabase -sourceDB TC23AI -forceArchiveLogDeletion -silent

Configure True Cache

The next step is to create true cache instance. With DBCA, we can also create a True Cache instance.

$ORACLE_HOME/bin/dbca -createTrueCache \
-gdbName TC23AI \
-sid TC23AI \
-sourceDBConnectionString dbsdpl24.sub08101943421.cnvcn01.oraclevcn.com:1521/P23AI_jt7_yyz.sub08101943421.cnvcn01.oraclevcn.com \
-trueCacheBlobFromSourceDB /home/oracle/scripts/blob_2024-08-20_04-35-42PM.tar.gz \
-sgaTargetInMB 14848 \
-pgaAggregateTargetInMB 3712 \
-silent -listeners LISTENER

Expected output

[oracle@dbsdpl53 scripts]$ $ORACLE_HOME/bin/dbca -createTrueCache \
-gdbName TC23AI \
-sid TC23AI \
-sourceDBConnectionString dbsdpl24.sub08101943421.cnvcn01.oraclevcn.com:1521/P23AI_jt7_yyz.sub08101943421.cnvcn01.oraclevcn.com \
-trueCacheBlobFromSourceDB /home/oracle/scripts/blob_2024-08-20_04-35-42PM.tar.gz \
-sgaTargetInMB 14848 \
-pgaAggregateTargetInMB 3712 \
-silent -listeners LISTENER
Enter Remote DB SYS user password:

Enter password for the source database TDE wallet:

[FATAL] [DBT-10317] Specified SID Name (TC23AI) already exists.
   ACTION: Specify a different SID Name that does not already exist.
[oracle@dbsdpl53 scripts]$ vi /etc/oratab
[oracle@dbsdpl53 scripts]$ $ORACLE_HOME/bin/dbca -createTrueCache -gdbName TC23AI -sid TC23AI -sourceDBConnectionString dbsdpl24.sub08101943421.cnvcn01.oraclevc                                                n.com:1521/P23AI_jt7_yyz.sub08101943421.cnvcn01.oraclevcn.com -trueCacheBlobFromSourceDB /home/oracle/scripts/blob_2024-08-20_04-35-42PM.tar.gz -sgaTargetInMB 1                                                4848 -pgaAggregateTargetInMB 3712 -silent -listeners LISTENER
Enter Remote DB SYS user password:

Enter password for the source database TDE wallet:

[WARNING] [DBT-10331] Specified SID Name (TC23AI) may have a potential conflict with an already existing database on the system.
   CAUSE: The specified SID Name without the trailing numeric characters (TC23AI) may have a potential conflict with an already existing database on the system.
   ACTION: Specify a different SID Name that does not conflict with existing databases on the system.
Session ID of the current execution is: 5
Log file location: /u01/app/oracle/cfgtoollogs/dbca/TC23AI/trace.log_2024-08-20_05-28-57PM_98530
-----------------
Running Extract_password_file_from_blob_file job
Completed Extract_password_file_from_blob_file job
25% complete
-----------------
Running Create_static_listener job
Skipping. Job is detected as not applicable.
38% complete
-----------------
Running Register_listener job
Completed Register_listener job
50% complete
-----------------
Running Extract_tde_wallet_from_blob_file job
Completed Extract_tde_wallet_from_blob_file job
54% complete
-----------------
Running Setup_required_directories job
Skipping. Job is detected as not applicable.
57% complete
-----------------
Running Create_pfile job
Completed Create_pfile job
61% complete
-----------------
Running Start_nomount_instance job
Completed Start_nomount_instance job
64% complete
-----------------
Running Create_TDE_wallet job
Completed Create_TDE_wallet job
68% complete
-----------------
Running Create_truecache_instance job

Completed Create_truecache_instance job
71% complete
-----------------
Running Add_oratab_entry job
Completed Add_oratab_entry job
75% complete
-----------------
Running Reopen_wallet job
Completed Reopen_wallet job
100% complete
---------- PLUGIN NOTES ----------
Successfully created True Cache.
In order to complete the operation,configure the True Cache database application services from the primary database.
---------- END OF PLUGIN NOTES ----------
Look at the log file "/u01/app/oracle/cfgtoollogs/dbca/TC23AI/TC23AI1.log" for further details.

After the creation True cache instance status

No data file is needed for this, as everything is managed in-memory. Similar to Active Data Guard, archives will push all frequently accessed data.

select open_mode,database_role from v$database;

OPEN_MODE            DATABASE_ROLE
-------------------- ----------------
READ ONLY WITH APPLY TRUE CACHE

-- MRP 

SQL>  select INST_ID,PROCESS,STATUS,THREAD#,SEQUENCE#,BLOCK# from GV$MANAGED_STANDBY;

   INST_ID PROCESS   STATUS                  THREAD#  SEQUENCE#     BLOCK#
---------- --------- -------------------- ---------- ---------- ----------
         1 DGRD      ALLOCATED                     0          0          0
         1 DGRD      ALLOCATED                     0          0          0
         1 ARCH      CONNECTED                     0          0          0
         1 ARCH      CONNECTED                     0          0          0
         1 ARCH      CONNECTED                     0          0          0
         1 ARCH      CONNECTED                     0          0          0
         1 RFS       IDLE                          1          0          0
         1 RFS       RECEIVING                     1          5    1335415
         1 RFS       IDLE                          0          0          0
         1 MRP0      APPLYING_LOG                  1          5    1335416
         1 DGRD      ALLOCATED                     0          0          0

   INST_ID PROCESS   STATUS                  THREAD#  SEQUENCE#     BLOCK#
---------- --------- -------------------- ---------- ---------- ----------
         1 RMI       IDLE                          0          0          0
         1 RMI       IDLE                          0          0          0

13 rows selected.

Conclusion

In a fast-paced world where every millisecond counts, caching is essential, and Oracle's True Cache is revolutionizing database performance. By accelerating data access and enhancing reliability and efficiency, True Cache empowers businesses to stay competitive and deliver exceptional user experiences. If you're aiming to boost your database performance, True Cache could be the game-changing solution you've been looking for.

Troubleshoot ODA Repo Issue

 

Intro 

If you found previous blog posts helpful for addressing ODA upgrade issues on virtualization platforms, the following article will ease your journey toward the 19.8 upgrade.

Article on Upgrades and Issues:

• ODA upgrade 12.1.2.12 to 18.3.0.0 -- Journey to 19.9.0.0 - Part 1
• Virtualized ODA upgrade 18.3.0.0 to 18.8.0.0 - Journey to 12.1.2.12 - 19.13.0.0 - Part 2
• Virtualized ODA upgrade 18.8.0.0 to 19.8.0.0 - Journey to 12.1.2.12 - 19.13.0.0 - Part 3
• ODA upgrade issues for - 12.1.2.6 to 12.1.2.10 

ODA virtualized upgrades are always challenging, with unexpected issues often arising. One consistent problem I've noticed in upgrades up to version 18.8.0.0 is the repository disappearing after a node reboot.

12.1.2.6 -> 12.1.2.10 
12.1.2.10 -> 12.1.2.12 
12.1.2.12 -> 18.3.0.0 
18.3.0.0 -> 18.8.0.0 
18.8.0.0 -> 19.8.0.0 
19.8.0.0 -> 19.13.0.0

In this article, I will elaborate on how you can overcome this repo issue. First, check the cluster VIP status.

KVM Upgrade issue : 4.4.10.22– 4.4.10.30

 

Intro

Virtualization has significantly transformed the IT industry by enhancing the efficient utilization of server resources. Despite the rapid adoption of cloud technology, many organizations hesitate to migrate their workloads to the cloud due to concerns regarding data sensitivity and operational challenges. For such businesses, virtualization continues to be the preferred solution, offering substantial cost savings in capital expenditure (CapEx) and a secure operational environment.

Ensuring the security of critical database workloads hosted in virtualized environments is paramount. Oracle Linux Virtualization Manager (OLVM) plays a crucial role in managing these virtual environments, and maintaining its updates is vital for safeguarding infrastructure integrity. Regular KVM upgrades are essential to uphold the security and reliability of these virtualized environments.

While upgrading our KVM hosts, we encountered several issues, particularly with hosts that previously utilized Gluster data domains.

OCI immutable backup : version control

 

Intro

In today's data-driven era, businesses leverage data analysis to seize opportunities and gain a competitive edge. This makes it crucial for organizations to have a robust disaster recovery (DR) plan. Most organizations leverage cloud backup features to store their data securely. When backups are in the public cloud, it is essential to ensure they are not altered and can be retrieved even after a ransomware attack. Oracle Cloud Object Storage provides an excellent feature of object versioning to ensure backups are safe and can be restored at any time during ransomware attacks.

Here are several reasons why immutable backups are important:

Measuring Storage Performance for Oracle DBs

 

Intro

Storage vendors often provide extensive product performance data, but this information may not accurately predict how the storage will perform with an Oracle database. This article offers practical methods to evaluate storage system performance, including Oracle-provided utilities.

There are two main methods to analyze the performance of storage.

• Oracle Orion
• Oracle procedure: DBMS_RESOURCE_MANAGER.calibrate_io.

I will show you how to measure IO using both methods in this article. 

The easiest way to use procedure DBMS_RESOURCE_MANAGER.calibrate_io. 

In Oracle, the DBMS_RESOURCE_MANAGER package provides procedures to manage database resources. To generate a read-only workload to measure the maximum number of IOPS (Input/Output Operations Per Second) and MB/s (Megabytes per second), you can use the CALIBRATE_IO procedure. This procedure helps in determining the I/O capabilities of the storage subsystem.

Oracle 23ai : SQL Firewall - Part 1 : Intergrate SQL-Firewall with Data-Safe

 

Intro 

We live in the data era, where every organization invests significant resources in securing its IT infrastructure. Protecting data is crucial because modern businesses rely heavily on data analysis. Ensuring the security of sensitive data has become the primary responsibility of security engineers and database administrators. Due to the critical nature of this data, hackers often attempt to gain control through :

• SQL injection attacks 
• Compromised accounts. 

Even OCI introduced the Web application firewalls (WAFs) claim to mitigate SQL injection attacks, but attackers can bypass these pattern-matching techniques. Allowlist-based and network-based SQL firewalls provide stronger protection but are ineffective for local and encrypted traffic. Additionally, they need more run-time context to thoroughly analyze SQL queries.

Oracle's latest long-term release 23ai came up with the latest features to integrate SQL firewall into the database. This enables the database administrator to elevate their database protection.