DSXchange

I am looking for urgent help for impact analysis.
presently We are working on IBM Datastage inforsphere and Quality designnger 11.7
our all jobs are in one database name for example "X" if we want to change the data base name "Y" so
1) what are the steps will involv in this process so that we can import all our existing jobs in that new data base.
2) What would be the impact.

Please help me ASAP I really want expert help on impact analysis.


Thanks.

Hi Rucha.

That's a wide open question, primarily because there are so many different ways that you might specify a "database" in DataStage/QualityStage. How does the team indicate their names in the Jobs?

Are they hard coded strings?
Do you use Job Parameters?
Are they consistent across your entire development team?
Do you use Parameter Sets so that all the Job Parameters are in one place and easily reviewed?
Project level parameters?

These are just rhetorical questions for you to consider, and there are many more, including the dependencies on how you are accessing those databases? Is it via regular Stages/Connectors?

It could be very easy to make the changes, or more difficult, depending on the variables above and probably more. Search the archives here -- there are lots of posts over the years of people manipulating .dsx export files to accomplish what they need, or examining better use of shared assets such as Parameter Sets and Shared Containers. ...and the usage analysis features that exist within the Designer. Chances are, you will need/want a combination of methods to best understand what Jobs need to be updated and how & where.

Ernie

Or if the database name is indeed changing, you could opt to update the pointer to the database on the DataStage server so that the physical database name changes to match the new name, but the database alias keeps the old name, in which case you don't have to change anything else.

I am a very new developer in IBM Datastage and Quality Stage We are using version 11.7.
I will really appreciate help on detail steps on
what would need to change in the DS project and jobs if the database name changed?
We want to create a new database and migrate this database structure, ds project, and All jobs. What changes need to be done?

Please read Ernie's reply up above. The answers are there.

Review both of our answers above very carefully. What I believe qt_ky is referring to is the abstraction that is naturally available with most connectivity solutions.....whereby if DataStage connects to Database01, but now it is Database01A, the underlying connectivity solution can still provide Database01 for DataStage and other applications, but over on the database side, it is really pointing to Database01A. ...to do that, however, means understanding how you are connecting...is it ODBC? JDBC? Native connectivity via the particular database? You will need to have more details and share more information for the participants here to be helpful. What kind of database is it? DB2? Oracle? Teradata? other? (there are many...).

Regarding the other questions above, it is important that you familiarize yourself with how the Databases are being specified. Open some of the Jobs and look for their source stages. What database is it? When you edit it, how is the database name (or server name in some of the Stages/Connectors) specified? Do you see a hard coded string such as "Database01" from the example above?

...or do you see something like #myDatabase# ? ....or other perhaps more complex string that with dots and dollar signs? These are all ways of specifying Job Parameters.

Basically --- you need to get to know your environment and the current condition of your DataStage Jobs. It sounds like you may have inherited these Jobs from other teams. That's ok -- but you will have to dig into them a bit further.

In a perfect world, the prior team used 100% parameter sets and project level variables and you might only need to change one item (or resolve with the connectivity solution also noted)....

Some sites use best practices always --- others.....well.....not so much.

We are here to help, but it is going to need you to provide more input and more investigation of your existing library of DataStage resources.

Ernie