Hi,
is there a plan to create a PL/SQL Developer 64 bit ?
I'am working on Windows 7 64 and Oracle 11i R2 64 bit.
Many thanks and regards
Friedhold
We are working on a 64 Bit version, but we do not yet have a date.
At the moment you will need to install a 32 Bit Oracle11g Client. PL/SQL Developer is a 32 Bit application, so it cannot interface with a 64 Bit Oracle Client.
The 32 Bit Oracle Client can communicate with a 64 Bit Server, even on the same machine if necessary. The 32 Bit client can coexist with a 64 Bit Oracle installation when installed in separate Oracle Home directories.
Hi Marco, any new status on PL/SQL Developer 64 bit?
I followed your instructions and attempted to install Oracle 11g Client 32 bit) on Win 2008-64 bit. The Oracle installation kept abort. Therefore, I could not get PL/SQL Developer to work on this system.
Much appreciate if we get PLS/SQL Developer (64 bit)!
We are working on a 10.0.x 64 Bit version now, bit do not yet have a date.
The easiest way to add a 32 Bit Oracle Client:
- Download the Oracle 11g or 12c Instant Client.
- Create an "InstantClient" subdirectory in the PL/SQL Developer installation directory.
- Unzip the downloaded instant client into this directory.
- Define a TNS_ADMIN environment variable and set it to the directory where the tnsnames.ora file of your 64 Bit Oracle Client is located (e.g. C:\Oracle\product\11.2.0\client_1\network\admin).
- Define an NLS_LANG environment variable and set your language, territory and character set (e.g. AMERICAN_AMERICA.WE8MSWIN1252).
To set environment variables you can start the Windows Control Panel, click on "System", "Advanced system settings", "Environment Variables".
Marco:
Can you announce a release date yet for 10.0.x 64 Bit version?
Will a license purchased to the currently-available 32-bit apply to the 64-bit version, once released?
I don't understand why is it so important to have a 64bit PL/SQL Developer? 4Gigs of RAM isn't enough for your daily work, or something else? Because I do not see any reason for such a software (web browser, mail client, office, pl/sql developer, etc) to be a native 64bit application. Video editing, and some very special tasks, where a 4GB memory is a limit, and using 8-16Gb could be much faster, but otherwise, it is not important.
On the other hand, it is better, if the application is a 32bit app, and it means, that memory leaks, flash player, or javascript errors cannot kill the whole machine. I had such memory problems with some websites, and with many opened tabs, and Firefox startet to allocate 3Gigs of memory, it died later, but my PC with 8Gigs of RAM didn't noticed anything. If it were a 64bit app, it could use all the 8Gig memory, making the whole PC unusable. (As it was with Chrome, because chrome launches all browser tabs in a separate process, and this 4Gig limit applies by process).
Just for the usage of 64bit Oracle client.
ATM among all our tools only PLD needs 32bit client.
We have oracle servers behind a secure network and behind firewalls and we have to access them using a terminal server for troubleshooting. In short, our server environments are all 64bit and we have to install a 32bit oracle client just to run PL/SQL developer. Not ideal. I have been asking for a 64bit version for a few years now.
vlevi: The biggest reason for a 64-bit PL/SQL Developer is so that it is compatible with the 64-bit Oracle client. PL/SQL Developer rarely breaks the 2GB memory barrier (you know 32-bit apps can only access 2GB of addressing space, correct? And that fragmented memory can cause applications to throw out-of-memory exceptions long before they've used all of this?), however it has happened on occasion. In fact, there are a lot of operations PL/SQL Developer doesn't handle very well, including a large set of inserts, and copying the results grid with large resultsets.
As for "a 32-bit app cannot kill the whole machine", your problem isn't your memory; it's most likely your swap file settings, your hard drive, fragmentation on either of those, or a very slow PC. No single application can kill the whole machine easily; the whole point of the Windows OS is to isolate application issues, and you have to have a lot wrong to take your PC down from one application hogging memory.
Each app has a memory priority, just like its process priority, and though you can't see it in task manager, the OS trumps both by having the highest process and memory priority. The only way you can take down the OS is if the OS itself (despite being top priority) can't keep up with the actions you're asking it to take (such as paging memory). Most likely your swap file is set to automatically grow, you have a physical hard drive (not SSD), and your drive and paging file are fragmented as h***.
Also, Firefox cannot allocate 3GB of memory unless you are booting with a special 3GB memory switch (or have executed an editbin /largeaddressaware against the fx executable), and if that's the case, I think you are messing with things you may not fully understand. It's true that 8GB is just a higher limit that could be hit by running fx as 64-bit, but throttling the individual processes' memory usage to keep them far below the machine's memory isn't the way to resolve issues like this.
Regardless, I would prefer to have everything be native 64-bit. As with the 16-bit -> 32-bit conversion back in the days of Windows 95, running 32-bit apps on a 64-bit machine takes a performance hit. It may not be noticeable on a good machine, but apps that run natively in the OS's memory space are always preferable. I doubt you wish apps were still 16-bit... moving to native 64-bit is the natural progression of processor capabilities, and applications need to keep up with the times.
Marco:
Where do you stand on the release of 64-bit?
How are things looking for end of year rollout of 64-bit PL/SQL Developer?
It looks like that:
[quote]The initial release of PL/SQL Developer 11.0 will be 32 Bit, but we'll have a 64 Bit version available in the first half of next year.[/quote]
Now that ver 11 has released...64-bit ETA?
Can you please give us a release date for 64-bit version? Thanks
Probably not in the foreseable future.
The 64-bit version of Direct Oracle Access package are missing some important functions, and there has been no response from Marco since October 2014.
See for yourself in the DOA forum, topic no 2 (at least right now).
I guess that PL/SQL developer has this package as its essential pipe to Oracle, so the prognosis seems a bit pessima ;-(
Update on 64-bit PL/SQL Developer please Marco?
From the product page..."To connect to an Oracle database, PL/SQL Developer requires a 32-bit SQL*Net, Net 8, Net 9, Net 10, Net 11 or Net 12 version".
This really needs to go away! We require 64-bit Oracle for nearly all else now...maintaining both 32-bit and 64-bit Oracle Homes is an unneeded burden for our developer support teams...they don't understand the nuances and they honestly shouldn't have to at this point. For large company computing environments it's becoming commonplace that the developer isn't allowed to install and maintain their own PC software environment...and non-developers don't understand the complexities of maintaining the dual Oracle environments
What is the ETA for a 64-bit compatible PL/SQL Developer?
It will be available later this year. We'll have a public beta version available as usual. I can't give you a solid date just yet.
Is there any chance of a very early (closed, not public) alpha release so I can check, and maybe update, my plugins?
No problem. As soon as we have an alpha version we'll let you know.
How could I participate in x64 version testing?
Good thing is "later this year" cannot be much "later" now.
Do you have a date now, Marco? Or, at least, something like "November 2nd half"?
We'll have a public beta available in November.
That should be available this month.
Great. Can hardly wait ;-)
Our organization is at a critical juncture. PL/SQL Developer is now the only tool keeping our developers in a 32-bit world. We have to make a painful decision to go with either Toad (too much functionality geared towards the DBA function that our developers don't even have rights-enough on their DB instances to use if they wanted to...and expensive)...or the free Oracle SQL Developer (clunky, our developers mostly hate it in comparison). We have at most 30 days before we have to make a choice. Where do you stand with 64-bit PL/SQL Developer release date?
It will be available this year.
Marco:
Do you have a release date for 64-bit PL/SQL we can bank on yet?
Marco,
FWIW, I'm looking forward to the 64-bit compatible version. When I see the public beta I will renew my support and download it. I have to build a new development environment and I'd like to do it cleanly without the dual home nonsense...
Cheers