Saturday, May 11, 2024

Unveiling the Power of Oracle Globally Distributed Database: Oracle Database 23ai Advancements

In the realm of database technology, Oracle Database 23ai marks a transformative era by ushering in a wave of advancements. Among these advancements, a standout focus lies on augmenting the capabilities of the Oracle Globally Distributed Database. As we approach this release, our attention centers on the integration of pioneering features tailored for distributed data environments. This blog serves as a preview, shedding light on the exciting enhancements Oracle Database 23ai brings to the Oracle Globally Distributed Database. These new features are poised not only to address challenges but also to reshape the landscape of distributed database operations, bringing forth heightened performance and unparalleled efficiency. As we delve into the specifics of these transformative features, Oracle Database 23ai emerges as a pivotal milestone, empowering businesses with tools to harness the full potential of distributed data scenarios. This blog sets the stage for exploring these enhancements, offering insights into how Oracle Database 23ai elevates the capabilities of the Oracle Globally Distributed Database, propelling it into a new era of excellence.

New Features: Oracle Globally Distributed Database and 23ai


1. Raft Replication

One of the notable features introduced in Database version 23ai is Raft replication (Consensus based replication protocol), offering automatic configuration of replication across all shards. Raft replication is integrated and transparent to applications. Raft replication automatically reconfigures replication in case of shard host failures or when shards are added or removed from the sharded database. The system declaratively configures the replication factor to help maintain a specified number of replicas available at all times. In the event of a node failure, failover is swift, and all nodes remain active. Crucially, this feature encompasses an automatic sub-second failover mechanism, reinforcing data integrity and operational continuity. This capability suits organizations requiring a highly available and scalable database system.

Ensuring Data Integrity and Seamless Operations

Raft Replication brings streamlined management and heightened availability to distributed database environments. This proves pivotal in scenarios where high availability and data integrity are paramount. With rapid fail-over and consistent data across nodes, Raft Replication empowers organizations to deliver optimal user experiences and meet stringent SLAs. This benefit is especially crucial in critical applications where uptime and data consistency directly influence business success.

Unveiling the Power of Oracle Globally Distributed Database: Oracle Database 23ai Advancements

Unveiling the Power of Oracle Globally Distributed Database: Oracle Database 23ai Advancements
Raft Replication

2. Directory-Based Sharding Method

Directory-based sharding introduces a versatile user-defined approach, where the location of data records associated with a sharding key is specified dynamically at the time of insert based on user preferences. The process involves storing key location information within a directory, housing an extensive collection of key values, often numbering in the hundreds of thousands. This technique not only facilitates the dynamic movement of individual key values between locations but also allows for efficient bulk movements. The capability to adaptively shift key values offers a high degree of customization, enhancing data management, scalability, and load balancing across databases or clusters.

Key Value Grouping for Enhanced Data Organization

Directory-based sharding is useful when you need to group certain key values together into the same location or chunk for affinity purposes, and when needed this group can be moved together in an efficient manner

An example is a social network application, where grouping together customers who often exchange messages on the same shard minimizes the cross-shard traffic. The grouping must be preserved during re-sharding when data is moved between shards. On the other hand, if a member of a group starts communicating more with members of another group, their data must be moved to the appropriate group with minimal impact on the application.

3. Automatic Data Move on Sharding Key Update

Automatic data move on sharding key update is a potent attribute within Oracle Globally Distributed Database that streamlines data management within sharded tables. Sometimes a sharding key value needs updating. The previous solution was to delete the data associated with the old key value and re-insert it with a new key value. The goal of this enhancement is to allow row movement both within a shard and between shards.

When the sharding key value on a particular row of a sharded table is updated, Now moving the data to a new location is handled by Oracle Globally Distributed Database, whether it is in a different partition on the same shard or on a different shard.

This feature provides you with the flexibility to update the sharding key without worrying about the destination of the records, because this feature allows Oracle Globally Distributed Database to take care of the row movement regardless of the row destination, which could be on a different shard.

Streamlined Data Updates

In a global e-commerce platform with sharded tables, automatic data movement on sharding key updates helps ensure seamless transitions. For instance, when customers relocate, their order history effortlessly shifts to the new region's shard, eliminating manual intervention. This dynamic reallocation empowers businesses with efficient sharded table management, maintaining data integrity and uninterrupted user services amidst changes.

4. Fine-Grained Refresh Rate Control for Duplicated Tables

Fine-grained refresh rate control for duplicated tables is a powerful feature that enables refresh rate control for individual duplicated tables. This feature allows configuring varying refresh intervals during table creation or via the ALTER TABLE statement. By tailoring refresh rates to data change frequency, resource utilization optimization is achieved. This capability enhances system performance and efficiency by customizing refresh rates per duplicated table.

Customized Data Refresh

In complex data environments, where data change rates vary across tables, fine-grained refresh rate control proves indispensable. Imagine a sales database with high-frequency transaction tables and reference tables that change less often. With this feature, high-transaction tables can be set to refresh more frequently, allowing real-time insights. Simultaneously, reference tables refresh less often, conserving resources. This customization maximizes efficiency, streamlining resource allocation, and bolstering system performance.

5. Synchronous Duplicated Tables

The introduction of synchronous duplicated tables offers a robust mechanism for synchronizing duplicated tables across all shards. This feature introduces a new kind of duplicated table that is synchronized on the shards ‘on-commit’ on the shard catalog. The synchronization occurs when active transactions executing Data Manipulation Language (DML) operations on the duplicated tables in the shard catalog are committed. This feature provides impeccable data consistency and real-time synchronization across all shards, underscoring a heightened level of data integrity.

Ensuring Data Consistency in Real-time

In data-intensive environments, like financial systems, the synchronous duplicated table feature plays a crucial role. As transactions span multiple shards, this feature provides instant synchronization of duplicated table data across all shards upon transaction commitment. Financial data remains uniformly accurate, reducing disparities and delivering real-time insights. Particularly vital in precision-dependent sectors, this feature enhances data integrity and reliability in distributed systems.

6. Sharded Database Coordinated Backup and Restore Enhancements

Coordinated backup and restore functionality in Oracle Globally Distributed Database has been extended to include the following:

  • Enhanced error handling and diagnosis for backup jobs
  • Improved automation of sharded database restore
  • Support for running RMAN commands from GDSCTL
  • Support for using different RMAN recovery catalogs for different shards
  • Encryption of backup sets
  • Support for additional backup destinations: Amazon S3, Oracle Object Storage, and ZDLRA

The benefits of this functionality are:

  • Easily diagnose problems in backup jobs
  • Backups sets can be encrypted so that the data is secure
  • Support for additional destinations other than on-disk storage
  • Support for different RMAN catalogs and destinations to abide by data residency requirements

This feature enhances diagnosability and automation in backup and restore jobs while securing data with encryption and supporting additional backup destinations.

Robust Data Protection and Recovery

Imagine a scenario where a sharded e-commerce platform faces a catastrophic data loss event. By utilizing the enhanced coordinated backup and restore functionality, the system gains superior error handling, automated restoration processes, and broader backup destination options such as Amazon S3 and Oracle Object Storage. Additionally, encrypted backup sets enhance data security. This feature helps ensure swift diagnosis of backup issues, safeguarded data integrity through encryption, and efficient data restoration for minimal downtime and maintaining operational resilience.

7. Parallel Cross-Shard DML Support

The Oracle Globally Distributed Database query coordinator can run cross-shard updates and inserts in parallel on multiple shards.

This feature improves cross-shard DML performance by running updates and inserts in parallel rather than serially.

Online Retail Inventory Management

In an online retail business with a globally distributed database, Oracle's Parallel Cross-Shard DML Support plays a crucial role in managing inventory. When restocking products or updating prices across multiple geographical regions, the feature allows simultaneous updates and inserts into different shard locations. This means that inventory data remains synchronized, prices are adjusted in real-time, and customer orders are processed efficiently, providing a seamless shopping experience for customers while optimizing inventory management for the retailer.

8. Automatic Parallel Direct Path Load Using SQL*Loader

SQL*Loader enables direct data loading into the database shards for high speed data ingest. SQL*Loader can load data faster and easier into Oracle Database with automatic parallelism and more efficient data storage.

With this release, SQL*Loader client can automatically start a parallel direct path load for data without dividing the data into separate files and starting multiple SQL*Loader clients. Instead of preparing your tables manually for parallel loads and setting the PARALLEL parameter, you can perform the same task automatically by running SQL*Loader with just one command, setting the degree of parallelism using the DEGREE_OF_PARALLELISM parameter, and setting DIRECT=TRUE.

High-Volume Data Ingestion for Financial Analytics

In the context of a financial services organization, managing vast volumes of market data from various sources is paramount for timely and accurate analytics. With the Automatic Parallel Direct Path Load feature using SQL*Loader, the organization can seamlessly ingest massive datasets into its Oracle Globally Distributed Database. Instead of labor-intensive manual preparation, SQL*Loader simplifies the process and an organization achieves efficient, high-speed data ingestion for real-time financial analysis, enabling informed decision-making and competitive advantage.

To conclude, Oracle Database 23ai brings groundbreaking advancements to the world of database technology. These innovations, with a keen focus on optimizing the Oracle Globally Distributed Database, are set to revolutionize the world of distributed database operations.

From the dynamic capabilities of Raft Replication to the agility of Directory-Based Sharding, these features redefine how businesses manage data across regions. Automatic Data Move on Sharding Key Update provides seamless transitions in evolving scenarios, while Fine-Grained Refresh Rate Control optimizes resource utilization. The Synchronous Duplicated Tables' near real-time data consistency enhances reliability. Coordinated Backup and Restore Enhancements reinforce data protection, while Parallel Cross-Shard DML Support revolutionizes cross-shard data management by allowing parallel updates and inserts, boosting efficiency. Additionally, Automatic Parallel Direct Path Load Using SQL*Loader simplifies high-volume data ingestion, benefitting financial analytics and decision-making processes for organizations dealing with vast market data.

Oracle Database 23ai doesn't just mark an upgrade; it signifies a new era where these features empower businesses to embrace the potential of distributed data scenarios, all underpinned by the reliability of the Oracle Globally Distributed Database.

Source: oracle.com

Friday, May 10, 2024

OCI multicloud solutions with Megaport Cloud Router

OCI multicloud solutions with Megaport Cloud Router

Organizations are rapidly moving and scaling their applications into the cloud ecosystem. Enterprise customers who want to optimize and modernize their operations in this cloud ecosystem need interconnectivity to and between multiple cloud service providers (CSPs). While several architectures are available, demand from enterprise customers for split-stack multicloud deployments, where an analytics application runs on one cloud and the data resides on another cloud, are on the rise, especially to support data integration from disparate sources and reporting using the powerful Oracle Analytics Cloud (OAC) platform. The enterprise analytics application user or the line of business (LOB) decision-maker benefits from the modernized connecting and reporting across best-in-class cloud providers’ applications without having to incur expensive migration, data replication, and data redundancy costs.

The described scenario can be accomplished horizontally across any industry and between any CSP’s platform connecting to the OAC platform. This blog post provides a solution that drives economies of scale for the customer’s increasing analytics needs.

Megaport Cloud Router


The Megaport Cloud Router (MCR) is a virtual routing appliance, which delivers a fast, secure, and scalable solution to connect multiple cloud platforms through private network connections in a colocation facility. Coupled with private network solutions, such as Oracle FastConnect and Amazon Web Services (AWS) Direct Connect, the MCR bypasses the public internet and enables cloud-to-cloud connectivity, purpose-built for high throughput and predictable performance. Data moves between multiple public cloud platforms directly, reducing end-to-end latency between Oracle Cloud Infrastructure (OCI) and other cloud platforms for data migrations or steady-state split-stack architectures.

Why Megaport for Oracle multicloud implementations 


Megaport’s multicloud connectivity solution connecting through its virtual cloud router for Oracle enables OCI Database services, such as Autonomous Database and Exadata Database Service on Dedicated Infrastructure, with cloud-to-cloud connectivity to other CSPs, such as Microsoft Azure, AWS, and Google Cloud Platform (GCP). This connectivity benefits the coexistence of best-of-breed applications that can span multiple clouds and helps organizations realize better performance and scalability, while helping to ensure efficiencies in interoperability and availability.

Customers gain the following capabilities by using the Megaport virtual cloud router solution for Oracle:

  • Ability to move workloads to hybrid cloud architecture ecosystems.
  • Run workloads on low-latency, highly reliable (five nines availability) connectivity between apps and data, especially for data consolidation, integration, and analytics workloads.
  • Bypass public internet traffic with dedicated connectivity between client and provider data center networks.
  • Multicloud architecture with both full and split stacks.

Oracle multicloud: Split-stack architecture use case enabled by MCR


To test the MCR solution for multicloud connectivity, we built a split-stack multicloud architecture use case with the application stack running OAC on OCI, predominantly used for analytics and reporting by application users. We built another stack on Amazon Redshift, acting as a data warehouse that encompasses trend data and streaming data from multiple data feeds and downstream systems.

The three primary elements of this network architecture are Megaport Cloud Router (MCR), Megaport Virtual Cross Connect (VXC) to OCI FastConnect, and VXC to AWS Direct Connect.

OCI multicloud solutions with Megaport Cloud Router
Figure 1: Architecture Diagram for example solution connecting Amazon Redshift to Oracle Analyics Cloud using Megaport Cloud Router

Megaport’s cloud router solution made it possible to read and report on multicloud data sources through OAC’s advanced analytics and visualization capabilities. Organizations across many industries can use this scenario to achieve better performance and cost efficiencies for analytics.

This solution includes the following benefits:

  • Ability to run data analytics at the source.
  • Modern analytics reporting with real-time data and faster delivery of reports.
  • Increased throughput and sub 5-millisecond latency according to standard observations depending on location of cloud regions and onramps. In some cases, it can be lower depending on the architecture and gerographic regions. 
  • Dramatically improved data transfer rates from several hours to few minutes. 

Source: oracle.com

Tuesday, May 7, 2024

Transportable Binary XML – modern XML document storage in Oracle Database 23ai

Traditional XML storage in Oracle Database


In 2010, Oracle Database introduced native XML storage capabilities to optimize the storage and usage of XML documents with Oracle Database 11g (11.2.0.2). Oracle's approach for native XMLType storage then was purely document-centric, called Compact Schema-Aware XML (CSX) or Non-transportable Binary XML. This binary format was built on a central token table set approach where every XML document is encoded in binary format, and the keys to encode and decode the binary data are stored in a single, central dictionary. Such a design is excellent for the storage and performance within a single database. There is no duplication of work for encoding and decoding tokens, and there is always just one reference. Since hashing of tokens is one of the most expensive tasks, this approach saves a lot of time. However, as a natural consequence, every operation involving the decoding of binary XML data needs to access the central dictionary.

What is Transportable Binary XML


Although CSX succinctly compresses XMLType data, its use of a central dictionary (token table) and schema registries prevent an easy adoption for distributed and remote architectures, such as sharding, cross containers, remote database links, or even robust import/export capabilities. Any scenario where the central dictionary is not directly accessible imposes a challenge. To overcome these challenges, Oracle Database 23ai introduced Transportable Binary XML (TBX) as a storage option, a variant built on top of CSX but without the dependency of a central dictionary.

TBX is far more flexible and scalable without this dependency, enabling binary stored XML documents to be transportable and usable in distributed environments. Transportable Binary XML is the recommended method for storing XML documents natively in the Oracle Database beginning with Oracle Database 23ai. The following will walk you through how to use Transportable Binary XML and how to migrate earlier legacy binary XML storage formats.

Working with Transportable Binary XML


Beginning with Oracle Database 23ai, Transportable Binary XML is the default XML storage type. You do not need to explicitly specify the storage type of your XML columns. However, if you want to specify TBX explicitly, the DDL looks as follows:

CREATE TABLE tx( ID NUMBER, XMLDOC XMLTYPE) 
XMLTYPE COLUMN XMLDOC STORE AS TRANSPORTABLE BINARY XML;

To validate that a table has an XMLType column stored as TBX, you can just describe the table:

DESCRIBE TX 
Name                         Null?    Type 
------------------          -------- ----------------------------------------- 
ID                                         NUMBER 
XMLDOC                             SYS.XMLTYPE STORAGE TRANSPORTABLE BINARY

Transportable Binary XML provides full data processing compatibility with non-transportable binary XML storage. All XML operators and SQL generally continue to work like before without any behavior changes. Transportable Binary XML only changes how your XML documents are stored in the database and how XML documents are handled internally.

The only change of Transportable Binary XML is lifting existing constraints, enabling binary XML documents in modern architectures like Oracle Sharding.

Transportable Binary XML and Oracle Sharding


Sharding is a database architecture technique used to scale databases by partitioning data across multiple independent servers or instances, each holding a portion of the total data (shards). The shards are all coordinated by one instance (coordinator), where all the information is gathered and presented as a single database.

Transportable Binary XML – modern XML document storage in Oracle Database 23ai

This architecture is based on a shared-nothing architecture, meaning that each shard knows nothing about the other shards. Each shard could also be used as an independent, single database. Transportable binary XML as self-encapsulated, self-decoding/encoding binary storage on table level allows using a native XMLType with Sharding: it enables sending XML documents over the wire to any other database without limits. Transportable Binary XML is the only supported XMLType storage format in Oracle Sharding environments; specifying other XMLType storage types will throw an error.

To create a sharded table with an XMLType column using Transportable Binary XML, the DDL looks as follows:

CREATE SHARDED TABLE SHARDEDTAB
   ( SHDKEY NUMBER NOT NULL, 
     CTRY_CODE VARCHAR2(3) NOT NULL, 
     XMLDOC XMLTYPE, 
     CONSTRAINT SHARD_PK PRIMARY KEY (SHDKEY, CTRY_CODE)
    ) 
PARTITION BY LIST (CTRY_CODE) 
    ( PARTITION P_REG_1 VALUES (‘RG1’) TABLESPACE TBS1, 
      PARTITION P_REG_2 VALUES (‘RG2’) TABLESPACE TBS2, 
      PARTITION P_REG_3 VALUES (‘RG3’) TABLESPACE TBS3 
     ) 
XMLTYPE COLUMN XMLDOC STORE AS SECUREFILE TRANSPORTABLE BINARY XML;

Your table will be sharded across all participating databases (shards), using the new Transportable Binary XML as storage format for your XML documents without the need of a central repository. Needless to say that TBX is also supported in system or composite sharding environments.

Transportable Binary XML and Search Indexes


Hand in hand with TBX, Oracle Database 23ai introduced new, simplified SQL syntax for XML Search Indexes specifically for TBX. Whenever you require full-text and/or range-search capabilities over large, unstructured XML documents and you adopted the new Transportable Binary XML storage format, Oracle recommends that you use XML Search Index to index your XML data.

To create an XML search index for both full-text and range-search, you can use syntax similar to the following DDL:

CREATE SEARCH INDEX myXMLDocumentsSearchIndex 
ON myXMLDocumentsTable(myXMLTypeColumn)
FOR XML PARAMETERS ('SEARCH_ON TEXT_VALUE (BINARY_DOUBLE, VARCHAR2, TIMESTAMP)');

This example enables both the full-text and range-search components for the specified data types BINARY_DOUBLE, VARCHAR2, and TIMESTAMP.

If you are unsure about your workload and business requirements it is recommended to build the index for search and range scans for common data types in your XML documents.

The use cases of a search index for full text search and range-search using relational operators (>, <, <=, >=, or =) in an XMLExists expression within a SQL where clause are slightly different in nature of internal processing, so you can optimize your XML search index structure for your specific requirements.

If you are aiming solely for text search, you can create your XML search index by specifying the FOR XML clause in the CREATE SEARCH INDEX statement. As mentioned before, you can create such an XML search index only on XML documents stored as TBX and you must be granted the CTXAPP database role.

The syntax to create a search index to solely index documents for text search is as simple as the following example.

CREATE SEARCH INDEX myXMLDocumentsSearchIndex 
ON myXMLDocumentsTable(myXMLTypeColumn) 
FOR XML;

OR, using the more verbose syntax. You would only do this for clarity reasons; this is the default, as seen in the previous example:

CREATE SEARCH INDEX myXMLDocumentsSearchIndex 
ON myXMLDocumentsTtable(myXMLTypeColumn) 
FOR XML PARAMETERS (‘SEARCH_ON TEXT’);

If you are aiming to build your index solely for range scans within your XML documents, you simply specify the list of datatypes that you intend to search on:

CREATE SEARCH INDEX myXMLDocumentsSearchIndex 
ON MyXMLDocumentsTable(myXMLTypeColumn) 
FOR XML PARAMETERS ('SEARCH_ON VALUE (BINARY_DOUBLE, VARCHAR2, TIMESTAMP)');

Conversion to Transportable Binary XML


While it’s easy to see how to adopt TBX for future applications and systems, many existing applications built using XML storage in the Oracle Database will be upgraded to Oracle Database 23ai. It is recommended to migrate all your tables using a legacy XML storage format to TBX.

There are different options to do this migration:

◉ You can do a simple CTAS (Create Table As Select), casting the legacy XML datatype to TBX. This is the most pragmatic approach. However, it introduces downtime for your application and requires you to manually rebuild all dependent structures, such as indexes.

◉ Online Redefinition is similar to the CTAS approach, but enables your migration to happen in an ONLINE mode.

◉ DataPump has specific import parameters to do the storage migration at data import time, namely TRANSFORM = XMLTYPE_STORAGE_CLAUSE: '" TRANSPORTABLE BINARY XML"'.

◉ GoldenGate, Oracle’s flagship product for real-time data integration and replication in heterogeneous IT environments. This method is only applicable if you are moving your whole database. 

Source: oracle.com

Sunday, May 5, 2024

Oracle Announces General Availability of AI Vector Search in Oracle Database 23ai

Oracle Announces General Availability of AI Vector Search in Oracle Database 23ai

Oracle AI Vector Search is a novel capability that allows users to search data based on the semantics or meaning of data, in addition to by the values of data, such as attribute values or keywords, as databases have traditionally supported.

A vector, or vector embedding, is a popular data structure used in AI applications. A vector is a list of numbers, generated by deep learning models from diverse data types (e.g. images, documents, videos, etc.), that encodes the semantics of the data.


Oracle AI Vector Search allows you to generate, store, index, and query vector embeddings along with other business data, using the full power of SQL. As an example, for searching documents, vector search is often considered more effective than keyword-based search, as vector search is based on the meaning and context behind the words and not the actual words themselves. 

Oracle AI Vector Search allows you to combine semantic document search with searches on structured document properties. For example, in a database of technology articles, a question such as “find articles about fine-tuning Large Language Models (LLMs) for enterprise use cases that have been published in the last 5 years by a certain author and a certain publisher in a certain country”, requires searching both the article text as well as article attributes, that may be present in one or more tables.

Oracle AI Vector Search includes a collection of powerful capabilities to enable semantic search for business use cases. These features include

  1. New SQL operators to generate vector embeddings from unstructured data
  2. A new first-class VECTOR data type for storing vector embeddings
  3. New state-of-the-art Vector Indexes for fast approximate searches
  4. New SQL operators, and syntax, to easily express similarity search in business queries
  5. Support for the Full Generative AI pipeline including preprocessing and vectorizing data, and augmenting LLMs with business data

The VECTOR data type is fully integrated in SQL and PL/SQL, and is supported across multiple clients and programming languages, with native binding capabilities in python-oracledb, node-oracledb, JDBC, and ODP.NET drivers. This comprehensive support provides seamless vector search functionality across multiple development environments.

Oracle AI Vector Search is also fully integrated in popular 3rd party Generative-AI frameworks such as LangChain.

Oracle AI Vector Search includes native APIs to make REST callouts to LLM APIs for content generation (like text) or summarization and other operations used in the Generative-AI pipeline. These new capabilities allow seamless support for Retrieval Augmented Generation (RAG), a breakthrough generative AI technique that augments large language models (LLMs), with private business data, to deliver accurate responses to natural language questions on business data.

Benefits of Oracle AI Vector Search


Oracle Database is a leading repository of operational and enterprise data. Enterprise applications usually need to search a combination of business data and unstructured data.  For example, a retail website could feature searches based on a natural language product description and a target product image, along with other filters, such as price, store location, manufacturer, and current availability. This search requires simultaneously searching unstructured catalog data (product description and image), structured catalog data (price, store location and manufacturer) as well as real time transactional data (such as current inventory).

The combination of the converged capabilities of Oracle Database, and Oracle AI Vector Search, provides several unique benefits.

Seamless Combination of AI Vector Data with Your Business Data

This is a key benefit of Oracle AI Vector Search, since it lets users run AI-powered vector similarity searches within their existing Oracle Databases instead of having to move business data to a separate vector database. Avoiding data movement can reduce complexity, improve security, and enable searches on current data.

Oracle AI Vector search allows far more powerful searches than most dedicated Vector databases, by combining sophisticated business data search with AI vector similarity search using simple, intuitive SQL and the full power of converged database – JSON, graph, text, relational, spatial, etc. all within a single query.

Powering Retrieval Augmented Generation with Business Data

Vector Databases improve interactions with LLMs since they provide scenario-specific private context to LLMs to obtain more accurate answers. This is a well-known workflow referred to as Retrieval Augmented Generation (RAG). 

Oracle AI Vector Search also leverages the full power of business data to further refine LLM interactions, making use of business criteria such as security filters, business metrics and business rules, resulting in ultra-sophisticated RAG for the Enterprise.

Support for the Full Generative AI Pipeline for Business Data

Oracle AI Vector Search supports native database APIs to perform all aspects of the generative AI pipeline, from end to end, making it easier for your developers to build next-gen AI applications using your business data, directly within Oracle Database. 

Unique Combination of AI Vector Search and Full Machine Learning Suite

Oracle Database offers both a full suite of in-database machine learning algorithms as well as similarity search on AI vectors. This combination enables Oracle Database to handle a very wide range of AI use cases involving machine learning actions (decisions, predictions, classification, forecasts, etc.) as well as the power of AI-based vector search. For instance, it is easy to combine inference and classification with AI Vector Search, within the same SQL query.

Proven, Enterprise-Class Scalability, Fault Tolerance and Security

Oracle Database is a leading repository of business data, and the combination of business data and semantic search is what enterprises need to implement artificial intelligence solutions. AI Vector Search is built into Oracle Database and leverages:

  • Partitioning, RAC, Sharding and Exadata for proven, industrial-strength scalability.
  • Extreme HA and DR technologies like Data Guard, Golden Gate, Flashback, RMAN, ZDLRA and more.
  • Cutting-edge security with Oracle Advanced Security including features such as Transparent Data Encryption, Key Vault, Audit Vault, Virtual Private Database and more.

Example Use Cases


Oracle AI Vector Search enables the combination of search on semantic and business data resulting in more-accurate answers quickly, and securely. With the addition of AI Vector Search to Oracle Database, users can quickly, and easily get the benefits of artificial intelligence without sacrificing security, data integrity or performance.

Use cases include:

  • Conversational AI, or Chatbots: Build AI-powered digital assistants
  • Similarity Search: Match customers with products
  • Content-Based Filtering: Enable personalized recommendations, locate retail items from pictures
  • Natural Language Processing: Text classification and clustering SQL generation
  • Data Analysis: Anomaly detection, pattern recognition
  • Computer Vision: Face recognition, biometric identification, object detection
  • Biomedical Research: Gene/DNA similarity research, molecular structure search
  • Geographic Information Systems: Spatial analysis, map rendering
  • Industrial Applications: Quality control, predictive maintenance, machinery malfunction

Summary

Oracle AI Vector Search, with Oracle Database, enables a new class of applications making it possible to transform traditional business processes by enabling semantic searches using LLMs augmented with existing business data.

  • New SQL operators, and syntax, enable you to easily combine relational search, on business data, with semantic search on unstructured data
  • AI-powered vector similarity searches using Oracle Database – no need to move business data to a separate vector database
  • Easily utilize Retrieval Augmented Generation (RAG) to augment LLM responses with your enterprise specific content
  • Enhance your applications with the enterprise-class security, scalability, and partitioning capabilities of Oracle Database

Source: oracle.com

Saturday, May 4, 2024

Announcing Oracle Database 23ai : General Availability

General Availability 


We are pleased to announce the general availability of Oracle Database 23ai. Over the last four years, Oracle Database Development has worked hard to deliver the next long-term support release of the Oracle Database, with a focus on AI and developer productivity. Given the focus on AI in this release of the database, we decided to change the database's name from Oracle Database 23c to Oracle Database 23ai. This reflects the focus of this release as well as the climate in which it is being released. 

Announcing Oracle Database 23ai : General Availability

Game-Changing Innovations


Oracle Database 23ai has focused on three key areas.

◉ AI for Data
◉ Dev for Data
◉ Mission Critical for Data

In this Blog, we'll describe some of the critical features of this release that highlight our work on these important focus areas and provide details when you see them on your platform of choice.

AI for Data


Our goal with AI for Data is two-fold:

1. To enable app developers to add AI functionality into their data-driven applications more easily
2. To incorporate GenAI capabilities into our products so that all users of Oracle Database, from data analysts to app developers and DBAs, can be more productive.

This is achieved by employing AI to streamline Oracle's data management processes, offering AI algorithms for uncovering new insights from your data, facilitating natural language interactions for database queries, and empowering users to store AI-generated vectors for swift and efficient object similarity searches. Let's delve into these features further.

Augmenting a new generation of AI models

People are feeling the impact of AI Large Language Models (LLM), exemplified by offerings such as ChatGPT, Google Gemini, Cohere, and LLaMA. Whilst LLMs are having a profound impact on the way we perform everyday tasks, one of the challenges that these engines face is that they are restricted to answering questions in the specific time window of their creation. They also lack context and details of the data held within your organization. To make these and other LLMs useful, we need to augment their existing understanding with data relevant to the questions you ask about the data held within your database. 

In Oracle Database 23ai, we are introducing AI Vector Search, a powerful new technology that enables you to leverage a new generation of AI models to generate and store vectors. These vectors, sometimes referred to as embeddings, are multi-dimensional representations of documents, images, videos, sound, etc. By encoding these objects as vectors, you gain the ability to look for similarities between them using mathematical calculations. The real power of Oracle Database23ai's solution is that you can combine these similarity searches with searches on your business data using simple SQL. Anyone with a basic understanding of SQL can create a powerful statement combining similarity and other search criteria. These types of queries provide LLMs with additional context, augmenting their knowledge and making their responses more accurate and relevant to your customers' or organizations' questions. To enable this functionality, we've added a new data type, new vector indexes, and extensions to the SQL language to make it incredibly simple to query vectors alongside your existing business data by leveraging Oracle Database 23ai's advanced analytical capabilities.

Announcing Oracle Database 23ai : General Availability

Secure encoding of data

To enable the considerable benefits that LLMs offer, we first need to enrich our understanding of our datasets and the objects within them. The models to encode these objects are potentially large and complex pieces of code. As a result, it has become common practice to offload this processing to third-party services. This can require you to share potentially sensitive information with third parties with the inherent risks that entails.

To ensure the secure encoding of objects, Oracle Database 23ai allows you to load your own trusted AI models directly into the database through its support of the ONNX standard. This enables Oracle Database 23ai to encode objects as they are inserted into the database. This enables the secure near real-time inferencing of objects and ensures that data does not need to be extracted from the database and handed off to a third-party service.

Asking questions naturally

While SQL is an incredibly powerful language, it can be a little challenging to get started with. To enable a broader range of users to ask the most complex questions of the Oracle Database, we are integrating with LLMs such as Cohere and Llama to allow you to ask questions using natural language.  So you can simply ask a question like "Show me the last 4 quarters' sales of products that are popular with the younger generation". Oracle Database 23ai will share the table's metadata to answer the question with the LLM along with the user's question. The LLM understands the meaning of "younger generation" and converts it into a data range as a filter in the SQL query, which it returns to the database. We, of course, aren't limiting Oracle Database 23ai to just allowing you to query the information within the database. You'll also have the ability to ask questions on all aspects of the Oracle Database. 

Finding new insights in data

Since the release of Oracle Database 9iR2 over 20 years ago, the database has featured built-in Machine learning (ML) algorithms, enabling you to quickly look for patterns and trends in data held within its tables and predict customer behaviors. These ML algorithms give you the ability to use sophisticated ML algorithms without the need for complex ETL operations to extract the data and write back results. These models could then be used to classify, cluster, and predict as your data is inserted or loaded into the Oracle Database, providing tangible business benefits like customer recommendations and fraud detection. Since that release, we've improved and added new ML algorithms and capabilities to the Oracle Database, creating one of the industry's most sophisticated and capable data mining platforms.

Available in all editions of the Oracle Database

AI Vector Search is part of Oracle Database 23ai and is available at no additional charge in Enterprise Edition, Standard Edition 2, Database Free, and all Oracle Database cloud services.

Feedback from early testers

AI Vector Search generated a great deal of interest even before the launch, and many customers and partners were keen to try out and provide feedback on the latest capabilities like AI Vector Search. Here's a sample of the feedback we received.

“We are happy to see AI Vector Search added to Oracle Database. We appreciate that we can run AI Vector Search in the same Oracle Database as our other workloads, which allows us to provide a reliable and secure solution.”

Shinichiro Otsuka, NRI Certified IT Architect, Nomura Research Institute, Ltd.

“AI Vector Search changes the way we think of the business by bringing AI to your data: for instance we can use natural language to query our documentation to find answers to questions customers are asking. This makes the process of serving customers much faster and the quality of the service improves as well. Being able to use the power of Generative AI with our own data makes a huge difference."

Heli Helskyaho, CEO, Miracle Finland Oy

“We have been consulting on various business transformation projects using advanced digital technology. Oracle Database 23ai AI Vector Search is very simple to implement by adding a vector column to the current relational database system. I am thrilled that the vector data is within a single record with existing data so that similarity reordering can be done with a single SQL statement. This makes it easy to combine large language models and company data to create and operate enterprise-level retrieval augmented generation systems.”

Shigeru Urushibara, Chairman, UL Systems Inc.

"With the decreasing domestic workforce in Japan, XCAT‘s customers want to adopt labor-saving measures. Oracle Database 23ai’s AI Vector Search allows customers to use SQL for vector retrieval, making it an excellent tool for engineers with little or no AI knowledge to handle vector data. In addition, the ability to manage AI data at no additional cost is a major attraction for many Oracle Database customers."

Mitsunori Yamane, President, Cross Cat Co., Ltd.

Dev for Data

Oracle Database 23ai focus was to make the experience of developing applications simpler by removing the complexity associated with your database interaction. Removing complexity from the application development process means you get more opportunities to focus on the intricacies of creating elegant applications that meet your customer's requirements rather than getting bogged down in technical details. Moreover, reducing complexity can lead to faster development cycles, this is crucial in today's fast-paced digital landscape, where market demands can shift rapidly.

JSON or Relational, a difficult choice?

Oracle 23ai introduces a number of key technologies to reduce the complexity for developers. Perhaps the most innovative and important of them is the introduction of JSON Relational Duality. This technology allows you to leverage the power of relational and the simplicity of JSON development approaches all within a single app. JSON provides an elegant data modeling approach where all of the relevant data needed to answer a query is contained in a single object without the need to perform complex joins across tables. The relational approach provides a flexible, storage-efficient, consistent data model that is easy to query with languages such as SQL. Historically the problems come when you are forced to choose which database modelling approach to take at the start of your application lifecycle. Decisions made at this stage may have implications much later on as the business requirements change. The beauty of JSON Relational Duality is that you can benefit from both approaches without the need to use complex and unwieldy Object Relational Mapping frameworks (ORMs). 

By creating simple JSON Duality views on top of relational tables you can build applications that use documents to query and update the underlying data sets. Data duplication, a fundamental issue in document modeling, is avoided, and even the complexities of database-level concurrency control are hidden from you as Oracle Database 23ai manages document-level serializability on your behalf. You can continue to use simple HTTP PUT, POST, and GET operations or use language-specific API such as Oracle's SODA API or even MongoDB API directly against the Oracle database. With JSON Duality Views the old phrase of "You can't have your cake and eat it" no longer holds true.

Announcing Oracle Database 23ai : General Availability

SQL just got a little easier

SQL remains one of the most popular development languages in use with application developers today. Its versatility when asking the simplest or most complex questions of your business data has made it the cornerstone of data management, a position it is likely to hold for the foreseeable future. That is not to say there are areas where it could be improved. In Oracle Database 23ai we listened to common enhanced requests and looked at what could be made simpler or offer more compelling ways to interact with the database. Examples of just a few of the SQL improvements we've made include the addition of two new datatypes "Boolean" and "Vector", we added "Data Usecase Domains" to allow you to enrich the meaning of datatypes used in table definitions, the removal of the need for "from dual" in simple SQL statements to improve readability, making it easier to aggregate over the "interval" datatype, the introduction of table value constructors to make it easy to specify multiple rows in insert select or merge statements. These are just a few of the many improvements we've made to SQL.

As with AI Vector Search, we also appreciate receiving a lot of useful feedback from customers and partners who participated in the Oracle Database 23ai Beta program. Here's a sample of the comments we received -

“JSON Relational Duality Views are a game changer for application development by finally solving the problem of object-relational mapping. And, we at last have ACID-compliant transactions in a multi-tier or web architecture.”

Peter de Vaal, Principal Consultant, Transfer Solutions

“JSON Relational Duality gives you the best of both worlds: Relational experts can work on the same data as Document database experts without having to learn a new skill. App developers have the flexibility they need, and database management is simpler. Oracle has taken a massive leap beyond other databases.”

Patrick Barel, Sr. Oracle Consultant, Qualogy

“Oracle Database 23ai with JSON Relational Duality Views and Oracle APEX have allowed us to create full-featured, standards-compliant applications for working with JSON healthcare data.”

Rade Pobulic, Technical Director, VDEL Informationstechnik & Consulting GmbH

Property Graphs modelling complex relationships

Graph databases provide a fresh perspective on modeling intricate relationships found in real-world scenarios. Yet, until recently, developers grappled with proprietary languages and having to ship data tp databases tailored for managing these relationships. This hindered the widespread acceptance of this groundbreaking technology. Fortunately, the industry has taken a collaborative approach to bring graphs to the masses, culminating in the establishment of standards. These standards empower developers with the versatility and familiarity of SQL, fostering a more accessible landscape. Oracle Database 23ai stands as the pioneering commercial database to embrace this newfound standard. With these advancements, we anticipate a significant surge in the integration of Graph databases within enterprise ecosystems.

As with JSON Duality Views, you can express your intent on how you would like to use your data held within existing relational tables or your JSON collections through the user of property graph views. With a simple view, you can enrich the data to model the potentially complex relationships that your data holds. A new SQL extension makes it much simpler to write powerful queries to find a deeper understanding of information that would have been hard to describe using standard SQL. We've also added a new set of sophisticated graph algorithms (shortest path, classification, connects, etc. ), which will be released shortly after GA.


Announcing Oracle Database 23ai : General Availability

The property graph Property Graph is available in all editions of Oracle Database 23ai.

Mission Critical for Data


Oracle Database is renowned for powering some of the world's most vital applications. Over the years, it has established itself as a stalwart guardian of businesses' most precious asset: data. Unrivalled in its breadth of features, Oracle Database excels in safeguarding critical systems against unforeseen downtime. A prime example is Oracle Real Applications Clusters (RAC), a cutting-edge technology that enables all-active, shared disk databases, ideal for the most mission-critical scenarios. Oracle Active DataGuard and Oracle GoldenGate offer unparalleled flexibility in crafting both homogenous and heterogeneous architectures for data replication. 

Shard better, faster, simpler

For use cases where businesses are looking to distribute their data over larger distances, either for regulatory reasons where the data of users must be stored in the country the customer resides in or to reduce the latency of access associated with globally distributed applications: We introduced support for database sharding in Oracle Database 12c. Sharding distributes a dataset across a number of Oracle databases but is managed as a single logical data set. This sharded architecture allowed the database to be scaled up or down by adding and removing shards and allowing Oracle to automatically rebalance the dataset. Oracle is able to do this online and with little impact on the business as the concept of sharding is baked directly into the database.

In Oracle Database 23ai our Globally Distributed Database technology introduces support for Raft replication. This is a consensus-based protocol that facilitates the automatic configuration of replication across all shards. With raft, replication holds copies called replication units across all of the shards. In the advent of a shard failure or reconfiguration, Oracle Database 23ai automatically rebalances the data. The new Raft protocol also enables sub-second failover to ensure continued business continuity. 

Announcing Oracle Database 23ai : General Availability

Oracle 23ai brings a number of improvements across the board for our high availability products, such as the new "Local Rolling Database Maintenance" to simplify the impact of rolling patches in a cluster by standing up another instance on the same node that is receiving the patch. We are also introducing support for a new Data Guard Per Pluggable Database (PDB) allowing Pluggable Database level disaster protection between two Container databases (CDB) with each CDB running an active workload. We've also improved the integration and management of PDBs within Oracle Clusterware. 

Caching data made simple

Caching data in the application tier can offer considerable benefits. It is often used to make applications more responsive and reduce the load on the database, as queries are offloaded to the cache typically located closer to the code. However, to achieve these benefits, developers face a number of challenges; one of the biggest is ensuring that the cache is consistent with the data held within the backend database or risk serving stale and potentially incorrect data. Developers are often forced to create complex code to manage these scenarios and often have to resort to design patterns such as "time to live" where data is periodically flushed from the cache and reloaded. These and many other challenges often mean the cache becomes difficult and expensive to maintain and, in some instances, a bigger problem than the one it was designed to solve.

In Oracle Database 23c we are looking to solve the problems of caches built against the Oracle Database with a new feature called "True Cache". True Cache is a diskless Oracle Instance running in front of the primary database. The True Cache instances leverage Active Data Guard technology to ensure it is automatically updated as data changes in the primary database instance. One of the most important features of this new caching technology is its simple configuration and minimal code changes that are needed to leverage the benefits it offers. 

Announcing Oracle Database 23ai : General Availability

Making SQL execution safer

One of the challenges that organisations face is continued attempts by malicious actors to steal data or disrupt their day-to-day activities. In Oracle Database 23ai, to prevent the execution of unauthorised SQL, be they via SQL-Injection attacks or simply by unauthorised staff, we are introducing SQL Firewall. SQL Firewall allows you to train the Database on what SQL is permitted to be executed. The "allow list" of SQL can then be used to either log unauthorised SQL or blog its execution. Additional criteria can be added to allow exceptions for IP ranges or authorised calling programs. The power of SQL Firewall is that it is part of the Oracle Database, and as a result, it imposes very little overhead on the execution of SQL. Setting up and training SQL Firewall is incredibly simple being able to be done from a GUI or via a few simple calls to stored procedures. 

Announcing Oracle Database 23ai : General Availability

Over 300+ new features


I discussed the cloud release of Oracle Database 23ai and described some of the 300+ new features. Some other notable features include 

  • Java Script Stored Procedures
  • Priority Transactions
  • Data Usecase Domains
  • Schema privileges
  • Annotations
  • Boolean datatype
  • Developer Role
  • Read-Only-Per-PDB Standby
  • JSON Schema
  • Real-Time SQL Plan Management
  • Performance Improvements
  • Lock Free Reservations
  • Improved Microservice Support
  • XML and JSON Search Index Enhancements
  • And many many more

Platform Rollout

Oracle Database 23ai is now available on Oracle Exadata Cloud@Customer, OCI Exadata Database Service and OCI Base Database Service. It is also available in the Azure Oracle Database Service. For developers, Oracle Database 23ai is now available in Always Free Autonomous Database as well for download in the Autonomous Database 23ai Container Image and Oracle Database 23ai Free. We are also pleased to announce that Oracle GoldenGate 23ai and GoldenGate 23ai Free as also available for download. On-premises versions of Oracle Database 23ai for Linux (OL & RHEL 8/9) and Windows will be out shortly with other platforms rolling out over the coming months. For further details please check the Oracle Support note Doc ID 742060.1

The general availability of Oracle Database 23ai marks a new phase in this important release. Thousands of developers have contributed to its design, development and testing resulting in what we believe is the very best enterprise database in the market.

Source: oracle.com

Friday, May 3, 2024

Why run Oracle Database on Arm

Why run Oracle Database on Arm

Why run Oracle Database on Arm


CPUs or Central Processing Units have been the core talking point in the computing space. Moore's law ("the number of transistors in a dense integrated circuit doubles approximately every two years" still stays valid. Processor speed is always measured in terms of instructions per second. New CPU architectures now measure millions or billions of instructions per second. A rise in demand for mobile gadgets has also shaped the path of today's processors. Power consumption and heat production are two significant factors in a smaller form factor (mobile devices). In recent years, the technological landscape has witnessed a considerable rise in the popularity of Arm processors due to their unique low power consumption capabilities. RISC-based architectures, of which Arm is part, focus on simplicity and efficiency. The RISC-based architecture uses a simplified set of instructions, each performing a single operation, aiming to execute instructions quickly. Arm processors offer unique capabilities in the mobile and handheld segment, but they have now been realized to be helpful in the server market. In this blog, we will explore why Arm processors are better suited for desktops and servers and explore why relational databases can perform exceptionally well on Arm.

Arm-based computing started with mobile and embedded devices; the technology (Arm-based) has now evolved to support hyperscale data centers and cloud computing. Oracle began to offer Arm-shaped VMs because they scale linearly, provide predictable performance, and provide the highest density of cores, all at a lower price point. With Arm-based cloud computing, customers can run existing workloads less expensively and build new applications with superior economics and performance. To help developers transition, make, and run Arm-based workloads, Oracle and other cloud vendors have accelerated the Arm developer ecosystem with the best tools and platform possible. Arm can provide all the capabilities of x86 computing, including virtualization.

What about current workloads:

x86, for decades, has been a de-facto standard for running workloads of various types. Workloads over time have become quite complex, resulting in millions and billions of instructions per second. Arm, with its simple design, offers a complementary substitute for some of the workloads that run on x86 architecture. Oracle Databases running on x86 platforms can seamlessly migrate to Arm architecture using standard methods. Arm architecture provides the following benefits:

  • Efficiency and Power Consumption: Arm processors are renowned for their efficiency and low power consumption compared to x86 processors. Arm's reduced instruction set architecture (RISC) approach enables processors to execute instructions more efficiently, resulting in improved power efficiency and reduced heat generation. By consuming less power, Arm processors can allocate more resources to managing tasks, benefiting the overall performance of a system.
  • Technology trends: The needs of hyper-growth markets, such as cloud-based supercomputing and artificial intelligence, dictate that we turn to specialized hardware where we can add more servers into data centers while staying within energy budgets. Arm is highly customizable, meaning cloud providers can tailor chips to their needs rather than depend on chip vendors. Most cloud vendors are coming up with their implementation of Arm-based chips to fit their needs. For example, NVIDIA has introduced its Grace Hopper super chip, based on Arm, to deliver a CPU+GPU coherent memory model to accelerate AI and high-performance computing applications.
  • Scalability and Customization: Some of the Arm processors available in the market boast 128 cores per processor. One of the Arm vendors boasts 192 processor cores, the highest core count of any available data center server processor. Due to their scalability and customization capabilities, Arm processors have gained significant traction in the mobile and embedded systems markets. Unlike x86, Arm processors are designed to be highly customizable, allowing manufacturers to tailor them to specific use cases. The higher core count also eliminates the need for dual CPU (x86-based systems). This flexibility enables system designers to optimize Arm-based systems for database workloads, enhancing performance and efficiency. Additionally, the modular nature of Arm-based systems allows for easier integration of different components, making them adaptable to various database requirements.
  • Increased Parallel Processing: Relational databases often deal with large volumes of data and complex queries, necessitating efficient parallel processing capabilities. Arm processors, featuring multiple cores and superior multithreading capabilities, excel in this aspect. With the proliferation of multicore Arm processors, database operations can be parallelized, enabling faster query execution and improved overall database performance. This parallel processing prowess of Arm processors is particularly beneficial for demanding workloads in relational databases, where simultaneous execution of multiple queries is essential.
  • Enhanced Memory Bandwidth: Memory bandwidth plays a crucial role in database performance, especially when dealing with high data transfer rates. Arm processors often feature memory architectures designed for optimal bandwidth utilization, which can improve the speed of data access and retrieval. This increased memory bandwidth contributes to a more responsive and efficient database system, enabling faster query execution and reduced latency.
  • Cost-Effectiveness: Arm processors have established a reputation for cost-effectiveness, making them an attractive choice for organizations seeking to optimize their IT infrastructure. The Arm ecosystem offers manufacturers various hardware options, resulting in competitive pricing and increased affordability. For businesses running relational databases, deploying Arm-based systems can be a financially viable solution without compromising performance.
  • Security: Ampere Altra processors based on Arm (available in Oracle Cloud) run on a single thread per core processor, eliminating potential thread-security issues and isolating workloads. When run as a single thread per core, there is no sharing of the execution engine, registers, and L1/L2 cache between threads, which minimizes the attack surface for exploits.

Why Database Engines on Arm:

  • Customization for Database Needs: Arm develops the Arm architecture and licenses the IP to allow its licensees/partners/customers to subsequently build and sell the chip within their designs/products, such as system-on-chip or system-on-modules designs. SoC (system-on-chip) is an efficient design model where significant components of a computer or electronic system reside on a small, low-power board. This approach differs from other CPU manufacturers, such as Intel or AMD, that design and manufacture their chips. The ability to license Arm design gives database vendors, like Oracle, the flexibility to design their chips based on Arm architecture.
  • Scalability: Database engines do require scalability. Oracle Database runs high transactional applications and requires vertical and horizontal scalability. Arm processors, compared to their x86 counterparts, are highly dense and provide more cores on a CPU.
  • Endianness: Endianness describes the order in which a sequence of bytes is stored in computer memory. Big-Endian systems store the most significant byte (big end) first in the order, and Little-Endian systems store the least significant bytes (little end) first. Arm architecture, by design, is bi-endian, which means it can support both big-endian and little-endian byte orderings. To complement its x86 offering, Oracle will use little-endian byte ordering for its Arm implementations and interoperability with x86 counterparts.
  • Portability: Oracle is adopting Arm architecture with Ampere One and Ampere AltraMax processors and will use little-endian format for byte ordering. Using little-endian format means migrating running databases on x86-based systems to Arm-based systems or vice versa will be easier. Generally available migration techniques like backup and restore will work across x86 and Arm-based systems.
 

Oracle Database Availability on Arm


Oracle Database Enterprise Edition is available on the Arm platform (Ampere Altra brands) in the cloud with flexible shapes (VM.Standard.A1.Flex) for Oracle Base Database Service (BaseDB). VM.Standard.A1.Flex is based on Arm computer processors and CPU cores. VM.Standard.A1.Flex shapes for BaseDB support any number of OCPUs, up to a maximum of 64, in a single VM. Each OCPU includes 8 GB of memory and 1 Gbps of network bandwidth, up to a maximum of 40 Gbps. VM.Standard.A1.Flex shapes offer balanced and higher-performance block volume storage that can scale up to 40 TB in data capacity. When provisioned with higher-performance storage, customers can achieve a maximum of 500K IOPS for a single VM.

Oracle Database on the Arm platform was released from Database release version 19.19. This database version complements the Oracle Database you have been running on x86 and other platforms, including RAC (on-premises currently), Data Guard, and others. Oracle Database on Arm is available on-premises and in Oracle Cloud Infrastructure. Currently, Oracle licenses are certified and licensed for Ampere Altra and Ampere Altra Max processors with a core factor of .25. Please refer to the core-factor table here: https://drive.google.com/file/d/14qOc_TP_NPe-kNeyCXbUtkK8Npg1prwJ/view?usp=sharing. All other Arm processors, not referred to in the core factor table, will use a core factor of 1 for licensing purposes.

Source: oracle.com