How To determinate if an emcpower partition is valid for asmlib

 

 

If you are trying to create an asmlib disk using an emcpower # partition and you get the next error:

ASM Disk: asmtool: Device "/dev/emcpowera11" is not a partition [failed]

 

Then you will need to determinate if the emcpower # partition is valid.

 

 

The solution is as follows:

In order to confirm the emcpower # partition is valid:

1) Check if you can create a tablespace directly on the block partition:

 

[Root @ dbaasm ~] # Cd/dev
[Root @ dbaasm Dev] # ls-l emcpowerd1
BRW-RW ---- 1 root disk 3, 19 APR 29 16:00 emcpowerd1
[Root @ dbaasm Dev] # chmod 777 emcpowerd1
[Root @ dbaasm Dev] # ls-l emcpowerd1
Brwxrwxrwx 1 root disk 3, 19 APR 29 16:00 emcpowerd1
[Root @ dbaasm Dev] # exit

 

Dbaasm.us.oracle.com:/u01/APP/Oracle/11.1/DB: Test: Oracle> sqlplus "/
Sysdba"

SQL * Plus: Release 11.1.0.6.0-production on Thu May 1 09:09:02 2008

Copyright (c) 1982,200 7, Oracle. All rights reserved.

Connected:
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0-Production
With the partitioning, OLAP, data mining and real application testing options

SQL> Create tablespace test datafile '/dev/emcpowerd1' size 100 m;

Tablespace created.

 

2) if so, then drop the previous tablespace.

 

3) then check if a diskgroup can be created directly on the block partition:

Connect as root and execute:

# Dd If =/dev/Zero of = '/dev/emcpowerb1' BS = 8192 COUNT = 12800

Then connect as Oracle, and then connect to the ASM instances and execute:

SQL> alter system set asm_diskstring = '/dev/emcpowerb1' scope = memory;

SQL> Create diskgroup test external redundancy disk '/dev/emcpowerb1 ';
Diskgroup created.

 

4) if the tablespace and diskgroup can be create directly on the block partition then this cocould be a problem with asmlib configuration. Therefore you will need to check if the correct asmlib RPMs were installed.

5) Alternatively, you can check if the problem is reproducible on another emcpower # partition or ask the SA to recreate the original one.

 

 

 

 

From Oracle

Bytes -------------------------------------------------------------------------------------------------------

Blog: http://blog.csdn.net/tianlesoftware

Email: dvd.dba@gmail.com

Dba1 group: 62697716 (full); dba2 group: 62697977 (full) dba3 group: 62697850 (full)

Super DBA group: 63306533 (full); dba4 group: 83829929 dba5 group: 142216823

Chat group: 40132017 chat 2 group: 69087192

-- Add the group to describe the relationship between Oracle tablespace and data files in the remarks section. Otherwise, the application is rejected.