Migrating OVPI database

From Sybase to Oracle

                                                                        By

logo.jpgSamartha InfoSolutions Pvt Ltd.

#190, 2nd phase, 2nd Stage,
WOC Road, Service Road,
Bangalore  560 086
Karnataka, INDIA.

Contact Us

 

 

 

 

 

 

 

 

 

 

 

 

 

1. Requirement

Migrating HP’s OVPI database from Sybase to Oracle

Reasons:

  1. Data size is growing more
  2. No. of nodes are increased
  3. The performance is poor

2. Considered Version

 

OVPI Version    :                                   5.3

Oracle               :                                   10g

Sybase             :                                   15.01

OS                   :                                   Windows 2003 Server

3. Deployment Architecture

 


4. System Backup

 

It is recommended to take system backup before performing any changes.

 

  1. Complete system back up of both the Systems.
  2. Application backup of Source Server
  3. Application backup of Destination Server
  4. Database backup of Source Server
  5. Database backup of Destination Server

5. Solution Configurations

 

  1. The required latest patches are applied to the destination system
  2. The required Datapipes & Report packs (Default & Custom Developed) are installed at destination server including required views.
  3. The Datapipes and Report packs are upgraded to the latest version.

 

6. Step by Step migration actions

 

  1. Stop the trendtimer in source and destination servers.
  2. Make sure that Oracle is running on destination server with DB mode as open.
  3. Add the source server as satellite server in destination server.
  4. If the data storage in source server is large; then run the indexmaint in force mode to fix up the index issues.
  5. Configure the trendcopy policy to copy all the tables from source server to destination server

trendcopy -s PRIMARY_DB -S BACKUP_DB

NOTE: PRIMAY_DB is source DB [satellite server] and BACKUP_DB is destination DB [central server]

  1. Copy the trendtimer.sched file from source server to destination server.
  2. Re-start Database and web access server in destination server.
  3. Start the collection in destination server by starting the trendtimer services.
  4. Wait for few hours, so that central server can poll and collect the data.
  5. Verify the NRT reports with all the KPI values.
  6. Wait for at least 2 days and verify the daily / yesterday reports.
  7. Similarly verify the weekly / monthly reports if any.