DSXchange

Just to clarify the discussion was about the Repository DB and not the source and target DBs.

Source and Target DBs on Oracle 10g are compatible with DataStage 9.1 ?

Thanks All for your comments.

Upgrading the DB is certainly a plan in the near future . However just wanted to understand if that is a mandate for DS 9.1.

Hi , But what I can see in the IBM System requirements link for DataStage 9.1, Oracle 10g is not supported. Please clarify on this as we currently have DS 7.5.2 + oracle 10g and we are planning to upgrade DS to 9.1 , so do we need to upgrade DB as well. Databases (Mandatory) DB2 Enterprise Server Ed...

Thanks all for your responses. However, I have been able to narrow down the issue to the Editor I used .. That was NOTEPAD++. Using Wordpad/Notepad for replacing the ReadOnly field works perfectly fine.

If i try the other option of adding the message handler (not through job log), but from Message Handler Management in Director->Tools, however for thsi I would need the Message ID. Where can I find the Message ID? Got an answer for this search - we can get the message ID from the RT_log file of the...

Thanks All for the responses.

I am looking for a table which would give me monitor information about the previous runs of a job.

I can see the job monitor for the latest run. But I wanted to compare the latest set of monitor records with the previous runs.

Is there any way I can achieve this?

Hi Team,

How can I find out the list of tables in uv.

eg. DSJOB, DS_ROUTINES, DS_METADATA

Hi All, Has anyone tried to extract data from Oracle 11g using DataStage 7.5 setup. What could be the possible technical/performance issues that we may encounter? Currently, we are extracting data using DS 7.5.3 from Oracle 10g source system. hwever, source systems are planned to be upgraded to 11g....

There is a batch which is scheduled to run everyday at 5pm.

We are currently running the batch on adhoc at 12pm and its 4pm. We want to unschedule the run for 5PM and continue the currently running instance so that it does not coincide with its scheduled run.

Please help.

ray.wurlod wrote:If the size of the DSX file is now 0 bytes you have managed to empty it of content, probably by using the wrong command in whatever editor you're using.

We have just replaced the read only = 1 field wherever present to read only = 0.

Agreed modifying the dsx is not a recommended approach to make the dsx writeable. But i am unaware of any other approach. Can you please suggest what needs to be done to make the dsx writeable. If I am directly importing the code without making any changes to read-only parameter what problems can i ...

You are right.. but, Since we are on DataStage 7.5.2 version which has ended support from IBM, dont think we'll get any answer from them other than to upgrade the environment.

As a workaround, we recreated the issue on a different project, where we were able to view the Message IDs. After getting the warnings in the different project, retrieved the appropriate message id. Added to the Message Handler Management and it worked fine. However, the main issue, Add rule to the ...

Hi Craig, It doesnt seem to be an issue with the client, but with the particular proj (eg: ABC) on QA. As I have tried opening message handler with the same client 1) on different env (Test), Opens up fine. 2) Tried opening the handler on a different proj (eg :DEF) on the same QA env. Opens up fine....

Thanks All for your prompt replies. :) What we did was, Since it was a huge export, we replaced all the read-only from '1' to '0'. Do you think this is an incorrect way to make a job writeable. Is there any other way? As a workaround we just imported it without changing the read-only from 1 to 0. Bu...