Error: Select members failed [Cannot query members by name. Essbase Error(1007090) When Run Financial Reporting (FR) Batch with Bursting Enabled

(Doc ID 2329637.1)

Last updated on DECEMBER 05, 2017

Applies to:

Hyperion BI+ - Version 11.1.2.3.700 to 11.1.2.4.003 [Release 11.1]
Information in this document applies to any platform.

Symptoms

An error is thrown in the Financial Reporting Batch Scheduler for batches that use bursting.

The batch status reflects an error and it creates an erroneous folder with wording Error: Could not obtain alias for given grid.

The following error message appears in FRLogging:

[FinancialReporting0] [ERROR] []
[oracle.EPMFR.core] [tid: [ACTIVE].ExecuteThread: '1' for queue:'weblogic.kernel.Default (self-tuning)'] [userId: <anonymous>] [ecid:0000Jet8kA6ESOG_Ix5Eif1G^RAF000005] [APP:FINANCIALREPORTING#11.1.2.0]
[URI:/hr/modules/com/hyperion/reporting/web/scheduler/HRSchedulerClient.jsp]
[SRC_CLASS: com.hyperion.reporting.util.MessageHelper] [SRC_METHOD:getMessage] [[
java.util.MissingResourceException: Can't find resource for bundle
java.util.PropertyResourceBundle, key Error executing query: Error: Select
members failed [Cannot query members by name. Essbase Error(1007090): Unknown
member name [User Point of View for Time Periods] in Outline Query]
at java.util.ResourceBundle.getObject(ResourceBundle.java:374)
at java.util.ResourceBundle.getObject(ResourceBundle.java:371)
at java.util.ResourceBundle.getString(ResourceBundle.java:334)
at com.hyperion.reporting.util.MessageHelper.getMessage(MessageHelper.java:170)
at com.hyperion.reporting.scheduler.JobStatusObject$JobStatusMessage.getLocalizedMessage(JobStatusObject.java:246)
at com.hyperion.reporting.scheduler.JobStatusObject.getDescriptiveStatus(JobStatusObject.java:66)


Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms