Thread: Error deploying OTM
View Single Post
  #2 (permalink)  
Old June 28th, 2007, 15:47
chrisplough's Avatar
chrisplough chrisplough is offline
Site Moderator
  
Join Date: Jun 2006
Location: West Chester, PA
Posts: 847
Blog Entries: 7
Thanks: 53
Thanked 205 Times in 124 Posts
Groans: 0
Groaned at 0 Times in 0 Posts
Rep Power: 10
chrisplough has a spectacular aura aboutchrisplough has a spectacular aura aboutchrisplough has a spectacular aura about
Send a message via AIM to chrisplough
Re: Error deploying OTM
Hello!

I've found that it's necessary to utilize a partitioned database with OTM v5.5 CU1 and above. While I haven't seen the official specs haven't changed (I believe), the recent patches appear to have been only tested on a partitioned database. If you're not able to move to a partitioned database, I'd recommend contacting Oracle Support in order to log this as a bug and get the issues resolved by development.

I know that the OTM development group was looking to drop support for non-partitioned databases at some point, so I definitely recommend moving in this direction for all new OTM instances.

Another point - for development instances, using Oracle Application Server is fine, but I strongly recommend against using it for production instances until it has been production proven. To put it simply, OTM has run on WebLogic for 8 years now and only for 6 months on OAS.

Thanks!
--Chris
__________________
Chris Plough
MavenWire

www.MavenWire.com
Reply With Quote