Hi,   the import task failed with this error below.   Especially the "Please avoid performing database maintenance tasks during import." message.  Does that indicate the SQL Admin team is doing the database maintenance task which causing the ILMT database not accessible?

2024-03-10 06:00:08 (+0:00:00.047) INFO: Data Source: MSSQL database collation:  SQL_Latin1_General_CP1_CI_AS.
2024-03-10 06:00:08 (+0:00:00.047) INFO: Initialize datasource Data Source: Success
2024-03-10 06:00:08 (+0:00:00.000) INFO: Initialize datasource DisconnectedScan: Start
2024-03-10 06:00:08 (+0:00:00.173) INFO: Initialize datasource DisconnectedScan: Success
2024-03-10 06:00:08 (+0:00:00.031) INFO: ETL from Data Source - RawDatasourceSite                  (0x00000005EF2B8720 - N/A): Start
2024-03-10 06:00:08 (+0:00:00.016) INFO: ETL from Data Source - RawDatasourceSite                  (0x00000005EF2B8720 - 0x00000005F06494BD): Success
2024-03-10 06:00:08 (+0:00:00.000) INFO: ETL from Data Source - DatasourceSite                     (0x00000005EF2B8720 - N/A): Start
2024-03-10 06:00:09 (+0:00:00.062) INFO: ETL from Data Source - DatasourceSite                     (0x00000005EF2B8720 - 0x00000005F06494BD): Success
2024-03-10 06:00:09 (+0:00:00.016) INFO: ETL from Data Source - RawDatasourceAnalysisActivation    (0x00000005EF2B8720 - N/A): Start
2024-03-10 06:00:09 (+0:00:00.015) INFO: ETL from Data Source - RawDatasourceAnalysisActivation    (0x00000005EF2B8720 - 0x00000005F06494BD): Success
2024-03-10 06:00:09 (+0:00:00.002) INFO: ETL from Data Source - RawDatasourceAnalysis              (0x00000005EF2B8720 - N/A): Start
2024-03-10 06:00:09 (+0:00:00.031) INFO: ETL from Data Source - RawDatasourceAnalysis              (0x00000005EF2B8720 - 0x00000005F06494BD): Success
2024-03-10 06:00:09 (+0:00:00.015) INFO: ETL from Data Source - DatasourceAnalysis                 (0x00000005EF2B8720 - N/A): Start
2024-03-10 06:00:09 (+0:00:00.142) INFO: ETL from Data Source - DatasourceAnalysis                 (0x00000005EF2B8720 - 0x00000005F06494BD): Success
2024-03-10 06:00:09 (+0:00:00.000) INFO: ETL from Data Source - DatasourceProperty                 (0x00000005EF2B8720 - N/A): Start
2024-03-10 06:00:09 (+0:00:00.111) INFO: ETL from Data Source - DatasourceProperty                 (0x00000005EF2B8720 - 0x00000005F06494BD): Success
2024-03-10 06:00:09 (+0:00:00.000) INFO: ETL from Data Source - RawComputerId                      (0x00000005EF2B8720 - N/A): Start
2024-03-10 06:00:13 (+0:00:04.041) INFO: ETL from Data Source - RawComputerId                      (0x00000005EF2B8720 - 0x00000005F06494BD): Success
2024-03-10 06:00:13 (+0:00:00.000) INFO: ETL from Data Source - Computer                           (0x00000005EF2B8720 - N/A): Start
2024-03-10 06:00:13 (+0:00:00.000) INFO: Performing scoped ETL
2024-03-10 06:00:14 (+0:00:00.978) INFO: The computer with the following ID: 541528973 on the Data Source datasource will be reactivated and restored.
2024-03-10 06:00:14 (+0:00:00.000) INFO: The computer with the following ID: 1624729169 on the Data Source datasource will be reactivated and restored.
2024-03-10 06:17:31 (+0:17:16.847) WARN: Please avoid performing database maintenance tasks during import. See log below for details.
2024-03-10 06:17:31 (+0:00:00.000) ERROR: SQL: {call [dbo].[etl_computers](?,?,?,?)} Queue: 1000 Exception: #<Java::ComMicrosoftSqlserverJdbc::SQLServerException: Snapshot isolation transaction failed in database 'ILMT' because the object accessed by the statement has been modified by a DDL statement in another concurrent transaction since the start of this transaction.  It is disallowed because the metadata is not versioned. A concurrent update to metadata can lead to inconsistency if mixed with snapshot isolation.>
2024-03-10 06:17:31 (+0:00:00.000) ERROR: Batch execution error: 
2024-03-10 06:17:31 (+0:00:00.000) INFO: ETL from Data Source - Computer                           (0x00000005EF2B8720 - 0x00000005F06494BD): Failed
2024-03-10 06:17:31 (+0:00:00.016) WARN: Please avoid performing database maintenance tasks during import. See log below for details.
2024-03-10 06:17:31 (+0:00:00.000) ERROR: Sequel::DatabaseError: DBNAME: ILMT - Java::ComMicrosoftSqlserverJdbc::SQLServerException: Snapshot isolation transaction failed in database 'ILMT' because the object accessed by the statement has been modified by a DDL statement in another concurrent transaction since the start of this transaction.  It is disallowed because the metadata is not versioned. A concurrent update to metadata can lead to inconsistency if mixed with snapshot isolation.
    com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(com/microsoft/sqlserver/jdbc/SQLServerException.java:265)

------------------------------
York Ly
------------------------------

It basically indicates that some database maintenance jobs (database backup, reindex, update) are conducted at the ILMT import time... 
Does this error also shows up when import is scheduled/run at any other time then 06:00 AM ?

If there are no errors at other timeframe it's definitely some concurrent tasks started at that particular time interfering with ILMT for database access.
Please verify which database maintenance jobs are started around that time:  06:00 AM.

If that error shows up intermittently regardless of timing please verify output from following SQL statements run right after the import problem shows up :

• SELECT command, a.text AS Query, start_time, percent_complete, dateadd(second,estimated_completion_time/1000, getdate()) as estimated_completion_time FROM sys.dm_exec_requests r CROSS APPLY sys.dm_exec_sql_text(r.sql_handle) a
• SELECT * from sys.sysprocesses cross apply sys.dm_exec_sql_text (sql_handle) WHERE OPEN_TRAN > 1 or blocked = 1
• EXEC sp_who2
• EXEC sp_lock

those SQL queries should help to verify if there are any concurrent tasks (together with possible locks) interfering with ILMT...

 

------------------------------
Thank you,
Oktawian

Oktawian Powązka, L3 Support
IBM License Metric Tool
------------------------------