DSXchange

Maybe you are covering the whole command string within a double quotes. Try single quotes over field demiliter (or viceversa)

Did you identify which records are missing and see whether there is any pattern that may case them to be dropped ?

Also what happens if you load only the 900 rows that were successfully loaded.

Maybe your 3rd party s/w is working in 90% efficiency.

Did you try searching?

There are loads of similar (or identical) posts.

General Answer: Use stage variables

Even though I wish to differ from Ray that Datasets can be compressed but agree that the benefits are not huge.

As mentioned before, you may gain by organising it better.

Even though I wish to differ from Ray that Datasets can be compressed but agree that the benefits are not huge.

SQL loader control file is different from control file of Oracle.

They are text files created in OS.

Did you look at the sql loader control file from operating system level?

How did you come to the conclusion? What errors did you obtain?

Did you check the ctl file from OS level ?

That is a SQL Server issue.

Is DB down?

You can compress using normal OS commands.

Compression ratio depends on the content - just like the text files.

Before going down that route, did you try clearing unwanted and "expired" datasets.

You can compress datasets.

But before that can you provide more info on what you are trying to achieve.

Check your PATH.

Try a simple Unix command from DataStage.

Do you have any "Date" or "Calendar" table in oracle ?

It will be better to generate rows in Oracle itself.

Create a view to generate rows for last n years. You can join this in Oracle source.

Do you have relevant permissions to load?

What do you mean by 'source 2' ?

Can you provide a pseudo-code of your expected logic.