Many of the internal error message numbers live in a table called SYS.MESSAGE. This has a six character key, so you may need to add leading zero(es). For example: SELECT * FROM SYS.MESSAGE WHERE @ID = '081002'; Some of those that aren't in SYS.MESSAGE can be found, with some degree of difficulty, in...
The first error message tells you very clearly what the problem is. You have specified a dataset for the input link (to the Transformer stage) but have specified a rejects link without a corresponding dataset. Therefore the job has no mechanism for dealing with the rows rejected in each partition. Y...
At my current site a few runs were performed that ran more than 2-3 hours, and were definitely nowhere near 100GB. Of course, elapsed time is as much as anything a function of how complex the analysis you're performing is. More complex analyses take longer; this is a simple fact of life. It being Su...
Welcome aboard! :D I note that you are on Windows, this explanation relates to that platform. To extract data from Excel, the data must be in columnar format with column headings. Set up an ODBC data source using Microsoft ODBC driver for Excel as the driver, and select the workbook that you wish to...
Thank you again for the kind words. I was lucky to be in the right place at the right time when DataStage was being developed and first released, and to have a background in Prime INFORMATION and UniVerse (and, curiously, HyperStar, which afforded in-depth knowledge of how ODBC works). It is both be...
DataStage system variables are documented in the DataStage BASIC manual. Some of them are documented in on-line help (the topic System Variables will get you started). Values generated by these can not, in general, be inserted directly into SQL. You use the system variables in a Transformer stage to...
I suspect that the display of elapsed time uses Oconv(seconds, "MTS"), which is written so as to return a value in the range 00:00:00 through 23:59:59.
You can test it yourself; Oconv(Iconv("28:00:00","MTS"), "MTS:") returns "04:00:00")
Of course, a database unload might be the fastest possibility. I don't know Oracle well enough to say whether conditional unloading is possible. It certainly is in Red Brick - the unload is performed at a physical level and is mega-fast! Red Brick is a trademark of International Business Machines Co...
For example, what is SYSDATE for one database's SQL might be CURRENT_DATE in another. If you're writing user-defined SQL it must be correct for the database/driver with which you're communicating.
Lookahead in a delimited text file is possible (using SQL via ODBC driver for text files) but horrendously slow. Ken's suggestion (using a hashed file) is the best solution. The nice thing about this approach is that DataStage internal date format is an integer, which makes it so easy to get day+1, ...
The only parameterised columns in a lookup query are the key columns (think about it). More accurately, the only parameterised columns in a lookup query generated by DataStage are those columns that your design has asserted to be key columns (you are permitted to lie, and can use that fact to get mu...
Always correct the first error first. In your case, this is the error regarding the PWD environment variable. There is another thread updated as recently as today on this topic.