Native Version of Oracle DB on FreeBSD? - EBS on Linux

Is there any chance of getting a native version of Oracle on FreeBSD? I don't care about official support (the FreeBSD community was always very helpful).
What is needed here:
Oracle Client 8+ as some things are a real pain with the old oracle-7 client. Example: One of our customers is using 30+ Webservers that connect to an Oracle DB.
I'd be interested to run Oracle-DB-Servers for SAP using FreeBSD. Even if linux-emulation is working, native binaries (at least for the DB) would be much appreciated.

Oracle unfortunately doesnt make a BSD distro. They are, however, coming out with a Mac OSX version later on.


Request for Comments and Experiences with Instant Client

Thank you everyone for coming to the Instant Client forum. To ensure that we are giving you the best product that we can, I would like to get all the feedback you may have so far regarding Instant Client.
How have your experiences been?
What benefits have you had?
What drawbacks hindered your way?
What quirks confused you?
What would be nice to have?
Please include your platform and database versions as well. Thanks! Looking forward to hearing from all of you! 
I am testing it now and I am excited about having a simpiler client setup process for our application, not to mention "thinner". I think it will go along way in the eyes of our end users to reduce the perception that "Oracle is complicated!".
Everthing looks good so far except for one show stopper, the Oracle Provider for OLE DB isnt supported yet. I saw your post that it is under concederation, but it's unusable for us without it.
Is there anyway to install the provider manually?
Glad to hear that you're doing well with Instant Client. However, I'm even more glad to hear about your problems. We want to hear all the problems so that we can make sure they are fixed.
For Oracle Provider for OLE DB, there is no supported way to install the provider manually. We will likely support the Provider in the near future, but keep a lookout for upcoming news to confirm.
What are you doing specifically with OLE DB? Can you describe your applications a bit more? 
We have a VB application that we are migrating from DAO(ODBC) to ADO(OLE DB). ADO allows us to give the user better feedback, like a full Oracle error message instead of "ODBC call failed".
I have run into problems getting the Instant CLient to work on machines with an exsiting Oracle 9i home, but have gotten it to work on a virgin machine following the instructions on the download page.
I REALLY like the fact that no TNSNames.ora or is nessessary. This removes a layer of abstration but reduces complexity (file dependencies), and that is always better in the long run.
The connection string syntax (host/instance) reguired some research. I would suggest a readme in the client files covering the basics of getting it to work. I was unable to access the white paper last week, maybe it is convered in there. 
Hi Toliver,
the installation-routine for the ODBC-Driver does not work under NT4.
And: we would be interested in access to servers lower than 8.1.7.
At the moment I have a problem where I would need access to a server running 8.1.6 where I have no environment so I cannot use the "normal" client with registry entries and so on.....
Here is a copy of my problem that I had psoted earlier in this forum. HAve you heard of any else with this type of issue, or know of any solutions?
I have setup the Instant Client on a Windows Server 2003 machine running SQL Server 2000 Enterprise Edition. I hav a DTS that will run fine when I am logged into the machine, but when I logout and have the DTS run from the Scheduler.
I get an error that the Oracle Driver can not be found.
I am logged into the machine locally as administrator and both SQL Server and SQL Server Agent Services run as the local administrator as well. Any ideas or suggestions as to why this doesn't work?
Thank You
Hi everyone.
We are glad that Oracle has released Instant Client. the TNSNAMES.ORA are really a problem when we need to share the application with a large number of users.
Even though it's a very good client, I would like to make some suggestions.
1. Remove the dependency of the ODBC client with the folder where it is installed. Maybe it would be better to have only one possible installation. We made a custom Installation and the ODBC Driver is just called "Oracle Instant Client".
2. We need support for Oracle Database with version lower than 8.1.7. Maybe it is blocking the users from "migrating" to Oracle Instant Client.
3. Release a Simple Windows Installer Program to simplify even more the installation of the Instant Client + ODBC Driver + JDBC Driver + Future OLE DB. Please don't use Oracle Universal Installer.
4. The Client are heavy (80 MB). I know it is not as heavy as before, but it does require a litte work. If the Client weren't that heavy, it would be easy to "download" the client from some Corporate Intranet Server.
Thanks for your comments. Regarding your suggestions:
1. Unfortunately, the ODBC client itself is tied to the folder where it is installed since it is the Microsoft Driver Manager that controls the access to different ODBC drivers. Thus, unless you can wrangle Microsoft into changing such behavior, we cannot support that.
2. Instant Client does not support 8.1.7 databases since these versions of the databases are NOT supported by Oracle in any manner anymore. The support was dropped at the end of 2003.
3. You do not need to use the Oracle Universal Installer at the moment. We will consider options outside of what we currently offer at the moment.
4. The client is the current size because of the languages that we must support.
I hope that addresses your concerns. Please write more suggestions as they spring to mind. Thanks! 
2. Instant Client does not support 8.1.7 databases since these versions of the databases are NOT supported by Oracle in any manner anymore. The support was dropped at the end of 2003.
I assume that you meant "pre-8.1.7 databases" here-- the Instant Client will connect to databases. I assume that when the first 10g patchset comes out to allow connections to 8.1.7.x databases that the Instant Client will support those earlier patchsets as well.
Distributed Database Consulting, Inc. 
You are correct. I meant PRE-8.1.7 databases are not supported. Thanks for the second glance. 
I've used the instant client from a Windows platform with somewhat mixed results.
I can connect using SQLPlus to 10g, 9i and 8i databases running on Windows Server 2000/2003 which is great!
However, the ODBC drivers for the instant client has caused me a lot of problems, as the program using it to connect to the 9i database will just crash. If I use a regular Client it works just fine with ODBC on the 9i.
So any suggestions on getting Instant Client and ODBC to coorperate will be great.
What exactly are you doing with the ODBC drivers with Instant Client that are causing it to crash? 
I love the new homeless Instant Client! I wish we had it years ago. Some comments:
1) The MS ODBC administrator GPF's (blows up) when trying to configure a new data source using the new Oracle IC drivers. Have to hand-edit the registry.
2) I heartily agree with the request that the new client install without requiring the normal Oracle installer. It's just too bloated for easy deployment. I'd rather hand install the files than to have to use that. Also, .zip not .jar please.
3) Need better documentation on the connection string options. It took me 3 weeks to figure out that what used to be scott/tiger#mydb is now scott/ (it's looking for the GLOBAL_NAME, not the SID and TNSPING won't show you that! Doh!)
4) Please let us specify a range of ports (e.g. :1521-1524) and let it figure out where the SID is on that machine. We move ours around and don't want to update hundreds of clients with hardcoded command lines.
5) Maximum backward compatibility, please! It's not easy moving all those Oracle apps to databases, yet, but my old OCI client programs should not have to care. I don't want to have 2 SQL*net driver stacks on my PC's.
Thanks -- I'll be watching for new features.
I'm trying to use the instant client with ODBC to run Axapta 2.5. This is probably not certified, but it would be nice if it worked. I've triede to run against and oracle servers.
My hope was that someone here had already tried this and could give some hints on the ODBC that comes with the instant client.
BTW, must I use a specific MDAC version for this? 
 Hi Jue & all,
better late than never, I guess!
I have been using the instant client along with tora, both on linux (knoppix/debian), and windows (XP), accessing a 9i2 db with no apparent problems. Neat!
One advantage I see of the simple ZIP packaging is that it can be installed without administrative rights on windows.
On debian, I just converted the provided rpm to deb format using alien, and "it just worked". It would be nice to see at least the stable version of debian supported, though.
Useful and lightweight additions would be to include a sample tnsnames.ora, and the FAQ in text or html format. Tnsping and sqlldr would be real nice as well.
I could not get the //servername/dbname (as from the FAQ) connection string to work , but maybe that's just me...
Anyway thanks for finally providing an easily connectivity layer on linux, cheers,

Connecting to 8.1.7?

From the main page of Raptor on OTN: "Project Raptor can connect to any Oracle Database version and later". Yet, I was able to connect to an 8.1.7 database.
What is the reason behind limiting the version to a minimum of Thanks. 
Raptor may work well with 8.1.7; but we don't want to make the time to test it. We also issue different SQL depending on the db version 9.2, 10.1, 10.2; so if we offically supported 8i and 9iR1 we would need to review each and every SQL statement to ensure it was proper. So our primary reason is to focus our development efforts where it benifits the most oracle customers. I know many customers are still on 8.1.7; so it was a hard call; but since Raptor is a young product it made sense to be forward looking. What is your reason for not upgrading to 9iR2 or 10g? Are you running apps with 8i?
Thanks for your reply Mike. We do have two Oracle E-business suite installations, an older version running on 8.1.7, and a newer one running on 9.2, hence my question about 8.1.7.
Thanks again.

Multiple Clients & Multiple ODP.Net

I am trying - unsucessfully so far - to get 9i and 10g clients coexisting on a Windows 2003 Server with .Net Apps and web services that need to run the version they were tested with. I have read the FAQ for ODP.Net and some related messages from this forum, but the answer still eludes me.
If I remove the publish policy DLLs from the GAC, will code compiled on a PC that only had VS2003 and the 9i client pick up the 9i ODP.Net and the 9i binaries or the 9i ODP.Net and the 10g binaries? (10g was installed last).
How can I get two sets of web services to access different client binaries on a server that has both 9i and 10g clients (in different homes)?
I cannot see how to set a different local Windows System Path for specific web applications or specific web services as referenced (but not described) in the FAQ. I have checked the IIS Application properties and the IIS Application Pool properties (each app or services run in a dedicated process). How can I set up different Windows System PATHs? 
Why do you need both the Oracle 9i and 10g client on one computer? The 10g client will work with both the Oracle 9 ODP.NET and Oracle 10 ODP.NET with the policy files setup right. If you look at the requirements, I think you'll find that ODAC 9 requires Oracle 9 client OR HIGHER. And ODAC 10 requires Oracle 10 client. So make them both happy with just one Oracle 10g Client installed and no 9i Client.
I have clients with VS2003 and VS2005 apps using ODP 9 and ODP 10. Even the old programs written in VS2003 using ODP9 work on a client machine with Oracle 10 client and ODP9 installed.
One note on the Policy files and Oracle.DataAccess.dll: if you use the gacutil.exe in the .NET Framework SDK, use the one from .NET 2.0 to add to the GAC. The .NET 1.1 version won't always work right when adding to the .NET 2.0 GAC. You know you did this if you see "Unknown error" when you try to add it to the GAC with the wrong gacutil.
Thanks for the tip about the GACUTIL.
Why do you ask me why I want to know this? You may have had a good experience with applying updates and hot fixes and patches, but not everyone does. There are lots of posts in this forum about needing to apply patches in isolation of other applications and it's easy to understand why
(1) vendor apps only certified for specific versions, so applying patches will make it hard to get support ("please insall the verified versions then see if you still have the problem". "We only support the versions stated in our documentation")
(2) bad past experiences with backwards compatibility and
(3) a desire to minimize the risk of triggering outages in other production applications running on the same OS instance.
In spite of your anecdotal evidence, it is foolhardy to assume a vendor will always be 100% backwards compatibily and there is no way I can justify the expense having all applications thoroughly retested every time one of them needs a patch applied to the Oracle client or simply wants to try a new version of the client.
I am asking how to do what the FAQ for ODP.Net states you can do. The claim by Oracle that it can be done is a good reason to ask how to do it when it does not appear to work as documented.
Sorry to jump on this, but it is frustating when respondents "ask why do you want to do that?" when the "how do I ..." question is reasonable. 
Hi Larry,
Have you already tried using both 9i and 10g, after removing the policy files? What error did you get?
You should be able to use both a 9i and 10g home at once without problems, as long as you 1) remove the policy files in the gac, which means you'll 2) need to have exactly the version of odp the apps were compiled with. I havent actually tried it myself however.
Where you'd run into issues though, is if you tried to have 2 9i homes or 2 10g homes. The multiple home issue isnt so much an ODP problem, as an Oracle client problem, and is due to the way the Oracle client software loads dll's, which relies on your PATH environmet variable. This shouldnt be a problem using 9 and 10, as the dll's now have version numbers in their names.. oraclient9.dll, oraclient10.dll, etc. 10.1 and 10.2 you'd have problems though as in both cases the dll is named oraclient10 for example.
As far as how you'd change IIS apps to use a certain path, I dont know if thats possible. Someone from MS may be able to comment better, but I'd be sursprised if there was a way to do that. As far as I know, you get the path that was in place when IIS was started.
Hope that helps,
ok, i should have read the faq before responding. It does seem to indicate you can configure IIS to use differnt paths for different apps. I still dont know how you do that though, and I wouldnt think you'd need to in the case of 9i and 10g MOH config.
Message was edited by:
Thanks, Greg.
I was about to try that (and assume it is likley to as far as apps that use the 9i and 10g client), but just realized I am officially on vacation for a week, so that will wait until I am back.
I, too, have been unable to find a way to specify a path for an IIS application pool, but the ODP.NET FAQ stated it was the way to go when you needed to access specific homes for different sub versions of the client, so I am trying to find out how to set that PATH for different web services to make sure I am ready when two 9i apps or two 10g apps need different patch levels and thus different Windows System Paths pointing to different homes. I guess I should open a TAR to see if Oracle can back up their FAQ statements (or provide a different method).
I wish Oracle would come out of the dark ages and stop relying on the Windows System Path for anything. In this day of config files and registry settings, it seemse ridiculous that the Path has any significance to a modern tool. Makes me wonder if Oracle's core is written in PL/1 <grin>.
Anyhoo ... Thanks for the reply.
Hi Larry,
I would like to know whether you could finally configure the IIS such that different apps use different clients. Also would like to know if you have created application specific policy files.
As you have pointed out in one of your posts, though these things are mentioned under the FAQ, there seems to be no way to implement them.
Please help

Any further development of 1.2?

Will there be any further development done on the 1.2 codebase? I am stuck supporting a couple of 8.1.7 instances while we migrate away from our "legacy" Unix environment onto Windows (blech!). Having a version of SQL Developer that is relatively bug-free and able to connect to 8i databases would be very helpful to customers who, for whatever reason (ours being that we are in the pharmaceutical industry, so upgrading databases takes several weeks of validation work), are stuck on older databases.
At least the Windows servers are running 10.2.
(sorry to double-post, but the first time was in a dead--or at least dying--thread) 
I wouldn't have thought so. It is not in oracle's interests to prolong the life of 8i, even indirectly.
From a general point of view, the thought of the sqldeveloper team trying to manage three code lines instead to the current two (1.5.x and 2.x) fills me with dread. 
True. I figured as much, but it couldn't hurt to ask. I guess I will just reinstall TOAD using my personal license and hope IT does not audit the software on my machine again until our 8i instances have been migrated.

Can VB.NET 4.0 application include oracle drivers?

We have recently deployed new Win 7 32-bit workstations to all our developers. The Oracle Application developer suite on these workstations includes oci.dll v10.1.0.4. We have developed a 4.0 utility application for the developers, but it was developed with the Oracle 11g drivers. The application is stored on a shared drive and the executable is run from the shared drive. When we run the application, we get an OCIEnvCreate failed with return code -1" error. Some research indicates that this is due to using an older version of the oracle client on Win 7.
Rather than attempting to upgrade all the developer workstations and possibly risk interfering with the developer software, my boss has asked me if there is any way to package my utility such that it included all the required Oracle drivers and would use those drivers when launched from the shared drive?
Does anybody know if this is possible, and if so, how I would build the app so it includes all the drivers?
Oracle announced recently that they're going to make a fully managed driver at some point, that would make this a snap (add reference, set copy local to true, done).
It's not out yet. In the mean time there's a couple of threads on ways to bundle the necessary DLLs, but it's significantly less straightforward. Here's one such thread: 11g ODP.NET 32bit/64bit minimum requirements to install to a client machine
Realistically if you're talking about Windows 7 and a few development machines, you really just want to install the 11g client software on them. The 10 client just won't work reliably in Windows 7.
I'm also curious about what developer software you think it'll interfere with? You can just install the client and not the developer tools if you don't want those. 
The developer workstations have Oracle Development Suite installed and if anything I request to be installed for my utility messes with that I'll be dogmeat. 
I followed the instructions in the link and moved the specified oracle dlls into the folder alongside my executable and that seems to work!
Thanks for the pointer!
Great, glad it helped. :) 
Great, glad it helped. :) 
Great, glad it helped. :) 
Great, glad it helped. :)