on 01-07-2010 11:06 AM
Hi Experts,
We are getting the below error message for a flat file load after server migration from windows to UNIX.
'Error 4 in the update'
can someone help us in solving this issue, thanks in advance
When you double click on the message you should get a long text that explains the error. Or look into the detail view.
A wild guess would make me think that you have a codepage problem if it was running before.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shashi,
for how many records you are getting errors , check in error stock / psa,
find out if there is any filed length issue by comparing the success full record and eroneus record;
if you are in BI7, edit the records in Error Stock and run the error DTP.
Error 4 is related to Data only, make sure the file is closed and not used by other application while the time of loading.
analyse more and let us know more details for solution
Regards
ReddY A
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi All,
this issue is now resloved,
the reason behind this issue is invalid character u2018#u2019 which was getting inserted to all the rows of the flat files copied to our UNIX server from Windows server.
Seems to be problem with copying these files from Windows to Unix, the way the 2 operating systems handles some characters is different. Unix provides command to fix this (converting the files to Unix format using dos2unix).
Thanks all..i have assigned the points.
Hi Shasi,
There might be chance of misinterpreting the filed and its length. Compare the structure of the flatfile and structure of the datasource.
Regards,
Venkata Boga.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
'Error 4 in the update'
Means problem with data updation its coz of data inconsistency like special char or missing currency fiels etc..
Could you be more specific, In RSMO for sure this is not alone the message, try to click on the secound line of error message which will tells you about the error record log in psa(If you loaded via psa else try loading via psa to filter the error records).
Correct the erroneous record in psa and load it back else maintain the special character acceptance criteria in RSKC.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
Please check OSS Note 555788. If note already implemented, then try to analyse the Flat File.
I think you are facing an invalid character issue.
This issue can be resolved by correcting the error records in PSA or the FlatFile and updating it into the target. for that the first step should be to identify if all the records are there in PSA. You can find out this from checking the Details tab in RSMO, Job log , PSA > sorting records based on status,etc. Once its confirmed force the request to red and delete the particular request from the target cube. Then go to PSA and edit the incorrect records (correcting or blanking out the invalid entries for particular field InfoObject for the incorrect record) and save it. Once all the incorrect records are edited go to RSA1>PSA find the particular request and update to target manually (right click on PSA request > Start update immediately).
This should solve your problem for now. Hope this helps.
Hope this helps.
Regards,
Mahesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.