17.3.01 Transport CIs from one to other server

[Peter Schmidt]

Hi folks,
I have 2 Systems running CA Service Managment.
I want to transport CIs from one system to the other.
The problem is that pdm_load does not work for ca_owned_resource since 17.3 and still not in 17.3.0.1.

I need a workaround to do this.
Extract CIs from servrer1-mdb and import into server2-mdb.

Dataexport/import-tool offers nothing for nr-Object.

Regards,
Peter

------------------------------
Senior Technical Consultant
Fujitsu Services
------------------------------

[Cristi Mitrana]

pdm_load is not recommended at all for loading CIs, you risk of having inconsistencies in the MDB's CORA tables. Use grloader to bulk load CIs.

[Peter Schmidt]

Hi Cristi,
yes your right at all and when I'm doing imports from other sources I do it with grloader.
And I didn't ask how to do it with pdm_load (I would be able to) because pdm_load does not work for CIs under 17.3.

So ... back to my question ...
How can I transport CIs from one machine's mdb to the other's mdb?
Is grloader able to do this and when yes ... how?

Regards,
Peter

------------------------------
Senior Technical Consultant
Fujitsu Services
------------------------------

[Cristi Mitrana]

If you've never used GRLoader, then take a look in the docs on how to use it. Basically you'll export the necessary info (CI Name, Class, Family, Desc, etc.) and create a CSV/XLS file with the info, then you can use GRLoader to import it. There is a sample `.xlsx` file under $NX_ROOT/samples/GRLoader that has multiple examples of how GRLoader accepts formatted data.

[Peter Schmidt]

Hi Cristi,
again you missunderstood me.

I know how to import CI - Data using xml. With perl I wrote an import-Tool which can read different source-Types - create xml and use grloader for filling TWA and then loading it to CMDB.

But what I hoped is that there is an ready mechanism to transport CIs including ca_owned, usp_owned, ... and extensionTable-content from one Server-DB to the other.

So, again, I have to do it myself.

Thanks and regards,
Peter

------------------------------
Senior Technical Consultant
Fujitsu Services
------------------------------

[Cristi Mitrana]

I see, unfortunately I'm not aware of any tool to do that (semi)automatically for CIs.
The Data Export/Import utility included in SDM doesn't export CIs, maybe it could be enhanced to do so.

[Brian Mathato]

Hi Peter,

Have you looked into the 'CA SDM Environment Promotion' utility yet?

https://techdocs.broadcom.com/us/en/ca-enterprise-software/business-management/ca-service-management/17-3/administering/administering-ca-service-desk-manager/ca-sdm-environment-promotion.html

Perhaps this may help?


Otherwise, you may have to try writing a webservice based thingy if you have the luxury of time to put some effort into this.


------------------------------
Kind Regards,
Brian
------------------------------

[Peter Schmidt]

Hi Brian,
datapromotion would be great for this
but
there is no export defined for object nr.

What I'm trying next is
- MSSQL Export/import tables (ca_owned_resource, usp_owned_resource, ... neede extension tables)
- pdm_reg_asstes (hoping cora tables will be updated)

The first problem I have with mssql export/import that it trys to creat the target-Tables what does not work naturally.

Regards,
Peter

------------------------------
Senior Technical Consultant
Fujitsu Services
------------------------------

[Peter Schmidt]

Hi Cristi,
yes, object nr cannot be exported with the tool.

Would be gread if there is anybody who knows how to enhance it.

Because of relations in other objects like IN, ID's have to remain the same in target DB.

Thanks,
Peter

------------------------------
Senior Technical Consultant
Fujitsu Services
------------------------------

[Oliver Gaida]

Hello Peter,

do you know my ruby gem usd? With a little ruby knowledge, it shouldn't be a problem to write a transfer-script with it. Please have a look at https://github.com/ogaida/usd/wiki/import-scripts 

You can simultaneously create two object instances to the two databases and export data from server1 with first instance and with the other instance import into server2. The usd-ruby-module is using the rest-API, so all object-inserts and -updates will be validated and logged with the common SDM-rules.

Kind regards
Oliver

------------------------------
Devops Engineer
Sycor GmbH
------------------------------

[Peter Schmidt]

Good morning Oliver,
unfortunately I do not have the time to deal with your solution. I will script the data transport so that the constraints are temporarily disabled and the required data (including cora tables) is transported 1to1.
A complete mdb transport is not possible in my case because the systems have different installation states. Furthermore the migrated system (under 14.x all tables were installed which are now also included in the migrated system) is filled with tables which are not needed.

Thanks for your ideas.
Regards,
Peter

------------------------------
Senior Technical Consultant
Fujitsu Services
------------------------------

[Peter Schmidt]

Hi all,
new additional info,
trying pdm_reg_assets has the same problem as pdm_load of ca_owned_resource has:
cora-registration service hangs:
stdlog: problem with MDB register. ERROR: Timed out waiting for response from mdb_registration_nxd
Same error occurs when trying to load ca_owned_resource wit pdm_load. 

We have an open CASE for it hoping to get a solution as fast as possible (hopefully with 17.3.0.2 - RU02)

Regards,
Peter

------------------------------
Senior Technical Consultant
Fujitsu Services
------------------------------