Hi all,
I defined job that reads data from informix odbc and writes to postgres odbc.
Problem is that job gets data from source and don't write to destination.
In postgres logs i have that
- conection recived...
- some sets
- some select from metastage_loc_info that does not exist
- select which i don't understand
SELECT FIELD1,FIELD2,... FROM TABLE
Question is why destination stage selects data from table in spite of writing.
This table is big and i think that is waiting for all data and then it will start to write.
Can anyone explain me what is going on ?
best regards
--
k.p
postgres - strange sql
Moderators: chulett, rschirm, roy
-
ray.wurlod
- Participant
- Posts: 54595
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Welcome aboard.
The SELECTs are queries to the ODBC driver to check that the metadata (column names, data types, etc.) in your job match those in the table to which you are referring in your INSERT/UPDATE query.
The SELECTs are queries to the ODBC driver to check that the metadata (column names, data types, etc.) in your job match those in the table to which you are referring in your INSERT/UPDATE query.
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.
Thanks for quick answer.
It seems like database sends answer for this query but in the transaction.
So datastage waits for all data from this table.
It takes time, datastage servers takes more and more memory and processors are killed (almost 100%)
Maybe it is a problem of transactions seting on database or ODBC ?
I think that the structure should be confirmed after first portion of data.
Memory usage suggests that datastage recives data from odbc and waits for the end of the data stream and something doesn't allow him to stop after first record.
Can I do anythink with this ?
best regards
--
k.p
It seems like database sends answer for this query but in the transaction.
So datastage waits for all data from this table.
It takes time, datastage servers takes more and more memory and processors are killed (almost 100%)
Maybe it is a problem of transactions seting on database or ODBC ?
I think that the structure should be confirmed after first portion of data.
Memory usage suggests that datastage recives data from odbc and waits for the end of the data stream and something doesn't allow him to stop after first record.
Can I do anythink with this ?
best regards
--
k.p