Best match

Most recent

Oracle Corporation

Mexico

Telmex

Oracle (ORCL) opens a second Oracle Cloud Region in Mexico in partnership with Teléfonos de México (TELMEX-Triara), becoming the first hyperscaler to have two c

Oracle joins hands with TELMEX-Triara, offering two cloud regions in Mexico

https://www.bing.com/th?id=ODF.T3WKS_yw6iQ2VstDFu9FMw&pid=news

Seeking Alpha

As Oracle CloudWorld 2023 kicked off, important questions about Oracle's generative AI strategy had not been publicly addressed. But via keynotes and sessions for media/analysts, that changed. Here's what I learned on crucial questions for AI customers,

https://www.bing.com/th?id=OVFT.iRH9OoQeaGmMa8fBwfPiIS&pid=News

Cloud World 23 - Oracle addresses the hot questions on generative AI pricing, customer data, and where SIs fit in

https://www.bing.com/th?id=ODF.PEmaFmOAZF-DFU65WYPtlg&pid=news

Diginomica

Insider

Oracle opens new region in Monterrey in partnership with Teléfonos de México (TELMEX-Triara) and continues expanding its global cloud region

Oracle Partners with TELMEX-Triara to Become the Only Hyperscaler with Two Cloud Regions in Mexico

https://www.bing.com/th?id=ODF.LrIq_5vxtu4ONs5zIW54FA&pid=news

Business Insider

Splunk

Analysis

Cisco Systems, Inc.

Cisco Systems' $28 billion deal for Splunk is likely to prompt other technology giants to splash out on similar acquisitions of software vendors with predictable subscription revenue, investment bankers and analysts say.

https://www.bing.com/th?id=OVFT.rrRG0o9tqxtzGHvqT9G66C&pid=News

Analysis-Cisco's $28 billion Splunk deal may ignite software deal frenzy

https://www.bing.com/th?id=ODF.6l3fMUjuba1Bx26WywDhqQ&pid=news

Marketplace

Wage

DailyPay, a Fintech focused on earned wage access, and a member of Oracle Partner Network, is available on Oracle Cloud Marketplace.

DailyPay, a Fintech Focused on Earned Wage Access Services, Available via Oracle Cloud Marketplace

https://www.bing.com/th?id=ODF.oSZPaedojiaxzQf3-kdw4Q&pid=news

Crowdfund Insider

Vernor Vinge

Suite

Ranked Industry Analyst Patrick Moorhead explains the new AI-driven functionality in the Oracle Fusion cloud application suite.

https://www.bing.com/th?id=OVFT.ntvy156gmm0fCm2tFwxWMi&pid=News

Oracle Incorporates Generative AI Functionality Across Its Fusion Suite

https://www.bing.com/th?id=ODF.U6nYa4Huf-RFEhjg-V4hNg&pid=news

Forbes

CloudWorld conference held in Las Vegas last week, Oracle Corporation (NYSE:ORCL) introduced a range of products and updates centered around generative AI, a technology that co-founder and CTO Larry Ellison considers one of the

https://www.bing.com/th?id=OVFT.HqyvfE98hRbj3H30t-npmy&pid=News

Electronic health record

Digital Equipment Corporation

Oracle rolls out generative AI services and updates at CloudWorld 2023

https://www.bing.com/th?id=ODF.ioabjhuoYuW67hzKy8HG5g&pid=news

uk.investing.com on MSN.com

Inflection

The valuation of Oracle shares has compressed after its earnings report. I see the report as highlighting an inflection to higher growth. Read more on ORCL.

https://www.bing.com/th?id=OVFT.R_rw93DYKwzPupJ6VVNDQS&pid=News

Oracle: A Growth Inflection Is Coming Into View

Oracle CloudWorld, the user conference that attracts tens of thousands of customers and prospects, occurred this week.

https://www.bing.com/th?id=OVFT.gOjD5xuhl6DTFsO4DLvhZy&pid=News

Key Takeaways From Oracle CloudWorld 2023

A decade into its cloud-computing shift, Oracle has a message for those who know it primarily as a database heavyweight with hardball sales tactics: We’re cheaper than the competition.

https://www.bing.com/th?id=OVFT.sdQMdetZ-NdgsvS_YNBoZS&pid=News

Oracle, Aiming for Cloud-Era Reinvention, Pitches Itself as the Cheaper Alternative

https://www.bing.com/th?id=ODF.15fnkpKGfQuTaaskfJ-smw&pid=news

The Wall Street Journal on MSN.com

Get the most recent info and news about Oracle on HackerNoon, where 10k+ technologists publish stories for 4M+ monthly readers.

Oracle Corporation provides products and services that address enterprise information technology environments worldwide. The company's cloud and license business engages in the sale, marketing, and delivery of its applications and infrastructure technologies through cloud and on-premise deployment models, including cloud services and license support; and cloud license and on-premise license. Its cloud software as a service offerings include a suite of cloud software applications, including enterprise resource planning (ERP), enterprise and performance management, supply chain management, human capital management, and customer experience cloud-based industry solutions, as well as NetSuite application suite, a cloud-based ERP solution. The company also provides cloud infrastructure as a service; enterprise database; database products, including MySQL, Oracle TimesTen In-Memory Database, Oracle Berkeley DB, and Oracle NoSQL Database; middleware software; Java licenses; server and storage products; hardware products and services comprising point-of-sale terminals and related hardware for managing businesses within the food and beverage, hotel and retail industries; and hardware products and services for communications networks, including network signaling, policy control and subscriber data management solutions, and session border control technology. In addition, it offers operating systems, including Oracle Linux and Oracle Solaris, virtualization software, and other hardware-related software; management technologies and products, such as Oracle Enterprise Manager; and product repairs, maintenance services, and technical support services. It also serves various industries, government agencies, and educational institutions. The company was founded in 1977 and is headquartered in Redwood City, California.

Oracle

The previous articles discussed how to recover a node after losing " " and " " This time, let's try to recover from losing both binaries. only the DB BINARIES only the GRID BINARIES. My configuration
Oracle RAC with 2 nodes: ol8-19-rac1 and ol8-19-rac2
CDB: cdbrac1
PBD: pdb1

Grid Version
34318175;TOMCAT RELEASE UPDATE 19.0.0.0.0 (34318175)
34160635;OCW RELEASE UPDATE 19.16.0.0.0 (34160635)
34139601;ACFS RELEASE UPDATE 19.16.0.0.0 (34139601)
34133642;Database Release Update : 19.16.0.0.220719 (34133642)
33575402;DBWLM RELEASE UPDATE 19.0.0.0.0 (33575402)

DB Version
34086870;OJVM RELEASE UPDATE: 19.16.0.0.220719 (34086870)
34160635;OCW RELEASE UPDATE 19.16.0.0.0 (34160635)
34133642;Database Release Update : 19.16.0.0.220719 (34133642)

When you see <dbenv>, load the DB HOME variables.
When you see <gridenv>, load the GRID HOME variables.

When you see <bnode>, execute the command on the broken node.
When you see <anode>, execute the command on any other working node. I am using an installation where both DB and GRID are installed under the user ORACLE, and I set the variables to access each environment. But the same procedure works even if the installation is done using two different users (usually oracle e grid). Always validate any procedure before you try it in a production environment. Scenario C - DB and GRID Binaries Corrupted On ol8-19-rac2 After Applying a Patch This time, we will combine previous solutions to complete the job. For the sake of simplicity, I'll only provide the steps needed, and you can check how to execute them in the previous articles. I. From the article on , execute the following steps: DB Binaries Backup the $ORACLE_HOME/network/admin. Deinstall the DB binaries. II. From the article on , execute all the steps. GRID Binaries III. From the article on , execute the following steps: DB Binaries Add the node back. Add the instance back. If needed, restore the $ORACLE_HOME/network/admin on the ex-broken node. Voilà, that's it. Now, your database is supposed to be back online on the ex-broken node.

Fixing Oracle RAC Node Problems With Addnode: GRID and DB Binaries

In this tutorial, we'll explore how to use SQL expressions for validation in Oracle APEX. SQL expressions are like smart rules that help you decide if the data entered in your application is correct. We'll go through the process step by step and provide examples to make it easy to understand. What is an SQL Expression for Validation? An SQL expression for validation is like a detective checking if something is true or false in your application. It's a way to define a condition that must be met for data to be considered valid. If the condition is true, the data is accepted; if it's false, you'll get an . Oracle APEX error message Creating an SQL Expression Validation Let's walk through the process of creating an SQL expression validation: Go to Page Designer: Open your Oracle APEX application and go to "Page Designer." Select Your Page Item: Choose the page item that you want to validate. In our example, we'll use . P2_JOB Add a Validation: In the properties of the selected page item, go to the "Validation" section and click on "Add." Choose Validation Type: Select "SQL Expression" as the validation type. This tells APEX that we're going to use an SQL expression to validate our data. Define the SQL Expression: In the "SQL Expression" field, enter your SQL code. Let's say we want to validate that the job is either 'MANAGER' or the department is located in 'CHICAGO'. Here's the SQL expression: :P2_JOB = 'MANAGER' OR
EXISTS (
    SELECT 1
    FROM dept
    WHERE deptno = :P2_DEPTNO
    AND loc = 'CHICAGO'
) This SQL expression checks if is 'MANAGER' or if the department specified by is located in 'CHICAGO'. If either condition is true, the data is valid. P2_JOB P2_DEPTNO Set Validation Attributes: You can further customize your validation by setting attributes like error message text, error message display location, and more. Save and Run: Save your validation, and now, when a user enters data in , it will be checked against your SQL expression. If it meets the conditions, it's valid; otherwise, an error message will be displayed. P2_JOB Additional Examples Example 1: Checking Age Limit Let's say you have a page item where users enter their age. You want to make sure they are older than 18. Here's the SQL expression: P3_AGE :P3_AGE > 18 This SQL expression checks if the age entered in is greater than 18. If it is, the data is valid. P3_AGE Example 2: Validating Email Format Suppose you have a page item where users enter their email addresses. You want to validate that the email follows a proper format. Here's the SQL expression: P4_EMAIL REGEXP_LIKE(:P4_EMAIL, '^[A-Za-z0-9._%+-]+@[A-Za-z0-9.-]+\\.[A-Za-z]{2,4}$') This SQL expression uses a to check if the email address matches a valid format. regular expression Example 3: Ensuring Unique Usernames If you have a page item where users enter their usernames, you may want to ensure that the username is unique. Here's the SQL expression: P5_USERNAME NOT EXISTS (
    SELECT 1
    FROM users
    WHERE username = :P5_USERNAME
) This SQL expression checks if the username entered in doesn't already exist in the user’s table. P5_USERNAME Testing the SQL Expression Validation To test your SQL expression validation, simply run your APEX application and enter different values in the respective page items. The validation will check if the conditions are met and provide error messages when needed. Conclusion SQL expressions for validation in Oracle APEX are like detectives ensuring that your data is correct. In this tutorial, we learned how to create an SQL expression validation, define the SQL code, and customize its attributes.

A Quick Tutorial on Using SQL Expressions for Validation in Oracle APEX

Hello, and welcome back to the last part of . In this part, let’s run some tests on our multipath disks. our article Testing the multipath disks --check the multipath disks
root@has03:/ $> multipath -ll
mpdata1 (36589cfc000000580ddee277e9cda411e) dm-2 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:2 sdf 8:80  active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 8:0:0:2 sdi 8:128 active ready running
mpfra1 (36589cfc000000f5feabc996aa1a12876) dm-3 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:3 sdg 8:96  active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 8:0:0:3 sdj 8:144 active ready running
mpdata2 (36589cfc00000025b4072a1536ade2f9d) dm-4 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:1 sde 8:64  active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 8:0:0:1 sdh 8:112 active ready running

--shutdown the device enp0s8  
root@has03:/ $> nmcli con down enp0s8
Connection 'enp0s8' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/4)

--check the disks, now we have a "failed faulty" path
root@has03:/ $> multipath -ll
mpdata1 (36589cfc000000580ddee277e9cda411e) dm-2 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=0 status=enabled
| `- 7:0:0:2 sdf 8:80  failed faulty running
`-+- policy='service-time 0' prio=50 status=active
  `- 8:0:0:2 sdi 8:128 active ready running
mpfra1 (36589cfc000000f5feabc996aa1a12876) dm-3 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=0 status=enabled
| `- 7:0:0:3 sdg 8:96  failed faulty running
`-+- policy='service-time 0' prio=50 status=active
  `- 8:0:0:3 sdj 8:144 active ready running
mpdata2 (36589cfc00000025b4072a1536ade2f9d) dm-4 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=0 status=enabled
| `- 7:0:0:1 sde 8:64  failed faulty running
`-+- policy='service-time 0' prio=50 status=active
  `- 8:0:0:1 sdh 8:112 active ready running

--the ASM disks still exist
root@has03:/ $> ll /dev/oracleasm/mp*
lrwxrwxrwx. 1 root root 7 Apr 30 11:53 /dev/oracleasm/mpdata1 -> ../dm-2
lrwxrwxrwx. 1 root root 7 Apr 30 11:53 /dev/oracleasm/mpdata2 -> ../dm-4
lrwxrwxrwx. 1 root root 7 Apr 30 11:53 /dev/oracleasm/mpfra1 -> ../dm-3

--the Oracle Restart is still up and running
root@has03:/ $> crsctl status res -t
--------------------------------------------------------------------------------
Name           Target  State        Server                   State details
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DATA.dg
               ONLINE  ONLINE       has03                    STABLE
ora.FRA.dg
               ONLINE  ONLINE       has03                    STABLE
ora.LISTENER.lsnr
               ONLINE  ONLINE       has03                    STABLE
ora.asm
               ONLINE  ONLINE       has03                    Started,STABLE
ora.ons
               OFFLINE OFFLINE      has03                    STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd
      1        ONLINE  ONLINE       has03                    STABLE
ora.diskmon
      1        OFFLINE OFFLINE                               STABLE
ora.evmd
      1        ONLINE  ONLINE       has03                    STABLE
ora.money.db
      1        ONLINE  ONLINE       has03                    Open,HOME=/u01/app/o
                                                             racle/product/19c/db
                                                             home_1,STABLE
-------------------------------------------------------------------------------- So, our multipath seems to work fine. Let’s try to shut down the other interface. --startup the device enp0s8  
root@has03:/ $> nmcli con up enp0s8
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/6)

--check the multipath disks
--no more faulty paths
root@has03:/ $> multipath -ll
mpdata1 (36589cfc000000580ddee277e9cda411e) dm-2 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:2 sdf 8:80  active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 8:0:0:2 sdi 8:128 active ready running
mpfra1 (36589cfc000000f5feabc996aa1a12876) dm-3 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:3 sdg 8:96  active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 8:0:0:3 sdj 8:144 active ready running
mpdata2 (36589cfc00000025b4072a1536ade2f9d) dm-4 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:1 sde 8:64  active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 8:0:0:1 sdh 8:112 active ready running

--shutdown the device enp0s9
root@has03:/ $> nmcli con down enp0s9
Connection 'enp0s9' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/5)

--check the multipath disks
--now, the other path is faulty, as expected
root@has03:/ $> multipath -ll
mpdata1 (36589cfc000000580ddee277e9cda411e) dm-2 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:2 sdf 8:80  active ready running
`-+- policy='service-time 0' prio=0 status=enabled
  `- 8:0:0:2 sdi 8:128 failed faulty running
mpfra1 (36589cfc000000f5feabc996aa1a12876) dm-3 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:3 sdg 8:96  active ready running
`-+- policy='service-time 0' prio=0 status=enabled
  `- 8:0:0:3 sdj 8:144 failed faulty running
mpdata2 (36589cfc00000025b4072a1536ade2f9d) dm-4 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:1 sde 8:64  active ready running
`-+- policy='service-time 0' prio=0 status=enabled
  `- 8:0:0:1 sdh 8:112 failed faulty running

--our has still working like a charm
root@has03:/ $> crsctl status res -t
--------------------------------------------------------------------------------
Name           Target  State        Server                   State details
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DATA.dg
               ONLINE  ONLINE       has03                    STABLE
ora.FRA.dg
               ONLINE  ONLINE       has03                    STABLE
ora.LISTENER.lsnr
               ONLINE  ONLINE       has03                    STABLE
ora.asm
               ONLINE  ONLINE       has03                    Started,STABLE
ora.ons
               OFFLINE OFFLINE      has03                    STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd
      1        ONLINE  ONLINE       has03                    STABLE
ora.diskmon
      1        OFFLINE OFFLINE                               STABLE
ora.evmd
      1        ONLINE  ONLINE       has03                    STABLE
ora.money.db
      1        ONLINE  ONLINE       has03                    Open,HOME=/u01/app/o
                                                             racle/product/19c/db
                                                             home_1,STABLE
-------------------------------------------------------------------------------- Now, let’s go crazy, and shutdown both interfaces. root@has03:/ $> nmcli con down enp0s8
Connection 'enp0s8' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/6)

root@has03:/ $> nmcli d
DEVICE  TYPE      STATE         CONNECTION
enp0s3  ethernet  connected     enp0s3
enp0s8  ethernet  disconnected  --
enp0s9  ethernet  disconnected  --
lo      loopback  unmanaged     --

--no miracle here, both paths are faulty
root@has03:/ $> multipath -ll
mpdata1 (36589cfc000000580ddee277e9cda411e) dm-2 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=0 status=enabled
| `- 7:0:0:2 sdf 8:80  failed faulty running
`-+- policy='service-time 0' prio=0 status=enabled
  `- 8:0:0:2 sdi 8:128 failed faulty running
mpfra1 (36589cfc000000f5feabc996aa1a12876) dm-3 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=0 status=enabled
| `- 7:0:0:3 sdg 8:96  failed faulty running
`-+- policy='service-time 0' prio=0 status=enabled
  `- 8:0:0:3 sdj 8:144 failed faulty running
mpdata2 (36589cfc00000025b4072a1536ade2f9d) dm-4 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=0 status=enabled
| `- 7:0:0:1 sde 8:64  failed faulty running
`-+- policy='service-time 0' prio=0 status=enabled
  `- 8:0:0:1 sdh 8:112 failed faulty running
root@has03:/ $>

--the disks are still present
root@has03:/ $> ll /dev/oracleasm/mp*
lrwxrwxrwx. 1 root root 7 Apr 30 12:00 /dev/oracleasm/mpdata1 -> ../dm-2
lrwxrwxrwx. 1 root root 7 Apr 30 12:00 /dev/oracleasm/mpdata2 -> ../dm-4
lrwxrwxrwx. 1 root root 7 Apr 30 12:00 /dev/oracleasm/mpfra1 -> ../dm-3

--but the diskgroups and the database "died", as expected
root@has03:/ $> crsctl status res -t
--------------------------------------------------------------------------------
Name           Target  State        Server                   State details
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DATA.dg
               ONLINE  OFFLINE      has03                    STABLE
ora.FRA.dg
               ONLINE  OFFLINE      has03                    STABLE
ora.LISTENER.lsnr
               ONLINE  ONLINE       has03                    STABLE
ora.asm
               ONLINE  ONLINE       has03                    Started,STABLE
ora.ons
               OFFLINE OFFLINE      has03                    STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd
      1        ONLINE  ONLINE       has03                    STABLE
ora.diskmon
      1        OFFLINE OFFLINE                               STABLE
ora.evmd
      1        ONLINE  ONLINE       has03                    STABLE
ora.money.db
      1        ONLINE  OFFLINE                               Instance Shutdown,ST
                                                             ABLE
-------------------------------------------------------------------------------- Now, let’s clean up the mess. --let's bring the interfaces back online
root@has03:/ $> nmcli con up enp0s8
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/7)

root@has03:/ $> nmcli con up enp0s9
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/8)

--the disks are happy again
root@has03:/ $> multipath -ll
mpdata1 (36589cfc000000580ddee277e9cda411e) dm-2 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:2 sdf 8:80  active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 8:0:0:2 sdi 8:128 active ready running
mpfra1 (36589cfc000000f5feabc996aa1a12876) dm-3 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:3 sdg 8:96  active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 8:0:0:3 sdj 8:144 active ready running
mpdata2 (36589cfc00000025b4072a1536ade2f9d) dm-4 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:1 sde 8:64  active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 8:0:0:1 sdh 8:112 active ready running
  
--since the Oracle Restart is not going to mount the disks automatically, let's give him a hand
grid@has03:[GRID]:/home/grid $> crsctl stop has -f
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'has03'
CRS-2673: Attempting to stop 'ora.LISTENER.lsnr' on 'has03'
CRS-2673: Attempting to stop 'ora.evmd' on 'has03'
CRS-2673: Attempting to stop 'ora.asm' on 'has03'
CRS-2677: Stop of 'ora.LISTENER.lsnr' on 'has03' succeeded
CRS-2677: Stop of 'ora.evmd' on 'has03' succeeded
CRS-2677: Stop of 'ora.asm' on 'has03' succeeded
CRS-2673: Attempting to stop 'ora.cssd' on 'has03'
CRS-2677: Stop of 'ora.cssd' on 'has03' succeeded
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'has03' has completed
CRS-4133: Oracle High Availability Services has been stopped.

grid@has03:[GRID]:/home/grid $> crsctl start has
CRS-4123: Oracle High Availability Services has been started.

--It's AAAALLLLLIVEEEEE!!!
grid@has03:[GRID]:/home/grid $> crsctl status res -t
--------------------------------------------------------------------------------
Name           Target  State        Server                   State details
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.DATA.dg
               ONLINE  ONLINE       has03                    STABLE
ora.FRA.dg
               ONLINE  ONLINE       has03                    STABLE
ora.LISTENER.lsnr
               ONLINE  ONLINE       has03                    STABLE
ora.asm
               ONLINE  ONLINE       has03                    Started,STABLE
ora.ons
               OFFLINE OFFLINE      has03                    STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.cssd
      1        ONLINE  ONLINE       has03                    STABLE
ora.diskmon
      1        OFFLINE OFFLINE                               STABLE
ora.evmd
      1        ONLINE  ONLINE       has03                    STABLE
ora.money.db
      1        ONLINE  ONLINE       has03                    Open,HOME=/u01/app/o
                                                             racle/product/19c/db
                                                             home_1,STABLE
-------------------------------------------------------------------------------- C’est fini mes amis. In this article, I hope I have shown you how to create a homemade environment to implement and test multipath disks. À la prochaine.

Playing With Oracle ASM and Multipath Disks — Benchmarking Your Performance

Previously, I explained where only the DB binaries were corrupted. Now, let's try to fix a node with only the GRID binaries corrupted. how to fix a node My configuration
Oracle RAC with 2 nodes: ol8-19-rac1 and ol8-19-rac2
CDB: cdbrac1
PBD: pdb1

Grid Version
34318175;TOMCAT RELEASE UPDATE 19.0.0.0.0 (34318175)
34160635;OCW RELEASE UPDATE 19.16.0.0.0 (34160635)
34139601;ACFS RELEASE UPDATE 19.16.0.0.0 (34139601)
34133642;Database Release Update : 19.16.0.0.220719 (34133642)
33575402;DBWLM RELEASE UPDATE 19.0.0.0.0 (33575402)

DB Version
34086870;OJVM RELEASE UPDATE: 19.16.0.0.220719 (34086870)
34160635;OCW RELEASE UPDATE 19.16.0.0.0 (34160635)
34133642;Database Release Update : 19.16.0.0.220719 (34133642)

When you see <dbenv>, load the DB HOME variables.
When you see <gridenv>, load the GRID HOME variables.

When you see <bnode>, execute the command on the broken node.
When you see <anode>, execute the command on any other working node. I am using an installation where both DB and GRID are installed under the user ORACLE, and I set the variables to access each environment. But the same procedure works even if the installation is done using two different users (usually oracle e grid). Always validate any procedure before you try it in a production environment. Scenario B - GRID Binaries Corrupted On ol8-19-rac2 After Patch Apply In this scenario, only the GRID binaries were affected, so let's try to preserve the DB binaries. The stack is already down since the binaries are corrupted. 01. Backup the OCR configuration
================================
As root, at any other node, create a OCR's backup. Better safe than sorry.


<anode gridenv root>
[root@ol8-19-rac2 scripts]# ocrconfig -manualbackup
ol8-19-rac2     2022/11/17 13:40:44     +CRS:/ol8-19-cluster/OCRBACKUP/backup_20221117_134044.ocr.258.1121002845     896235792


02. Check whether both nodes are unpinned (they must be Unpinned to proceed)
============================================================================
<anode gridenv>
[oracle@ol8-19-rac1 ~]$ olsnodes -s -t
ol8-19-rac1     Active  Unpinned
ol8-19-rac2     Active  Unpinned

If the node is pinned, then run the crsctl unpin css.


03. Backup the $ORACLE_HOME/network/admin
=========================================
<bnode gridenv>
[oracle@ol8-19-rac2 ~]$ mkdir -p /tmp/oracle; tar cvf /tmp/oracle/grid_netadm.tar -C $ORACLE_HOME/network/admin .


04. Deinstall the GRID binaries
===============================
<bnode gridenv>
[oracle@ol8-19-rac2 ~]$ $ORACLE_HOME/deinstall/deinstall -local
Confirm whether everything is OK, then say yes.

After, execute  the root step on another prompt.
[root@ol8-19-rac2 ~]# /u01/app/19.0.0/grid/crs/install/rootcrs.sh -force  -deconfig -paramfile "/tmp/deinstall2022-11-17_01-49-44PM/response/deinstall_OraGI19Home1.rsp"
...
2022/11/17 13:58:09 CLSRSC-336: Successfully deconfigured Oracle Clusterware stack on this node

Now, press enter to continue and finish the deinstall.


05. Remove the broken node from the cluster
===========================================
<anode gridenv root>
[root@ol8-19-rac1 ~]# crsctl delete node -n ol8-19-rac2
CRS-4661: Node ol8-19-rac2 successfully deleted.


06. Remove the broken node's VIP
================================
<anode gridenv root>
[root@ol8-19-rac1 ~]# srvctl stop vip -vip ol8-19-rac2
[root@ol8-19-rac1 ~]# srvctl remove vip -vip ol8-19-rac2
Please confirm that you intend to remove the VIPs ol8-19-rac2 (y/[n]) y


07. Check if the cluster is OK after the node removal
=====================================================
<anode gridenv>
[oracle@ol8-19-rac1 ~]$ cluvfy stage -post nodedel -n ol8-19-rac2 -verbose

Performing following verification checks ...

  Node Removal ...
    CRS Integrity ...PASSED
    Clusterware Version Consistency ...PASSED
  Node Removal ...PASSED

Post-check for node removal was successful.

CVU operation performed:      stage -post nodedel
Date:                         Nov 17, 2022 2:04:22 PM
Clusterware version:          19.0.0.0.0
CVU home:                     /u01/app/19.0.0/grid
Grid home:                    /u01/app/19.0.0/grid
User:                         oracle
Operating system:             Linux5.4.17-2136.312.3.4.el8uek.x86_64


08. Pre node addition validation
================================
If we were adding an actual new node, we were supposed to run some cluster verification checks to confirm that everything is OK, but since the node was already part of the cluster, I usually skip this validation, but you can execute it, if you want.

[oracle@ol8-19-rac1 ~]$ cluvfy stage -pre nodeadd -n ol8-19-rac2 -verbose -fixup


09. Add the node back
=====================
From any other node, add the ex-broken node back. This step takes a while, as it copies the files from one node to another.

<anode gridenv>
[oracle@ol8-19-rac1 ~]$ $ORACLE_HOME/addnode/addnode.sh -silent "CLUSTER_NEW_NODES={ol8-19-rac2}" "CLUSTER_NEW_VIRTUAL_HOSTNAMES={ol8-19-rac2-vip}" "CLUSTER_NEW_NODE_ROLES={hub}"

On the ex-broken node, execute the root script
<bnode root>
[root@ol8-19-rac2 tmp]# /u01/app/19.0.0/grid/root.sh


10. Check if the cluster is OK
==============================
From any other node, run the cluster verification.

<anode grid>
[oracle@ol8-19-rac1 ~]$ cluvfy stage -post nodeadd -n ol8-19-rac2 -verbose
...
Post-check for node addition was successful.


CVU operation performed:      stage -post nodeadd
Date:                         Nov 17, 2022 2:32:12 PM
Clusterware version:          19.0.0.0.0
CVU home:                     /u01/app/19.0.0/grid
Grid home:                    /u01/app/19.0.0/grid
User:                         oracle
Operating system:             Linux5.4.17-2136.312.3.4.el8uek.x86_64 Voilà, your cluster, and your database are supposed to be back online. [oracle@ol8-19-rac2 ~]$ crsctl check cluster -all
**************************************************************
ol8-19-rac1:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************
ol8-19-rac2:
CRS-4537: Cluster Ready Services is online
CRS-4529: Cluster Synchronization Services is online
CRS-4533: Event Manager is online
**************************************************************

[oracle@ol8-19-rac2 ~]$ srvctl status database -db cdbrac
Instance cdbrac1 is running on node ol8-19-rac1
Instance cdbrac2 is running on node ol8-19-rac2 In my next article, I'll show you how to recover from a scenario where we lost both GRID and DB binaries.

Fixing Oracle RAC Node Problems With Addnode: GRID Binaries

In this blog, I will show you how to quickly create an entirely free app using a JavaScript program that runs within the free Oracle database and calls AI, the results of which are stored in the database and can then be accessed using , , Rest, or any other language. All of the source code is, of course, available . Hugging Face SQL JSON here A typical sequence of actions in applications, both in general and particularly in AI applications, involves an application utilizing an AI service. The acquired information is then stored in a database, ready for retrieval, subsequent processing (such as using OML), analysis, and future queries. When the command originates directly from the database, the data is promptly stored and gains higher reliability. This approach is in-process and eliminates the need for an additional network call for persistence. Additionally, by housing the logic and even code within the database, the remarkable features of the robust Oracle database, including high availability, management, and observability, are naturally harnessed. This distinct capability is a hallmark of the Oracle database, which encompasses both Java and, as detailed in this blog, JavaScript runtime engines within the database itself. Hugging Face specializes in crafting tools for constructing applications using machine learning. Particularly notable is its transformers library designed for natural language processing applications, along with its platform facilitating the sharing of machine learning models and datasets. It has garnered significant popularity in recent years. In short, we’ll… Create a cohere.com or huggingface.co account, create and copy an access token, and select a model. Create the Oracle database. Create the database user and table(s). Run a short JavaScript program in the database to make a call to the Cohere or Hugging Face AI model and store the results in the table. Query these results using SQL, JSON, Rest, etc. Setup Cohere account and AI model Go to https://cohere.com and , go to your , and click the button. Sign Up Profile Settings Click on , then API Keys, create a key (or use trial) and copy its value for use later. Dashboard Click on and select the hamburger menu/icon on the left of any page to view the API Reference list and select one. In this case, we will select section and API Reference generate Co.Generate. Select and then select the option in order to see a sample code snippet to call the model. Ianguage JavaScript Setup Hugging Face account and AI model Go to https://huggingface.co and , go to your , and click the button. Sign Up Profile Settings Click on , create a token, and copy its value for use later. Access Tokens Click on and select a model. In this case, we will select a model under the section for Models Natural Language Processing Question Answering. Select a model (perhaps one of the more popular ones), notice the information in the on the left, and then select the drop-down menu on the right. Model Card Deploy Select and then select the option in order to see a sample code snippet to call the model. Inference API JavaScript Setup Oracle Database We can use any flavor of the Oracle database 23c. On the cloud, we can use Oracle always free autonomous database later this year when 23c should be available. We can use the Oracle 23c Free version as it’s available now and we can simply install or use a container image locally. Or of course, we could use the local for dev and cloud for production, etc. and either of these options is very quick to set up… Oracle Database Free… You can go here to set up the Free Oracle Database. Using the container image is very simple. You can simply pull the image: docker pull container-registry.oracle.com/database/free:latest Then, execute the one line below, replacing with a password of your choice (you can also add a parameter with a directory location in order to persist changes across restarts). Notice the param that allows calls out of the container. This is the setting for Macs and will be different if running on a different OS. -e ORACLE_PASSWORD=Welcome12345 -v oracle-volume:/somedirectory --add-host docker.for.mac.host.internal:host-gateway docker run -d -p 1521:1521 — add-host docker.for.mac.host.internal:host-gateway -e ORACLE_PASSWORD=Welcome12345 gvenzl/oracle-free Setup SQLcl (or Database Actions) and connect You can install SQLcl to manage the database by: Downloading and install from this location https://www.oracle.com/database/sqldeveloper/technologies/sqlcl/download/ This will provide an executable that we will use to administer the database. For convenience, you may add to your PATH. [SQLcl_INSTALL_DIR]/bin/sql [SQLcl_INSTALL_DIR]/bin Login replacing with the location of your SQLcl and replacing with the one you provided as when creating the database Here is an example when using a local install (eg Oracle Database Free container image): [SQLcl_INSTALL_DIR] Welcome12345 ORACLE_PASSWORD [SQLcl_INSTALL_DIR]/bin/sql /nolog SQL> connect sys@//localhost:1521/freepdb1 as sysdba Password? (**********?) ************* Connected. Create the users, with appropriate privileges, that will call Cohere and/or Hugging Face via JavaScript. Run the following SQL files to create the user and its necessary grants and ACLs (note that these can be further tightened for better security). aijs @sql/create_aijs_acl.sql SQL> @sql/create_aijs_user.sql``SQL> Now connect the user and create a table to store the results of the call to Hugging Face SQL> connect aijs/Welcome12345; SQL> create table huggingfacejson (id json); SQL> create table coherejson (id json); Now everything is ready to run! Run either the Cohere or HuggingFace queries from the JavaScript code in the database Cohere Example SQL> @sql/coherequery.sql PL/SQL procedure successfully completed. Then, check the JSON results stored in the table by doing a SQL query. SQL> select * from coherejson; [{"id":"1b42f8f9-ea6d-4a65-8f02-bdcf89d9bd79","generations":[{"id":"d6467c0b-4a78-4dd4-b822-c1e2bfa4ecb0","text":"\n LLMs or Large Language Models are artificial intelligence tools that can read, summarize and translate texts and"}],"prompt":"Please explain to me how LLMs work","meta":{"api_version":{"version":"1"}}} Looking at the code we just executed we can see the JavaScript module created and the function being called: create or replace mle module cohere_module language javascript as import "mle-js-fetch"; import "mle-js-oracledb"; export async function cohereDemo(apiToken) { if (apiToken === undefined) { throw Error("must provide an API token"); } const modelId = "generate"; const restAPI = `https://api.cohere.ai/v1/${modelId}`; const headers = { accept: 'application/json', 'content-type': 'application/json', "Authorization": `Bearer ${apiToken}` }; const payload = { max_tokens: 20, return_likelihoods: 'NONE', truncate: 'END', prompt: 'Please explain to me how LLMs work' }; const resp = await fetch( restAPI, { method: "POST", headers: headers, body: JSON.stringify(payload), credentials: "include" } ); const resp_json = await resp.json(); session.execute( `INSERT INTO COHEREJSON (id) VALUES (:resp_json)`, [ JSON.stringify(resp_json) ] ); } / create or replace procedure coherequery( p_API_token varchar2 ) as mle module cohere_module signature 'cohereDemo(string)'; / -- this is how you can test the API call begin utl_http.set_wallet('system:'); coherequery('[yourcoheretokenhere]'); end; / Hugging Face Example SQL> @sql/huggingfacequery.sql PL/SQL procedure successfully completed. Then, check the JSON results stored in the table by doing a SQL query. SQL> select * from huggingfacejson; [{"score":0.16964051127433777,"token":2053,"token_str":"no","sequence":"the answer to the universe is no."},{"score":0.07344779372215271,"token":2498,"token_str":"nothing","sequence":"the answer to the universe is nothing."},{"score":0.05803246051073074,"token":2748,"token_str":"yes","sequence":"the answer to the universe is yes."},{"score":0.043957971036434174,"token":4242,"token_str":"unknown","sequence":"the answer to the universe is unknown."},{"score":0.04015727713704109,"token":3722,"token_str":"simple","sequence":"the answer to the universe is simple."}] Looking at the code we just executed we can see the JavaScript module created and the function being called: create or replace mle module huggingface_module language javascript as import "mle-js-fetch"; import "mle-js-oracledb"; export async function huggingfaceDemo(apiToken) { if (apiToken === undefined) { throw Error("must provide an API token"); } const payload = { inputs: "The answer to the universe is [MASK]." }; const modelId = "bert-base-uncased"; const headers = { "Authorization": `Bearer ${apiToken}` }; const restAPI = `https://api-inference.huggingface.co/models/${modelId}`; const resp = await fetch( restAPI, { method: "POST", headers: headers, body: JSON.stringify(payload), credentials: "include" } ); const resp_json = await resp.json(); session.execute( `INSERT INTO HUGGINGFACEJSON (id) VALUES (:resp_json)`, [ JSON.stringify(resp_json) ] ); } / create or replace procedure huggingfacequery( p_API_token varchar2 ) as mle module huggingface_module signature 'huggingfaceDemo(string)'; / -- this is how you can test the API call begin utl_http.set_wallet('system:'); huggingfacequery('[hf_yourhuggingfacetokenhere]'); end; / Useful parameters and debug information for Hugging Face can be found . here The results can now be queried, analyzed, etc. using SQL or JSON (simultaneously thanks to the new JSON duality feature), REST, or even the MongoDB API.Oracle Database is the perfect database for AI for a number of reasons, particularly as it is a vector database with capabilities such as the following already available today: Native data types for vector representation and storage: RAW, BLOB, JSON In-Memory Column Store to store & search vector embeddings w/ SIMD kernels for amazing performance Extensible indexing framework to create data-model specific indices (e.g., Text, Spatial) Native Oracle Machine Learning APIs — Modeling, Classification, Scoring, Clustering, etc. Plus, many other capabilities which, used together, make Oracle a better Vector Database DMLs, Parallel Loading, Partitioning, Advanced Compression, Parallel Query, RAC, Sharding, etc. It is also possible to call Oracle OCI AI and other services from within the Oracle database. Conclusion The blog went into how to call Hugging Face APIs from within the Oracle database using JavaScript thus demonstrating a powerful combination of features perfectly suited to a broad array of AI solutions and friendly to JavaScript developers. Some other blogs related to JavaScript in the database, in general, the MultiLingual Engine (MLE) that makes it possible, etc. can be found and . Thanks to Martin and Lucas for all their help. in Martin Bach’s blogs this post about JavaScript modules I look forward to any comments or questions you may have and really appreciate your time reading. Also published . here

Calling Hugging Face AI From an Oracle Database Using JavaScript

Hi, and welcome back to the second part. If you missed the first part, where we configured the TrueNAS, please look . Now we will configure the iSCSI, the multipath, and the ASM disks. here Oracle Environment For the sake of simplicity, I will use a VM previously configured with Oracle Restart and one database already used in other tests. I only added two new network interfaces to the VM to use the multipath. I’ve added the TrueNAS VM IPs to the /etc/hosts. Configuring the new network interfaces You must configure the new internal networks with IPs in the same network as the TrueNAS portal (10.1.1.1/10.1.2.1). Configuring the iSCSI --discover the iscsi target
root #> iscsiadm -m discovery -t sendtargets -p truenas1
10.1.2.1:3260,1 iqn.2005-10.org.freenas.ctl:has03
10.1.1.1:3260,1 iqn.2005-10.org.freenas.ctl:has03

--enable automatic login during startup
root #> iscsiadm -m node --op update -n node.startup -v automatic

--login to both network interfaces
root #> iscsiadm -m node -p truenas1 --login
root #> iscsiadm -m node -p truenas2 --login Configuring the multipath --enable and start the service
root@has03:/ $> systemctl enable multipathd
root@has03:/ $> systemctl start multipathd

--create the multipath.conf
cat <<EOF>/etc/multipath.conf
defaults {
    find_multipaths yes
    user_friendly_names yes
    failback immediate
}

blacklist {
     devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
     devnode "^hd[a-z][[0-9]*]"
     devnode "^sda[[0-9]*]"
     devnode "^cciss!c[0-9]d[0-9]*"
}
EOF

root@has03:/ $> ll /etc/multipath.conf
-rw-r--r--. 1 root root 849 Apr 30 10:24 /etc/multipath.conf

--reload the service
root@has03:/ $> systemctl reload multipathd

--check if the disks exist
root@has03:/ $> ll /dev/mapper
total 0
crw-------. 1 root root 10, 236 Apr 30 09:34 control
lrwxrwxrwx. 1 root root       7 Apr 30 10:24 mpathd -> ../dm-4
lrwxrwxrwx. 1 root root       7 Apr 30 10:24 mpathe -> ../dm-2
lrwxrwxrwx. 1 root root       7 Apr 30 10:24 mpathf -> ../dm-3
lrwxrwxrwx. 1 root root       7 Apr 30 09:34 ol-root -> ../dm-0
lrwxrwxrwx. 1 root root       7 Apr 30 09:34 ol-swap -> ../dm-1 Using the multipath command, you can check if the disks use both networks. root@has03:/ $> multipath -ll

mpathe (36589cfc000000580ddee277e9cda411e) dm-2 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active   <--- network 1
| `- 7:0:0:2 sdf 8:80  active ready running
`-+- policy='service-time 0' prio=50 status=enabled  <--- network 2
  `- 8:0:0:2 sdi 8:128 active ready running

mpathd (36589cfc00000025b4072a1536ade2f9d) dm-4 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:1 sde 8:64  active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 8:0:0:1 sdh 8:112 active ready running

mpathf (36589cfc000000f5feabc996aa1a12876) dm-3 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:3 sdg 8:96  active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 8:0:0:3 sdj 8:144 active ready running Let’s simplify our lives by adding aliases to the disks. I’ve updated the multipath.conf file and did reload the service. root@has03:/ $> cat /etc/multipath.conf
defaults {
    find_multipaths yes
    user_friendly_names yes
    failback immediate
}

blacklist {
     devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
     devnode "^hd[a-z][[0-9]*]"
     devnode "^sda[[0-9]*]"
     devnode "^cciss!c[0-9]d[0-9]*"
}

multipaths {
    multipath {
        wwid    36589cfc000000580ddee277e9cda411e
        alias   mpdata1
    }
    multipath {
        wwid    36589cfc00000025b4072a1536ade2f9d
        alias   mpdata2
    }
    multipath {
        wwid    36589cfc000000f5feabc996aa1a12876
        alias   mpfra1
    }
}

root@has03:/ $> systemctl reload multipathd Now we have better names (aliases). root@has03:/ $> multipath -ll

mpfra1 (36589cfc000000f5feabc996aa1a12876) dm-3 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:3 sdg 8:96  active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 8:0:0:3 sdj 8:144 active ready running

mpdata2 (36589cfc00000025b4072a1536ade2f9d) dm-4 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:1 sde 8:64  active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 8:0:0:1 sdh 8:112 active ready running

mpdata1 (36589cfc000000580ddee277e9cda411e) dm-2 TrueNAS,iSCSI Disk
size=5.0G features='0' hwhandler='1 alua' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| `- 7:0:0:2 sdf 8:80  active ready running
`-+- policy='service-time 0' prio=50 status=enabled
  `- 8:0:0:2 sdi 8:128 active ready running Nice, it worked. Now it’s time to use those disks in our ASM. The VM has03 already has an Oracle Restart installation, so I already have 3 ASM local disks. Let’s add our multipath disks to the UDEV. --find the disks' UUID
root@has03:/ $> udevadm info --query=all --name=/dev/mapper/mpdata1 | grep UUID
E: DM_UUID=mpath-36589cfc000000580ddee277e9cda411e

root@has03:/ $> udevadm info --query=all --name=/dev/mapper/mpdata2 | grep UUID
E: DM_UUID=mpath-36589cfc00000025b4072a1536ade2f9d

root@has03:/ $> udevadm info --query=all --name=/dev/mapper/mpfra1 | grep UUID
E: DM_UUID=mpath-36589cfc000000f5feabc996aa1a12876

--edit the udev conf file to add the new disks and rules, using the previously UUIDs
root@has03:/ $> cat /etc/udev/rules.d/96-asm.rules
#multipath disks
KERNEL=="dm-*", SUBSYSTEM=="block", ENV{DM_UUID}=="mpath-36589cfc000000580ddee277e9cda411e", SYMLINK+="oracleasm/mpdata1", OWNER="grid", GROUP="asmadmin", MODE="0660", OPTIONS:="nowatch"
KERNEL=="dm-*", SUBSYSTEM=="block", ENV{DM_UUID}=="mpath-36589cfc00000025b4072a1536ade2f9d", SYMLINK+="oracleasm/mpdata2", OWNER="grid", GROUP="asmadmin", MODE="0660", OPTIONS:="nowatch"
KERNEL=="dm-*", SUBSYSTEM=="block", ENV{DM_UUID}=="mpath-36589cfc000000f5feabc996aa1a12876", SYMLINK+="oracleasm/mpfra1", OWNER="grid", GROUP="asmadmin", MODE="0660", OPTIONS:="nowatch"
#local disks
KERNEL=="sd*", SUBSYSTEM=="block", ENV{ID_SERIAL}=="VBOX_HARDDISK_VB647c8062-550861fd", SYMLINK+="oracleasm/data1", OWNER="grid", GROUP="asmadmin", MODE="0660", OPTIONS:="nowatch"
KERNEL=="sd*", SUBSYSTEM=="block", ENV{ID_SERIAL}=="VBOX_HARDDISK_VB84084872-e9ff80ef", SYMLINK+="oracleasm/data2", OWNER="grid", GROUP="asmadmin", MODE="0660", OPTIONS:="nowatch"
KERNEL=="sd*", SUBSYSTEM=="block", ENV{ID_SERIAL}=="VBOX_HARDDISK_VB9de588bd-fea7d130", SYMLINK+="oracleasm/fra1", OWNER="grid", GROUP="asmadmin", MODE="0660", OPTIONS:="nowatch"

--reload UDEV
root@has03:/ $>udevadm control --reload-rules && udevadm trigger

--check if the disks exist
root@has03:/ $> ll /dev/oracleasm
total 0
lrwxrwxrwx. 1 root root 6 Apr 30 10:58 data1 -> ../sdb
lrwxrwxrwx. 1 root root 6 Apr 30 10:58 data2 -> ../sdc
lrwxrwxrwx. 1 root root 6 Apr 30 10:58 fra1 -> ../sdd
lrwxrwxrwx. 1 root root 7 Apr 30 10:58 mpdata1 -> ../dm-2
lrwxrwxrwx. 1 root root 7 Apr 30 10:58 mpdata2 -> ../dm-4
lrwxrwxrwx. 1 root root 7 Apr 30 10:58 mpfra1 -> ../dm-3 Configuring the Oracle ASM Now let’s swap our local disks with the multipath disks on the ASM diskgroups. --check the candidates disks
grid@has03:[GRID]:/home/grid $> asmcmd lsdsk --candidate
Path
/dev/oracleasm/mpdata1
/dev/oracleasm/mpdata2
/dev/oracleasm/mpfra1

--check the current disks' names
--I removed some columns from the result below
grid@has03:[GRID]:/home/grid $> asmcmd lsdsk -k
Total_MB  Free_MB  OS_MB  Name       Failgroup  Path
    5120     3468   5120  DATA_0000  DATA_0000  /dev/oracleasm/data1
    5120     3464   5120  DATA_0001  DATA_0001  /dev/oracleasm/data2
    5120     3323   5120  FRA_0000   FRA_0000   /dev/oracleasm/fra1

--swap the disks
grid@has03:[GRID]:/home/grid $> sqlplus / as sysasm

SQL*Plus: Release 19.0.0.0.0 - Production on Sat Apr 30 11:05:50 2022
Version 19.14.0.0.0

Copyright (c) 1982, 2021, Oracle.  All rights reserved.


Connected to:
Oracle Database 19c Enterprise Edition Release 19.0.0.0.0 - Production
Version 19.14.0.0.0

SQL> alter diskgroup fra add disk '/dev/oracleasm/mpfra1' drop disk fra_0000 rebalance power 1024;

Diskgroup altered.

SQL> alter diskgroup data add disk '/dev/oracleasm/mpdata1', '/dev/oracleasm/mpdata2' drop disk data_0000, data_0001 rebalance power 1024;

Diskgroup altered.

SQL> Now we wait until the rebalance ends and validate the new disks. Voilà, everything working like a charm! That’s the end of the second part. In the next and last part, we will run some tests on our new multipath disks. If you missed the first part, where we configured the TrueNAS, please look . here À la prochaine.

Playing With Oracle ASM and Multipath Disks - Configuring the ISCSI and the ASM Disks

Hello friends, The Oracle DBA occasionally needs to update some of the Oracle Clusterware network configurations. Today let's check how to update the private network part. The Environment Oracle RAC with 2 nodes: ol8-19-rac1 and ol8-19-rac2

Oracle Linux Server release 8.8

Grid Version
34318175;TOMCAT RELEASE UPDATE 19.0.0.0.0 (34318175)
34160635;OCW RELEASE UPDATE 19.16.0.0.0 (34160635)
34139601;ACFS RELEASE UPDATE 19.16.0.0.0 (34139601)
34133642;Database Release Update : 19.16.0.0.220719 (34133642)
33575402;DBWLM RELEASE UPDATE 19.0.0.0.0 (33575402)

DB Version
34086870;OJVM RELEASE UPDATE: 19.16.0.0.220719 (34086870)
34160635;OCW RELEASE UPDATE 19.16.0.0.0 (34160635)
34133642;Database Release Update : 19.16.0.0.220719 (34133642)

When you see <dbenv>, load the DB HOME variables.
When you see <gridenv>, load the GRID HOME variables.

IPs
# Public
192.168.56.161  ol8-19-rac1.localdomain  ol8-19-rac1
192.168.56.162  ol8-19-rac2.localdomain  ol8-19-rac2

# Virtual
192.168.56.163  ol8-19-rac1-vip.localdomain    ol8-19-rac1-vip
192.168.56.164  ol8-19-rac2-vip.localdomain    ol8-19-rac2-vip

# Private
10.1.2.161  ol8-19-rac1-priv.localdomain   ol8-19-rac1-priv
10.1.2.162  ol8-19-rac2-priv.localdomain   ol8-19-rac2-priv As the grid user, take a backup of profile.xml on all cluster nodes before proceeding. [oracle@ol8-19-rac1 ~]$ cp -p $ORACLE_HOME/gpnp/`hostname`/profiles/peer/profile.xml $ORACLE_HOME/gpnp/`hostname`/profiles/peer/profile.xml.bkp

[oracle@ol8-19-rac1 ~]$ ll $ORACLE_HOME/gpnp/`hostname`/profiles/peer/profile.xml.bkp

-rw-r--r--. 1 oracle oinstall 2171 May 27 20:09 /u01/app/19.0.0/grid/gpnp/ol8-19-rac1/profiles/peer/profile.xml.bkp Now, let’s check the Oracle CRS networks and the Linux networks. It’s possible to identify that Oracle is using the network as his private one. “eth2 10.1.2.0” [oracle@ol8-19-rac1 ~]$ oifcfg getif
eth1  192.168.56.0  global  public
eth2  10.1.2.0  global  cluster_interconnect,asm

[oracle@ol8-19-rac1 ~]$ ip -c -br a
lo               UNKNOWN        127.0.0.1/8 ::1/128
eth0             UP             10.0.2.15/24 fe80::a00:27ff:fe63:d73f/64
eth1             UP             192.168.56.161/24 192.168.56.163/24 192.168.56.166/24 192.168.56.165/24 fe80::a00:27ff:fe4f:b8aa/64
eth2             UP             10.1.2.161/24 169.254.1.211/19 fe80::a00:27ff:fe01:a7de/64
eth3             UP             10.1.3.161/24 fe80::a00:27ff:fef3:172b/64

[oracle@ol8-19-rac2 ~]$ ip -c -br a
lo               UNKNOWN        127.0.0.1/8 ::1/128
eth0             UP             10.0.2.15/24 fe80::a00:27ff:fe63:d73f/64
eth1             UP             192.168.56.162/24 192.168.56.164/24 192.168.56.167/24 fe80::a00:27ff:fe76:b954/64
eth2             UP             10.1.2.162/24 169.254.26.118/19 fe80::a00:27ff:fe7f:8663/64
eth3             UP             10.1.3.162/24 fe80::a00:27ff:fea8:d7c3/64 Let’s also check the ASM Listener configuration and take note. [oracle@ol8-19-rac1 ~]$ srvctl config listener -asmlistener
Name: ASMNET1LSNR_ASM
Type: ASM Listener
Owner: oracle
Subnet: 10.1.2.0
Home: <CRS home>
End points: TCP:1525
Listener is enabled.
Listener is individually enabled on nodes:
Listener is individually disabled on nodes:

[oracle@ol8-19-rac1 ~]$ srvctl status listener -l ASMNET1LSNR_ASM
Listener ASMNET1LSNR_ASM is enabled
Listener ASMNET1LSNR_ASM is running on node(s): ol8-19-rac2,ol8-19-rac1

[oracle@ol8-19-rac1 ~]$ srvctl config asm
ASM home: <CRS home>
Password file: +CRS/orapwASM
Backup of Password file: +CRS/orapwASM_backup
ASM listener: LISTENER
ASM instance count: 2
Cluster ASM listener: ASMNET1LSNR_ASM Firstly, let’s check if both nodes are able to reach the network we intend to use. [oracle@ol8-19-rac1 tmp]$ ping -c 3 10.1.3.161
PING 10.1.3.161 (10.1.3.161) 56(84) bytes of data.
64 bytes from 10.1.3.161: icmp_seq=1 ttl=64 time=0.010 ms
64 bytes from 10.1.3.161: icmp_seq=2 ttl=64 time=0.014 ms
64 bytes from 10.1.3.161: icmp_seq=3 ttl=64 time=0.018 ms

--- 10.1.3.161 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2052ms
rtt min/avg/max/mdev = 0.010/0.014/0.018/0.003 ms

[oracle@ol8-19-rac1 tmp]$ ping -c 3 10.1.3.162
PING 10.1.3.162 (10.1.3.162) 56(84) bytes of data.
64 bytes from 10.1.3.162: icmp_seq=1 ttl=64 time=0.168 ms
64 bytes from 10.1.3.162: icmp_seq=2 ttl=64 time=0.151 ms
64 bytes from 10.1.3.162: icmp_seq=3 ttl=64 time=0.171 ms

--- 10.1.3.162 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2068ms
rtt min/avg/max/mdev = 0.151/0.163/0.171/0.013 ms

[oracle@ol8-19-rac2 tmp]$ ping -c 3 10.1.3.161
PING 10.1.3.161 (10.1.3.161) 56(84) bytes of data.
64 bytes from 10.1.3.161: icmp_seq=1 ttl=64 time=0.153 ms
64 bytes from 10.1.3.161: icmp_seq=2 ttl=64 time=0.156 ms
64 bytes from 10.1.3.161: icmp_seq=3 ttl=64 time=0.176 ms

--- 10.1.3.161 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2081ms
rtt min/avg/max/mdev = 0.153/0.161/0.176/0.017 ms

[oracle@ol8-19-rac2 tmp]$ ping -c 3 10.1.3.162
PING 10.1.3.162 (10.1.3.162) 56(84) bytes of data.
64 bytes from 10.1.3.162: icmp_seq=1 ttl=64 time=0.010 ms
64 bytes from 10.1.3.162: icmp_seq=2 ttl=64 time=0.025 ms
64 bytes from 10.1.3.162: icmp_seq=3 ttl=64 time=0.015 ms

--- 10.1.3.162 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2037ms
rtt min/avg/max/mdev = 0.010/0.016/0.025/0.007 ms Since everything seems OK, now we will start changing the private network. We will change it from the subnet to . As the grid user, proceed as below in only one of the nodes. eth2:10.1.2.0 eth3:10.1.3.0 [oracle@ol8-19-rac1 ~]$ oifcfg setif -global eth3/10.1.3.0:cluster_interconnect,asm
[oracle@ol8-19-rac1 ~]$ srvctl add listener -asmlistener -l ASMNEWLSNR_ASM -subnet 10.1.3.0
[oracle@ol8-19-rac1 ~]$ srvctl update listener -listener ASMNET1LSNR_ASM -asm -remove -force

--The error below is expected, as we are only testing if the previous listener still exists.
[oracle@ol8-19-rac1 ~]$ lsnrctl stop ASMNET1LSNR_ASM

LSNRCTL for Linux: Version 19.0.0.0.0 - Production on 28-MAY-2023 07:55:09

Copyright (c) 1991, 2023, Oracle.  All rights reserved.

TNS-01101: Could not find listener name or service name ASMNET1LSNR_ASM Check if the ASM Listener was created correctly. [oracle@ol8-19-rac1 ~]$ srvctl config asm
ASM home: <CRS home>
Password file: +CRS/orapwASM
Backup of Password file: +CRS/orapwASM_backup
ASM listener: LISTENER
ASM instance count: 2
Cluster ASM listener: ASMNEWLSNR_ASM

[oracle@ol8-19-rac1 ~]$ srvctl config listener -asmlistener
Name: ASMNEWLSNR_ASM
Type: ASM Listener
Owner: oracle
Subnet: 10.1.3.0
Home: <CRS home>
End points: TCP:1526
Listener is enabled.
Listener is individually enabled on nodes:
Listener is individually disabled on nodes: In the 19c version, we also have one more resource to handle, the ASM Network. [oracle@ol8-19-rac1 ~]$ srvctl config asmnetwork
ASM network 1 exists
Subnet IPv4: 10.1.2.0//
Subnet IPv6:
Network is enabled
Network is individually enabled on nodes:
Network is individually disabled on nodes:

[oracle@ol8-19-rac1 ~]$ srvctl status asmnetwork
ASM network is running on ol8-19-rac2,ol8-19-rac1 As the root user, proceed as below. [root@ol8-19-rac1 scripts]# srvctl remove asmnetwork -netnum 1 -force
[root@ol8-19-rac1 scripts]# srvctl add asmnetwork -netnum 1 -subnet 10.1.3.0 Now let’s restart the entire cluster. [root@ol8-19-rac1 ~]# crsctl stop cluster -all -f
CRS-2673: Attempting to stop 'ora.crsd' on 'ol8-19-rac2'
CRS-2673: Attempting to stop 'ora.crsd' on 'ol8-19-rac1'
...
CRS-2673: Attempting to stop 'ora.cssd' on 'ol8-19-rac1'
CRS-2677: Stop of 'ora.cssd' on 'ol8-19-rac1' succeeded

[root@ol8-19-rac1 ~]# crsctl stop crs -f
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'ol8-19-rac1'
...
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'ol8-19-rac1' has completed
CRS-4133: Oracle High Availability Services has been stopped.

[root@ol8-19-rac2 ~]# crsctl stop crs -f
CRS-2791: Starting shutdown of Oracle High Availability Services-managed resources on 'ol8-19-rac2'
...
CRS-2793: Shutdown of Oracle High Availability Services-managed resources on 'ol8-19-rac2' has completed
CRS-4133: Oracle High Availability Services has been stopped.

[root@ol8-19-rac1 ~]# crsctl start crs
CRS-4123: Oracle High Availability Services has been started.

[root@ol8-19-rac2 ~]# crsctl start crs
CRS-4123: Oracle High Availability Services has been started. Check if everything is OK. [oracle@ol8-19-rac1 tmp]$ crsctl status res -t
--------------------------------------------------------------------------------
Name           Target  State        Server                   State details
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
ora.LISTENER.lsnr
               ONLINE  ONLINE       ol8-19-rac1              STABLE
               ONLINE  ONLINE       ol8-19-rac2              STABLE
ora.chad
               ONLINE  ONLINE       ol8-19-rac1              STABLE
               ONLINE  ONLINE       ol8-19-rac2              STABLE
ora.net1.network
               ONLINE  ONLINE       ol8-19-rac1              STABLE
               ONLINE  ONLINE       ol8-19-rac2              STABLE
ora.ons
               ONLINE  ONLINE       ol8-19-rac1              STABLE
               ONLINE  ONLINE       ol8-19-rac2              STABLE
ora.proxy_advm
               OFFLINE OFFLINE      ol8-19-rac1              STABLE
               OFFLINE OFFLINE      ol8-19-rac2              STABLE
--------------------------------------------------------------------------------
Cluster Resources
--------------------------------------------------------------------------------
ora.ASMNEWLSNR_ASM.lsnr(ora.asmgroup)
      1        ONLINE  ONLINE       ol8-19-rac1              STABLE
      2        ONLINE  ONLINE       ol8-19-rac2              STABLE
ora.CRS.dg(ora.asmgroup)
      1        ONLINE  ONLINE       ol8-19-rac1              STABLE
      2        ONLINE  ONLINE       ol8-19-rac2              STABLE
ora.DATA.dg(ora.asmgroup)
      1        ONLINE  ONLINE       ol8-19-rac1              STABLE
      2        ONLINE  ONLINE       ol8-19-rac2              STABLE
ora.LISTENER_SCAN1.lsnr
      1        ONLINE  ONLINE       ol8-19-rac2              STABLE
ora.LISTENER_SCAN2.lsnr
      1        ONLINE  ONLINE       ol8-19-rac1              STABLE
ora.LISTENER_SCAN3.lsnr
      1        ONLINE  ONLINE       ol8-19-rac1              STABLE
ora.RECO.dg(ora.asmgroup)
      1        ONLINE  ONLINE       ol8-19-rac1              STABLE
      2        ONLINE  ONLINE       ol8-19-rac2              STABLE
ora.asm(ora.asmgroup)
      1        ONLINE  ONLINE       ol8-19-rac1              Started,STABLE
      2        ONLINE  ONLINE       ol8-19-rac2              Started,STABLE
ora.asmnet1.asmnetwork(ora.asmgroup)
      1        ONLINE  ONLINE       ol8-19-rac1              STABLE
      2        OFFLINE OFFLINE                               STABLE
ora.cdbrac.db
      1        ONLINE  ONLINE       ol8-19-rac1              Open,HOME=/u01/app/o
                                                             racle/product/19.0.0
                                                             /dbhome_1,STABLE
      2        ONLINE  ONLINE       ol8-19-rac2              Open,HOME=/u01/app/o
                                                             racle/product/19.0.0
                                                             /dbhome_1,STABLE
ora.cvu
      1        ONLINE  ONLINE       ol8-19-rac1              STABLE
ora.ol8-19-rac1.vip
      1        ONLINE  ONLINE       ol8-19-rac1              STABLE
ora.ol8-19-rac2.vip
      1        ONLINE  ONLINE       ol8-19-rac2              STABLE
ora.qosmserver
      1        ONLINE  ONLINE       ol8-19-rac1              STABLE
ora.scan1.vip
      1        ONLINE  ONLINE       ol8-19-rac2              STABLE
ora.scan2.vip
      1        ONLINE  ONLINE       ol8-19-rac1              STABLE
ora.scan3.vip
      1        ONLINE  ONLINE       ol8-19-rac1              STABLE
-------------------------------------------------------------------------------- In my case, the ASM Network was not running on node 2, so I started it manually, and I will check in future reboots if I face the same issue again. [oracle@ol8-19-rac2 tmp]$ srvctl start asmnetwork

[oracle@ol8-19-rac2 tmp]$ srvctl status asmnetwork
ASM network is running on ol8-19-rac2,ol8-19-rac1 Since everything is running smoothly, let’s remove the previous network from the Oracle CRS. As the grid user, proceed as below. [oracle@ol8-19-rac1 tmp]$ oifcfg delif -global eth2/10.1.2.0

[oracle@ol8-19-rac1 tmp]$ oifcfg getif
eth1  192.168.56.0  global  public
eth3  10.1.3.0  global  cluster_interconnect,asm In the next article, I will explain how to update the IP from the other layers of the Oracle CRS. That’s it!

How to Modify Private Network Information in Oracle Clusterware 19c

Occasionally, a DBA faces an Oracle RAC node that needs to be fixed, usually after applying a nasty patch. Currently, my first approach is to remove the node, then add it back. There are other methods to try fixing the problem, but they usually will take some time, such as opening an SR with Oracle. Even though it sounds complicated, it's not. I will show you how to recover a node from several disaster scenarios. A. GRID binaries corrupted on ol8-19-rac2 B. GRID binaries corrupted on ol8-19-rac2 C. GRID and DB binaries corrupted on ol8-19-rac2 My configuration Oracle RAC with 2 nodes: ol8-19-rac1 and ol8-19-rac2 CDB: cdbrac1 PBD: pdb1 Grid Version 34318175;TOMCAT RELEASE UPDATE 19.0.0.0.0 (34318175) 34160635;OCW RELEASE UPDATE 19.16.0.0.0 (34160635) 34139601;ACFS RELEASE UPDATE 19.16.0.0.0 (34139601) 34133642;Database Release Update : 19.16.0.0.220719 (34133642) 33575402;DBWLM RELEASE UPDATE 19.0.0.0.0 (33575402) DB Version 34086870;OJVM RELEASE UPDATE: 19.16.0.0.220719 (34086870) 34160635;OCW RELEASE UPDATE 19.16.0.0.0 (34160635) 34133642;Database Release Update : 19.16.0.0.220719 (34133642) When you see , load the DB HOME variables. <dbenv> When you see , load the GRID HOME variables. <gridenv> When you see , execute the command on the broken node. <bnode> When you see , execute the command on any other working node. <anode> I am using an installation where both DB and GRID are installed under the user ORACLE, and I set the variables to access each environment. But the same procedure works even if the installation uses two different users (usually oracle e grid). OBS: Always validate any procedure before you try it in a production environment. Scenario A - DB Binaries Corrupted On ol8-19-rac2 After Applying a Patch This scenario's grid binaries were unaffected, so we don't need to replace them. The database is already down since the binaries are corrupted. Backup the $ORACLE_HOME/network/admin <bnode dbenv>
[oracle@ol8-19-rac2 admin]$ mkdir -p /tmp/oracle; tar cvf /tmp/oracle/db_netadm.tar -C $ORACLE_HOME/network/admin . Deinstall the DB binaries <bnode dbenv>
[oracle@ol8-19-rac2 admin]$ $ORACLE_HOME/deinstall/deinstall -local Confirm the database name, and choose yes to delete the instance. It's not unusual to face file deletion error messages; ignore them. Add the node back If we were adding an actual new node, we were supposed to run some cluster verification checks to confirm that everything is OK, but since the node was already part of the cluster, let's skip that. Due to that, it's not unusual to face the message "[WARNING] [INS-13014] Target environment does not meet some optional requirements." ignore it. From any other node, add the ex-broken node back. This step takes a while, as it copies the files from one node to another. <anode dbenv>
[oracle@ol8-19-rac1 ~]$ $ORACLE_HOME/addnode/addnode.sh -silent "CLUSTER_NEW_NODES={ol8-19-rac2}"

As root, execute the following on the ex-broken node.
<bnodt>
[root@ol8-19-rac2 scripts]# /u01/app/oracle/product/19.0.0/dbhome_1/root.sh Add the instance back From any other node, as oracle user execute the following to each existing database to add the nodes' instance back (recreate UNDOTBS, REDOS, etc). <anode dbenv>
[oracle@ol8-19-rac1 ~]$ dbca -silent -ignorePrereqFailure -addInstance -nodeName ol8-19-rac2 -gdbName cdbrac -instanceName cdbrac2 -sysDBAUserName sys -sysDBAPassword SysPassword1 If needed, restore the $ORACLE_HOME/network/admin on the ex-broken node <bnode dbenv>
[oracle@ol8-19-rac2 admin]$ tar xfv /tmp/oracle/db_netadm.tar -C $ORACLE_HOME/network/admin

[oracle@ol8-19-rac2 ~]$ srvctl status database -db cdbrac
Instance cdbrac1 is running on node ol8-19-rac1
Instance cdbrac2 is running on node ol8-19-rac2 Voilà, that's it. Now your database is supposed to be back online on the ex-broken node. In the following article, I'll show how to recover from corrupted GRID binaries.

Oracle

oracle.com

135000 employees

Since 1977

COMPANY RANKING

Oracle

EVERGREEN INDEX #513

See more notable links about Oracle

Apply to get your Tech Company News Page live on HackerNoon.com today!

Read More Tech Stories Related to #Oracle

Oracle

Oracle

oracle.com

135000 employees

Since 1977

COMPANY RANKING

Oracle

EVERGREEN INDEX #513

Related CompaniesRank

Oracle Story MentionsComplete List

See more notable links about Oracle

Apply to get your Tech Company News Page live on HackerNoon.com today!

Read More Tech Stories Related to #Oracle

Oracle