FM Error XQE-DAT-0004 A decimal type with precision 131089 and scale 0 is invali

[Binway]

Hi Team,
I have installed Congos Analytics 11.0.3 on 64 bit Windows 10 and have connected to Mongo following the steps in https://docs.mongodb.com/bi-connector/installation/.
One of the steps is to install the postgresql-9.4.1209 jar file in drivers directory for CA.
When using the direct connection via a data module I can generate a simple list report with no errors.
To get proper query flexibility I needed to connect to Mongo using FM so I installed the latest version I could see which was 32bit Windows version 11.0.1.
I placed the postgresql-9.4.1209 jar file in the C:\Program Files (x86)\ibm\cognos\model\webapps\p2pd\WEB-INF\lib directory as it is a 32bit app.
The problem I have is that when I verify my Model I get the following error:
XQE-DAT-0004 A decimal type with precision 131089 and scale 0 is invalid.
I can't seem to change this setting as it is detected by FM when using the Model Wizard so am wondering if there is a different driver or I have it in the wrong location.
Any thoughts appreciated.

Binway

[MFGF]

Hi Team,
I have installed Congos Analytics 11.0.3 on 64 bit Windows 10 and have connected to Mongo following the steps in https://docs.mongodb.com/bi-connector/installation/.
One of the steps is to install the postgresql-9.4.1209 jar file in drivers directory for CA.
When using the direct connection via a data module I can generate a simple list report with no errors.
To get proper query flexibility I needed to connect to Mongo using FM so I installed the latest version I could see which was 32bit Windows version 11.0.1.
I placed the postgresql-9.4.1209 jar file in the C:\Program Files (x86)\ibm\cognos\model\webapps\p2pd\WEB-INF\lib directory as it is a 32bit app.
The problem I have is that when I verify my Model I get the following error:
XQE-DAT-0004 A decimal type with precision 131089 and scale 0 is invalid.
I can't seem to change this setting as it is detected by FM when using the Model Wizard so am wondering if there is a different driver or I have it in the wrong location.
Any thoughts appreciated.

Binway

Hi,

If you're using Dynamic Query Mode, the only place the jdbc needs to be located is in the Drivers folder on the application server machine(s). You don't need it on the FM machine - FM connects to the server and uses the driver on the server to retrieve data.

If you have an 11.0.3 server instance of Cognos Analytics, you need the corresponding 11.0.3 version of Framework Manager too. It looks like currently you have a version mismatch. Grab the FM install from the main 11.0.3 distribution assembly on the downloads page and replace your 11.0.1 install with 11.0.3. See if you still get the same error...

Cheers!

MF.

[Binway]

Thanks for the info.
Uninstalled the old FM version, found the new 11.0.3 FM installation exe and have installed that.
Still get the error, was advised to raise a PMR with IBM so if I can get a resolution from them I will add it here.

Regards

Binway

[MFGF]

Thanks for the info.
Uninstalled the old FM version, found the new 11.0.3 FM installation exe and have installed that.
Still get the error, was advised to raise a PMR with IBM so if I can get a resolution from them I will add it here.

Regards

Binway

Ahhh, that's a shame. I was hoping it was just the version mismatch causing the problem. Let us know how you get on with the support call - hope it's soon fixed!

Cheers!

MF.

[the6campbells]

The Mongo BI-connector describes all numeric and character types to Postgres (which the 1.x product is using) as one of numeric or character types with massive precisions. The numeric types should be bound as Float64 which was not happening in 11.R3 properly.

It is a defect that is fixed in 11.R4

[Binway]

I have downloaded and upgraded from 11.0.3 to 11.0.4 today eg just install .4 over the top of .3 and didn't seem to lose any of my previous work. I created a connection to the MongoDB in Data Server Connections in CA.  I created a new project in Framework Manager  that used this MongoDB Connection and published the package to CA.  I then created a simple list report based on the FM package and it returned data that looks fine.  I would say the issue has been resolved so we are good to create reports directly connected to MongoDB.  Nice.