Oracle to certify its database v.12c for Windows 10 Oracle's decided it will support Windows 10. For its databases. Big Red's popped out a ”Statement of Direction” (PDF) in which it says it “plans to certify Oracle Database 12c (12.1.0.2) on Windows 10 by October 2015”. The 32-bit Oracle Database client will get the nod on the 32-bit and 64-bit versions of Windows 10. The 64- …
No, the mainframe version was much, much, worse. I think it's good in a certain space, you've got to be big enough to need all the bells and whistles (RAC etc) and to employ a few good full time DBA's, to have midrange UNIX (AIX or Solaris) and real (or virtualised) SAN, not NAS, and then you can tune it and make it fly.
If you have the midrange Unix but only one good DBA on a part time basis, try DB2, it's 90% of the goodness for 10% of the massage and stroking...and if you're on Windows then SQL Server, 80% as good until you get to real data sizes for maybe 2% the DBA attention.
Oracle performance tuning is essentially an arcane set of incantations, runes and chants to force the bloated engine to keep as much of your well-used data in memory for as long as possible.
Given the sort of ultra-reliable hardware and humongous amounts of memory Oracle demands even to run whatever stupid example DB has the scott/tiger credentials, it'd be surely cheaper and just as reliable to put all your data into a single Java ConcurrentHashMap with a very large JVM heap.
This must have escaped me until now.
a 32 Bit version of windows 10?
Honestly: why? The AMD64 extensions are like 10 years old and more than 3GB ram are cheap since forever. What purpose could a dedicated 32Bit OS in the year 2015 possibly fullfill?
Yes, I know, wrong thread an all that...
Yes, but we did not exactly run version12 on this kind of hardware. Ah, back in the days when 32GB disk still required eight drives. Eleven, actually, as you needed two raid groups (6+1 was the largest allowed on the controller) and you DEFINITLY wanted a hot spare.
I'm not expert enough to make much sense of my search results, but I was under the impression that ORACLE support had a few limitations when running on VMs -- specifically that they will not provide support for any issue that is not known to happen on native O/S unless the user can demonstrate that the issue is not related to the use of, for instance, VMware.
It's not quite 'insisting on physical machines' but it does seem to me (again, not an expert) that this may be a bit of an out-dated attitude. Would much appreciate comments from the knowledgeable...
I have not run the latest Visual Studio on Windows 10 (or anything else). But Visual Studio 2013 was a 32 bit affair. If you wanted to build something using the integrated website debugger, you would need both 32 bit and 64 bit versions of your Oracle assemblies. You can conveniently code and debug a site in Visual Studio, and deploy it in IIS as 64 bit.
The managed versions of the Oracle .NET assemblies (ODP.NET) worked pretty smoothly. Unfortunately, they did not support things like UDTs, which are pretty much mandatory when working against eBusiness Suite (EBS). So, we ended up having to use the unmanaged assemblies, which where basically shims over the runtime client DLL files. Unmanaged assemblies have to match both the version and bit level (32 vs 64) of the runtime DLL files. This got really painful because EBS was very particular about what runtime it would use, and that runtime was usually pretty old and not compatible with new versions of the runtime that TOAD and other developer tools wanted installed. Setting up development environments was a nightmare. Deploying was a nightmare. Oracle needs make the managed ODP.NET libraries feature complete.
Mine's the one with the gun in the pocket, which I will point at my head the next time I have to work with anything associated with EBS and the Oracle runtime libraries.
The Register 
Biting the hand that feeds IT
Copyright. All rights reserved © 1998–2024
