A bug? BC4J ViewObject where clause change doesn't affect view contents

Hi!
I've found the following interesting behaviour (maybe a bug?) of BC4J ViewObject caching:
1) make a viewobject with where clause and 1 parameter in it.
2) set parameter binding to some value
3) execute query
4) then change viewobject's where clause, but leave parameter binding intact
5) execute query again
6) view object contents haven't changed!
actually, changing where clause text should make view object requery data from the database instead of using cached rows...
If to add a call to viewobject.clearCache() before second viewobject.executeQuery(), then everything works fine and view object's contents are changed.
Does anybody have any ideas about this? Or is this a some kind of a feature, or it is already fixed in a newer version of JDev?
Thnx!
PS. JDeveloper version 9.0.3.4 (build 1247).

delete message

Similar Messages

Index usage in depending on where clause changes.

Hello Friends,
I need your help for one issue.
I have one query , which is using two table Say T1 and T2, where C1 is common column using which both are joined.
C1 is primary key in T1, but no index available in T2 for C1. T1C2 is the column which we want to select.
(Note that Either of table can be a Master table)
Now see the query:
Select T1C2
From T1, T2
where T2.C1 = T1.C1
Here where clause may have other conditions and From clause may have others tables as per requirements.
I want to know that, if, I change the query like following to let my query use the available index of T1.C1.
Select T1C2
from T1, T2
where T1.C1 = T2.C1
Then, Will the query use the available index of T1. and Will i get better performance. Even a little improvement in performance may help me a lot as this kind of query is being used within a where loop (so it is going to be executed multiple times).
Please advise on this..
Regards,
Dipali..

Hi,
18:43:17 rel15_real_p>create table t1(c1 number primary key, c2 number);
Table created.
18:43:26 rel15_real_p>create table t2(c1 number, c2 number);
18:45:08 rel15_real_p>
18:45:09 rel15_real_p>begin
18:45:09   2 for i in 1..100
18:45:09   3 loop
18:45:09   4        insert into t1(c1,c2) values (i,i+100);
18:45:09   5 end loop;
18:45:09   6 commit;
18:45:09   7 end;
18:45:09   8 /
PL/SQL procedure successfully completed.
18:45:09 rel15_real_p>
18:45:09 rel15_real_p>
18:45:09 rel15_real_p>begin
18:45:09   2 for i in 1..100
18:45:09   3 loop
18:45:09   4        insert into t2(c1,c2) values (i,i+200);
18:45:09   5 end loop;
18:45:09   6 commit;
18:45:09   7 end;
18:45:09   8 /
18:45:23 rel15_real_p>select count(*) from t1;
COUNT(*)
       100
18:45:30 rel15_real_p>select count(*) from t2;
COUNT(*)
       100
18:45:49 rel15_real_p>select index_name,index_type from user_indexes where table
_name='T1';
INDEX_NAME                     INDEX_TYPE
SYS_C0013059                   NORMAL
18:48:21 rel15_real_p>set autotrace on
18:52:25 rel15_real_p>Select T1.C2
18:52:29   2 From T1, T2
18:52:29   3 where T2.C1 = T1.C1
18:52:29   4 /
        C2
       101
       102
       103
       104
       105
        C2
       200
100 rows selected.
Execution Plan
   0      SELECT STATEMENT Optimizer=ALL_ROWS (Cost=7 Card=100 Bytes=
          900)
   1    0   HASH JOIN (Cost=7 Card=100 Bytes=3900)
   2    1     TABLE ACCESS (FULL) OF 'T1' (TABLE) (Cost=3 Card=100 By
          es=2600)
   3    1     TABLE ACCESS (FULL) OF 'T2' (TABLE) (Cost=3 Card=100 By
          es=1300)
Statistics
          0 recursive calls
          0 db block gets
         21 consistent gets
          0 physical reads
          0 redo size
       1393 bytes sent via SQL*Net to client
        562 bytes received via SQL*Net from client
          8 SQL*Net roundtrips to/from client
          0 sorts (memory)
          0 sorts (disk)
        100 rows processed
18:52:31 rel15_real_p>analyze table t1 compute statistics;
Table analyzed.
18:55:35 rel15_real_p>analyze table t2 compute statistics;
18:55:38 rel15_real_p>set autotrace on
18:55:42 rel15_real_p>Select T1.C2
18:55:43   2 From T1, T2
18:55:45   3 where T2.C1 = T1.C1
18:55:46   4 /
        C2
       101
       102
       103
       104
       105
        C2
       200
100 rows selected.
Execution Plan
   0      SELECT STATEMENT Optimizer=ALL_ROWS (Cost=6 Card=100 Bytes=7
          00)
   1    0   MERGE JOIN (Cost=6 Card=100 Bytes=700)
   2    1     TABLE ACCESS (BY INDEX ROWID) OF 'T1' (TABLE) (Cost=2 Ca
          rd=100 Bytes=500)
   3    2       INDEX (FULL SCAN) OF 'SYS_C0013059' (INDEX (UNIQUE)) (
          Cost=1 Card=100)
   4    1     SORT (JOIN) (Cost=4 Card=100 Bytes=200)
   5    4       TABLE ACCESS (FULL) OF 'T2' (TABLE) (Cost=3 Card=100 B
          ytes=200)
Statistics
          1 recursive calls
          0 db block gets
         23 consistent gets
          0 physical reads
          0 redo size
       1393 bytes sent via SQL*Net to client
        562 bytes received via SQL*Net from client
          8 SQL*Net roundtrips to/from client
          1 sorts (memory)
          0 sorts (disk)
        100 rows processed
18:56:56 rel15_real_p>Select T1.C2
18:56:56   2 From T1, T2
18:56:56   3 where T1.C1 = T2.C1
18:56:58   4 /
        C2
       101
       102
       103
       104
       105
        C2
       200
100 rows selected.
Execution Plan
   0      SELECT STATEMENT Optimizer=ALL_ROWS (Cost=6 Card=100 Bytes=7
          00)
   1    0   MERGE JOIN (Cost=6 Card=100 Bytes=700)
   2    1     TABLE ACCESS (BY INDEX ROWID) OF 'T1' (TABLE) (Cost=2 Ca
          rd=100 Bytes=500)
   3    2       INDEX (FULL SCAN) OF 'SYS_C0013059' (INDEX (UNIQUE)) (
          Cost=1 Card=100)
   4    1     SORT (JOIN) (Cost=4 Card=100 Bytes=200)
   5    4       TABLE ACCESS (FULL) OF 'T2' (TABLE) (Cost=3 Card=100 B
          ytes=200)
Statistics
          1 recursive calls
          0 db block gets
         23 consistent gets
          0 physical reads
          0 redo size
       1393 bytes sent via SQL*Net to client
        562 bytes received via SQL*Net from client
          8 SQL*Net roundtrips to/from client
          1 sorts (memory)
          0 sorts (disk)
        100 rows processed- Pavan Kumar N

Dynamic where clause change

Hi,
I have code as below
Scenario1
FOR i in (Select .................... from table1 Where id in(select id from Sample_table where status='Submit'))
Loop
End loop;
Scenario2
FOR i in (Select .................... from table1 Where id in(select id from Sample_table where status='Saved'))
Loop
End loop;
Scenario3
FOR i in (Select .................... from table1 Where id in(select id from Sample_table where status='Inprogress'))
Loop
End loop;Query is same here but only chage is where clause
Total length of this query is exceeding varchar2 length. so i cant use variable to hold this query and append where clause dynamically.
Do we have any other method to change where clause dynamically?

>
We have around 200 columns to select from multiple tables...Here I gave sample code...
so its exceeding length
>
So 200 columns at 30 bytes per column name is only 6000 bytes. That means the rest of the query is using over 26000 bytes: 260 lines of query if each line was 100 bytes long.
You need to rethink what you are doing. So far your queries are too big, your row-by-row processing is a terrible way to process data and repeating that process multiple times just aggravates the performance even more.
I can't imagine there is ANY justification for doing things that way.
Even if you HAD to do things that way you couldn't exceed the CLOB length so why aren't you using a CLOB variable?
http://docs.oracle.com/cd/B28359_01/appdev.111/b28370/openfor_statement.htm
>
OPEN-FOR StatementThe OPEN-FOR statement executes the SELECT statement associated with a cursor variable. It allocates database resources to process the statement, identifies the result set (the rows that meet the conditions), and positions the cursor variable before the first row in the result set.
With the optional USING clause, the OPEN-FOR statement processes a dynamic SELECT statement that returns multiple rows: it associates a cursor variable with the SELECT statement, executes the statement, identifies the result set, positions the cursor before the first row in the result set, and zeroes the rows-processed count kept by %ROWCOUNT.
dynamic_string
A string literal, string variable, or string expression that represents any SQL statement. It must be of type CHAR, VARCHAR2, or CLOB.

Response time of query utterly upside down because of small where clause change

Hello,
I'm wondering why a small change on a where clause in a query has a dramatic impact on its response time.
Here is the query, with its plan and a few details:
select * from (
SELECT xyz_id, time_oper, ...
     FROM (SELECT
                    d.xyz_id xyz_id,
                    TO_CHAR (di.time_operation, 'DD/MM/YYYY') time_oper,
                    di.time_operation time_operation,
                    UPPER (d.delivery_name || ' ' || d.delivery_firstname) custname,
                    d.ticket_language ticket_language, d.payed,
                    dsum.delivery_mode delivery_mode,
                    d.station_delivery station_delivery,
                    d.total_price total_price, d.crm_cust_id custid,
                    d.bene_cust_id person_id, d.xyz_num, dpe.ers_pnr ers_pnr,
                    d.delivery_name,
                    TO_CHAR (dsum.first_travel_date, 'DD/MM/YYYY') first_traveldate,
                    d.crm_company custtype, UPPER (d.client_name) partyname,
                    getremark(d.xyz_num) remark,
                    d.client_app, di.work_unit, di.account_unit,
                    di.distrib_code,
                    UPPER (d.crm_name || ' ' || d.crm_firstname) crm_custname,
                   getspecialproduct(di.xyz_id) specialproduct
               FROM xyz d, xyz_info di, xyz_pnr_ers dpe, xyz_summary dsum
              WHERE d.cancel_state = 'N'
             -- AND d.payed = 'N'
                AND dsum.delivery_mode NOT IN ('DD')
                AND dsum.payment_method NOT IN ('AC', 'AG')
                AND d.xyz_blocked IS NULL
                AND di.xyz_id = d.xyz_id
                AND di.operation = 'CREATE'
                AND dpe.xyz_id(+) = d.xyz_id
                AND EXISTS (SELECT 1
                              FROM xyz_ticket dt
                             WHERE dt.xyz_id = d.xyz_id)
                AND dsum.xyz_id = di.xyz_id
           ORDER BY di.time_operation DESC)
    WHERE ROWNUM < 1002
) view
WHERE view.DISTRIB_CODE in ('NS') AND view.TIME_OPERATION > TO_DATE('20/5/2013', 'dd/MM/yyyy')
plan with "d.payed = 'N'" (no rows, *extremely* slow):
| Id | Operation                          | Name             | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                   |                  | 1001 | 4166K| 39354   (1)| 00:02:59 |
|* 1 | VIEW                              |                  | 1001 | 4166K| 39354   (1)| 00:02:59 |
|* 2 |   COUNT STOPKEY                    |                  |       |       |            |          |
|   3 |    VIEW                            |                  | 1001 | 4166K| 39354   (1)| 00:02:59 |
|   4 |     NESTED LOOPS OUTER             |                  | 1001 |   130K| 39354   (1)| 00:02:59 |
|   5 |      NESTED LOOPS SEMI             |                  |   970 |   111K| 36747   (1)| 00:02:47 |
|   6 |       NESTED LOOPS                 |                  |   970 |   104K| 34803   (1)| 00:02:39 |
|   7 |        NESTED LOOPS                |                  |   970 | 54320 | 32857   (1)| 00:02:30 |
|* 8 |         TABLE ACCESS BY INDEX ROWID| XYZ_INFO         |    19M|   704M| 28886   (1)| 00:02:12 |
|   9 |          INDEX FULL SCAN DESCENDING| DNIN_IDX_NI5     | 36967 |       |   296   (2)| 00:00:02 |
|* 10 |         TABLE ACCESS BY INDEX ROWID| XYZ_SUMMARY      |     1 |    19 |     2   (0)| 00:00:01 |
|* 11 |          INDEX UNIQUE SCAN         | SB11_DSMM_XYZ_UK |     1 |       |     1   (0)| 00:00:01 |
|* 12 |        TABLE ACCESS BY INDEX ROWID | XYZ              |     1 |    54 |     2   (0)| 00:00:01 |
|* 13 |         INDEX UNIQUE SCAN          | XYZ_PK           |     1 |       |     1   (0)| 00:00:01 |
|* 14 |       INDEX RANGE SCAN             | DNTI_NI1         |    32M|   249M|     2   (0)| 00:00:01 |
| 15 |      TABLE ACCESS BY INDEX ROWID   | XYZ_PNR_ERS      |     1 |    15 |     4   (0)| 00:00:01 |
|* 16 |       INDEX RANGE SCAN             | DNPE_XYZ         |     1 |       |     2   (0)| 00:00:01 |
Predicate Information (identified by operation id):
1 - filter("DISTRIB_CODE"='NS' AND "TIME_OPERATION">TO_DATE(' 2013-05-20', 'syyyy-mm-dd'))
2 - filter(ROWNUM<1002)
8 - filter("DI"."OPERATION"='CREATE')
10 - filter("DSUM"."DELIVERY_MODE"<>'DD' AND "DSUM"."PAYMENT_METHOD"<>'AC' AND "DSUM"."PAYMENT_METHOD"<>'AG')
11 - access("DSUM"."XYZ_ID"="DI"."XYZ_ID")
12 - filter("D"."PAYED"='N' AND "D"."XYZ_BLOCKED" IS NULL AND "D"."CANCEL_STATE"='N')
              ^^^^^^^^^^^^^^
13 - access("DI"."XYZ_ID"="D"."XYZ_ID")
14 - access("DT"."XYZ_ID"="D"."XYZ_ID")
16 - access("DPE"."XYZ_ID"(+)="D"."XYZ_ID")
plan with "d.payed = 'N'" (+/- 450 rows, less than two minutes):
| Id | Operation                          | Name             | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT                   |                  | 1001 | 4166K| 58604   (1)| 00:04:27 |
|* 1 | VIEW                              |                  | 1001 | 4166K| 58604   (1)| 00:04:27 |
|* 2 |   COUNT STOPKEY                    |                  |       |       |            |          |
|   3 |    VIEW                            |                  | 1002 | 4170K| 58604   (1)| 00:04:27 |
|   4 |     NESTED LOOPS OUTER             |                  | 1002 |   130K| 58604   (1)| 00:04:27 |
|   5 |      NESTED LOOPS SEMI             |                  | 1002 |   115K| 55911   (1)| 00:04:14 |
|   6 |       NESTED LOOPS                 |                  | 1476 |   158K| 52952   (1)| 00:04:01 |
|   7 |        NESTED LOOPS                |                  | 1476 | 82656 | 49992   (1)| 00:03:48 |
|* 8 |         TABLE ACCESS BY INDEX ROWID| XYZ_INFO         |    19M|   704M| 43948   (1)| 00:03:20 |
|   9 |          INDEX FULL SCAN DESCENDING| DNIN_IDX_NI5     | 56244 |       |   449   (1)| 00:00:03 |
|* 10 |         TABLE ACCESS BY INDEX ROWID| XYZ_SUMMARY      |     1 |    19 |     2   (0)| 00:00:01 |
|* 11 |          INDEX UNIQUE SCAN         | AAAA_DSMM_XYZ_UK |     1 |       |     1   (0)| 00:00:01 |
|* 12 |        TABLE ACCESS BY INDEX ROWID | XYZ              |     1 |    54 |     2   (0)| 00:00:01 |
|* 13 |         INDEX UNIQUE SCAN          | XYZ_PK           |     1 |       |     1   (0)| 00:00:01 |
|* 14 |       INDEX RANGE SCAN             | DNTI_NI1         |    22M|   168M|     2   (0)| 00:00:01 |
| 15 |      TABLE ACCESS BY INDEX ROWID   | XYZ_PNR_ERS      |     1 |    15 |     4   (0)| 00:00:01 |
|* 16 |       INDEX RANGE SCAN             | DNPE_XYZ         |     1 |       |     2   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   1 - filter("DISTRIB_CODE"='NS' AND "TIME_OPERATION">TO_DATE(' 2013-05-20', 'syyyy-mm-dd'))
   2 - filter(ROWNUM<1002)
   8 - filter("DI"."OPERATION"='CREATE')
10 - filter("DSUM"."DELIVERY_MODE"<>'DD' AND "DSUM"."PAYMENT_METHOD"<>'AC' AND "DSUM"."PAYMENT_METHOD"<>'AG')
11 - access("DSUM"."XYZ_ID"="DI"."XYZ_ID")
12 - filter("D"."XYZ_BLOCKED" IS NULL AND "D"."CANCEL_STATE"='N')
13 - access("DI"."XYZ_ID"="D"."XYZ_ID")
14 - access("DT"."XYZ_ID"="D"."XYZ_ID")
16 - access("DPE"."XYZ_ID"(+)="D"."XYZ_ID")
XYZ.PAYED values breakdown:
P   COUNT(1)
Y   12202716
N    9430207
tables nb of records:
TABLE_NAME           NUM_ROWS
XYZ                  21606776
XYZ_INFO            186301951
XYZ_PNR_ERS           9716471
XYZ_SUMMARY          21616607
Everything that comes inside the "select * from(...) view" parentheses is defined in a view. We've noticed that the line "AND d.payed = 'N'" (commented above) is the guilty clause: the query takes one or two seconds to return between 400 and 500 rows if this line is removed, when included in the query, the response time then switches to *hours* -sic !- but then the result set is empty (no rows returned). The plan is exactly the same whether this "d.payed = 'N'" is added or removed, I mean the nb of steps, access paths, join order etc., only the rows/bytes/cost columns values change, as you can see.
We've found no other way of solving this perf issue but by taking out this "d.payed = 'N'" condition and setting it outside the view along with view.DISTRIB_CODE and view.TIME_OPERATION.
But we would like to understand why such a small change on the XYZ.PAYED column turns everything upside down that much, and we'd like to be able to tell the optimizer to perform this check on payed = 'N' by itself in the end, just like we did, through the use of a hint if possible...
Anybody ever encountered such a behaviour before ? Do you have any advice regarding the use of a hint to reach the same response time as that we've got by setting the payed = N condition outside of the view definition ??
Thanks a lot in advance.
Regards,
Seb

I am really sorry I couldn't get back earlier to this forum...
Thanks to you all for your answers.
First I'd just like to correct a small mistake I made, when writing
"the query takes one or two seconds": I meant one or 2 *minutes*. Sorry.
> What table/columns are indexed by "DNTI_NI1"?
aaaa.dnti_ni1 is an index ON aaaa.xyz_ticket(xyz_id, ticket_status)
> And what are the indexes on xyz table?
Too many:
XYZ_ARCHIV_STATE_IND           ARCHIVE_STATE
XYZ_BENE_CUST_ID_IND           BENE_CUST_ID
XYZ_BENE_TTL_IND               BENE_TTL
XYZ_CANCEL_STATE_IND           CANCEL_STATE
XYZ_CLIENT_APP_NI              CLIENT_APP
XYZ_CRM_CUST_ID_IND            CRM_CUST_ID
XYZ_DELIVE_MODE_IND            DELIVERY_MODE
XYZ_DELIV_BLOCK_IND            DELIVERY_BLOCKED
XYZ_DELIV_STATE_IND            DELIVERY_STATE
XYZ_XYZ_BLOCKED                XYZ_BLOCKED
XYZ_FIRST_TRAVELDATE_IND       FIRST_TRAVELDATE
XYZ_MASTER_XYZ_IND             MASTER_XYZ_ID
XYZ_ORG_ID_NI                  ORG_ID
XYZ_PAYMT_STATE_IND            PAYMENT_STATE
XYZ_PK                         XYZ_ID
XYZ_TO_PO_IDX                  TO_PO
XYZ_UK                         XYZ_NUM
For ex. XYZ_CANCEL_STATE_IND on CANCEL_STATE seems superfluous to me, as the column may only contain Y or N (or be null)...
> Have you traced both cases to compare statistics? What differences did it reveal?
Yes but it only shows more of *everything* (more tables blocks accessed, the same
for indexes blocks, for almost all objects involved) for the slowest query !
Greping WAIT on the two trc files made for every statement and counting the
object IDs access show that the quicker query requires much less I/Os; the
slowest one overall needs much more blocks to be read (except for the indexes
DNSG_NI1 or DNPE_XYZ for example). Below I replaced obj# with the table/index
name, the first column is the figure showing how many times the object was
accessed in the 10053 file (I ctrl-C'ed my second execution ofr course, the
figures should be much higher !!):
[login.hostname] ? grep WAIT OM-quick.trc|...|sort|uniq -c
    335 XYZ_SUMMARY
20816 AAAA_DSMM_XYZ_UK (index on xyz_summary.xyz_id)
    192 XYZ
   4804 XYZ_INFO
    246 XYZ_SEGMENT
      6 XYZ_REMARKS
     63 XYZ_PNR_ERS
    719 XYZ_PK           (index on xyz.xyz_id)
   2182 DNIN_IDX_NI5     (index on xyz.xyz_id)
    877 DNSG_NI1         (index on xyz_segment.xyz_id, segment_status)
    980 DNTI_NI1         (index on xyz_ticket.xyz_id, ticket_status)
    850 DNPE_XYZ         (index on xyz_pnr_ers.xyz_id)
[login.hostname] ? grep WAIT OM-slow.trc|...|sort|uniq -c
   1733 XYZ_SUMMARY
38225 AAAA_DSMM_XYZ_UK (index on xyz_summary.xyz_id)
   4359 XYZ
12536 XYZ_INFO
     65 XYZ_SEGMENT
     17 XYZ_REMARKS
     20 XYZ_PNR_ERS
   8598 XYZ_PK
   7406 DNIN_IDX_NI5
     29 DNSG_NI1
   2475 DNTI_NI1
     27 DNPE_XYZ
The overwhelmingly dominant wait event is by far 'db file sequential read':
[login.hostname] ? grep WAIT OM-*elect.txt|cut -d"'" -f2|sort |uniq -c
     36 SQL*Net message from client
     38 SQL*Net message to client
107647 db file sequential read
      1 latch free
      1 latch: object queue header operation
      3 latch: session allocation
> It will be worth knowing the estimations...
It show the same plan with a higher cost when PAYED = N is added:
SQL> select * from sb11.dnr d
2* where d.dnr_blocked IS NULL and d.cancel_state = 'N'
SQL> /
| Id | Operation                   | Name                 | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT            |                      | 1002 |   166K|    40   (3)| 00:00:01 |
|* 1 | TABLE ACCESS BY INDEX ROWID| XYZ                  | 1002 |   166K|    40   (3)| 00:00:01 |
|* 2 |   INDEX RANGE SCAN          | XYZ_CANCEL_STATE_IND |       |       |     8   (0)| 00:00:01 |
Predicate Information (identified by operation id):
   1 - filter("D"."XYZ_BLOCKED" IS NULL)
   2 - access("D"."CANCEL_STATE"='N')
SQL> select * from sb11.dnr d
2 where d.dnr_blocked IS NULL and d.cancel_state = 'N'
3* and d.payed = 'N'
SQL> /
Execution Plan
Plan hash value: 1292668880
| Id | Operation                   | Name                 | Rows | Bytes | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT            |                      | 1001 |   166K|    89   (3)| 00:00:01 |
|* 1 | TABLE ACCESS BY INDEX ROWID| XYZ                  | 1001 |   166K|    89   (3)| 00:00:01 |
|* 2 |   INDEX RANGE SCAN          | XYZ_CANCEL_STATE_IND |       |       |    15   (0)| 00:00:01 |

Viewobject where clause

Hi, i need to get the where clause from vo in a manage bean method when i'm using a query component.
I have a button than execute one reports and I need to pass to reports a where clause generate in the page with the query component.
thanks in advance

Hi, i've got it. The code is the next:
DCBindingContainer bc = (DCBindingContainer)this.getBindings();
DCIteratorBinding dcIb = bc.findIteratorBinding("TwcdpalabclaveView1Iterator");
ViewObject vo = dcIb.getViewObject();
String v_query = vo.getQuery();
System.out.println(v_query);
System.out.println(v_query.indexOf("WHERE"));
System.out.println(v_query.substring(v_query.indexOf("WHERE")));
String v_where =v_query.substring(v_query.indexOf("WHERE"));
v_where = v_where.replaceAll("WHERE","AND");
System.out.println(v_where);
AttributeList attr = vo.getNamedWhereClauseParams();
String[] attrname= attr.getAttributeNames();
String v_value;
String v_name;
int i =0;
while (i<attrname.length){
v_name = attrname;
System.out.println(v_name);
v_value = "'"+vo.getNamedWhereClauseParam(v_name).toString()+"'";
System.out.println(v_value);
v_where = v_where.replaceAll(v_name,v_value);
i++;
System.out.println(v_where);
thanks dear friends for your time.
Best regards.
luis

Bc4j: set where clause at runtime for view objcet ?

how to set where clause for a view object that is not put in a subselect at runtime ?
select a.para_id, b.para_para_id
from table1 a, table2 b
need to set at runtime either:
where a.para_id = b.para_para_id
or:
where a.para_id = b.para_para_id(+)
problem is that bc4j is useing it as followed:
select * from (
select a.para_id, b.para_para_id
from table1 a, table2 b
) where (a.para_id = b.para_para_id(+))
cant use outer join like this
any suggestions

If you do not want to issue the framework built query, you may want to set the query for a VO yourself instead of setting just the where clause by using setQuery() api. TO revert back to framework built query, call setQuery(null).
This way, when you need the xtra where-clause and not the "innerSQL stuff", you can build a custom sql with whereclause etc, and call setQuery(), execute that SQL, perform your tricks with the VO and then when the VO is usage is done, reset the VO query to original by calling setQuery(null).

Dynamically set ViewObject where clause dynamically from Java bean

I have a requirement to display all of the records from a table when the JSP is first brought up, so my View Object looks like this:
"select emp_name from emp"
Then the users wants to ability to pass paramters to that View Object to refine the list so from by Java class I tried to do this:
ViewObject vo = cpd.findViewObject("EmpViewObject");
vo.setWhereClause("empName = :1");
vo.setWhereClauseParam(1,varEmpName);
vo.executeQuery();
But I am getting JBO errors and I'm not sure what I'm doing wrong. Can anyone offer a hint as to how I can do this?

this is exactly how the code is done -
1. emp_name in the View Object
2. emp_name in the where clause
The two are identical. I have tried many variations of this - any time I set the where clause from my bean I get an error.
When I take the SQL stmnt and run it in TOAD it returns expected rows when I run it in the SQL worksheet in JDev it gives an invalid Identifier - but if I hard code the where clause in the View Object it returns the same results as TOAD.

Dynamically changing the WHERE clause in detail VO in Master Detail

Hi, I want to develop a search functionality, results will be in a table, which will have an inline table displaying the details per row found.
I have a MD defined trough viewlink. I do change the master VO at runtime (set the entire SQL), based on the criteria entered by the user.
Is there a way to change the VO at the detail end of the link at runtime - that is what I haven't been able to do.
I have read that the ADF framework creates internal VO for each master row, whenever accessed trough accessor (which is not I am trying to do). I haven't been able to find a way to get a hold of the REAL VO at the detail end and have its WHERE clause changed.
Changes to the "VO instance in AM" (same one used as a definition in the detail end in the ViewLink def) does not seem to reflect the detail VO.
I have a MasterView, DetailView, MasterDetailLink (MasterView->DetailView).
MasterDetailLink is used to create a table with inline detail table. At runtime:
1.get MasterView (from AM), change query trough setQuesry() - works.
2.get DetailView (from AM), change query trough addWhereClause() - does not work (no exceptions) - the results I am getting DO NOT reflect the conditions of the where clause, I mean the clause have not been addedd.
I 've looked at the logs (debug enabled) and it seems to me that there no "activities" related to the detail VO, even after the where clause of the VO from step 2 is changed.
Looks like there is a separate VO which I would like to get a hold of :)
Thanks, and sorry for the long explanation

After you have added a new where clause on the detail VO, try re-executing VO's query by DetailVO.executeQuery()
If it doesn't work try re-executing the MasterVO's query after you have added the where clause on the detail

Howto use jsp with where-clause restriction for viewObject

hello there,
i am currently trying to figure out how to pass parameters via url to the jsp,
so that the corresponding viewobjects where clause can be extended and i only get the select-results that i want. i am familiar with doing this in a stright java-environment but don't know how to implement it in a jsp-client.
does anyone know something about this or can name me a ressource i can read about that.
Thanx
Selim Keser

thank you, but i have only 19 days left for
my diploma and nobody in this company can help me with this issue.
what i need is an example or something like a reciept about what to do
to achieve the following:
I want to type in an url like:
localhost:8080/myapp/browse.jsp?customerid=123
so that i can extend the where-clause in my ViewObject
and only see the rows of customer 123 in my jsp.
it is a bit hard for a newbie to figure out how to pass down the parameters way down to the ViewObject. I am shure that this is easy to do once one understands the how it works. This is my first "Web-Experience" and I am running out of time.
Thanx
Selim Keser

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????

Including additional where clause conditions to view criteria dynamically

Hi,
We have a set of view objects that serves as LOV for various other view objects. All such LOV view objects have three specific attributes, two date attributes namely EffectiveStartDate, EffectiveEndDate and a String attribute namely UserSwitch based on which the LOV list needs to be filtered.
All the view objects are having one or more view criterias with specific where clause conditions.
Apart from those view criteria conditions, invariantly, we need the following conditions also
:bindEffDate between EffectiveStartDate and EffectiveEndDate and UserSwitch = :bindUserSwitch.
We wish not to include the above condition in each and every view criteria of each and every view object (Since we have around 800 view objects and a minimum of 2 view criterias per view object). Instead, we created a dummy view object (BaseViewObject) with two bind variables :bindEffDate and :bindUserSwitch and all the LOV view objects were made to extend this BaseViewObject.
Therefore, whenever a view object atribute is attached with LOV using the above said LOV View Objects, the bind variables of the baseViewObject as well as the view object specific bind variables are available in the view accessors tab of the view object wizard where we can supply values to those bind variables.
Now, we need to construct the view criteria filter clause. To achieve this, we created a class, CustomCriteriaAdapter.java extending oracle.jbo.server.CriteriaAdapterImpl. In the getCriteriaClause() method, we included the follwoing code:
public String getCriteriaClause(ViewCriteria pViewCriteria)
ViewObject vo = pViewCriteria.getViewObject();
String userSelectSwitch = (String) vo.ensureVariableManager().getVariableValue("bindUserSwitch");
String effBgnDt = vo.getAttributeDef(vo.getAttributeIndexOf("EffectiveStartDate")).getName();
String effEndDt = vo.getAttributeDef(vo.getAttributeIndexOf("EffectiveEndDate")).getName();
String customCriteria = " ( :bindEffDate >= " + effBgnDt + " ) AND ( :bindEffDate <= " + effEndDt + " OR " + effEndDt + " IS NULL ) ";
StringBuffer completeCriteria = new StringBuffer();
String criteriaClause = super.getCriteriaClause(pViewCriteria);
if (criteriaClause != null && !criteriaClause.isEmpty())
completeCriteria.append(criteriaClause + " AND ");
completeCriteria.append(customCriteria);
if (userSelectSwitch != null && "Y".equals(userSelectSwitch))
String userSelectSw = vo.getAttributeDef(vo.getAttributeIndexOf("UserSwitch")).getName();
completeCriteria.append(" AND (" + userSelectSw + "='Y' ) ");
return completeCriteria.toString();
Issues:
The LOV list is not filtering the records based on the constructed conditions. Instead it is listing either all of the records considering only the view criteria conditions applied at design time irrespective of the userswitch and effectivedate conditions or the list is empty.
Here, my questions are,
1. Am I in the correct approach? If not, guide me in a more proper approach to achieve the same requirement.
2. If the way I am trying is correct, where things are going wrong and why the dynamic condition is not getting effected?
Kindly help in sorting out the issue.
Thanks in advance.

Hi Jobinesh,
Thanks for your response and yes, we have done exactly as what you have mentioned. As explained earlier, a baseViewObject along with its Impl class has been created and it will be extended by all the viewobjects meant for serving LOV. Therefore, the superClass for any such LOV viewObject is the baseViewObjectImpl class. In that baseViewObjectImpl(), we have over-rided the criteriaAdapter() method and returned an instance of our customCriteriaAdapter() class.
Below is the code we are using in the baseViewObjectImpl():
package model.base.vo;
import oracle.jbo.CriteriaAdapter;
import oracle.jbo.server.ViewObjectImpl;
public class BaseViewObjectImpl
extends ViewObjectImpl
* This is the default constructor (do not remove).
public BaseViewObjectImpl()
* Over-rided method of ViewObjectImpl class of the framework.
* Calls the customized criteria adapter so that the default where clauses are added to the view criteria.
* @return CriteriaAdapter.
@Override
public CriteriaAdapter getCriteriaAdapter()
return new CustomCriteriaAdapter();
I'll create a sample in HR schema and share with you shortly.
Thanks and regards.

Dynamically adding filters in where clause in sql server

Hello I have a question,
may be asked many times but could not find a thread,
I have 8 parameters,... and user can select any of these parameters they can select 3,4 or all 8.
I know we could use dynamic sql for this, because the sql is same.. just the where clause changes as how many parameters we are selecting,
i am using sql server 2012.. is there a easy way to manage this,
Please let me know.

Consider static (dynamic) search:
http://www.sommarskog.se/dyn-search.html
Alternative, dynamic SQL:
http://www.sqlusa.com/bestpractices/dynamicsql/
Kalman Toth Database & OLAP Architect
SQL Server 2014 Database Design
New Book / Kindle: Beginner Database Design & SQL Programming Using Microsoft SQL Server 2014

VOWizard-Bug: WHERE Clause not modified on EO add if manually changed befor

VOWizard-Bug: WHERE Clause is not modified on adding a EO (with association) if it was manually changed before
Testcase:
- Create a VO based on 2 EO (Association already defined) --> Jon in WHERE Clause automatically created by Wizard
- Then modify the WHERE clause, e.g. change an equal to outer join.
- All works fine.
- Then add a EO (also Association defined) and chose some attributes.
- Test and wonder why there are much more rows in the result than expected.
- Look into the Query-Tab and control the WHERE clause: Wizard forgot to add the new join... and therefore we get a cartesian product between the old view and the new added EO...
Possible solutions to fix the Bug:
1. add the JOIN ;-)
or
2. at least display a warning that the JOIN is not automatically created!
Regards, Markus
GE Medical Systems

Hi Markus-
Once the where clause has been customized, we don't update it in the interest of not messing up the user's custom code. However, we should probably warn the user in the types of cases you mention above that he will need to update the where clause manually to include the new information. We will add this in a future release.
Thanks,
Ray

Where clause with Bind Variable in ViewObject

As per recomendations from Jdev team they say that using Bind varialbles in where clause will improve the performance (Option 1) But it is causing us to create more view objects.
Example : Lets say we have a View Object EmpVO
Option 1:
ViewObject vo=context.getViewObject("EmpVO");
vo.setWhereClause("EMPNO=?");
vo.setWhereClauseParam(0,st);
(or)
Option 2:
vo.setWhereClause("EMPNO="+st);
If we want to use same View Object "EmpVO" in another Action Class
ViewObject vo1=context.getViewObject("EmpVO");
vo1.setWhereClause("DEPTNO=?");
vo1.setWhereClauseParam(0,str);
It this case it throws an error saying BIND VARIABLE already exits. So we have to make another View Object.
Where as if we did not use bind variable but used Option 2 approach the same view object can be used in multiple pages.(at the expense of performance as per Jdev team)
Are we doing something wrong here or are there other ways to use the same view object when using bind variable in where clause.
Thanks

I haven't been using BC4J for a while, but I seem to recall that the recommendations are that you don't set the where clause at runtime: You're supposed to define your view with the bind parameter already in it.
So you'd probably define an EmpsForEmpNoVO and type "EMPNO = ?" in the where box. (There are other ways of finding a single row/entity and one of those may well be more efficient. Perhaps a better example of where you might want a view of employees is WHERE DEPTNO = ?.)
IIRC, all instances of a particular type of view share the same definition, so you have to be careful if you alter that at runtime. However, I think everything's set up so that you can have many different (and separate) resultsets for a single view (instance) - meaning that it's possible to "run" a view for (e.g.) two different ids. (It's definitely possible to create two different instances of a view from its definition - and the resultsets will definitely be separate then. I think there's a "create" method on the application module; I remember that "find..." always returns the same instance of the view.)
Hope that's a push in the right direction (since no-one else had replied - and I hope not too much has changed since 9.0.3)....
Mike.

Prompted value corrupts SQL WHERE clause - bug?

Using 10.1.3.4...
I implemented a simple pivot based request that navigates to a second request when the user drill down on one of the fields. This field is set to "value is prompted" in my second request. (I chose navigate method above drill (dimensions) for a few reasons not really important to this posting, mainly to do with format of requests at different levels)
All good and the drill down works well, parameters are passed correctly, except then I noticed that totals in my second request doesn't accurately tie back to my first request. After some research I found a very odd reason for this, my WHERE clause is getting corrupted - which almost looks like a bug in OBIEE and were wondering if anybody else has seen this behaviour from OBIEE and know a work around (before I try the Oracle support channels)
From Answers the request SQL is (I'll highlight the lines getting messed up):
SET VARIABLE DISABLE_CACHE_HIT = 1;
SELECT
BUSINESS_UNIT.Segment saw_0, BUSINESS_UNIT."Business Unit" saw_1, OPPORTUNITY.CLOSEPROBABILITY saw_2, OPPORTUNITY.CLOSEPROBABILITY saw_3, YEAR(OPPORTUNITY.ESTIMATEDCLOSE) saw_4, OPPORTUNITY_ADDON.TCV_IN_USD/1000000 saw_5, OPPORTUNITY_ADDON.WEIGHTED_TCV_IN_USD/1000000 saw_6, CASE OPPORTUNITY.CLOSEPROBABILITY WHEN 100 THEN OPPORTUNITY_ADDON.TCV_IN_USD/1000000 ELSE 0 END saw_7 FROM "Sales"
WHERE (OPPORTUNITY.STAGE NOT IN ('Lost', 'On Hold')) AND (YEAR(OPPORTUNITY.ESTIMATEDCLOSE) >= YEAR(CURRENT_DATE)) AND
((({color:#ff0000}OPPORTUNITY.CLOSEPROBABILITY > 25) AND (TIMESTAMPDIFF(SQL_TSI_MONTH, CURRENT_DATE,OPPORTUNITY.ESTIMATEDCLOSE) <= 4)) OR ((OPPORTUNITY.CLOSEPROBABILITY >= 10) AND (TIMESTAMPDIFF(SQL_TSI_MONTH, CURRENT_DATE,OPPORTUNITY.ESTIMATEDCLOSE) > 4{color})))
ORDER BY saw_0, saw_1, saw_2, saw_3, saw_4, saw_5, saw_6, saw_7
Which results in the following SQL request (from NQQuery.log)... The prompted value (BUSINESS_UNIT.Segment) is added correctly to the WHERE clause, but see how the remainder get's changed:
SQL Request:
SET VARIABLE QUERY_SRC_CD='Report',SAW_DASHBOARD='/shared/01 - Financials/_portal/4. Pipeline',SAW_DASHBOARD_PG='Pipeline',SAW_SRC_PATH='/shared/01 - Financials/4. Pipeline/Pipeline - Current - T2',DISABLE_CACHE_HIT = 1;
SELECT
BUSINESS_UNIT.Segment saw_0, BUSINESS_UNIT."Business Unit" saw_1, OPPORTUNITY.CLOSEPROBABILITY saw_2, OPPORTUNITY.CLOSEPROBABILITY saw_3, YEAR(OPPORTUNITY.ESTIMATEDCLOSE) saw_4, OPPORTUNITY_ADDON.TCV_IN_USD/1000000 saw_5, OPPORTUNITY_ADDON.WEIGHTED_TCV_IN_USD/1000000 saw_6, CASE OPPORTUNITY.CLOSEPROBABILITY WHEN 100 THEN OPPORTUNITY_ADDON.TCV_IN_USD/1000000 ELSE 0 END saw_7 FROM "Sales"
WHERE (BUSINESS_UNIT.Segment = 'Enterprise') AND (OPPORTUNITY.STAGE NOT IN ('Lost', 'On Hold')) AND (YEAR(OPPORTUNITY.ESTIMATEDCLOSE) >= YEAR(CURRENT_DATE)) AND
((({color:#ff0000}OPPORTUNITY.CLOSEPROBABILITY >= 10) AND (TIMESTAMPDIFF(SQL_TSI_MONTH, CURRENT_DATE,OPPORTUNITY.ESTIMATEDCLOSE) > 4)) OR ((OPPORTUNITY.CLOSEPROBABILITY >= 10) AND (TIMESTAMPDIFF(SQL_TSI_MONTH, CURRENT_DATE,OPPORTUNITY.ESTIMATEDCLOSE) > 4{color})))
ORDER BY saw_0, saw_1, saw_2, saw_3, saw_4, saw_5, saw_6, saw_7
Which definitely explains why my totals do not add up when drilling down. Interestingly, if I run my second request without the prompt from Answers, the SQL request works like a charm:
SET VARIABLE QUERY_SRC_CD='Report',SAW_SRC_PATH='/shared/01 - Financials/4. Pipeline/Pipeline - Current - T2',DISABLE_CACHE_HIT = 1;
SELECT BUSINESS_UNIT.Segment saw_0, BUSINESS_UNIT."Business Unit" saw_1, OPPORTUNITY.CLOSEPROBABILITY saw_2, OPPORTUNITY.CLOSEPROBABILITY saw_3, YEAR(OPPORTUNITY.ESTIMATEDCLOSE) saw_4, OPPORTUNITY_ADDON.TCV_IN_USD/1000000 saw_5, OPPORTUNITY_ADDON.WEIGHTED_TCV_IN_USD/1000000 saw_6, CASE OPPORTUNITY.CLOSEPROBABILITY WHEN 100 THEN OPPORTUNITY_ADDON.TCV_IN_USD/1000000 ELSE 0 END saw_7 FROM "Sales"
WHERE (OPPORTUNITY.STAGE NOT IN ('Lost', 'On Hold')) AND (YEAR(OPPORTUNITY.ESTIMATEDCLOSE) >= YEAR(CURRENT_DATE)) AND
((({color:#ff0000}OPPORTUNITY.CLOSEPROBABILITY > 25) AND (TIMESTAMPDIFF(SQL_TSI_MONTH, CURRENT_DATE,OPPORTUNITY.ESTIMATEDCLOSE) <= 4)) OR ((OPPORTUNITY.CLOSEPROBABILITY >= 10) AND (TIMESTAMPDIFF(SQL_TSI_MONTH, CURRENT_DATE,OPPORTUNITY.ESTIMATEDCLOSE) > 4{color})))
ORDER BY saw_0, saw_1, saw_2, saw_3, saw_4, saw_5, saw_6, saw_7
Anybody had the same problem before?

Here's the excerpt (it's relative to crashing, but I think it should also address the bug):
# PRESENTATION SERVER CRASH AFTER UPGRADING TO 10.1.3.4 (Doc ID 756541.1)
crash when they run the reports containing Pivot Table. This has been a known issue with version ... subsequently upgraded to version
Doc Type:ALERTModified:2/10/2009

A bug? BC4J ViewObject where clause change doesn't affect view contents

Similar Messages

Maybe you are looking for