ETL: Failed to sync between staging DB and DCO db?

[DCIM_Support]

I'm trying to use the "Netwok import" job on "ETL Integration Examples".

Imported configuration items are successfully detected and then I associated them to the devices on DCO Client.

After forcing synchronization, the network port are added in the network tab on DCO client.
But, I still could not find the network connection between the devices on DCO Client.

I checked the "network_connection" tables in staging database and found that all the "state_flag" columns are still "changed". So, I think it's still not yet synced with DCO database.

I have several questions.

1) Log file
  I'd like to check the log for synchronizing between staging database and DCO database. Which log file I should check?

  # I checked the logs below but I could not find doubtful records in the logs.
     /opt/jboss-as/standalone/log/etl.log
     /opt/jboss-as/standalone/log/server.log

2) DCO client view for network_connection

 I assume that, if it's successfully synchronized, the imported network connection should be graphically shown on the network view as which is manually connected on DCO client. 
Is my understanding correct?

3) How to delete the imported configuration items from DCO?
  This is not directly relate with this issue, but I'd like to remove several configuration items from "Unassociated Devices" tab. How should I delete them?

I assume that I can delete them by changing the corresponding state flag value from "synced" to "changed" from pgAdmin.
Is that ok? (I'm doing this test on my testing environment.)

Regards,

Akihiro Yamagami

(CID:134034085)

[DCIM_Support · Accepted solution]

Hello Akihiro

Perhaps someone else might assist you with the import etc of cable links.

Keeping Track of Information State has a good description of how to use state_flag.

To delete CIs, set state_flag to "delete", then sync.  If it's all good, the sync will change state_flag to "sync_deleted" 

I hope that helps

Cheers

Ed

new, changed, deleted, synced

(CID:134034098)

[DCIM_Support]

Hello Akihiro. You are correct the desktop client should display the new connections after they are processed through ETL. The client may not show them immediately if your desktop client is left in planning mode. Clicking the save button or switching to operations mode should cause the desktop client to update.

I have attached a brief pdf which describes how to import several items into DCO using ETL including network connections.

ETL-Database-Demo - V2.pdf

Couple of things to keep in mind for this to work. The two items you are connecting via a network connection must be defined in the configuration_item table in the import database and they must be associated to their appropriate assets in DCO before the connection will be completed. So I would suggest creating your configuration_item entries, associating them to DCO assets, then completing the network connection definitions in ETL.

Regards

Greg Sterling

(CID:134034841)

[DCIM_Support]

Hello Ed and Greg,

Thank you for your information.
Using the pdf document, after several try and error, I finally could see the network connection which is imported using ETL on DCO client.
As Ed commented, it seems that it's because of the below.

• In the "network_connection" table, the values of "cable_type_id" field are missing.
• In the "cable_type" table, no cable type is defined.

After editing the values, using PgAdmin, I could see the network connections. 

In the "NETWORK_CONNECTION" table documentation, there is no description about the "cable_type_id".

I think this it's better to update the document at least. How do you think?

http://sxwhelpcenter.ecostruxureit.com/display/public/DCIMDEVELOPER/ETL+Import+Database

By the way, concerning about 3 questions from me, I still don't have answer for "1) Log file" in the below.
Do you have any information about this?

> 1) Log file
>I'd like to check the log for synchronizing between staging database and DCO database. Which log file I should check?

># I checked the logs below but I could not find doubtful records in the logs.
>/opt/jboss-as/standalone/log/etl.log
>/opt/jboss-as/standalone/log/server.log

(CID:134035507)

[DCIM_Support]

Hi, check server.log again.   At the command prompt issue

cd 

tail -f server.log| grep -i etl

then start a manual sync and you should see some messages.   You can then use some log watching software (e.g. swatch) to watch server.log and email you when certain events occur

(CID:134036368)

[DCIM_Support]

Hello Ed, 

 Thank you for your kind explanation. I could find several warning messages relating to ETL.  I'm still not sure whether it's enough or not, but it's quite helpful.

Regards,

Akihiro

(CID:134037933)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.