Changing connection in Universe

[former_member213259]

Hello All,

This is the scenario. I am currently using BO 3.1. I have a universe using connection A pointing to database A. It has around 5000 objects. Now the requirement is to point to a different database B using a different connection B. The objects are fully qualified i.e. Ownername.tablename.columnname. If I repoint the same universe to the new connection B, will the objects break?  What is the best way to handle this?

Appreciate help on this.

Thanks,

Sowrabha

[former_member193452 · Accepted solution]

Hi Sowrahba,

This can be done very easilty without breaking any reporting associations in the Webi.

1. Import the universe in Universe designer.

2. Create a new connection to the new data source.

3. Left Click In the Graphical Table display area white space.

4. Go the toolbar and EDIT and SELECT ALL.  (all of the tables with be highlighted)

5. Right Click in the Table area and select RENAME Table

6. Change the owner and qualifier to the new connection values.

7. Click SAVE.  (This is still a local save)

8. On the Toolbar click Refresh Structure (no tables should be missing.

9. Run the Integrity checker and Export to the repository if no errors are encountered.

associated to the new data source without breaking any Webi Reports.

Here is a link to the Kbase with screen shots.

http:// service.sap.com/sap/support/notes/1989135

Hope this helps! Jacqueline

[former_member213259 · Accepted solution]

It works great Thanks a lot!

[former_member4998 · Accepted solution]

Hi

Good ...Please mark blog helpful & answered

[former_member4998]

Hi

requirement is to point to a different database B using a different connection B.

If the Ownername.tablename.columnname (Schema Name, Table Name, Field Name) same coming from connection B and Data base B. you can repoint the universe to the new connection B.

will the objects break?  What is the best way to handle this?

And it’s won’t break the objects. But whatever the data is there in the database B only able to see in the report. No table to see the data from the database A