OLAPExportHierarchy Error 372

Hi all,

Has anyone experienced and resolved the following error when using OLAPExportHierarchy:

Executing the process failed with an error. The returned message was: An error has occurred:
Calling function 'OLAPExportHierarchy' failed with this message: SQL error during export to SQL process.. Error code '372': SQL error during export to SQL process.

It seems to work for most small dimensions (less than 20 elements) but not for the larger ones, I can't find an exact cause.

V12 M/T, Using Kai's scripts: OLAP to Relational Modeling V3

Thanks in advance,

Ibrahim

Ford GTL.pdf

Find more posts tagged with

Infor EPM Discussions

Comments

martin-reischl

Hi Ibrahim,

I've had this issue too, and worked with Support on it. The script is fine but the export command seems to run into some issues with attributes, under certain conditions. They are giving me hope that the upcoming version 2022.08 will solve the issue. So help may be just around the corner.

Best Regards

Martin

unknown

Thanks for your response Martin, after some investigating I have found the cause; the character '-' is not an accepted character when defining a staging table name, therefore you would find that you can't access dimension view for your created tables (if using Kai's xml creator) for any tables containing '-'.

Quick fix: after the StringReplaceRegex for sTableName is populated, insert

sTableName = StringReplace(sTableName, "-", "", false);

martin-reischl

Hi Ibrahim,

thanks for checking and sharing. I've never come across a dimension or cube name with a "-", so we'd never have found out without your help.

Regards

Martin

vikas-sharma

I encountered the same issue today, encountering Error code '372' in the 2024.04 release. After investigation, I discovered that the problem caused by an attribute field configured as Date. Strangely, it seemed to have issues with the data in date format. However, switching the attribute data type to string resolved the issue.

martin-reischl

Hi Vik, from my own experience this may be due to empty attribute values. The process handles dates well but if the field is empty, it will try to write an empty string to the date field, which will of course fail.

You may have to enter some date into this field for all elements, e.g. 1/1/1900 00:00. Then exporting will work well. You can then still use SQL to replace 1/1/1900 00:00 with NULL. Building the dimension will work in this case.

We are seeing similar effects with numeric and Boolean attributes.

Best Regards

Martin

vikas-sharma

Thanks Martin, fully understand your solution, my concern was that the error message is too generic it doesn't help much in troubleshooting. It will be great if the users get some pointers on where the job is failing and how to rectify the issue, just to save time.

Copyright © 2025 Infor. All rights reserved.