Introducing Oracle Exadata Database Service on Exascale Infrastructure

We are pleased to announce the general availability of Oracle Exadata Database Service on Exascale Infrastructure. Exadata Database Service provides customers around the world with extreme performance, reliability, availability, and security benefits they depend on for their Oracle Database workloads. With the introduction of highly scalable and affordable Exadata Exascale infrastructure, these benefits are now available in Oracle Cloud Infrastructure (OCI) for any size workload and every Oracle Database customer.

 

Oracle Exadata Exascale: World’s Only Intelligent Data Architecture for Cloud

Exadata Exascale is Oracle’s revolutionary multitenant architecture that combines the intelligence of Exadata with all the benefits of modern clouds. This loosely-coupled architecture incorporates the Exascale intelligent storage cloud and a pool of Exascale database-optimized compute to provide hyper-elasticity while meeting even the most demanding workload requirements.

Exascale delivers the best of Exadata and the best of cloud

When running Exadata Database Service on Exascale Infrastructure, you have access to its intelligent capabilities across your application portfolio. Database-optimized intelligent infrastructure runs AI, analytics, mission-critical OLTP, and developer workloads faster and more efficiently, reducing overall IT costs. Some of these capabilities include:

• Intelligent AI: The combination of AI Smart Scan with Exadata System Software 24ai offloads key AI Vector Search operations to the Exascale intelligent storage cloud, enabling massive amounts of vector data to be searched up to 30X faster.

• Intelligent analytics: The combination of intelligent columnarization and Smart Scan make hundreds or thousands of processing cores in the Exascale intelligent storage cloud available to process any SQL query.

• Intelligent OLTP: Exascale’s intelligent architecture automatically tiers data between DRAM, flash, and disk enabling low-latency, high-throughput Remote Direct Memory Access (RDMA) to frequently accessed data and delivers the performance of DRAM, the IOPS of flash, and the capacity of disk.

• Database-aware intelligent clones: The Exascale intelligent storage cloud uses redirect-on-write snapshot technology to instantly create space-efficient database clones from read-write sources.

Extreme Performance for Workloads at Any Scale

Until now, Exadata Database Service ran only on dedicated infrastructure allocated to a single tenant. While this approach is instrumental in providing extreme performance for demanding workloads, isolation for every customer, and efficient database consolidation, it requires a higher minimum investment for Exadata adoption.

Starting today, you can enjoy Exadata Database Service benefits at a lower entry cost for smaller, but no less critical, databases. Exadata Database Service on Exascale Infrastructure bridges the gap between dedicated Exadata infrastructure and virtual machines on shared commodity infrastructure. It extends Exadata’s advantages to every organization in every industry, regardless of size or workload.

You can start small using virtual machine (VM) cluster configurations with as little as 8 ECPUs and 22 GB of memory per VM, and 300 GB of intelligent database storage. You can easily scale up the number of ECPUs and number of VMs in the cluster, and then shrink them when you don’t need them. To ensure ECPU capacity is available when you need it, you can reserve ECPUs at a nominal cost.

The same powerful automation available with Exadata Database Service on Dedicated Infrastructure is used to manage the VM cluster and databases, but with the physical compute and storage abstracted from the service. You just deploy the VM cluster and databases without concern for the Oracle-managed infrastructure on which they are running. Your databases are isolated in VM clusters that are fully under your control. VM images are stored on Exascale block storage, eliminating the size limitations of local drives and facilitating migration in the event of a failure.

 

Benefits of Oracle Exadata Database Service on Exascale Infrastructure

Exadata Database Service benefits are now even more affordable

• Powerful: Exascale infrastructure inherits all the capabilities of Exadata that deliver extreme performance, reliability, availability, and security. AI, analytics, and mission-critical OLTP workloads are accelerated by Exascale’s intelligent data architecture for cloud.

• Extreme low cost: With Exascale infrastructure, you only pay for the compute and storage resources used by your database, starting with a low, highly affordable minimum size. There’s no additional charge for IOPS, making costs predictable.

• Scalable pooled resources: Exascale infrastructure leverages pools of shared intelligent storage and compute, allowing databases to easily scale without concern for downtime, server-based size limitations, or disruptive migrations.

• Agile development: Exascale infrastructure features the ability to create rapid and efficient database thin clones with native Exadata performance that lowers storage costs and enhances developer agility.

Application Modernization with Oracle Database 23ai

Exadata Database Service on Exascale Infrastructure exclusively works with Oracle Database 23ai which not only extends extreme performance to AI Vector Search capabilities, but also includes many developer productivity enhancing features such as JSON Relational Duality that dramatically simplifies building and modernizing your applications.

Key Takeaways

Exadata Database Service on Exascale Infrastructure is a new way for any organization to gain the benefits of using Exadata in OCI. Built on Exadata Exascale, the world’s only intelligent data architecture for cloud, this new deployment option delivers Exadata intelligence with all the benefits of modern clouds.

Exadata Database Service on Exascale Infrastructure extends the performance, reliability, availability, and security benefits of Exadata to workloads at any scale. It provides extremely affordable consumption-based pricing and the elasticity to grow as needed.

Your development and testing teams will enhance their productivity with Exascale’s flexible cloning capabilities. By leveraging Oracle Database 23ai features such as JSON Relational Duality and Exadata capabilities like AI Smart Scan, they will be able to quickly modernize applications and integrate new powerful features.

Source: oracle.com

Continue reading

Table Values Constructor in Oracle Database 23ai

The table values constructor allows us to define multiple rows using a single constructor for use in SQL statements.

◉ Setup

The following table is required to run the examples in this article.

drop table if exists t1;

create table t1 (

  id number,

  code varchar2(6),

  description varchar(25),

  constraint t1_pk primary key (id)

);

◉ INSERT

The table values constructor allows us to insert multiple rows into a table in a single step.

insert into t1

values (1, 'ONE', 'Description for ONE'),

       (2, 'TWO', 'Description for TWO'),

       (3, 'THREE', 'Description for THREE');

commit;

select * from t1;

        ID CODE   DESCRIPTION

---------- ------ -------------------------

         1   ONE      Description for ONE

         2   TWO     Description for TWO

         3   THREE  Description for THREE

SQL>

That's a single network round trip without having to combine all the insert statements into a PL/SQL block.

◉ SELECT

The same type of table values constructor can be used in the FROM clause of a SELECT statement. Notice we have to alias the column names so they are presented correctly.

select *

from   (values

          (4, 'FOUR', 'Description for FOUR'),

          (5, 'FIVE', 'Description for FIVE'),

          (6, 'SIX', 'Description for SIX')

       ) a (id, code, description);

        ID CODE DESCRIPTION

---------- ---- --------------------

         4   FOUR Description for FOUR

         5    FIVE  Description for FIVE

         6    SIX    Description for SIX

SQL>

◉ WITH Clause

The table values constructor can be used as part of a WITH clause.

with a (id, code, description) AS (

  values (7, 'SEVEN', 'Description for SEVEN'),

         (8, 'EIGHT', 'Description for EIGHT'),

         (9, 'NINE', 'Description for NINE')

)

select * from a;

        ID CODE  DESCRIPTION

---------- ----- ---------------------

         7   SEVEN Description for SEVEN

         8   EIGHT  Description for EIGHT

         9   NINE   Description for NINE

SQL>

◉ MERGE

The table values constructor can be used as the source data for a MERGE statement.

merge into t1 a

  using (values

          (4, 'FOUR', 'Description for FOUR'),

          (5, 'FIVE', 'Description for FIVE'),

          (6, 'SIX', 'Description for SIX')

        ) b (id, code, description)

  on (a.id = b.id)

  when matched then

    update set a.code        = b.code,

               a.description = b.description

  when not matched then

    insert (a.id, a.code, a.description)

    values (b.id, b.code, b.description);

3 rows merged.

SQL>

select * from t1;

        ID CODE   DESCRIPTION

---------- ------ -------------------------

         1   ONE      Description for ONE

         2   TWO     Description for TWO

         3   THREE  Description for THREE

         4   FOUR    Description for FOUR

         5   FIVE      Description for FIVE

         6   SIX        Description for SIX

6 rows selected.

SQL>

rollback;

Source: oracle-base.com

Continue reading

Transport Layer Security (TLS) Connections without a Client Wallet in Oracle Database 23ai

In previous releases HTTPS callouts from the database required the use of a client wallet. From Oracle database 23ai onward we can use the operating system certificate store instead.

Operating systems usually have a certificate store containing the root certificates of popular certificate authorities. This allows the operating system to make trusted connections to sites using those root certificates. These certificate stores are kept up to date with operating patches. Oracle 23ai allows us to make use of the operating system certificate store, rather than having to use a wallet, which removes the burden of certificate management from us.

Test a URL From the Operating System

The simplest way to test a HTTPS URL is to use the curl command from the operating system command line. If a valid HTTPS connection is possible, we should get a "200 OK" response. We can see it works fine.

$ curl -is https://oracle-base.com/sitemap.xml | grep HTTP

HTTP/1.1 200 OK

$

This means the required root certificate is present in the operating system certificate store.

Create an ACL

In order to do a database callout we need an Access Control List (ACL) for the host. The following example creates an ACL for the host "oracle-base.com" on port 443. The principal is TESTUSER1, which is the user we will make the call from.

conn sys/SysPassword1@//localhost:1521/freepdb1 as sysdba

begin

  dbms_network_acl_admin.append_host_ace (

    host       => 'oracle-base.com', 

    lower_port => 443,

    upper_port => 443,

    ace        => xs$ace_type(privilege_list => xs$name_list('http'),

                              principal_name => 'testuser1',

                              principal_type => xs_acl.ptype_db)); 

end;

/

conn testuser1/testuser1@//localhost:1521/freepdb1

Test a Database Callout Without a Wallet

We create a procedure using the UTL_HTTP package to return the contents of a URL.

create or replace procedure show_html_from_url (

  p_url  in  varchar2

) as

  l_http_request   utl_http.req;

  l_http_response  utl_http.resp;

  l_text           varchar2(32767);

begin

  -- Make a http request and get the response.

  l_http_request  := utl_http.begin_request(p_url);

  l_http_response := utl_http.get_response(l_http_request);

  -- Loop through the response.

  begin

    loop

      utl_http.read_text(l_http_response, l_text, 32766);

      dbms_output.put_line (l_text);

    end loop;

  exception

    when utl_http.end_of_body then

      utl_http.end_response(l_http_response);

  end;

exception

  when others then

    utl_http.end_response(l_http_response);

    raise;

end show_html_from_url;

/

In previous releases attempting to use the procedure without opening a wallet would result in a certificate validation failure. That is not the case in Oracle 23ai, as we are using the operating system certificate store by default.

set serveroutput on long 1000000

exec show_html_from_url('https://oracle-base.com/sitemap.xml');

<?xml version="1.0" encoding="UTF-8"?>

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">

  <url>

... output removed ...

  <url>

</urlset>

PL/SQL procedure successfully completed.

SQL>

We could have achieved a similar result using HTTPURITYPE.

set serveroutput on long 1000000

select HTTPURITYPE.createuri('https://oracle-base.com/sitemap.xml').getclob();

HTTPURITYPE.CREATEURI('HTTPS://ORACLE-BASE.COM/SITEMAP.XML').GETCLOB()

--------------------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8"?>

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">

  <url>

... output removed ...

  <url>

</urlset>

SQL>

Test a Database Callout With a Wallet

We can still use a wallet containing the relevant root certificate, but once we reference the wallet it takes priority. If the wallet doesn't contain the correct root certificate, the call will fail. To demonstrate this we make a new wallet containing a self-signed certificate, rather than the root certificate of the URL we are calling.

mkdir -p /u01/wallet

orapki wallet create -wallet /u01/wallet -pwd WalletPasswd123 -auto_login

orapki wallet add -wallet /u01/wallet -pwd WalletPasswd123 \

  -dn "CN=`hostname`, OU=Example Department, O=Example Company, L=Birmingham, ST=West Midlands, C=GB" \

  -keysize 1024 -self_signed -validity 365

We connect to a new session, open the wallet, and attempt to run the procedure to make the callout. As expected, this results in a certificate validation failure.

conn testuser1/testuser1@//localhost:1521/freepdb1

set serveroutput on long 1000000

exec utl_http.set_wallet('file:/u01/wallet', null);

exec show_html_from_url('https://oracle-base.com/sitemap.xml');

*

ERROR at line 1:

ORA-29273: HTTP request failed

ORA-06512: at "TESTUSER1.SHOW_HTML_FROM_URL", line 26

ORA-29024: Certificate validation failure

ORA-06512: at "SYS.UTL_HTTP", line 380

ORA-06512: at "SYS.UTL_HTTP", line 1189

ORA-06512: at "TESTUSER1.SHOW_HTML_FROM_URL", line 9

ORA-06512: at line 1

Help: https://docs.oracle.com/error-help/db/ora-29273/

SQL>

We get the same error when we try to use HTTPURITYPE.

conn testuser1/testuser1@//localhost:1521/freepdb1

set serveroutput on

exec utl_http.set_wallet('file:/u01/wallet', null);

select HTTPURITYPE.createuri('https://oracle-base.com/sitemap.xml').getclob();

ERROR:

ORA-29273: HTTP request failed

ORA-06512: at "SYS.HTTPURITYPE", line 38

ORA-29024: Certificate validation failure

ORA-06512: at "SYS.UTL_HTTP", line 380

ORA-06512: at "SYS.UTL_HTTP", line 1189

ORA-06512: at "SYS.HTTPURITYPE", line 23

Help: https://docs.oracle.com/error-help/db/ora-29273/

SQL>

We add the correct certificate to the wallet.

orapki wallet add -wallet /u01/wallet -trusted_cert -cert "/tmp/ISRG Root X1.crt" -pwd WalletPasswd123

Now the previous tests work as expected.

conn testuser1/testuser1@//localhost:1521/freepdb1

set serveroutput on long 1000000

exec utl_http.set_wallet('file:/u01/wallet', null);

exec show_html_from_url('https://oracle-base.com/sitemap.xml');

<?xml version="1.0" encoding="UTF-8"?>

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">

  <url>

... output removed ...

  <url>

</urlset>

PL/SQL procedure successfully completed.

SQL>

select HTTPURITYPE.createuri('https://oracle-base.com/sitemap.xml').getclob();

HTTPURITYPE.CREATEURI('HTTPS://ORACLE-BASE.COM/SITEMAP.XML').GETCLOB()

--------------------------------------------------------------------------------

<?xml version="1.0" encoding="UTF-8"?>

<urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">

  <url>

... output removed ...

  <url>

</urlset>

SQL>

Mark a Self-Signed Certificate as Trusted

We are not always working with certificates from a certificate authority. Sometimes we may need to make callouts to services using self-signed certificates. Fortunately we can mark self-signed certificates as trusted on the OS of the database server. The following actions were performed as the "root" user.

We create a self-signed certificate, as demonstrated.

mkdir -p ~/certs

openssl req \

  -newkey rsa:4096 -nodes -sha256 -keyout ~/certs/${HOSTNAME}.key \

  -x509 -days 3650 -out ~/certs/${HOSTNAME}.crt \

  -subj "/C=GB/ST=West Midlands/L=Birmingham/O=Example Company/OU=Devs/CN=Tim Hall/emailAddress=me@example.com"

We copy it to the "/etc/pki/ca-trust/source/anchors/" directory and run update-ca-trust to make the change take effect.

cp ~/certs/${HOSTNAME}.crt /etc/pki/ca-trust/source/anchors/

update-ca-trust

We use trust list to check the certificate is present.

# trust list --filter=ca-anchors | grep -B 4 -A 2 "Tim Hall"

pkcs11:id=%EE%3A%98%8F%93%C2%64%23%E0%42%7F%52%97%54%6D%87%7F%C0%2F%05;type=cert

    type: certificate

    label: Tim Hall

    trust: anchor

    category: authority

#

Source: oracle-base.com

Continue reading

XML, JSON and Oracle Text Search Index Enhancements in Oracle Database 23ai

In Oracle 23ai the CREATE SEARCH INDEX statement allows us to create search indexes on XML, JSON and text data, making the syntax consistent between them.

◉ XML Search Indexes

The index type of XDB.XMLIndex was introduced in a previous release to allow us to index XML data.

drop table if exists t1 purge;

create table t1 (

  id    number,

  data  xmltype

);

create index t1_xmlindex_idx on t1 (data) indextype is xdb.xmlindex;

In Oracle 23ai we can create search indexes for XML using the CREATE SEARCH INDEX ... FOR XML syntax. The full syntax is available here.

drop table if exists xml_tab purge;

create table xml_tab (

  id    number,

  data  xmltype

)

xmltype column data

store as transportable binary xml;

create search index xml_tab_search_idx on xml_tab (data) for XML

parameters (

  'search_on text'

);

The SEARCH_ON parameter must be set for XML search indexes.

• TEXT : Only text data is indexed for full-text search queries.
• VALUE(data_types) : Enables range-search for the specified data types. One or more of BINARY_DOUBLE, NUMBER, TIMESTAMP, VARCHAR2 as a comma-separated list.
• TEXT_VALUE(data_types) : A combination of support for full-text searches queries and range-search for the specified data types.

The XMLTYPE column must be stored as transportable binary XML to build a XML search index. For other storage types we can create an Oracle Text search index instead.

drop table if exists xml_tab purge;

create table xml_tab (

  id    number,

  data  xmltype

);

create search index xml_tab_search_idx on xml_tab (data);

◉ JSON Search Indexes

The original syntax for JSON search indexes in Oracle 12.1 was rather ugly.

drop table if exists t1 purge;

create table t1 (

  id    number,

  data  clob,

  constraint t1_json_chk check (data is json)

);

create index t1_search_idx on t1 (data)

  indextype is ctxsys.context

  parameters ('section group ctxsys.json_section_group sync (on commit)');

In Oracle 12.2 the JSON search index syntax was simplified using the CREATE SEARCH INDEX ... FOR JSON syntax. The full syntax is available here.

drop index if exists t1_search_idx;

create search index t1_search_idx on t1 (data) for json;

The SEARCH_ON parameter defaults to TEXT_VALUE for XML search indexes.

• NONE : JSON queries are not supported. Only the data guide index is maintained.
• TEXT : Only text data is indexed for full-text search queries.
• VALUE(data_types) : Enables range-search for the specified data types. One or more of NUMBER, TIMESTAMP, VARCHAR2 as a comma-separated list.
• TEXT_VALUE(data_types) : A combination of support for full-text searches queries and range-search for the specified data types.
• TEXT_VALUE_STRING : A combination of support for full-text searches queries and range-search for NUMBER, TIMESTAMP and VARCHAR2 data types.

◉ Oracle Text Search Indexes

Oracle has a long history of full-text indexing for text data. You can read about it here.

- Full Text Indexing using Oracle Text

In Oracle 23ai we can create full-text search indexes using the CREATE SEARCH INDEX syntax. The full syntax is available here.

drop table if exists text_tab purge;

create table text_tab (

  id    number,

  data  clob

);

create search index text_tab_search_idx on text_tab (data);

Source: oracle-base.com

Continue reading

Oracle Database 23ai Free RPM Installation On Oracle Linux 8 (OL8)

Oracle Database 23ai free can be installed on Oracle Linux 8 using an RPM. This article describes the RPM installation of Oracle Database 23ai free 64-bit on Oracle Linux 8 (OL8) 64-bit. The article is based on a server installation with a minimum of 2G swap and secure Linux set to permissive.

1. Hosts File

The "/etc/hosts" file must contain a fully qualified name for the server.

<IP-address>  <fully-qualified-machine-name>  <machine-name>

For example.

127.0.0.1       localhost localhost.localdomain localhost4 localhost4.localdomain4

192.168.56.107  ol8-23.localdomain  ol8-23

Set the correct hostname in the "/etc/hostname" file.

ol8-23.localdomain

2. Oracle Installation

Download the relevant RPM from download page here.

- oracle-database-free-23ai-1.0-1.el8.x86_64.rpm

With the RPM file downloaded, we can install the Oracle prerequisites using the following commands as the "root" user.

dnf install -y oracle-database-preinstall-23ai

We now install the 23ai software using the following command as the root user. This assumes the RPM file is in the "/tmp" directory.

dnf -y localinstall /tmp/oracle-database-free-23ai-1.0-1.el8.x86_64.rpm

The ORACLE_HOME for the software installation is "/opt/oracle/product/23ai/dbhomeFree".

3. Create Database

In addition to the software installation, the RPM creates a script that allows us to create a demo database called "FREE", with a pluggable database (PDB) called "FREEPDB1". In the following example we set the DB_PASSWORD environment variable so we can do a silent database creation using the script.

# export DB_PASSWORD=SysPassword1

# (echo "${DB_PASSWORD}"; echo "${DB_PASSWORD}";) | /etc/init.d/oracle-free-23ai configure

Specify a password to be used for database accounts. Oracle recommends that the password entered should be at least 8 characters in length, contain at least 1 uppercase character, 1 lower case character and 1 digit [0-9]. Note that the same password will be used for SYS, SYSTEM and PDBADMIN accounts:

Confirm the password:

Configuring Oracle Listener.

Listener configuration succeeded.

Configuring Oracle Database FREE.

Enter SYS user password:

*************

Enter SYSTEM user password:

**************

Enter PDBADMIN User Password:

************

Prepare for db operation

7% complete

Copying database files

29% complete

Creating and starting Oracle instance

30% complete

33% complete

36% complete

39% complete

43% complete

Completing Database Creation

47% complete

49% complete

50% complete

Creating Pluggable Databases

54% complete

71% complete

Executing Post Configuration Actions

93% complete

Running Custom Scripts

100% complete

Database creation complete. For details check the logfiles at:

 /opt/oracle/cfgtoollogs/dbca/FREE.

Database Information:

Global Database Name:FREE

System Identifier(SID):FREE

Look at the log file "/opt/oracle/cfgtoollogs/dbca/FREE/FREE.log" for further details.

Connect to Oracle Database using one of the connect strings:

     Pluggable database: localhost.localdomain/FREEPDB1

     Multitenant container database: localhost.localdomain

[root@localhost yum.repos.d]#

We can of course create a database in the normal way, using the Database Configuration Assistant (DBCA). We don't have to use this script.

4. Using It

From the "oracle" user we can connect as follows.

export ORACLE_HOME=/opt/oracle/product/23ai/dbhomeFree

export PATH=$ORACLE_HOME/bin:$PATH

-- Root container

sqlplus sys/SysPassword1@//localhost:1521/free as sysdba

-- Pluggable database

sqlplus sys/SysPassword1@//localhost:1521/freepdb1 as sysdba

We can stop and start the service from the root user with the following commands.

/etc/init.d/oracle-free-23ai stop

/etc/init.d/oracle-free-23ai start

5. Vagrant Example

If you want to see it in action, you might want to try one of these Vagrant build.

- ol8_23_free

Source: oracle-base.com

Continue reading

Oracle Database 23ai Free RPM Installation On Oracle Linux 9 (OL9)

Oracle Database 23ai free can be installed on Oracle Linux 9 using an RPM. This article describes the RPM installation of Oracle Database 23ai free 64-bit on Oracle Linux 9 (OL9) 64-bit. The article is based on a server installation with a minimum of 2G swap and secure Linux set to permissive.

◉ Hosts File

The "/etc/hosts" file must contain a fully qualified name for the server.

<IP-address>  <fully-qualified-machine-name>  <machine-name>

For example.

127.0.0.1       localhost localhost.localdomain localhost4 localhost4.localdomain4

192.168.56.107  ol9-23.localdomain  ol9-23

Set the correct hostname in the "/etc/hostname" file.

ol9-23.localdomain

◉ Oracle Installation

Download the relevant RPM from download page here.

- oracle-database-free-23ai-1.0-1.el9.x86_64.rpm

With the RPM file downloaded, we can install the Oracle prerequisites using the following commands as the "root" user.

dnf install -y oracle-database-preinstall-23ai

We now install the 23ai software using the following command as the root user. This assumes the RPM file is in the "/tmp" directory.

dnf -y localinstall /tmp/oracle-database-free-23ai-1.0-1.el9.x86_64.rpm

The ORACLE_HOME for the software installation is "/opt/oracle/product/23ai/dbhomeFree".

◉ Create Database

In addition to the software installation, the RPM creates a script that allows us to create a demo database called "FREE", with a pluggable database (PDB) called "FREEPDB1". In the following example we set the DB_PASSWORD environment variable so we can do a silent database creation using the script.

# export DB_PASSWORD=SysPassword1

# (echo "${DB_PASSWORD}"; echo "${DB_PASSWORD}";) | /etc/init.d/oracle-free-23ai configure

Specify a password to be used for database accounts. Oracle recommends that the password entered should be at least 8 characters in length, contain at least 1 uppercase character, 1 lower case character and 1 digit [0-9]. Note that the same password will be used for SYS, SYSTEM and PDBADMIN accounts:

Confirm the password:

Configuring Oracle Listener.

Listener configuration succeeded.

Configuring Oracle Database FREE.

Enter SYS user password:

*************

Enter SYSTEM user password:

**************

Enter PDBADMIN User Password:

************

Prepare for db operation

7% complete

Copying database files

29% complete

Creating and starting Oracle instance

30% complete

33% complete

36% complete

39% complete

43% complete

Completing Database Creation

47% complete

49% complete

50% complete

Creating Pluggable Databases

54% complete

71% complete

Executing Post Configuration Actions

93% complete

Running Custom Scripts

100% complete

Database creation complete. For details check the logfiles at:

 /opt/oracle/cfgtoollogs/dbca/FREE.

Database Information:

Global Database Name:FREE

System Identifier(SID):FREE

Look at the log file "/opt/oracle/cfgtoollogs/dbca/FREE/FREE.log" for further details.

Connect to Oracle Database using one of the connect strings:

     Pluggable database: localhost.localdomain/FREEPDB1

     Multitenant container database: localhost.localdomain

[root@localhost yum.repos.d]#

We can of course create a database in the normal way, using the Database Configuration Assistant (DBCA). We don't have to use this script.

◉ Using It

From the "oracle" user we can connect as follows.

export ORACLE_HOME=/opt/oracle/product/23ai/dbhomeFree

export PATH=$ORACLE_HOME/bin:$PATH

-- Root container

sqlplus sys/SysPassword1@//localhost:1521/free as sysdba

-- Pluggable database

sqlplus sys/SysPassword1@//localhost:1521/freepdb1 as sysdba

We can stop and start the service from the root user with the following commands.

/etc/init.d/oracle-free-23ai stop

/etc/init.d/oracle-free-23ai start

◉ Vagrant Example

If you want to see it in action, you might want to try one of these Vagrant build.

- ol9_23_free

Source: oracle-base.com

Continue reading