Page 1 of 1

Unable to connect to a Unidata 6 account

Posted: Fri Sep 24, 2004 4:35 pm
by neusebio
I am using Datastage 7.5 and the new Unidata6 stage. We have Unidata6 running on a HP-UX 11 platform. I ran the MIGRATE.SQL command as well as the Privilege.B command in two accounts --on our production system, accts DEMO and COLLIVE and on our test system, accts DEMO and COLTEST. Usually the data is COLLIVE and COLTEST is accessed through an application by Datatel called Colleague. If I go to the DataStage Manager, I have no problem connecting to either of the DEMO accounts. I never had a problem before we changed to Unidata 6. We have checked permissions, spent countless hours on the phone with Ascential and I still can't connect to these accounts.

All I get is the "DSUCITables:Sqlconnect - Unable to connect to database" error. It is acting like a giant door is being slammed shut every time Datastage tries to connect to these accounts. Even trying to access these accounts through Telnet, I'm blocked. It won't even give me a login and password prompt.

:shock:

Posted: Fri Sep 24, 2004 6:03 pm
by ray.wurlod
Welcome aboard! :D

That telnet connections are also refused suggests that the problem is somewhere in UniData configuration rather than in DataStage.

Is the unirpcd daemon running on the UniData server? Is it listening on the correct port number (31438)? Is UniData running on UNIX or Windows? It is VERY odd if you can't get a telnet connection to a UNIX machine, but on Windows it might be that the U2 telnet service had not been started.

DataStage is, as I understand it, using the UCI to connect to UniData, not telnet.

Get IBM support to help you to resolve the inability to connect via telnet, and I suspect you'll have resolved the DataStage difficulty too.

Incidentally, are you using "regular" UniData, or schemas generated using VSG? If the latter, you could possibly try connecting via ODBC. Of course, you would need to have a UNIX-based ODBC driver for U2 installed on the DataStage machine. But you could test from a Windows client on which your UniODBC client had been installed.