How to register diskgroup to a cluster

Source: Internet
Author: User
Previously, renamedg was used for ora. CRS. dg rename ora. DUPCRS. however, the disadvantage of the renamedg is that it cannot synchronize the modified information to the whole cluster level, and the dg before the modification will still be stored at the cluster level: as shown below: Therefore, You need to manually clear it, and re-register the modified dg Information. Rename requirement: ora. CRS. dg

Previously, renamedg was used for ora. CRS. dg rename ora. DUPCRS. however, the disadvantage of the renamedg is that it cannot synchronize the modified information to the whole cluster level, and the dg before the modification will still be stored at the cluster level: as shown below: Therefore, You need to manually clear it, and re-register the modified dg Information. Rename requirement: ora. CRS. dg

Previously, renamedg was used to rename ora. CRS. dg. ora. DUPCRS. dg
However, renamedg cannot synchronize the modified information to the whole cluster level, and the dg before the modification will remain at the cluster level:
As shown below: You need to manually clear and re-register the modified dg Information.

Rename
Requirement: ora. CRS. dg -------------- ora. DUPCRS. dg
Register ora. DUPCRS. dg into cluster

Grid: 11203

Db: 11202
[Grid @ vmrac1 ~] $ Crsctl stat res-t
--------------------------------------------------------------------------------
Name target state server STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
Ora. ARCH. dg
ONLINE vmrac1
ONLINE vmrac2
Ora. CRS. dg
Online unknown vmrac1
Online offline vmrac2
Ora. DATANEW. dg
ONLINE vmrac1
ONLINE vmrac2
Ora. DUPCRS. dg
Online offline vmrac1
Online unknown vmrac2

Test 1]
-------- The configuration information of ora. DUPCRS. dg-type ora. diskgroup. type after crsctl add res ora. DUPCRS. dg is registered:
-------- Cluster resource status information is as follows:

[Grid @ vmrac1 ~] $ Crsctl stat res-t
--------------------------------------------------------------------------------
Name target state server STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
Ora. ARCH. dg
ONLINE vmrac1
ONLINE vmrac2
Ora. CRS. dg
Online unknown vmrac1
Online offline vmrac2
Ora. DATANEW. dg
ONLINE vmrac1
ONLINE vmrac2
Ora. DUPCRS. dg
Online offline vmrac1
Online unknown vmrac2
Ora. FLASH. dg
ONLINE vmrac1
ONLINE vmrac2


----- The configuration result is obviously incorrect.

[Grid @ vmrac1 ~] $ Crsctl stat res ora. DUPCRS. dg-p
NAME = ora. DUPCRS. dg
TYPE = ora. diskgroup. type
ACL = owner: grid: rwx, pgrp: oinstall: rwx, other: r --
ACTION_FAILURE_TEMPLATE =
ACTION_SCRIPT =
AGENT_FILENAME = % CRS_HOME %/bin/oraagent % CRS_EXE_SUFFIX %
ALIAS_NAME =
AUTO_START = never --------------- there is a problem
Check_integer = 300
CHECK_TIMEOUT = 30
DEFAULT_TEMPLATE =
DEGREE = 1
DESCRIPTION = CRS resource type definition for ASM disk group resource
ENABLED = 1
LOAD = 1
LOGGING_LEVEL = 1
NLS_LANG =
NOT_RESTARTING_TEMPLATE =
OFFLINE_CHECK_INTERVAL = 0
PROFILE_CHANGE_TEMPLATE =
RESTART_ATTEMPTS = 5
SCRIPT_TIMEOUT = 60
START_DEPENDENCIES = hard (ora. asm) pullup (ora. asm)
START_TIMEOUT = 900
STATE_CHANGE_TEMPLATE =
STOP_DEPENDENCIES = hard (intermediate: ora. asm)
STOP_TIMEOUT = 180
TYPE_VERSION = 1.2
UPTIME_THRESHOLD = 1d
USR_ORA_ENV =
USR_ORA_OPI = false
USR_ORA_STOP_MODE =
VERSION = ------------- the problem also exists here, but I don't think this parameter is very important.

Test 2]

------ Delete DUPCRS dg:
[Grid @ vmrac1 ~] $ Crsctl delete res ora. DUPCRS. dg

------ Register resource ora. DUPCRS. dg
[Grid @ vmrac1 ~] $ Crsctl add res ora. DUPCRS. dg-type ora. diskgroup. type-attr

"ACL = 'owner: grid: rwx, pgrp: oinstall: rwx, other: r -- ', AUTO_START = always, VERSION = 11.2.0.2.0"-I

----- View the configuration information of ora. DUPCRS. dg:
[Grid @ vmrac1 ~] $ Crsctl stat res ora. DUPCRS. dg-p
NAME = ora. DUPCRS. dg
TYPE = ora. diskgroup. type
ACL = owner: grid: rwx, pgrp: oinstall: rwx, other: r --
ACTION_FAILURE_TEMPLATE =
ACTION_SCRIPT =
AGENT_FILENAME = % CRS_HOME %/bin/oraagent % CRS_EXE_SUFFIX %
ALIAS_NAME =
AUTO_START = always
Check_integer = 300
CHECK_TIMEOUT = 30
DEFAULT_TEMPLATE =
DEGREE = 1
DESCRIPTION = CRS resource type definition for ASM disk group resource
ENABLED = 1
LOAD = 1
LOGGING_LEVEL = 1
NLS_LANG =
NOT_RESTARTING_TEMPLATE =
OFFLINE_CHECK_INTERVAL = 0
PROFILE_CHANGE_TEMPLATE =
RESTART_ATTEMPTS = 5
SCRIPT_TIMEOUT = 60
START_DEPENDENCIES = hard (ora. asm) pullup (ora. asm)
START_TIMEOUT = 900
STATE_CHANGE_TEMPLATE =
STOP_DEPENDENCIES = hard (intermediate: ora. asm)
STOP_TIMEOUT = 180
TYPE_VERSION = 1.2
UPTIME_THRESHOLD = 1d
USR_ORA_ENV =
USR_ORA_OPI = false
USR_ORA_STOP_MODE =
VERSION = 11.2.0.2.0

---------- View the status of ora. DUPCRS. dg in the cluster again:
[Grid @ vmrac1 ~] $ Crsctl stat res-t
--------------------------------------------------------------------------------
Name target state server STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
Ora. ARCH. dg
ONLINE vmrac1
ONLINE vmrac2
Ora. CRS. dg
Online unknown vmrac1
Online offline vmrac2
Ora. DATANEW. dg
ONLINE vmrac1
ONLINE vmrac2
Ora. DUPCRS. dg
OFFLINE vmrac1
OFFLINE vmrac2
Ora. FLASH. dg
ONLINE vmrac1
ONLINE vmrac2

------------ Restart the resource ora. DUPCRS. dg:
[Grid @ vmrac1 ~] $ Crsctl start res ora. DUPCRS. dg
CRS-2672: Attempting to start 'ora. DUPCRS. dg 'on 'vmrac2'
CRS-2672: Attempting to start 'ora. DUPCRS. dg 'on 'vmrac1'
CRS-2676: Start of 'ora. DUPCRS. dg 'on 'vmrac1' succeeded
CRS-2676: Start of 'ora. DUPCRS. dg 'on 'vmrac2' succeeded


----------- Confirm the status of dg again:
[Grid @ vmrac1 ~] $ Crsctl stat res-t
--------------------------------------------------------------------------------
Name target state server STATE_DETAILS
--------------------------------------------------------------------------------
Local Resources
--------------------------------------------------------------------------------
Ora. ARCH. dg
ONLINE vmrac1
ONLINE vmrac2
Ora. CRS. dg
Online unknown vmrac1
Online offline vmrac2
Ora. DATANEW. dg
ONLINE vmrac1
ONLINE vmrac2
Ora. DUPCRS. dg
ONLINE vmrac1 --------- the status is correct
ONLINE vmrac2
Ora. FLASH. dg
ONLINE vmrac1
ONLINE vmrac2

[Grid @ vmrac1 ~] $

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.