I am trying to connect jasperserver to oracle autonomous database (OADB), but with no success. I have successfully configured OADB access from jaspersoft studio by following this tutorial (https://www.oracle.com/a/ocom/docs/database/adw-conn-tibco-jaspersoft.pdf). I also have access to the target OADB from sqlplus on the same server where jasperserver is installed. I tried to configure access for jasperserver similarly to the instructions for jaspersoft studio, also for configuration I used the recommendations from this JDBC Thin Connections with Wallets (mTLS) tutorial. I'm trying to create a connection to the OADB using the jasperserver web interface, but it doesn't seem to accept the format of the string that contains the wallet path (err example image).
Is it even possible to connect jasperserver to oracle autonomous database at the moment? Please help if someone faced a similar task. I would be grateful for any help.
My software environment:
Jasperserver Community Edition 7.8
OS: Oracle-Linux-7.9-2021.08.27-0
Java: openjdk 11.0.12
Oracle driver: ojdbc8
At this link you will see pre-requisites:
JDBC Thin Connections with Wallets (mTLS)
on section 3. tells about the JDK version you must use when connecting with this JDBC.
AND Per link:
https://community.jaspersoft.com/questions/821941/how-can-i-tell-jaspersoft-studio-use-my-current-java-version-instead-bundled-one
Edit your Jaspersoft Studio.ini and remove the lines that read:
-vm
features/jre.win32.win32.x86_64.feature_1.8.0.u151/jre/bin
This will cause jaspersoftstudio to use the JDK you have installed in your computer (not the one that jaspersoft studio has "embedded"); so make sure your computer has at least jdk "1.8.0_171"
Related
Is there any way to connect to Oracle using TOAD without installing an Oracle client?
If you check Installation Guide, Database requirements specify:
An Oracle client must be installed and configured on the system where you are running Toad (...)
Therefore, I'd say no is the answer to your question.
I'm trying use Microsoft SSMA for Oracle to migrate a database onto Azure SQL, but I can't get it going. I've double checked the server name, server port, Oracle SID, password... everything. No matter the type of entry screen I use, I can't get it to connect to the on-premise Oracle instance.
I'm pretty sure the login information is all correct, and I should have a working connector to Oracle since I connect to it from TOAD on a daily basis. I tried installing Oracle libraries per previous posts but not sure if I did it successfully because the issues still remains.
What are the troubleshooting steps I should take in order to make this work?
Log in screen:
Error 1:
Unable to find specified provider.
Compatible Oracle Data Access Connectivity libraries were not found on the machine. You can install them from Oracle product media or download it from Oracle web site.
Error 2:
Connection to Oracle failed.
ORA-01017: invalid username/password; logon denied
Error 3:
Connection to Oracle failed.
Network Naming: No LDAP server detected or configured
After a few more days of debugging, I was finally able to get SSMA to work. This answer helps to document my solution for personal use, as well as hopefully answer anyone else's question in the future.
After looking at the list of prerequisites to have SSMA running, I saw that I needed to have a correct Oracle client running. After some internal discussion, it was likely that the Oracle client SSMA needed was different than the one my computer already had for TOAD. The .Net provider for the TOAD connectors was probably not useful for SSMA.
We run Oracle 11g but I had to install Oracle 12c because 11g did not support Windows 10 apparently. Not too much of a roadblock here.
I found this guide to install Oracle client 12c pretty helpful. Shoutout to my alma mater.
Unfortunately the installer kept freezer, but using this former post, I was able to bypass it with the windows command:
setup.exe -ignoreprereq -J"-Doracle.install.client.validate.clientSupportedOSCheck=false"
After that, I saw different error messages when trying to connect SSMA. I kept trying different options with my logins until it worked. Provider: OLEDB Provider, Mode: Standard.
After being granted the appropriate permissions, I was finally able to access our internal tables and objects.
It was a pretty annoying question with a lot of rabbit holes along the way, but it was definitely worth it, being able to translate all our Oracle schemas to Azure SQL with a few clicks. Hope this helps!
Make sure to validate all steps mentioned below before going to install Microsoft SQL Server Migration Assistant for Oracle.
Make sure you have already installed SQL Server instance that will host the migrated database. Also keep in mind that you are not installing SQL Server Express edition to host the migrated database.
You must have sysadmin account to install SQL Server Migration Assistant for Oracle.
Make sure to install SSMA for Oracle on the server that will host newly migrated database on SQL Server.
It is recommended to install Oracle client software on your target system where SQL Server Instance is running.
Make sure your windows server has Microsoft Windows Installer 3.1 or a later version. Port 1434 should be open.
For more details, You can reference: How to Install SSMA for Oracle to Migrate Oracle Database to SQL Server.
Here's the Azure Database Migration Guide: Migrate Oracle to Azure SQL Database. As you prepare for migrating to the cloud, verify that your source environment is supported and that you have addressed any prerequisites. This will help to ensure an efficient and successful migration.
Connect to Oracle with Oracle Client Provider.
Azure also has other way can help you migrate Oracle database to Azure SQL database, such as with Azure Data Factory. If you still has the connect error. I think you can try to use it. Please reference this tutorial: Copy data from and to Oracle by using Azure Data Factory.
Hope this helps.
I am trying to connect PowerBI with Oracle-DB with no success.
First: when I open PowerBI and try to connect the Oracle Database on Get Data Icon, I get the following error:
Second: I click ok and try to set the connection mannualy:
But in the end I get the ORA-12145: TNS:could not resolve the connect identifier specified error:
I don't know what's happening since my Oracle version is the most recent one (Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production):
Also, my PowerBI Desktop version is Version: 2.63.3272.40262 64-bit (October 2018)
I've already set up the tsnames.ora and listener.ora files, but nothing helped.
Do you have an idea how to figure that out?
In my case the issue was that I was putting the server name wrong, for example I was just putting my db name like
Server : DB
and the way I fixed was
Server: Server/DB
"Power BI" covers a lot of different components. I presume/guess you mean Power BI Desktop?
Your Oracle Database version is not that relevant. The important piece you are probably missing is the drivers, in this case the Oracle Data Access Client (ODAC) drivers. Here's the page in the manual you should read:
https://learn.microsoft.com/en-us/power-bi/desktop-connect-oracle-database
I have a server with an Oracle Database. Using Navicat I can connect to the Database and see the database tables, run queries etc.
I am trying to add ODBC support for Oracle to be used with Crystal Reports.
What I have done so far:
I struggled to install instant client and get it working as shown in some guides. As suggested I downloaded ODAC which bundled on the Oracle ODBC Driver and Instant Client etc.
After installing I had Oracle installed in C:\app\Administrator\product\12.1.0\client_1
I added two Environmental Variable:
%ORACLE_HOME% to go to C:\app\Administrator\product\12.1.0\client_1
%TNS_ADMIN% - to go to C:\app\Administrator\product\12.1.0\client_1\Network\Admin
Once added, I then went to control panel->Administrative Tools->ODBC.
I clicked system DSN and added the connection. The connection was successful.
However, when selecting the ODBC connection via Crystal Reports, the Database is showing the database functions (I assume stored functions as they appear in the functions section for the DB in Navicat). I cannot however, see the actual database tables.
Has anyone else experienced this issue and if so does anyone know how to resolve this. Many thanks for your time
I am having an issue with Oracle connectivity from an SSIS project, and have been Googling around to try to find a solution for over a week, now, and haven't found anything.
I have the following configuration in my dev environment:
O/S: Windows Server 2008 R2 Datacenter, 64-bit
SQL Server Data Tools, 2010
I need to configure an SSIS Data Flow Task to pull data from four different Oracle Data Sources (among others). One is Oracle version 11.1.0.7, two are version 9.2.0.4.0 and one is 9.2.0.8.0.
We use local TNSNAMES and SQLNET.ora files for our configuration.
I have tried this with many different Oracle clients, and basically get the same result, so will highlight one that I did:
Installed the Oracle Client 11gR2 64 bit.
Installed the Oracle Client 11gR2 32 bit (that order is recommended).
Copied my TNSNAMES and SQLNET.ora files into both network/admin configuration folders.
Did a successful TNSPING on each of the 4 databases named above. Successful.
Opened up SQL Server Data Tools and opened a new project
Did a "Create new Connection Manager", picked ADO.NET
Selected "Oracle Client Data Provider", enter the details of the 11g database
Did a "test Connection". Success.
Repeat the procedure for one of the 9.0 databases. When I do the "Test Connection" I get a "Test Connection failed because of an error in initializing provider. ORA-12645: Parameter does not exist".
I get this same result for all three of the 9.x databases.
Oracle "help" says that this error is caused by a missing parameter in the SQLNET.ora file, and that the solution is to add the missing parameter. Trouble is, nowhere does it say what is missing.
I have tried this same procedure with other Oracle client installs other than the two clients - ODTwithODAC1120320_32 bit, ODAC1120320_x64 and get exactly the same result. I can't go to a version 12 client because as I understand it, it won't work with a 9 database. I can't go to a 10 client because that won't work with an 11 database.
I have a feeling that it's very specific to the 64-bit O/S and version of SQL server, but that is our target platform, so need to make it work.
Can anyone help me with this, please?