DSXchange

Would it not have been easier to pre-filter with, say, grep and pipe that result into awk?

What precision and scale did you specify for the Decimal data type? Did you try increasing this when the "insufficient precision" message occurred?

A Lookup File Set has to be prepared to support range lookups when it is being created. The Range Lookup property is set to "Yes" which exposes three properties Bounded Column, Lower Bound and Upper Bound. The Options folder has two useful properties - Allow Duplicates and Diskpool.

Chapter 13 of the manual Information Server Administration addresses the topics of backing up and restoring Information Server.

That was an exceptionally well-deserved award. Well done.

I guess you will just have to wait until next time U logs in here.

The second person personal pronoun in English is spelled "you". U is one of our posters.

It's very odd that a single byte is being reported as a problem in a two-bytes-per-character code set (GB2312). Does your row contain an odd number of bytes?

Actually this is probably the correct forum for a question about the internal WriteHash() function.

There are several possible causes for failure to write to a hashed file, including an illegal key (null or one that contains mark characters) or a corrupted hashed file.

Have you tried creating (and using) an XSD, as suggested?

What's the block size? How many nodes?

Please read this post carefully. We don't do "urgent". After all, it's not urgent for us. DSXchange is an all-volunteer site whose members post when and if they can. Indeed, some of us find "urgent" requests for our unpaid time offensive. If you really do need urgent answers, sig...

You can restrict the large table SELECT to those rows that fall between the largest and smallest dates in your driver data. Then you should be able to perform a range lookup.

We did not have any information about which stage types were being used, so I thought I'd throw in that gem. It also depends on whether Data Element "Date" (etc.) is specified whether internal format conversion occurs.

Performance statistics are not preserved in any location that the Director can access. You can probably access historical performance data in Metadata Workbench (and possibly through the Reporting Console).

The more entries that exist in &PH& and/or logs, the slower job startup times will be, particularly on operating systems that use linear directory file structures. &PH&, being a directory, can not fill with files until there are more than 4G entries (or the disk fills). If RT_LOGnnn ...