Oracle Database 12c Is Available for Download

File this under “it’s about time” and “ICYMI (In Case You Missed It), but Oracle has released Database 12c (12.1.0.1.0). Downloads can be found on their TechNet and E-Delivery sites. At this point, the only available versions are for Linux (x86-64), Solaris (Sparc64), and Solaris (x86-64). Other platforms will surely follow

Not officially released… yet

According to media reports (and my inability to find an actual press release from Oracle), the formal launch of Database 12c will occur “within a couple of weeks”.

Differences between TechNet and E-Delivery

While, otsensibly, it may be the same software, there is always the possibility that you’ll get slightly different versions. The software that you download from TechNet is usually in the form of either a zip file or a “tarball” of the staged installation. The downloads from E-Delivery are also zip files, but they represent the actual media packs (CD or DVD). For some reason, Oracle doesn’t do ISOs, but, nevertheless, the E-Delivery downloads are typically viewed as more “supported”. As a result, I recommend using the E-Delivery downloads rather than TechNet if you’re planning on doing anything that is going to need to be handled under a support contract.

Naturally, for either method, you will have to agree to license terms and export conditions. If you have never used E-Delivery from your Oracle account, there might be a slight delay as your account is verified by Oracle.

As with all new software, be sure to test thoroughly and make sure any applications are certified with 12c before deploying to production.

Oracle Client 12c is also available

The Oracle 12c Client can also be downloaded for the following platforms: Linux (x86-32), Linux (x86-64), Microsoft Windows (x86-32), Microsoft Windows (x86-64), Solaris (Sparc 64), Solaris (Sparc 32), Solaris (x86-32), Solaris (x86-64).

NOT CERTIFIED WITH E-BUSINESS SUITE

Since this blog is focused on E-Business Suite (and E-Business Suite is what I do), I feel the need to state that Database 12c is NOT certified with ANY RELEASE of E-Business Suite at this point. I suspect that we’ll see it certified against 12.1.3 and the upcoming 12.2 at some point in the future (maybe 12.2 on release). It is highly unlikely (in my opinion) to be certified against any release 11i. In the event that it is certified against 11i, you can bet that it will be a pretty low priority item.

You can find them available here:

Oracle E-Delivery: https://edelivery.oracle.com

Oracle TechNet: http://www.oracle.com/technetwork/indexes/downloads/index.html

— James

.

Internet Explorer 10 and E-Business Suite

In case you hadn’t noticed, Microsoft started pushing out Internet Explorer 10 to Windows 7 customers back in early March.  Internet Explorer 10 is, at this point, not certified with any versions E-Business Suite.

You can read more about it on the E-Business Suite Technology blog (otherwise known as “Steven Chan’s Blog”).  A link to that posting can be found here.

Deciphering support and licensing issues surrounding Oracle on VMWare

I frequently run into clients that are wanting to run Oracle products in their VMWare cluster. Since I generally deal with E-Business Suite customers, I tend to take the position of “anything that swallows machines whole should probably have a physical machine” approach to production systems. However, I can see some distinct advantages to virtualization, particularly when it comes to managing numbers of non-production environments.

Unfortunately, there is a lot of confusion out there as it relates to Oracle and virtualization… particularly surrounding one of the most popular virtualization solutions, VMWare. I’ll try to provide my best understanding of the issues here.

Are Oracle products certified on VMWare?

The short answer is, NO. But, that really shouldn’t be that much of a concern. Keep in mind that a VMWare Virtual Machine is, technically, hardware. Oracle doesn’t tend to certify against hardware. And that’s what that VMWare really is, it’s “virtual hardware”. As such, it’s really no different than a particular model of Dell or HP ProLiant.

What Oracle does do is certify against a platform. A platform is the combination of a particular version of an operating system (Solaris 10 vs. Solaris 11, for example) and processor architecture (Sun SPARC vs. Intel x86-32 or Intel x86-64). In the case of a deployment to VMWare, your platform will be determined by the operating system that you intend to run inside of the virtual machine. (For example, Red Hat Enterprise Linux 4/5/6 for x86 or x86-64).

Are Oracle products supported on VMWare?

Oracle’s official support position can be found in MOS Note 249212.1, copied below (emphasis mine):

Support Position for Oracle Products Running on VMWare Virtualized Environments [ID 249212.1]

Purpose

Explain to customers how Oracle supports our products when running on VMware

Scope & Application

For Customers running Oracle products on VMware virtualized environments. No limitation on use or distribution.

Support Status for VMware Virtualized Environments

Oracle has not certified any of its products on VMware virtualized environments. Oracle Support will assist customers running Oracle products on VMware in the following manner: Oracle will only provide support for issues that either are known to occur on the native OS, or can be demonstrated not to be as a result of running on VMware.

If a problem is a known Oracle issue, Oracle support will recommend the appropriate solution on the native OS. If that solution does not work in the VMware virtualized environment, the customer will be referred to VMwar for support. When the customer can demonstrate that the Oracle solution does not work when running on the native OS, Oracle will resume support, including logging a bug with Oracle Development for investigation if required.

If the problem is determined not to be a known Oracle issue, we will refer the customer to VMware for support. When the customer can demonstrate that the issue occurs when running on the native OS, Oracle will resume support, including logging a bug with Oracle Development for investigation if required.

NOTE: Oracle has not certified any of its products on VMware. For Oracle RAC, Oracle will only accept Service Requests as described in this note on Oracle RAC 11.2.0.2 and later releases.

In my understanding of the actual way that the policy is applied, it’s really a matter of whether or not the support engineer suspects VMWare to be the culprit. What I’m saying here is that, generally speaking, the support engineer will work your issue the same way that he/she would if you were on physical hardware. However, once that engineer thinks that VMWare could be the cause of your problem, they reserve the right to “punt” and say “call us back once you’ve reproduced it on physical hardware”.

Now, VMWare, to their credit, has a policy that they call “Total Ownership”, where they will accept accountability for any Oracle-related issues. You can read their official policy at the link below.

http://www.vmware.com/support/policies/oracle-support.html

It is my understanding that, as part of the “Total Ownership” policy, VMware will reproduce the problem on physical hardware for the customer if Oracle decides that VMWare is the problem.

What about Licensing?

Part of the big problem I’ve always had with Oracle on VMWare is caused by Oracle’s per-CPU licensing policy. My original understanding was that, if you have a total of 64 cores in your VMWare cluster, it didn’t matter if you were only using 8 cores for Oracle. Oracle would tell you that you had to pay for 64 cores. The idea behind this is that you could, potentially, resize the virtual machine to suit certain needs. Maybe you need more horsepower during month end?

What I’ve since learned is that Oracle has a policy document (below) that talks about “soft” vs. “hard” partitioning.

http://www.oracle.com/us/corporate/pricing/partitioning-070609.pdf

What I’ve described above would fall under the concept of “soft partitioning”. However, “hard partitioning” methodologies allow for a different approach. VMWare has (naturally) a nice document that explains their approach to implementing clusters that are in compliance with Oracle’s licensing requirements.

http://www.vmware.com/files/pdf/techpaper/vmw-understanding-oracle-certification-supportlicensing-environments.pdf

From that document, pay particular attention to section 2.2. In that section (specifically Scenario B), they discuss DRS Host Affinity rules and VMWare CPU pinning. (emphasis mine)

2.2 Clusters: Fully Licensed Versus Partially Licensed Clusters

Scenario B: Partially Licensed Clusters

When a customer does not have enough Oracle application instances to justify creating a dedicated cluster for those applications, only a subset of the hosts in the cluster are licensed for the Oracle application. In this situation, the customer must be careful to restrict the movement of Oracle application instances and virtual machines to only those hosts that are licensed to run the product.

In this case, DRS Host Affinity rules can be used to appropriately restrict the movement of virtual machines within the cluster. DRS Host Affinity is a vSphere feature that enables you to ensure that your Oracle applications are restricted to move only between a subset of the hosts—that is, not all hardware in the cluster is “available” to the Oracle software. DRS Host Affinity is a clustering technology and is not a mechanism for soft or hard partitioning of the servers. As explained in section 2.1, using VMware CPU pinning to partially license a host is not currently recognized by Oracle as a “hard partitioning” mechanism that receives subsystem pricing. However, once you have fully licensed the host, you have the right to design your environment such that the Oracle workloads are free to run on the licensed hosts inside the cluster. At present, Oracle does not have any stated policy regarding clustering mechanisms or DRS Host Affinity. Customers can easily maiatain records for compliance purposes as explained in section 2.3.

The advantages of this approach are similar to the advantages achieved with a fully licensed cluster. Because customers are typically able to increase the utilization of licensed processors, they reduce license requirements. However, consolidation ratios tend to be lower, because advanced vSphere features can be employed only on a smaller subset of the hosts.

VMWare CPU pinning is a feature that (in my understanding) would allow you to say that a given VM would only use certain cores in a physical host. So, if you have a single host with 16 cores, you can “pin” a given VM to four of them. According to Oracle’s partitioning document (and VMWare’s document), you would still be required to pay for all 16 cores in the box. The basic logic here is that Oracle’s licensing policy is based on the number of cores in a physical server. You can’t license part of a box. Period. No exceptions.

On the other hand, DRS Host Affinity, is a way to pin a virtual machine to a given host (or collection of hosts) within a cluster. So, let’s say that you have ten (10) 8-core physical hosts (total of 80 cores) in your VMWare cluster. Using DRS Host Affinity, youcould restrict your Oracle VMs to a subset of those physical hosts. For example, if you restricted your Oracle VMs to only five (5) of those physical hosts, VMWare’s contention is that you would only have to license 40 cores.

I sould probably include the standard “IANAL” (I am not a lawyer) disclaimer. I’m also not a VMWare administrator. What I am is a DBA and an IT Geek. That’s pretty much the limit of it.

Hopefully this provides some clarity on the issue.

For further reading on the subject, here are a couple of blog links that I used in my research:

http://blogs.vmware.com/apps/2012/11/update-on-virtualizing-oracle.html

http://longwhiteclouds.com/2012/07/21/fight-the-fud-oracle-licensing-and-support-on-vmware-vsphere/

– James

Why I don’t depend on TOAD (or OEM) and neither should you.

My apologies in advance, as this posting may sound like something of a rant.

The first thing I’d like to point out is that I have no real problem with TOAD, Oracle Enterprise Manager, or Windows-based editors. They are all excellent tools that can be extremely helpful in your environment. My objection to these tools is based solely on a lowest-common-denominator argument.

First, a little background. Back in the early 1990’s, I was working as a Unix Systems Administrator for a company in Kansas City, MO. Since then, I’ve worked mainly as a consultant.

Shortly before I started that job in Kansas City, the company had hired a new CIO who let go about half of the legacy (mainframe, COBOL) IT department. The new direction for the company was implementation of Oracle E-Business Suite on Data General Unix (DG/UX).

The mainframe IT staff that survived were being re-trained in the new technology. At one point, several of them came to me insisting that I install ISPF (an editor they were used to on the mainframe) onto the DG/UX boxes because they were struggling to learn to use the vi editor. I informed them that, while they (as a group) may carry enough weight to convince the CIO to direct me to install it (assuming it was even available). However, when they go to their next job and claim that “they know Unix”, they would be alone and wouldn’t have that leverage.  My suggestion was that I would help them to learn the vi editor. (I did offer emacs as an alternative, since it is and was extremely common on Unix systems… Unfortunately, friendlier editors like pico, nano, and joe didn’t exist yet.)

If your primary job is software development, a tool like TOAD is generally something you can depend on having. However, as a DBA, you can’t necessarily depend on having TOAD (or even Oracle Enterprise Manager) at your disposal at all times. Maybe you’re starting a new job and the previous DBA hadn’t set up Enterprise Manager (or you haven’t gotten around to it yet). Even in environments where those tools are available, they may or may not be working when you need them.

So, my advice? There are certain tools that are almost ALWAYS there. Get comfortable with ssh, SQL*Plus, and vi (or vim).  They are your friends.

— James

Oracle Support Changes for EBS (part deux)

On Monday, Cliff Godwin announced some significant changes to E-Business Suite support. The official announcement is now available on MOS (Note: 1495337.1). The text of the announcement is below:

As part of Oracle’s continued commitment to our customers, we will be providing an exception for the first 13 months of Sustaining Support on Oracle E-Business Suite Release 11.5.10 (11i10), valid from December 1, 2013 – December 31, 2014. This exception support will be comprised of three components: (1) new fixes for Severity 1 production issues, (2) United States Form 1099 2013 year-end updates, and (3) payroll regulatory updates for the United States, Canada, United Kingdom, and Australia for fiscal years ending in 2014.


In addition, the Extended Support period for E-Business Suite Release 12.1 has been extended through December, 2018. Customers with an active Oracle Premier Support for Software contract will automatically be entitled to Extended Support deliverables for E-Business Suite 12.1.

NOTE: The changes to 11i Sustaining Support do NOT extend to the security patches. Oracle will NOT provide Quarterly CPU patch for 11i will come out in October, 2013. The one exception to this is that they will provide fixes for “P1” security issues.

— James

E-Business Suite Current Release and Roadmap

Current release is R12.1.3 (but you already knew that!). Enhancements coming with R12.2 include Online Patching (20 years in the making) based on a database feature specifically requested by the E-Business Suite group called “Edition-Based Redefinition”. The expectation is that you will be able to apply patches of any size with minimal downtime (less than an hour, target is more like 15 minutes).  (I will discuss this feature in a more in-depth posting later).

Other enhancements include integration with Endeca to provide an e-commerce shopping experience to many of your ERP business processes. (I’ve heard the “shopping for shoes” reference three times already at OpenWorld when discussing this feature). Cliff Godwin provided an interesting demo of this feature during his presentation earlier today. It is expected that this capability will be released “within the year”. Cliff made a point to indicate that initial releases will cover several modules (I believe it was eight at initial release) but that new modules and Endeca-related features should come along quickly (due to the rapid development cycles available with Endeca). He was unclear, however, as to whether the Endeca feature set will be available on releases prior to R12.2.

— James

Oracle Support Changes Announced for EBS

During his session earlier today, Cliff Godwin announced some significant changes to the E-Business Suite support deadlines. I will put together a more polished post later, but for now, here are the details:

EBS 11i (11.5.10.2) is STILL on Sustaining Support until December 31, 2013. However, they are making a few exceptions to the Sustaining Support policy. First, they will continue to provide bugfixes for Severity 1 production problems until December 31, 2014. Secondly, they will continue to provide updates for US Form 1099 through 2013 Year End. And finally, they are committing to provide Fiscal Year End 2014 Payroll updates for US, Canada, and UK.

For customers on Release 12.1, Oracle is waiving the Extended Support fees until December of 2018.

— James

MINOR CORRECTION: EBS 11i is not “still on sustaining support”. EBS 11i is actually on Extended Support until Nov 2013. (Thanks, Srini, for pointing this out!)

Impact of EBS R12.2 changes – WebLogic

A number of very smart people seem to think that the introduction of WebLogic is going to be a major “game changer” for E-Business Suite DBAs. There is certainly some truth to that thought. WebLogic is a completely different animal than the Apache or Oracle Application Server that we’ve gotten accustomed to in E-Business Suite 11i and R12.

But consider this. I suspect that most environments are fairly vanilla. When it comes to the basic degree of interaction that an E-Business Suite DBA has with the Applications Server, I suspect that the change will be largely transparent. Consider what you do with the current Applications Server product. Start and stop? That’s done through AutoConfig managed scripts. Basic configuration for EBS? That’s handled through AutoConfig. Why would we expect these things to change just because they’ve changed out the tool?

What will it change?

I’m certain that the log files will be different. The naming convention will probably change and the location of the files might change. The content of the files will certainly be different. As will the configuration files (but, again, I would expect those to be AutoConfig managed).

The big place where you will notice the WebLogic change (from an Administrator standpoint) is if you’re trying to do something else with it. If you’re dealing with Discoverer or deploying APEX, for example, you’ll certainly get up-close-and-personal with WebLogic.

So, should you be afraid of the WebLogic change? I don’t think so. Yes, custom deployments (anything that actually requires you to “deep-dive” into the configuration of WebLogic) will have a learning curve. That said, many of the components of Oracle Fusion Middleware already use WebLogic and, if you’re doing any custom deployments, odds are you’re also already dealing with WebLogic elsewhere and will have some familiarity by the time you go to tie it into E-Business Suite.

When you factor in these things with the fact that WebLogic is a more mature and overall better product than the current applications server used in E-Business Suite, I think that the change is probably a good thing.

— James

Speculation about EBS Release 12.2

Floyd Teeter raises some good points in his blog posting out today. You can read the full posting here (http://orclville.blogspot.com/2012/08/i-wonder-what-tomorrow-has-in-mind-for.html). Primarily, that we won’t actually have EBS R12.2 released during OpenWorld (as many of us were hoping).

Don’t get me wrong, there will certainly be some good EBS R12.2 information out there. Oracle put together a very informative presentation and discussion surrounding the patching changes at Collaborate in Las Vegas this past spring. You can almost certainly bet that there will be an updated version at OpenWorld.

But, considering that the closed Beta program is still underway and the Early Adopter program hasn’t started, any path of deduction should tell you that you’re not going to have a R12.2 “GA” announcement for a few months at best. Which most means that sometime around Collaborate 2013 (Denver) would be a decent guess.

— James

Listing Installed Packages on Linux

First, let me mention that, unless otherwise indicated, when I blog about Linux it will be about the RPM-based distributions that are certified with the Oracle Database (RedHat Enterprise Linux, Oracle Enterprise Linux).

Normally, when you’re looking to see which packages are installed on Linux (RedHat, Oracle, CentOS), you would use this command:

rpm -qa

Unfortunately, the standard output of that command omits alot of useful information. It may or may not indicate if you have the 32 or 64 bit version of a package installed, for example.

So, for a command that will show you which packages are installed in a format that looks like the name of the RPM file:

rpm -qa --queryformat \
"%{NAME}-%{VERSION}-%{RELEASE}.%{ARCH}.rpm\n" |\
sort > pkglist_`date +%Y%m%d-%H%M`.txt

— James