DSXchange

Use sqlplus to run any SQL script. Choose a Batch or Sequence job to do the deed.

OPENPATH has to be used with hashed files in non-project directories, unless you've used SETFILE to create a pointer.

It doesn't matter how big your server is if you exceed the ability of the server to handle its tasks. For example, if a 4 cpu machine can't handle 16 simultaneous DS jobs, it reasons that a 8 cpu machine can't handle 32 simultaneous DS jobs. You need to look at the demand placed on the server and ad...

Database vendor specific connections are managed thru the database client software, be it an connection layer (OCI, CLI plugins to native DB APIs) or a command line layer (sqlldr, OSQL, etc). ODBC is handled thru the ODBC manager. Any Oracle configurations are managed via Oracle. You need to worry a...

The time may be an issue, try OCONV(ICONV(LEFT(Incoming Link,10),"D4 YMD"),"DQ")

Verify permissions of the directory, umask setting in ds.rc script, and userid with group.

Sounds like a Windoze file that is being accessed may be open by another process. Even having a Windoze Explorer focused on a file will prevent the file from being removed or processed by a DS job.

No matter what, you'll need a positional cross-reference for each indicator value. Consider writing a function that takes two arguments: value and token. Pass the function the binary text string as the value, and a token such as "FRED", where the token corresponds to an named indicator. Use a CASE s...

Your routines returned errors, fix them. Post the logic for help (please preserve formatting).

No. You'll need to send your database output to another passive stage first and then on to the database. Or, set your commit (if rollback space allows) to 0 and make the database the last link in the execution order. If the files finish first, then the database link will close issuing the commit.

The fact that there's a differing model (Star Schema) for analytical systems indicates there are very good reasons. Consider reading Kimball's Toolkit books for more information why.

Troubleshooting a job that mixes source relational stages and target relational stages are nearly impossible to tune. You have too many variables, too many degrees of freedom. Are there database issues stalling source data, are there database issues stalling loading target data? Are your source and ...

Good thing we have a PAID webmaster. Gee, where does that money come from?

Paste the routine logic, we need to see what the routine is doing to see why concurrent execution might not work.

You could gimmick the ODBC stage to output from an SP a dummy row after its done doing whatever you need.