Issue 3 after Migration from 5.0 to 5.5 CU3+RU#01

[[email protected]]

Issue 3 after Migration from 5.0 to 5.5 CU3+RU#01


3. Full Audit (Action) -
Documents (Smartlinks) -
Error Message: - java.lang.NullPointerException

Error Stacktrace: - java.lang.NullPointerException
at glog.ejb.finderset.db.FinderSetPK.hashCode(FinderS etPK.java:51)
at weblogic.ejb20.locks.ExclusiveLockManager.getBucke tForPk(ExclusiveLockManager.java:101)
at weblogic.ejb20.locks.ExclusiveLockManager.getBucke tForPk(ExclusiveLockManager.java:105)
at weblogic.ejb20.locks.ExclusiveLockManager.getOwner (ExclusiveLockManager.java:229)
at weblogic.ejb20.manager.ExclusiveEntityManager.alre adyCached(ExclusiveEntityManager.java:1277)

Note for Full Audit action: - From Finder Result page if you click this action, on the resultant page with this reported error, if you click on the OTM image on the left top corner of the page (Usually after clicking this area you would see the associated XML for this) I could see the the Finder Result page of Audit Trail. This is happening on Default Finder Pages however this is not happening on an OTM 5.5 CU3 Freshly installed setup.

Note for Documents Smartlink: - From Shipment Finder Result page if you click this action, on the resultant page with this reported error, if you click on the OTM image on the left top corner of the page (Usually after clicking this area you would see the associated XML for this) I could see the the Finder Result page of Document associated with the shipment. This is happening on Default Finder Pages however this is not happening on an OTM 5.5 CU3 Freshly installed setup.

And finally Issue No. 4 - "Set Appointment" action from Order Release is also not, which is already reported (http://www.otmfaq.com/forums/f20/jav...exception-503/)

Please let us know if anybody encountered these issues after migration from 5.0 to 5.5 CU3 release, they could resolve these.

Thanks very much in advance,

Regards,
Suresh

[ianlo]

Re: Issue 3 after Migration from 5.0 to 5.5 CU3+RU#01

Hi Suresh

I have encountered a similiar issue where I get a null pointer exception when viewing a full audit of a business object.

What we have encountered was that if the full audit was done from a View of the object, it is ok.

I have raised this issue with Oracle Support and I would strongly recommend that you raise it too so that your issue can be looked into as well

Ian

[[email protected]]

Re: Issue 3 after Migration from 5.0 to 5.5 CU3+RU#01

Thanks Ian for the information. Its behaving exactly the same way you have described.
Please let us know if you have received any resolution for this issue from Oracle?

Regards,
Suresh

[ianlo]

Re: Issue 3 after Migration from 5.0 to 5.5 CU3+RU#01

Hi Suresh,

Oracle support has confirmed it is a bug and they are tracking the status. It may come out in CU3 RU2 hopefully!

[[email protected]]

Re: Issue 3 after Migration from 5.0 to 5.5 CU3+RU#01

Thanks Ian.
Do you have any feedback on the issues that exists from your sites where OTM 55 CU3 is installed.

Based on the issues encountered, do you think CU3 is a stable Release to apply on.

- Thanks,
Suresh

[ianlo]

Re: Issue 3 after Migration from 5.0 to 5.5 CU3+RU#01

Thanks Ian.
Do you have any feedback on the issues that exists from your sites where OTM 55 CU3 is installed.

Based on the issues encountered, do you think CU3 is a stable Release to apply on.

- Thanks,
Suresh

Hi Suresh,

Thats a difficult question to answer as each implementation will have its own fair share of issues to be resolved. I can only give you some memorable ones however I cannot guarantee that you will/will not encounter them. The best way to do this is through multiple rounds of regression testing.

1) Implement 5.5 in test env
2) Execute detailed regression testing
3) Identify and record issues from (2) and fix them
4) Retest (until no more issues)
5) Rehearse migration
6) Fix issues
7) Rehearse migration (until confident)

That was our approach and we took no less than 3 months to test and re-test and 1 solid month of migration rehearsals. Even then, we had issues during the migration!

What I can share is this:

1) Watch out for integration - files with UTF-8 BOM will be rejected in 5.5
2) Watch out for Agents and Direct SQLs executing in them - esp note that $Gid is now $gid!
3) Watch out for your custom stored procedures / triggers (if any) - schema changes have caused me some stomach aches.
4) Test, test, test and RE-TEST!
5) Pray and hope for a smooth migration

Hope this helps!

Ian

[[email protected]]

Re: Issue 3 after Migration from 5.0 to 5.5 CU3+RU#01

Hi Ian,

Yes I agree to your points what you have expressed.

Thanks very much for putting your valuable time to provide this excellent suggestion, experiences, points to take care.

Regards,
Suresh

[cwarner]

Re: Issue 3 after Migration from 5.0 to 5.5 CU3+RU#01

Just another note, this is still not fixed, even in CU3 RU3.

[ianlo]

Re: Issue 3 after Migration from 5.0 to 5.5 CU3+RU#01

Hi cwarner,Thanks for the update! All I got on Metalink was that they will be fixing this. Looks like we have to wait for CU04!Ian

[cwarner]

Re: Issue 3 after Migration from 5.0 to 5.5 CU3+RU#01

I've requested a one off patch, and mentioned this thread in the service request. Would that patch be something you would find useful?