Cognos Analytics 12 > Manage > Data Server Connections > {Data Server} > Assets > {Asset} > Load Metadata:  fails with error message MSR-SMT-2190 with no information provided as to which Asset is at fault or what the problem is with the Asset.

I have 55 tables and views defined, so have had to trawl through, in a, very time-consuming, trial and error approach, to identify the problem (= not happy!).

It appears there are many errors that can result in an MSR-SMT-2190 error message being displayed.  So, identifying the errant table/view was only the 1st troubleshooting step.

Having eventually identified the SQL view causing the problem, and reviewing it's definition, it became clear that, in this instance, Cognos did not like a ROW_NUMBER() generated column view.  I would have expected Cognos 12 to handle this standard SQL feature. Or I would have accepted an error message indicating an issue with the particular view/column.  The biggest issue with Cognos failing to handle this feature, is that the resolution requires a source database change to remove/hide the source column.

For anyone interested in the ROW_NUMBER() solution, Cognos provides an equivalent as: running-count ( rank (orderbyfield ASC/DESC  for partitionfield) for partitionfield). So,the resolution is to swop the source SQL view column for the Data Module equivalent, and remove the SQL view column from the Data Module.

Hi,

From Assets, when you click on Load options, you need to uncheck Retrieve sample data.

It is working fine if you choose to disable Retrieve sample data.

Best regards,

Cognos Analytics 12 > Manage > Data Server Connections > {Data Server} > Assets > {Asset} > Load Metadata:  fails with error message MSR-SMT-2190 with no information provided as to which Asset is at fault or what the problem is with the Asset.

I have 55 tables and views defined, so have had to trawl through, in a, very time-consuming, trial and error approach, to identify the problem (= not happy!).

It appears there are many errors that can result in an MSR-SMT-2190 error message being displayed.  So, identifying the errant table/view was only the 1st troubleshooting step.

Having eventually identified the SQL view causing the problem, and reviewing it's definition, it became clear that, in this instance, Cognos did not like a ROW_NUMBER() generated column view.  I would have expected Cognos 12 to handle this standard SQL feature. Or I would have accepted an error message indicating an issue with the particular view/column.  The biggest issue with Cognos failing to handle this feature, is that the resolution requires a source database change to remove/hide the source column.

For anyone interested in the ROW_NUMBER() solution, Cognos provides an equivalent as: running-count ( rank (orderbyfield ASC/DESC  for partitionfield) for partitionfield). So,the resolution is to swop the source SQL view column for the Data Module equivalent, and remove the SQL view column from the Data Module.

Cognos Analytics 12 > Manage > Data Server Connections > {Data Server} > Assets > {Asset} > Load Metadata:  fails with error message MSR-SMT-2190 with no information provided as to which Asset is at fault or what the problem is with the Asset.

I have 55 tables and views defined, so have had to trawl through, in a, very time-consuming, trial and error approach, to identify the problem (= not happy!).

It appears there are many errors that can result in an MSR-SMT-2190 error message being displayed.  So, identifying the errant table/view was only the 1st troubleshooting step.

Having eventually identified the SQL view causing the problem, and reviewing it's definition, it became clear that, in this instance, Cognos did not like a ROW_NUMBER() generated column view.  I would have expected Cognos 12 to handle this standard SQL feature. Or I would have accepted an error message indicating an issue with the particular view/column.  The biggest issue with Cognos failing to handle this feature, is that the resolution requires a source database change to remove/hide the source column.

For anyone interested in the ROW_NUMBER() solution, Cognos provides an equivalent as: running-count ( rank (orderbyfield ASC/DESC  for partitionfield) for partitionfield). So,the resolution is to swop the source SQL view column for the Data Module equivalent, and remove the SQL view column from the Data Module.

------------------------------
Mr Minihan
------------------------------

*SIGH*     MSR-SMT-2190.

We need to make the logging during import better. Please log a defect.


Unchecking the sampling option during metadata import is a work around, albeit bought at the price of additional manual work by the modeler in the review metadata after import stage, which is part of the Cognos proven practices.

------------------------------
IAN HENDERSON

Original Message:
Sent: Tue May 13, 2025 07:30 AM
From: Mr Minihan
Subject: MSR-SMT-2190 Internal error trying to create smart metadata.

Cognos Analytics 12 > Manage > Data Server Connections > {Data Server} > Assets > {Asset} > Load Metadata:  fails with error message MSR-SMT-2190 with no information provided as to which Asset is at fault or what the problem is with the Asset.

I have 55 tables and views defined, so have had to trawl through, in a, very time-consuming, trial and error approach, to identify the problem (= not happy!).

It appears there are many errors that can result in an MSR-SMT-2190 error message being displayed.  So, identifying the errant table/view was only the 1st troubleshooting step.

Having eventually identified the SQL view causing the problem, and reviewing it's definition, it became clear that, in this instance, Cognos did not like a ROW_NUMBER() generated column view.  I would have expected Cognos 12 to handle this standard SQL feature. Or I would have accepted an error message indicating an issue with the particular view/column.  The biggest issue with Cognos failing to handle this feature, is that the resolution requires a source database change to remove/hide the source column.

For anyone interested in the ROW_NUMBER() solution, Cognos provides an equivalent as: running-count ( rank (orderbyfield ASC/DESC  for partitionfield) for partitionfield). So,the resolution is to swop the source SQL view column for the Data Module equivalent, and remove the SQL view column from the Data Module.

------------------------------
Mr Minihan
------------------------------

Hi Ian,

Thanks for replying - I will log a defect.

As it happens, I've found another SQL feature that causes the MSR-SMT-2190 error.  In this case, we had a View that performed an INNER JOIN that had join specifications on the JOIN but also on the WHERE clause. E.g. SELECT a1, b1 FROM a INNER JOIN b ON b2 = a1 WHERE b3 = a3.

The load Metadata worked when redesigned to put the join specifications on the INNER JOIN.  I.e. SELECT a1, b1 FROM a INNER JOIN b ON b2 = a1 AND b3 = a3.

It's possible that this specific issue was due to data volumes/timeout somewhere - but I'm not sure.

Regards,

John Minihan

*SIGH*     MSR-SMT-2190.

We need to make the logging during import better. Please log a defect.


Unchecking the sampling option during metadata import is a work around, albeit bought at the price of additional manual work by the modeler in the review metadata after import stage, which is part of the Cognos proven practices.

------------------------------
IAN HENDERSON

Original Message:
Sent: Tue May 13, 2025 07:30 AM
From: Mr Minihan
Subject: MSR-SMT-2190 Internal error trying to create smart metadata.

Cognos Analytics 12 > Manage > Data Server Connections > {Data Server} > Assets > {Asset} > Load Metadata:  fails with error message MSR-SMT-2190 with no information provided as to which Asset is at fault or what the problem is with the Asset.

I have 55 tables and views defined, so have had to trawl through, in a, very time-consuming, trial and error approach, to identify the problem (= not happy!).

It appears there are many errors that can result in an MSR-SMT-2190 error message being displayed.  So, identifying the errant table/view was only the 1st troubleshooting step.

Having eventually identified the SQL view causing the problem, and reviewing it's definition, it became clear that, in this instance, Cognos did not like a ROW_NUMBER() generated column view.  I would have expected Cognos 12 to handle this standard SQL feature. Or I would have accepted an error message indicating an issue with the particular view/column.  The biggest issue with Cognos failing to handle this feature, is that the resolution requires a source database change to remove/hide the source column.

For anyone interested in the ROW_NUMBER() solution, Cognos provides an equivalent as: running-count ( rank (orderbyfield ASC/DESC  for partitionfield) for partitionfield). So,the resolution is to swop the source SQL view column for the Data Module equivalent, and remove the SQL view column from the Data Module.

------------------------------
Mr Minihan
------------------------------