It's all about the answers!

Ask a question

How to Restore RAM Production DB instance to RAM Dev instance


anoop mc (74811188221) | asked Sep 05 '14, 6:11 a.m.
 Hi,

We have a RAM production instance running on version -7.5.1 using a DB2 database by name UISRAMDB (which has lot of data in it)

Similarily we have another RAM dev instance which is running on version - 7.5.2.1 Configured to use DB2 Database (it is a new installation) (Three Databases has been created as a part of installation - RAMDB,RTCDB and JTSDB)

Our Requirement is ?

We want the production DB instance to be mirrored to the prepod instance to complete the testing ?

What we have done >>>

1. In Dev instance we have created an empty database by same name UISRAMDB.
2. Took the backup of the PROD DB instance UISRAMDB and copied the file over to the dev server.
3. Ran the restore command from the Dev Server.

My question here is how will we make Dev RAM point to the database (UISRAMDB) in which we have restored the production data to.

6 answers



permanent link
Ary Zhang (2324) | answered Sep 07 '14, 9:50 p.m.
JAZZ DEVELOPER
hi,
Please still use RAM setup. Go back to the database configuration step and point to the Dev RAM db.
Thanks a lot.

permanent link
anoop mc (74811188221) | answered Sep 09 '14, 10:16 a.m.
  Hi,

The production RAM is on 7.5.1 and if I remember in the older RAM we need only two databases ie one for RAM and one for RTC 

Here we have only two databases 1. UISRAMDB and other one is 2. JTSDB

These two databases we need to restore to the new instance of RAM Version 7.5.2.1 with DB2 10.1

With the new RAM setup I noticed we have to create three dbs RAM,CCM,JTS 

What I have done now is on the new server from DB2 command window ran the db2 restore command against the prod database back which is copied over to the new RAM server.

E:\Softwares\UISRAMDB backup12-08-2014>db2 restore database UISRAMDB taken at 20140812134339
SQL2555I  The database was restored and then successfully upgraded to the
current DB2 release where you issued the RESTORE DATABASE command.

E:\Softwares\RTCDB Backup12-08-2014>db2 restore database RTCDB taken at 20140812132738
SQL2555I  The database was restored and then successfully upgraded to the
current DB2 release where you issued the RESTORE DATABASE command.

During RAM 7.5.2.1 setup I think I can specify the current UISRAMDB ad RAM DB and RTCDB as CCMDB.

What about JTS DB ? 

permanent link
anoop mc (74811188221) | answered Sep 10 '14, 10:48 a.m.
 Hi,

I followed the step you suggested -- Go back to the database configuration step and point to the Dev RAM db. Got the below setup page. 

Look like we need to copy the RTC 2.0 zip file file from the 7.5.1.1 RAM instance and proceed with the setup

Currently I am stuck at the below window.

ram_db_migrate

permanent link
anoop mc (74811188221) | answered Sep 11 '14, 12:54 a.m.
Install location for RTC 2.0 I just specified a folder similar to the one showing for RTC 3.0 and and 4.0 

E:\Program Files (x86)\IBM\WebSphere\profiles\AppSrv01\config\cells\INBLR-3DBPDEVNode01Cell\RTC\server1

Similarly entered the paths for RTC and JTS cliked Migrate Button which took me to me the last page with out any warnings.

Another question I have is ?

Do we need to copy the RAM_Persist folder from the production server and replace the existing persist folder content with the old one ?





permanent link
anoop mc (74811188221) | answered Sep 19 '14, 2:28 p.m.
 Hi,

After restoring the databases and running the RAM setup again we are getting the below error.

ram_db_err

permanent link
anoop mc (74811188221) | answered Sep 30 '14, 8:43 a.m.
Please find the below message when we click on Migrate button

Migration Required
Couldn't find migration path between current version and desired version. Current repository version is 7.5.1.1.v20120730tf5 and software installed is at version 7.5.1.1.v20120229.

The Rational Asset Manager repository is not the correct version.

IBM Rational Asset Manager 7.5.1.1

The current database version is 7.5.1.1.v20120730tf5 and the software that is installed expects the database version 7.5.1.1.v20120229.

Click the Migrate button to perform the migration. Before migrating, back up the database and persistence storage in case there are errors during migration.     

We have tried redoing the whole setup and still have the same issue.


Comments
anoop mc commented Sep 30 '14, 8:46 a.m.

 Any suggestion for applying a particular fix pack would be of great help. We tried applying a cumulative fix pack which did not fix the issue. 



Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.