Cognos Analytics error messages related to data sets store connections
When a Db2 exception is returned to IBM® Cognos® Analytics, the message includes a value associated to the Db2 SQLCODE and SQLSTATE.
For more information, see SQL messages on the IBM Db2 Documentation page (https://www.ibm.com/docs/en/db2/11.5?topic=messages-sq).
DRD-101 Ambiguous connection
The current Cognos Analytics user has access to multiple data set server connections. A user can have access to only one connection.
- Use Cognos Analytics security to limit the user's access
to the connection objects.
For more information, see Managing multiple connections to the same data source.
- If any of the connections is not required, delete it.
DRD-102 Cannot truncate decimal values
The precision or scale of an input column is larger than the supported Db2 decimal data type.
- DECIMAL type with a precision and scale that Db2 supports
- Double precision
DRD-104 Unsupported data type
The data type of a column in a data set is not supported by Db2.
To resolve the error:
- In the data set specification, use a CAST expression to convert the value to a data type supported by Db2. For example, use the EXTRACT scalar function to return the INTEGER representation of the YEAR.
- Drop the column from the data set specification if the column is not required.
DRD-105 Only one data source of connection can be configured per user
The current Cognos Analytics user has access to multiple data set server connections. A user can have access to only one connection.
To resolve the error:
- Use Cognos Analytics security on the connection objects
to limit the user’s access to one connection.
For more information, see Managing multiple connections to the same data source.
- If any of the connections is not required, delete it.
DRD-106 The vendor version is not supported for storing data
A data set server connection is referencing a database product which is not supported. The error includes the product name and version that the connection is referencing.
To resolve the error, correct the connection URL to refer to a supported instance of Db2 Linux, Unix, or Db2 on Cloud.
DRD-107 Error calling CM for data source with dataset capability
A request for information from the Content Manager service failed.
If the error continues to occur, contact IBM support.
MSR-GEN-0110 This is an internal special purpose data source, access is forbidden
Data set connections are not intended to be used for actions including importing metadata.
By default, actions including importing metadata from the Manage user interface and Framework Manager import wizard do not display data set connections.
MSR-UPL-2146 Dataset "{0}" data serialization has failed due to "{1}"
Uploading of a file encountered an error. Review the error message and Cognos Analytics log files for additional details.
Errors could include those thrown by Db2 as the data was being moved into a target table.
MSR-UPL-2147 Missing or corrupt data for "{0} " table
Modelling service was unable to locate an output object in the Content Manager store. If the condition continues, contact IBM Cognos support.
MSR-UPL-2154 Error while opening IJMDConnection during file update
Modelling service was unable to connection to the Dataset server database. Review the error message and Cognos Analytics log files for additional details.
If the error continues to occur, contact IBM support.
MSR-UPL-2155 Failed to drop unused table " {0}" during file update
Modelling service attempted to drop a table in the Dataset server database. Review the error message and Cognos Analytics log files for additional details.
MSR-UPL-2156 No data source connections are configured for data source {0} to store data for uploaded files and data sets
Modelling service was unable to find a data source connection that is configured to store data for uploaded files and data sets.
MSR-UPL-2157 There is no data source configured to store data for uploaded files and data sets
Modelling service was unable to find a Dataset server connection that the user has access to. Either the connection is missing, marked disabled or Cognos security disallows the user access.