DataStage 11.3.1 Unable to connect to project dstage1

JayanK · Post by **JayanK** » Wed Jan 14, 2015 11:15 pm

Hi all,

This is a new installation of DataStage 11.3.1 and received the following message while trying to connect to the project dstage

-------------------------------------------------------------------------------
Error message:
-------------------------------------------------------------------------------
Failed to find an entry for the DataStage server (xx.xxx.xx.xxx) and project (dstage1) in the repository

The Project 'dstage1' cannot be found in the repository
--------------------------------------------------------------------------------

Apart from that under administrator client, the projects are listed as broken:
dstage(broken)

For you information:
This new installation is on a server with the same hostname as the existing 9.1 version but has an alias name.

Thank you and appreciate all your responses.

cheers,
Jayan

PaulVL · Post by **PaulVL** » Thu Jan 15, 2015 8:31 am

Can you explain what you mean by Alias Name?

You need to specify the different port that the version 11 is listening on. You need to source that DSENV, you need to tweek /.dshome for each version. There are other posts regarding tips and tricks on installing multiple versions of the product on the same server.

Start debugging with simple commands like "dsjob -listprojects" you will most likely have to add the domain and port to it. Using an authfile for each version is a good idea.

JayanK · Post by **JayanK** » Thu Jan 15, 2015 5:24 pm

The new 11.3 installations are on new servers ( Server_A - Engine Tier, Server_B - Service & Repository Tier) , its not a side by side installation.

These new servers are on the same network as the 9.1 versions. Because there will be hostname conflicts they have been given server alias names as Server_A2, Server_B2. Is it necessary to have the same hostnames for the purpose of migration?

Steps Followed:
1. Checked all OS requirement installed library files and updated kernels.
2. Created user id's and groups
3. Installed repository and service tier on Server_B2. Installation was successful.
4. Installed engine tier on Server_A2. Installation was successful.
5. Logged into the console to map the engine credentials. Unable to see the engine being listed here.

Also while installation of the engine tier in the wizard page where we have to provide the service tier information i have specified the Server_B details and port 9443 appears as default instead of port 9080. Not sure if this will be an issue.

Thank you. Appreciate your responses.

JRodriguez · Post by **JRodriguez** » Fri Jan 16, 2015 8:18 pm

On 11.3.1 only https connections are allowed to the services tier, that's why the default port 9443. Have you added the security certificate for the clients? If not then below link explains step by step how to and more
http://www-01.ibm.com/support/knowledge ... _dsqs.html

http://www-01.ibm.com/support/knowledge ... JPZ_11.3.0

JayanK · Post by **JayanK** » Wed Feb 04, 2015 5:09 pm

Thanks JRodriguez. Yes I have added the security certificate to the clients as well.

The issue was solved by simply restarting the services and both the Service and Engine Tiers.

Thank you all.