04-18-2007
I highly recommend you get a SAN Engineer that knows what they are doing. I f you have SAN support with IBM *CALL THEM*. they are smart enough not to take you beyond what they are capable.
I believe they let you have one support call at purchase that they will let you keep open for 30 days.
If don't have support pay the T&M to IBM. Even if it costs a couple thousand it may be worth it.
This is not much, but a SAN Engineer upgraded our ESS sdd and host attachment scripts over a year ago. The pool of disks were at that time viewable by all of 4 AIX systems, but the disks weren't carved on all 4 systems. At any rate, the vpath #s did change after our upgrade. From what I understood they where expected to change. The LUN IDs are what is important. Be careful.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
There is a TSM server in which iam getting this error
Unable to read or write logical volume manager
record. PV may be permanently corrupted. Run diagnostics
how do i run the diagnostics??
any suggestions will really help.
Thanks!
karthik (1 Reply)
Discussion started by: karthikosu
1 Replies
2. UNIX for Advanced & Expert Users
Hi
We are running AIX5.3 on pseries 570. We have IBM ESS SAN stroage attached. We need to kick off flashcopy backups on the SAN. I have installed the CLI software but am missing a fileset. ibm2105esscli.rte or ibm2105cli.rte
This fileset contains the commands that can be issued from AIX to... (1 Reply)
Discussion started by: terrym
1 Replies
3. UNIX for Advanced & Expert Users
Hi all,
Sorry if this is in the wrong place but needed to make sure lots of people saw this so that hopefully someone will be able to help.
Basically i've upgraded a test server from 4.3 to 5.3 TL04.
The server has hdisk0 and 1 as rootvg locally but then has another vg setup on our ESS... (1 Reply)
Discussion started by: djdavies
1 Replies
4. AIX
Hi,
I have a strange problem. we're trying to connect an IBM pseries, to a Brocade switch, for SAN acess, using a badged emulex card, (IBM FC6239) WE can configure the device to see the fabric. The only problem we have is that the Brocade sees the HBA as storage, and not as a HBA.
We've zoned... (1 Reply)
Discussion started by: praxis22
1 Replies
5. AIX
Sorry for my english.
We have a IBM BLADES JS21. AIX 5.3 update to 6.
Our JS21 has 2 FC (fcs0 and fcs1).
We have one DS4072, one Disk system with 2 controllers and 2 FC by controllers.
This means, all AIX FC see all Disk systems controllers by 2 FC switchs. (one fc two roads)
FC AIX... (4 Replies)
Discussion started by: fjgonzalez
4 Replies
6. Shell Programming and Scripting
Hi,
when i am trying to FTP one file (test.txt) from Unix server to my local machine then i am getting the following error, as shown below
ftp> binary
200 Type set to I.
ftp> put C:\FTP\test.txt
C:FTPtest.txt: No such file or directory
ftp>
The red color text is the error.
Can... (3 Replies)
Discussion started by: sunitachoudhury
3 Replies
7. AIX
Hi folks.
We want to move a "physical" AIX box to a VIOed LPAR. The physical box is running SDD with disks from a DS8300. I want to be able to reattach those LUNs from the DS8300 to my VIO server which is running SDDPCM and then assigned them back to my AIX LPAR. Any thoughts about this?
I... (1 Reply)
Discussion started by: Stephan
1 Replies
8. AIX
I have sdd driver installed correctly but
when I run the command:
datapath query adapter
No device file found
what does it mean.. it is not using vpath or whats wrong? (2 Replies)
Discussion started by: Vit0_Corleone
2 Replies
9. AIX
Hi
What are the steps to be followed when upgrading MQ version from 6 to 7 in aix server?
cbsdbprd01 # oslevel -s
5300-10-01-0921
cbsdbprd01 # lslpp -l | grep -i mq
mqm.base.runtime 6.0.2.1 COMMITTED WebSphere MQ Runtime for
mqm.base.samples 6.0.2.1 ... (0 Replies)
Discussion started by: samsungsamsung
0 Replies
10. UNIX for Beginners Questions & Answers
What happens if we perform a Native AIX TL Upgrade on a VIO server? I mean instead of updateios I logged into oem_setup_env and ran a update_all to a new TL. (2 Replies)
Discussion started by: wibhore
2 Replies
LEARN ABOUT SUSE
ovdb_init
OVDB_INIT(8) InterNetNews Documentation OVDB_INIT(8)
NAME
ovdb_init - Prepare ovdb database for use
SYNOPSYS
ovdb_init ["-u"|"-r"]
DESCRIPTION
This command must be run before any other process can access the overview database. It performs the following steps:
1. Creates the database environment, if necessary
2. If the database is idle (and if the "-u" option is not specified), it performs a normal recovery. The recovery will remove stale
locks, recreate the memory pool cache, and repair any damage caused by a system crash or improper shutdown.
3. If the "-u" option is specified, it performs any necessary upgrades to the database. See the UPGRADING section below.
4. Starts the DB housekeeping processes (ovdb_monitor) if they're not already running. (Unless the "-r" option is specified).
5. Starts the ovdb readserver (ovdb_server) processes if readserver in ovdb.conf is true, and if they are not already running. (Unless
the "-r" option is specified).
Returns exit status of 0 if all steps were completed successfully. In the event of an error, messages are written to syslog and/or stderr.
If a recovery was attempted but it failed, the database may be damaged beyond repair, requiring a rebuild with makehistory(8).
This command is normally invoked automatically by rc.news(8).
It is OK to run this command multiple times.
OPTIONS
"-r"
Perform recovery only. "ovdb_monitor" is not started.
"-u"
Perform any needed upgrades. Recovery is not attempted. "ovdb_monitor" is started if the upgrade succeeded.
UPGRADING
There are two situations in which the database will need to be upgraded:
o You upgrade the Berkeley DB library to a newer version, for example from 2.7.7 to 3.1.17. In this case, the Berkeley DB db->upgrade()
method is used.
o You upgrade ovdb to a newer major version; i.e., ovdb-1.0 to ovdb-2.0.
In both of these cases, the database is upgraded in-place; and the upgrade can not be undone. Do not interrupt the upgrade process once it
has started, because there is a risk of irrepairable corruption. The upgrade may take several minutes to complete. If an upgrade does get
interrupted, try running the upgrade again.
Here's an example procedure to upgrade a database created with Berkeley DB 2.7.7 to use Berkeley DB 3.1.17:
1. Build and install the Berkeley DB 3.1.17;
2. Run configure in the INN source tree and make sure it picks up the right Berkeley DB directory (e.g., /usr/local/BerkeleyDB.3.1);
3. Do a "make";
4. Shut down INN (e.g., with "rc.news stop") and be sure to kill all instances of nnrpd as well;
5. Do a "make update" to install the new binaries;
6. Run "ovdb_init -u" as the news user;
7. Start INN with "rc.news".
It is OK to specify "-u" even if no upgrades are needed.
HISTORY
Written by Heath Kehoe <hakehoe@avalon.net> for InterNetNews.
$Id: ovdb_init.pod 7851 2008-05-26 19:33:08Z iulius $
SEE ALSO
ovdb(5), makehistory(8)
INN 2.5.2 2009-05-21 OVDB_INIT(8)