Oracle Failover Database Cluster with Grid Infrastructure ...

2014 © Trivadis

BASEL BERN BRUGG LAUSANNE ZUERICH DUESSELDORF FRANKFURT A.M. FREIBURG I.BR. HAMBURG MUNICH STUTTGART VIENNA

2014 © Trivadis

Oracle Grid Infrastructure 12c Release 1

In Practice

Robert Bialek, MU-IMS

Principal Consultant

18 November 2014

DOAG Conference 2014: Oracle Grid Infrastructure 12.1 In Practice

1

2014 © Trivadis

Who Am I

Principal Consultant, Partner and Trainer at Trivadis GmbH

[email protected]

Focus:

Oracle Database High Availability

Database Administration

Backup/Recovery

Performance Tuning

Linux Administration

Trainer for the following Trivadis courses

Oracle Grid Infrastructure (O-GRINF)

Oracle Real Application Cluster (O-RAC)

Oracle Data Guard (O-DG)

18 November 2014


2

2014 © Trivadis

Brief introduction of Trivadis

18 November 2014


3

Trivadis is a market leader in IT consulting, system integration,

solution engineering and the provision of IT services focusing

on and technologies in Switzerland,

Germany and Austria.

We provide our services in the following strategic business areas:.

Our training services guarantee transfer of know-how.

2014 © Trivadis

With over 600 IT experts and specialists on site for you

18 November 2014


4

11 Trivadis branches with

over 600 employees

200 service level agreements

More than 4000 training participants

Research and development budget:

CHF 5.0 /EUR 4 million

Financially independent and

consistently profitable

Experience from more than 1900

projects per year for over 800

customers

Hamburg

Düsseldorf

Frankfurt

Freiburg Munich

Vienna

Stuttgart

Zurich Lausanne

Brugg Basel

Bern

2014 © Trivadis

Oracle Grid Infrastructure – Short History

Oracle version 10.1 introduced two software products

Cluster Ready Services (TruCluster) – cluster manager

Automatic Storage Management – logical volume manager

In the version 11.2 both products have been bundled into Oracle Grid

Infrastructure

A lot of new concepts: Policy Cluster, Server Pools, GNS, SCAN,…

Goal: easier management, reduction in hardcoding, more flexibility

In the version 12.1, Oracle Grid Infrastructure has been extended again

by many new concepts

Flex Cluster, Flex ASM, ASM Client Cluster, GNS Server/Client Cluster, …

18 November 2014


5

2014 © Trivadis

AGENDA

1. Standard Cluster with Standard ASM

2. Standard Cluster with Flex ASM

3. Flex Cluster with Flex ASM

4. ASM Client Cluster

5. Grid Naming Service (GNS)

6. Grid Infrastructure Management Repository

7. Upgrade / Downgrade

8. Conclusions

18 November 2014


6

2014 © Trivadis

18 November 2014


Standard Cluster with Standard ASM

7

2014 © Trivadis

Standard Cluster with Standard ASM – Big Picture

18 November 2014


8

Private Network

Public Network

Oracle ASM

ASM Disk Storage

HU

B N

od

e

Oracle ASM

DB

Instances

HU

B N

od

e

crsd.bin

OCR Writer

oraagent.bin orarootagent.bin

DB

Instances crsd.bin


… ADVM

ACFS

ADVM

ACFS

No

de #

1

No

de #

4

2014 © Trivadis

Standard Cluster with Standard ASM – Local Resource

Like pre 12c Grid Infrastructure architecture

Storage must be accessible on all cluster nodes (HUB nodes)

ASM instance is a local resource

One instance on all current and future cluster nodes

Delivers metadata to all local clients

ASM clients perform I/O directly to the disks

All local clients connect using Oracle Bequeath NT Protocol

18 November 2014


9

crsctl get node role status -all

Node 'cldb01' active role is 'hub'

Node 'cldb02' active role is 'hub'

crsctl get cluster mode config

Cluster is configured as "standard"

asmcmd showclustermode

ASM cluster : Flex mode disabled

ASM ASM ASM ASM

CLIENTS CLIENTS

2014 © Trivadis

Standard Cluster with Standard ASM – High Availability

Local hard dependency between clients and ASM

ASM instance crash will lead to crash of all its local

clients

To start a client the local ASM instance must be available

It is the default architecture after upgrade from a pre 12c release

You can convert the architecture at a later time to

Standard Cluster with Flex ASM

Flex Cluster with Flex ASM

You cannot convert Flex Cluster/ASM architectures to Standard Cluster

with Standard ASM, without cluster re-creation

18 November 2014


10

NOTE: ASMB terminating

ORA-15064: communication failure with ASM instance

ORA-03113: end-of-file on communication channel

Instance terminated by ASMB, pid = 4411

ASM ASM ASM

CLIENTS

2014 © Trivadis

Standard Cluster with Standard ASM – Installation

OUI in GUI mode

OUI in silent mode

18.11.2014


11

oracle.install.crs.config.ClusterType=STANDARD

oracle.install.crs.config.clusterName=cl12

oracle.install.crs.config.gpnp.scanName=cl12.trivadis.com

oracle.install.crs.config.gpnp.scanPort=1521

oracle.install.crs.config.networkInterfaceList=eth0:192.168.122.0:1,

eth1:10.10.0.0:2

oracle.install.crs.config.storageOption=LOCAL_ASM_STORAGE

2014 © Trivadis

Standard Cluster with Standard ASM – Use Case

Small 2-nodes static database cluster

No plans (e.g Standard Edition) to extend the cluster

Less complexity (cluster resources) than other architectures

Less memory/CPU usage than other architectures

The local hard dependency between database instance and ASM

instance/disk groups is not that critical

18 November 2014


12

2014 © Trivadis

18 November 2014



13

2014 © Trivadis

Standard Cluster with Flex ASM – Big Picture

18 November 2014


14

Private Network

Public Network

Oracle ASM

ASM Disk Storage

…

ASM Network

DB

Instances crsd.bin

oraagent.bin

orarootagent.bin

OCR Writer

ASM Proxy

ASM

Listener

ADVM

ACFS

DB

Instances crsd.bin

oraagent.bin

orarootagent.bin

ASM Proxy

ASM

Listener

ADVM

ACFS

HU

B N

od

e

No

de #

1

HU

B N

od

e

No

de #

4

No ASM

Instance

+ASM

2014 © Trivadis

Standard Cluster with Flex ASM – Cluster Resource

A new architecture introduced with the 12.1 version

Storage must be accessible on all cluster nodes (HUB nodes)

ASM instance is now a cluster resource

The default cardinality is 3 – can be changed manually

Delivers metadata to all local and remote clients

ASM clients perform I/O directly to the disks

ASM password needs to be stored on the shared storage

All local clients connect using Oracle Bequeath NT Protocol

All remote clients connect using TCP/IP NT Protocol via ASM Listener

18 November 2014


15


ASM cluster : Flex mode enabled

srvctl config asm

...

ASM instance count: 3

Cluster ASM listener: ASMNET1LSNR_ASM

ASM ASM ASM

CLIENTS

2014 © Trivadis

Flex ASM – Older Client Versions

For older database versions the ASM instance must be available on all

nodes

18.11.2014


16

srvctl modify asm -count ALL

srvctl config asm

ASM home: <CRS home>

Password file: +GRID/orapwASM

ASM listener: LISTENER

ASM instance count: ALL

Cluster ASM listener: ASMNET1LSNR_ASM

2014 © Trivadis

Flex ASM – Remote Clients

All remote clients connect to ASM instances using

asm network

- Might be the same as the private network (in most cases sufficient)

+ASM service

- LISTENER_NETWORKS parameter modified automatically by oraagent

18 November 2014


17

Private Network

ASM Network

+ASM1 +ASM2 +ASM3

ASM

Listener

ASM

Listener

ASM

Listener ASM

Listener

LISTENER_NETWORKS

oifcfg getif

bond0 192.168.122.0 global public

bond1 10.10.0.0 global cluster_interconnect,asm

2014 © Trivadis

Flex ASM – Client Re-Connect

ASM uses connect-time load-balancing, not a run-time load-balancing!

Load-balancing might be triggered manually

The client might connect to the same Flex ASM instance again

A Flex ASM instance can be relocated to other cluster node

But not if used by the OCR Writer

As a workaround

Restart the OCR Writer ora.crsd resource: it will failover to other node

18 November 2014


18

SQL> alter system relocate client '-MGMTDB:_mgmtdb';

System altered.

srvctl relocate asm -currentnode clflexdb03 -targetnode clflexdb04

...

CRS-5027: The ASM instance on node "clflexdb03" cannot be stopped because

it is currently being used by Cluster Ready Services.

crsctl stop res ora.crsd –init ; crsctl start res ora.crsd -init

2014 © Trivadis

Flex ASM – ASM Proxy Instance

ADVM, ACFS communicate with ASM via

a new ASM Proxy instance (a local resource)

Started in NOMOUNT mode – can be a local or a remote Flex ASM client

In the 12.1.0.1 version +APX[n] instances are started on every HUB node

In the 12.1.0.2 version, only if necessary (part of the ADVM creation)

Crash of a local ASM Proxy instance will lead to a failure of all local file

systems based on ADVM

18 November 2014


19

srvctl status asm -proxy

ADVM proxy is running on node clflexdb04,clflexdb01,clflexdb03,clflexdb02

+ASM1

+APX1 +APX4

ASM

LSN

R

memory_target = 1076M

instance_type = ASMPROXY

cluster_database = FALSE (it is not a cluster, like ASM)

HUB Node

#1 HUB Node

#4

2014 © Trivadis

Flex ASM – Password File

Do not change the password for the

crsuser__asm_001 user or simply re-create

the password file

Credentials are stored in the password file as well

as cluster (OCR/OLR)

crsd.bin will start only on one node (OCR Writer node)

Incorporate the ASM password file into your GI backup/recovery concept

To query the automatically generated password

18 November 2014


20

1017 error=ORA-01017: invalid username/password; logon denied

OCR Writer

User: crsuser__asm_001

crsd.bin crsd.bin

OLR

ASM PW File

ASMCMD> pwcopy +GRID/orapwASM /home/grid/orapwASM

copying +GRID/orapwASM -> /home/grid/orapwASM

crsctl query credmaint -path ASM/Self

crsctl get credmaint -path <PATH_OUTPUT_COMMAND_ABOVE> \

> -credtype userpass -id 0 -attr passwd -local

2014 © Trivadis

Standard Cluster with Flex ASM – High Availability

Global hard dependency between Flex ASM and 12c clients

ASM Flex instance crash will not lead to a crash of its local/remote

clients

The clients will re-connect smoothly to a least-loaded available Flex ASM

instance

You can convert the architecture at a later time to


You cannot convert Flex ASM to Standard ASM (without cluster re-

configuration)

18 November 2014


21

NOTE: Flex client id 0x10001 [RAC2:RAC_SITE1] attempting to reconnect

NOTE: registered owner id 0x10001 for RAC2:RAC_SITE1 (reconnecting)

START_DEPENDENCIES=hard(global:uniform:ora.U01.dg) pullup(global:ora.U01.dg)

2014 © Trivadis

Standard Cluster with Flex ASM – Installation

OUI in GUI mode

OUI in silent mode

18.11.2014


22

oracle.install.crs.config.ClusterType=STANDARD

oracle.install.crs.config.clusterName=cl12

oracle.install.crs.config.gpnp.scanName=cl12.trivadis.com



eth1:10.10.0.0:5

oracle.install.crs.config.storageOption=FLEX_ASM_STORAGE

2014 © Trivadis

Standard Cluster with Flex ASM – Use Case

Most of the Oracle database cluster deployments

More flexibility/high availability with 12c clients

- Global cluster resource dependency between database instance and ASM

instance/disk groups

One shared network for ASM and cluster interconnect

Does it make sense to use Flex ASM for the “Small 2-nodes static

database cluster” category?

Q: how critical is the local hard dependency between database instance and

ASM instance/disk groups for you?

A: critical YES, non critical NO

18 November 2014


23

2014 © Trivadis

Standard Cluster with Flex ASM – DEMO

18 November 2014


24

2014 © Trivadis

18 November 2014



25

2014 © Trivadis

Flex Cluster with Flex ASM – Big Picture

18 November 2014


26

Private Network

Public Network

Oracle ASM

ASM Disk Storage

…

ASM Network

DB

Instances crsd.bin

oraagent.bin

orarootagent.bin

OCR Writer

ASM Proxy

ASM

Listener

ADVM

ACFS

crsd.bin


Listener

LEAF

Application 1 Application 2

VIP1

HU

B N

od

e

No

de #

1

LEA

F N

od

e

No

de #

10

0

No database instances

2014 © Trivadis

Flex Cluster with Flex ASM – HUB And LEAF Nodes

A new architecture introduced with the 12.1 version

Prerequisites: GNS (with or without zone delegation)

A Flex cluster uses two types of nodes

HUB nodes – shared storage must be accessible

LEAF nodes – shared storage is not necessary

HUB nodes

Like pre 12c cluster nodes, shared storage is required

Maximum 64 nodes per cluster (node IDs <1-99> reserved for HUB nodes)

18 November 2014


27

crsctl get cluster mode config

Cluster is configured as type "flex"

crsctl get node role status -all

Node 'clflexdb01' active role is 'hub'



Node 'clflexdb04' active role is 'leaf'

2014 © Trivadis

Flex Cluster with Flex ASM – HUBSIZE

The maximum amount of hub nodes in a cluster is limited

by the hubsize parameter

If the hubsize < #cluster_nodes

Oracle Clusterware will terminate on #(cluster_nodes – hubsize) nodes

The node type can be changed after the installation

Change from LEAF to HUB requires some preparation, though

18 November 2014


28

crsctl get cluster hubsize

CRS-4950: Current hubsize parameter value is 32

[OCSSD(14573)]CRS-1665: maximum number of cluster Hub nodes reached; the

CSS daemon is terminating

sudo crsctl set node role leaf

CRS-4408: Node 'clflexdb04' configured role successfully changed; restart

Oracle High Availability Services for new role to take effect.

2014 © Trivadis

Flex Cluster with Flex ASM – LEAF Nodes

LEAF nodes

No shared storage necessary

Connect to the cluster through the HUB nodes

Might be useful for some applications (cluster dependencies)

- Separate VIPs can be created (additional network required)

The first LEAF node has a node ID 100

Currently no Clusterware managed database instances

using ASM can be started on a leaf node

Seems not to be fully implemented yet

The node type can be changed after the installation

Change from LEAF to HUB requires some preparation, though

18 November 2014


29

srvctl status listener -l LISTENER_LEAF

Listener LISTENER_LEAF is enabled

Listener LISTENER_LEAF is not running

2014 © Trivadis

Flex Cluster with Flex ASM – High Availability

The same Flex ASM characteristics as for Standard Cluster with Flex

ASM applies also to this architecture

Example resource dependency between application and a database

service

You cannot convert the architecture at a later time to (without cluster re-

configuration)


Standard Cluster with Standard ASM

18 November 2014


30

START_DEPENDENCIES=hard(http.vip, global:ora.rac_site1.oltp.svc)

pullup:always(http.vip, global:ora.rac_site1.oltp.svc)

STOP_DEPENDENCIES=hard(http.vip, global:ora.rac_site1.oltp.svc)

2014 © Trivadis

Flex Cluster with Flex ASM – Installation

Prerequisites for a Flex Cluster

Grid Naming Service (GNS) configuration with one static VIP

- With or without zone delegation (see later)

Flex ASM is mandatory

OUI in GUI mode

18.11.2014


31

2014 © Trivadis

Flex Cluster with Flex ASM – Installation

OUI in silent mode

18.11.2014


32

oracle.install.crs.config.ClusterType=FLEX

oracle.install.crs.config.clusterName=cl121flex

oracle.install.crs.config.gpnp.scanName=cl121flex.cloud.trivadis.com


oracle.install.crs.config.gpnp.configureGNS=true

oracle.install.crs.config.autoConfigureClusterNodeVIP=true

oracle.install.crs.config.gpnp.gnsSubDomain=cloud.trivadis.com

oracle.install.crs.config.gpnp.gnsVIPAddress=192.168.122.28

oracle.install.crs.config.clusterNodes=clflexdb01.trivadis.com:AUTO:HUB,

clflexdb02.trivadis.com:AUTO:HUB,

clflexdb03.trivadis.com::LEAF


eth1:10.10.0.0:5

oracle.install.crs.config.storageOption=FLEX_ASM_STORAGE

2014 © Trivadis

Flex Cluster with Flex ASM – Use Case

Databases which are used together with applications within one cluster

and are dependent on each other

HUB nodes used by Oracle databases

LEAF nodes used by applications and its VIPs

(additional network resource, user-defined resources)

Cluster resource dependencies between application

and database

- Database instance start should trigger automatically

start of the application

- Shutdown of the last database instance should trigger beforehand

shutdown of the application

One shared network for ASM and cluster interconnect

At present no practical use case for a database cluster only

18 November 2014


33

APP DB DB

2014 © Trivadis

Flex Cluster with Flex ASM – DEMO

18 November 2014


34

2014 © Trivadis

18 November 2014


ASM Client Cluster

35

2014 © Trivadis

ASM Client Cluster – Remote Storage

ASM Client Cluster has been introduced with the patch set 12.1.0.2

Works starting with 12.1.0.2.1 (plus GI PSU Oct 2014)

Goal:

Provide shared storage for client clusters over ASM network

No shared storage / ASM resources on the client side

18 November 2014


36

ASM Cloud (Server) Cluster ASM Client Clusters

ASM Network

2014 © Trivadis

ASM Client Cluster – Installation

Prerequisites:

Server cluster using GNS (with or without zone delegation)

Version 12.1.0.2.1 (plus GI PSU Oct 2014) on the ASM server cluster

Export the ASM Client Cluster credential on the ASM Server Cluster

The credentials can be used only once!

ASM Client Cluster

Perform GI 12.1.0.2 Software Only installation

Apply GI PSU 12.1.0.2.1, than config.sh

18 November 2014


37

ASMCMD> mkcc cldbasm /home/grid/cldbasm.xml --version 12.1.0.2.0

2014 © Trivadis

ASM Client Cluster – Restrictions

The current version (12.1.0.2.1) allows using ASM Cloud (Server)

Cluster for

Voting files, OCR and password file

Might be useful for application clusters

Seems not to be fully implemented yet

As of now you cannot create a database (applies also to the MGMTDB)

18 November 2014


38

crsctl query css votedisk

1. ONLINE c2fe227b530d4 (+U01/CL121/VOTINGFILE/vfile.271.863285091) [U01]

Located 1 voting disk(s).

ORA-17502: ksfdcre:4 Failed to create file +U01

ORA-15001: diskgroup "U01" does not exist or is not mounted

ORA-15040: diskgroup is incomplete


Connected to an idle instance.

Client cluster

2014 © Trivadis

ASM Client Cluster – Use Case

Applications which need a cluster functionality on a hardware without

shared storage

ASM Cloud (Server) Cluster provides remote shared storage

ASM Server/Client Cluster uses the same ASM network

- Separate network for ASM and cluster interconnect recommended

User-defined application cluster resources

Other architecture, but at present the concept and use case is similar to

LEAF nodes with Flex Cluster

18 November 2014


39

2014 © Trivadis

Grid Naming Service (GNS) – Overview

GNS has been introduced with the 11.2.0.1 version

One zone delegation for each cluster

Naming resolution for SCAN and host VIPs

(DHCP)

18.11.2014


41

srvctl config gns

GNS VIP addresses: 192.168.122.28

Domain served by GNS: cloud.trivadis.com

<SCAN>.cloud.trivadis.com ?

<SERVER>-VIP. cloud.trivadis.com ?

triv

ad

is.c

om

DNS

DHCP

<SCAN> ?

<SERVER>-VIP ?

cloud.trivadis.com gnsd.bin:53

IP Address(es)

IP Address(es)

2014 © Trivadis

Grid Naming Service (GNS) – Overview

In the version 12.1.0.1 the concept

has been extended

GNS setup is also possible without zone

delegation

Host and SCAN VIPs configured in DNS

18 November 2014


42

srvctl config gns

GNS VIP addresses: 192.168.122.50

Domain served by GNS: N_FWD

2014 © Trivadis

Shared GNS – Server/Client Cluster

In the 11.2 version there is one GNS per cluster

In the 12.1 version, you can use one GNS Server Cluster which services

many GNS Client Clusters

A Flex Cluster cannot be used as a GNS Client Cluster

But a Flex Cluster can be a GNS Server Cluster

18 November 2014


43

cloud1.trivadis.com gnsd.bin:53 cloud2.trivadis.com gnsd.bin:53

cloud.trivadis.com gnsd.bin:53

Cluster 1

(GNS Client

Cluster)

GNS Server

Cluster

Cluster 2

(GNS Client

Cluster)

2014 © Trivadis

GNS Server/Client Cluster – Configuration

A Client Cluster needs the GNS client data configuration from the Server

Cluster

The GNS client data can be imported during the installation

Or afterwards

The GNS configuration at the client side

18 November 2014


44

sudo srvctl export gns -clientdata cl121_cluster.xml

sudo srvctl add gns -clientdata /home/grid/cl121_cluster.xml

srvctl config gns

Domain served by GNS: cl121.cloud.trivadis.com

Name of the cluster where GNS is running: cl121flex

GNS listening addresses: 192.168.122.28.

2014 © Trivadis

GNS Server/Client Cluster – Naming Conventions

The SCAN name in a Client Cluster uses

the following naming convention

Example

The host VIPs in a Client Cluster uses the following naming convention

Example

Note: GNS Server Cluster might be a SPOF!

18 November 2014


45

<scan>.<client_cluster_name>.<server_cluster_GNS_subdomain>

srvctl config scan

SCAN name: cl121.cl121.cloud.trivadis.com, Network: 1

Subnet IPv4: 192.168.122.0/255.255.255.0/eth0, dhcp

cldb01-vip.cl121.cloud.trivadis.com

<server>-vip.<client_cluster_name>.<server_cluster_GNS_subdomain>

Cluster 1

(GNS Client

Cluster)

2014 © Trivadis

Grid Naming Service (GNS) – Use Case

Oracle Flex and ASM Client Cluster

Use GNS without zone delegation – easier to manage, less complex

GNS with zone delegation

Limited to very dynamic clusters (many delete/add node procedures)

No practical use case for a typical database cluster

Shared GNS

Interesting for customers already using the GNS concept

- to reduce the amount of delegated domains

However, outage of the GNS Server Cluster will cause connectivity issues for

the whole Oracle Grid Infrastructure database environment

18 November 2014


46

2014 © Trivadis


In pre 12c versions the Cluster Health Monitor (CHM) data has been

stored on each cluster server in a Berkley database

<GRID_INFRA_HOME>/crf/db/<hostname>/

In the 12c version Oracle has introduced a new management database

Database name: _MGMTDB, instance name: -MGMTDB

Used for storing Cluster Health Monitor (CHM) and QoS data

Uses the same ASM disk group as for voting files and OCR

A new database and listener configured as failover resources

18 November 2014


48

srvctl status mgmtlsnr -verbose

Listener MGMTLSNR is enabled

Listener MGMTLSNR is running on node(s): clflexdb01

Detailed state on node clflexdb01: 169.254.31.252 10.10.0.25

srvctl status mgmtdb -verbose

Database is enabled

Instance -MGMTDB is running on node clflexdb01. Instance status: Open.

2014 © Trivadis


In the 12.1.0.1 release you could choose, whether to create the

management database or not

As a non-CDB

In the 12.1.0.2 release the database is mandatory

The database will be created as a single tenant CDB.

PDB name: <cluster_name>

The database is configured in NOARCHIVELOG mode

Backup is not necessary

To re-create or relocate to other ASM disk group: MOS Doc ID 1589394.1

18 November 2014


49

SQL> SHOW PDBS

CON_ID CON_NAME OPEN MODE RESTRICTED

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

2 PDB$SEED READ ONLY NO

3 CL121FLEX READ WRITE NO

2014 © Trivadis

Upgrade to the 12.1.0.2 Version

Make sure you have sufficient free space in the first disk group (hosting

Voting/OCR and ASM spfile)

If necessary replace the disks

If the length of the remote node name is longer than the local one

The cluster configuration/upgrade will fail during the start of CTSSD

Solution: Software Only installation PSU 12.1.0.2.1 config.sh

Starting with 12.1.0.2, the log files have been integrated into the ADR

18 November 2014


51

2014/09/10 15:20:21 CLSRSC-245: Failed to start Cluster Time

Synchronization Service (CTSS)Died at

/u00/app/grid/product/12.1.0.2/crs/install/crsupgrade.pm line 804.

<ORACLE_BASE>/diag/crs/<hostname>/crs/trace

2014 © Trivadis

Upgrade to the 12.1.0.2 Version – Unreachable Node

If a node becomes unreachable during an upgrade

Force the upgrade to finish (available also in pre 12c version)

Starting with 12.1 version you don’t need to delete and add the skipped

node – instead use

18 November 2014


52

/u00/app/grid/product/12.1.0.2/rootupgrade.sh –force

The CRS was successfully upgraded.

Forcibly upgraded the Oracle Clusterware.

Oracle Clusterware operating version was forcibly set to 12.1.0.2.0

/u00/app/grid/product/12.1.0.2/rootupgrade.sh -join -existingnode white

2014 © Trivadis

Downgrade To A Previous Version

On all remote nodes

On the last node

To avoid BUG 17780903 run the command from a directory that has write

permissions for GI installation use (grid)

At the end adopt the OUI inventory

18 November 2014


53

sudo /u00/app/grid/product/12.1.0.2/crs/install/rootcrs.pl –downgrade

...

Successfully downgraded Oracle Clusterware stack on this node

sudo /u00/app/grid/product/12.1.0.2/crs/install/rootcrs.pl -downgrade \

> –lastnode

...

Successfully downgraded Oracle Clusterware stack on this node

Run '/u00/app/grid/product/11.2.0.4/bin/crsctl start crs' on all nodes to

complete downgrade

2014 © Trivadis

Core Messages

In most cases, the Standard Cluster with Flex ASM

architecture is the best choice

Shared private/asm network sufficient for most deployments

Flex Cluster / ASM Client Cluster / GNS Server Cluster

At present the application area in an Oracle database

environment is somewhat limited

Some features not fully implemented yet

Installation/Upgrade

Prepare more space for the first ASM disk group (MGMTDB)

Apply the GI PSU Oct 2014

You cannot downgrade, after converting ASM to the Flex

architecture

18 November 2014


54

2014 © Trivadis

Questions and answers ...

2014 © Trivadis

BASEL BERN BRUGG LAUSANNE ZUERICH DUESSELDORF FRANKFURT A.M. FREIBURG I.BR. HAMBURG MUNICH STUTTGART VIENNA

Robert Bialek

Principal Consultant

Tel.: +49 89 99275930

[email protected]

18 November 2014


55

Oracle Failover Database Cluster with Grid Infrastructure ...

Documents

Transcript of Oracle Failover Database Cluster with Grid Infrastructure ...