Tag Archives: NQSERROR

ORACLE not available ORA-27101: shared memory realm does not exist Linux-x86_64

Problem: Error message in report

Screenshot:

Shared memory realm does not exist Linux-x86_64

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.

The logical column referenced by DESCRIPTOR_IDOF does not specify a Descriptor ID column

Problem: Error message in report

Screenshot:

The logical column referenced by DESCRIPTOR_IDOF does not specify a Descriptor ID column

Screenshot text:

State: HY000. Code: 10058. [NQODBC][SQL_STATE: HY000][nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 23026] The logical column referenced by DESCRIPTOR_IDOF does not specify a Descriptor ID column. (HY000)

SQL Issued: {call NQSGetQueryColumnInfo("SELECT DESCRIPTOR_IDOF([COLUMN]) FROM ([SUBJECT_AREA])}

Possible solution:

  • log in to OBIEE as administrator
  • edit the report
  • remove the filter that is defined on the column [COLUMN]
  • save the report
  • (optional) add the filter again
  • save the report
  • click Administration on the top right
  • click Reload Files and Metadata

Reload Files and Metadata

  •  go back to the report

Now, the error message is not displayed anymore.

Het bericht The logical column referenced by DESCRIPTOR_IDOF does not specify a Descriptor ID column verscheen eerst op OBIEE 24/7.

The logical column referenced by DESCRIPTOR_IDOF does not specify a Descriptor ID column

Problem: Error message in report

Screenshot:

The logical column referenced by DESCRIPTOR_IDOF does not specify a Descriptor ID column

Screenshot text:

State: HY000. Code: 10058. [NQODBC][SQL_STATE: HY000][nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned from OBIS. [nQSError: 23026] The logical column referenced by DESCRIPTOR_IDOF does not specify a Descriptor ID column. (HY000)

SQL Issued: {call NQSGetQueryColumnInfo("SELECT DESCRIPTOR_IDOF([COLUMN]) FROM ([SUBJECT_AREA])}

Possible solution:

  • log in to OBIEE as administrator
  • edit the report
  • remove the filter that is defined on the column [COLUMN]
  • save the report
  • (optional) add the filter again
  • save the report
  • click Administration on the top right
  • click Reload Files and Metadata

Reload Files and Metadata

  •  go back to the report

Now, the error message is not displayed anymore.

Het bericht The logical column referenced by DESCRIPTOR_IDOF does not specify a Descriptor ID column verscheen eerst op OBIEE 24/7.

Oracle BI Scheduler: TNS:listener does not currently know of service requested

Problem: BI Scheduler error in the Enterprise Manager.

Screenshot:

TNS listener does not currently know of service requested in connect descriptor at OCI call OCIServerAttach

Screenshot text:

The next error occured: Error Oracle BI Scheduler: [nQSError: 17014] Could not connect to Oracle database. [nQSError: 17001] Oracle Error code: 12514, message: ORA-12514: TNS:listener does not currently know of service requested in connect descriptor at OCI call OCIServerAttach. [nQSError: 68021] Message from Oracle BI Scheduler.

Solution:

  • log in to the console of the environment
  • click on Business Intelligencecoreapplication
  • click on DeploymentScheduler

TNS listener does not currently know of service requested in connect descriptor at OCI call OCIServerAttach - enterprise manager

  • click Lock and Edit Configuration
  • copy the string from Data Source. The format is like
  • (DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=[HOSTNAME])(PORT=[PORTNUMBER])))(CONNECT_DATA=(SERVICE_NAME=[SERVICENAME])))

[HOSTNAME], [PORTNUMBER] and [SERVICENAME] must be filled in.

  • open SQL Plus

TNS listener does not currently know of service requested in connect descriptor at OCI call OCIServerAttach - sql plus

  • paste the string in Host String
  • click OK

If the Host String is wrong, then you will see the message “ORA-12514: TNS:listener does not currently know of service requested in connect descriptor”

TNS listener does not currently know of service requested in connect descriptor at OCI call OCIServerAttach - sql plus 2

  • change the Host String until you are succesfully logged in
  • copy the Host String that you used
  • paste it in the Data Source in Enterprise Manager
  • click restart to apply recent changes
  • restart all services.

Now the error message will not be displayed and the BI Scheduler will work again.

Het bericht Oracle BI Scheduler: TNS:listener does not currently know of service requested verscheen eerst op OBIEE 24/7.

Internal error: No matching table for expr

If you are editing a report and get this error message;

Internal error No matching table for expr

then probably an applied filter is the problem.

In my case, one of the filter on my report was

http://bi01.boekhuis.nl:9804/analytics/res/sk_blafp/answers/filter_protect.png Day is equal to / is in @{[repository_variable]}

After removing this filter, the error message was gone.

Het bericht Internal error: No matching table for expr verscheen eerst op OBIEE 24/7.