Hi! So many objects in Maximo are referential and LD is certainly one. You can look at the meta data in the maxrelationship table to get an idea about static relationships. To respond to your question, yes you will have referential issues if you neglect to bring the ld table(s) over. I would say that the issues are potentially manageable, but the risk is that you would break another mbo operation internally and perhaps not even know (because there aren't necessarily error traps for things that logically should never occur). You might try an alternative solution (replace the contents with shorter descriptions?)
Anyway, just saying probably not a good approach to drop the table entirely...
------------------------------
keith simmons
Aquitas Solutions
------------------------------
Original Message:
Sent: 02-23-2023 11:55
From: vineet joshi
Subject: Instructions for refreshing Maximo 7.6 Dev with Production data and settings
Hello Sun
I wanted Long Description table to be excluded from the refresh which I believe should not cause much of referential integrity issues.
This table has grown enormous over period of time, and I don't want my Dev database to be upgraded (size wise) every time during production refresh.
Thanks
VJ
------------------------------
vineet joshi
Original Message:
Sent: 02-22-2023 01:36
From: sun kim
Subject: Instructions for refreshing Maximo 7.6 Dev with Production data and settings
What specific tables do you want to exclude from a refresh? I can see referential integrity being an issue. To answer your question, the answer is maybe.
The only other minor tidbit I'd add is help.host URL may need an update.
report.custom.* if you use ERI (External Reporting Integration) may need an update.
I also change the welcomemaximomessage to say test. You can also change the skin or an replace graphic images in webclient (e.g. different color banner/header/login screen) to help differentiate.
------------------------------
sun kim
Original Message:
Sent: 02-21-2023 11:23
From: vineet joshi
Subject: Instructions for refreshing Maximo 7.6 Dev with Production data and settings
Hello Steven,
Little late in the discussion but is there a way we can refresh dev database from production without refreshing specific tables ?
Thanks
VJ
------------------------------
vineet joshi
Original Message:
Sent: 10-29-2020 10:19
From: Steven Shull
Subject: Instructions for refreshing Maximo 7.6 Dev with Production data and settings
Adam and Alex gave quite a few good examples on PROD->DEV refresh that are important areas to focus on. I'll try to avoid rehashing too much, but the biggest thing we do for customers is disable a lot of the background processes (PMWOGEN, Reorder, email listener, etc.) and updating the integration information to be appropriate for that environment. These tend to be areas that cause confusion for users or data issues with your PROD system and it'll be unique to your system in what you want to do.
The one thing I didn't see in either is a DEV environment might not be an exact replica of PROD from a configuration perspective. You should always have 1 environment that is a mirror configuration of PROD (so you can validate things prior to deploying to PROD), but a lot of organizations will have more than 1 NPE (Non-Production Environment). We'll have to remove some cluster configuration references in those smaller NPE environments (changing connection factories on JMS queues, removing server specific system properties such as cron task dorun/donotrun, etc.).
------------------------------
Steven Shull
Projetech
Original Message:
Sent: 10-28-2020 18:23
From: justin haley
Subject: Instructions for refreshing Maximo 7.6 Dev with Production data and settings
Hi,
I was curious if anyone had documentation for refreshing Maximo 7.6 Dev data with Production data and what settings need to be done to get the Development environment pointed to dev servers and not production. I've found documentation for 7.5 but it is no longer recommended with 7.6.
When we currently try to refresh dev, the settings from production are transferring to dev and we want to make sure that when we modify work orders or any other record that it does not get updated in our production environment.
Examples:
System Properties
Database.SQL.ServerHostName
mxe.doclink.doctypes.defpath
#Administration
#MaximoUserGroups
------------------------------
justin
------------------------------