View Single Post
  #2 (permalink)  
Old December 21st, 2007, 15:27
nick.polites nick.polites is offline
Senior Member and Blogger
 
Join Date: Nov 2007
Location: Drexel Hill, PA
Posts: 240
Thanks: 0
Thanked 35 Times in 35 Posts
Groans: 0
Groaned at 0 Times in 0 Posts
Rep Power: 2
nick.polites is on a distinguished road
Re: [NEWS] OTM v5.5 CU04 has been released

After applying CU-4 we saw the following errors when applying the dbpatch_55

Adding patch data content
Updating general content...
(Call for updating content is ./update_content.sh /otm/glog/config V55P)

GLOGOWNER connection set to dbaglogowner
REPORTOWNER connection set to dbareportowner

java.io.FileNotFoundException: /otm/glog/config/glog.patches.properties (No such file or directory)


The installer is supposed to remove the glog.patches.properties file after each CU upgrade, however something else is now referencing it and as it doesn’t exist, it throws the stack trace. I believe that you can ignore the errors and the database should be upgraded correctly. To fix the error, you can create a blank file named glog.patches.properties in your OTM/glog/config directory and re-run dbpatch_55.sql.

Also there is a typo in the release notes for this patch under the section on removing a weblogic file.

It says the following:

File To Be Removed for WebLogic
You must remove a file from the WebLogic installation because of a code conflict between it and the latest JDBC drivers with which OTM ships. The simplest and safest way to do this is to rename the file. The file in question is:
<weblogic_install_path>/server/lib/odbc14.jar
rename it to be:
<weblogic_install_path>/server/lib/odbc14.jar.bak


The filename is incorrect, it is ojdbc14.jar.

__________________
MavenWire Hosting Admin
Over 7 years of OTM experience
The Oracle OTM / G-Log GC3 Experts
Offering Incubator and Production OTM instances
www.mavenwire.com
Reply With Quote