Hi, Unable to initialize the importer."record_length=fixed" (no length given) and record field format is variable-length. The first variable-length field is ""
Job works fine in DS9.1 dev env . For the same file in higher environment the fails with above error . Is this a file issue or env issue.
I see several posts and I tried all options..no luck..
Sequential file unable to initialize importer
Moderators: chulett, rschirm, roy
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
First and obvious question - what's different about the dev environment that it works there and not in the other environments?
That you have a zero length string (presumably in a VarChar column) is almost certainly the sourced of your problems. Is this supposed to represent NULL? If you go the fixed-length route, then all strings must be of data type Char and their Null Field Value must have the same number of characters as the size of the field.
That you have a zero length string (presumably in a VarChar column) is almost certainly the sourced of your problems. Is this supposed to represent NULL? If you go the fixed-length route, then all strings must be of data type Char and their Null Field Value must have the same number of characters as the size of the field.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Ray,
all the fields have length defined. The job was imported from dev environment. Everything is intact. Its strange. Its supposed to work in the current environment like in the dev. If I read fixed with file through a single column I can view the data. SInce there are a large number of columns reading a single column and then parsing is not practical.. I cannot make a design change at this point.
all the fields have length defined. The job was imported from dev environment. Everything is intact. Its strange. Its supposed to work in the current environment like in the dev. If I read fixed with file through a single column I can view the data. SInce there are a large number of columns reading a single column and then parsing is not practical.. I cannot make a design change at this point.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
You didn't answer my question.
What's different between the environments? (Tip: the answer is not "nothing". Clearly.)
Might there be a difference in the data, for example? The "" value does not occur in the file in dev but does in the new environment.
Also, reading a single column and parsing is always practical. The parsing then occurs in parallel.
What's different between the environments? (Tip: the answer is not "nothing". Clearly.)
Might there be a difference in the data, for example? The "" value does not occur in the file in dev but does in the new environment.
Also, reading a single column and parsing is always practical. The parsing then occurs in parallel.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.