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
metadevadm(1M)                                            System Administration Commands                                            metadevadm(1M)

NAME
metadevadm - update metadevice information SYNOPSIS
/usr/sbin/metadevadm [-h] [-n] [ [-l]-r] [-s setname] [-u disk_specifier] [-v] DESCRIPTION
The metadevadm command facilitates the administration of device ID entries in Solaris Volume Manager. Use this command when the pathname stored in the metadevice state database no longer correctly addresses the device or when a disk drive has had its device ID changed. This command requires root privileges. OPTIONS
The following options are supported. -h Provide a help display. -l Specify that metadevadm log to syslog(3C). metadevadm logs to the the DAEMON facility at the ERR level by default. See syslog.conf(4) for additional information on changing logging levels. Use this option anytime. It is most useful in startup scripts and less useful interactively. -n Emulate the effect of a command, without making any changes to the system. -r Recompute the pathname and disk specifier (including slice) associated with all devices in the metadevice state database if the device supports device IDs. If a device does not support device IDs or the device is not available, then no action is taken for that device. Use this option when the disk has been moved or readdressed. This option is run automatically at boot time to detect device ID changes and update the state database. -s setname Specify the name of the disk set on which metadevadm works. This option causes the command to perform its adminis- trative function within the specified disk set. Without this option, the command performs its function on devices in the local disk set. -u disk_specifier Obtain the device ID associated with the disk_specifier (for example, c1t2d0) of a device and update the metadevice state database. If the device ID has not changed this option does nothing. Use this option when a disk drive has had its device ID changed during a firmware upgrade or due to changing the controller of a storage subsystem. -v Execute in verbose mode. This option has no effect when used with -u. Verbose is the default. EXAMPLES
Example 1: Updating Device ID of Disk The following example updates the device c2t3d0: # metadevadm -u c2t3d0 Updating SLVM device relocation information for c2t3d0. Old device reloc information: id19280192391293123012012010012012091398 New device reloc information: id19380192391293123012012010012012091398 The following example is a variation of the preceding, using the full pathname. # metadevadm -u /dev/dsk/c2t3d0 The following example uses the -n option, which means that the command is emulated, but does not take effect. Note that when the -v option is used with -u, -v has no effect (verbose is the default). # metadevadm -u -v -n c2t3d0 Updating SLVM device relocation information for c2t3d0. Old device reloc information: id19280192391293123012012010012012091398 New device reloc information: id19380192391293123012012010012012091398 Example 2: Recomputing Pathnames In the following example, all device names are valid. # metadevadm -r Disk movement detected. Updating device names in SLVM. In the following example, once again device names are valid. # metadevadm -r -v Disk movement detected. Updating device names in SLVM. c0t0d0s0 changed to c0t0d1s0 from device relocation information id12098123lkmklsdjaasdkfjadfjakds In the following example, metadevadm detects an invalid device name. # metadevadm -r Invalid device relocation information detected in SLVM. Please check status of following disk(s): c3t0d0 RETURN VALUES
The following exit values are returned: 0 Command was successful. 1 metadevadm encountered an error condition. 2 An invalid device ID was detected when using the -r option. This is for use in the rc2.d script. See init.d(4). ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ SEE ALSO
mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metarename(1M), metareplace(1M), metaroot(1M), metaset(1M), metassist(1M), metastat(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), md.tab(4), attributes(5), md(7D) Solaris Volume Manager Administration Guide SunOS 5.10 13 Sep 2004 metadevadm(1M)