Knowledgebase: HFM
Extended Analytic output uses field type "VARGRAPHIC" exporting to DB2, incompatible with EIS
Posted by Priya Doyle on 07 December 2010 05:45 PM

Extended Analytic output uses field type "VARGRAPHIC" exporting to DB2, incompatible with EIS [ID 605572.1]

 Modified 18-JAN-2010 


Symptoms

Run an Extended Analytics database from HFM 9.3.1 to a DB2 schema. Columns which should be created with data-type "NVARCHAR" are being created with data-type "VARGRAPHIC".

This data-type cannot be read by Essbase Integration Services, so the resulting database cannot be used by EIS to create an application.

Changes

This problem will not be seen when using SQLServer or Oracle as target database for Extended Analytics, so you might encounter it when switching to a DB2 instance.

Cause

DB2 does not have the NVARCHAR data type that supports double byte characters, so HFM has to use the VARGRAPHIC data type instead.

Solution

There are very few options for this situation, the following are simple suggestions:

  • generate the Star Schema in an Oracle instance or SQLServer instance.
  • get EIS to somehow CAST the data type from VARGRAPHIC to VARCHAR or similar.


(0 vote(s))
Helpful
Not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments: