DSXchange

You must use TO_DATE(...) functions on all columns that are DATE or TIMESTAMP datatypes. DS passes text strings that look like dates to Oracle, but your SQL must include this. If you use GENERATED SQL, you'll see that DS automatically adds TO_DATE when writing and TO_CHAR when reading using the ORAO...

I have such a utility job in my website members area if you're interested:

SetDefaultParams - A batch utility that selectively can copy job parameters from one job to a wildcard list of other jobs.

600+ MB


You really should be exporting by category and use multiple concurrent exports on your machine to expedite the process.

What is the target stage you are using? It matters.

Manual (Explorer or command line) as long as the files aren't in use.

Follow Kim's advice, but the general idea is that you will use a reference lookup to the OCI stage and custom SQL that does the select of the next value from the sequence.

Sometimes customers send data files to other applications or offsite to other business associates. To insure data integrity, you could build a delimited file with an extra column on each row of data that contains the checksum of the data in the row. The receiver can validate each row when parsing th...

What is your source, and what is your target? Different stages do different things.

Methinks you need to look at the SQL after following Craig's advice. Your SQL may/may not contain the schema owner, plus the column derivations in the ODBC/OCI stage contain fully qualified names. Even if you have your table name correct, if the derivations contain another table name you need to cle...

Sure, dsjob takes as parameters the server, userid, password, project, and jobname. The Sequencer and Batch job control API's only work with the current project. Awhile back I considered writing a universal job control that included the project name with the job, but the functionality of dsjob is no...

Sure, Unix machines scale into monster sizes with hundreds of CPUs and GBs of RAM with lightning fast disk darms.

clarcombe wrote:Is my only alternative to encapsulate DSLogInfo in a routine and pass the variables as parameters.

Yes. Think of it as an opportunity for a custom fit solution that handles all of your needs, written by you.

The query must be indicating something like a DECIMAL(30) as the datatype for the computed column. If you do a CREATE TABLE AS (your select query), what is the data type of the computed column? Unless you do an explicit TO_CHAR() on the column, my guess is that the datatype is being supplied as a DE...

Ahh, so your "computed" column is done via custom SQL (sorry I didn't understand your terminology) and you had to create custom metadata to support the returning values. Yes, the metadata does matter. The SQL query is a cursor, and all columns have to be data typed. By choosing CHAR, you automatical...

The Search facility has a threshold for indexing common words. Once something hits that magic number, it doesn't get included in global searches. Sometimes that causes heartache for new members who aren't used to using it. Yeah yeah yeah, given enough time and money your Webmaster will probably enha...