My method so far to make changes to our existing reports has been to
1. Open the report
2. Modify
(Most, if not all, are Direct Database Requests)
3. Cut and Paste the SQL into my editor (JDeveloper)
4. Fix any issues
5. Run in SQL*Plus
6. Cut and paste back into OBIEE
On occasion, I’ll have to use the Catalog Manager, select report, properties, Edit XML and get the SQL from there. Obviously not the most efficient way, but it works.
Others, like Mr. Berg, have suggested turning the log level to level 2 and capturing the SQL being passed to the database. I’m not that industrious yet.
Anyway, I’ve run across this error a couple of times so far.
When I do number 6 and click on Validate SQL and Retrieve Columns, I get the above mentioned error. Hmmm…I’ve just run this thing in SQL*Plus and it works just fine. The queries are really too big to simply eyeball either.
So I went simple, in the text box I entered SELECT * FROM DUAL and clicked on Validate SQL and Retrieve Columns:
error : Odbc driver returned an error (SQLExecDirectW).
error : State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43093] An error occurred while processing the EXECUTE PHYSICAL statement. [nQSError: 17001] Oracle Error code: 933, message: ORA-00933: SQL command not properly ended at OCI call OCIStmtExecute. [nQSError: 17010] SQL statement preparation failed. (HY000)
error : SQL Issued: {call NQSGetQueryColumnInfo(‘EXECUTE PHYSICAL CONNECTION POOL «BIDEV».»Connection Pool» SELECT * FROM DUAL when mailing_group = »EMPLOYEE» then »Other» when mailing_group = »TEST» then »Other» when mailing_group = »VIP-EXTERNAL» then »Other» when mailing_group = »SITEUSERS» then »Other» else mailing_group end )’)}
It appears the query that previously occupied that box is still there…partially.
Mr. Berg suggested clearing the cache, so I went into the Administration tool, Manage, but cache was grayed out. I asked the DBA and Linux guy to pass me the file, but they were being difficult today, so I didn’t get it.
In the short term, I just created a new report appended with » R» (refactored) and moved on to the next one. Hopefully tomorrow I’ll be able to get some answers.
After migrating OBIEE from 11g to 12c, BI answers encounter the following error.
Odbc driver returned an error (SQLExecDirectW).
State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. (HY000)
State: HY000. Code: 43113. [nQSError: 43113] Message returned from OBIS. EVALUATE_SUPPORT_LEVEL inside NQSConfig.INI is not set to support EVALUATE. (HY000)
asked Aug 24, 2021 at 2:57
The following workaround can fix the issue.
-
Go to the NQSConfig.INI file location
File location:$DOMAIN_HOME/config/fmwconfig/biconfig/OBIS/
-
Open the NQSConfig.INI
-
Change the following line
EVALUATE_SUPPORT_LEVEL = 0;
to
EVALUATE_SUPPORT_LEVEL = 2;
-
Restart the OBIEE12c services
answered Aug 24, 2021 at 3:08
RejaReja
5341 gold badge9 silver badges17 bronze badges
Here is some python code which is being executed against a HIVE database
pyodbc.autocommit = True
con = pyodbc.connect("DSN=MyCon", autocommit=True)
cursor = con.cursor()
cursor.execute("select name, surname from foo f inner join bar b on f.id = b.id")
Error
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
pyodbc.Error: ('HY000', "[HY000] [Hortonworks][HiveODBC] (35) Error from
Hive: error code: '0' error message: 'ExecuteStatement finished with operation
state: ERROR_STATE'. (35) (SQLExecDirectW)")
asked Apr 16, 2015 at 3:12
Knows Not MuchKnows Not Much
30.1k59 gold badges195 silver badges369 bronze badges
I solved it. when creating the ODBC connection use the user hdfs. I had read a tutorial and was using the user hue.
this caused the problem.
answered Apr 16, 2015 at 3:57
Knows Not MuchKnows Not Much
30.1k59 gold badges195 silver badges369 bronze badges
Hi,
I’m having a problem with ClouderaImpalaODBC64.dll version 2.16.14.1016.
SQLExecDirectW function returns an error when executing the following query:
With variable1 as
(
SELECT orders.order_id, orders.order_date
FROM quest_stage.orders orders
WHERE orders.order_date = (CAST(? AS TIMESTAMP))
)
Select * from variable1
Error details:
[Cloudera][ImpalaODBC] (110) Error while executing a query in Impala: [HY000]: ParseException: Syntax error in line 5
It seems to be the problem when you combine WITH and CAST keywords.
Both of the following queries below work:
SELECT orders.order_id, orders.order_date
FROM quest_stage.orders orders
WHERE orders.order_date = (CAST(? AS TIMESTAMP))
———————————————————————————————-
With variable1 as
(
SELECT orders.order_id, orders.order_date
FROM quest_stage.orders orders
)
Select * from variable1
Could you help me understand what seems to be the problem here and is there any solution to this problem?
I have more:
pyodbc.ProgrammingError: (‘42000’, «[42000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]External file access failed because the specified path name ‘/OK/FILESERVER/SOMEPATH/2019/10/07’ does not exist. Enter a valid path and try again. (105002) (SQLExecDirectW)»)
and
pyodbc.ProgrammingError: (‘42000’, ‘[42000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]HdfsBridge::recordReaderFillBuffer — Unexpected error encountered filling record reader buffer: HadoopExecutionException: Not enough columns in this line. (107090) (SQLExecDirectW)’)
I’m not sure how the SQL server is set up, these logs came from the client, I don’t have direct access to the DB. But googling around, the errors seem related to Parquet or HDFS or Hadoop… maybe some SQL adapter? Is there such thing?
I’ve not seen this before, but I’m thinking the error could be related to the SQL Server’s adapter configuration, rather than pyodbc.
@gordthompson there’s no CAST/CONVERT, this is a straight up SELECT {columns} FROM [db_name].[schema_name].[table_name].