dear frnds,
i am looking for deltas from source to staging (delta is looked via max(order_id))
where V_ORDERS.ORDER_ID>
(SELECT (MAX(ETL_CONTROL_TABLE_LOAD.MAX_ROW_ID))
FROM E_EXPRESS.ETL_CONTROL_TABLE_LOAD
WHERE ETL_CONTROL_TABLE_LOAD.TABLE_NAME = 'STG_SSWAT_ORDER')
its ok,
i am applying same logic for development it always give me
4 rows less then Staging area.
where STG_SSWAT_ORDER.ORDER_ID>
(SELECT (MAX(ETL_CONTROL_TABLE_LOAD.ROWS_REQD))
FROM DSADMIN.ETL_CONTROL_TABLE_LOAD
WHERE ETL_CONTROL_TABLE_LOAD.TABLE_NAME = 'DIM_SSWAT_ORDER')
its 4 row less everytime
but the the count is same
i was wondering if the count is same from source to staging to development why
the max value is less ,
plz advice ,
Thanxs
bobby
problem in delta
Moderators: chulett, rschirm, roy
Re: problem in delta
My friend,
Your problems are very hard to solve via a forum like this.
I don't think it's a DataStage problem or issue (not that I know of). Are your restarts ok, are the values of the 2 restart points you seem to be using the same, what do you mean with "4 row less" but "the count is the same"?
Ogmios
Your problems are very hard to solve via a forum like this.
I don't think it's a DataStage problem or issue (not that I know of). Are your restarts ok, are the values of the 2 restart points you seem to be using the same, what do you mean with "4 row less" but "the count is the same"?
Ogmios
It would make buffering a pretty useless functionality when you would lose rows.
Run your 2 input queries outside of DataStage (via WinSQL or any other database query tool) and check how many rows get returned. If you still have the same difference then your problem is somewhere in your "design", your restart point values or your SQL statements... and not in DataStage.
In one query you're e.g. using ROWS_REQD in the other MAX_ROW_ID... maybe that's significant.
Ogmios
Run your 2 input queries outside of DataStage (via WinSQL or any other database query tool) and check how many rows get returned. If you still have the same difference then your problem is somewhere in your "design", your restart point values or your SQL statements... and not in DataStage.
In one query you're e.g. using ROWS_REQD in the other MAX_ROW_ID... maybe that's significant.
Ogmios