Page 1 of 1
External string too long..Job Aborted
Posted: Thu Oct 29, 2015 2:30 pm
by Developer9
Hi,
While I am testing my jobs in latest version 11.3 I got below error ..In version 8.5 job is running fine (I am using same data file )
Code: Select all
APT_CombinedOperatorController,xx: External string too long. Imported only 100 out of 125 external characters. Ignoring last 25 characters up to delimiter.
Please let me know if any one has seen this error message before
Thanks
Posted: Thu Oct 29, 2015 3:08 pm
by qt_ky
Yes, I have seen this many times when migrating to newer versions.
There is usually a metadata mismatch or some other detail in the job design, such as delimiter or other setting, that does not match the data.
In the older versions like 8.5 or 8.7, DataStage was more relaxed about enforcing metadata settings. In newer versions it is more strict.
Developer needs to pay more attention in newer versions and choose correct data types, lengths, etc. Hope that helps!
Posted: Fri Oct 30, 2015 2:28 pm
by Developer9
Thank you for the suggestion ..When I ran the job in stand alone (not in through sequence job)job finished with too many warnings.
If there are no data issues ,How can we eliminate these warnings with out making the changes to the jobs ?As we need to make lot of changes the jobs (each job reading around 100-200 columns and all are defined as varchar)
Looking for the Options to have the Sequence job to finish with out abort .
Posted: Fri Oct 30, 2015 6:52 pm
by qt_ky
Warnings are there to alert you of potential data loss and the like. It is a good practice to go after the root cause and correct the jobs that process the data to prevent the warnings and ensure correct results through a wide range of testing.
To mask the problem, you could choose to change the sequence jobs to allow warnings or run with no warning limit or handle the warnings with a message handler. I think message handlers are usually a poor choice, to be reserved as a last resort.
Just to reiterate, these types problems have been there all along, but only the newer version is informing you. The problems are not with the newer version itself.