Information

Title	Why the Error 1024 is reported in EP Mid Tier message log?

Summary	This article explains the cause of "Error jda.bi.jade.engines.pkbdatasourcemanager.core.datasourceview CallbackShim::DoLogCallbackFcn: -) 166 (- EQLnnn DSAPI ERROR: (1024)" in the EP Mid-Tier Message Log. and also error - "EQLnnn DSAPI ERROR: (1024) Data source structures have changed." in pkbds.log.

URL Name	Why-the-Error-1024-is-reported-in-EP-Mid-Tier-message-log

Resolution

Wait until Quartz Structure Synchronization has completed.

Products	Enterprise Planning Server Edition

Module	EP Mid-Tier

Version	All

Error Message Code

EPMT message-log
"
'EqlDsGetTimeStamps' failed with: Error 1024: Error when the shape changes and the data source cannot process a 'non-utility' API call. 'Data source structures have changed
Error jda.bi.jade.engines.pkbdatasourcemanager.core.datasourceview CallbackShim::DoLogCallbackFcn: -) 166 (- EQLnnn DSAPI ERROR: (1024)
Warning jda.bi.jade.engines.pkbdatasourcemanager.core.plugin JDAAutoLogger::DumpException: 'LTSPEKB/Cube '<cubename>', Subcube '<cubename'' Unable to get shape time"
"

PKBDS log
"
[Sun Jun 20 08:08:01.636 2010] 0x0c3b6008 tid=86c :EQLnnn DSAPI ERROR: (1024)
[Sun Jun 20 08:08:01.636 2010] 0x0c3b6008 tid=86c :EQLnnn DSAPI ERROR: (1024) Data source structures have changed.
"

Cause

This error may occur if the time stamp on the memory structures for the subcube shapes on the Enterprise Planning MidTier (EPMT) being older than the time stamp that was returned from the database.

Additional Information

This is an expected message when the Quartz Structure Synchronization is executing while EPMT is running
Environment is in a valid state

Publication Status	Published

Why the Error 1024 is reported in EP Mid Tier message log?

Information