DB2OLEDB Issue - Possible Bug
Jul 23, 2007
I have several SSIS packages where I am connecting to a DB2 catalog to grab data on a nightly basis. These packages drop/create and reload data from DB2 to both my 2005, 32 bit and 64 bit servers. In the Connection Properties of the packages that reside on my 64 bit server, I am noticing a quirk in setting the password for the DB2 catalog. If I go in and manually type in the password and test the connection, everything is fine. The package will run either right there through Debug Mode, or at the next run time, without any issues. However, as soon as it runs the very next time, the password for the DB2 catalog reverts back to a blank password and the package will fail when it runs the next/second time. I have unchecked the Blank Password box and checked the Allow For Saved Password box on BOTH the Data Link page and the Connection Properties page. But, this does not resolve the issue. It is almost as if it is ignoring the Allow For Saved Password.
The packages are running fine in the 32 bit environment, by the way. I am only experiencing this issue on the 64 bit server.
Thnx in advance, for any suggestions or answers.
Scottye
View 1 Replies
Mar 10, 2000
Anyone knows where I can find and install the above driver.
Trying to use Link Server from SQL 7.0 to access AS400 database using OLE DB option.
Urgent matter... Help!!!!
Have already tried to find and install this driver using SNA Client Software with out any success. SQL 7 does not come with this OLE DB drivers. Any idea where I can get it.
Thank you in advance....
View 1 Replies
View Related
Aug 10, 2007
Hi
I'm using Microsoft DB2 OLE DB Driver to access a DB2 database, and I have a problem when I create an OLE DB Source using a parameterized query. Everytime I push the "Parameters" button, I get this error:
TITLE: Microsoft Visual Studio
------------------------------
Parameters cannot be extracted from the SQL command. The provider might not help to parse parameter information from the command. In that case, use the "SQL command from variable" access mode, in which the entire SQL command is stored in a variable.
------------------------------
ADDITIONAL INFORMATION:
El proveedor no puede derivar la información del parámetro, no se llamó a SetParameterInfo. (Microsoft DB2 OLE DB Provider)
------------------------------
I would really appreciatte any help.
Thanks.
View 5 Replies
View Related
Sep 19, 2006
The Microsoft OLEDB provider for DB2 (DB2OLEDB) is available in the "Feature Pack for SQL Server 2005 €“ April 2006." The installation routine, however, will only install on the enterprise edition or the developer edition. Is the DB2OLEDB provider not available for SQL Server 2005 standard edition?
View 9 Replies
View Related
Mar 22, 2006
I have a simple SSIS package that I want to move data from SQL 2005 to DB2/AS400. In order to use OLEDDB destination, I installed HIS2004 that provides DB2OLEDB support.
For simplicity and testing purpose, I created a connection pointing to a SQL table that contains only one ccolumn "last_name" of type "nvarchar(50)". This is my source, I then created another connection using DB2OLEDB pointing to a table on DB2 that contains only one field "name" of type "GRAPHIC(50)". This is my destination and the connection works fine to DB2 database. When I run the package, it has type conversion error as follows:
[OLE DB Destination [34]] Error: An OLE DB error has occurred. Error code: 0x00040EDA. An OLE DB record is available. Source: "Microsoft DB2 OLE DB Provider" Hresult: 0x80040E07 Description: "Data or literal value could not be converted to the type of the column in the data source, and the provider was unable to determine which columns could not be converted. Data overflow or sign mismatch was not the cause.".
If I manually assign a vaule to the "last_name" using the "Derived Column" task like "Hello John", it just works fine.
Anyone knows what went wrong? Did I miss anything here? Thanks.
As a FYI: DTS works great in moving data from SQL 2000/2005 to DB2.
Your help will be appreciated.
View 2 Replies
View Related
Aug 20, 2007
I have SQL Server 2005 Developer Edition installed on XP Pro sp2 and have not been able to get OLE DB Provider for DB2 Version 1.0 with Service Pack 1 to install. After getting a notice that the install has failed, I get these log files:
=== Logging started at: 2:12:35 PM Monday, August 20, 2007 Build: 7.0.3038.0 Calling process: H:SQL2005DB2OLEDB7Setup.exe === The current user is NORTHGRUMdinsest. Computer name: DICA2ESITE13005 OS Version: 5.1 Build: 2600 Service Pack: 2.0 Suite: 256 Product Type: 1
[2:12:35 PM Info] Command Line: H:SQL2005DB2OLEDB7Setup.exe
[2:12:35 PM Info] Language: 1033
[2:12:59 PM Info] Raw module path: H:SQL2005DB2OLEDB7Setup.exe
[2:12:59 PM Info] Universal module path: H:SQL2005DB2OLEDB7Setup.exe
[2:12:59 PM Info] Current version of msi.dll is: 3.1 build: 4000 platform: 2
[2:12:59 PM Info] Raw module path: H:SQL2005DB2OLEDB7Setup.exe
[2:12:59 PM Info] Universal module path: H:SQL2005DB2OLEDB7Setup.exe === Logging stopped: 2:12:59 PM Monday, August 20, 2007 === === Logging started at: 2:13:00 PM Monday, August 20, 2007 Build: 7.0.3038.0 Calling process: C:DOCUME~1dinsestLOCALS~1TempEBZ34671.tmpSetup.exe === The current user is NORTHGRUMdinsest. Computer name: DICA2ESITE13005 OS Version: 5.1 Build: 2600 Service Pack: 2.0 Suite: 256 Product Type: 1
[2:13:00 PM Info] Command Line: H:SQL2005DB2OLEDB7Setup.exe /Relaunch /RunningFromTemp /SetupXML C:DOCUME~1dinsestLOCALS~1TempEBZ34671.tmpHISDB2_x86.xml
[2:13:00 PM Info] Language: 1033
[2:13:00 PM Info]
[2:13:00 PM Info] Running prehook init function
[2:13:00 PM Info] Entering PreInitHook
[2:13:00 PM Info] Detecting Sql Server 2005 (32bit)
[2:13:00 PM Info] Enumerating Sql Server 2005 instances from SoftwareMicrosoftMicrosoft SQL ServerInstance NamesSQL
[2:13:00 PM Info] Checking SQL version and edition for: SoftwareMicrosoftMicrosoft SQL ServerMSSQL.1Setup
[2:13:00 PM Info] Got Version 9.2.3042.00
[2:13:00 PM Info] Got edition Developer Edition
[2:13:00 PM Info] Done enumerating Sql Server 2005 instances, original hr = 00000000
[2:13:00 PM Info] Done enumerating Sql Server 2005 instances, hr = 00000000
[2:13:00 PM Info] Done detecting Sql Server 2005, hr = 00000000
[2:13:00 PM Info] Detecting existing integration server installations
[2:13:00 PM Info] Integration server is not installed
[2:13:00 PM Info] Done detecting existing integration server installations, hr = 00000000
[2:13:00 PM Info] Leaving PreInitHook (hr = 00000000)
[2:13:00 PM Info] Prehook Init function returned: 0.
[2:13:00 PM Info] Prehook Init function returned the following mode: 0
[2:13:01 PM Info] Product code: {722CAF00-DE6E-4438-82DE-E664B8B6222B}
[2:13:01 PM Info] Product name: Microsoft OLE DB Provider for DB2
[2:13:01 PM Info] Product PIDSKU: BI6-00082
[2:13:01 PM Info] Product Code (MPC): 91197
[2:13:01 PM Info] OEMID:
[2:13:01 PM Info] Product is not already installed.
[2:13:01 PM Info] Successfully opened Msi package: H:SQL2005DB2OLEDB7Msix86HISDB2.msi
[2:13:01 PM Info] Raw module path: C:DOCUME~1dinsestLOCALS~1TempEBZ34671.tmpSetup.exe
[2:13:01 PM Info] Universal module path: C:DOCUME~1dinsestLOCALS~1TempEBZ34671.tmpSetup.exe
[2:13:10 PM Info] Initializing Component Updater ...
[2:13:10 PM Info] Initialized Component Updater
[2:13:10 PM Info] No updates were found on the SUS server to download.
[2:13:14 PM Info] Required platform components:
[2:13:20 PM Info] Initializing Component Updater ...
[2:13:20 PM Info] Initialized Component Updater
[2:13:20 PM Info] No updates were found on the SUS server to download.
[2:13:20 PM Info] Required platform components: (none)
[2:13:20 PM Info] MSI command line: ADDLOCAL=REQUIRED_FEATURE,OLE_DB_PROVIDER_FOR_DB2 INSTALLDIR="C:Program FilesMicrosoft OLE DB Provider for DB2" PIDKEY="R2D433DHG9DQ79WW3DXQ929DY" USERNAME="Northrop Grumman Corporation" COMPANYNAME="NGGN" FILESINUSEERROR=""
[2:13:20 PM Info] MSI command line is ADDLOCAL=REQUIRED_FEATURE,OLE_DB_PROVIDER_FOR_DB2 INSTALLDIR="C:Program FilesMicrosoft OLE DB Provider for DB2" PIDKEY="R2D433DHG9DQ79WW3DXQ929DY" USERNAME="Northrop Grumman Corporation" COMPANYNAME="NGGN" FILESINUSEERROR=""
[2:13:20 PM Info] Detailed Log information for product H:SQL2005DB2OLEDB7Msix86HISDB2.msi is available at DetailedLog
[2:13:20 PM Info] MSI installation returned 2 - The system cannot find the file specified.
[2:13:20 PM Error] Error 0 occurred during MSI installation.
[2:13:20 PM Error]
[2:13:20 PM Error] === Logging stopped: 2:13:25 PM Monday, August 20, 2007 ===
Detailed Log
=== Verbose logging started: 8/20/2007 14:13:20 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: C:DOCUME~1dinsestLOCALS~1TempEBZ34671.tmpSetup.exe ===
MSI (c) (E4C) [14:13:20:343]: Resetting cached policy values
MSI (c) (E4C) [14:13:20:343]: Machine policy value 'Debug' is 0
MSI (c) (E4C) [14:13:20:343]: ******* RunEngine:
******* Product: H:SQL2005DB2OLEDB7Msix86HISDB2.msi
******* Action:
******* CommandLine: **********
MSI (c) (E4C) [14:13:20:343]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (E4C) [14:13:20:343]: Grabbed execution mutex.
MSI (c) (E4C) [14:13:20:359]: Cloaking enabled.
MSI (c) (E4C) [14:13:20:359]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (E4C) [14:13:20:359]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (B88) [14:13:20:374]: Grabbed execution mutex.
MSI (s) (B8:90) [14:13:20:374]: Resetting cached policy values
MSI (s) (B8:90) [14:13:20:374]: Machine policy value 'Debug' is 0
MSI (s) (B8:90) [14:13:20:374]: ******* RunEngine:
******* Product: H:SQL2005DB2OLEDB7Msix86HISDB2.msi
******* Action:
******* CommandLine: **********
MSI (s) (B8:90) [14:13:20:374]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (B8:90) [14:13:20:406]: MainEngineThread is returning 2
MSI (c) (E4C) [14:13:20:421]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (E4C) [14:13:20:421]: MainEngineThread is returning 2
=== Verbose logging stopped: 8/20/2007 14:13:20 ===
Does anyone have an idea as to why the installation is failing?
TIA,
Steve
P.S. Those aren't really smileys, they're actually semicolon Ds but I can't seem to get rid of the cartoon translation, even after checking the "This post contains a code sample" checkbox.
View 1 Replies
View Related
