Post reply

Create linked server to Avaya CMS database

  • June 30, 2011 at 7:57 am

    #252761

    Hi!

    I'm trying to create a linked server with an Avaya CMS database.

    I've created a DSN using Openlink ODBC driver and works fine.

    The DSN configuration is:

    Driver: OpenLink Generic ODBC Driver

    Server: xxx.xxx.xxx.xxx:5000

    Domain: Informix 2000

    Database: /cms

    ...,but is impossible to create a linked server.

    In the attachment you can see the linked server creation screen.

    What should I put in every place?

    Is better to use other protocol?

    Thanks!!

  • June 30, 2011 at 8:03 am

    #1346552

    the IBM website has a walk through on using the SSMS GUI to create a linked server;

    does this help?

    https://www-304.ibm.com/support/docview.wss?uid=swg21195578

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • June 30, 2011 at 8:57 am

    #1346598

    Thaks for your reply!

    So, I must install Informix Client SDK in my SQL Server?

    My Local DNS works perfectly with Access, and I have not installed Informix Client SDK !!

  • June 30, 2011 at 9:03 am

    #1346606

    no, if you have already installed the ODBC driver on your server, you don't need any SDK or anything else.

    all you need to do is use the screenshots int hat example as a model for setting up your specific linked server to informix;

    I get a little lost when using the GUI and wondering what values to put in the text fields that allow free test.

    Lowell

    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • July 1, 2011 at 2:45 am

    #1346910

    I'm affraid that is my problem.

    I don't know what is the exact correspondance between DSN parameters and linked server parameters.

    I tried (I think) all combinations, and the linked server is created, but when I try to view in the Enterprise Manager the list of tables the server gets "frozen" (and sometimes I must reboot the server to kill the tasks!!)

  • July 9, 2014 at 11:16 am

    #1728161

    I don't know if the original poster still needs this but I know I would have loved to find this . . .

    I have been hunting down a similar problem for the better part of a two weeks. The bad news is unless you are running a 32 bit version of SQL server such as SQL 2000 a linked server will not work.

    But there is hope! You can create an SSIS package that can connect to Avaya CMS. I'm aware that if you try to make this connection normally when you expand the table names you will see something like "root" "hagent" and the meta data will fail, errors, errors, and more errors. It makes me said this is so simple. . . Going to give credit where credit is due.

    http://help.pragmaticworks.com/dtsxchange/scr/FAQ%20-%20How%20to%20run%20SSIS%20Packages%20using%2032bit%20drivers%20on%2064bit%20machine.htm

    If you don't want to go to the link the answer is that VS studio is running in 64 bit and the 32 bit driver doesn't like it. Right click the project node -> properties -> debugging: Run64BitRunTime from true to false. That's it it makes the SSIS play nice.

    When you setup a job in SQL Sever in the step under the table execution options check the box "User 32 bit runtime."

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply