Kbase P125435: Where can I find the necessary steps to migrate my OE Management 3.1A installation to 3.1B or 3.1C.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/14/2010 |
|
Status: Verified
GOAL:
Where can I find the necessary steps to migrate my OE Management 3.1A installation to 3.1B or 3.1C.
GOAL:
What are the necessary steps to migrate OE Management 3.1A to 3.1B or 3.1C?
GOAL:
How to migrate OpenEdge Management from 3.1B to 3.1C without losing all our configurations?
FACT(s) (Environment):
UNIX
Windows
OpenEdge Management 3.1x
FIX:
The readme file located in the OE Management Installation directory provides this information. It is copied below (modified slightly for clarification purposes):
The steps are the same when upgrading from 3.1A to 3.1C.
1. Fathom Management 3.1A Migration to OpenEdge Management 3.1B ===============================================================
Migrating the 3.1A Resources and Trending database data to version 3.1B
RN#: 101B-00110
===============
Preparations steps:
1. Shutdown AdminServer and FathomTrend database.
2. Truncate Bi on the FathomTrend database
($DLC101A/bin/proutil fathom -C truncate BI)
3. Backup the 3.1A FathomTrend database using probkup. This must be done before moving or removing the 3.1A/10.1A install. For the script to work the backup needs to have been done using the 10.1A environment and probkup utility.
4. Copy the 3.1A installation tree to a backup location.
5. If you plan to monitor the same databases and other resources in 3.1B, then copy the following files to a backup location:
5.1 $DLC101A/properties/agent.properties - to preserve database agent port setting
5.2 $DLC101A/properties/smdatabase.properties - to preserve scripted database resource definition
5.3 $DLC101A/properties/ubroker.properties - to preserve OpenEdge server definitions like AppServer, WebSpeed, NameServer etc.
5.4 $DLC101A/properties/conmgr.properties - to preserve managed database definitions
Some of the data types in the trend database have had to be widened in 3.1B.
The schema changed them from integer to int64 in order to accommodate 64 bit
VST values. The 3.1B database is built with type 2 storage and 4KB block size. To salvage The data from the 3.1A database it needs to be dumped and then loaded into the 3.1B database.
Before doing the dump and load consideration should be given to running the
data compaction job on the 3.1A database. The script provided to do the
dump and load uses ASCII dump and load. There is a 2GB table size limit on
the ASCII representation of tables when using ASCII dump and load.
Only databases that have a schema updated to the 3.1A level are compatible with this procedure. This includes 3.0A04 installs after all manual migration steps to update the schema to the level shipped with that release have been performed.
The script files to assist the dump and load process are shipped with OpenEdge Management 3.1B and are run in that environment.
$FATHOM/perl/scripts/dbmigrate.*
$FATHOM/src/dbload*, dbdump*, dberasecf.*
Steps to migrate the data from the Fathom 3.1A trend database to the OpenEdge
Management 3.1B trend database:
1. Install 3.1B. If 3.1B is installed into the directory where 3.1A was, it
will make it easier to salvage the resource database contents. If this
is your choice, before installing 3.1B the 3.1A directory tree will need
to be deleted.
2. Start 10.1B AdminServer.
3. Go through initial OpenEdge Management 3.1B configuration pages. Note that the building of the Trend database will not fully complete until the AdminServer is shutdown (in the next step).
4. Shutdown AdminServer and stop FathomTrend database if it is started. On Windows (and possibly UNIX), the Trend db won't be started if the AdminServer hasn't been stopped & restarted since completing the configuration pages.
5. Create two empty directories (anywhere on your server), one to hold a restored 3.1A temporary trend database and one to hold the dumpfiles. These directories must be empty before running the script.
6. Execute $DLC/bin/proenv (if on UNIX), or select the "Set OpenEdge Management Environment" icon fro.m the OpenEdge Management icon group on Windows.
7. Run $fathomInstallDir/perl/scripts/dbmigrate.sh or
%FATHOMINSTALLDIR%\perl\scripts\dbmigrate.bat
Steps to migrate Fathom 3.1A resource database, configurations and resource/job/alert definitions and results to OpenEdge Management 3.1B:
Before starting 10.1B adminserver:
1. Copy $FATHOM31A/config/fathom.o* files to $FATHOM31B/config location. Note: If you install OE Management 3.1B in the same location as 3.1A, then the path names in the resource databases will be the same.
2. Copy $FATHOM31A/fathomwork/reports, $FATHOM31A/fathomwork/jobs_results.out to corresponding $FATHOM31B location.
3. Copy backed up files from $DLC101A/properties (as per step 5 in preparation steps) to corresponding $DLC101B/properties.
4. Start the 10.1B AdminServer..