SQL Server 2005 (64 bit) returns truncated text from Oracle 10g (64 bit)

Hi all,
I'm no expert in Oracle so I desperately need your advice.
I'm using SQL Server 2005 (64 bit) and trying to pull data from a Oracle 10g (64 bit) server. I am able to connect to the Oracle server with no problems.
The problem came when I was trying to pull a text column (I think it's BLOB in Oracle) from the Oracle server. The results came back BUT truncated to only 100 characters. (This is a column containing event logs so the text is really really long...)
As you may already know, Microsoft is not providing the driver for this case (which is insanely ridiculous!!!). There is no standard “Microsoft OLE DB Provider for Oracle” which we would normally use to establish a linked server connection to Oracle. Instead, we had to install the provider given by Oracle (Oracle Provider for OLE DB).
I have tried to Google for solutions but didn't find much. Please help! :(
Thanks in advance,
Eleni

If this is a one time activity, you need to find a migration utility which will do the job for you. SQL Developer is available had your case been the other way round (migrate from SQL Server to Oracle).
Check out tools from SwisSQL
http://www.swissql.com/products/oracle-to-sqlserver/oracle-to-sql-server.html
Microsoft's own SSMA (I think this is what you are using already)
http://www.microsoft.com/sqlserver/2005/en/us/migration-oracle.aspx
Apart from this, if there are any issues with the tools themselves, you need to get in touch with the respective vendors.

Similar Messages

SQL Server 2005 Migration Q's

Ok so I have a SQL Server 2005 database and have migrated it to Oracle 10g Rev 2..
All the text fields are right padded :( how do I stop the extra padding on the text fields is there a flag or something ?
thanks

What are the column types in SQL Server and in Oracle?
CHAR types are always padded to their full length with spaces whereas VARCHAR types only store what is actually there.

Reading BLOB from SQL Server 2005 using DB Link from Oracle 10g

Hi All,
I am trying to read a table's data from SQL Server 2005 using ODBC DB Link created in Oracle 10g (10.2.0.3/4) database. I am not using oracle gateway.
I am able read all data except for the BLOB data from SQL server 2005. It gives error given below when I try to execute query SELECT * from T_TRANSACTION_DATA@sdeslink inside a stored procedure:
ORA-22992: cannot use LOB locators selected from remote tables
Kindly help how to read BLOB from SQL server 2005 inside Oracle 10g.
Best Regards!
Irfan

Irfan,
If you can read the blob data using 10.2 HSODBC then there should be no problem using the 11g gateway.
I recommend you download the latest version which is 11.2.0.3 available from My oracle Support as -
Patch 10404530: 11.2.0.3.0 PATCH SET FOR ORACLE DATABASE SERVER
This is a full version and does not need a previous version to have bene installed. When installing it needs to be in a completlely separate ORACLE_HOME from the existing 11.2 install.
For the Ora-22992 problem have a look at this note in My Oracle Support -
Ora-22992 has a workaround in 10gR2 (Doc ID 436707.1)
Regards,
Mike

OraOledb, Linked Servers and SQL Server 2005 issues

Some issues I've come across when using SQL Server 2005 (and SQL Server Express 2005), the OraOLEDB provider (10.2.0.1) and a linked Oracle database (8.1.7.4.0 64-bit)
1) You must set the OraOledb.Oracle\AllowInProcess value to 1 to allow the OraOledb provider to run in SQL Server's process. Without doing this I receive an 'unspecified error' from the OLE DB provider when attempting to run a query
2) When running a ' select * ' query across a linked server using the provider, I receive the following error: Msg 9803, Level 16, State 1, Line 1
Invalid data for type "numeric". I can, however, select all of the columns by name and the query completes (no error). Sometimes the 'select *' query returns a few rows before the error, sometimes it doesn't. The Microsoft Provider for Oracle does not have this problem

Okay... I've got a Win2K3 Std Ed server (x64) running 64-bit SQL Server 2005 Enterprise Edition. I've installed the Oracle 10g 10.2.1 full client and admin tools, added two named services via the NetConfig assistant, and successfully set up (and tested) a connection via the ODBC Administrator to an Oracle database.
Now... when I try to create a new connection manager in SQL Server 2005 Integration Services, the OLEDB provider for Oracle can't be found, and when I try to manually add an underlying OLEDB connection to the database, SQL Server reports:
Test connection failed because of an error in initializing provider. The 'OraOLEDB.Oracle.1' provider is not registered on the local machine.
Does anyone know what I need to do to see my ODBC Server data connections in SQL Server 2005 (64 bit)? I don't have this issue on my 32-bit SQL Server 2005 servers.

Oracle 10g to sql server 2005 - how to setup

Hi,
I have been searching on how to setup a connection from oracle 10g to sql server 2005 and i have to admit i am struggling a bit.
I have read about Heterogeneous Services and Database Gateway but we really dont want to fork for licence fees so it looks like i have to investigate HS.
My environment is:
10gR2 Linux 32 bit
SQL Server 2005 32bit.
Would someone be able to provide me with a list of steps to help me get this setup?
Thanks.
B

Hi,
If you don't want to pay for any licence fees then you will have to use the 11g Database Gateway for ODBC (DG4ODBC) which is included in your RDBMS license.
You need to use the 11g versions because all previous gateway versions have been desupported for some time. The latest version is 11.2.0.3 which can be downloaded from My Oracle Support as -
Patch 10404530: 11.2.0.3.0 PATCH SET FOR ORACLE DATABASE SERVER
and download -
p10404530_112030_platform_5of7.zip
- this is the Gateway media pack and has everything needed for a standalone gateway install.
This version is certified the following RDBMS versions - 10.1.0.5 + RDBMS patch 5965763, 10.2.0.3 + RDBMS patch 5965763, 10.2.0.4, 10.2.0.5, all 11.1 versions, all 11.2 versions.
You have 2 choices about where you can install it and it would be better to install the gateway into a new and separate ORACLE_HOME from any existing Oracle installs -
1. On the Linux 32-bit platform where the RDBMS is running. If you install it here you will need to supply a third party ODBC driver. The only free one I am aware of is from FreeTDS but there may be others. There can be problems with the FreeTDS so another one may be preferable but these usually require a license fee.
See this note in My Oracle Support -
How to Configure DG4ODBC on Linux x86 32bit or on HP-UX RISC (DG4ODBC 11.1 only) to Connect to Non-Oracle Databases post install (Doc ID 466228.1)
2. Install DG4ODBC on the Windows platform where SQL*Server is running. If you install on Windows then you will be able to use the Microsoft SQL*Server ODBC driver which should already be installed. See this note on My Oracle Support -
How to Setup DG4ODBC (Oracle Database Gateway for ODBC) on Windows 32bit (Doc ID 466225.1)
If you don't have access to My Oracle Support you will need to contact someone in your organisation to access the notes for you or review the gateway documentation -
http://www.oracle.com/pls/db112/homepage
Regards,
Mike

Error"Failed to open the connection" - Named Instance of SQL Server 2005

"Failed to open the connection" error, when connecting to the Named Instance of SQL Server 2005
The report is throwing error, when changing the logon information dynamically through C#.
Code
     string reportPath = @"D:\NET\TestReport\TestReport.rpt";
     ReportDocument reportDocument = new ReportDocument();
     reportDocument.Load(reportPath);
     foreach(CrystalDecisions.CrystalReports.Engine.Table table in tables)
          TableLogOnInfo tableLogonInfo = table.LogOnInfo;
          tableLogonInfo.ConnectionInfo.ServerName = @"TestServer\Instance1"; //Connnecting to Named instance of SQL Server 2005
          tableLogonInfo.ConnectionInfo.UserID = "sa";
          tableLogonInfo.ConnectionInfo.Password = "password";
          tableLogonInfo.ConnectionInfo.DatabaseName = "TEST_DB";
          table.ApplyLogOnInfo(tableLogonInfo);
     crystalReportViewer1.ReportSource = reportDocument;
Error Message
     Failed to open the connection.
     Failed to open the connection.
     C:\DOCUME1\PUGALE1\LOCALS~1\Temp\{DF9593A5-5C80-4CBC-ABC3-EC4EF204A7EB}.rpt
The error is occuring only whenever i am connecting to the Named Instance of SQL Server 2005.
Thanks in Advance
Edited by: pugalendran p on Feb 2, 2009 10:32 AM
Edited by: pugalendran p on Feb 2, 2009 10:43 AM

Hi,
Following solution might help you to resolve the issue.
Solution1:
Issue happens because universe connection to the Database is not responding and the Data Source Name is not configured to write SQL Server 2005 database.
Resolution
Created new DSN connection under SYSTEM DSN to SQL Server 2005 Database.
Import the universe from the designer.
Go to File->Parameters.
Edit Connection.
On the Database Middleware Page expand SQl Server 2005->Select SQL Server 2005 driver.
Change the DSN to new DSN connection
Test the connection.
Save the Universe and Export it to the repository.
Solution2:
I am taking Oracle as an example over here.
This can be caused when the SQLNET.ora is located in a remote location using mapped drives.
Resolution
To resolve,
check the registry [HKLM\SOFTWARE\ORACLE] you should see a folder called HOME0
look for any paths that contain a mapped drive partition
Change the mapped drive letter to a UNC path (
server\folder)
Open a command prompt and do a tnsping using the tnsname and verify the location of the SQLNET.ora or TNSNAMES.ora
If the path is not updated to the new path
Reboot the server
Regards,
Sarbhjeet Kaur

Error in adding PRIMARY Data file of SQL Server 2005

Hi Experts,
I am using SQL 2005 as back end database for SAP ECC6. Due to Space problem in PRD data volume, i have added PRDDATA4.ndf file in SSMS ( SQL Server Management Studio) and saved. But, suddenly i got one more idea and extended the file size of exisiting PRDDATA1.mdf, PRDDATA2.ndf & PRDDATA3.ndf immediately i removed the PRDDATA4.ndf file before starting the service. But, while seeing in SAP using ST04 it showing the PRDDATA4.ndf with error message of file missing. What i have to do now? How can i delete the information showing in ST04. But it is not showing in SSMS.
Please help how to solve this.
Regards,
B.Sudharsan

Hi,
Following solution might help you to resolve the issue.
Solution1:
Issue happens because universe connection to the Database is not responding and the Data Source Name is not configured to write SQL Server 2005 database.
Resolution
Created new DSN connection under SYSTEM DSN to SQL Server 2005 Database.
Import the universe from the designer.
Go to File->Parameters.
Edit Connection.
On the Database Middleware Page expand SQl Server 2005->Select SQL Server 2005 driver.
Change the DSN to new DSN connection
Test the connection.
Save the Universe and Export it to the repository.
Solution2:
I am taking Oracle as an example over here.
This can be caused when the SQLNET.ora is located in a remote location using mapped drives.
Resolution
To resolve,
check the registry [HKLM\SOFTWARE\ORACLE] you should see a folder called HOME0
look for any paths that contain a mapped drive partition
Change the mapped drive letter to a UNC path (
server\folder)
Open a command prompt and do a tnsping using the tnsname and verify the location of the SQLNET.ora or TNSNAMES.ora
If the path is not updated to the new path
Reboot the server
Regards,
Sarbhjeet Kaur

I can't link to an I series (IBM AS400) server from my sql server 2014 server (64 bit) -- but yes can link on sql server 2005 (32 bit)

I have an I series (IBM AS400) server linked "OK" to a sql 2005 sql server (32 big). I copied the link script (but changed credentials) from the sql server 2005 link and attempted to run it in the sql server 2014 server (on win 7 64
bit). There are no complaints from SSMS when I run the script, but when I try to query a table I get this error message:
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
Msg 7303, Level 16, State 1, Line 11
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
Here is the script (from the sql server 2005 (32 bit)) I ran on the sql server 2014 SSMS -- is there anything I need to change? How can I get this I series server to link to my sql server 2014 server?
USE [master]
GO
/****** Object: LinkedServer [CWMPDTA] Script Date: 9/25/2014 10:39:12 AM ******/
EXEC master.dbo.sp_addlinkedserver @server = N'CWMPDTA', @srvproduct=N'cwmpdta', @provider=N'MSDASQL', @datasrc=N'iseries2', @provstr=N'Provider=IBMDA400.DataSource.1;Password=myPwrd;Persist Security Info=True;User ID=myID;Data Source=10.0.0.51;Initial Catalog=T9S', @catalog=N'T9S'
/* For security reasons the linked server remote logins password is changed with ######## */
EXEC master.dbo.sp_addlinkedsrvlogin @rmtsrvname=N'CWMPDTA',@useself=N'False',@locallogin=NULL,@rmtuser=N'myID',@rmtpassword='myPwrd'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation compatible', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'data access', @optvalue=N'true'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'dist', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'pub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'rpc out', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'sub', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'connect timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'collation name', @optvalue=null
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'lazy schema validation', @optvalue=N'false'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'query timeout', @optvalue=N'0'
GO
EXEC master.dbo.sp_serveroption @server=N'CWMPDTA', @optname=N'use remote collation', @optvalue=N'true'
GO
Rich P

Thank you for this reply. I went to the link and selected the option for DB2s and ran the install. Then I started up SSMS. I copied the same script as above, and it executed successfully. But when I try to run a query against
a table in a database on this linked sever -- I get this error message:
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed".
OLE DB provider "MSDASQL" for linked server "CWMPDTA" returned message "[IBM][System i Access ODBC Driver]Key value in connection string too long.".
Msg 7303, Level 16, State 1, Line 8
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "CWMPDTA".
Do I need to change the line containing -- @provider=N'MSDASQL', maybe?
this is the query I'm running:
select TOP 10 * from CWMPDTA.T9S.CWMPDTA.INSKU
The same exact query runs fine on the sql server 2005 linked server. Is there something I need to configure?
Rich P

SQL Server 2005 64-bit & SQL CLR Stored Procedures using DI API. COM Error.

Hi,
We've created a set of SQL CLR Stored Procs in C# .NET which use the DI API to import data into SAP (DEV was carried out on 32-bit environment).
The DLLs and Interop.SAPbobsCOM have been successfully deployed as assemblies on SQL Server with their permission set to UNSAFE on the following environment:
Microsoft Windows Server 2003 R2 Standard Edition 64-bit, Service Pack 2
Microsoft SQL Server 2005 - 9.00.3073.00 (X64)
SAP Business One 2007 A (8.00.180) SP:00 PL:45
When executing the SQL CLR Stored Procs from SQL Server Management Studio, the following error is returned:
"Retrieving the COM class factory for component with CLSID {632F4591-AA62-4219-8FB6-22BCF5F62007} failed due to the following error: 80040154."
From our understanding, this occurs because SQL Server loads the assemblies into it's 64-bit process space, whereas the SAPbobsCOM is 32-bit. Are we assuming correctly?
What can be done to solve this problem?

Hi Jeremy,
I'd agree with your assumption that it's to do with your DLL running in a 64 bit process. When you build your project, try setting the build properties to use a X86 instruction set (ie 32 bit).
More details here:
Re: Addon Develeped on 32bit Install on 64bit
I've never tried for a CLR stored procedure but this is how you get around the issue when running a DI API addon on a 64 bit machine so hopefully it will work if the dll is executed by SQL Server. Let us know how you get on.
Kind Regards,
Owen

SQL Server 2005 64 bit and Oracle 9

Hi,
I have a situation which involves SQL Server 2005 64 bit and Oracle 9 32 bit,
I have a requirement that involves creating Stored Procedures from Oracle 9 which will call tables from SQL Server 2005 64 bit, with operations involving 'Select' 'Insert' 'Update' and 'Delete'.
it works fins, except when attempting to search for an SQL Server 'varchar' value, wher no mapping is done
though the Oracle sees the field as 'varchar2'
can anyone please advice on this
thanks
Basel

I think you're somehow not getting a resuklt because you're query doesn't return any data.
Why the fiealdA=pat=parameterA construct? Wouldn't it just work if you changed it to fieldA=parameterA?
Also, can you not just define parameterA as a varchar to make them match?
What if you do "select * from (<your query without where>) a where a.fieldA = :parameterA"
While not efficient, it would make the filtering occur in Oracle and maybe that will let you see the problem in native Oracle land and then reuse the solution in your orginal query. If that doesn't work, drop the where clause and inspect the data closly and hardcode a simple where without using PL*SQL or bind variables.

Error 1406 while installing SQL server 2005 on windows 2003 64 bit standard

Hi Gurus,
When I am trying to install SQL SERVER 2005 on Windows Serevr 2005 i get the error code 1406
I tried using the script sql4sap.vbs. and tried to set the named instance.
please suggest
Please find the contents of the Summary.txt
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version      : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time            : Mon Apr 14 14:51:07 2008
Machine         : UKSAPTEST02
Product         : .NET Framework 2.0
Product Version : 2.0.50727
Install         : Failed
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST02_.NET Framework 2.0.log
Last Action     : InstallFinalize
Error String    :Could not write value to key \Software\Classes\.appref-ms
Error Number    : 1406
UKSAPTEST02 : There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.
SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.
Time            : Mon Apr 14 14:52:26 2008
List of log files:
     C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST02_Core.log
Many thanks
Sreeram
Edited by: sreeram kaki on Apr 14, 2008 6:12 PM

Hi Clas,
Thanks for the valuable suggestions,
I tried to install the database (sql server 2005) using the local admin password on another server which do not have the antivirus installed. I started the installation at 3:15 PM today and the installation is still in progerss
please see the log below from Summary.txt.
Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version      : Microsoft Windows Server 2003 family, Standard Edition Service Pack 2 (Build 3790)
Time            : Tue Apr 15 15:04:28 2008
Machine         : UKSAPTEST01
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLSupport_1.log
Machine         : UKSAPTEST01
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLNCLI_1.log
Machine         : UKSAPTEST01
Product         : Microsoft SQL Server VSS Writer
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SqlWriter_1.log
Machine         : UKSAPTEST01
Product         : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_MSXML6_1.log
Machine         : UKSAPTEST01
Product         : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLSupport_2.log
Machine         : UKSAPTEST01
Product         : Microsoft SQL Server Native Client
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_SQLNCLI_2.log
Machine         : UKSAPTEST01
Product         : Microsoft SQL Server 2005 Books Online (English)
Product Version : 9.00.1399.06
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_BOL_1.log
Machine         : UKSAPTEST01
Product         : MSXML 6.0 Parser
Product Version : 6.00.3883.8
Install         : Successful
Log File        : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_UKSAPTEST01_MSXML6_2.log
Also see the last few lines of the log file
SQLSetup0001_UKSAPTEST01_SQL.log
Action start 17:10:43: Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!50) [17:10:43:815]: PROPERTY CHANGE: Deleting Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '1 0 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
Action ended 17:10:43: Rollback_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<Func Name='ScheduleActionX'>
<Func Name='SetCAContext'>
MSI (s) (C0!50) [17:10:43:815]: PROPERTY CHANGE: Adding Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its value is '1 1 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
MSI (s) (C0!50) [17:10:43:815]: Doing action: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Action start 17:10:43: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!50) [17:10:43:830]: PROPERTY CHANGE: Deleting Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '1 1 0 Installing Local Groups 50000 SQLServer2005MSFTEUser$UKSAPTEST01$RDE NT AUTHORITY\SYSTEM '.
Action ended 17:10:43: Do_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<EndFunc Name='Write_sqlGroupMember' Return='0' GetLastError='0'>
PerfTime Stop: Write_sqlGroupMember : Tue Apr 15 17:10:43 2008
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (C0:F0) [17:10:43:830]: Doing action: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
Action ended 17:10:43: Write_sqlGroupMember.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
MSI (s) (C0:50) [17:10:43:830]: Invoking remote custom action. DLL: C:\WINDOWS.0\Installer\MSI1D8.tmp, Entrypoint: Write_sqlUserSecurity
Action start 17:10:43: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
<Func Name='LaunchFunction'>
Function=Write_sqlUserSecurity
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlUserSecurity
PerfTime Start: Write_sqlUserSecurity : Tue Apr 15 17:10:43 2008
<Func Name='Write_sqlUserSecurity'>
<Func Name='ScheduleActionX'>
<Func Name='SetCAContext'>
MSI (s) (C0!34) [17:10:43:924]: PROPERTY CHANGE: Adding Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its value is '0 1 0 Setting User Security 50000 SQLServer2005SQLBrowserUser$UKSAPTEST01 SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeChan
MSI (s) (C0!34) [17:10:43:924]: Doing action: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Action start 17:10:43: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
MSI (s) (C0!34) [17:10:43:924]: PROPERTY CHANGE: Deleting Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B property. Its current value is '0 1 0 Setting User Security 50000 SQLServer2005SQLBrowserUser$UKSAPTEST01 SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005SQLAgentUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeChangeNotifyPrivilege SQLServer2005MSSQLUser$UKSAPTEST01$RDE SeIncreaseQuotaPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeServiceLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeBatchLogonRight SQLServer2005MSFTEUser$UKSAPTEST01$RDE SeAssignPrimaryTokenPrivilege SQLServer2005MSFTEUser$UKSAPTEST01$
Action ended 17:10:43: Do_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
<EndFunc Name='ScheduleActionX' Return='0' GetLastError='0'>
<EndFunc Name='Write_sqlUserSecurity' Return='0' GetLastError='0'>
PerfTime Stop: Write_sqlUserSecurity : Tue Apr 15 17:10:43 2008
<EndFunc Name='LaunchFunction' Return='0' GetLastError='0'>
MSI (s) (C0:F0) [17:10:43:940]: Doing action: Write_sqlFileSDDL.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B
Action ended 17:10:43: Write_sqlUserSecurity.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B. Return value 1.
MSI (s) (C0:10) [17:10:43:940]: Invoking remote custom action. DLL: C:\WINDOWS.0\Installer\MSI1D9.tmp, Entrypoint: Write_sqlFileSDDL
Action start 17:10:43: Write_sqlFileSDDL.3EA9D9BF_D9D2_4023_B2A7_9E2137B2FB1B.
<Func Name='LaunchFunction'>
Function=Write_sqlFileSDDL
<Func Name='SetCAContext'>
<EndFunc Name='SetCAContext' Return='T' GetLastError='0'>
Doing Action: Write_sqlFileSDDL
PerfTime Start: Write_sqlFileSDDL : Tue Apr 15 17:10:43 2008
Thanks & Regards,
Sreeram
Edited by: sreeram kaki on Apr 15, 2008 6:45 PM

OraOledb for 64-bit, Linked Servers and SQL Server 2005 issues

Our environment is : SQL Server 2005, Windows Server 2003, 64-bit and 32-bit operating systems.
Problem on 64-bit operating system box: (32-bit works fine).
I am trying to access Oracle 10g database using linked server from our SQL Server 2005. In case of number fileds i got the following error:
Invalid data for type "numeric".
After going through one of the posting in this forumn i was able to resolve the problem by converting those column values to char while querying and then converting them back to numeric type on SQL server side.
But today i ran into another problem. There is a VARCHAR2 column. I was able to retrieve the data yesterday for that column but today i am getting a blank recordset. If i exclude the colum from the query then i am getting all the rows.
I am querying against a view and it has got a number of columns whose data type is VARCHAR2.
Again the problem is on 64-bit operating system only. We have a 32-bit operating system on which i am able to retrieve the data including this column. I looked at the data and everything looks OK. No funny characters etc.
I tried workarounds like using cast, to_char, checking for nulls etc., Nothing works.
Any help is greately appreciated. Thanks.

Did you find a resolution for this? We have similar problem. Set up a linked server in SQL 2006 to Oracle (running on Windows 64-bit) Linked server works and views I had set up were working but they added some new data in the Oracle test database I am using and now I get errors on one of the views.
Error I am getting on the view is "Cannot initialize the data source object of OLE DB Provider "OraOLDEDB.ORacle" for the linked server"
If I fine tune my queries to find the specific table or view that is at issue, then I get the error "inconsistent metadata for a column"

Linked Server error: Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON' between sql server 2005 32 bit and sql server 2012 64 bit

Hi All,
Here the linked server is created between sql server 2012 64 bit and sql server 2005 32 bit. I am getting the below error when i try to access linked server from third server. I have created linked from Instance 1 to Instance 2. When i access it from
instance 3 i am getting the below error. SPN setting has been done between these 2 servers. Also the option 'Trust the delegate' is enabled for the both the service account.
'Login Failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
Appreciate your quick response.
Vikas.M.S

Hello,
Please read the following resources:
http://www.databasejournal.com/features/mssql/article.php/3696506/Setting-Up-Delegation-for-Linked-Servers.htm
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/ea26de43-4c6b-4991-86d7-e1578f107c92/linked-server-login-failed-for-user-nt-authorityanonymous-logon?forum=sqldataaccess
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

How to access Oracle 8g from SQL Server 2005 SP3 EE 64 Bits ?

Dear All,
How to access Oralce 8g from SQL Server 2005 SP3 EE 64 Bits (liked server).
Best regards,
Miguel Gavinhos

Hi!
For the Oracle version is 8.1.6. what should I install, to access Oracle trought a linked server.
Best regards
Miguel Gavinhos

What Drivers should I use to access SQL Server 2005 SP2 from Windows Server 2008 64 bit

and yes I do know that is an odd scenario so let me explain
I have just joined a project that is "in flight" where the customer is upgrading a LOT of things at the same time
(some Microsoft, some other supplier: some at the OS level, others at server or services levels)
the current step is replacing some services leaving the back end databases as they are
i.e. SQL Server 2005 SP2
a later step will upgrade the backend data bases which may make more work
What we have now runs on Windows Server 2003 32 bit using the OLEDB drivers
version 2000.86.3959.00
What we want must run on Windows Server 2008 64 bit still using the OLEDB option
which version should I download & try to install?

Here are a known list of issues with this configuration with their corresponding workarounds: https://support.microsoft.com/kb/936302/en-us
Satish Kartan www.sqlfood.com

SQL Server 2005 (64 bit) returns truncated text from Oracle 10g (64 bit)

Similar Messages

Maybe you are looking for