Hi
I am selecting 10 million from a DB2 TABLE in Z/Linux .but i am getting error as limit reached time out..
how can i fix this issue ...how can i fine tune this in datastage ...
DBA dont want to increase time ... and the table is not yet partitioned ...
SELECT rows from table
Moderators: chulett, rschirm, roy
SELECT rows from table
Last edited by sainath on Wed Nov 16, 2011 8:02 am, edited 1 time in total.
-
- Participant
- Posts: 54607
- Joined: Wed Oct 23, 2002 10:52 pm
- Location: Sydney, Australia
- Contact:
Eliminating any GROUP BY or ORDER BY clause in your SELECT statement should allow Oracle to stream data into your job as they are retrieved. Unless, of course, Oracle has to materialize a view or perform some other operation that takes too long before being able to deliver rows.
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.
5 CPU seconds and 50000 service units seem pretty small...sounds as if the database may normally be used and tuned for small transaction processing rather than batch extracts.
If you're performing a join within DB2Z you may wish to move it into the datastage job instead and perform just simple selects from the tables.
With the DB2 connector you can perform a Modulus partitioned read based on an integer table column if available, so long as the partitioning won't affect your query results in the end.
Regards,
If you're performing a join within DB2Z you may wish to move it into the datastage job instead and perform just simple selects from the tables.
With the DB2 connector you can perform a Modulus partitioned read based on an integer table column if available, so long as the partitioning won't affect your query results in the end.
Regards,
- james wiles
All generalizations are false, including this one - Mark Twain.
All generalizations are false, including this one - Mark Twain.