Hyperion SQR Production Reporting Job with a Complex 'WHERE' Clause in the Input Parameter Gets Corrupted After LCM Import
Last updated on SEPTEMBER 16, 2016
Applies to:Hyperion BI+ - Version 220.127.116.11.00 and later
Information in this document applies to any platform.
A simple SQR job is published in Workspace with an INPUT parameter defined with "Choice of values obtained from a SQL query".
Data Type: String
In the SQL query section of the job in the INPUT parameter, a long complex (but valid) SQL query is inserted which contains SELECT, WHERE clause, SUBSTR, OR, AND, NOT IN, GROUP BY, etc.
An export of this SQR job is done using LCM, and later an import of this same job is done (both export/import say "completed" in the LCM migration report).
When right-clicking and selecting properties on the imported job in Workspace, the following error message is returned:
"Unable to perform request
A general error was encountered contacting the server.
Detailed Message: Error in com.sqribe.transformer.GetContainerCommand.execute();
Recommended Action: Contact your corporate technical support."
- When trying to delete the imported job the following error is returned:
"Could not delete: 1000174".
It seems the imported job gets corrupted when the parameter is complex/long.
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