Easy upgrade path from CMSDK 9.0.4.2 to 9.0.4.6

Each Oracle CMSDK 9.0.4.6.x release comes with three different installation options.
  1. Create a new Oracle CMSDK 9.0.4.6 schema
  2. Upgrade from an existing Oracle CMSDK 9.0.4.2 installation
  3. Patch an existing 9.0.4.6.x installation

The upgrade process is divided into three phases: the Pre-SchemaUpgrade, Offline-SchemaUpgrade and Post-SchemaUpgrade phases.

Within each of these phases, a list of upgrade actions are performed in a specific sequence. The time required to complete the entire upgrade process depends on the size and complexity of the existing Oracle CMSDK schema. To minimize the down time of a production system, most of the long running actions are executed during either the Pre-SchemaUpgrade or the Post-SchemaUpgrade phase, because during these phases the system can remain in production. It is only during the Offline-SchemaUpgrade phase that the Oracle CMSDK system must be completely shut down.

Here is a brief overview of the three phases.

Pre-SchemaUpgrade

  • Executes while 9.0.4.2 system is running
  • Performs a number of long running actions
  • Can be executed multiple times before beginning next phase
Offline-SchemaUpgrade
  • 9.0.4.2 system must be shut down as this phase begins
  • Optimized to complete in a relatively short period of time
  • Pre-SchemaUpgrade actions are executed again, to process any "deltas" since the last time that phase completed
  • Offline-SchemaUpgrade actions are executed only once
Post-SchemaUpgrade
  • Can execute while 9.0.4.6 system is running
  • Performs actions which are largely optimizations
Our internal tests showed that a CMSDK system with 10 million documents required an actual down time of less than 15 minutes and a total upgrade time of roughly 25 hours. Again, this can vary based on other factors.

Detailed upgrade and installation instructions can be found in the Readme bundled with each release.

Comments:

Hi,

I have chosen the first option =>Create a new Oracle CMSDK 9.0.4.6 schema using "createscheme.bat"

However, I got the following error, if you could suggest a resolution would be great. I am cracking my head against this issue for few days now..

"********** IFS CredentialManager is being used **********"
XML Parser started ...
SchemaCreator arguments = [propertiesFile=Environment, actionsFile=C:\TEMP\17086
605\install\config\CoreSchemaSeed.xml], Exception traces ---->
java.util.MissingResourceException: Can't find bundle for base name Environment,
locale en_GB
at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle
.java:1499)
at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1322)

Thanks,
Balu

Posted by guest on June 11, 2014 at 04:12 PM PDT #

Based on your exception, I guess you are trying to install CMSDK in the UK with a LOCALE set to en_GB. Can you try to set the LOCALE to en_US or use no LOCALE during the CMSDK schema creation? Will that work?

Posted by Frank Closheim on June 13, 2014 at 03:30 AM PDT #

Post a Comment:
  • HTML Syntax: NOT allowed
About

Latest news, best practices, examples and product updates for CMSDK.

Search

Archives
« April 2015
SunMonTueWedThuFriSat
   
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
  
       
Today