Maximo Wire - The IBM Maximo Help & Discussion Forum
February 10, 2012, 04:31:46 am *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Welcome to Maximo Wire, the IBM Maximo help forum. Feel free to register and ask any Maximo related questions you like.
 
  Home Help Search Login Register  
*
Pages: [1]   Go Down
  Print  
Author Topic: Maximo 7 db transfer  (Read 3039 times)
0 Members and 2 Guests are viewing this topic.
webbp2
Newbie
*

Karma: 0
Posts: 7


View Profile
« on: August 04, 2009, 10:45:44 am »

Maximo 7. Websphere. SQL 2005

I have a Maximo 7 MAM runnning in a Dev environment. I also have a database
backup from a Production system from elsewhere. (Both on same release level)

As the majority of Maximo's properties are now held in the database, is there
anyway of restoring the PROD version into the DEV environment, then changing the
relevant properties so that Maximo will run?

There are a few perameters in the Maximo.Properties file that would need
changing (then re-encrypting) but what properties in the database would need
changing?

Thank you in advance

Regards

Paul
Logged
amdisuk
Administrator
Full Member
*****

Karma: -1
Posts: 198


allandonaldson@hotmail.com
View Profile WWW
« Reply #1 on: August 06, 2009, 07:37:11 am »

I'm no expert on Maximo 7 but we used to use a tool that allowed you to visually move records from one database to another. There aren't too many tables that converting but it is a time consuming job.
Logged

Big Al
mxes_installer
Newbie
*

Karma: 1
Posts: 6



View Profile
« Reply #2 on: September 01, 2009, 07:14:01 am »


Hi webbp2,

I have not so much experience with DB2, but we have the same problem with oracle like you. And we solved the problem.

We have only one parameter in the maximo.properties. The database value with port and owner. We checked / change this value to the right one and before we start the application we have change some parameters with a sql tool in the database. Search in the table MAXPROPVALUE after your old database ip and make a update.

mxes_installer
Logged
srihari.varadarajan
Newbie
*

Karma: 1
Posts: 11


View Profile
« Reply #3 on: February 23, 2010, 10:59:06 am »

Even I am new to Maximo but my understanding is that we can use migration manager application of 7.1 for your requirement. The docs required to understand migration manager are available in IBM site. I

Does this answer your question?
Logged
Ethen
Global Moderator
Sr. Member
*****

Karma: 16
Posts: 299



View Profile WWW
« Reply #4 on: March 02, 2010, 07:58:45 am »

do u want to run prod and dev from same database instance or u want to copy prod database dump into dev (or dev to prod ) and run prod and dev with two  diff database instances..
Logged

regards,

Ethen...
Razor007
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #5 on: March 07, 2010, 08:25:36 pm »

I guess the guy had already figured out, it is a very old post... But if some one is looking for some thing similar -  there is a post on maximokb.com and on IBM it is http://www-01.ibm.com/support/docview.wss?rs=3503&context=SS6HJK&dc=DB560&dc=DB520&uid=swg21382026&loc=en_US&cs=UTF-8&lang=en&rss=ct3503tivoli
Logged
sckl
Newbie
*

Karma: 0
Posts: 5


View Profile
« Reply #6 on: July 05, 2010, 09:01:21 am »

we're using following sql command after transferring the productive environment into the test environment (sample)

update maxpropvalue set propvalue = 'http://maximourl/meaweb' where propname = 'mxe.int.webappurl';
update maxpropvalue set propvalue = 'InstanceName' where propname = 'Database.Oracle.InstanceName';
update maxpropvalue set propvalue = 'FQDN hostname' where propname = 'mxe.hostname';
update maxpropvalue set propvalue = 'FQDN hostname' where propname = 'WAS.DeploymentManagerHostName';
update maxpropvalue set propvalue = 'FQDN hostname' where propname = 'WAS.WebServerHostName';
update maxpropvalue set propvalue = 'FQDN hostname' where propname = 'Database.Oracle.ServerHostName';
update maxpropvalue set propvalue = 'jdbc:oracle:thin:@FQDN hostname:1521:InstanceName' where propname = 'mxe.db.url';
commit;

may it helps you
Logged
webbp2
Newbie
*

Karma: 0
Posts: 7


View Profile
« Reply #7 on: September 02, 2010, 10:57:01 am »

Dear All,

Thanks for the replies.

After some investigation I found the following.
Using seperate Maximo instances on their own VM Machines, using the same Port numbers, passwords etc.

Properties that would require changing would be:-

From maxpropvalue.propname


Database.SQL.DatabaseName
Database.SQL.ServerHostName
mxe.adminmode.logoutmin
mxe.db.url
mxe.doclink.path01
WAS.DeploymentManagerHostName
WAS.WebServerHostName

Although we have also found you can do a straight backup and restore from one SQL db to another as long as you do not rebuild the EAR files!
Logged
KiranK
Newbie
*

Karma: 2
Posts: 5


View Profile
« Reply #8 on: October 24, 2011, 07:21:11 pm »

This is summed up pretty much well here.

https://www-304.ibm.com/support/docview.wss?uid=swg21392272
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Recent

TinyPortal v1.0 beta 4 © Bloc
Powered by MySQL Powered by PHP Powered by SMF 1.1.15 | SMF © 2011, Simple Machines Valid XHTML 1.0! Valid CSS!