Physical SQL contains apostrophe

In OBIEE-11g, how can we escape apostrophe in physical SQL. For example a filter that contains member name(Amy O'Brien) is being sent as 'where member_name ='Amy O''''Brien'. The four quotes are leading to mismatch of the conditiona and hence not returning any results.
Thanks

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?

Similar Messages

Logical SQL to physical SQL in datamodel.

I am designing a report in BI publisher and for that I am creating a datamodel.
My datamodel contains 4 dataset with 4 different logical SQLs and all use source as Oracle BIEE.
When I generate/execute xml from datamodel I observed in nqquery.log that BI publisher is executing each logical SQL in sequence.
That is OBIEE first send logical SQL of one of the dataset and then convert it to physical SQL. After first physical SQL is completed then only it is converting second logical SQL to physical.
So logical to physical query is happening in sequence rather than in parallel.
My datamodel contains huge logical SQLs and OBIEE takes almost 40 seconds each to convert it physical query. This will result in total 160 seconds for just converting 4 logical SQLs to physical SQLs.
Does anybody know if there is any setting where I can manage to convert multiple logical to physical in parallel?

Hi Experts,
Please help on this.

Logical SQL to physical SQL taking time in datamodel.

I am designing a report in BI publisher and for that I am creating a datamodel.
My datamodel contains 4 dataset with 4 different logical SQLs and all use source as Oracle BIEE.
When I generate/execute xml from datamodel I observed in nqquery.log that BI publisher is executing each logical SQL in sequence.
That is OBIEE first send logical SQL of one of the dataset and then convert it to physical SQL. After first physical SQL is completed then only it is converting second logical SQL to physical.
So logical to physical query is happening in sequence rather than in parallel.
My datamodel contains huge logical SQLs and OBIEE takes almost 40 seconds each to convert it physical query. This will result in total 160 seconds for just converting 4 logical SQLs to physical SQLs.
Does anybody know if there is any setting where I can manage to convert multiple logical to physical in parallel?

Hi Experts,
Please help on this.

Runtime Parameter is failing if it contains apostrophe (')

Hi All,
I have created a simple report in standalone BIP (10.1.3), which has product name as parameter. When we select product, report will display its sales information. In the data set we are not able to get the product number. So we are printing product name in the header using dynamic parameter
<?param@begin:varProduct?>
and in the header <?$varProduct?>
Its working displaying as expected. But when product contains apostrophe ('), program is erroring out. I am able to get the xml data if i select the output type as data. But it is erroring out when i select a template.
Please help.

Sattti,
The easiest way would be to pass the parameter into your sql query select list and use a replace function to replace the apostrophe with '
Now reference this column, instead of a parameter, in your template header/body.
Thanks
-bifacts
http://www.obinotes.com

How to get physical SQL query

Hi All,
How to get the physical SQL query for the OBIEE reports.
Thanks in advance,
Haree.

Hi Anitha,
Thanks for your reply,
I am getting XML script in log file. (Settings > Administration > Manage Sessions > View Log).
How to get physical SQL query ?
Thanks,
Haree

View log not showing physical SQL generated in OBIEE 11.1.1.6.7

Hi,
I am currently using OBIEE 11.1.1.6.7 version. In this version I am unable to view the physical SQL generated by OBIEE under Administration --> Manage Marketing Jobs --> Select a Job --> Click on View SQL OR Administration --> Manage Sessions--> Select a Job --> Click on View SQL. It is not showing the physical SQL generated by OBIEE for a report or segment which I have executed.
It was available in previous version i.e. OBIEE 10.1.3.4.2.
I have searched in metalink and it has been suggested to use the following <Filters> section into instanceconfig.xml file. I have added the following details into existing instanceconfig.xml file and then restarted the BI services. Still the problem persist.
<Filters>
<FilterRecord writerClassGroup="Console" path="saw" information="16" warning="31" error="31" trace="32" incident_error="1"/>
<FilterRecord writerClassGroup="File" path="saw" information="16" warning="31" error="31" trace="32" incident_error="1"/>
<FilterRecord writerClassGroup="Marketing" path="saw.mktgsqlsubsystem.joblog" information="16" warning="31" error="31" trace="32" incident_error="1"/>
<FilterRecord writerClassGroup="File" path="saw.httpserver.request" information="16" warning="31" error="31" trace="32" incident_error="1"/>
<FilterRecord writerClassGroup="File" path="saw.httpserver.response" information="16" warning="31" error="31" trace="32" incident_error="1"/>
</Filters>
Thanks,
Prasanta

Hi,
Thanks for the reply.
We used to view the log details (physical SQL) using Manage Marketing Jobs in OBIEE10g.
In OBIEE11g we can see the job details and when selecting a job (under Action column Details link) there is an option in left pane as 'View Log'. If I click on 'View Log' it is showing as 'No Logs Found'.
Just wanted to confirm if this is an issue in OBIEE11g.
Also, I believe there is a limitation in 'Manage Session' to view the number of job details whereas in 'Manage Marketing Jobs' section we can increase the number of jobs to be displayed.
Thanks,
Prasanta

Difference between logical and physical SQL

Hi all,
I created a dashboard prompt and added some columns from the dimensions and one column from the fact table.
When I run the report in the dashboard and filters using the prompts,I see in the logical sql that all the filters have been applied to the report, but when I check the physical SQL only the filters on the dimensions columns have been applied.
I don't see the filter on the columns from the fact table.
Is there any reason for that?
Regards

I could figure out what was the issue.
My fact table was using a different MV as source table.The fact table column I was using in the prompt was not mapped correctly to the one in the MV.
Regards

OBIEE: logical SQL to Physical sql conversion

Hi,
Is there any way i can get the physical sql from logical sql ( Apart from reading log file).. I am looking something like JAVA api which does that for us.. Do we have any mapping table which stores this mapping.
Does the OBIEE provides any Java API.
Appreciate your help in advance.

Hi Experts,
Please help on this.

[NQQuery log]: Physical SQL generated agaisnt 2 Database in OBIEE 11g

Hi Experts,
I have a problem regarding the physical SQL generated by Query log.
So this is the setup.
SCENARIO 1:
Oracle Data Warehouse DB
- col1
- col2
- col3
OLAP_OBIEE
- col4
When I run these columns together in Analysis. It seems like the physical SQL generated in the Query log is partitioned with each other and I cant get the exact SQL so I can make comparison with the total record count in Analysis UI and the SQL developer.
select col1, col2, col3 from Oracle Data Warehouse tables
select col4 from OLAP_OBIEE tables
================================================================
SCENARIO 2:
Oracle Data Warehouse DB
- col1
- col2
- col3
- col4
Running these columns together in Analysis. I am wondering why the physical SQL is somewhat also partitioned just like in SCENARIO 1.
select col1, col2, col3 from Oracle Data Warehouse tables
select col4 from Oracle Data Warehouse tables
Hope that you get what am I trying to say. :(
Thanks,
Edited by: OBIEE/BIP Forumer on Oct 29, 2012 1:27 AM
Edited by: OBIEE/BIP Forumer on Oct 29, 2012 1:27 AM

Hi Maqsoon,
Sorry for the confusion, in my Analysis report, I have a report where it generates 2 physical SQL in one Database, also I have a report where it uses 2 Database which also generates 2 physical SQL.
Below is the SQl generated in my Analysis report using 1 Database
select count(distinct case when T68197.OPTY_WID > 0 then concat(T67058.INTEGRATION_ID, cast(T67058.DATASOURCE_NUM_ID as CHARACTER ( 30 ) )) end ) as c1,
T67058.OPTY_O_REVN as c2,
T67365.CUST_VALUE_NAME as c3,
T157680.NAME as c4,
T157680.INTEGRATION_ID as c5
from
W_OPTY_D T67058 /* Dim_W_OPTY_D */ ,
W_REVN_F T68197 /* Fact_W_REVN_F */ ,
W_PARTY_D T157680,
W_PARTY_ORG_D T67365
where ( T67058.ROW_WID = T68197.OPTY_WID and T67365.ROW_WID = T157680.PARTY_ORG_WID and T68197.PR_CUSTOMER_WID = T157680.ROW_WID )
group by T67058.OPTY_O_REVN, T67365.CUST_VALUE_NAME, T157680.NAME, T157680.INTEGRATION_ID
order by c5, c2
[2012-10-30T11:44:39.000+00:00] [OracleBIServerComponent] [TRACE:2] [USER-18] [] [ecid: 352c537d7893ee94:-5718ddd6:13aaccb7670:-8000-0000000000005c50] [tid: f650d700] [requestid: 45ca0005] [sessionid: 45ca0000] [username: joshua.l.manego.iii] -------------------- Sending query to database named Oracle Data Warehouse (id: <<1201371>>), connection pool named Oracle Data Warehouse Connection Pool, logical request hash edb0c7c0, physical request hash 87553d2a: [[
select sum(D1.c1) over (partition by D1.c4, D1.c2) as c1,
D1.c2 as c2,
D1.c3 as c3,
D1.c4 as c4,
sum(D1.c5) over (partition by D1.c6, D1.c4, D1.c2) as c5,
D1.c6 as c6
from
(select count(T84444.ORDER_WID) as c1,
T67365.CUST_VALUE_NAME as c2,
T157680.NAME as c3,
T157680.INTEGRATION_ID as c4,
sum(T84444.ORDER_NRC) as c5,
T67058.OPTY_O_REVN as c6
from
W_OPTY_D T67058 /* Dim_W_OPTY_D */ ,
W_PARTY_ORG_D T67365,
W_ORDER_F T84444 /* Fact_W_ORDER_F */ ,
W_PARTY_D T157680
where ( T67058.ROW_WID = T84444.OPTY_WID and T67365.ROW_WID = T157680.PARTY_ORG_WID and T84444.CUSTOMER_WID = T157680.ROW_WID )
group by T67058.OPTY_O_REVN, T67365.CUST_VALUE_NAME, T157680.NAME, T157680.INTEGRATION_ID
) D1
order by c4, c6
Below is the physical SQL that uses 2 Database
select T68071.QUOTE_NUM as c1,
T116081.CURRENT_BASE_POSTN as c2,
T66755.PER_NAME_MONTH as c3,
T68071.STATUS_I as c4,
T68071.QUOTE_TYPE_I as c5,
T68071.SUB_TYPE_I as c6,
T84523.ROW_WID as c7
from
W_POSITION_D T74722 /* Dim_W_POSITION_D */ ,
W_QUOTE_D T68071 /* Dim_W_QUOTE_D */ ,
W_QUOTE_F T84523 /* Fact_W_QUOTE_F */ ,
W_DAY_D T66755 /* Dim_W_DAY_D_Common */ ,
W_POSITION_DH T116081 /* Dim_W_POSITION_DH_Position_Hierarchy */
where ( T66755.ROW_WID = T84523.OPEN_DT_WID and T68071.ROW_WID = T84523.QUOTE_WID and T74722.ROW_WID = T84523.PR_EMP_POS_WID and T74722.ROW_WID = T116081.POSITION_WID and T84523.PR_EMP_POSTN_DH_WID = T116081.ROW_WID )
order by c7
[2012-10-30T11:51:42.000+00:00] [OracleBIServerComponent] [TRACE:2] [USER-18] [] [ecid: 352c537d7893ee94:-5718ddd6:13aaccb7670:-8000-0000000000005cb8] [tid: f61fc700] [requestid: 45ca0007] [sessionid: 45ca0000] [username: joshua.l.manego.iii] -------------------- Sending query to database named OLAP_OBIEE (id: <<1204144>>), connection pool named Connection Pool, logical request hash c180fd3b, physical request hash a2e8b0d6: [[
select T315910.NIVEL_APPROVACAO as c1,
T315910.ALCADA_DESCONTO as c2,
T315910.ROW_WID as c3
from
W_QUOTEITEM_F T315910
order by c3
Based on what you said, so it is impossible to merge the physical SQL if we use 2 Database right?
Your effort in answering to my question is much appreciated, Thank you.

Multiple Physical SQL for one report

Hi,
Can someone please explain me why i am seeing multiple physical Queries generated for a single report.
Please find below the physical sql.
select sum(T314772.MONTHLY_BUDGET_AMT) as c1,
T157680.NAME as c2
from
W_PARTY_D T157680,
XXKC_CUSTSITE_SHIPTO_BUDGET_F T314772 / Fact_XXKC_CUSTSITE_SHIPTO_BUDGET_F */*
where ( T157680.ROW_WID = T314772.CUSTOMER_WID )
group by T157680.NAME
and
select sum(case when T97600.W_XACT_TYPE_CODE = 'Chargeback' then T93664.NET_AMT T93664.GLOBAL1_EXCHANGE_RATE end ) as c1,*
sum(case when T97600.W_XACT_TYPE_CODE = 'Credit Memo' then T93664.NET_AMT T93664.GLOBAL1_EXCHANGE_RATE end ) as c2,*
sum(case when T97600.W_XACT_TYPE_CODE = 'Debit Memo' then T93664.NET_AMT T93664.GLOBAL1_EXCHANGE_RATE end ) as c3,*
sum(case when T97600.W_XACT_TYPE_CODE = 'Standard Invoice' then T93664.NET_AMT T93664.GLOBAL1_EXCHANGE_RATE when T97600.W_XACT_TYPE_CODE = 'Invoice Cancellation' then T93664.NET_AMT * -1 * T93664.GLOBAL1_EXCHANGE_RATE end ) as c4,*
T157680.NAME as c5
from
W_PARTY_D T157680,
W_SALES_INVOICE_LINE_F T93664 / Fact_W_SALES_INVOICE_LINE_F */ ,*
W_XACT_TYPE_D T97600 / Dim_W_XACT_TYPE_D_Sales_Ivclns */*
where ( T93664.CUSTOMER_WID = T157680.ROW_WID and T93664.XACT_TYPE_WID = T97600.ROW_WID and T93664.DELETE_FLG = 'N' )
group by T157680.NAME
please let me know the reason and how to control this kind off behavior

Combined request is like, within a report you can create multiple requests. You can either use it in case of combining different subject area or within the same subject area and in same report when different filters apply.
For example
Fire Marine Motor
State No. Amt. No. Amt. No. Amt.
Andra Pradesh 10 |20000 11 |100000 20 |200000
TamilNadu 11 |40000 10 |120000 20 |200000
The first request is for Andra, so we will apply the filter as 'state is equal to in 'andra pradesh''. We specify filter(No using Product_code in 'Fire') in the column formula. Then there is an option as 'combine' by which u create another request and now the filter is 'state is equal to in 'Tamil Nadu''. So when you execute the report, it will generate you two different queries.
Regards,
Anitha.B

OBIEE 11g Usage Tracking - Physical SQL

Hi All,
The Query Text column gives me only the logical SQL. The Log Level is set at 2. How can I get the physical SQL via Usage tracking?
Thanks for your time and help.

Hi,
Good for you.
Maybe you can post the solution and how you solved your issue to help other users having the same problem and then close the thread (currently it's still This question is Not Answered.)

Physical SQL Query of the BI Publisher Report

Hi,
Where can we see the Physical SQL Query of the BI Publisher Report with OBIEE as a Data Source? As you people might be knowing, when we chose OBIEE - a logical SQL will/need to be placed.
Thanks,
Vency

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?

Row Number() over partition by Order by in OBIEE Physical SQL

Hi ,
I created a OBIEE report in Dev using Answers. When I move the same report to Live, the count of rows was more in Live environment when compared to Dev.
The objects count is same in both Dev and Production.
WheniI verified the log file, I found that the Physical SQL in test has
ROW_NUMBER ()
OVER
PARTITION BY c1, c4, c5 order by c1,c4,c5) whereas the physical SQL in Production has
ROW_NUMBER ()
OVER
PARTITION BY c1, c4, c5, c8,c9 order by c1,c4,c5,c8,c9)
How this Partiton is done in OBIEE. I have just copied the report from catalog and moved to production.There is no changes in report.
Whether there are any settings to control it? HOw OBIEE does this Row Number() Partiton ? How can get this similiar to Test?
Please help!
Thanks
Johnny

Hi Saichand,
The links were helpful. But i am not getting how it is working in test and not in live.
I found one difference while deploying . The column names of the object both in Test and Production had spaces.For E.g: Full Name
When this column Full Name is pulled to the repsository in test , it automatically put double quotes for the column names in the physical sql when it hits the database.
But, In production , when I pulled the column the report gave error as Invalid Identifier since OBIEE generated column name as Full Name without double quotes.
Then I changed the column in Phyiscal Layer repository by having double Quotes for all columns. Afte that report worked fine.
Whether this has caused any issue in Row Partition.
Is there any setting to have column name in Double Quotes ?
Thanks,
Johnny

Can we change physical SQL generated by BI Server?

Hello gurus:
I have a doubt. How can we change the physical SQL generated by OBIEE?
is there any way we can modify the SQL Cost?
Let me know.
Thanks.
Vinay R.

So If I have a View and a physical table, so View will have lower cost compared to Table?
Can you explain a bit more about this?There is absolutely no way we can estimate the cost of a view or a table we don't know. There are too many variables so your question is too wide and unprecise. Generally speaking views that select from only one table do not add any extra cost to the execution plan, Oracle will convert them to the underlaying table. Having said the usual reason to have a view is to join different tables and apply some data filtering conditions so it will depend a lot on what kind of query you are running.

Physical SQL

I have another question for the experts.
I have tried accessing the SQL of a query through the presentation layer by going through Manage sessions....set variable loglevel 2 thru 5 and still keep getting the query in XML. How can I access the physical SQL?
OBIEE
11G

You can find the log in nqquery.log under <BI Instance>\instance1\diagnostics\logs\OracleBIServerComponent\coreapplication_obis1
OR else viewing the log in Manage my session Administration

Physical SQL contains apostrophe

Similar Messages

Maybe you are looking for