Please suggest what is the difference between odbc connection and oracle server connection in crystal reports while connecting to oracle database.
Please suggest when we will use both of them
ODBC works with "rectangular" or 2D data. If you have spatial data, you will need to use the native Oracle client. Our DBA also says Oracle ODBC has to convert data types while a native client would be "apples to apples".
If you have a Crystal Server accessing an Oracle database, use the native Oracle client. On your workstation, also run the same client whether ODBC or Native as the server.
Related
I understand that to reverse engineer a database in Visio you require a ODBC data source name. I created one using the PostgreSQL Unicode(x64) driver.
In the Visio Reverse Engineering Wizard, you can select from Microsoft SQL Server, ODBC Generic Driver, and Oracle Server. The created DSNs show only up under Microsoft SQL Server and Oracle Server; when selecting the ODBC Generic Driver, there are no Data sources. When I create one using the New button, it again shows up under both the Microsoft SQL Server and Oracle Server.
When I select the DSN from either list, I can enter the User and Password, but get the one of the following errors:
Oracle driver: Warning! You are using a Visio 'Oracle Server' driver to connect with a 'PostgreSQL' DBMS datasource. By using an incompatible driver, it is possible that the catalog information retrieved will be incomplete.
Microsoft SQL driver: Function sequence error
In both cases, I am unable to generate a diagram. Any thoughts?
The "Setup" button next to the installed Visio drivers allows you to select the ODBC drivers to use. If no ODBC driver is selected, all DSNs are displayed; if specific ODBC drivers are selected, only those DSNs which use that specific driver will be displayed.
In my case, the Microsoft SQL Server and Oracle Server Visio drivers did not specify any ODBC drivers to use so all DSNs were displayed.
On the other hand, the ODBC Generic Driver had the PostgreSQL ANSI drivers selected which resulted in my DSN using the PostgreSQL Unicode driver NOT to be displayed. Clicking on the Setup button and adding a checkmark to the PostgreSQL Unicode drivers made the DSN available for selection and the Visio was able to reverse-engineer the database.
Select ODBC drivers associated with "ODBC Generic Driver"
Can Oracle 9.2 client connect to Oracle 12c server?
We have an old server which is an 11g version, and so far there's no problem connecting from client.
Thank You.
That isn't a supported combination, no. As it says in the documentation, you can see the supported client/server combinations at My Oracle Support note 207303.1.
The 9i client used to be supported with an 11g server, but is not with a 12c server. There is a specific note about it:
Attempting to connect from 9.2 to 12.1 will fail with an "ORA-28040: No matching authentication protocol" error.
We are currently using the 9i 32bit Client to connect to Oracle 12c 64bit server in test at the moment and so far it works but with caution.
For example, whenever you query certain data types not available in 9i but available in 12c, the system may crash. We therefore had to build views that convert the timestamp data type to the date data type for example. Then it works fine. Even use of indexes seem to work fine.
Has anyone connected Adempiere (ERP) (or any PostGreSQL db) to SQL Server 2012 Express?
There used to be an IT manager to help me out with this, but now i'm left alone with this.
I downloaded the free Sql Server 2012 Express and wanted to use the SSRS for Adempiere. It seems its running on the SQL Server 2010 for SSRS.
I have already added the ODBC Data Sources for 32 Bit. My computer is using 64bit, is there any incompatibility? I'm not sure if my server is 32 or 64bit.
I've tried following the instructions on http://postgresblog.blogspot.com/ but to no avail.
I already have Crystal Report running, so i'm sure its possible to run 3rd party software for Adempiere.
Anyone knows how i can use SSRS for Adempiere? Thanks!
Since you're using Express edition, if you're trying to connect to any Data Source other than an database on the same SQL Server instance it won't work.
See Features Supported by Reporting Services in SQL Server Express.
From that article:
Report data sources must be SQL Server relational databases that run
locally in SQL Server Express.
Also:
Analysis Services, Oracle, XML, SAP, SQL Server Integration Services
(SSIS), OLE DB, and ODBC data sources are not supported.
You're going to need a different edition to connect to an ODBC Data Source.
I have a client with FileMaker Pro 11 Advanced.
I need to be able to connect to the filemaker database via SQL. I am using MS SQL Server 2008 R2, or Server 2012 can be used.
These are the steps I have tried
0) Turned on ODBC/JDBC sharing in File -> Sharing on FileMaker Pro 11 Advanced for "All Users"
1) installed the FileMaker OBDC driver included on the filemaker disc
2) odbcad32.exe in C:\Windows\SysWOW64 and added a new filemaker System DSN and directed it to the filemaker database.
3) Attempted to add a linked server to SQL using Provider Microsoft OLE DB Provider for OBDC Drivers and the System DSN name i created for Data Source. I left all other fields blank.
I get this error:
Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "FILEMAKER2".
OLE DB provider "MSDASQL" for linked server "FILEMAKER2" returned message "[Microsoft][ODBC Driver Manager] The specified DSN contains an architecture mismatch between the Driver and Application". (Microsoft SQL Server, Error: 7303)
FILEMAKER2 is the what i called the System DSN.
What am I doing wrong/What do I need to correct in order to connect to filemaker with SQL?
Is there a connection string to put in for Provider String?
I have the same mismatch error trying to do a test connect with access.
Thank you for any help.
The error you're getting is because of the driver installed is a 32bit driver propably on a 64bit system.
Look in the downloads of FM for the correct xbit driver.
I've connected to FM using ODBC from PHP apps to do basic inserts, updates, deletes of data. I haven't worked with it like you're attempting to do, though, and like #ted said, FM really wasn't built as a SQL platform.
Their answer to this was to go the other way around. You can setup External SQL sources within FileMaker, and bind your SQL database to FM so that those tables show up in FM the same as regular FM tables. These tables can then be used within FM scripts accordingly, so you could setup any data sync steps necessary there. You could create scripts to move data from FM layouts into the SQL DB layouts at given intervals throughout the day, for example.
Hope that helps.
FileMaker 11 only comes with a 32 bit ODBC driver. The error you got happens when you use a 32 bit driver with the 64 bit ODBC admin utility. Set up your DSN using the 32 bit utility, found here:
C:\Windows\SysWOW64\odbcad32.exe
...and it will work fine.
I'm trying to convert some old Excel-reports to Crystal Reports. The excel sheets uses OLAP-cubes and connects to a database using a XMLA connection over a SimbaO2X driver.
I just can't figure out which connection settings to use in Crystal Reports to be able to connect to the database.
I've tried both XML and OLAP connections, but just can't get a database connection.
Any help with the connection setting would be appreciated!
Edit: The database is a bit of a black box; it's probably an Oracle database (it was an Oracle database before the end user frontend was rewritten in java. They could have changed the database as well.) I have however no success with neither the Oracle Server nor the Microsoft OLE DB for Oracle connection method.
I have also this morning found a SimbaO2X provider under the OLE DB folder. While not working it's the best so far -- it accepts the username and password and lets me select which database to connect to but then fails with ADO Error Code: 0x80040e73 (Format of the initialization string does not conform to the OLE DB specification.) At least I have something to go on.
I'm running Crystal Reports XI if someone needs to know.
Partial solution:
Upgrade Crystal Reports XI to Release 2, service pack 4.
Update from service pack 4 to service pack 6.
Upgrades and updates can be downloaded from the SAP Community Network
A connection can now be made with the SimbaO2X OLE DB driver. This solution should also resolve connection problems with some other databases as well.
However, adding a table to the report results in a 0x800a0cc1 error (Item cannot be found in the collection corresponding to the requested name or ordinal)