11/3/2022 0 Comments Ebcdic file viewer![]() ![]() Then I created package that calls the procedure with the desired options. TmpPath = localDirectory + "/" + localFilename + "~" # There is probably a better way to do this ![]() LocalPath = localDirectory + "/" + localFilenameįtp = snpsftp.SnpsFTP(remoteServer, remoteLogin, remotePassword) RemotePath = remoteDirectory + "/" + remoteFilename The original file format is fixed EBCDIC with each record containing 16 fields for a length 210 bytes per record, and my hacked version adds 1 byte to each record for a new length of 211.Ĭan someone from Oracle please advise how we should proceed? I'm not opposed to writing a custom knowledge module that inserts the newline character, but I'm still hoping that ODI can handle this condition "out of the box." This must be a common situation for ODI integrations.įirst I created a procedure called "ftpGetEbcdicFile" that takes the following options: I can now see all of the records in the file, and all fields are being translated correctly. The calculator displays a text file content in the encoding of your choice. Next, as a test I also manually created a version of the data file that separates each line with the EBCDIC newline character, and this causes the data viewer work perfectly. Initially I tried to view the data without defining the record separator but ODI threw exceptions stating ".dataset.DataSetException: Execution of query failed." and ": Record separator cannot be null for file C:/FILENAME" Inspecting the data file through a hex dump I can verify there are no record separator characters present. I specified the EBCDIC newline character (hex 0x15) for this field, but this was just an educated guess. Presumably this is because it never finds the record separator character that I was forced to define in the "Files" tab. Using the "View Data" feature I can see all my fields being translated perfectly, but it doesn't go beyond the first record. ![]() I'm connecting to the file using the .file.FileDriver / jdbc:snps:dbfile driver. I'm experiencing the same issue in ODI 11g.įirst I ftp'd (in binary mode) a copy of the EBCDIC file to my local drive (Windows XP) and defined the file format manually in ODI Studio. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |