Viewing the physical query in OBIEE

In the NQQuery.log file the physical query executed on the database is not logged. I have changed the logging level of the user to "2" in the Administration Tool. What else is needed to view the physical query?

Hi ,
if the caching is on your sql runs from cache and you can see 'cache hit' in your NQQuery.log file.If you turn off your caching property from nqsconfig.ini file and purge your cache files from administration tool or manually deleting from its directory then you should see the physical query.
If your caching property is off, I dont have an idea about it.

Similar Messages

How to extract the Physical Query(database Query)

Hi ,
How to extract the Physical Query(database Query) from obiee which was fired in obiee
Regards
Ranga

Hi Ranganath,
Have a look the following links.
Setting Logging level:
http://gerardnico.com/wiki/dat/obiee/loglevel
How to see physical query:
http://gerardnico.com/wiki/dat/obiee/manage_session_log
If you are new to OBIEE, spend some hours on the following blog to learn from basics to advanced level.
http://gerardnico.com/wiki/
http://obiee101.blogspot.com/
http://www.rittmanmead.com/blog/
Hope it helps you.
Regards,
Kalyan Chukkapalli
http://123obi.com

Physical Query in OBIEE 10g vs OBIEE 11g

Hi Everyone,
We're in the middle of an OBIEE 10g to an OBIEE 11.1.1.6.4 upgrade and as part of our assembly testing we were planning on comparing the physical query generated for a report generated in obiee 10g vs the physical query for a report in obiee 11g.
After a couple reports we noticed that the query structure in 11g is completely different than the query structure in 10g. The reports still generated the same data in 10g vs 11g. So my question is:
1) is it worth while (or necessary) to do a physical query comparison for an obiee 10g to 11g upgrade? or is validating the front-end report data & drill down/interactions adequate?
2) what are some general reasons why a query generates differently in obiee 10g vs 11g?

Pl post details of OS versions, exact database versions (to 4 digits) and init.ora parameters of the 10g and 11g databases. Have statistics been gathered after the upgrade ?
For posting tuning requests, pl see these threads
HOW TO: Post a SQL statement tuning request - template posting
When your query takes too long ...
Pl see if the SQL Performance Analyzer can help - MOS Doc 562899.1 (TESTING SQL PERFORMANCE IMPACT OF AN ORACLE 9i TO ORACLE DATABASE 10g RELEASE 2 UPGRADE WITH SQL PERFORMANCE ANALYZER)
HTH
Srini

How to view the sql query?

hi,
how to view the sql query formed from the xml structure in the receiver jdbc?

You can view SAP Note at
http://service.sap.com/notes
But you require SMP login ID for this which you should get from your company. The content of the notes are as follows:
Reason and Prerequisites
You are looking for additional parameter settings. There are two possible reasons why a feature is available via the "additional parameters" table in the "advanced mode" section of the configuration, but not as documented parameter in the configuration UI itself:
Category 1: The parameter has been introduced for a patch or a SP upgrade where no UI upgrade and/or documentation upgrade was possible. In this case, the parameter will be moved to the UI and the documentation as soon as possible. The parameter in the "additional parameters" table will be deprecated after this move, but still be working. The parameter belongs to the supported adapter functionality and can be used in all, also productive, scenarios.
Category 2. The parameter has been introduced for testing purposes, proof-of-concept scenarios, as workaround or as pre-released functionality. In this case, the parameter may or may not be moved to the UI and documentation, and the functionality may be changed, replaced or removed. For this parameter category there is no guaranteed support and usage in productive scenarios is not supported.
When you want to use a parameter documented here, please be aware to which category it belongs!
Solution
The following list shows all available parameters of category 1 or 2. Please note:
Parameter names are always case-sensitive! Parameter values may be case-sensitive, this is documented for each parameter.
Parameter names and values as documented below must be used always without quotaton marks ("), if not explicitly stated otherwise.
The default value of a parameter is always chosen that it does not change the standard functionality
JDBC Receiver Adapter Parameters
1. Parameter name: "logSQLStatement"
              Parameter type: boolean
              Parameter value: true for any string value, false only for empty string
              Parameter value default: false (empty String)
              Available with: SP9
              Category: 2
              Description:
              When implementing a scenario with the JDBC receiver adapter, it may be helpful to see which SQL statement is generated by the JDBC adapter from the XI message content for error analysis. Before SP9, this can only be found in the trace of the JDBC adapter if trace level DEBUG is activated. With SP9, the generated SQL statement will be shown in the details page (audit protocol) of the message monitor for each message directly.
              This should be used only during the test phase and not in productive scenarios.
Regards,
Prateek

How to view the physical size of objects

Hi
Please advise how to view the physical size of objects like tables, indexes, materialize views etc.
Wishes
Jawad

To see the physical size of objects like tables, indexes, use
USER_SEGMENTS where SEGMENT_TYPE=table/index/partition etc.
But for views/packages/java/trigger, you can only see rough estimate in USER_OBJECT_SIZE

Addition of Filters on Answers changing the physical query

Hello,
I have three Dimensions D1, D2 and D3 joining (as left outer join in BM layer, i have a requirement where i have to show all the records from Dimension) to a common Fact 'F'
I am trying to build a report based on columns from 3 dimensions.
The report gives a correct output, and returns a single physical query.
If i add a filter condition from say D1 on the report like D1.Col = <something> on the answers report, the physical
query splits in two and then join the two query to give the result.
Any thoughts what could have gone wrong here?
Thank You

hi..
First tell me all dimensions are left outer with fact?
Then, check your fact table LTS levels..
If you have created hierarchies for dimensions, and all dimensions are directly connected to the facts... then, mention the levels for particular fact LTS to detail level for all dimensions. .
Check this...

Logging level to get the physical query

Hi All,
Can anyone let me know , what log level i have set it up, so that I can get the physical query for BI Answers request.
Thanks
S

hi,
Logging Levels
Level 0
No logging.
Level 1
Logs the SQL statement issued from the client application.
Logs elapsed times for query compilation, query execution, query cache processing, and back-end database processing.
Logs the query status (success, failure, termination, or timeout). Logs the user ID, session ID, and request ID for each query.
Level 2
Logs everything logged in Level 1.
Additionally, for each query, logs the repository name, business model name, presentation catalog (called Subject Area in Answers) name, SQL for the queries issued against physical databases, queries issued against the cache, number of rows returned from each query against a physical database and from queries issued against the cache, and the number of rows returned to the client application.
Level 3
Logs everything logged in Level 2.
Additionally, adds a log entry for the logical query plan, when a query that was supposed to seed the cache was not inserted into the cache, when existing cache entries are purged to make room for the current query, and when the attempt to update the exact match hit detector fails.
Do not select this level without the assistance of Technical Support.
Level 4
Logs everything logged in Level 3.
Additionally, logs the query execution plan. Do not select this level without the assistance of Technical Support.
Level 5
Logs everything logged in Level 4.
Additionally, logs intermediate row counts at various points in the execution plan. Do not select this level without the assistance of Technical Support.
Level 6 and 7
Reserved for future use.
Hope this helps,
cheers,
vineeth

How to view the sql query generated in query designer..?

Hi experts,
Can i view the sql query generated by the query designer for a query in sap bw?
regards,
ksvsivam

Hi Sivam,
You can definitely view the sql query.
Go to RSRT and give the report name. Then goto Execute+Debug and click on it.
A new window will open, there tick the box Display SQL/BIA Query and the press on the ok button.
Finally click on execute. The Sql query will be displayed.
Hope this helps.
Thanks,
Rahul

Creating views in Physical Layer of OBIEE Administration Tool

Hello,
I am doing a proof of concept of creating an OBIEE repository using the Administration Tool to make a model for an in house sandbox OLTP system. Because this POC isn't using a warehouse that is built nicely with everything I need, I am having to import the OLTP tables into the Physical Layer and then create a few extra views (by creating a new physical table object and selecting "Table Type: Select") to add some new columns I will need.
My problem is that once I have created two views 'ViewA' and 'ViewB', I want to then create a third view 'ViewC' that is the union of 'ViewA' and 'ViewB'. But when I create ViewC from these two views and try to then update row count or view data in newly created ViewC, I get an error message of the effect:
Message 208: Invalid object name 'DBO.ViewA'
Message 208: Invalid object name 'DBO.ViewB'
When I try and create ViewC with DBO.OriginalTableA and DBO.OriginalTableB, however, it works just fine. And I am also able to successfully update row count and view data in ViewA and ViewB independently. So it seems to me like a view initialization problem when trying to have ViewC be created from A and B.
Am I trying to do something that is not allowed in the Physical Layer of the BI Admin Tool? I would think that I should be able to work with views just like actual physical tables from my OLTP. Maybe not.
Any help or insight would be greatly appreciated. Many thanks.

Hi Hammett81 ,
I think, I have given configured connection pool correct. (following Oracle guidelines: 'In the Connection Pool dialog box, on the General tab, verify that the call interface is set to Default (OCI 10g) and change the data source name to the appropriate tnsnames.ora entry ( ORCL in this example). Please note that this is the TNS service name, not the ODBC DSN. ' )
I tried to give ODBC DSN (SH) as call interface, which resulted in an Error dialogue, implying, previous configuration was correct.
So, I reverted back.
Regards,
Deeba

Physical Query of OBIEE

Hi All,
I noticed in many queried of OBIEE to database containing the select 0 as c1. Please let me know why it is firing 0 from table if so it always return zero for particular coulmn. Can any plz let me know whats the logic behind it..
Below is the one of the query where OBIEE uses select 0 as c1
select D1.c1 as c1,
D1.c2 as c2,
D1.c3 as c3,
D1.c4 as c4
from
(select D1.c1 as c1,
D1.c2 as c2,
D1.c3 as c3,
D1.c4 as c4
from
*(select 0 as c1,*
D1.c2 as c2,
D1.c1 as c3,
D1.c3 as c4,
ROW_NUMBER() OVER (PARTITION BY D1.c2, D1.c3 ORDER BY D1.c2 ASC, D1.c3 ASC) as c5
from
(select LAST_VALUE(D1.c4) OVER (PARTITION BY D1.c3 ORDER BY NVL2(D1.c4, 1, 0) , D1.c3 NULLS FIRST, D1.c5 NULLS FIRST ROWS BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING) as c1,
D1.c2 as c2,
D1.c3 as c3
from
(select T156337.MCAL_PER_NAME_YEAR as c2,
T156337.MCAL_YEAR_WID as c3,
sum(T134466.BALANCE_GLOBAL1_AMT) as c4,
T156337.ROW_WID as c5
from
W_MCAL_DAY_D T156337 /* Dim_W_MCAL_DAY_D_Fiscal_Day */ ,
W_GL_GROUP_ACCOUNT_D T102174 /* Dim_W_GL_GROUP_ACCOUNT_D */ ,
W_GL_BALANCE_A T134466 /* Fact_Agg_W_GL_BALANCE_A */
where ( T102174.ROW_WID = T134466.GROUP_ACCT_WID and T102174.GROUP_ACCOUNT_NUM = 'AR' and T134466.BALANCE_DT_WID = T156337.ROW_WID )
group by T156337.ROW_WID, T156337.MCAL_YEAR_WID, T156337.MCAL_PER_NAME_YEAR
) D1
) D1
) D1
where ( D1.c5 = 1 )
) D1
order by c1, c2

I don't see it in NQQuery log:(
Ideally, it should be because it will hit BI Server. Moreover, I can see it (report's logical SQL) in BI Server Cache.
Any other thoughts?

Re: View physical query issued by Obiee 11g

Guys,
I want to view the physical query generated by the report in OBIEE 11g, but in the logs, i can only see these queries: (Just writing the first line to illustrate)
SELECT
0 s_0,
"Marketing Contact List"."- Account Address"."Billing Abode Name" s_1,
And this query:
RqList distinct
0 as c1 GB,
Account.Billing Abode Name as c2 GB,
Both these queries are NOT the physical ones.
I have the appropriate log level, and even set it manually from the front end, but I'm unable to view the physical query. Please help!

A.Budd,
After running a report in OBIEE, click the Administration Link in the top right corner. New window appears and select "Manage Sessions". Look for the latest time executed that applies to the time you executed your report and click View Logs. Scroll almost to the bottom of the log.
What you are looking for is the generated logic that starts with "*With*"
WITH
SAWITH0 AS (select sum(T443244.AGING030) as c1,
sum(T443244.AGING6190) as c2,
sum(case when T443244.CURRENCYCODE = 'C
Copy the whole logic from WITH to the end of the logic (typically ends with Order By) (not the log) and paste it in your query tool. This is based on the physical layer.
Antexity

Syntax error in OBIEE generated Physical query - Advance filter concept

I encountered a syntax error when running a report with the help of advanced filter concept.
I am getting syntax error at the physical query generated by the OBIEE for main report.
I used a sub report with the help of advanced filter concept in main report.
I am posting the physical query for the convenience.
select D1.c2 as c1,
D1.c1 as c2
from
(select sum(T600347.sales_usd) as c1,
T601002.currency as c2
from
(Select distinct currency from pfact) T601002,
pfact T600347
where ( T600347.currency = T601002.currency and T600347.pdate between ( select distinct min(D1.c1) as c1* from
(select D1.c1 as c1
from
(select D1.c1 as c1
from
*(select max(T600425.pdate) as c1*
from
*(select distinct pdate from pdates where pdate is not null) T600425*
where ( T600425.pdate < 11/22/2010 )
*) D1*
) D1
) D1 ) and '11/25/2010')
group by T601002.currency
) D1
I executed the query against my database(sybase) in query tool. It showed error.
I took out the column alias generated by the OBIEE ("as c1" as underlined). Then the query is working fine.
How to disable OBIEE from generating the alias.
Is there any way to do it.
If obiee is generating the physical query, i am suprised to see a syntax error.
The bold part is the query from Intermediate report
I underlined the problematic part.
Please help me. This is an urgent reuirement,
Thanks in advance for the help.

HI,
When I execute the query on query tool ( my database is sybase)
I am geting error at "as c1" part, as underlined in the query.
when I remove that and execute the query, It is generating the output.
here is the better view of query and error:
http://img255.imageshack.us/img255/4719/25187227.jpg

Physical query generation: unneeded dimension tables get joined to the fact

Hi there!
The setup is the following:
There is a logical fact table which is joined to 7 logical dimensions, it has 4 table sources which correspond to different time dimension levels (all other dimensions are mapped to Detail level).
Time dimension logical table also has 4 different table sources (for days, months, quarters, and years).
The data source is an Oracle Database 11gR2.
The problem is:
No matter what the logical query is, in the physical query all 7 joins are performed, even if the resulting data is then simply discarded. This results in very bad query performance.
I feel that it is somehow related to the level-based fragmentation (since, for instance, inclusion of time dimension columns in SELECT list (not in WHERE) seems to affect physical queries), but lack sufficient knowledge to solve this problem or put up with it.
My questions are the following:
1) Have you ever encountered such a situation?
2) Can unneeded joins be eliminated?
2.1) If yes, how?
2.2) If not, then why are they needed?
Thanks in advance!

Physical level:
D01-D06 - ordinary physical tables.
D_DATES - all time levels from dates to years, D_MONTHS - time levels from months to years, also D_QUARTERS and D_YEARS.
F_DAILY - fact table joined to all of the D01-D06 and to D_DATES, F_MONTHLY - joined to D01-D06 and D_MONTHS, also F_QUARTERLY and F_YEARLY. All measure columns are the same.
Logical level:
D01-D06 correspond to ordinary logical tables with a single table source. Logical dimensions are created.
D_TIME is a logical time dimension with four levels (dates, months, quarters, and years) and four table sources ( D_DATES, D_MONTHS, D_QUARTERS, and D_YEARS ).
F is a fact table with four logical table sources ( F_DAILY, F_MONTHLY, F_QUARTERLY, and F_YEARLY ) with aggregation content levels set correspondingly.
OBIEE correctly picks physical table sources for different time levels, but generates extremely inefficient SQL (joining all dimension sources in a WITH-subquery, doing ROW_NUMBER over a result set, and then discarding half the columns, which were not needed to start with).

OBIEE Issue - Physical Query not picking cascaded Conditions

In one the OBIEE Reports, I have given a set of NOT LIKE conditions as below:
Session Name is not LIKE (pattern match) '%AUDIT%'
AND Session Name is not LIKE (pattern match) '%audit%'
AND Session Name is not LIKE (pattern match) '%Audit%'
But when we refresh the report, it filters only records which uses AUDIT keyword as part of Session Names. When I checked the session log (attached for reference), I found that though logical table query takes those three conditions, while firing against database Physical Query contains condition only for AUDIT wild card as filter. Whether there is any limitation applied on using NOT LIKE conditions or is it a bug or the way the conditions are sequenced is wrong (in OBIEE sense).

Thanks buddy. Though this workaround will solve the issue, I am curious to know why OBIEE behaves such a way. Its peculier to see OBIEE admits all 3 conditions in logical query where the Physical query skips few of the conditions in session log itself.

View the query in runtime in oaf

Can anyone please tell me that is it possible to view the execution query on the fly like in php i can see the statement by var_dump($sql).
i would like to see the execution sql script on the fly.
would you please tell the way if possible.
mofizur

mofizur,
You can make use of vo.getQuery before vo.executeQuery to get the script.
Regards,
Gyan

Viewing the physical query in OBIEE

Similar Messages

Maybe you are looking for