Re: SSIS package Informix to SS 2005

I am using Avaya Openlink driver 4.2 and after much trial and error I have
been able to connect to the database and import data into SQL Server 2005. I
had trouble with scheduling a package but overcame this when I saved the
package using Server storage and created a proxy account to run under. I
have occassionally had problems with specific fields which caused the package
to fail so I reverted to Access for thos tables. I am receiving error
OXC020901c. If anyone knows how to fix that I'd appreciate the help. I
found an article about changing the registry when you get this error message
when trying to import Excel spreadsheets but I can't find anything on
informix.

"Phani" wrote:

Can anybody suggest me or explain how we can overcome the requirement like
picking data from ODBC and pushing it to SS 2005 Database through SSIS
package...

Thanks in advance..Request you to help me out...

Solution is appriciated...

Regards,
K.Phanish

"technical.support@xxxxxxxxxxxxxx" wrote:

On Sep 30, 7:20 pm, Scott Anderson <Scott
Ander...@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
Gary,

How can you call the ODBC access viaSSIS, Access, Excel, etc. illegal?
This is the whole purpose of ODBC access into the CMS database. The idea is
to enhance meager reporting capabilities of Avaya's CMS system by utilizing
another reporting package (in this example, it's probably MS Reporting
Services).

Our company also uses Avaya CMS, and we've had numerous problems with
ACSAUTO scripts failing randomly. Therefore, we have moved to using the ODBC
system to export data from CMS into SQL Server. I'm actually encountering
the same problem as Sheldon.

I understand if your Native OLE DB adapter for OpenLink ODBC is licensed
separately. I also understand that OEM OpenLink software from Avaya does not
provide this license. What I don't understand is how extracting your own
data from a CMSInformixdatabase utilizing the software provided by Avaya
for specifically this purpose is in violation of any license agreement.
Please explain.

Isn't the whole point of the Avaya CMS ODBC access system so you can extract
data from the database? Furthermore, I'm unaware of any Avaya-provided
software that actually utilizes the ODBC connection in the way you outline
above (excepting demo applications that are actually created by OpenLink)..

Thanks,

Scott Anderson

"OpenLink Technical Support" wrote:
Hi Sheldon,

First, I feel the need to explain the situation --

You are using Avaya CMS and, along with it, an OEMed version of the OpenLink
Multi-tier ODBC Driver forInformix.

As I said this is an OEMed product and as such comes with restrictions --

i) It is licensed solely for use with Avaya's CMS application and
therefore your use of it with any other ODBC client application is in breach
of this license agreement and therefore illegal.

That is - if you are using the driver viaSSIS, Access, Excel, etc,
etc, or any other non-Avaya CMS ODBC application then you are using the
driver illegally.

ii) Avaya themselves are your point of contact for technical support for
this product.

OpenLink would be more than happy to assist but this would require you to
evaluate and purchase a non-OEMed version of the driver with the license
restrictions (above) removed.

In order to proceed down this route you should contact sa...@xxxxxxxxxxxxxxx

Second, the missing license you refer to is oledb_lt.lic which is a license
for the OpenLink Single-tier OLE DB Provider for ODBC.

Since this OLE DB Provider is not OEMed to Avaya and is a totally separate
product to the Multi-tier ODBC Driver forInformixit therefore requires its
own license file.

Once again you should contact sa...@xxxxxxxxxxxxxx if you need further
clarification.

Regards,

Garry M. Biggs
Technical Support
OpenLink Software
http://www.openlinksw.com
Product Weblogs:
Virtuoso:http://www.openlinksw.com/weblogs/virtuoso
UDA:http://www.openlinksw.com/weblogs/uda
Universal Data Access & Virtual Database Technology

"Sheldon" wrote:

Hello -

We are running Sql Server 2005 in a Windows Server 2003 environment.

I have been unable to create anSSISpackage to copy four tables from an
Informixdatabase; nor am I able to manually import from this DB. This is a
DB created by Avaya and they gave me an OpenLink ODBC driver which does not
work for this. I keep getting a licensing error complaining about not having
an ole license. I have contacted both OpenLink and Avaya on numerous
occasions and have run into a bunch of morons.

I can, however create a connection and see all of the tables in BIDS. I can
also import the tables into Access. I need to delete the tables and
re-import them daily. Any suggestions on how to do this will be greatly
appreciated!

(Also, I'm curious that the only DB sources are DataReader, Excel, Flat
File, OLE DB, Raw File and XML. I don't quite understand why BIDS doesn't
have an ODBC DB Source.)

Again, any help will be greatly appreciated!
--
Sheldon
Hi all,

Ok, I feel the need to clarify my initial response ----

Basically, the licensing restriction I spoke of is an application
specific restriction.

That is, Avaya have OEMed the OpenLink Multi-tier ODBC Driver for
Informix exclusively for use with their CMS application (the CMS
application being the application that puts the data into the Informix
database in the first place).

So - what is required is a fully licensed version of the ODBC Driver
purchased through OpenLink Software.

It is only a fully licensed version of the driver that is permitted to
be used with non-Avaya CMS ODBC applications such as SSIS, Access,
Excel, etc

I guess this was a commercial decision made by Avaya at the time
contracts for OEMing the driver were drawn up.


At no point did I said "ODBC access via SSIS, Access, Excel, etc was
illegal".

What I *did* said is - "ODBC access via SSIS, Access, Excel, etc
through the OpenLink Multi-tier ODBC Driver for Informix that is OEMed
to Avaya is illegal.


I hope this clears things up.


Regards,

Garry M. Biggs
Technical Support
OpenLink Software
http://www.openlinksw.com
Product Weblogs:
Virtuoso: http://www.openlinksw.com/weblogs/virtuoso
UDA: http://www.openlinksw.com/weblogs/uda

.