I started an earlier thread, but now I have more information.
1. Created an mdq for an Oracle Database
2. Defined a table called t_edi_310
3. Defined a query edi_310 that is simply "select * from t_edi_310"
4. Generated a tree for the query (edi_300.mtt)
Now, I want to create a map using the query for input. I created an input card using:
Type Tree: edi_300.mtt
Type: Row edi_300 Data
Query: edi_300
The map builds successfully. However, when I run the map it reads one time, then I receive:
"Input valid but unknown data found"
* The input log looks fine; it shows all of the rows with all columns delimited properly
* The mtr file, however, shows what appears to be the key to the problem. It maps each column of the first row properly, but then shows this:
(Level 0: Offset 0, len 490, comp 1 of 0, #1, DI 00000015
Data at offset 0 ('0|SHIP |200') was found to be of TYPE X'0003' (Row edi_310 Data).
INPUT 1 was valid but contained 59537 bytes of unknown data at the end.
* The '0|SHIP...' is actually the data from the second row in the query. It's as if it did not recognize that we've started a new row.
I have to believe I've defined something wrong, but I have no idea what it might be.
1. Created an mdq for an Oracle Database
2. Defined a table called t_edi_310
3. Defined a query edi_310 that is simply "select * from t_edi_310"
4. Generated a tree for the query (edi_300.mtt)
Now, I want to create a map using the query for input. I created an input card using:
Type Tree: edi_300.mtt
Type: Row edi_300 Data
Query: edi_300
The map builds successfully. However, when I run the map it reads one time, then I receive:
"Input valid but unknown data found"
* The input log looks fine; it shows all of the rows with all columns delimited properly
* The mtr file, however, shows what appears to be the key to the problem. It maps each column of the first row properly, but then shows this:
(Level 0: Offset 0, len 490, comp 1 of 0, #1, DI 00000015
Data at offset 0 ('0|SHIP |200') was found to be of TYPE X'0003' (Row edi_310 Data).
INPUT 1 was valid but contained 59537 bytes of unknown data at the end.
* The '0|SHIP...' is actually the data from the second row in the query. It's as if it did not recognize that we've started a new row.
I have to believe I've defined something wrong, but I have no idea what it might be.