Query SQL datastore with XML where clause source

Hope I am in the right place. New to Bus Obj Data Services Designer....I have cerated xml schemas, added it to the page as an xml source in. Mapped a test xml file and all is well there. I have added a query that grabs the xml.
I need to then query the MS SQL datastore ans use the data form the xml query as the where clause. How is this done? Or do I put a query on the datastore for all the data in a table then do anotehr query filtering one with the other? seems like that would be rather heavy and low performance. The results will then be sent back out as xml (schema and test file already set up as an xml out)
Thanks!

Thanks for the tips.
I'm trying to implement this option, using your ViewDefHelper.
I´m running into a problem though. After I create my dynamic View Object using a ViewDef, I need to create some view links.
So I get the AttributeDefs of the columns (source, and destination) from the method findAttributeDef (which is the whole purpose of performance in my post). This method is returning the correct Attribute Def, but when I create the view Link with the method createViewLinkBetweenViewObjects(java.lang.String vlName,
java.lang.String accessorName,
ViewObject master,
AttributeDef[] srcAttrs,
ViewObject detail,
AttributeDef[] destAttrs,
java.lang.String assocClause)
My destination query is generating the where clause as:
null = ?
Any Ideas what I'm doing wrong ?
Thanks again.
John.

Similar Messages

SQL query in SQL_REDO Logminor showing where clause with ROWID

SQL query in SQL_REDO Logminor showing where clause with ROWID. I dont wanted to use rowid but wanted to use actual value.
OPERATION SQL_REDO SQL_UNDO
DELETE delete from "OE"."ORDERS" insert into "OE"."ORDERS"
where "ORDER_ID" = '2413' ("ORDER_ID","ORDER_MODE",
and "ORDER_MODE" = 'direct' "CUSTOMER_ID","ORDER_STATUS",
and "CUSTOMER_ID" = '101' "ORDER_TOTAL","SALES_REP_ID",
and "ORDER_STATUS" = '5' "PROMOTION_ID")
and "ORDER_TOTAL" = '48552' values ('2413','direct','101',
and "SALES_REP_ID" = '161' '5','48552','161',NULL);
and "PROMOTION_ID" IS NULL
and ROWID = 'AAAHTCAABAAAZAPAAN';
DELETE delete from "OE"."ORDERS" insert into "OE"."ORDERS"
where "ORDER_ID" = '2430' ("ORDER_ID","ORDER_MODE",
and "ORDER_MODE" = 'direct' "CUSTOMER_ID","ORDER_STATUS",
and "CUSTOMER_ID" = '101' "ORDER_TOTAL","SALES_REP_ID",
and "ORDER_STATUS" = '8' "PROMOTION_ID")
and "ORDER_TOTAL" = '29669.9' values('2430','direct','101',
and "SALES_REP_ID" = '159' '8','29669.9','159',NULL);
and "PROMOTION_ID" IS NULL
and ROWID = 'AAAHTCAABAAAZAPAAe';
Please let me know solution/document which will convert SQL redo rowid value with actual value.
Thanks,

Please enclose your output within tag so that people here can read it easily and help you. Also the reason that why you want to remove rowid?
Salman
Edited by: Salman Qureshi on Mar 20, 2013 3:53 PM

How to create a procedure to output REF CURSOR with any WHERE clause?

I have an requirement like this: I have huge query which need to reuse in my code more than 10 times. This SQL has about 50 lines. Thing is for those 10 odd times sometimes the WHERE clause changes (columns are the same). So I cannot create a view since SQL is not static.
I thought of writing a procedure with a WHERE_CLAUSE input para. I output a sys refcursor by adding the where clause. But I can't do it since you cannot add a where clause like that.
i.e.
PROCEDURE dynamyic_query (p_where_clause IN VARCHAR2, p_out_query OUT SYS_REFCURSOR ) IS
BEGIN
OPEN p_out_query FOR SELECT ......... FROM table WHERE || ' ' || p_where_clause;
END;The above gives error.
How to handle a situation like this???? Any help would be greatly appreciated.

I tried this method:
I created a table tab_test which has these records:
TNAME                          TABTYPE    CLUSTERID
ABS_V4_P_ERROR_MESSAGES        TABLE
ABS_V4_P_ORG_PARAM             TABLE
ABS_V4_P_PARAMETER             TABLE
ABS_V4_P_SYS_PARAM             TABLE
ACCINTERFACE_PARAMETERS        TABLE
ACCOUNTS                       TABLE
ACCOUNT_EXTRACT_PERIODS        TABLE
ACCOUNT_EXTRACT_PERIODS#       TABLE
ACCOUNT_EXTRACT_PERIODS_1      TABLE                                                                                                                                                                                   Now I create this proc:
PROCEDURE FORMS_TEXT_DYN_SQL_TEST(p_where_cluase IN VARCHAR2, p_out_cursor OUT SYS_REFCURSOR) IS
v_stmt VARCHAR2(1000);
BEGIN
v_stmt := 'SELECT tname FROM tab_test WHERE tname LIKE ''%ABS_V4%'' AND tabtype = :x';
OPEN p_out_cursor FOR v_stmt using p_where_cluase;
END;I create this code block and run it:
declare
v_tname varchar2(200);
out_cursor sys_refcursor;
begin
forms_text_dyn_sql_test('TABLE', out_cursor );
LOOP
    fetch out_cursor INTO v_tname;
    exit when out_cursor%NOTFOUND;
    DBMS_OUTPUT.PUT_LINE(v_tname);
END LOOP;
end;
/I get correct output:
ABS_V4_P_ERROR_MESSAGES
ABS_V4_P_ORG_PARAM
ABS_V4_P_PARAMETER
ABS_V4_P_SYS_PARAMHowever, when I change the proc like this:
PROCEDURE FORMS_TEXT_DYN_SQL_TEST(p_where_cluase IN VARCHAR2, p_out_cursor OUT SYS_REFCURSOR) IS
v_stmt VARCHAR2(1000);
BEGIN
v_stmt := 'SELECT tname FROM tab_test WHERE tname LIKE ''%ABS_V4%'' AND :y';
OPEN p_out_cursor FOR v_stmt using p_where_cluase;
END;And run this code block:
declare
v_tname varchar2(200);
out_cursor sys_refcursor;
begin
forms_text_dyn_sql_test(' 1 = 1 ', out_cursor );
LOOP
    fetch out_cursor INTO v_tname;
    exit when out_cursor%NOTFOUND;
    DBMS_OUTPUT.PUT_LINE(v_tname);
END LOOP;
end;
/I get error:
[1]: (Error): ORA-00920: invalid relational operator ORA-06512: at "ABS.FORMS_TEXT_DYN_SQL_TEST", line 6 ORA-06512: at line 5Looks like you can only put column_name = :z, column_name = :y type values. You cannot it seems replace it with any WHERE CLAUSE????

"create columns with a where clause" in BMM

Hi All,
I have a question about OBI EE Meta data layer.
We have OBIEE sitting on a Data Warehouse with a star schema.
Our Fact table holds the following fields...
EmployeeID
CompanyID
Measure ID
Measure Name
MEASURE
This is what we have in the physical layer, BMM layer and the presentation layer but I want to be able to "create columns with a where clause"
So my fact table in the presentation layer would look like this
Amount Sold
Unit Cost
Company Amount
I thought I could just create a logical column with
Amount Sold = Measure
where Measure Name = "Amount Sold"
But I can't seem to find any to do that.
Any ideas?
Thanks

Or you simply map your measure in the Logical Table source as something like :
CASE WHEN MEASURE_NAME = 'Amount Sold' THEN MEASURE ELSE 0 END.
You need to decide if you want the where clause adding in the Logical table source (be careful you will need a seperate LTS for each measure, this will mean more than one SQL being fired when you have more than one measure in the report).
Or you go with this case method on each measure, be able to have all the measures mapped in 1 LTS, include all those in the report and they will be retrieved by one SQL block.

WHERE clause sources

Hi,
it is said that there are four WHERE clause sources:
1. WHERE clause block property (on datablock or programatically defined)
2. ONETIME_WHERE clause block property (on datablock)
3. Example Record
4. Query/Where dialog box
I dont have any idea where I can find/ where the process takes place for items 3&4? Please enlighten me. Thanks

You can update some data, and you can see lots of data you shouldn't. Eg in a form based on emp and with a restriction in the block's where clause property, you can bring up the Query/Where window and type garbage. Then the "Help > Display Error" window shows something like this
SELECT ROWID,EMPNO,ENAME,JOB,MGR,HIREDATE,SAL,COMM,DEPTNO
FROM scott.emp WHERE deptno = user_dept_no() and (garbage!)The proper Where Clause will only let you see data from your own department, but if you put
1=2) union select ROWID,EMPNO,ENAME,JOB,MGR,HIREDATE,SAL,COMM,DEPTNO
FROM scott.emp WHERE (1=1in the Query/Where window, you can see and update the data from all departments.
And if you try
1=2) union select null, null, table_name, null,null, null,null, null,null
from all_tables WHERE (1=1then you're on your way towards getting access to lots of data which you shouldn't. A form with a large text field would be better for this sort of hacking.
Trying to update through a function gets this:
ORA-14551: cannot perform a DML operation inside a queryWith well defined synonyms, privileges and FGAC/VPD it should be safe to keep this enabled. Putting something after the colons means you don't need to know the column names.
It's handy functionality but I've never been keen on the user-unfriendliness of this window. I'd rather see a dialog showing all the Prompt names and next to each would be a list containing 'Between, <=, != etc', with a free text field after that (or a date picker for date fields, something else for checkboxes, multi-select lists for the list fields, etc). Another for the wish list!

REPORT with dynamic WHERE CLAUSE (run RDF or REP) ?

Hi:
When running a REPORT (myreport.rep) with dynamic where clause using a lexical parameter, I got this error:
REP-1439: Cannot compile .REP or .PLX file as it does not have source
If i run the report specifiying RDF extension (myreport.rdf) the report run successfully! Is this normal ?
If I specify RDF extension will Report Server COMPILE the report everytime I execute it ?
When using dynamic WHERE CLAUSE I will have to run RDF files instead of REP ?
I'm running Reports 9i under Linux, with IDS under Windows.
Waiting Help
Joao Oliveira

It sounds like you are building the .rep files on one platform (windows) and running them on another (linux). The reason that the .rdf file continues to work is that Reports recompiles the PL/SQL within the report when you move from one platform to another or change schemas. .rep files can't be re-compiled in this way so you need to ensure they are compiled successfully when converting them.
You need to convert from .rdf to .rep on the platform that you are intending to run on. Try running rwconverter on the linux platform with "compile_all=yes" to produce the .rep file and running that .rep file.

Using SAMPLE with a WHERE clause

(Oracle 9iR2)
I am using the SAMPLE keyword in a SELECT statement with a WHERE clause. Is the sample extracted before or after applying the WHERE clause?
For example, if I have the statement:
SELECT emp_id FROM employees SAMPLE(10)
WHERE salary > 50000;
Does the database first extract a 10% sample of all the rows and then apply the salary filter on the sample (meaning it's possible that no rows are returned even though there are rows with salary > 50000)? Or does it return a 10% sample of the rows that meet the filter condition (meaning rows will always be returned as long as there are rows with salary > 50000)?

The sample is extracted before the where clause:
SQL> drop table sample_test;
Table dropped.
SQL> create table sample_test (id number, salary number);
Table created.
SQL>
SQL> begin
2 for i in 1..99 loop
3 insert into sample_test values (i, 100);
4 end loop;
5
6 insert into sample_test values (100, 1000);
7 end;
8 /
PL/SQL procedure successfully completed.
SQL>
SQL> commit;
Commit complete.
SQL>
SQL> select * from sample_test sample(5)
2 where salary > 100;
no rows selected

Insert Row is visible in other VO with excluded where-clause

Hi,
i found something that makes me a little bit confusing about ADF BC...
TestCase:
Env:
JDev 10.1.2
HR Schema / Table "regions"
All Objects created ´by ADF BC Wizards
- ViewObject A and ViewObject B based on Entity "Regions"
- ViewObject A with WHERE-CLAUSE region_id=10 at DesignTime
- ViewObject B with NO WHERE-CLAUSE (select * from regions)
JUnitTest:
public void testInsertRow()
ViewObject viewA = fixture1.getApplicationModule().findViewObject("RegionsAView");
ViewObject viewB = fixture1.getApplicationModule().findViewObject("RegionsBView");
System.out.println("ViewA:"+viewA.getRowCount()); //-->0
assertTrue("Must 0 ! region_id = 10",viewA.getRowCount() == 0);
Row row = viewB.createRow();
row.setAttribute("RegionId",new Number(99));
row.setAttribute("RegionName","NRW");
viewB.insertRow(row);
System.out.println("ViewB:"+viewB.getRowCount()); // -> 5
System.out.println("ViewA:"+viewA.getRowCount()); // -> 1
//this assert failt !
assertTrue("Must 0 ! where clause is region_id = 10 and insert region_id was 99 ",viewA.getRowCount() == 0);
Is this a bug or feature ? Can anybody explain that behavior ? thx :)
uli

See this article on my blog for an explanation and a code sample for how to gain more fine-grained control over this View Link Consistency feature...
http://radio.weblogs.com/0118231/2004/02/27.html#a242

SQL query optimization by changinf the WHERE clause

Hi all,
I need to know about the SQL query performance improvement by changing the WHERE clause. Consider a query :
select * from student where country ='India' and age = 20
Say, country = 'India' filters 100000 records and age = 20 filters 2000 records if given one by one. Now can anyone tell if the performance of the query can be changed by changing the query like this :
select * from student where age = 20 and country ='India'
as first where clause will give 2000 results and next filter will be applicable on only 2000 rows. While in the former query first where clause would give 100000 rows and seconde filter, hence, would be applicable on 100000 rows???
Kindly explain.
Thanks in advance.
Abhideep

in general the order of the where condition should not be important. However there are a few exeptions where sometimes it might play a role. Sometimes this is called order of filter conditions. Among others it depends on RBO or CBO used, Oracle Version, Indexes on the columns, statistic information on the table and the columns, CPU statistics in place etc.
If you want to make this query fast and you know that the age column has much better selectivity then you can simply put an index on the age column. An index on the country column is probably not useful at all, since to little different values are in this column. If you are already in 11g I would suggest to use a composite index on both columns with the more selective in first position.
Edited by: Sven W. on Nov 17, 2008 2:23 PM
Edited by: Sven W. on Nov 17, 2008 2:24 PM

Binding parameters to dynamic VO with PL/SQL API call with no where clause

Hi all,
I am required to change exisiting queries to queries with "bind" parameters. Some of our VOs are dynamic and with PL/SQL api calls like below:
String stmtStr = "selectXXX_API_UTILS.chk_urg_since_last_prg("
+ projectId + "," + PPCId + ",'XYZ_TASKS'," + taskId+ ")"
+" from dual ";
ViewObject tmpVO = transaction.createViewObjectFromQueryStmt(stmtStr);
In this regard, I am unsure how to bind the PPCId and taskId parameters to the VO. setWhereClauseParams() would not work here as there is now where clause.
Thanks in advance,
Srini

In case of preparedStatement, we mention bind parameters to be passed using "?". Then we pass paramters sequencially.
But in the your case following is enough:
int projectId = 100 ; (hardcoding values for example)
int taskId = 500 ;
String stmtStr = "selectXXX_API_UTILS.chk_urg_since_last_prg("
+ projectId + "," + PPCId + ",'XYZ_TASKS'," + taskId+ ")"
+" from dual ";
-Anand

Improve the performance in stored procedure using sql server 2008 - esp where clause in very big table - Urgent

Hi,
I am looking for inputs in tuning stored procedure using sql server 2008. l am new to performance tuning in sql,plsql and oracle. currently facing issue in stored procedure - need to increase the performance by code optmization/filtering the records using where clause in larger table., the requirement is Stored procedure generate Audit Report which is accessed by approx. 10 Admin Users typically 2-3 times a day by each Admin users.
It has got CTE ( common table expression ) which is referred 2 time within SP. This CTE is very big and fetches records from several tables without where clause. This causes several records to be fetched from DB and then needed processing. This stored procedure is running in pre prod server which has 6gb of memory and built on virtual server and the same proc ran good in prod server which has 64gb of ram with physical server (40sec). and the execution time in pre prod is 1min 9seconds which needs to be reduced upto 10secs or so will be the solution. and also the exec time differs from time to time. sometimes it is 50sec and sometimes 1min 9seconds..
Pl provide what is the best option/practise to use where clause to filter the records and tool to be used to tune the procedure like execution plan, sql profiler?? I am using toad for sqlserver 5.7. Here I see execution plan tab available while running the SP. but when i run it throws an error. Pl help and provide inputs.
Thanks,
Viji

You've asked a SQL Server question in an Oracle forum. I'm expecting that this will get locked momentarily when a moderator drops by.
Microsoft has its own forums for SQL Server, you'll have more luck over there. When you do go there, however, you'll almost certainly get more help if you can pare down the problem (or at least better explain what your code is doing). Very few people want to read hundreds of lines of code, guess what's it's supposed to do, guess what is slow, and then guess at how to improve things. Posting query plans, the results of profiling, cutting out any code that is unnecessary to the performance problem, etc. will get you much better answers.
Justin

Performance with unspecific where clause

Hi gurus,
at the moment I do have a sql statement on a view with an unspecific where clause like
select from <view> where <textfield> like %whatIsearch%
The text field is not in the key fields which are used to create the view. An index on <textfield> does not help, because the where clause starts with a %.
Other databases like Oracle do finish the statement within seconds, maxdb needs minutes.
I there a possibility to speedup the statement in MaxDB? (Besides telling the user to use better qualified statments.)
Why is Oracle that fast?
Thanks for you help.
Best regards
Christian G

> Other databases like Oracle do finish the statement within seconds, maxdb needs minutes.
> I there a possibility to speedup the statement in MaxDB? (Besides telling the user to use better qualified statments.)
> Why is Oracle that fast?
Hi Christian,
In that case Oracle can take advantage from beeing able to brute-force read many blocks at once (aka multiblock read).
When we assume that there is an index on the oracle database available, then Oracle will likely decide to read all blocks of that index into the cache and look for matches then. It's called Fast Full Scan.
It's not a very efficient method to address specific rows, but for this requirement it works well.
Anyhow, you should be aware that this way of evaluating rows does not scale very well - in fact it get's more expensive with every block the index grows.
MaxDB cannot easily read all blocks in a row, due to the fact that the pages are mixed over all data volumes. This way of storing data eliminates the need for reorganisations and evens out I/O traffic, but it comes for the price of beeing less performant when people use such unefficient predicates.
Because of this and the way who indexes work in MaxDB (primary keys instead of rowids), MaxDB does only consider an index access for like conditions that start with a '%' when the query can be answered by only accessing the index (index only access).
What you may try out to improve the situation is to activate the experimental read-ahead or prefetch feature, which is currently available in MaxDB 7.6. only (not in 7.5 or in 7.7).
By setting READAHEAD_TABLE_THRESHOLD to a value >0, say 128, MaxDB can choose to
perform table scans (no index scans!) in parallel with multiple server tasks for all table scans that are expected to pass the threshold (unit here is pages as visible in the execution plan of your statement).
That way the usertask running the query can work on checking the data in the pages, while the server task load the pages into the cache.
Another approach would be to have the DB Cache big enough so that most of the table would be found in the cache.
regards,
Lars

Query designer removing parts of where clause in VS 2012

I'm new to reporting services and I'm finding the query designer very frustrating. First off, I have read here and
am having a problem where the tool automatically wipes out parameters I have changed/added in the query designer. I read this 5 years ago, yet it seems that this problem still exists. I've tried changing the XML as suggested by some with mixed
results. Now I am having a problem when I changed the WHERE clause it keeps disappearing if I try and make any other change. Does anyone have advice on working with this tool? Should one keep a running copy of the query and keep pasting it
back in whenever a change is needed? Is this behavior not expected? Is anything different with SSRS 2014?
Thanks

Hi billywinter,
According to your description, parameters are wiping out automatically when you change something in query designer.
In Reporting Service, if we use where clause to add parameters in query designer, Define Query Parameters will pop-up when running the query. Please refer to screenshot below:
Regarding the issue, we couldn’t understand it clearly, and we would like to confirm something from you below:
1. Does parameters disappear in your query? Or when you preview the report, the selected box of parameters doesn’t display?
2. How about the query in query designer when parameters disappear?
3. What’s the modification have you performed for where clause? And what’s the result after this modification?
4. What the query type you are using, MDX query, stored procedure or another query type?
Please provide more information about the issue then we can understand the issue clearly. If possible, please provide some screenshots about the query in query designer, and the results of parameters before and after changing where clause.
In addition, we have found a feedback which descripts an issue about overwriting parameter in MDX query designer, and this issue is resolved by design. Is this issue same as yours? Please refer to this feedback:
MDX Query Designer Overwrites Parameter Queries.
Best regards,
Qiuyun Yu

PL/SQL Evaluation problem of where clause in case of NUMBER column type

I found the following problem in Oracle® Database 2 Day Developer's Guide 11g Release 1 (11.1) B28843-04:
The sole parameter of function eval_frequency is employee_id IN employees.employee_id%TYPE.
An ORA-01422 exception occurs when the execution reaches the following select command
SELECT e.hire_date
INTO hire_date
FROM employees e
WHERE employee_id= e.employee_id;
A possible cause of the error is that the type of employee_id is NUMBER while the employees.employee_id is NUMBER(6,0) . The result of the selection is the same as there were no WHERE clause at all.
Everything worked fine, when I declared a temporary variable of NUMBER(6,0) for storing the actual parameter of function and used this variable in the where clause, but I consider this "solution" as being no solution.
It is pointless to use %TYPE parameter of a function for flexibility if I must degrade this flexibility by a fixed declaration of a temporary variable of the same type as the column in question.
What is wrong?
The Developer'Guide I used, the Oracle Sql Developer I used or the PL/SQL version ?

Hi,
Welcome to the forum!
user8949829 wrote:
A possible cause of the error is that the type of employee_id is NUMBER while the employees.employee_id is NUMBER(6,0) . The result of the selection is the same as there I don't think so. The variable employee_id is defined as having the exact same type as the eponymous column. Even if it didn't, I believe Oracle will always implicity convert between datatypes when possible, rounding if necessary. That may cause errors, but it isn't causing this error.
No, the error has nothing to do with the data type. It has to do with the ambiguity of employee_id: is it a column, or is it a variable?
The default is that it means the column name, so
WHERE   employee_id = e.employee_idis equivalent to saying
WHERE   e.employee_id = e.employee_idwhich isn't quite the same thing as not having a WHERE clause; rows with NULL employee_id would still be excluded, if there were any.
I think it's best not to use variable names that are the same as column names. You could call the variable v_employee_id, or, since it's an IN-argument, in_employee_id.
If you must use a variable that can be mistaken for a column, then qulaify it with the name of the procedure, like this:
WHERE   eval_frequency.employee_id = e.employee_id
Everything worked fine, when I declared a temporary variable of NUMBER(6,0) for storing the actual parameter of function That makes sens. You probably gave that variable a name that couldn't be mistaken for a column in the table.
Edited by: Frank Kulash on Jan 12, 2011 8:27 PM

Outer join with a WHERE clause

hi, this is driving me round the bend. I thought i was ok with sql joins and the like, but im really struggling on this one.
I have table A (for argument sake tblRegion) and table B (tblBranch). if i want to return everything i would do something like this:-
select * from tblRegion join tblBranch on tblRegion.id=tblBranch.reg_id.
If i wanted to return all regions even if they do have a branch associated i would do something like this:-
select * from tblRegion left outer join tblBranch on tblRegion.id=tblBranch.reg_id.
My problem is, I want to return all Regions and use a WHERE clause to narrow the Branch results.
I've tried something like this but it doesnt work
select * from tblRegion left outer join tblBranch on tblRegion.id=tblBranch.reg_id WHERE branch.name like 'LONDON%'
Is there anyway i can return all branches where name is like LONDON, and STILL return all Region if there is no data for that Region?
Do i need to use a nested select statement maybe?
Many thanks in anticipation somebody will save me from my current madness. David

Check this link. It explains the most common problem/coding error while using outer join.
http://www.orafaq.com/node/855
Effectively in your case you need the following condition in your where clause
where nvl(branch.name,'LONDON') like 'LONDON%'
Hope that helps.
Regards
Raj

Query SQL datastore with XML where clause source

Similar Messages

Maybe you are looking for