[chrisplough]

Hello!

Just a quick note to let everyone know that OTM v5.5 CU2 was released on 5/15/07 and is available on MetaLink as patch # 6052575.

The updates are much to numerous to list, but here's some of the larger ones:

• Updated UI
• Significant new functionality
  • Fusion Business Intelligence (i.e. Analytics)
  • Too many more to list
• TONS of integration changes
  • Significant Schema changes
  • Improved BPEL support
  • Improved Web Service support
  • Improved EBS/OTM Integration
• Improved Proxy Server support
• Improved OAS support
• SCA improvements

If you have a Metalink account, you can view the release notes here:

OTM v5.5 CU3 Release Notes

I have yet to install this and am not aware of any pitfalls or issues, but I'd love to hear any experiences out there. If you've installed this (or plan to), please share your tips with us.

Hope this helps!

--Chris

[chrisplough]

FYI - I've now installed this onto a client's site. So far, the everything has gone well, however, there were a couple of hitches during the installation of the patch:

When installing the CU3 patch, I received the error:

Incorrect OTM Version!
----------------------
This patch is not compatible with the version of OTM you have installed under

This was resolved by changing the following entries in the glog.properties file from:

glog.software.version=Otmv552
glog.software.patch.version=Otmv552-P20061218

To:

glog.software.version=OTMv55
glog.software.patch.version=OTMv55-CU02

Note: This should only occur if your OTM installation is based off of the v5.5.2 installer and was not updated manually to CU02.

Next while running the installer, it errored out and crashed with the message:

Invocation of this Java Application has caused an InvocationTargetException. This application will now exit. (LAX)

Stack Trace:
java.lang.InternalError: jzentry == 0,
 jzfile = -849907184,
 total = 58991,
 name = /opt/otm55mwtest/glog/gc3webapp/WEB-INF/lib/glogserver.jar,
 i = 17,
 message = invalid LOC header (bad signature)
        at java.util.zip.ZipFile$3.nextElement(Unknown Source)
        at java.util.zip.ZipFile$3.nextElement(Unknown Source)
        at ZeroGy.d(DashoA8113)
        at ZeroGy.a(DashoA8113)
        at ZeroGy.b(DashoA8113)
        at ZeroGd.g(DashoA8113)
        at com.zerog.ia.installer.actions.InstallUninstaller.c(DashoA8113)
        at com.zerog.ia.installer.actions.InstallUninstaller.installSelf(DashoA8113)
        at com.zerog.ia.installer.Action.install(DashoA8113)
        at com.zerog.ia.installer.actions.InstallDirectory.install(DashoA8113)
        at com.zerog.ia.installer.Action.install(DashoA8113)
        at com.zerog.ia.installer.GhostDirectory.install(DashoA8113)
        at com.zerog.ia.installer.Installer.install(DashoA8113)
        at com.zerog.ia.installer.LifeCycleManager.a(DashoA8113)
        at com.zerog.ia.installer.LifeCycleManager.a(DashoA8113)
        at com.zerog.ia.installer.Main.main(DashoA8113)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
        at java.lang.reflect.Method.invoke(Unknown Source)
        at com.zerog.lax.LAX.launch(DashoA8113)
        at com.zerog.lax.LAX.main(DashoA8113)
This Application has Unexpectedly Quit: Invocation of this Java Application has caused an InvocationTargetException. This application will now exit. (LAX)

This is a known issue - just re-run the patch and it will succeed the 2nd time.

Finally, when applying the DB portion of the OTM patch, it notifies you that a particular patch (5730086) will not be applied automatically, due to potential performance issues.

Here's the details of patch 5730086:

Description: Shipment actions do not work well on shipments with arbitraries.

Details: Actions such as Recalculate Cost and Assign Rate can be performed on shipments with arbitraries. Also added an order movement action to Build Shipments and select/refine shipments on a leg.

If you decide to apply this patch, just sqlplus into your OTM DB as glogowner and run the following:

@create_dbpatch_55
exec dbpatch_55.apply_patch('patch5730086');
drop package dbpatch_55;

Hope this helps!
--Chris

[chrisplough]

Hello!

It appears that I spoke a bit too soon. We've found two known issues with the CU3 installation (Oracle notes 432983.1 and 432847.1).

The first issue (432983.1) is easy to resolve - just re-run the patch installer and it will work the second time (covered earlier).

The second issue (432847.1) requires some manual steps to resolve:

1. Shutdown OTM
2. Log into the application server and go to the <otm_install_dir>/glog/oracle/script8 directory. Once there log into the database as glogowner using sqlplus and run the following command:

   SQL> exec vpd_pre_run.enable_all_policies;

3. Restart the OTM DB
4. Startup OTM

If you absolutely need to avoid restarting the db, web and app, log into the database using sqlplus as sys and flush the shared_pool:

SQL> alter system flush shared_pool;

Note: Be sure to log out of the database as sys before running any of the the remaining installation steps for CU-03.

Hope this helps!

--Chris

[chrisplough]

Hello all!

I found more CU3 documents available within Oracle's public site - so you can view the release documents and information about the additional functionality (such as FTI) included:

• OTM v5.5 CU3 Release Notes
• OTM v5.5 CU3 Additional Functionality

Thanks!
--Chris