DSXchange

For a start off on this quickly, these are the things you need to consider for migration. Havent done this before, but will get more inputs for sure: 1. ODBC connections to be added to the odbc.ini and uvodbc.config files in the Ascential folder. 2. The directory structure for the jobs need to be cr...

Wouldnt you need to odbc connections on the host.

Did you try the ODBC stage which is a generic driver itself.

You are sure there are no warning messages in the message file?
What about the directors log?
How many columns are you passing?

Welcome Aboard You have an extra line at the end. This happened to me too once, when I NDM'd the file from the mainframe over to the file server on windows. The best way to handle it , is to go to the column tab in the sequential file stage, and set the 'Contains Terminators' of the last row to Yes.

If you are loading the table using the DB2 load stage then 80-100 rows/sec is extremely slow. You can get better performance with the DB2 API stage with that. Ideally, with the load stage, you should be getting about 15k - 35k rows/sec.

Yea thanks Kumar, your really helping (Sense the sarcasm ).

I could reach it
No encryption. I am nice

Did you try going into your control panel and checking if all the services are up and running (Ascential services i mean)?

I could sense purging The simplest way is to maintain two tables. Like say if your table name is myTable then second table would be the history table say, Hist_mytable . Once the records reach a certain limit, in your case 4 years, just rename your myTable to Hist_mytable . Thats what we do here. Sa...

Kumar, you are going to get me killed by our two top gurus, ill stick to aiming at the moon

Good catch Craig. Even i was thinking about that.

No. The job status becomes the status code of the command when you use -jobstatus along with the -run. Otherwise it will just return either a 0 or a 1.
Then to read that jobstatus you would use $?

Whenever such database errors pop up, always pay close attention to their codes. ORA-01652 usually happens when a sort operation cannot be finished in memory alone. Thats when the disk space comes into play but even that is falling short for your case. This error is begging you to get more room in t...

It doesnt matter how 'volumninous' the data is, backup's of databases are always taken. Do you need additional copies of that data to be stored? Isnt that waste of space and resources? Or is your requirement due to some purging requirements?