Well, as it turns out, once again the answer becomes clear within minutes of
going to the list.
But that's not a bad thing.
The data is being validated in, and the import is coming from, a .csv file.
My error, mentioning the .arx file. All the missing fields we're
experiencing are being cut off at the end of the record, as demonstrated by
contrasting the import log with the Excel file. It took me a while to figure
that out.
Also, I was completely missing the obvious fact that the records with the
missing fields were being imported.
So far, all the fields seem to be lined up without shifting or without
fields being inserted and throwing the rest of the record off.
Thanks for the quick response. You helped me verify what I thought I saw.
On 5/21/07, Rick Cook <[EMAIL PROTECTED]> wrote:
** Good advice, Ron. One other thought, to kind of piggyback on that is
that sometimes data columns get skewed or shifted to the right by a random
control character or data value in the raw data. Making sure that the last
column is all lined up properly for all records, as Ron suggested, should
ferret things like that out.
*Rick*
------------------------------
*From:* Action Request System discussion list(ARSList) [mailto:
[EMAIL PROTECTED] *On Behalf Of *Fariss, Ron
*Sent:* Monday, May 21, 2007 10:05 AM
*To:* arslist@ARSLIST.ORG
*Subject:* Re: Importing records, not enough fields....
** Bob,
Can you read the file with Excel?
If so, after you load the data into Excel, press Ctrl-End to go to the
last column, last row.
Make a note of what the last column and row are.
Typically, I find that there will be several blank rows at the end of the
spreadsheet. If blank rows exists, delete them from the spreadsheet and
save your file as a .csvfile for re-import.
If there aren't any blank rows, then make sure that all of your coulmns
have valid data. Sometimes one record near the beginning of the dataset
will have extra columns that do not exist for the majority of the file.
Please note that Excel formats all of the cells that you open, to a format
that it believes is correct. So, some of your values might be altered.
If this happens, then you might need to edit the import file within
Notepad after you determine what problems exist.
Ron Fariss
AIG Technologies
------------------------------
*From:* "Action Request System discussion list(ARSList)" [mailto:
[EMAIL PROTECTED] *On Behalf Of *Bob Rowe
*Sent:* Monday, May 21, 2007 11:50 AM
*To:* arslist@ARSLIST.ORG
*Subject:* Importing records, not enough fields....
** ARS 6.3, ITSM 6, CMDB 1.1, Oracle on Solaris
We are importing large amounts of data into the system in preparation for
going live with a new server with CMDB 1.1 added. The development has been
going well.
However, data import to the new server is resulting in a large number of
ARERR 4210 problems--"Not enough fields, found 72, expecting 83," for
example.
Comparing the rejection log with the import file, the missing fields seem
to be at the end of the record. Do you know of a common cause of this kind
of problem? Such as an oddball character causing a record truncation on
export to the .arx file?
Anything?
Thanks.
--
Bob Rowe, Remedy Action Request System Development and Administration
[EMAIL PROTECTED]
"The golden rule is to test everything in the light of reason and
experience, no matter from where it comes."
Mohandas K. Gandhi
__20060125_______________________This posting was submitted with HTML in
it___ __20060125_______________________This posting was submitted with HTML
in it___
__20060125_______________________This posting was submitted with HTML in
it___
--
Bob Rowe, Remedy Action Request System Development and Administration
[EMAIL PROTECTED]
"The golden rule is to test everything in the light of reason and
experience, no matter from where it comes."
Mohandas K. Gandhi
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers
Are"
