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.
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
Nvr Blame a day in ur life....... Good day gives "happiness" & Bad day gives "experience" ......
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.
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.