OLEDB driver have funny performance on VS2019 SSIS Extension - oracle

I have an SSIS that using OLE DB to query oracle database.
The query is actually working well. However, I don’t know why I have following funny performance from my SSIS:
I cannot preview my query result on any data flow, it will turn up with OLEDB run into unknown error
Even clicked “save password”, it will still forgot my password as long as I run into the error from step 1.
I am pretty sure I have OLEDB installed for oracle as I can use debug mode to run the entire package. But I just cannot understand why this happens.
May I ask anyone to share any light?
Thanks in advance!

Related

Can't get JTDS drivers to work in Oracle SQL developer

I am very inexperienced and without appropriate training so apologies if I don't phrase this right or include enough information.
I am attempting to connect a SQL server (Accessed typically via Microsoft SQL Server Management Studio) to a data warehouse via Oracle SQL Developer. But I just can't get SQL developer to recognise the JTDS drivers to enable the SQL Connection. I have downloaded multiple versions of the driver (Jtds1.2.2 and Jtds1.3.1) and I have used the Tools/Preferences/Database/Third Party JDBC drivers tab to specify their location. But I never get a SQL connection option in the connection dialogue. There are no error messages produced, it just never seems to do anything.
The goal of my efforts is to be able to directly access the data warehouse from our SQL server.
I have watched numerous videos showing this process working and I can't work out what is going wrong. The Oracle website suggests that these drivers can be installed via the Check for Updates function but this doesn't do anything when I have attempted it.
The solution was to Copy the drivers into the same parent directory as the SQL developer. Previously I had tried copying it inside one of the sub folders and tried copying it outside of the directory. But as soon as I put it in the main SQL developer folder it worked.
Thanks to thatjeffsmith

Oracle ODBC connection failure (using oracle's stock ODBC drivers)

Want to use an Oracle-ODBC connection in Visual Studio 2017/ SSIS as it's much faster than OLE DB during tests.
Problem:
I follow Oracle's steps to the letter.
Install instant client (v18, also tried v12).
Download/ extract ODBC download in same library. Run odbc_install.exe.
See the Driver in 'ODBC Data Sources/ Admin' in Windows 10.
Add new User Data Source. TNS Service names pull up fine. Test
Connection (User/ Pass) -- it works!! The Connection works!!
I tried this with 64 bit in Oracle, their instant client v18.3 or 12.2 both. All works in Window's "Oracle Source Administrator" via test connections.
I tried this with 32 bit downloads as well. All is good.
Now, open Visual Studio. First tried 64 bit (my Windows OS is 64 bit, but Visual Studio Data Tools is only 32 bit). Had a hunch it wouldn't work.
Error message "system architecture and client is not the same" or such. Gotcha.
Tried the 32 bit Oracle ODBC driver (User Source). I keep getting the same message (tried 18_3 and 12_2 versions).
Now .... SQLORA32.dll is in the very file path it named. It's right there! Why can't it be found? The test connection in ODBC Source Admin works! What is going on here?
And I'm unsure if I have to "register" something via the command line, I had to do that once before, maybe it was an unrelated issue.
To boot, when I tried a 3rd party "Devart Oracle ODBC connector" -- it's a simple 5-second install wizard that works flawlessly instantly. Problem is it's a 30-day trial and costs $150 at least. How can I can get an Oracle-created ODBC connector (Oracle being world-renowned for janky-azz products) to actually work?
Devart, and probably Attunity Oracle ODBC: 5 second installs
Oracle's own: Harder to install than breaking into Fort Knox/ learning Mandarin Chinese. Please advise.
I am answering my own question.
Unfortunately some of us ETL/ BI guys need to go so wide on problems that there's no time to figure out every little detail/ glitch of Oracle's ... whatever they're doing now.
But here's a fix. In Visual Studio 2017/ Data Tools/ the SSIS IDE .... if you want an Oracle ODBC connection (Faster than OLE Db for some reason) --- when you're setting it up, instead of selecting a NAMED "user or system data source" that you created in ODBC Source Administrator, simply using the "Builder" option (to the left of Use Connection String) for a connection string. It does the exact same steps as the ODBC Source Admin, but within Visual Studio. I don't know what the difference is here, but some wizardry/// who knows what is different, and the connection somehow, suddenly, for some reason, works.

Compilation error with procedures in Oracle SQL Developer

I am constantly facing a strange problem using Oracle SQL Developer.
I have a procedure in my schema, which is correctly compiled. However almost each time I close a database connection or restart computer, I see this procedure uncompiled althought I didn't make any changes in code...
Has anyone ever faced similar case? Thanks in advance for help.

Error occurs while install Oracle BIEE

I'm trying to install Oracle BIEE 11g on my computer, but something wiered happend.
I've tried on a x86 computer with 2GB memory and a x64 computer with 4GB memory. Both of them are running Windows OS. I want to connect a MS-SQLSERVER database, and I've finished creating related DEV_ tables using RCU.
I followed the tutorial from the doc.oracle.com, but then I stopped at the 14th step, it says "设置数据库连接失败". I can continue install, but another error occurs, service obisch1 cannot start. I can open localhost:9704 after installation, but it will return a 500-error after I restart my computer.
I searched the internet, it says I should set my database source using "Net Manager" Tool, but I don't know how. And after install I got a database source using driver "MERANT OEM 5.3 32-BIT SQL Server Wired Protocol", but I can't make change to it, cause the system says can't find the driver...
I don't know what to do now... Anybody can help me? Thanks very much.
Well, I've kind of solved it.
I still don't know why my computer cannot find the odbc drier "MERANT OEM 5.3 32-BIT SQL Server Wired Protocol", which seems to be the reason why I can't connect to the database at the 14th step while I install OBIEE.
However, I add an odbc-connect through the system's function, I found it in the control panel.
On the other hand, the url http://localhost:7001/em and http://localhost:7001/analytics can be still accessed(after a long time, it can be accessed).
So, then I create a rpd file use my own odbc-connect, and it seems work fine.
Thanks everybody, anyway, and hopes can help

What is the best way to debug an Oracle SP?

I am sort of new with Oracle. We are having lot of issues.
We use two main clients for running queries. SqlDeveloper (provided by Oracle) and PL/SQL Developer 7.1.
We are trying to debug a stored procedure. Problems are:-
There are some Stored Procedures that are compiled with somename.SPNAME meaning they are in a different schema/or synonym? So when we login to our DB from SQLDeveloper we are not able to see the stored procs that were compiled with somename.SPNAME.
When we login to the Same DB via PL/SQL developer we ARE able to see above mentioned SP's however, we are not able to debug anything. Clicking on Debug toolbar shows everthing is grey'ed out (except setting/modifying breakpoints).
So from here, we need to resolve either of the issues. Either change something in sql developer so all the SP's are shown and then we can debug them (since we know debugger in sql developer works) OR make debugging work in PL/SQL developer.
I know the question and explanation got a little verbose but we are struggling with this problem and could really use some help.
For Oracle SQL Developer, you'll see other schema's objects by expanding the "Other Users" node.
For debugging with PL/SQL Developer, you'll need the "DEBUG CONNECT SESSION" privilege.

Resources