Object Name Change

security Supervisor (4.x - 6.x)
1

Hi listers,

Here’s a question related to the thread on universe changes. We are migrating our production database to a new machine and upgrading to Oracle 8i. Along with those changes we’re migrating our production universe domain to the new box. And… at the same time some of the column names are changing, so we’re changing the corresponding object names in the universe. (A lot of changes at one time!) When we modified the object names in the existing universe, they retained the same object ID. But when we exported the universe to the new universe domain, it got a new universe ID. So, now when we try to run an existing report against the new universe, if it contains one of the renamed objects, we get “Some of the objects from the XYZ universe are missing or ambiguous. You cannot run the query on this universe.” According to the BO Tech Notes (case #2719), this error message occurs when you try to point a report that contains UDOs to a new universe, but that is not the case here.

It seems like it’s just a matter of the universe IDs being different, since an object name change doesn’t cause a problem when the universe ID remains the same. I thought of trying to update the universe ID to be the same as the original universe, but I know it’s not usually a good idea to mess with (do direct updates on) the repository tables. Also, it appears that the universe IDs are always unique, even across different domains, so there must be something in the security tables that controls this – i.e., probably shouldn’t even mention that option!

Does anyone have any suggestions?

TIA,
Melody

Listserv Archives (BOB member since 2002-06-25)

2

In article
59F60C5FEAA8D3119FB200508B6FDF1E2F4CE1@exmail01.ago.roadway.com, Melody.Shackelford@ROADWAY.COM (Shackelford, Melody) wrote:

Hi listers,

Here’s a question related to the thread on universe changes. We are migrating our production database to a new machine and upgrading to Oracle
8i.

If you plan to migrate your repository (security or universe domains) to a different database then to ensure that all existing reports continue to work, do not simply export the universe to the new repository - this will indeed give it a new universe id.

The easiest way to do this is to use Oracle export/import functionality. Export all of the required database schemas from the current database and import into the new one. As this is effectively a copying operation then the universe ids will not change. Your DBA will know how to transfer schemas in this way.

If the connection parameters are changing after you migrated to the new database, then you will need to amend the connection through supervisor for the universe domain.

Hope this helps

Brian Patterson

Listserv Archives (BOB member since 2002-06-25)