ASM disks - expand a based San LUN

Similar Questions

• ASM disk - based SAN LUN expansion

  Hi all
  I'm learning a bit about the ASM and best practices to follow properly set up/use it at its best.
  
  Using an external FC SAN storage, if I create a logical volume with a LUN number and expose this LUN to my server ASM, I can see it properly and add it to an ASM disk group.
  
  So far so good. After that, if I develop this LUN on the external storage (using the tools), I'm not able to see the new space of the DSO. Looks like Oracle somehow "partitioned" originally the LUN when I first added it to the instance of the DSO, and after the "marking" it, even if I increase the Volume, the "expansion" is not seen.
  
  Is there a way to tell ASM as ther IS actually more space available? If I "fdisk-l", I see the amount of space on the device. But the 'blocks' are always the old value...
  
  I know that the creation of another logic unit number and adding to the disk group, there is no problem, but I would rather be able to expand an existing LUN on my external storage to create new LUNS on it all the time... Please help me understand if what I have in mind is correct or not on a best practices perspective.
  
  Thanks for any help.

  Yes you're right. Add the 20 GB lun, you can with 0 downtime and then remove the old 10GB of the diskgroup lun (assuming that you don't change the 10 GB to 20 GB :)) If you hold rebalance low power, Re-balance I/O will be even not worth the performance system IO too muchl.) But the problem here is that hesitate to use only a single lun 20 GB as the entire disk to ASM diskgroup. If you increase the number of LUNs (disks asm) even by creating separate volumes on the same physical disks you will increase the number of logical I/O paths which contributes to the homogeneity of distrubution of I/O.

  Kind regards
  Hüsnü
  http://husnusensoy.WordPress.com

• ASM backup with snapshots of SAN strategies

  Hello people,
  
  in one of our facilities, we have a database server (11.2) that has only the binaries and config (not the data files) and all the ASM disks residing on the San. The SAN has daily snapshots, so data files are saved. My question is, how should I proceed if the database server fails and needs to be reinstalled? My question is how can I tell the grid that we already have a diskgroup with disks on the SAN. I found md_backup and md_restore, but I don't know how and when do md_restore.
  I searched for a long time, but I'm quite confused with the approaches, please note that RMAN is not an option in this environment.
  
  
  Thanks in advance
  
  Alex

  Hello

  O.k., that changes things. You should have mentioned that in the beginning of your post, this stop the database you before you make the snapshot and you don't not to aid in archivelog mode.
  I would also suggest to disassemble start it before making snapshots.
  However, when was the last time you tried the archivelog mode? 11g has greatly increased performance.

  Note: in this case the snapshot is only a point of view. In case of error, you will lose data. (The last hours of your last backup).

  Now regarding your questions:

  -Online you will install a new system with the GI and the database software. You will need a new diskgroup (e.g. INFRA) to the new OCR and voting disks (they should not be included in other starts as DATA and FRA, so no don't need the old INFRA snapshot).
  => Then to present the DATABASE LUN and FRA diskgroup on the new server. ASM will be able to start it as soon as all the disks are available (and have the authorization of right). No need md_backup or restore. Backup MD_BACKUP the content of ASM headers, but since you have always drives this meta information is still intact.
  -Online record new data and services with the grid Infrastructure (srvctl add the database / srvctl add service etc.). Make sure you just point to the correct spfile (you can find for example with ASMCMD).
  => Database of departure...

  It's your snapshot was working. Only have another forum thread, where a diskgroup has been corrupted due to the snapshot (fortunately only FRA).

  And just as a reminder: a snapshot is not a backup. Depending on how the storage is the snapshot, you should take precautions to move to separate disks and check the TI (is it usable).

  Concerning
  Sebastian

• the ASM disks can be in a different Partition for a database

  Hi all
  I have 2 datababase on the server. I save the data file on MDMDISK1 for the MDM and DWHDISK1 database to the DWH database.
  I can add/dev/sdd5, / dev/sdd6, / dev/sdd7 to DWHDG1 disk group to give more space to the DWH database.
  
  Table of Partition disk configuration
  Group name size GB ASM Disk Disk drive
  / dev/SDS (MON) 107
  / dev/sdd1 7 CRSDISK1
  / dev/sdd2 7 CRSDISK2
  / dev/SDS3 7 CRSDISK3
  / dev/SDS4 8
  / dev/sdd5 24
  / dev/SDD6 24
  / dev/sdd7 24
  / dev/sde (MON) 107
  / dev/SDE1 24 MDMDISK1 + MDMDG1
  / dev/SDE2 24 MDMDISK2
  / dev/SDE3 24 MDMDISK3
  / dev/sde4 24 MDMDISK4
  / dev/sdf (MON) 107
  / dev/SDF1 24 DWHDISK1 + DWHDG1
  / dev/sdf2 24 DWHDISK2
  / dev/SDF3 24 DWHDISK3
  / dev/sdf4 24 DWHDISK4

  user5846399 wrote:

  but I wanted insurance with people with experience as you go this drive on differnet LUN will not impede performance.

  A LUN is a logical unit - it may be a single physical disk. It may consists of 20 physical drives. If the LUN itself does not determine the performance. Performance is determined by the parts in movement under it.

  Multiple LUNS to the same diskgroup using or the volume of file system is a common practice. If this would be a problem (performance or otherwise) depends on the cloth under the LUN.

  For example, a logic unit number could be RAID5 and another logic unit number can be RAID0 + 1. Mixture of different RAID levels is not really a good idea.

  A LUN can be a storage on a San and accessible via the fiber channel. Another logic unit number could be an iScsi device, accessed through intellectual property. Mix very different storage architecture and storage protocols are not a good idea.

  A LUN can be RAID0, through fiber double channels connected to a switch, for the storage of 1 storage server. Another logic unit number can also be RAID0 and accessible through the same fiber channels and switch, but since the storage server 2. Whereby the RAID levels are the same and the storage Protocol and infrastructure the same - and that will not only make a compatible mix, but can actually increases the redundancy if you use these as disk mirrors ASM (which means that ASM can lose the server storage 1 or 2 and still works).

• 2 san LUNS have been disassembled automatically need to pull up the same

  Dear Experts,

  last night all of a sudden we found two san LUNS are not mounted on one of the vcb server, but we are able to see the same on a disk management window, need your help how to mount these LUNS without losing any data. How to download buttons pressure or attachment...

  Need urgent help

  concerning

  Mr. VMware

  Hello

  What operating system is installed on the computer?

  Contact VMware support for assistance.

  http://www.VMware.com/support/

  Hope this information helps.

• os vs ASM disk size

  Hello

  When I compare the size of the operating system disks, each is 2.6 to.

  But when I look at ASM, they are 2 TB each.

  I'm reasonably sure, not 100%, I've created with external redundancy, so I thought the asm disks would be the same size as the operating system.

  fdisk -l
  data         /dev/sdb1      2627.4 GB        
  data2     /dev/sdg1        2627.4 GB        
  
  
  Name  REDUNDA MOUNT_S   TOTAL_MB    FREE_MB      OS_MB  
  ------------- ------- ---------- ---------- ---------- -
  DATA  UNKNOWN CACHED     2097144     842200    2097150  
  DATA  UNKNOWN CACHED     2097144     842392    2097150  
  

  Can someone explain this to me?

  Thank you

  Randy

  Version of grid Infrastructure?  ASM has limit GI version< 11.2="" on="" maximum="" size="" of="" luns="" (2tb)="" that="" can="" be="" used="" for="" asm="">

  https://jonathanlewis.WordPress.com/2009/08/14/Tera-bug/

• Difference between ADVM Volume and filesystem ACFS ASM disk group

  Q1. What is the difference between an ASM disk group and a Volume of ADVM?

  In my opinion, an ASM disk group is actually a logical volume to the database (including the FRA files) files.

  11 GR 2 appears to have introduced the notions of volumes ADVM and filesystems ACFS.

  11 GR 2 ASM disk group can contain:

  • ASM disks
  • Volumes ADVM
  • Filesystems ACFS

  Q2. ADVM volumes appear to be dynamic volumes.

  However is it therefore not effectively overlaying a logical volume (the volume ADVM) under ASM disk group (conceptually a logical volume as well)?

  Even worse, if you left the ASM disk group redundancy in hardware RAID / SAN level (as recommended Oracle), you actually have 3 layers of logical disk? (ASM on top of ADVM on top of RAID/SAN)?

  Q3. If it is 2 layers of logical disk (i.e. on top of ADVM ASM), what makes this better than 2 layers using a 3rd party volume manager (for example the DSO at the top of the 3rd party LVM) - something Oracle encourages against?

  Q4. ACFS file systems, seem to be file systems clustered for not including ORACLE_HOMEs database files, application exe etc (but NOT GRID_HOME, OS root, OCR or voting records)

  Can you create / modify filesystems ACFS using ASM.

  The diagram of topology of oracle for ASM in ASM 11 GR 2 administration guide, says ACF in ASM. I'm not sure about that if ACFS belongs to ASM or ASM is located at the top of the ACF?

  Q5. Connected to the 4th quarter. There seems to be a number of different ways, ACFS file systems can be created? Which of this is the valid methods?

  • Thanks to ASM?
  • through native OS file system creation?
  • through OEM?
  • through acfsutil?

  my head explodes

  Any help and clarification appreciated

  Jim

  
  

  Q1 - volume ADVM is a type of special file created at the DG of the DSO.  Once created, it creates a block device on the BONE itself which can be used as any other block device.  http://docs.Oracle.com/CD/E16655_01/server.121/e17612/asmfilesystem.htm#OSTMG30000

  Q2 - the asm disk group is a group of disks, not really a logical volume.  It combines the attributes of both when it is used for purposes of database as the database and some other applications know how to talk about Protocol 'ASM '.  However, you won't find all the versatile applications that can do.  In addition, some clients prefer to deal directly with files and devices of volume systems which ADVM is forced to make.  In your thinking, you have 3 layers of logical disk, but each of them provides features and different attributes.  This is not a bad thing, though, as each has a slightly different purpose - os file system\device, specific database and storage-centric.

  Q3 - ADVM is specifically developed to extend the features of the DSO for use by General applications of BONE.  It includes the performance of database features and is tuned to work well in this situation.  Because it is developed in-house, it benefits from the design of ASM model.  In addition, rather than having to communicate with several vendors for support, your support is limited to calling Oracle, a single window.

  Q4 - you can create and modify filesystems ACFS by using command line tools and the ASMCA.  Creation and modification of logical volumes coming through SQL (ASM), asmcmd and ASMCA.  EM can also be used for the two elements.  ACFS is located at the top of the ADVM, which is a file in an ASM disk group.  ACFS is aware of the characteristics of the ASM\ADVM volumes and tunes it's IO make best use of these features.

  Q5 - several ways:

  1) connect to ASM with SQL, use 'alter diskgroup add volume' as Mihael points out.  This creates an ADVM volume.  Then, put in shape volume using the "mkfs" (* nix) or acfsformat (windows).

  (2) use ASMCA - a GUI to create volume and a file system.  Probably the easiest if your head is explosion.

  (3) use "asmcmd" to create a volume and 'mkfs' to put in shape file ACFS system.

  Here is information on the ASMCA, with examples:

  http://docs.Oracle.com/CD/E16655_01/server.121/e17612/asmca_acfs.htm#OSTMG94348

  Information about the command line tools, with examples:

  Basic steps to manage systems Oracle ACFS

• need help to set up a SAN LUN...

  Dear team,

  Today, all of a sudden, we have identified two san LUNS are not mounted on one of the vcb server, but we are able to see the same on a disk management, here is the screenshot window, need your help how to make these existing LUNS without losing any data.

  

  LUNS that are not initialized these r the LUN I want to mount as drive Q and O, and here's event logs

  

  need urgent help

  concerning

  Mr. Vmware

  First, look at the status of logic on the side of SAN unit number.

  The windows machine

  1. make sure that you can see WWPN in the HBA bios.

  2. starting at OS level check LUN status using above commands so Multipathing s/w is installed, Else look for hard drives in the Device Manager (it must be something lik DISK IBM)

  3 simple reboot may go up Mon

• MSCS with a RDM SAN LUN

  I'm building a Microsoft Cluster with two VM on the physical host computers separate servers.  Based on what I have read so far using a RDM SAN LUN is supported when the cluster nodes are on separate host servers.  VMFS formatted SAN LUNS are not supported when the nodes are on separate host servers.

  If I have I need of several shared volumes, the only commune RDM LUN can cause several volumes in windows or each shared volume is associated with a RDM LUN?

  ESXi 5.0

  Windows Server Standard 2008 R2 x 64-cluster nodes

  Welcome to the community,

  usually, you would create a volume on a LUN (essentially identical with the physical installation of MSCS). Having multiple volumes on a single LUN would make not much sense anyway, because MSCS can not move LUN between nodes (i.e. only a single cluster node can be the owner/Defender).

  André

• Conversion of a server that has SAN LUNS attached

  Hello

  Need help.

  I need a file server, which currently has 4 mapped to the EVA SAN drives, each drive is almost 1.6 TB of P2V.

  I also have the CD VMware converter acronis.

  How can I get it work? as I'm not able to migrate the attached SAN LUN due to space issues.

  Any help appreciated...

  How can I get it work? as I'm not able to migrate the attached SAN LUN due to space issues.

  You don't need to convert the SAN disks, ignore those.  NPIV can be used to attach these LUNS later once it is converted.

  Use VM Converter, convert JUST the boot disk for the file server.

• SAN LUNS vs. VMFS Block Size block size

  Hi all

  I searched a bit and you read some documents on VMFS block sizes and alignment. However, I'm still a little confused. I think I get the concept of aligning vmfs partitions and how the block size affects max vmdk/size of the file on a partition. When creating new virtual disks and LUNS on my SAN, however, I can choose the sizes of different block there, as well.

  Choose size of block even when you create a SAN LUNS as VMFS partition that will reside on this subject? There is also 'the band height' and I wonder how it might affect things. The default value is 64 k, which I was using.

  Thank you very much

  Take a look at: disk partition alignment

  Block is not to same size, cause VMFS use big block (not available at the level of storage).

  André

• Migration of data to assist based SAN store

  Hey guys,.

  We have two esx servers. ESX1 and ESX2.

  ESX1 is autonomous, while ESX2 is with a SAN (connected to the HBA fibre channel)

  I am now loading on ESX1 vcenter, once this is done, I want to move the VM ESX1 the ESX2 server machine, BUT this time it should reside in the SAN logical unit number.

  I know that I can't move without interruption because they have not San already, so I'll have to cold migrate virtual machine to esx2 esx1 but is it the same as usage of vconverter? Also if I migrate can I ask vcenter to load the machine in the logical unit number of the san and not on the esx2 data store?

  Please help, I really need to get the VMs on the San and not having to build them from scratch once again.

  Thank you

  RJ

  We will all live a virtual life...

  OK

  The fact that you are directly connected to the San, and you can see the LUN in the section maps storage equates not once he is able to do something with this LUN.

  You must go to the STORAGE (should not be confused with storage adapters) and add it to your server AGAIN.

  When asked if the physical storage disk/LUN or connected to the network, you select disk physics/LUN. You will be presented a list of LUN storage adapters can see (including this LUN you're talking 200 GB)... Select it by clicking on it. Then, you will be asked to select the size of the block... I would recommend selecting 1 Mb. Then, you will be asked to give it a name (something like Datastore1_From_SAN works well) and then the server create a VMFS partition on it. Virtual machines LIVE in a VMFS partition - without one on this SAN LUNS, you will not be able to migrate your VM to it

  It will then appear in the tab for data warehouses (according to my pic) on the summary page of your server and appears in the page of DATA storages as well

  Hope this helps

• recommendation of the number of ASM disks on 11 GR 2

  Hi all
  
  I'm deployment RAC Oracle 11 g 2 + ASM AIX6.1 and an EMC SAN.
  
  I am planing to create three groups of disks DATA, FRA, and OCR, I use external redundancy.
  I have the questions:
  
  How many records you create for each group of records? is there any number of disks recommended for the DATA and FRA?
  FRA: This is for the flash recovery area disk group so all the backups will be stored here. should have the size of the DATA multiplied by 2?
  OCR: Will contain OCR and voting disks, is it enough not to have only a single drive since I'm on external redundancy? What is the recommendation?
  
  Kind regards

  Hello

  What is the right way to create my ASM disks? If I follow these steps, I should find the/dev / disks in my ASM_DISKS list? and then, of these discs, I can create my groups of disks?

  Yes... It is simpler than Linux (when you use MPIO or ASMLIB)... On AIX you just set the permission on/dev/rhdisk and asm_diskstring/dev/rhdis *, you need to create partition (LV) on these physical disks.

  These permissions are constantly, only returning to the default root: System in case of device to remove/add.

  You must use rhdisk hdisk.

  The special file rhdisk provides first IO functions to access and control to physical disk for the physical disk device drivers. Access IO gross is provided through the/dev/rhdisk0, / dev/rhdisk1,..., character special files.

  Direct access to physical disks through block special files should be avoided. This access may affect the performance and also cause problems of consistency of the data between the data and the data in the buffer cache pages system block I/O. Special files/dev/hdisk block are reserved for the system in the management of logical volumes, paging devices and file systems.

  Important: the physics of the disks MUST NOT have PVID. {: identifier of the thread = 2312281}

  # Added: edited by: Levi Pereira January 12, 2012 16:07
  Also, I recommend:
  DOC said: Oracle recommends that the allocation unit (to THE) size for a group of disks attached to 4 megabytes (MB).
  Definition of SIZE is a difference when you don't need broadband to e/s. IE: used for Diskgroup that will store the data files

  See the example:

  # lspv
  DISK            PVID                                VG_NAME
  ============================================================
  hdisk12         none                                None
  hdisk13         none                                None
  hdisk14         none                                None
  
  ## Change permission of /dev/rhdisk*  to GRID OS owner and ASMADMIN OS group and "chmod 660"
  ## If you are not using  job role separation installation the default is "oracle: dba"
  #  ls -ltr /dev/rh*
  crw-rw----    1 oracle   asmadmin     17, 10 Jan  5 17:01 /dev/rhdisk12
  crw-rw----    1 oracle   asmadmin     17, 11 Jan 12 15:00 /dev/rhdisk13
  crw-rw----    1 oracle   asmadmin     17, 12 Jan 12 15:16 /dev/rhdisk14
  
  Disks to discover [disks=raw,asm,all]
  raw = disks not used by ASM
  asm = disks used by ASM
  all = All disks
  
  $ /u01/app/grid/grid_has/kfod disks=raw asm_diskstring='/dev/rhdisk*'
  --------------------------------------------------------------------------------
   Disk          Size Path                                     User     Group
  ================================================================================
     1:     204800 Mb /dev/rhdisk12                             oracle   asmadmin
     2:     204800 Mb /dev/rhdisk13                             oracle   asmadmin
     3:     204800 Mb /dev/rhdisk14                             oracle   asmadmin
  --------------------------------------------------------------------------------
  ORACLE_SID ORACLE_HOME
  ================================================================================
        +ASM /u01/app/grid/grid_has
  
  SQL>
  set linesize 100
  col path for a30
  col header_status for a20
  select path,header_status from v$asm_disk
  where header_status <> 'MEMBER';
  PATH                           HEADER_STATUS
  ------------------------------ --------------------
  /dev/rhdisk12                   FORMER
  /dev/rhdisk13                   FORMER
  /dev/rhdisk14                   FORMER
  
  $ sqlplus / as sysasm
  
  SQL>
   CREATE DISKGROUP DATA NORMAL REDUNDANCY
      FAILGROUP STG1_CTL1 DISK '/dev/rhdisk12'
      FAILGROUP STG2_CTL1 DISK '/dev/rhdisk13'
      FAILGROUP STG1_CTL2 DISK '/dev/rhdisk14'
   ATTRIBUTE 'compatible.asm' = '11.2.0.0.0';
  
  Diskgroup created.
  
  $ asmcmd lsdg DATA
  
  Inst_ID  State    Type    Rebal  Sector  Block       AU  Total_MB  Free_MB  Req_mir_free_MB  Usable_file_MB  Offline_disks  Voting_files  Name
        1  MOUNTED  NORMAL  N         512   4096  1048576    614400   614238           204800          204719              0             N  DATA/
  
  $  asmcmd  lsdsk -p -G DATA
  Group_Num  Disk_Num     Incarn  Mount_Stat  Header_Stat  Mode_Stat  State   Path
          5         0  782499361  CACHED      MEMBER       ONLINE     NORMAL  /dev/rhdisk12
          5         1  782499362  CACHED      MEMBER       ONLINE     NORMAL  /dev/rhdisk13
          5         2  782499363  CACHED      MEMBER       ONLINE     NORMAL  /dev/rhdisk14
  
  $  asmcmd lsdsk -k -G DATA
  Total_MB  Free_MB   OS_MB  Name       Failgroup  Failgroup_Type  Library  Label  UDID  Product  Redund   Path
    204800   204746  204800  DATA_0000  STG1_CTL1  REGULAR         System                         UNKNOWN  /dev/rhdisk12
    204800   204746  204800  DATA_0001  STG2_CTL1  REGULAR         System                         UNKNOWN  /dev/rhdisk13
    204800   204746  204800  DATA_0002  STG1_CTL2  REGULAR         System                         UNKNOWN  /dev/rhdisk14
  

  Kind regards
  Levi Pereira

  Published by: Levi Pereira January 12, 2012 15:50

• Move the ASM disks

  Windows 2008 R2 64-bit server running Oracle Enterprise Database 11.2.0.2
  
  This server was supposed to be an isolated system, which can be moved to another location...
  the person who took leave, and now they want to move...
  
  I started to go into the config and discovered that it didn't load basic disks to ASM data on local hard drives that were bought for her. they were loaded in our SAN storage...
  I need to move the disks local ASM of our SAN to hard drives...
  
  NOTE: The space used is small... but more than the local disk space is space on the SAN... If the size of the readers will have to be reduced...
  
  I probably just format and will load another server and export/import data...
  But I was currious if there was a way to move a disk partition ASM disks to another...

  Please check:
  Passing a datacenter ASM disks to the other for the other machine

• How card ASM disk path to the physical drive on AIX?

  Hello world
  I work on a plug-in for Oracle Enterprise Manager 10 g 2 on AIX 5.3 which monitors storage bays and supports databases in addition to the "emrep" database ASM One of the metrics of this plug-in is populated by the result of a korn shell script. Directly, the script runs on the AIX host (connected to the storage array cable CF via HBA ports) and retrieves the mapping for - disk - logical disk - LUN - ASM.
  
  Now, I was able to get the mapping to physical disk - logical disk - LUN, but could not map drive ASM. I googled a lot for no idea, but did not find the answer to this specific problem.
  
  Now, I have the list of physical disks used for the DSO by the command:
  
  LSPV
  
  hdisk0 0001c22ac8d664ca rootvg active
  hdisk1 0001c22aa51f496a Oracle active
  hdisk2 0001c22ac478263a zero active
  hdisk3 0001c22ac472549a Oracle active
  hdisk4 0001c22ac4725d6a Oracle active
  hdisk5 none None
  hdisk6 none None
  hdisk7 none None
  hdisk8 none None
  hdisk9 none None
  hdisk10 none None
  hdisk11 none None
  hdisk12 none None
  hdisk13 none None
  hdisk14 none None
  hdisk15 none None
  hdisk16 none None
  
  Hdisk5-16 discs are ASM disks and there are currently of no PVID.
  
  I also have the list of ASM disks by the command:
  
  ls-l/dev | grep oracle
  
  CRW - rw - 1 oracle dba 22, 6 12 may 00:02 asm_rd10_1a
  CRW - rw - 1 oracle dba 22, 10 Apr 21 07:27 asm_rd10_1b
  CRW - rw - 1 oracle dba 22, 7 May 09 13:53 asm_rd10_1c
  CRW - rw - 1 oracle dba 22, 8 May 09 13:53 asm_rd5_1a
  CRW - rw - 1 oracle dba 22, 4 12 may 00:02 asm_rd5_1b
  CRW - rw - 1 oracle dba 22, 9 APR 21 07:28 asm_rd5_1c
  CRW - rw - 1 oracle dba 22, 12 12 may 00:02 asm_xbb2_rd10_1a
  CRW - rw - 1 oracle dba 22: 11 Apr 24 07:34 asm_xbb2_rd10_1b
  CRW - rw - 1 oracle dba 22, 13 May 09 13:53 asm_xbb2_rd10_1c
  CRW - rw - 1 oracle dba 22, 16 12 may 00:02 asm_xbb2_rd5_1a
  CRW - rw - 1 oracle dba 22, 14 Apr 24 07:34 asm_xbb2_rd5_1b
  CRW - rw - 1 oracle dba 22, 15 May 09 13:54 asm_xbb2_rd5_1c
  
  Now, I'm looking for a way to map these two lists with each other and had no luck so far.
  Oracle provides this information somewhere in the OEM installation structure or y at - it a command in AIX that could provide a way to map the ASM disks on the physical disks?
  
  Any help on this is greatly appreciated. Thanks in advance...
  
  
  FYI: ASMLib driver is not present on the system.

  I am not familiar with aix, but I think you can get the major and minor numbers as follows:

  ls-l/dev/asm_rd_10_1a
  CRW - rw - 1 oracle dba 22, 6 12 may 00:02 asm_rd10_1a
  ls-l/dev/hdisk5
  CRW - rw - 1 root root 22, 6 12 may 00:02 hdisk5

  the numbers would be 22 and 6.

  That's just a guess, on HP - UX, it's like that, but it will be a little tricky