I need to setup a linked server on my new sql 2008 R2 server but there is no oracle data provider in providers list of my server and when I'm trying to install oracle client or oracle data provider it's giving me an error saying doesn't support Operating system version 6.1 !!!
please tell me which driver do I have to install and where can I download it from ?
thanks
ok I found the way how to do it which I would explain it here as I think other people may have this problem :
Use the correct and only certified install source from here
Unpack and open a command prompt in the "..\database" directory where the "setup.exe" is located.
Run the following command: setup.exe -ignoreSysprereqs
Wait for the OUI windows and continue with your preferences selections.
When the OUI prerequisites window appear it will come with the following error:
INFO: The user has manually verified 'Checking operating system requirements ...'
INFO: Checking CertifiedVersions
This is a prerequisite condition to test whether the Oracle software is certified on the current O/S.
INFO: Expected result: One of 5.0,5.1,5.2,6.0
Actual Result: 6.1
Check complete. The overall result of this check is: Failed <<<<
Select the checkbox to bypass the error and continue installation
and something else that you have to do before creating the linked server is :
go to sql server management studio
open server objects\linked servers\providers
right click on oraoledb.oracle and the properties
in properties check the box for Allow inprocess.
it's all ready now use oraoledb.oracle to create the linked server .
Related
the cmd execution of registerRExt.exe
I am trying to install RRE(Revolution R Enterprise) v7.5 with RR0 3.2.2(Revolution R Open) on a SQL Server 2016 RC0 default instance. All the steps shown in the https://msdn.microsoft.com/en-us/library/mt590808.aspx have been completed and the error occurs in the Post installation Server configuration scripts. The script has also been replaced by the updated script for RC0 shown on the msdn site but still I get the same error on running the registerRExt.exe file.
The site shows while installing the instance the account name for Server Database engine has to be MSSQLSERVER, however this had also resulted in an error stating wait on database recovery handle failed which was sorted by changing the account name of Database engine to NT AUTHORITY/SYSTEM(I provided this info as it can also be the cause of the problem) . Now I need to sort the user pool failure. Any help would be appreciated..thanks in advance
SQL 2016 RC1 was just released https://blogs.technet.microsoft.com/dataplatforminsider/2016/03/18/sql-server-2016-release-candidate-1-now-available/.
SQL RC1 has a newer version 8.0.1 version of RRE. I suggest your try to install it and reply to this thread again if you hit the same failure. https://msdn.microsoft.com/library/mt590809.aspx has the details on where to find Microsoft R Open 8.0.1 and Revolution R Enterprise 8.0.1.
If the issue persists RevoScaleR\rxLibs\x64\registerrext.log would have more details on the exact failure - do share that.
I was able to sort out the issue..It was because I was installing the SQL server on domain controller and ignored the warning while install, but then changing some rules and demoting it from Server Manager worked and the install was successful.
However I do know there may be some better solution to that as all the other user accounts got reset in the process.
I found out when creating SSIS packages that I need to have this SSIS Service installed in order to schedule them from SQL Server Agent. So with that said I've been trying all over to figure out how to get this service installed without wiping my existing instance.
I've been all over online and no one seems to have the same issues that I'm having or their resolutions aren't helping me out. Here's what I do so far and the wall that I'm hitting:
I go to Start/All Programs/Microsoft SQL Server 2008 R2/Configuration Tools/SQL Server Installation Center (64-bit)
When the console opens I click on Installation and then "New installation or add features to an existing installation"
I then get a pop up that says to "brows for SQL server 2008 R2 Installation media so I point it to my Desktop where the file "SQLManagementStudio_x64_ENU.exe" resides and I get an error that says that my desktop "is not a valid installation folder"
Please help me figure this out, I've been racking my brains for days! The only solutions I've found online for this error are to completely uninstall everything and re-install and that's just not an option.
----- edit -----
I have looked at another link within stack overflow that "may" address my problem.
Add SSIS to existing SQL Server instance
It says that I have to get my hands on the "installation media folder" or download it from Microsoft's website. I can't however find anything on their website besides the "SQLManagementStudio_x64_ENU.exe" file that I was referring to later.
----- edit 2 -----
When I try to just use SQLManagementStudio_x64_ENU.exe I get to the point where I select my instance and get this 'instance id required but missing' error. Here's a screenshot
Don't go via Start/All Programs/Microsoft SQL Server 2008 R2/Configuration Tools/SQL Server Installation Center (64-bit).
Go directly to your installation media "SQLManagementStudio_x64_ENU.exe" file, and run it. It will open same panel, that installation center does, but it will not ask for any installation media, and will take you directly to next step.
Hope you go through successfully.
P.S.: You can't update SQL Server 2008R2 installation with SQL 2008 setup files.
I am trying to attach the AdventureWorks2012_Data.mdf database file to my SQL Server 2012 database.
I am getting this error:
TITLE: Microsoft SQL Server Management Studio
Attach database failed for Server 'USER-PC'. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=11.0.3000.0+((SQL11_PCU_Main).121019-1322+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Attach+database+Server&LinkId=20476
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Unable to open the physical file "C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\AdventureWorksDW2012_log.ldf". Operating system error 2: "2(failed to retrieve text for this error. Reason: 15105)". (Microsoft SQL Server, Error: 5120)
Maybe the message is clear that I don't have the .log file and yes I don't have it. But is it necessary to have it? Or is there is another thing? How can I solve that please?
This is a common error that anyone could encounter when you don't have any *.LDF log file for your database, like the AdventureWorks database. SQL Server complains about the *.LDF log file (typically associated to a database *.MDF file) that is missing.
Execute the following T-SQL query to attach the database considering only the *.MDF file:
USE [master]
GO
CREATE DATABASE [AdventureWorksDW2012] ON
( FILENAME = N'C:\Users\User\Desktop\ARPAD\AdventureWorks2012_Data.mdf' )
FOR ATTACH
GO
or remove the connection to the *.LDF log file (a new *.LDF file will be created for the database) through SQL Server Management Studio as shown in the screenshot below:
UPDATE
You get the error:
The database 'AdventureWorksDW2012' cannot be opened because it is version 706. This server supports version 661 and earlier. A downgrade path is not supported. Could not open new database 'AdventureWorksDW2012'. CREATE DATABASE is aborted. (Microsoft SQL Server, Error: 948)
because you're trying to attach a SQL Server 2012 (version 706) database file to SQL Server 2008 istance (version 661). For this reason, you cannot perform this downgrade. Download the AdventureWorks2008 database for your SQL Server 2008 istance instead, or upgrade your SQL Server istance with the latest version.
The version of your SQL Server istance is indeed SQL Server 2008: Microsoft SQL Server 2008 R2 (RTM) - 10.50.1617.0 (X64) Apr 22 2011 19:23:43 Copyright (c) Microsoft Corporation Express Edition with Advanced Services (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1).
Download and install SQL Server 2012 Express to solve the problem.
The key is this line (edited for clarity):
Unable to open the physical file
"C:\Program Files\Microsoft SQL Server\MSSQL11.MSSQLSERVER\MSSQL\DATA\AdventureWorksDW2012_log.ldf".
Operating system error 2:
"2(failed to retrieve text for this error. Reason: 15105)".
(Microsoft SQL Server, Error: 5120)
According to this page, operating system error 2 is "File Not Found". Based on this, I would guess that either, A) the file is not there , or B) the name or path is misspelled.
(I'm too slow the answer above is what I'm talking about)
FYI This answer assumes your using the attach a database dialog.
Make sure you've told sql manager where the ldf file is too. It will fill in an entry for a log even if you aren't attaching the log with the mdf.
You'll see it in the box below the one with the add button. You can just remove the log from the attach if you don't have it. Sql will make a new log and you can move merrily along the way.
I'm trying to create a database on my local machine using SSMS version 11.0.2100.60. I've run the application as administrator, logged in using Windows authentication, and I've added MYDOMAIN\my-username to the Logins. However if I try to create a db with this login I get the message
CREATE DATABASE permission denied in database 'master'.
(Microsoft SQL Server, Error: 262)
If I try to add the privelage dbcreator to my user, I get the following error.
User does not have permission to perform this action.
(Microsoft SQL Server, Error: 15247)
I can't log in as sa as I don't know/remember the password (is there a preset default?), and if I try to change the password I get the message:
Cannot alter the login 'sa', because it does not exist or you do not have permission.
(Microsoft SQL Server, Error: 15151)
Finally I note that the account 'sa' is disabled, and if I try to enable it I get the same error as before. Is there any way around this or do I need to re-install?
Version info:
Microsoft SQL Server Management Studio 11.0.2100.60
Microsoft Analysis Services Client Tools 11.0.2100.60
Microsoft Data Access Components (MDAC) 6.2.9200.16384
Microsoft MSXML 3.0 4.0 6.0
Microsoft Internet Explorer 9.10.9200.16635
Microsoft .NET Framework 4.0.30319.18051
Operating System 6.2.9200
I found the answer here:
In order to start SQL Server in single-user mode, you can add the
parameter “-m” at the command line. You can also use the SQL Server
Configuration Manager tool, which provides proper controls for the
file access and other privileges. To use the Configuration Manager
tool to recover your system, use the following steps:
Open the Configuration Manager tool from the "SQL Server 2005| Configuration" menu
Stop the SQL Server Instance you need to recover
Navigate to the “Advanced” tab, and in the Properties text box add “;–m” to the end of the list in the “Startup parameters” option
Click the “OK” button and restart the SQL Server Instance
A little more specific :
Open Sql Configuration Manager.
Select SQL Server Services.
On the right hand side, select the instance.
Right click on it and open properties.
In the advanced tab attach ";-m" at the end of the Startup Parameters field.
Apply and restart the service.
Now you have privilege to enable "sa" user and modify its password.
once done, remove ";-m" and restart the service.
You are good to go.
I'd like to point out an alternative answer laid out on DBA SE. Download PSExec onto the box that is having the problem and follow the instructions laid out in this blog post to effortlessly change admin settings using the NT Authority\System account.
./psexec -s -i "C:\...\Ssms.exe"
Wanted to share this solution as it solved my problem!
I've managed to connect my SQL Server 2005 in Windows 64 bit server with ORACLE database. (Thanks to Mr. Jeyong Park :http://knol.google.com/k/jeyong-park/accessing-oracle-data-source-from-64bit/3vywlm4f31xae/12)
The problem is :
In SSIS when I used Oracle as a OLE DB Data Source and previewed the data, it works, however, when I run the Package, the OLE DB Data Source task failed with the message :
[OLE DB Source [10882]] Error: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER.
The AcquireConnection method call to the connection manager "PROD_cm" failed with error code 0xC0202009.
There may be error messages posted before this with more information on why the AcquireConnection method call failed.
Since I can preview the data, I think there's no problem with the connection.
Please help...
When I encountered this problem a year ago with SQL Server 2008 on Windows Server 2003 64-bit the issue was caused by incorrect drivers. What is the version of the Oracle database to which you are connecting? If you are connecting to a 8g or 9i Oracle server, then you need to use the 9i Oracle drivers. If you are connecting to a 10g or better server, then you can use the 11i drivers.
Have you tried running the SSIS package while logged into the server as the SQL Server Agent service account or have you only tested this on your workstation? If it works on your workstation and doesn't work while logged into the server as the service account, then this screams driver issue to me.
Another possible problem is that you tnsnames.ora file may not be correctly setup. The file contents should be something like the below code for the 9.2 drivers. Please note you need to replace , , and with appropriate values.
# tnsnames.ora Network Configuration File: C:\oracle\product\10.2.0\client_1\NETWORK\ADMIN\tnsnames.ora
# Generated by Oracle configuration tools.
<SERVER_NAME> =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = <IP_ADDRESS>)(PORT = <PORT_NUMBER>))
)
(CONNECT_DATA =
(SID = <SERVER_NAME>
(SERVER = DEDICATED)
)
)
One more possible solution. If you can get the linked server connection working and cannot get the data flow to work for some reason, then you could execute a linked server query to pull down the data. I remember doing this for about 6 months when we couldn't get the MYSQL drivers to work with the CTP of SQL Server 2008. Eventually we found the right solution, but this helped us through the short-run period to get up and running.
One of The following should work:
Check the tnsnames.ora file - It should have the connection details to the Oracle DB hat you are trying to connect through your package.
Check if the Oracle DB you are trying to connect to is working. I wasted around two days finding a root cause of the error and later came to know that the Oracle DB was shut down.
Check that the passowrds are intact in the configuration manager/Connection string.
If you have been working for long on the package try closing and opening it again. The