My computer's operating system is Windows 7 64-bit. I just downloaded and install Oracle Express 11g Windows 64-bit. During installation it ask me to set password for both the SYS and the SYSTEM database accounts which I provide as P#ssword1. Everything went ok during installation.
Now I want to connect using SQL Plus. So I click on All Programs --> Oracle Database 11g Express Edition --> Run SQL Command Line to open SQL Plus.
There I type in connect system/P#ssword1 and press Enter key. But I get this error message: ORA-12154: TNS:could not resolve the connect identifier specified
SQL*Plus: Release 11.2.0.2.0 Production on Wed Jan 18 22:19:11 2017
Copyright (c) 1982, 2014, Oracle. All rights reserved.
SQL> connect system/P#ssword1 ERROR: ORA-12154: TNS:could not resolve
the connect identifier specified
SQL>
Why I cannot connect?
Thanks
Since you are using P#ssword1 as the password
Can you try the following for connecting to DB instance through SQL*PLUS?
connect system/"P#ssword1"
The reason for Oracle to throw the error is that it treats ssword1 (P#ssword1) as the connect identifier.
Related
I am trying to enable file stream on Microsoft SQL Server 2017, on a Windows Core 2019 Server.
I have changed the registry settings at the following location to enable it as there is no GUI. I set the value to 3
ServerName\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL14.InstanceName\MSSQLServer\Filestream.EnabledLevel
After This I restarted
I have also installed the latest Cumulative update (20) as I know there where issues with Driver signing.
After This I restarted
I am seeting the following Errors in the log file at C:\Program Files\Microsoft SQL Server\MSSQL14.InstanceName\MSSQL\Log
<{781FAE78-09AB-4EE5-B051-67747BDB19E3}>RsFxMgmtInitialize failed (the RsFx device is not found. Check if RsFx driver is started.): Error 0x80070002 (-2147024894)
2020-04-21 08:56:03.94 spid5s FILESTREAM: failed to connect to kernel driver RsFx0503.
<{1038F43D-3391-45F7-B1B3-BADF26459429}>Failed to initialize CFsaShareFilter: Error 0x80070002 (-2147024894)
<{1038F43D-3391-45F7-B1B3-BADF26459429}>Failed to initialize CFsaShareFilter: Error 0x80070002 (-2147024894)
2020-04-21 08:56:03.94 spid5s FILESTREAM: effective level = 0, configured level = 2.
2020-04-21 08:56:03.94 spid5s FILESTREAM feature could not be initialized. The operating system Administrator must enable FILESTREAM on the instance using Configuration Manager.
SELECT ##VERSION
Microsoft SQL Server 2017 (RTM-CU20) (KB4541283) - 14.0.3294.2 (X64) Mar 13 2020 14:53:45 Copyright (C) 2017 Microsoft Corporation Standard Edition (64-bit) on Windows Server 2019 Standard 10.0 <X64> (Build 17763: ) (Hypervisor)
I got this working on one server and cannot get it working on the second one.
There is also a version of sql 2019 on this box
Any help? Also any advice on getting this working on a cluster
I used "computer management" and remotly connect to your core server. From there, you can enable FileStream and configure it.
This seemed to work better that the registry method
I'm having the following issue:
I have an SSIS package that connects to an oracle DB using Attunity Connection Manager.
It does connect in my local pc (to a remote oracle db server) and extracts and all, seems to work.
The problem comes when I load it to SQL server to be run as a Job.
I have ran other jobs so the setup is proper, set to run with 32 bit runtime, loading as a file system type.
but when I try to execute the job it gives the following error:
Executed as user: username. Microsoft (R) SQL Server Execute Package
Utility Version 12.0.2548.0 for 32-bit Copyright (C) Microsoft
Corporation. All rights reserved. Started: 9:39:28 PM Error:
2019-09-27 21:39:28.90 Code: 0xC0010018 Source: Package
Description: Error loading value "
Now, as it runs locally, I believe that it might be related with something in the SQL server where I deploy the package so I'll give some information about the setup and some notes:
When running using the Native OLE DB source from SSIS it works (but I want to use the attunity as I read is faster)
Server version is: Microsoft SQL Server 2014 - 12.0.2548.0 (X64) on Windows NT 6.3 - Microsoft SQL Server Developer (64-bit)
I tried to install the Attunity components from here: https://www.microsoft.com/en-us/download/details.aspx?id=55179 but both in my local computer as in the server I get an error saying that it does's find SQL Server installed, however installation seems to finish succesfully after this screenshot below:
(I do get some error registering dlls:
---------------------------
Microsoft Connector for Oracle by Attunity
---------------------------
An error occurred during registration of:
"C:\Program Files\Attunity\Microsoft Connector for Oracle\50\ENU\AttunitySSISOraAdapters.dll"
---------------------------
An error occurred during registration of:
"C:\Program Files\Attunity\Microsoft Connector for Oracle\50\ENU\AttunitySSISOraConnections.dll"
---------------------------
An error occurred during registration of:
"C:\Program Files\Attunity\Microsoft Connector for Oracle\50\bin32\ENU\AttunitySSISOraAdapters.dll"
---------------------------
An error occurred during registration of:
"C:\Program Files\Attunity\Microsoft Connector for Oracle\50\bin32\ENU\AttunitySSISOraConnections.dll"
---------------------------
and after it
I'm running Visual Studio 2017 Professional 15.9.16 with the following among others:
SQL Server Data Tools 15.1.61906.03120 Microsoft SQL Server Data
Tools
SQL Server Integration Services Microsoft SQL Server Integration
Services Designer Version 14.0.3002.113
Oracle Developer Tools for Visual Studio 12.2.0.1.0 Oracle Developer
Tools for Visual Studio Copyright (c) 2005, 2017
Please let me know if I'm missing information to help pinpoint the problem.
I think I might be missing a component but I don't really know what.
UPDATE: I changed the TargetServerVersion in the package properties from SQL Server 2017 to 2014 (the version I have installed) and I'm getting this error now:
Error: 2019-09-30 17:53:13.20 Code: 0x000002C0 Source: Package Connection manager "Oracle Connector 1" Description: OCI error encountered. ORA-12154: TNS:could not resolve the connect identifier specified End Error
Error: 2019-09-30 17:53:13.20 Code: 0x0000020F Source: Data Flow Task 1 1 Oracle Source [343] Description: The AcquireConnection method call to the connection manager Oracle Connector 1 failed with error code 0x80004005. There may be error messages posted before this with more information on why the AcquireConnection method call failed. End Error
Error: 2019-09-30 17:53:13.20 Code: 0xC0047017 Source: Data Flow Task 1 1 SSIS.Pipeline Description: Oracle Source failed validation and returned error code 0x80004005. End Error
Error: 2019-09-30 17:53:13.20 Code: 0xC004700C Source: Data Flow Task 1 1 SSIS.Pipeline Description: One or more component failed validation. End Error
Error: 2019-09-30 17:53:13.20 Code: 0xC0024107 Source: Data Flow Task 1 1 Description: There were errors during task validation. End Error
DTExec: The package execution returned DTSER_FAILURE (1). Started: 5:52:41 PM Finished: 5:53:13 PM Elapsed: 32.125 seconds. The package execution failed. The step failed.
UPDATE 2
I have uninstalled all I had and installed only the V3 version of the Attunity Connection Manager, still getting the error from above. At this point I don't know what could be happening.
It works when I run it from my Visual Studio (2017, with all connection managers pointing to the servers) but then when I schedule it on the SQL Server Agent it give the error shown, Also, it does work well when I use OLE DB Manager, the issue comes when trying to use the Oracle Source (from Attunity)
I'm also using the Connection manager set with format: host:port/ServiceName
I'm thinking I might have something badly set on the server? on terms of the Oracle setting? I have the following:
TNS_ADMIN: C:\Oracle\product\product\11.2.0\client_64bit\network\admin
I don't have more set, shall I have something more?
You missed the explanation about getting the correct version for your version of SQL Server, perhaps. Also the part about
Microsoft Connector Version 4.0 for Oracle The Microsoft Connector for Oracle is a set of managed components for transferring data from or to an Oracle database. The component is designed to be used with the Enterprise and Developer editions of SQL Server 2016 Integration Services and will only operate in those environments. To install the component, run the platform-specific installer for x86 or x64 computers respectively. Read the installation topic in the Help file for installation prerequisites and additional information.
Also:
Microsoft Connector Version 5.0 for Oracle The Microsoft Connector for Teradata is a set of managed components for transferring data from or to Oracle database. The component is designed to be used with the Enterprise and Developer editions of SQL Server 2017 Integration Services and will only operate in those environments. To install the component, run the platform-specific installer for x86 or x64 computers respectively. Read the installation topic in the Help file for installation prerequisites and additional information.
Instead, try the Attunity V3 drivers that can be found here:
The error was being caused on the package trying to run in 32 bit mode. I changed the package settings to 64bit and the SQL Agent settings to run in 64 bits and it started running, it works perfect now :)
I have an Enterprise Oracle Database 12.2.0.1.0 installed. The output of 'show compatible' is 12.2.0.1.4.
When I try to run EXPDP with the correct credentials, I get the following error:
Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64bit Production
ORA-39001: invalid argument value
ORA-39021: Database compatibility version 12.2.0.1.4 is not supported.
After which EXPDP exists.
Should EXPDP's version be aligned with the 'compatible' parameter?
I'm having difficulty deploying an SSIS package developed on my Windows 10 Home machine to the SQL Server 2016 Express instance on my Windows 10 Pro machine.
I have two computers in my home network setup, a Windows 10 Home machine where I'm doing VB.NET and SSIS package development and a Windows 10 Pro machine where I'm running Microsoft SQL Server 2016 Express.
In running the package deployment wizard, after selecting the destination server name I'm running into the Kerberos error "The target principal name is incorrect. Cannot generate SSPI context".
Downloaded and ran the Kerberos Connectivity Troubleshooter on the Windows 10 Pro machine running SQL Server 2016 Express and got the error
Unable to access User Principal information from the System
when trying to connect to the local SQL instance on that machine.
In the log file for the troubleshooter I get some more specific information but I'm running into a dead end with my online research:
3/26/2017 6:55:50 PM Info: Connect to WMI, \root\cimv2
3/26/2017 6:55:52 PM Error: Access of User Principal information failed System.ArgumentException: The supplied context type does not match the server contacted. The server type is ApplicationDirectory.
at System.DirectoryServices.AccountManagement.PrincipalContext.DoServerVerifyAndPropRetrieval()
at System.DirectoryServices.AccountManagement.PrincipalContext..ctor(ContextType contextType, String name, String container, ContextOptions options, String userName, String password)
at System.DirectoryServices.AccountManagement.PrincipalContext..ctor(ContextType contextType, String name)
at KerberosCM.WMIHelper.TryGetUser(SystemInfo mi, UserPrincipal& user)
What do I need to check or configure next?
SQL Server Express does not have an SSIS server component.
Note here that Express does not have "SSIS Designer and runtime" https://learn.microsoft.com/en-us/sql/integration-services/integration-services-features-supported-by-the-editions-of-sql-server.
The Developer edition, which is free, does have this but you aren't allowed to use it for production purposes.
Further to that, I don't think those editions of windows support Kerberos either.
Since we upgraded some of our Azure SQL servers to V12, we can no longer restore a bacpac locally using command line sqlpackage.exe. We also tried using Management Studio, but no dice.
Our local developer machines are running:
Microsoft SQL Server 2014 - 12.0.4213.0 (X64)
Jun 9 2015 12:06:16
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.3 (Build 9600: )
Here is the error we encounter:
*** Error importing database:Could not import package.
Error SQL72014: .Net SqlClient Data Provider: Msg 33233, Level 16, State 1, Line
1 You can only create a user with a password in a contained database.
Error SQL72045: Script execution error....
This looks like it is having issues creating the users that were added by scripts.
Is anyone else running into this issue?
Update:
Apparently this has been a reported problem since April. https://social.msdn.microsoft.com/Forums/sqlserver/en-US/85bb12e8-5ae4-409c-93fa-8a9d025c6b35/error-when-importing-a-datatiers-application-from-azure-db-as-contained?forum=ssdt
The work around from the above post works. You need to modify the bacpac file and create a new checksum: http://inworksllc.com/editing-sql-database-azure-bacpac-files/
This is a workaround, not a fix.
Update: Looks like there will be a fix soon.