Urgent - 7.2.2 Object Manager failing

[entaroadun]

We have a MSTR 7.2.2 implementation with MD in Oracle 9i.

For our change control process, we create dev MDs in Access using project duplication. We then OM the new and modified objects into the production MD using 3-tier to 3-tier and 7.2.2 OM. This has always worked before.

We are doing a production move this evening and OM is failing. Every time we try to move an object from the dev Access MD into the production Oracle MD, we get an error message:

"The source configuration version is newer than the target configuration version. You need to update at least one of the target projects in order to update the configuration. This operation is invalid and will be cancelled."

I know that there are issues with migrating between MDs that are created using database dupe instead of project dupe. However, we used project dupe. I checked the project and version IDs and they are different.

The biggest head-scratcher is: OM works going the other way. Moving objects from production to dev works with no problems. If there were an issue with the project, version, or configuration IDs, this would fail.

Why would it go one way but not the other? How does it know that the source is newer than the target? GUIDs are randomly generated, so if MSTR is aware of new/old, then it must be reading a timestamp somewhere.

Even though the dev MD was created using project dupe, we tried the steps outlined in TN4200-7X0-0021. We renamed the project and restarted the IServer on the target. We also created a new user in the target in the Everyone group. No dice.

Anyone seen anything like this before?

 

[nlim]

are both md updated to the 7.2.2

 

[entaroadun]

Problem resolved.

We spoke with MSTR tech support and found that the dev MD was created with 7.2.3. Therefore, the configuration objects in the MD were marked version 7.2.3. That's why the OM failed, even though the project objects were 7.2.2 and the Intelligence Server running the MD was 7.2.2.

We upgraded the configuration objects in the target production MD to 7.2.3 by creating a new project in the metadata using 7.2.3 in 2-tier and dropping the project. This forced the configuration objects to upgrade to 7.2.3 while leaving the existing project at 7.2.2 and the Intelligence Server at 7.2.2.

We have not run into any issues thus far with 7.2.2 IServer running on 7.2.3 configuration objects.