Tag Archives: NQSERROR

July 29, 2016   Berry van den Heuvel

Invalid identifier at OCI call OCIStmtExecute (2)

Problem: Error when editing report

Screenshot:

invalid identifier at OCI call OCIStmtExecute (2)

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: "[TABLE_NAME]"."[COLUMN_NAME]": invalid identifier at OCI call OCIStmtExecute. [nQSError: 17010] SQL statement preparation failed.

Possible solution:

The physical column “[TABLE_NAME]”.”[COLUMN_NAME]” doesn’t exist anymore.

  • remove this column from the physical layer or create it in the database
  • check in
  • refresh screen

The error message is not displayed anymore.

Het bericht Invalid identifier at OCI call OCIStmtExecute (2) verscheen eerst op OBIEE 24/7 - Berry van den Heuvel (NL).

Read More
October 20, 2015   Berry van den Heuvel

The physical column has property Length set to zero

Problem: Consistency Check Warning No. 39064

Screenshot:

The physical column has property Lenght set to zero

Screenshot text:

WARNINGS: 
GLOBAL:
[39064] The physical column '[PHYSICAL_SCHEMA].[PHYSICAL_DB]."S_NQ_ACCT"."QUERY_BLOB"' has property Length set to zero.

Solution:

When you view data in physical layer, the column is not displayed in the results

  • double click on the physical column, in this case QUERY_BLOB

The physical column has property Lenght set to zero 2

  • set Length to 4000 (= maximum size)
  • click OK
  • check consistency
Twitt

Het bericht The physical column has property Length set to zero verscheen eerst op OBIEE 24/7 | Oracle Business Intelligence.

Read More
April 27, 2015   Berry van den Heuvel

No fact table exists at the requested level of detail

Problem: Display Error in report

Screenshot:

No fact table exists at the requested level of detail

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: 14025] No fact table exists at the requested level of detail: [,,,,,,,[NAME.NAME],,,,]. (HY000)

Possible cause:

Initially, the physical tables were dragged from the physical layer to the business layer. Because of this, the logical join was created automatically. Recently, the physical join is changed, but in the Business Model the join is not changed (automatically).

Possible solution:

  • open Administration Tool
  • open repository
  • show Business Model diagram
  • remove logical join
  • add logical join again
  • check in
  • refresh report

The error message is not displayed anymore.

Twitt

Het bericht No fact table exists at the requested level of detail verscheen eerst op OBIEE 24/7 | Oracle Business Intelligence.

Read More
March 30, 2015   Berry van den Heuvel

Invalid character at OCI call

Problem: Error when trying to save physical select statement

Screenshot:

invalid character at OCI call

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: 911, message: ORA-00911: invalid character at OCI call OCIStmtExecute. [nQSError: 17010] SQL statement preparation failed.

Possible solution:

  • remove comments (including /* and */)
  • remove semicolons / ;
  • save physical statement

 

Twitt

Het bericht Invalid character at OCI call verscheen eerst op OBIEE 24/7 | Oracle Business Intelligence.

Read More
March 20, 2015   Berry van den Heuvel

Not a valid month at OCI call OCIStmtExecute

Problem: Error in report

Screenshot:

Not a valid month at OCI call OCIStmtExecute

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: 1843, message: ORA-01843: not a valid month at OCI call OCIStmtExecute: select [STATEMENT] [nQSError: 17011] SQL statement execution failed. (HY000)

Possible cause:

One of the causes can be that the repository variable that is used, is not of the type Date.

Possible solution:

  • edit the variable block
  • change the type of the error causing repository variable.

for example, if the definition is

to_char(to_date(max(day_number),'yyyymmdd'),'dd-mm-yyyy') as var_date

then change it to

to_date(max(day_number),'yyyymmdd') as var_date
  • go back to the report
  • refresh
Twitt

Het bericht Not a valid month at OCI call OCIStmtExecute verscheen eerst op OBIEE 24/7.

Read More
« Older posts