Tag Archives: NQSERROR
Looping chain of synonyms at OCI call OCIStmtExecute
Problem: Error in report
Screenshot:
Screenshot text:
State: HY000. Code: 10058. [NQODBC][SQL_STATE: HY000][nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 17001] Oracle Error code: 1775, message: ORA-01775: looping chain of synonyms at OCI call OCIStmtExecute. [nQSError: 17010] SQL statement preperation failed. (HY000)
Possible cause:
The table that is queried is deleted, but the synonym on the table still exists.
Possible solution:
- open SQL plus or SQL developer
- log in to the database and schema that has to contain the table
- check if the table exists
- if it doesn’t exist, create the table (again)
- go back to the report
- refresh the result
The error message is not displayed anymore.
Het bericht Looping chain of synonyms at OCI call OCIStmtExecute verscheen eerst op OBIEE 24/7.
Invalid identifier at OCI call OCIStmtExecute
Problem: Error when editing initialization block
Screenshot:
Screenshot text:
[NQODBC][SQL_STATE: HY000][nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 43093] An error occurred while processing the EXECUTE PHYSICAL statement. [nQSError: 17001] Oracle Error code: 904, message: ORA-00904: [IDENTIFIER]: invalid identifier at OCI call OCIStmtExecute. [nQSError: 17010] SQL statement preparation failed.
Solution:
- edit the SQL statement
- change the part that is using [IDENTIFIER] to a part that is not using [IDENTIFIER]
- save the statement
The error message is not displayed anymore.
Het bericht Invalid identifier at OCI call OCIStmtExecute verscheen eerst op OBIEE 24/7.
Identifier is too long at OCI call OCIStmtExecute
Problem: Error when editing initialization block
Screenshot:
Screenshot text:
[NQODBC][SQL_STATE: HY000][nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 43093] An error occurred while processing the EXECUTE PHYSICAL statement. [nQSError: 17001] Oracle Error code: 972, message: ORA-00972: identifier is too long at OCI call OCIStmtExecute. [nQSError: 17010] SQL statement preparation failed.
Possible cause:
Oracle identifiers are not allowed to exceed 30 characters in length. An identifier with a length greater than 30 is used in the initialization block.
Solution:
- edit the SQL statement
- search for identifier(s) with a length greater than 30 characters (mostly these are aliases)
- abbreviate this identifier(s)
- save the statement
The error message is not displayed anymore.
Het bericht Identifier is too long at OCI call OCIStmtExecute verscheen eerst op OBIEE 24/7.
Set operation failed due to incompatible sort order
Problem: Error message in report
Screenshot:
Screenshot text:
State: HY000. Code: 10058. [NQODBC][SQL_STATE: HY000][nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 59107] Set operation failed due to incompatible sort order. (HY000)
Possible solution:
- click Criteria
- click Result Columns
- change Union to Union All
- go to Results
- (optional) click refresh
The error message is not displayed anymore.
Het bericht Set operation failed due to incompatible sort order verscheen eerst op OBIEE 24/7.
Set operation failed due to incompatible sort order
Problem: Error message in report
Screenshot:
Screenshot text:
State: HY000. Code: 10058. [NQODBC][SQL_STATE: HY000][nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 43119] Query Failed: [nQSError: 59107] Set operation failed due to incompatible sort order. (HY000)
Possible solution:
- click Criteria
- click Result Columns
- change Union to Union All
- go to Results
- (optional) click refresh
The error message is not displayed anymore.
Het bericht Set operation failed due to incompatible sort order verscheen eerst op OBIEE 24/7.
