mxe.db.url global value is not updated when migrating databases

Flash (Alert)


Abstract

When migrating a database from one instance down into another instance the global value will remain the same as it was for the previous database.

Content

After you have migrated your database from one instance to another. For example Production to Development the global value for the mxe.db.url will not be updated to match the current cached value being pulled from the maximo.properties. You will see this when you log in to Maximo and go to the system properties application and filter for mxe.db.url the global value and the cached value will not match.

When migrating your databases ensure the global value is updated or cleared before starting up the refreshed environment. You can do this via a SQL tool.

e.g

update maxpropvalue set propvalue ="correctjdbstring" where propname ='mxe.db.url'

Once done start up your Maximo environment and the JDBC connection strings should be in sync

Cross reference information
Segment Product Component Platform Version Edition
Systems and Asset Management Tivoli Service Request Manager Not Applicable 7.1, 7.1.2, 7.2, 7.2.1, 7.5
Systems and Asset Management Tivoli Change and Configuration Management Database 7.1, 7.1.1, 7.1.2, 7.2, 7.2.1, 7.2.2, 7.5
Systems and Asset Management Tivoli Asset Management for IT Not Applicable 7.1, 7.1.1, 7.1.2, 7.2, 7.2.1, 7.2.2, 7.5
Systems and Asset Management IBM SmartCloud Control Desk 7.5, 7.5.1

Rate this page:

(0 users)Average rating

Document information


More support for:

IBM Maximo Asset Management
System Related

Software version:

7.1.1, 7.5

Operating system(s):

Platform Independent

Reference #:

1639160

Modified date:

2014-07-30

Translate my page

Machine Translation

Content navigation