nv-l

RE: [nv-l] Error retrieving mapdb field info: Null field value

2005-09-13 11:25:48
Subject: RE: [nv-l] Error retrieving mapdb field info: Null field value
From: "Van Order, Drew \(US - Hermitage\)" <dvanorder AT deloitte DOT com>
To: <nv-l AT lists.us.ibm DOT com>
Date: Tue, 13 Sep 2005 10:21:49 -0500
As long as you have the .BAK files created during compression you can get back to where you were prior to all this happening. You still may need a prior backup to restore. Our value_info.ovf was over 2 GB--and thought best practice was to run ovmapcount and ovtopofix before compressing. Maybe compressing first caused the corruption?
-----Original Message-----
From: owner-nv-l AT lists.us.ibm DOT com [mailto:owner-nv-l AT lists.us.ibm DOT com] On Behalf Of Mario Behring
Sent: Monday, September 12, 2005 4:10 PM
To: NetView List
Subject: [nv-l] Error retrieving mapdb field info: Null field value

Hi list,
 
I have a NV 7.1.4 with Fixpack 3 running on a Solaris 5.8 box. For some reason the file value_info.ovf increased its size in 130MB in about an hour and continued this way. I executed the commands below after consulting IBM support:
 
nvturbodatabase space
nvturbodatabase speed
ovmapcount
ovtopofix -a
ovw_fields
ovw_config
ovw_verify
The problem is that now I have the following error message when trying to open the GUI:
 
"Error retrieving mapdb field info: Null field value"
 
Any ideas ??
 
Thank you.
 
Mario

__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com



This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law.  If you are not the intended recipient, you should delete this message. 

Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
<Prev in Thread] Current Thread [Next in Thread>