on 09-15-2005 5:23 PM
Hi folks,
after creating a UDC-datasource with connection to a MS SQL-Server 2000 database, extraction fails with the error message 'RSSDK:400 String index out of range:-1'.
All conversion exits were removed and case sensitivity was activated for each character field, as it is supposed.
It looks like a JDBC error message and does not occur on each table or view.
Does anybody have an idea???
Points will be rewarded for successfull help.
Hi Maik,
I don't know if this can be related but take a look to OSS Note 874549...
Bye,
Roberto
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Roberto,
thank you for your answer, but I checked all existing OSS-Notes related to UDC. We opened an OSS call and the solution they supposed was already implemented in our System, running on the highest released patch level.
My problem might be related to the design of source database, where I succeed my investigations tomorrow.
I was pretty sure that you were one of the only guys that could offer a hint.
Hi Maik,
I guess we know each other, don't we?
Now just a stupid guess. Are you extracting string (or at least long text) fields? If yes, is it possible for you to create a view for extraction limiting the text fields to a length of, lets say 60 chars, by using the substr function? I know this doesn't really fit to your error message, but I already had a similar message extracting long texts via dbconnect.
regards
Siggi
Hi Siggi,
well, we know each other from wolfcraft and I was your "successor" at HPC, now I work for Deloitte.
Actualy I solved the problem on my own. The problem was, that the view to be extracted contained some fields that needed to be converted to a compatible data type. The error message was a little bit confusing, because it didn't show any relation to the real bug.
But thanks for help.
Hi Maik,
I am encountering problem while pulling data from SQl data base.
the load is failing saying "String Index Out of range: -1".
You have mentioned that you have solved this problem by converting some fields into compatible data type. Can you please let me know what sort of conversion you have done from which data type to which data type and how
it is done.
Do we need change the data type of columns in SQL as it is not compatible to
UD Connect. how feasible is this...Please ket me know.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.