Hi, Linda --
The nvdbimport command requires that the fields already be defined. Instead of
editing ovw_fields, though, you should create a separate file under
/usr/OV/fields/C, so that your modifications are clearly identifiable and to
make future migration or updates easier.
I noticed that you left a space after the comma in " CircuitID" after the
comma. The nvdbimport command will try to update the field " CircuitID"
instead of "CircuitID".
The commas in your Selection names would be interpreted as field delimiters.
I'm not sure if there's some sort of a workaround for that. Someone else may
be able to answer that.
In a message dated Mon, 20 Mar 2000 4:46:48 PM Eastern Standard Time,
"Ferreira, Linda" <FerreiraL AT nabisco DOT com> writes:
> Hi everyone,
> In order to use the nvdbimport, do you first need to create the fields (by
> editing ovw_fields and running ovw-fields)? and then use ovdbimport to
> populate the fields? Or can the nvdbimport create and populate at the same
> time. In the manual it says that the fields need to exist first before you
> populate, but in reading some entries from the NL-LIST I decided to question
> some of you experts who have already done this?
> Also, I have a question as far as populating the fields.
> If, for example, I already have a Selection Name and I want to enter
> "CircuitId" to correspond w/ that selection name do I do the
> Selection Name, CircuitId
> Atlanta, GA, DHECXXXXXXXXXXX
> I know it must be comma delimited, the problem is that my "Selection Name"
> have comma's in it, will it ignore the commas in the "Selection Name" or
> will it mess up my database by changing my Circuit Id's to "GA" and "IL". I
> would appreciate any feedback from anyone who has used nvdbimport before.
> Is the format above correct for populating the fields???? Thanks.
> Linda Ferreira
> Network Management Center
> ferreiral AT nabisco DOT com
> NV-L List information (unsubscribing, policies, posting, digest version,
> searchable archives): http://www.tkg.com/nv-l