Category Archives: Berry van den Heuvel
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.
ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64
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] The query failed: [nQSError: 17001] Oracle-foutcode: 1034, bericht: ORA-01034: ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 Error: 2: No such file or directory at OCI call OCISessionBegin. [nQSError: 17014] Can not connection to the Oracle Database (HY000)
Possible solution:
- edit tnsnames.ora
- search for the entry that is used in the connectionpool the report is using
Example:
[DSN] = (DESCRIPTION = (LOAD_BALANCE=off)(FAILOVER=on) (ADDRESS = (PROTOCOL = TCP) (HOST=[HOST1])(PORT=[PORT1])) (ADDRESS = (PROTOCOL = TCP) (HOST=[HOST2])(PORT=[PORT2])) (CONNECT_DATA = (SERVICE_NAME = [SERVICENAME]) (FAILOVER_MODE=(TYPE=SELECT)(METHOD=BASIC))) )
if the entry contains 2 addresses, then probably you have to add an ADDRESS_LIST.
- add the red parts
[DNS] = (DESCRIPTION = (LOAD_BALANCE=on) (FAILOVER=on) (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST=[HOST1])(PORT=[PORT1])) (ADDRESS = (PROTOCOL = TCP) (HOST=[HOST2])(PORT=[PORT2])) ) (CONNECT_DATA = (SERVICE_NAME = [SERVICENAME]) (FAILOVER_MODE=(TYPE=SELECT)(METHOD=BASIC))) )
- refresh the report
Now, the error message is not displayed anymore.
Het bericht ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64 verscheen eerst op OBIEE 24/7.
