Sponsored Content
Operating Systems Solaris How to configure my SAN with Sun V880 servers to run Oracle 9i Post 80924 by 98_1LE on Saturday 13th of August 2005 10:14:26 PM
Old 08-13-2005
The internal disks in a V880 are on an internal loop, and cannot participate in the SAN.

As for configuring the "SAN", that depends on the actual storage array, switches, & HBA's that you have. Generally speaking you will need to format the parity groups into LDEV's, run fiber, present LUN's to a port, configure LUN security, then configure the zones on the switch. Then assuming you are using Sun HBA's (QLogic) with the leadville drivers, you `cfgadm -c configure c# c#` the controllers, and put a VTOC on the disks.

You can use either Veritas Volume Manager and file system, or Veritas storage foundation for Oracle which also comes in an HA flavor (VCS). Veritas brings some flexibility, simplicity, and performance, but is expensive. Sun Disk Suite (SDS) and the ufs file system ship with Solaris.

If you are hardware RAID 10 on your array, I would use concatonated volumes. I usually put the ORACLE_BASE/HOME undert /app/oracle, and put the database under /u01 thru /u05, and use /u06 for archive logs. If I need a local slice for backups, I put it at /app/backups.

If using vxfs, make sure to use the largest block size that equals or is a multiple of your db/tablespace block size.

All of my V880's only have 6 internal 72GB disks. I usually use two for the OS mirrored with SDS, and the other four for rootdg with pre 4.0 vxvm. With 4.x, I make them a disk group, and would put your Oracle binaries and indexes on those disks, and the rest of the database on the SAN.

Realize that if you put disks on the SAN and the internal disks in the same disk group/set, you may have errors on boot or in single user because the drivers for the SAN HBA's have not loaded, and only part of the disk group will be visible.

Be sure to put noatime as a mount option in the vfstab, and if using ufs, also logging.
 

9 More Discussions You Might Find Interesting

1. UNIX Benchmarks

Sun V880 Solaris 9

notes: System Configuration: Sun Microsystems sun4u Sun Fire 880 System clock frequency: 150 MHz Memory size: 8192 Megabytes Run E$ CPU CPU Brd CPU MHz MB Impl. Mask --- --- ---- ---- ------- ---- A 0 750 8.0 US-III 5.4 B 1 ... (0 Replies)
Discussion started by: tnorth
0 Replies

2. Solaris

Sun v440/v880 network adapter teaming

Is it possible to team two network adapters for fault tolerance in a Sun v440 or v880 Solaris 8 box? If so how would I go about doing so? (1 Reply)
Discussion started by: ghuber
1 Replies

3. Solaris

Sun V880

I have two mechine, one is SUN V880 and another is IBM p570. I run the same script on V880 and p570 , why the cpu usage always under 50% on V880 but the cpu usage can growth to 100% on p570. (4 Replies)
Discussion started by: golden
4 Replies

4. Solaris

Thoughts/experiences of SAN attaching V880 to EMC SAN

Hi everyone, I wonder if I can canvas any opinions or thoughts (good or bad) on SAN attaching a SUN V880/490 to an EMC Clarion SAN? At the moment the 880 is using 12 internal FC-AL disks as a db server and seems to be doing a pretty good job. It is not I/O, CPU or Memory constrained and the... (2 Replies)
Discussion started by: si_linux
2 Replies

5. UNIX for Dummies Questions & Answers

unable to telnet from win xp to sun fire v880 server

Hi everybody i am trying to telnet to sun server from win xp machine but getting message "x21 error connection closed by remote user". i had make changes in /etc/default/login & /etc/fuser file still i have not getting telnet access. my win xp machines ip is 10.205.121.177 & sun server ip is... (1 Reply)
Discussion started by: pshelke
1 Replies

6. Solaris

configure solaris 10 mail to relay email alerts from SAN switch

I want to be able to use an account on a solaris 10 server, eg root@myhost to act as a relay to forward mail to my domain account me@mycompany.com The reason for this is to configure root@myhost as a mail relay on Brocade SAN switches - so that when a port goes bad i get an email alert.... (0 Replies)
Discussion started by: wibidee
0 Replies

7. Solaris

How configure SAN to server?

Hi all, I have a server with Solaris version 9. I wanted to mount SAN storage to my server. I am new at this. Can anyone give me an overview on how to this. Any documents will be fine also. Please let me know if any information is required. Thanks in advance. Below shows the HBA port: ... (11 Replies)
Discussion started by: beginningDBA
11 Replies

8. Hardware

Help needed for non-SUN-HDD (original Seagate) in V880

Hello, we have a hardware error on a 36GB HDD within a SunFire V880. Disk seems to be really dead, cause changing the slot of the disk, moves the error along. So we bought a similar, but original) Seagte-Disk (on ebay) and screwed it in the HDD-Cage. Disk is now known in format, but is... (5 Replies)
Discussion started by: etomer_sk
5 Replies

9. Solaris

Could you run this benchmark? (Especially if you have a V880 or V890)

Hi all I am currently using a T5120 to write and run some simulation code I've been working on which heavily relies on large matrix multiplication procedures. I am posting this to call out for some of you run and share the results of a simple benchmark I've written to compare the matrix... (1 Reply)
Discussion started by: toguro123
1 Replies
metaimport(1M)															    metaimport(1M)

NAME
metaimport - imports disk sets into existing Solaris Volume Manager configurations SYNOPSIS
metaimport -s setname [-n] [-v] [-f] [disks...] metaimport -r [disks...] metaimport -V metaimport -? The metaimport command allows the importing of disk sets, including replicated disk sets, into an existing Solaris Volume Manager configu- ration. Replicated disk sets are disk sets created using remote replication software. The default Solaris Volume Manager configuration specifies a maximum number of disk sets that can be configured. The metaimport command fails if importing the disk set would result in exceeding the number of disk sets configured on the system. To increase the number of disk sets allowed on a system, see the . Use metaset(1M) or metastat(1M) to view the configuration of the imported set. You must run metaimport as root. metaimport requires a functional Solaris Volume Manager configuration before it runs. The following options are supported: -f Force the import, even if a quorum of replicas from the imported disk set is not available. This option could result in corrupt configurations and should only be used when metaimport fails with the "Insufficient quorum detected; exiting" error. If only a partial disk set is available, this option might be necessary to successfully import. Some or all data could be corrupted or unavailable when importing a partial set or a set lacking a replica quorum. -n Does not actually perform the operation, but shows the output or errors that would have resulted from the opera- tion, had it been run. -r Report on the non-configured disk sets found on the system. If no disk device or LUN is specified, metaimport reports on all non-configured disk sets attached to the system. When the name of one disk is specified, metaimport reports on the disk set (or virtual LUN) containing the specified disk. If two or more disks are specified, metaim- port reports on the set (or sets, if they belong to different disk sets) containing the specified disks. If two or more disks are specified, metaimport reports on the set (or sets, if they belong to different disk sets) containing the specified disks. -s setname Specify the disk set name to use when importing. The imported disk set will be called setname, without regard to the name it may have had on a different system. -v Verbose. Provides detailed information about the metadb replica location and status. -V Version information. -? Display a help message. Example 1: Importing a Disk Set The following example creates a disk set called blue and identifies c1t5d0 as a disk containing a state database replica from the disk set being imported. # metaimport -s blue c1t5d0 Example 2: Reporting Disk Sets to Import The following example scans all disks and LUNs attached to the system and configured as part of the system. It scans for disks that could be part of a disk set to be imported. Components that are already part of the Solaris Volume Manager configuration are ignored. This use of metaimport provides suggested forms of the metaimport command to use to actually import the disk sets that have been found. You can specify a component on the command line to reduce the scope of the scan and generate results more quickly. # metaimport -r 0 Successful completion. >0 An error occurred. See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWmdu | +-----------------------------+-----------------------------+ |Interface Stability |Stable | +-----------------------------+-----------------------------+ mdmonitord(1M), metaclear(1M), metadb(1M), metadetach(1M), metahs(1M), metainit(1M), metaoffline(1M), metaonline(1M), metaparam(1M), metarecover(1M), metareplace(1M), metaroot(1M), metaset(1M), metasync(1M), metattach(1M), md.tab(4), md.cf(4), mddb.cf(4), attributes(5) 16 May 2005 metaimport(1M)
All times are GMT -4. The time now is 11:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy