James and Gareth have both given excellent advice but I would like to add some
user experience. When we were running NV 5.1 and 5.1.1, our same file,
/usr/OV/openview/ovwdb/vurrent/value_info, would grow from a size of 30-40 meg
to 1-2 gig over a couple of days. We had to compress the database weekly.
This problem went away when we applied the 5.1.2 service. Applying the 5.1.3
service would be a good idea.
Just my 2 cents.
Dean Grant
Ahold Information Services
Gareth_Holl@TIVOLI.COM on 07/03/2000 04:39:04 PM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: IBM NetView Discussion <nv-l@tkg.com>
cc: (bcc: Dean Grant/AIS/US/Ahold)
Subject: Re: [NV-L] Database connection lost
A small correction to James' reply, the ovtopofix option -a should generally
should be used when you have multiple maps that contain different objects and
the -A option for when you only have one map - this is opposite to how it is
written in James' previous reply.
Other than that, I would agree with James in that running the ovwdbdmap command
on a database that has been converted to the NDBM format (using nvTurboDatabase
or dbmcompress) will probably result in corruption. You could try using
ovtopofix to fix any database corruption and/or you could try backing out of the
NDBM format by using the dbmcompress utility on your databases with no options
specified (see page 52 of the NetView 5.1 Release Notes - would recommend you
speak to Support for further advise here). But your best bet would be to restore
from a backup or completely re-discover. It is recommended that you always make
a backup before working on the databases.
"I used nvTurboDb speed (and space) but after syncronize the file grows
again." Which file grows ? This may suggest that the nvTurboDatabase command did
not complete the conversion successfully. The process of converting your
databases by using nvTurboDatabase will actually backup your databases and thus
it is expected that you have space available in your /usr file system for this
process - otherwise corruption may result. Using the ovwdbdmap command on a NDBM
formatted database would not of helped matters and should never be used from my
understanding.
To convert the standard NetView databases to NDBM format:
1. Backup you databases.
2. Run the ovmapcount -a and ovtopofix -A commands to cleanup inconsistencies
that may already exist.
3. Ensure adequate space in /usr for the database backups that will be performed
by the nvTurboDatabase utility.
4. Enter /usr/OV/service/nvTurboDatabase space
5. Enter /usr/OV/service/nvTurboDatabase speed
6. Enter ovw &, to start the NetView GUI. Note: DO NOT start netmon at this
time.
Wait for the topology and object databases to sync up with each other.
This step may take longer than usual but it is an important part of the process.
7. Enter ovstart netmon, to start the netmon daemon.
For further advise, you would probably be best to call Support as James has
suggested.
Gareth Holl
Level 2 Support Engineer
James_Shanks@TIVOLI.COM on 07/03/2000 09:40:02 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: IBM NetView Discussion <nv-l@tkg.com>
cc: (bcc: Gareth Holl/Tivoli Systems)
Subject: Re: [NV-L] Database connection lost
You are in a world of hurt now and you need to call Support immediately. The
proper thing would have been to do a compress with ovwdbdmap before you ran
nvTurboDb. It may be that there is now a corrupt object that can be found and
deleted -- I would try ovtopofix (either -a if you have only one map, -A if you
have more than one) and see if that helps. If it does not, then Support will
need to assist you. And you will also have to put on 5.1.3 is you have not done
so already.
I hope you kept a backup of /usr/OV/databases/openview before you started all
this, else you may have to delete your entire data base and start over.
The issue of a 2 GB database in a 1 GB filesystem is misleading.
Unfortunately, you have misinterpreted what is really going on. The NetView
databases are what are called "sparse" file systems, which means that they use a
pointer mechanism which may make it look like they are using much more space
than they actually are, because not all the system tools (ls, for example) are
built to deal with these unique structures.
James Shanks
Team Leader, Level 3 Support
Tivoli NetView for UNIX and NT
zuffranieri@IT.IBM.COM on 07/03/2000 08:55:25 AM
Please respond to IBM NetView Discussion <nv-l@tkg.com>
To: NV-L@UCSBVM.ucsb.edu
cc: (bcc: James Shanks/Tivoli Systems)
Subject: [NV-L] Database connection lost
Hi all,
I have a problem with Netview 5.1 on AIX 4.2.1
The file /usr/OV/databases/openview/ovwdb/current/value_info has become 2
GB large, in a filesystem of 1 GB !
I used nvTurboDb speed (and space) but after syncronize the file grows
again.
Then I used ovwdbdmap -c and now the file remains of 70 MB.
Some day after I received the error
Fatal ovw error
Database connection lost
ipmapBailout called from nl_callbacks.C(2732)
and ovwdb abends.
Do you know anything about?
Thanks Fabio
Fabio Zuffranieri
IBM Global Services-ITS
Via Sciangai 53-Rome 00144-ITALY
email:zuffranieri@it.ibm.com
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________________
NV-L List information and Archives: http://www.tkg.com/nv-l
|