DSXchange

This is BAD Do either a "df -k /yourprojectpath" or a "bdf /yourprojectpath" to get the stats on the filesystem. No matter what, you really need to protect yourself and make sure you've got all of your jobdesigns and functions saved. This affects all projects on that filesystem. Get an export right ...

If they're two different databases and technologies, you can't write a single SQL statement easily. The query supplied is an inner join, so only matching rows in both tables will be in the output. It matters which table is the driver, so use the driving table as the primary input stream, probably yo...

If it's just one job, export it and reimport it. If it's all of your jobs, export your project immediately or risk corroupting it. You need to check that you're not out of space on the project filesystem. If you are, make the export to save everything incase you corrupt the actually job design hash ...

I do have a trigger on the table to update update_user_id and update_date. Every row loaded hits this trigger, can it be disabled on this table and you do the work in the ETL job? You'll save a lot of time. Regarding table space etc. am I supposed to get Oracle error for that rather than abnormal e...

Please provide a text sketch of your job, something like this: OCI--->xfm--->SEQ--->xfm--->OCI. The way you described your job design left me scratching my head. I hope your job design is like the above sketch, as it will actually run 2 distinct processes with the second dependent on the full comple...

Either use the DS APIs for getting link statistics (read your DS BASIC manual, search DSXchange for examples) or use the dsjob command line to call the APIs for you. Either way, you'll need an after-job routine call, to either your custom subroutine or to ExecDOS to run a batch file of dsjob commands.

If you are sure you will have less than 3 possible different date values, this solution will work. Initialize 3 stage variables in a transformer to some known value, like "-999999", each stage variable will form the constraint for an output link. Have three output links, each with a constraint that ...

This is all nice and dandy. I love parameters. But the password is a different animal. It is a security issue. If hard codded in the job then it is masked. Yet passed as a perameter value it is open to everybody who can ps -ef the processes. Any ideas? Only if you use the dsjob program to set param...

Sure, DS ships with an ODBC driver to SQL-Server 7. You just configure the odbc.ini file with the entries to point to each SQL-Server. It will require things like IP or hostname, db name, port, etc. No problems doing what you want, as long as you have the right version and configuration information.

Release 7.5x2 is PX on NT.

You cannot take an Powermart/center mapping and load it into DataStage. There is no conversion tool either.

Verify that it is still running. Do a ps -ef |grep phantom to see what parts are still moving. If there are no parts, then the job may have died tragically and never updated its status. Clearing the status of the job using Director or recompiling will fix that. If the job is still running, then you'...

vcannadevula wrote:This will take care of last ouput row.

No it won't. Build the job, you will see that it does not work.

You should be fine. OCI8 using 8.1.7 client talking to 9i DB is very stable. It's the only solution if you need to connect with 7.3, 8, and 9 DB instances. 9 client does not work with 7.3 DB.

kommven wrote:So any built-in stage in DS?

The AGGREGATOR stage. If you insist on stage variables, then you are going to need to add a last row to your input datastream to trigger the last output group.