DSXchange

Read the forum again and as per some one's suggestion I broke the job into two streams and it worked. I am curious to know the reason for this behaviour ? Anyone care to explain.... It's just one of those things. The pipe solution is great for added performance, but if your performance is acceptabl...

Absolutely not, even versions of 7.5 are incompatible with each other. I suggest you look at the client switcher utility on the install cd.

Spool the data to a Sequential text file with a "," (comma) as the field separator, having the unique row identifier as the first column, an additional new column called "FAKE_SEPARATOR" with a derivation of literal "|" (pipe), and then the rest of the attribute columns after that. Read back the sam...

Use the Sequential stage, declare 1 column of metadata that will read the entire line. In a transformer constraint, throw away all lines that contain anything that identifies the line as blank, header, title, or other formatting information. Output the remaining data rows to a Sequential file. Now, ...

If you mean extracting from a snapshot (static copy of the primary database), sure, why not? You're basically hitting a remote copy, as long as the data is synchronized across all of the tables at the point of the snapshot, sounds okay. You've got a static dataset, so you'll have to coordinate aroun...

Don't know what the number means, but you should suspect that something happened to one of the objects in the dsx file and that it did not import correctly. You might try reimporting and see if the object name pops up as having an issue when overwriting.

There are no time elements to dates as Server has no data typing enforced, everything is a string. Therefore, any value of 2005-12-31 is just a text string inside DataStage. If you're asking from an SQL perspective, I suggest you specify in your SQL the format of date/time values. In Oracle, it woul...

Command line is done using DBACCESS. Google it for more info. You can generate the SQL script and run it from command line.

The load file must be resident on the same server as the database, and must be invoked via a call from that same server. DIRECT path does not care about indexes, constraints, and triggers. They are all disable during the load operation. Switching from CONVENTIONAL to DIRECT path is something that re...

If your stored procedures DO something, use a Sequencer job with a Command stage and run sqlplus or a Batch job to call the DSExecute API to have more control over the sqlplus session. If you're using sp's to STREAM data (input and output), then use your OCI stages. If you're using generated or user...

I scratched my head and except for a few fleas no memories of switches on given commands came to mind. The only solution I could think of is a .ksh script to parse each row, loop thru the count of "|" found in each line 1 to x, use cut -d"|" -fx to extract each field and then use cut -d"]" -f2 to ta...

Contact technical support. You'll probably have to create the projects fresh and then import the jobs if tech support can't help you fix the issue.

1. Windoze specific service for the DS engine
2. Allows users to telnet to the DS Engine and perform command line administration
3. Allows clients to talk to the repository.

It's mostly controlled to Windoze security, so make sure the users are in a valid domain for the server and then control individual user access thru DS roles of Operator, Developer, etc. in DS Administrator.

There is no dynamic SQL capability. You'll need to use a stored procedure to do what you wish.