UCMDB and UD Practitioners Forum (Previously CMS)
cancel

cmdb migration issue

Highlighted
parkar
Acclaimed Contributor.

cmdb migration issue

We are having 3 server bac deployment
One gateway server and 2 data processing server.
Also we are using common database oracle with following schemas
1)bac_mgmt_new
2)bac_bpi_new
3)bac_cmdb_new
4)bac_cmdbhis_new
5)bac_profile_new

Now We are migrating embedded cmdb to external ucmdb server with the recommended guidelines( KM751564 )

During migration we are using external ucmdb server which are having already following schema exists(already placed during ucmdb installation)
1)foundation schema (umdbf)
2)cmdb schema(ucmdbs)
3)cmdbhistory schema (ucmdbh)

So while connecting from gateway server to foundation schema it is successfully connected but while connecting from data processing it is giving the error opertaion failed.
Find the screenshot attached for reference.


Also wanted to confirm that from umdb external server also we need to connect to existing schemas of bac (cmdb & cmdbhistory) If yes, than where the existing schema details(ucmdbs and ucmdbh)of ucmdb server will be stored.

Pls suggest

Ucmdb Version : 8.04
BAC Version : 8.04

 

 

P.S. This thread has been moved from Application Perf Mgmt (BAC / BSM) Support and News Forum to CMS and Discovery Support and News Forum. - Hp Forum Moderator

Cheers!

Nvr Blame a day in ur life....... Good day gives "happiness" & Bad day gives "experience" ......
5 REPLIES
Dmitry Shevchenko
Acclaimed Contributor.

Re: cmdb migration issue

First of all, decide what external uCMDB server you are going to use for BAC. The one you created out of embedded uCMDB or the existing standalone uCMDB server. They are 2 separate uCMDB servers that have nothing to do with each other.
parkar
Acclaimed Contributor.

Re: cmdb migration issue

Thanks dimitry for reply

We want to use both

in our embedeeed bac ucmdb we have created views of sitecope and bpm

And In external ucmdb server team has mapped the ddmi and nnm integration.

So we want to use now one external ucmdb server without any loss

Is that possible?

Pls suggest

Thanks
Cheers!

Nvr Blame a day in ur life....... Good day gives "happiness" & Bad day gives "experience" ......
Dmitry Shevchenko
Acclaimed Contributor.

Re: cmdb migration issue

You cannot sit on 2 chairs at the same time. You have to choose which uCMDB to lose and re-create its contents in the one your BAC will use.

I used to answer a similar question. So check it out to see pros and cons of both options:

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=1412432
parkar
Acclaimed Contributor.

Re: cmdb migration issue

Thanks a lot dimitry for quick response

Suppose if we decided to lose BAC embedded uCMDB and then connect it to the existing standalone uCMDB server.
than in database configuration wizard of bac following is the way to connect the schema

1st bac_mgmt_new than
-> bac_bpi_new
-> cmdb schema(ucmdbs)[ schema of external ucmdb server]
-> cmdbhistory schema (ucmdbh)[ schema of external ucmdb server]

Also having one query where we have to connect the foundation schema of external ucmdb

Pls correct me if iam wrong

Cheers
Cheers!

Nvr Blame a day in ur life....... Good day gives "happiness" & Bad day gives "experience" ......
Dmitry Shevchenko
Acclaimed Contributor.

Re: cmdb migration issue

If you decide to deploy BAC with external uCMDB server you don't even have an option to connect to cmdb and cmdb history schemas while running BAC Connect to DB Wizard. You just provide details of the external uCMDB server and that's it. It's the uCMDB server that will connect to cmdb, cmdb_history and foundation schemas, not BAC.