An Oracle Support Gotcha When Upgrading EBS R12 to 11.2.0.2

If you are not aware, My Oracle Support enforces the limits to patch access during extended support of a product. If you try to download a patch that is in extended support, you get an error message telling you to contact Support Sales. I have no problem with this in general. However, I do have a problem when I cannot get patches that are required for a product still under premier support.

A major example of this occurs when trying to upgrade R12 to 11.2.0.2 because Oracle 11.2.0.2 uses time zone version 14 which means I need to upgrade the R12 tech stack to use time zone version 14 files. According to note 563019.1, this means applying the 10.1.0.5 time zone patch (9742718) to the 10.1.2 Oracle Home in the apps tier. Unfortunately, in spite the fact that R12 is still under premier support, it is not possible to download the required patch since 10.1 is in extended support.

This has not always been the case, If you were upgrading to 11.2.0.1, you would require the version 11 time zone patch (8524113). You can download this patch with a valid EBS CSI. You can also download patch 7695050, the required DST pre-req patch for time zone versions greater than 10. You cannot download version 13, 14 or 15 (the most current) patches at this time.

Hopefully, Oracle will get this resolved soon. Until then, all you can do is open an SR and have the analyst send you the required patch. Expect several iterations of them telling you to contact sales while you patiently explain this is to patch R12 which is still in premier support.

I will update this blog as soon as I can find a better solution (or Oracle fixes the access to the patch).

Update 8 March 2011: The patches still appear to be blocked, but I have been assured that Oracle is working to resolve the issue internally. They expect the patches to be available for download soon.

Update 31 March 2011: Still not available.  Hopefully this will be resolved before Collaborate.

Update 14 April 2011: Still not available.

My Oracle Support and Patches

Update: This issue has been resolved, you should no longer have problems with patch downloads from MOS. Also, if you have not looked at supporthtml.oracle.com (the non flash version), it has been dramatically improved.

Since the switch to My Oracle Support, I have been unable to download patches from E-Business Suite 12.0 via the My Oracle Support pages (both flash – it seems to only give me the R12 that points to 12.1, and html – it doesn’t give an EBS patches). Fortunately, the html version of updates.oracle.com still works. An easy way to connect is with http://bit.ly/OraclePatches.   You will still need to be logged in to the Oracle SSO account that is linked to My Oracle Support.

Printer setup for the E-Business Suite in Oracle Enterprise Linux Part 2 Migrating

Now that we have the printers all added, the last thing we want to do is have to rekey them all on every server.  Every time you do a manual migration, you increase the chance for errors.

We can use system-config-printer to migrate our queues at the linux level and FNDLOAD to migrate the queues in the E-Business Suite.  However, there is one manual step you must go through if you added any PPD files.

The first step in our process is to download the printers.

For linux (as root), enter the command:

system-config-printer-tui –Xexport > printers.xml

For the E-Business Suite (as oracle with the environment set for your apps tier), enter the command:

FNDLOAD apps/$APPS 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcppinf.lct source_printer_def.ldt FND_PRINTER

FNDLOAD apps/apps_password 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcppinf.lct source_printer_def.ldt FND_PRINTER

If you read the first part of this post on adding custom printers, you will recall that I said to keep track of the order that you added the PPD files.  You need to repeat the load of the PPD files in the same order on every system to which you are migrating the printers.  If you did not record the order, look in printers.xml for the printer_id tags, the custom ppd entries will be ppd#, e.g. ppd2.  The surrounding tag will be the name of the queue, so you should be able to reconstruct the order to add the PPD files.
On each system to which you wish to migrate these queues,

copy printers.xml and source_printer_def.ldt

For linux (as root):

system-config-printer-tui ==Xexport > backup-printers.xml
system-config-printer-tui –Ximport < printers.xml
service cups restart

Note: You are interrupting print services, make sure that you are doing it an appropriate time.
After you have completed this step, the queues will be the same on both systems.

For the E-Business Suite (as oracle with the environment set for the apps tier):

FNDLOAD apps/apps_password 0 Y DOWNLOAD $FND_TOP/patch/115/import/afcppinf.lct ${TWO_TASK}_printer_def.ldt FND_PRINTER

FNDLOAD apps/apps_password 0 Y UPLOAD $FND_TOP/patch/115/import/afcppinf.lct source_printer_def.ldt FND_PRINTER

This will merge the printers from the source to the new system.  Any printers that already exist on the new system should still be there, but you may have wiped out the linux queue in the previous step.