Disk Storage Need to Add more Disk


 
Thread Tools Search this Thread
Operating Systems Solaris Disk Storage Need to Add more Disk
# 1  
Old 11-10-2010
Disk Storage Need to Add more Disk

Hi,

Anyone can help me, just want to confirm, if possible adding a disk storage that we have a RAWDATA with +ASM in our database. If possible, what would you recommend "workaround used" from us to do and the preparation. And also how long the downtime will take.

Our disk continuous to grow, need to add more disk storage in our "Sun StorageTek 3510 FC Array".

Storage having the following above;

Database : Oracle10g release 10.2.0.3
OS : SUN Solaris 10
Number of Nodes and Oracle SID Mapping : 2 instances "db01 and db02" using rawdata with +asm

Thanks in Advance;
FP

Last edited by DukeNuke2; 11-10-2010 at 07:02 AM..
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. Linux

Move OS to storage disk

Hi We have RHEL 7.3 running from local disk and we want to move it to storage. I am unable to find any proper procedure to do this activity. Please help. (4 Replies)
Discussion started by: powerAIX
4 Replies

2. Red Hat

storage disk details

Hi, We have a OEL5.7 installed and which has a storage attached on it. While running application it shows poor performance for Disk IO "dm-0" Now the question is how do I find what exactly is "dm-0" # iostat Linux 2.6.32-100.23.1.el5 03/10/2012 avg-cpu: %user %nice %system... (9 Replies)
Discussion started by: shrshah64
9 Replies

3. Shell Programming and Scripting

Age of file in storage / disk

Hello all, Below is scripts to find the file following by: 30 days <- How many total file space within 30 days and not quantity 90 days 120 days 1 year From here also I can get data space to put on PIE Chart. Following this scripts can I do some enhance from this scripts like do... (1 Reply)
Discussion started by: sheikh76
1 Replies

4. Solaris

A1000 Disk storage array

I am new to the unix world. I have SunBlade 100 and A1000 Disk storage array with 12 Hard drives. I used SCSI card and SCSI cables to connect. When I do the format command,I can see disk storage as one disk instead of 12 disks as below. Could anybody can explain why? What should I do in order... (1 Reply)
Discussion started by: Dulasi
1 Replies

5. Solaris

( VxVM ) How to add the removed disk back to previous disk group

Previously , i remove the disk by #vxdg -g testdg -k rmdisk testdg02 But i got error when i -k adddisk bash-2.03# vxdisk list DEVICE TYPE DISK GROUP STATUS c0t0d0s2 auto:none - - online invalid c0t1d0s2 auto:none ... (1 Reply)
Discussion started by: waibabe
1 Replies

6. Solaris

3511 storage disk not detected

I need help in this :confused: there was a disk failure in one logical drive, and there was a hot spare, once the disk failed i removed it and the hot spare took its place. now after I got a new disk, I added it in the place of the failed disk (slot #2), but the storage is not showing me any... (3 Replies)
Discussion started by: Sun Fire
3 Replies
Login or Register to Ask a Question
disksecn(1M)															      disksecn(1M)

NAME
disksecn - calculate default disk section sizes SYNOPSIS
block_size] [-n disk_name] DESCRIPTION
is used to calculate the disk section sizes based on the Berkeley disk partitioning method. recognizes the following options: Produce tables suitable for inclusion in the device driver. Produce tables suitable for generating the disk description file When generating the above tables, use a sector size of block_size bytes, where block_size can be or Defaults to DEV_BSIZE (defined in if not specified. Specifies the disk name to be used in calculating sector sizes; for example, or If an unknown disk name is specified, prompts the user for the necessary disk information. If neither nor table selection switches are specified a default table of the section sizes and range of cylinders used is output. Disk section sizes are based on the total amount of space on the disk as given in the table below (all values are supplied in units of 256-byte sectors). If the disk is smaller than approximately 44 Mbytes, aborts and returns the message Section 44-56MB 57-106MB 107-332MB 333+MB 0 97120 97120 97120 97120 1 39064 39064 143808 194240 3 39064 39064 78128 117192 4 unused 48560 110096 429704 6 7992 7992 7992 7992 10 unused unused unused 516096 Note It is important to note the difference between the block size passed into via the switch argument and the sector size the user is asked to input when an unknown disk name is passed to via the switch argument. The block size is the sector size that assumes the disk to have when it prints the requested tables. All information printed in the tables is adjusted to reflect this assumed sector size (block size) passed in by the user. The sector size requested by when an unknown disk name is passed does not necessarily have to be the same as the assumed sector size (block size) passed in by the switch argument. For example, a user wants to see the device driver tables for the disk named with an assumed sector size (block size) of 256 bytes. The user has the following information about the disk: Disk type = winchester Sector size = 512 Number of sectors per track (512 byte sectors) = 16 Number of tracks = 7 Number of cylinders = 968 Revolutions per minute = 3600 The user invokes by typing the following command: Assuming that is an unknown disk name, prompts the user for the necessary disk information. The user should input the information as shown above, reflecting a sector size of 512 bytes. All the information will be adjusted within to reflect the assumed sector size (block size) of 256 bytes, passed as the argument of the switch, before the requested device driver table is output. This adjustment also takes place when the disk name is known and an assumed sector size (block size) is passed in as the argument of the switch which is not DEV_BSIZE bytes, the assumed sector size (block size) used to create the file. RETURN VALUE
returns the following values: Successful completion. Usage error. User did not input parameters for an unknown disk. Disk too small or an invalid block size. aborts and prints an error message under the following conditions: o was invoked without specifying a disk name. o Requested both and switch. o Illegal block size requested. o Unknown disk name was specified and user did not supply disk information. o Disk's maximum storage space is less than approximately 44 MB. WARNINGS
Alternate names are not included in the output when the switch is used. Blanks are required in the command line between each of the switches when invoking A blank is required between the switch and the disk name argument to that switch. For example: does not save the block size used to generate the disk description file. The system assumes that the block size used was DEV_BSIZE when it reads the information stored in the file. AUTHOR
was developed by the University of California, Berkeley. FILES
SEE ALSO
disktab(4). Servers Only disksecn(1M)