EcoStruxure IT forum
A support forum for Data Center Operation, Data Center Expert, and EcoStruxure IT product users to share knowledge on installation, configuration, and general product use.
Posted: 2020-07-04 06:51 PM
This question was originally posted on DCIM Support by Boris on 2018-06-13
Hello
How I can import patch panels connection back to dco from excel file.
Maybe any body has examples of this import ?
I mean back connections of the patch panels beetween racks .
Thsnks in advance
(CID:132651917)
Posted: 2020-07-04 06:52 PM
This answer was originally posted on DCIM Support by Ed Tarento on 2018-06-14
Hi Boris
The Excel asset load sheet does not have the facility to load connections to the back of patch panels.
This can be done using the ETL Import DB but can be a little fiddly. How many connections do you have to load between how many panels?
Regards
Ed
(CID:132652225)
Posted: 2020-07-04 06:52 PM
This comment was originally posted on DCIM Support by Boris on 2018-06-14
hello Ed
Many thanks .
I have a lot off patch panels and because this I'm interesting to understand import way through ETL .
Can you send me relevant link or guide ?
(CID:132652411)
Posted: 2020-07-04 06:52 PM
This comment was originally posted on DCIM Support by spezialist on 2018-06-14
By the way, almost the same topic was considered a year ago in post
With respect.
(CID:132652437)
Posted: 2020-07-04 06:52 PM
This comment was originally posted on DCIM Support by Boris on 2018-06-21
Hello
I have found the following link
http://sxwhelpcenter.ecostruxureit.com/display/public/DCIMDEVELOPER/ETL+Integration+Examples
I copy the kjb and ktr files to /data/pentaho/import
In additionally I have prepared the connections.xls .According to etl.log the import is working without errors . I see data from connections.xls into tables of the staging DB . But into operation this connection not exist . I attach screenshot
id | from_name | from_id | from_port_type | from_port_number | from_module_name | from_port_speed | from_patch_panel_rear | to_name | to_id | to_port_type | to_port_number | to_module_name | to_port_speed | to_patch_panel_rear |
1 | A | pp001 | FIBER_LC_REGULAR | 1 | A1 | 1Gbps | 0 | B | pp002 | FIBER_LC_REGULAR | 1 | A1 | 1Gbp | 0 |
2 | A | pp001 | FIBER_LC_REGULAR | 1 | B1 | 1Gbps | 1 | B | pp002 | FIBER_LC_REGULAR | 1 | B1 | 1Gbp | 1 |
PortConfiguration sheet
name | id | port_type | start_port_number | port_count | module_name | port_speed |
A | pp001 | FIBER_LC_REGULAR | 1 | 6 | A1 | 1Gbps |
B | pp002 | FIBER_LC_REGULAR | 1 | 6 | A1 | 1Gbps |
A | pp001 | FIBER_LC_REGULAR | 1 | 6 | B1 | 1Gbps |
B | pp002 | FIBER_LC_REGULAR | 1 | 6 | B1 | 1Gbps
|
(CID:132655693)
Posted: 2020-07-04 06:52 PM
This comment was originally posted on DCIM Support by Ed Tarento on 2018-06-22
Hi Boris
Have you created the External System in DCO referencing the Import DB?
(CID:132655753)
Posted: 2020-07-04 06:52 PM
This comment was originally posted on DCIM Support by Boris on 2018-06-25
Hello everybody
I'm sorry , unfortunatelly the example that exists into site doesn't work (http://sxwhelpcenter.ecostruxureit.com/display/public/DCIMDEVELOPER/ETL+Integration+Examples) .
Who can help me import back to back connection between patch panels?
I don't think , I am first who need to import back connections between patch
panenels.
Is there anybody that done it ?
(CID:132656503)
Posted: 2020-07-04 06:52 PM
This comment was originally posted on DCIM Support by Boris on 2018-06-25
Hello everybody
I'm sorry , unfortunatelly the example that exists into site doesn't work (http://sxwhelpcenter.ecostruxureit.com/display/public/DCIMDEVELOPER/ETL+Integration+Examples) .
Who can help me import back to back connection between patch panels?
I don't think , I am first who need to import back connections between patch
panenels.
Is there anybody that done it ?
(CID:132659407)
Posted: 2020-07-04 06:52 PM
This answer was originally posted on DCIM Support by Ed Tarento on 2018-06-26
Hi Boris
I've successfully done this although I didnt use the supplied files. I wrote programs to populate the Import DB directly from CSV files provided by the customer. It did work at the v7 version i used a few years back.. no reason to think its broken in this version but its possible
This is just a guess but are you using an XLS or XLSX? I can see the example posted is called connections.xls
Have you created the External System in DCO referencing the Import DB?
Webmin should show this
not this
When you right click on the External System and select "Synchronize external data" in DCO under "Planning - Device Association" what do you see?
look in /opt/jboss-as/standalone/log/server.log
Cheers
Ed
(CID:132656877)
Posted: 2020-07-04 06:53 PM
This comment was originally posted on DCIM Support by Boris on 2018-07-03
Hello Ed
Many thanks for your answer .
I'm using DCO 8.2.2 and I haven't problem to fill etl import DB dirctly .
My problem - what is tables I need to fill and how .I have learning the datagramma of the examples networ connection tables nad it's different that I have ( I think in apc site old datagrama ) .
I'm going check what you written
(CID:132660147)
Posted: 2020-07-04 06:53 PM
This comment was originally posted on DCIM Support by Boris on 2018-07-03
(CID:132660149)
Posted: 2020-07-04 06:53 PM
This comment was originally posted on DCIM Support by Boris on 2018-07-03
(CID:132660155)
Posted: 2020-07-04 06:53 PM
This comment was originally posted on DCIM Support by Boris on 2018-07-03
Also etl.log is ok .
Would you like help me fill etl import db tables correct ?
I think that doesn't work because not all tables has been filled.
For example connect between 2 racks small fiber patch panels (A and B)
(CID:132660159)
Posted: 2020-07-04 06:53 PM
This comment was originally posted on DCIM Support by Boris on 2018-07-03
2018-06-25 14:22:53,479 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLJobSchedulerImpl] (default task-10 GhliCPUZS3eYmRfmsedtCA) Scheduled single run ETL transformation job on: im22
2018-06-25 14:23:22,330 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLTransformationJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Obtained system lock: com.apc.etl.model.v1.SystemLock@1d83862d[lockName=SYSTEM_LOCK] for: im22 (8c3d2229-2484-4ba9-8d42-7a7a4e1c0a9f)
2018-06-25 14:25:26,166 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLTransformationJobStateTrackerImpl] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Job completed. State: ok
2018-06-25 14:25:26,177 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) ETL synch job for: im22 started
2018-06-25 14:25:26,178 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Running ETL synchronizer: ConfigurationItemSynchronizer for system: im22
2018-06-25 14:25:26,239 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.etl.server.v1.configurationitem.ConfigurationItemSynchronizer] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Synchronized configuration item records from im22
2018-06-25 14:25:26,260 WARN [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLConfiguationItemSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Ignoring update to non-existing ETL Asset: pp001
2018-06-25 14:25:26,260 WARN [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLConfiguationItemSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Ignoring update to non-existing ETL Asset: pp002
2018-06-25 14:25:26,261 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLConfiguationItemSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Sync-stats (new,updated,deleted): (0, 0, 0)
2018-06-25 14:25:26,306 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) ETL synchronizer: ConfigurationItemSynchronizer for system: im22 completed (127ms)
2018-06-25 14:25:26,309 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Running ETL synchronizer: AutoAssociationSynchronizer for system: im22
2018-06-25 14:25:26,368 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.etl.server.v1.configurationitem.AutoAssociationSynchronizer] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Found 0 auto-association candidate(s)
2018-06-25 14:25:26,408 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) ETL synchronizer: AutoAssociationSynchronizer for system: im22 completed (98ms)
2018-06-25 14:25:26,412 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Running ETL synchronizer: UpdateMeasurementIdsSynchronizer for system: im22
2018-06-25 14:25:26,471 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) ETL synchronizer: UpdateMeasurementIdsSynchronizer for system: im22 completed (58ms)
2018-06-25 14:25:26,473 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Running ETL synchronizer: ConnectorSynchronizer for system: im22
2018-06-25 14:25:26,542 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.etl.server.v1.connector.NetworkPortHelper] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) No associated devices for system im22 - skipping connection synching
2018-06-25 14:25:26,607 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) ETL synchronizer: ConnectorSynchronizer for system: im22 completed (133ms)
2018-06-25 14:25:26,610 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Running ETL synchronizer: BasicPropertiesSynchronizer for system: im22
2018-06-25 14:25:26,666 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.etl.server.v1.configurationitem.BasicPropertiesSynchronizer] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Found 0 item(s) with basic property changes
2018-06-25 14:25:26,694 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) ETL synchronizer: BasicPropertiesSynchronizer for system: im22 completed (83ms)
2018-06-25 14:25:26,701 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Running ETL synchronizer: BreakerPanelMeasurementsSynchronizer for system: im22
2018-06-25 14:25:26,771 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.measurements.PowerMeasurementRetriever] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Fetching peak power measurement information from ETL: im22
2018-06-25 14:25:26,776 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.measurements.PowerMeasurementRetriever] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Updating partial power measurement information from ETL: im22
2018-06-25 14:25:26,821 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) ETL synchronizer: BreakerPanelMeasurementsSynchronizer for system: im22 completed (120ms)
2018-06-25 14:25:26,830 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Running ETL synchronizer: WorkOrderSynchronizer for system: im22
2018-06-25 14:25:26,897 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) ETL synchronizer: WorkOrderSynchronizer for system: im22 completed (67ms)
2018-06-25 14:25:26,902 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Running ETL synchronizer: PropertySynchronizer for system: im22
2018-06-25 14:25:26,948 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) ETL synchronizer: PropertySynchronizer for system: im22 completed (45ms)
2018-06-25 14:25:26,954 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Running ETL synchronizer: MeasurementsSynchronizer for system: im22
2018-06-25 14:25:27,013 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) ETL synchronizer: MeasurementsSynchronizer for system: im22 completed (59ms)
2018-06-25 14:25:27,017 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Running ETL synchronizer: TagSynchronizer for system: im22
2018-06-25 14:25:27,070 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) ETL synchronizer: TagSynchronizer for system: im22 completed (53ms)
2018-06-25 14:25:27,072 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) Running ETL synchronizer: AlarmSynchronizer for system: im22
2018-06-25 14:25:27,110 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) ETL synchronizer: AlarmSynchronizer for system: im22 completed (37ms)
2018-06-25 14:25:27,113 INFO [GhliCPUZS3eYmRfmsedtCA] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 t08PnIlPRF2w3+SL+U3ODg) ETL synch job for: im22 finished
2018-06-25 14:25:27,279 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLTransformationJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Obtained system lock: com.apc.etl.model.v1.SystemLock@49657bb2[lockName=SYSTEM_LOCK] for: im22 (8c3d2229-2484-4ba9-8d42-7a7a4e1c0a9f)
2018-06-25 14:27:32,524 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLTransformationJobStateTrackerImpl] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Job completed. State: ok
2018-06-25 14:27:32,532 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) ETL synch job for: im22 started
2018-06-25 14:27:32,533 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Running ETL synchronizer: ConfigurationItemSynchronizer for system: im22
2018-06-25 14:27:32,570 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.etl.server.v1.configurationitem.ConfigurationItemSynchronizer] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Synchronized configuration item records from im22
2018-06-25 14:27:32,577 WARN [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLConfiguationItemSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Ignoring update to non-existing ETL Asset: pp001
2018-06-25 14:27:32,577 WARN [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLConfiguationItemSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Ignoring update to non-existing ETL Asset: pp002
2018-06-25 14:27:32,578 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLConfiguationItemSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Sync-stats (new,updated,deleted): (0, 0, 0)
2018-06-25 14:27:32,588 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) ETL synchronizer: ConfigurationItemSynchronizer for system: im22 completed (54ms)
2018-06-25 14:27:32,591 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Running ETL synchronizer: AutoAssociationSynchronizer for system: im22
2018-06-25 14:27:32,625 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.etl.server.v1.configurationitem.AutoAssociationSynchronizer] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Found 0 auto-association candidate(s)
2018-06-25 14:27:32,632 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) ETL synchronizer: AutoAssociationSynchronizer for system: im22 completed (41ms)
2018-06-25 14:27:32,634 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Running ETL synchronizer: UpdateMeasurementIdsSynchronizer for system: im22
2018-06-25 14:27:32,669 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) ETL synchronizer: UpdateMeasurementIdsSynchronizer for system: im22 completed (34ms)
2018-06-25 14:27:32,672 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Running ETL synchronizer: ConnectorSynchronizer for system: im22
2018-06-25 14:27:32,715 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.etl.server.v1.connector.NetworkPortHelper] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) No associated devices for system im22 - skipping connection synching
2018-06-25 14:27:32,737 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) ETL synchronizer: ConnectorSynchronizer for system: im22 completed (64ms)
2018-06-25 14:27:32,740 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Running ETL synchronizer: BasicPropertiesSynchronizer for system: im22
2018-06-25 14:27:32,774 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.etl.server.v1.configurationitem.BasicPropertiesSynchronizer] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Found 0 item(s) with basic property changes
2018-06-25 14:27:32,791 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) ETL synchronizer: BasicPropertiesSynchronizer for system: im22 completed (51ms)
2018-06-25 14:27:32,794 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Running ETL synchronizer: BreakerPanelMeasurementsSynchronizer for system: im22
2018-06-25 14:27:32,829 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.measurements.PowerMeasurementRetriever] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Fetching peak power measurement information from ETL: im22
2018-06-25 14:27:32,835 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.measurements.PowerMeasurementRetriever] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Updating partial power measurement information from ETL: im22
2018-06-25 14:27:32,843 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) ETL synchronizer: BreakerPanelMeasurementsSynchronizer for system: im22 completed (48ms)
2018-06-25 14:27:32,847 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Running ETL synchronizer: WorkOrderSynchronizer for system: im22
2018-06-25 14:27:32,903 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) ETL synchronizer: WorkOrderSynchronizer for system: im22 completed (55ms)
2018-06-25 14:27:32,906 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Running ETL synchronizer: PropertySynchronizer for system: im22
2018-06-25 14:27:32,943 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) ETL synchronizer: PropertySynchronizer for system: im22 completed (36ms)
2018-06-25 14:27:32,947 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Running ETL synchronizer: MeasurementsSynchronizer for system: im22
2018-06-25 14:27:33,030 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) ETL synchronizer: MeasurementsSynchronizer for system: im22 completed (82ms)
2018-06-25 14:27:33,033 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Running ETL synchronizer: TagSynchronizer for system: im22
2018-06-25 14:27:33,071 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) ETL synchronizer: TagSynchronizer for system: im22 completed (38ms)
2018-06-25 14:27:33,074 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) Running ETL synchronizer: AlarmSynchronizer for system: im22
2018-06-25 14:27:33,115 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) ETL synchronizer: AlarmSynchronizer for system: im22 completed (41ms)
2018-06-25 14:27:33,118 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLSyncJobExecutor] (QuartzSharedThreadPool-1 dsAT0VoVRayG7fDjobenKg) ETL synch job for: im22 finished
2018-06-25 14:30:00,061 INFO [7jeXCmzNSrSd/uKDFMPX+g] [apc] [com.apc.monitoring.etl.ETLTransformationJobExecutor] (QuartzSharedThreadPool-1 VoMPVicPQmeNvyLVnNC0yw) Obtained system lock: com.apc.etl.model.v1.SystemLock@77785dc3[lockName=SYSTEM_LOCK] for: im22 (8c3d2229-2484-4ba9-8d42-7a7a4e1c0a9f)
(CID:132660167)
Posted: 2020-07-04 06:53 PM
This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.
Create your free account or log in to subscribe to the forum - and gain access to more than 10,000+ support articles along with insights from experts and peers.