Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
This one has me completely stumped.
I have a csv file with 223 records in it. I am doing a left join to an existing table, pulling just three columns out of the file. There is no WHERE clause in the load statement.
When I run the refresh on the server, I'm only seeing 179 (this is according to the log file).
There are other csv files with the same type of data in the same format being read in, and this is the only file I'm having any issue with.
What I have been able to determine so far is that there is some commonality of the data that is not being read in. One column has 6 possible values; there are 29 rows that have a common value in that column which are missing, and there are another 15 with a common, but different, value as well.
Now for the wierd part. I have local copies of the exact same files on my laptop. When I run it there, all 223 rows are being read in.
Has anyone experienced anything like this before? If so, how did you correct it?
Deepak,
You aren't going to believe what I found. There was a second copy of the file, dated from back in April with the exact same name. Apparently the script that retrieves the file from an email box and copies it to the repository folder where we keep such data files did not properly overwrite the old file - so there must have been some corruption in the hard drive's table of content as a result. I had to delete both copies, then replace the file, and it loaded correctly.
hi,
The QV version on both server and local is it same ? Can you share the excel so that we can check it our end.
Deepak
Hi,
Sorry but I can't share the file, it has proprietary data in it.
According to the supporting engineer, server is V10 SR4; my client is V10 SR2 64-bit.
hi,
Then you have to try installing SR4 in your system and check if the issue is still there. If its issue exists then it might be BUG in SR4.
The new SR5 release is available for download. You can install it and check if it is working there or not.
Deepak
Deepak,
You aren't going to believe what I found. There was a second copy of the file, dated from back in April with the exact same name. Apparently the script that retrieves the file from an email box and copies it to the repository folder where we keep such data files did not properly overwrite the old file - so there must have been some corruption in the hard drive's table of content as a result. I had to delete both copies, then replace the file, and it loaded correctly.