In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-02-24 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >
Share
Shulou(Shulou.com)06/01 Report--
The error of Oracle ASM-- ORA-15033
System environment:
Operating system: AIX 5.3.8
Oracle: Oracle 10gR2
Failure phenomenon:
SQL > create diskgroup datafile 2 normal redundancy failgroup fg1 disk'/ dev/rlv_data1' 3 4 failgroup fg2 disk'/ dev/rlv_data2';create diskgroup datafile*ERROR at line 1:ORA-15018: diskgroup cannot be createdORA-15033: disk'/ dev/rlv_data2' belongs to diskgroup "RECOVER" ORA-15033: disk'/ dev/rlv_data1' belongs to diskgroup "DATA" SQL > select group_number,name,state from v$asm_diskgroup GROUP_NUMBER NAME STATE--0 REDO DISMOUNTED 0 ARCH DISMOUNTED 0 DATA DISMOUNTED 0 RECOVER DISMOUNTED
Cause of failure:
[oracle@aix213 dbs] $lsvg-l asmvgasmvg:LV NAME TYPE LPs PPs PVs LV STATE MOUNT POINTlv_data1 jfs 64 64 1 open/syncd N/Alv_data2 jfs 64 64 1 open/syncd N/Aasmredo2 jfs 32 32 1 open/syncd oracle@aix213 dbs A [oracle@aix213 dbs] $lspv hdisk1 00c6d0ef0395eef2 rootvg activehdisk0 0006816a72287441 asmvg active
It should be in AIX's ODM, rlv_data1 and rlv_data2, which already belong to another disk group.
Solution:
1) Clean up raw header information
[root@aix213 /] # dd if=/dev/zero of=/dev/rlv_data1 bs=8k count=256256+0 records in256+0 records out [root@aix213 /] # dd if=/dev/zero of=/dev/rlv_data2 bs=8k count=256256+0 records in256+0 records out
2) re-establish ASM DISKGROUP
[oracle@aix213 dbs] $sqlplus / as sysdbaSQL*Plus: Release 10.2.0.1.0-Production on Thu Jul 24 11:44:29 2014Copyright (c) 1982, 2005, Oracle. All rights reserved.Connected to:Oracle Database 10g Enterprise Edition Release 10.2.0.1.0-64bit ProductionWith the Partitioning, OLAP and Data Mining optionsSQL > select name, state from v$asm_diskgroup Data and recover diskgroup are automatically deleted after NAME STATE---REDO DISMOUNTEDARCH DISMOUNTED cleans the raw header information! SQL > create diskgroup datafile 2 normal redundancy 3 failgroup fg1 disk'/ dev/rlv_data1' 4 failgroup fg2 disk'/ dev/rlv_data2';Diskgroup created. Disk group created successfully!
3) Verification
SQL > select name, state from vandalism diskgroupterNAME STATE---REDO DISMOUNTEDARCH DISMOUNTEDDATAFILE MOUNTEDSQL > alter diskgroup redo mount;Diskgroup altered.SQL > alter diskgroup arch mount Diskgroup altered.SQL > select name, state from vicious asmosis diskgroupterName STATE---REDO MOUNTEDARCH MOUNTEDDATAFILE MOUNTED
@ at this point, the problem is solved!
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.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.