Shulou(Shulou.com)05/31 Report--

This article mainly explains "how to solve the problem that individual resources in Oracle RAC database can not be started automatically", interested friends may wish to have a look. The method introduced in this paper is simple, fast and practical. Let's let the editor take you to learn "how to solve the problem that individual resources in Oracle RAC database can't start automatically".

Recently I have dealt with several cases where individual resources cannot be started when RAC is restarted, such as instance, tns, and so on.

The resources are as follows:

NAME TARGET STATE SERVER STATE_DETAILS

Local Resources

Ora.CRS.dg

ONLINE ONLINE resdb1

ONLINE ONLINE resdb2

Ora.DATA.dg

ONLINE ONLINE resdb1

ONLINE ONLINE resdb2

Ora.LISTENER.lsnr

OFFLINE OFFLINE resdb1

OFFLINE OFFLINE resdb2

Ora.asm

ONLINE ONLINE resdb1 Started

ONLINE ONLINE resdb2 Started

Ora.gsd

OFFLINE OFFLINE resdb1

OFFLINE OFFLINE resdb2

Ora.net1.network

ONLINE ONLINE resdb1

ONLINE ONLINE resdb2

Ora.ons

ONLINE ONLINE resdb1

ONLINE ONLINE resdb2

Ora.registry.acfs

ONLINE ONLINE resdb1

ONLINE ONLINE resdb2

Cluster Resources

Ora.LISTENER_SCAN1.lsnr

1 ONLINE ONLINE resdb1

Ora.cvu

1 ONLINE ONLINE resdb2

Ora.oc4j

1 ONLINE ONLINE resdb1

Ora.resdb.db

1 OFFLINE OFFLINE resdb1

2 OFFLINE OFFLINE resdb2

As you can see from the above status information, the resdb1 and resdb2 instances of the resdb database and the listening TARGET and state values are both OFFLINE.

However, most of the primary DBA is basically sqlplus shut immediate when shutting down the database and listening, so the above problems will occur. (this will cause cluster to fail to manage resources properly)

View

The values for each resource property are as follows:

NAME=ora.LISTENER.lsnr

TYPE=ora.listener.type

ACL=owner:grid:rwx,pgrp:oinstall:rwx,other::r--

ACTION_FAILURE_TEMPLATE=

ACTION_SCRIPT=%CRS_HOME%/bin/racgwrap%CRS_SCRIPT_SUFFIX%

AGENT_FILENAME=%CRS_HOME%/bin/oraagent%CRS_EXE_SUFFIX%

ALIAS_NAME=ora.%CRS_CSS_NODENAME_LOWER_CASE%.LISTENER_%CRS_CSS_NODENAME_UPPER_CASE%.lsnr

AUTO_START=restore---- this property

CHECK_INTERVAL=60

CHECK_TIMEOUT=120

DEFAULT_TEMPLATE=PROPERTY (RESOURCE_CLASS=listener) PROPERTY (LISTENER_NAME=PARSE (% NAME%,., 2))

DEGREE=1

DESCRIPTION=Oracle Listener resource

ENABLED=1

ENDPOINTS=TCP:1521

LOAD=1

LOGGING_LEVEL=1

NAME=ora.resdb.db

TYPE=ora.database.type

ACL=owner:oracle:rwx,pgrp:oinstall:r--,other::r--,group:dba:r-x,group:oper:r-x,user:grid:r-x

ACTION_FAILURE_TEMPLATE=

ACTION_SCRIPT=

ACTIVE_PLACEMENT=1

AGENT_FILENAME=%CRS_HOME%/bin/oraagent%CRS_EXE_SUFFIX%

AUTO_START=restore---- this property

CARDINALITY=2

CHECK_INTERVAL=1

CHECK_TIMEOUT=30

CLUSTER_DATABASE=true

To avoid this problem, you can modify the following attributes: (root user)

. / crsctl modify resource "ora.LISTENER.lsnr"-attr "AUTO_START=always"

. / crsctl modify resource "ora.resdb.db"-attr "AUTO_START=always"

However, there are some differences between crs and 11G in 10G database.

The attributes of 10g are as follows:

$crs_stat-p

NAME=ora.dba.LISTENER_RACDB1.lsnr

TYPE=application

ACTION_SCRIPT=/oracle/oracle10g/bin/racgwrap

ACTIVE_PLACEMENT=0

AUTO_START=1

CHECK_INTERVAL=600

.

NAME=ora.dbb.LISTENER_RACDB2.lsnr

TYPE=application

ACTION_SCRIPT=/oracle/oracle10g/bin/racgwrap

ACTIVE_PLACEMENT=0

AUTO_START=1

CHECK_INTERVAL=600

DESCRIPTION=CRS application for listener on node

NAME=ora.RACDB.db

TYPE=application

ACTION_SCRIPT=/oracle/crs10g/bin/racgwrap

ACTIVE_PLACEMENT=0

AUTO_START=1

CHECK_INTERVAL=600

NAME=ora.RACDB.RACDB1.inst

TYPE=application

ACTION_SCRIPT=/oracle/oracle10g/bin/racgwrap

ACTIVE_PLACEMENT=0

AUTO_START=1

NAME=ora.RACDB.RACDB2.inst

TYPE=application

ACTION_SCRIPT=/oracle/oracle10g/bin/racgwrap

ACTIVE_PLACEMENT=0

AUTO_START=1

Attribute description:

AUTO_ start value

0, which means that it starts to the state before the resource restart

1, which means: start the resource

2, which means: do not start the resource

You can modify it with the following command

Crs_register resource_name-update-o as=2-(under root)

Generally speaking, when installing 11GR2 RAC, experienced dba will modify the resource properties.

Such as:

. / crsctl modify res ora.crf-attr AUTO_START=never

. / crsctl modify res ora.crf ENABLE=0-init

. / crsctl modify resource "ora.LISTENER.lsnr"-attr "AUTO_START=always"

. / crsctl modify resource "ora.racdb.db"-attr "AUTO_START=always"

At this point, I believe you have a deeper understanding of "how to solve the problem that individual resources in the Oracle RAC database cannot be started automatically". You might as well do it in practice. Here is the website, more related content can enter the relevant channels to inquire, follow us, continue to learn!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.