cache-query-results question

I have another post for general descriptor tag information but I do have a specific question. In a project I am looking at I see:
<cache-usage> check cache by primary key </cache-usage>
<cache-query-results>false</cache-query-results>
<maintain-cache>true</maintain-cache>
I'm not sure how to interpret this. Does this mean that a cache is in place or not? cache-query-rests is set to false which implies no caching, yet the other parameters imply a cache is in place. What overrides here?
Thanks

The XML maps directly to the API so the JavaDocs and related documentation are the best tools:
cache-usage: query.setCacheUsage(int)
This option indicates how the object cache should be used when processing the query. This is how in-memory query is configured as well as support for cache-hits on ReadObjectQuery.
cache-query-result: query.setShouldCacheQueryResults(boolean)
This option allows you to indicate that the results returned from the query execution should be held. When the query is executed again these results will be returned without going to the database or searching the object cache. This is just caching the results locally within the query.
maintain-cache: query.maintainCache() or query.dontMaintainCache()
This setting determines if the results returned from the query should be cached in the shared object cache. It is on by default and turning this off is very rare. Occasionally done to compare the cache version with the database verision when handling an optimistic locking failure.
Doug

Similar Messages

Cannot query using both conforming and cached query result

TopLink doesn't allow me to both use conforming and cached query result at the same time.
Conforming is certainly not a superset of the [cached query result] features.
Can you confirm that it's a limitation of TopLink?
Any know workaround to end-up with the same features as using both conforming and cached query result?
Conforming is about seeing modifications you do in the same transaction. As a bonus, if you query for one object and specify at least the id as criteria because TopLink will have to check in memory anyway it can avoid going to the database.
But if I do a query like "give me employees hired before now and after 30 days ago" it's about more than one objects and about finding existance so cached query result is needed to get acceptable performance in a complex application trying to avoid the same SQL generated over and over again.

Thats where the trace just ends? It doesnt look like there's any LIKE or filtering going on (with respect to the Oracle pieces anyway), apparently MSAccess simply requested the whole table.
What do you mean by 'hang' exactly? Are you sure it's just not taking a long time to complete? How long have you waited? How fast does it complete on the other environment?
ODBC tracing isnt likely to help much for that. SQLNet tracing would be better to see what is going on at a lower level. Specifically, what is going on at the network level? Is the client waiting for a packet to be returned from the database?
Is the database having a hard time processing the query, perhaps due to index/tuning issues?
Assuming that is indeed the query that is "hung", how much data does that return?
Are you able to reproduce the same behavior with that query and vbscript for example?
Greg

Service Offering, Query Results question.

Hi,
I got a question about the Service Offering, Query Results criteria page.
As shown in the Picture below i have a Query based on the Active Directory User Class.
The background is that i got alot of accounts more than 2000. The token "String" is used to narrow down the search. I also got some accounts that i dont want to show in the portal for the end users (The ones who
ends with "Z" in the pager).
Generally i would say that the "OR" would be "AND" (due to it is an logical operator, i want both conditions to be true) between the two UserPager properties, but i havent found any way to change that. I suspect that it is not possible
to change "OR" to "AND" when making criterias against the same values more than 1 time.
The Query below will return all accounts under that Distinguished name, even if i wrote something in the String prompt. Removing the Criteria Pager ends on "Z" makes the String prompt work. But it will not exclude those objects ending with
Z. Is this a normal behavior or am i thinking/doing sometime wrong?

This is how all criterias work in service manager. If the same property is included more than once it puts an OR inbetween. You would have to export the MP that contains the query result and edit the criteria manually to AND.
Cheers,
Anders Spælling
Senior Consultant
Blog:
Twitter: LinkedIn:
Please remember to 'Propose as answer' if you find a reply helpful

Caching query results?

Hi guys,
I have this page which calls the same query (across a database link!) four times! First when an initial LOV is generated (and the page is loaded), again for another LOV based off the initial one and finally for the report generated based off the 2 selections. This is crazily slow (30-40 seconds each load~) and also: When you try to sort with an Interactive Report by clicking the column names it then queries the database again (I assumed this part was cached but apparently not). I therefore need to cache the results from an initial query and then just limit the results locally. How can I do this? Guides? Examples?
Thanks for help.
Mike

I tried this example based on a view:
CREATE MATERIALIZED VIEW MV_TEST2
     REFRESH COMPLETE
     START WITH SYSDATE
     NEXT SYSDATE + 1/48
     WITH ROWID
     AS SELECT * FROM test1;REFRESH COMPLETE -- The complete refresh re-creates the entire materialized view.
START WITH SYSDATE -- run now
NEXT SYSDATE + 1/48 -- run again in half an hour
WITH ROWID -- I think this option is important if you use partial refresh of the view.
AS SELECT * FROM test1; -- test1 is a view:
CREATE OR REPLACE VIEW TEST1 AS
SELECT st_id, st_name
    FROM aaw_solution_tree;Are column indexes still possible? I'm not sure:
Indexing: !with respect to MV's on 10gR2 Jonathan Lewis wrote! ... you are allowed to create indexes on the tables that sit under materialized views - just don't make them unique indexes
How much freedom is there in setting the refresh rate?
What type of refreshing do you need?
Another useful link: [http://asktom.oracle.com/pls/ask/search?p_string=materialized+view|http://asktom.oracle.com/pls/ask/search?p_string=materialized+view]
Hope it helps.
Tobias

How to force Work Item Query Policy to refresh its cached query results?

I have enabled the Work Item Query Policy on my TFS project. It works as expected, except when using Visual Studio 2013 with the following sequence of steps:
User selects Check in Pending Changes from the Source Control Explorer
User enters in the ID of the work item to be associated to the changeset
User clicks the Check In button
Work Item Query Policy displays message ' Work item ##### was not found in the results of stored query...'
User realizes his mistake, and modifies (and saves) the work item so that it is returned in in the query result set
User clicks the Check In button again expecting the TFS policy to accept the association
Work Item Query Policy still displays message ' Work item ##### was not found in the results of stored query...'
Removing the Work Item and re-associating it does not make a difference. The only workaround that I have found is to close Visual Studio and reopen it. Does any one have a better solution than this?

Our setup is different from the one you are using:
- User is using VS 2013 Update 4.
- We are running TFS 2010 SP1
The test case that you described is different from the one that is causing my problem (that scenario works fine for me as well). I am trying to associate the check in to the same work item both times; whereas, you are associating it to a different
work item the second time. I can consistently reproduce the error using the following steps:
1) Create a query that returns All Bugs in Active state, and set it as the query for the Work Item Query Policy
2) Create and save a new Bug
3) Run the query to confirm that the new bug does not appear in the result set
4) Checkout a file, modify it, save it
5) Check in the file and associate it to the bug from step 2)
- the Work Item Query Policy will issue an error message saying that the work item cannot be found in the associated query
6) Change the state of the bug to Active, and save
7) Refresh the query to confirm that the bug now appears in the result set
8) Check in the file again
- error message from step 5) will not go away

OEM Query Results Question

Hi..
I am working on a query to display the last 30 days of uptime for our databases. This is the query:
select availability_status, target_name, target_type, end_time - start_time from (select availability_status, target_name, target_type,
nvl(end_timestamp, sysdate) end_time,
case when start_timestamp < sysdate -31 then sysdate -31
else start_timestamp end start_time
from MGMT$AVAILABILITY_HISTORY
where nvl(end_timestamp, sysdate) > sysdate -31
and target_name ='FSPERF11')
I get the results below:
AVAILABILITY_STATUS TARGET_NAME TARGET_TYPE END_TIME-START_TIME
Agent Down FSPERF11 oracle_database 0.006
Target Down FSPERF11 oracle_database 0.003
Target Down FSPERF11 oracle_database 0.001
Target Up FSPERF11 oracle_database 2.91
Target Up FSPERF11 oracle_database 10.803
Target Up FSPERF11 oracle_database 0
Target Up FSPERF11 oracle_database 17.27
The question I have is why do I have multiple results when I am only looking for database uptime/downtime? Why do I have 3 Target Up results?
Thanks...

Thanks! When I collect the SQL it gives me an invalid SQL statement error when I go to run it. This is the SQL listed:
SELECT sum(Avail) OVERALL_AVAILABILITY_PER_ID , sum(T_Uptime) TOTAL_UPTIME_HRS_ID , sum(T_Downtime) TOTAL_DOWNTIME_HRS_ID , sum(T_Blackouttime) TOTAL_BLACKOUT_TIME_HRS_ID, sum(T_Unmonitoredtime) TOTAL_UNMONITORED_TIME_HRS_ID from(
select 0 Avail, 0 T_Uptime, 0 T_Downtime, 0 T_Blackouttime, 0 T_Unmonitoredtime from dual UNION ALL
SELECT round( st_dur.tgt_up/(decode(st_dur.tgt_up+st_dur.agent_down+st_dur.tgt_down,0,1,st_dur.tgt_up+st_dur.agent_down+st_dur.tgt_down))*100,2) Avail
,round((st_dur.tgt_up*24),2) T_Uptime, round((st_dur.tgt_down*24),2) T_Downtime, round((st_dur.blackout*24),2) T_Blackouttime, round(((st_dur.agent_down+st_dur.metric_error+st_dur.pend_unknown+st_dur.unreach)*24),2) T_Unmonitoredtime
FROM (
SELECT SUM( decode(AVAI_STATUS,'agent down',DURATION,0)) agent_down,
     SUM(decode(AVAI_STATUS,'blackout',DURATION,0)) blackout,
     SUM(decode(AVAI_STATUS,'metric error',DURATION,0)) metric_error,
     SUM(decode(AVAI_STATUS,'pending/unknown',DURATION,0)) pend_unknown,
     SUM(decode(AVAI_STATUS,'target down',DURATION,0)) tgt_down,
     SUM(decode(AVAI_STATUS,'target up',DURATION,0)) tgt_up,
     SUM(decode(AVAI_STATUS,'unreachable',DURATION,0)) unreach FROM(
          SELECT LOWER(A.AVAILABILITY_STATUS) AVAI_STATUS
          ,ROUND(least(nvl(A.end_timestamp,(CAST(systimestamp at time zone B.TIMEZONE_REGION AS DATE))), MGMT_VIEW_UTIL.ADJUST_TZ(??EMIP_BIND_END_DATE??,??EMIP_BIND_TIMEZONE_REGION??,B.TIMEZONE_REGION) )
          -greatest(A.start_timestamp,MGMT_VIEW_UTIL.ADJUST_TZ(??EMIP_BIND_START_DATE??,??EMIP_BIND_TIMEZONE_REGION??,B.TIMEZONE_REGION) ),4) DURATION
          FROM mgmt$availability_history A,MGMT$TARGET B WHERE A.target_guid=??EMIP_BIND_TARGET_GUID?? AND A.TARGET_GUID=B.TARGET_GUID
     and A.start_timestamp>=(select min(NVL(end_timestamp,(CAST(systimestamp at time zone B.TIMEZONE_REGION AS DATE)))) from mgmt$availability_history where target_guid=??EMIP_BIND_TARGET_GUID?? )
     and ((A.start_timestamp>MGMT_VIEW_UTIL.ADJUST_TZ(??EMIP_BIND_START_DATE??,??EMIP_BIND_TIMEZONE_REGION??,B.TIMEZONE_REGION) AND NVL(A.end_timestamp,(CAST(systimestamp at time zone B.TIMEZONE_REGION AS DATE)))<MGMT_VIEW_UTIL.ADJUST_TZ(??EMIP_BIND_END_DATE??,??EMIP_BIND_TIMEZONE_REGION??,B.TIMEZONE_REGION))
          OR(MGMT_VIEW_UTIL.ADJUST_TZ(??EMIP_BIND_START_DATE??,??EMIP_BIND_TIMEZONE_REGION??,B.TIMEZONE_REGION) between A.start_timestamp AND NVL(A.end_timestamp,(CAST(systimestamp at time zone B.TIMEZONE_REGION AS DATE))))OR
          (MGMT_VIEW_UTIL.ADJUST_TZ(??EMIP_BIND_END_DATE??,??EMIP_BIND_TIMEZONE_REGION??,B.TIMEZONE_REGION) between A.start_timestamp and NVL(A.end_timestamp,(CAST(systimestamp at time zone B.TIMEZONE_REGION AS DATE)))))
)st_dur)
What do the "??" represent and how do I get it to run?
Thanks again...

Cache query results in too much garbage collection activity

Oracle Coherence Version 3.6.1.3 Enterprise Edition: Production mode
JRE 6 Update 21
Linux OS 64 bit
The application is using a object Customer having following structure
Customer(CustID, FirstName, LastName, CCNumber, OCNumber)
Each property of Customer is a inner classes having getValue as one of the methods retuning a value. The getValue method of CCNumber and OCNumber return a Long value. There are 150m instances of Customer in cache. To hold this much data in cache we are running several nodes on 2 machines.
The following code is used to create indexes on CCNumber and OCNumber:
     ValueExtractor[] valExt = new ValueExtractor[]{
          new ReflectionExtractor("getCCNumber"), new ReflectionExtractor("getValue")};
     ChainedExtractor chExt = new ChainedExtractor(valExt);
     Long value = new Long(0);
     Filter f = new NotEqualsFilter(chExt, value);
     ValueExtractor condExtractor = new ConditionalExtractor(f, chExt, true);
     cache.addIndex(condExtractor, false, null);The client code queries the cache with following code:
     ValueExtractor[] valExt1 = new ValueExtractor[]{
          new ReflectionExtractor("getCCNumber"), new ReflectionExtractor("getValue")};
     ChainedExtractor chExt1 = new ChainedExtractor(valExt1);
     EqualsFilter filter1 = new EqualsFilter(chExt1, ccnumber);
     ValueExtractor[] valExt2 = new ValueExtractor[]{
          new ReflectionExtractor("getOCNumber"), new ReflectionExtractor("getValue")};
        ChainedExtractor chExt2 = new ChainedExtractor(valExt2);
     EqualsFilter filter2 = new EqualsFilter(chExt2, ocnumber);
     AnyFilter anyFilter = new AnyFilter(new Filter[]{filter1, filter2})
     cache.entrySet(anyFilter);The observation is that for 20 client threads the application performs well(avg response time = 200ms) but as the number of client threads increases the application performance goes down disproportionately(query returns anywhere between 1000ms to 8000ms for 60 threads). I think this is because of the eden space filling up very fast when the number of client thread goes up. The number of collections per second goes up with the number of client threads. There are almost 2-3 ParNew collections every second when there are 60 client threads where as only 1 collection per second for 20 client threads. Even 100-200ms pause degrades the overall query performance.
My question is why coherence is creating so many objects that fills up eden so fast? Is there anything I need to do in my code?

Hi Coh,
The reason for so much garbage is that you are using ReflectionExtractors in you filters, I assume you do not have any indexes on your caches either. This means that each time you execute a query Coherence has to scan the cache for matches to the filter - like a full table scan in a DB. For each entry in the cache Coherence has to deserialize that entry into a real object then using reflection call the methods in the filters. Once the query is finished all these deserialized objects are garbage that needs to be collected. For a big cache this can be a lot of garbage.
You can change to POF extractors to save the deserialization step which should reduce the garbage quite a bit, although not eliminate it. You could also use indexes, which should eliminate pretty much more of the garbage you are seeing during queries.
JK

Performance problem...is there a way to cache query results?

Greetings team,
I've been deploying DS5.2 for a while now, and am on the cusp of pushing it into our production environment, however I've been noticing lately that some hosts are taking an exorbitantly long time to log in (actually, a user noted it, and I'm now investigating).
Logins to hosts in this environment can take anywhere from 10-50 seconds. One thing that I've noticed is that any time you run a command that requires any amount of awareness of uid->username translation (i.e. if you ls -l /opt/home), queries are made to the configured directory server for this information. Is this normal? Since uid's and usernames don't often change (in most environments, anyway), is there a way this could be cached?
I see also in my access log for my primary server (configured as a hub, btw) that there is near constant traffic to that host for LDAP info. I'm not sure why it's so chatty, but it does appear to be slowing things down a bit. The load on my LDAP host (a SunFire V210 w/ 1GHz processor, 1024MB RAM) seems to float between 1 and 12, with sar reporting an average idle time of about 44%.
Any ideas? I'm really at a loss to explain why there's so much traffic to this host when much of it seems to come from hosts with nobody logged into them.
Patrick

It is great that you have found the root cause of
your issue.
nscd is by default started at boottime by a usual OS
install. There is a /etc/nscd.conf but I doubt that
anyone will change anything there as the default
settings are good for most cases.
I think LDAP search performance is affected by the
existence of Search Indexes also.
I have observed that if the user home directory is
NFS mounted especially over a WAN, be it via
/etc/fstab or automount maps, the login process will
be very slow, it will take a while to obtain a
command prompt at the home directory level.
GaryGary et al,
In my environment nscd has been explicitly disabled for some historical reasons, none of which are still a problem. So, I'm going to enable it for only passwd and group caching, with the default values for those caches.
I'm in the process of working out my performance tuning plan for my LDAP servers, but I'm definitely going to have an eye on indices and caches. Those will probably have the least impact on search times and such for the moment since my directory is so tiny (261 entries!), but preventing that traffic from hitting the server at all will be a huge savings.
I can definitely see why WAN mounted homedirs would cause things to lag. That's not the case here since NFS is a big no-no.
Patrick

Query result caching on oracle 9 and 10 vs indexing

I am trying to improve performance on oracle 9i and 10g.
We use some queries that take up to 30 minutes to execute.
I heard that there are some products to cache query results.
Would this have any advantage over using indexes or materialized views?
Does anyone know any products that I can use to cache the results of this queries on disk?
Personally I think that by using the query result caching I would reduce the cpu time needed to process the query.
Is this true?

Your message post pushes all the wrong buttons starting with the fact that 9i and 10g are marketing labels not version numbers.
You don't tune queries by spending money and throwing resources at them. You tune them by identifying the problem queries, running explain plans, visualizing their output using DBMS_XPLAN, and addressing the root cause.
If you want help post full version numbers, the SQL statements, and the DBMS_XPLAN outputs.

Query result cache with functions

Hi all,
one of my colleagues has found a little bit weird behavior of a query result cache. He has set result_cache_mode = 'FORCE' (but it can be reproduced with a result_cache hint too) and suddenly functions called from the query get executed twice (for the first time) .
An easy example:
alter session set result_cache_mode = 'FORCE';
create sequence test_seq;
create or replace function test_f(i number)
return number
is
begin
dbms_output.put_line('TEST_F executed');
--autonomous transaction or package variable can be used too
return test_seq.nextval;
end;
prompt First call
select test_f(1) from dual;
prompt Second call
select test_f(1) from dual;
drop sequence test_seq;
drop function test_f;
First call
TEST_F(1)
         2
TEST_F executed
TEST_F executed
Second call
TEST_F(1)
         1
As you can see - for the first time the function is executed twice and return the value from the second execution. When I execute the query again it returns the value from the first execution... but it doesn't matter, problem is in the double execution. Our developers used to send emails via select (it's easier for them):
select send_mail(...) from dual;
... and now the customers complains that they get emails twice
And now the question - is there any way, hot to get rid of this behavior (without changing the parameter back or rewriting code)? I thought that the result cache is automatically disabled for non-deterministic functions...or is this an expected behavior?
Thanks,
Ivan

Interesting.. you are right:
SELECT /*+ RESULT_CACHE */ 'dog' FROM DUAL;
And at the second execution:
| Id | Operation        | Name                       | Rows | Cost (%CPU)| Time     |
|   0 | SELECT STATEMENT |                            |     1 |     2   (0)| 00:00:01 |
|   1 | RESULT CACHE    | cc5k01xyqz3ypf9t0j28r5gtd1 |       |            |          |
|   2 |   FAST DUAL      |                            |     1 |     2   (0)| 00:00:01 |
Hmmm..

Using the client result cache without the query result cache

I have constructed a client in C# using ODP.NET to connect to an Oracle database and want to perform client result caching for some of my queries.
This is done using a result_cache hint in the query.
select /*+ result_cache */ * from table
As far as I can tell query result caching on the server is done using the same hint, so I was wondering if there was any way to differentiate between the two? I want the query results to be cached on the client, but not on the server.
The only way I have found to do this is to disable all caching on the server, but I don't want to do this as I want to use the server cache for PL/SQL function results.
Thanks.

e3a934c9-c4c2-4c80-b032-d61d415efd4f wrote:
I have constructed a client in C# using ODP.NET to connect to an Oracle database and want to perform client result caching for some of my queries.
This is done using a result_cache hint in the query.
select /*+ result_cache */ * from table
As far as I can tell query result caching on the server is done using the same hint, so I was wondering if there was any way to differentiate between the two? I want the query results to be cached on the client, but not on the server.
The only way I have found to do this is to disable all caching on the server, but I don't want to do this as I want to use the server cache for PL/SQL function results.
Thanks.
You haven't provided ANY information about how you configured the result cache. Different parameters are used for configuring the client versus the server result cache so you need to post what, if anything, you configured.
Post the code you executed when you set the 'client_result_cache_lag' and 'client_result_cache_size' parameters so we can see what values you used. Also post the results of querying those parameters after you set them that show that they really are set.
You also need to post your app code that shows that you are using the OCI statements are used when you want to use client side result cacheing.
See the OCI dev guide
http://docs.oracle.com/cd/B28359_01/appdev.111/b28395/oci10new.htm#sthref1491
Statement Caching in OCI
Statement caching refers to the feature that provides and manages a cache of statements for each session. In the server, it means that cursors are ready to be used without the need to parse the statement again. Statement caching can be used with connection pooling and with session pooling, and will improve performance and scalability. It can be used without session pooling as well. The OCI calls that implement statement caching are:
OCIStmtPrepare2()
OCIStmtRelease()

Query results cached?

For a report region, is the query results cached?
That is, is the report query being executed again
in the following condition:
* when a user navigate between pages of a report
(from page 1 (1-100 of 1000 rows) to page 2 (101-200 of 1000 rows)
* when a user clicks on the column heading to sort the report

Ken,
In both cases the query is executed again.
Regards,
Marc

RE: Load of query results

Hi Patrice,
Currently, there is little difference between the enterprise edition and
the standard edition as you pointed out. However, over time, we expect
to see some major differences as we add fucntionality that is more
suited for enterprise application - caching is one of these major
differences.
We are staggering the release of the SE and EE versions for several
reasons: 1) we believe the EE needs to have additional functionality to
justify the two versions and what will be 2 different price points; 2)
we are hopeful that the specification is finalized shortly - we feel a
certain discomfort with releasing an "Enterprise" version based on a
Draft specification; and 3) we are using the SE version to better
understand the market and the needs of the EE customers. We've put out
the EE beta to inform those interested in the EE version that one will
be available.
No, we do not have a reseller in France at this time although we have
some development that takes place in Paris. We are definitely
interested in developing business development relationships throughout
the world to penetrate this market as efficiently as possible. Do you
have any suggestions on resellers in France?
Thanks for your interest.
Neelan Choksi
The Kodo JDO Product Team
-----Original Message-----
From: Patrice Thiebaud
To: Choksi, Neelan
Sent: 8/13/01 1:18 PM
Subject: RE: Load of query results
Choksi,
Thank you for the information.
I have the additional three following questions :
in my understanding :.. the Enterprise Edition currently only adds the synchronization with
the transaction manager of an application server
.. the JDO specification also mandates the use of a JCA adapter in the
context of a managed environment
- are you going to provide also a JCA adapter that could use any JDBC
driver ?
- how come that there is such a time interval between the GA dates of SE
and EE ?
do you have a reseller in France ? If not, are you looking for one ?Thanks in advance.
At 22:14 11/08/2001 -0400, you wrote:
Hi Patrice and all,
We are planning on releasing Kodo JDO Standard Edition in late August or
early September. We have not determined a release date for the
Enterprise
Edition (likely towards the end of the year).
Thanks,
Neelan Choksi
Kodo JDO Product Team
-----Original Message-----
From: White, Abe [ mailto:[email protected]
<mailto:[email protected]> ]
Sent: Friday, August 10, 2001 10:30 AM
To: JDO-ListServ
Subject: RE: Load of query results
Could you please clarify exactly what you mean by an 'automatic load' of
query results? And in what way is the 'resource manager' (db?) accessed
for each query object returned?
When Kodo issues a query it selects all fields of the expected result
class that lie in the primary table used by that type (with the
exception of LOB fields). Thus the objects returned by the query
already have all of their data filled in that is accessible with a
single SELECT. Additional queries are made only if you access fields of
an object that do not lie in its primary table, such as Collections,
arrays, Maps, and relations to other persistent objects.
Is that what you meant?
Whatever you mean, our goal is to implement the entire JDO
specification, including as much optional behavior as is useful to our
customers.
I'll have someone from marketing get back to you with the GA schedule.
-----Original Message-----
From: Patrice Thiebaud
To: [email protected]
Sent: 8/10/01 5:08 AM
Subject: Load of query results
Hi,
The final JDO specification is likely to support the need for having an
automatic load of query results, probably through a property (thus
answering a performance optimization need, as it is better to avoid
futher
access to the resource manager for each object used).
Will the GA version provide this feature ?
By the way, is it possible to know the scheduled date for GA ?
Thanks in advance.
BEA Systems : How Business Becomes E-Business
Patrice Thiebaud - Presales Senior Consultant
BEA Systems - France
Tour Manhattan
6 place de l'Iris
92095 PARIS La D__fense C__dex
Tel: 33 1 41 45 70 27 Mobile: 06 08 05 95 95
BEA Systems : How Business Becomes E-Business
Patrice Thiebaud - Presales Senior Consultant
BEA Systems - France
Tour Manhattan
6 place de l'Iris
92095 PARIS La D__fense C__dex
Tel: 33 1 41 45 70 27 Mobile: 06 08 05 95 95

I have tested Oracle only. Teradata has a "sample" command and I would hope that Web Intelligence would use that. The Oracle method involves the dbms_random package to assign each row a random number, then the query is sorted by that number and a limit is placed for the sample size.
I have not written about this on my blog yet, but it could be an interesting topic. Thanks for the suggestion.

Getting query results from a PL/SQL procedure

Hi! So, I’m a little stumped and I can’t seem to find the answer to what I believe is probably a simple question…
So, here goes… I have a big ol’ union query that I use to create a report on a page, it’s about 25k – not over the 32k limit, but fails to be able to compile every time (I always get a 400 – Bad Request error). I’m not sure why this is happening, but I can remove a union statement and it compiles just fine – so it has something to do with the size of the query. ANYWAY – I’ve resolved that I should put this bad boy into the database as a stored procedure and just call it from Apex, my problem is I can’t figure out quite how to do this with variables, etc.…
Instead of giving you my whole big query, I’ll use the emp table as the concept is the same:
Say we have a query that creates a report on a page:
select empno, ename, job, mgr, hiredate, sal, comm, deptno
from emp
where job = :P_JOB
and hiredate >= :P_HIREDATE;
How would I take this query, create it as a stored procedure on the db, pass the variables from Apex and return the query result set from the stored proc as a report?
I really appreciate any help on this!
Best,
Gilcrest

Hi Gilcrest,
You should create the query as a View and use the view name and the WHERE clause in the report's sql source.
Andy

How can I get Numbers to return the first row in a group of VLOOKUP query results instead of last one?

I'm trying to query from one table (call it Table1) a batch of rows in another table (Table2) using VLOOKUP on a date specified in the first table (Table1). My problem is it's returning the last incident in Table2 of the requested date instead of the first incident. This really breaks the OFFSET scheme I'd like to use to collect the rest of the items for that date. Is there some way to compel VLOOKUP to return the first row of query results, not the last?
NOTE: I see I've asked this before, but forgot to go back and look at responses given. It's been a while and I've limped along until now with the way things were. I'm actually trying to delete this questions, so if you see it, ignore it. I suppose if someone can tell me real quick how to delete a stupid question, that might be helpful.

you cannot delete a post yourself. You can flag the post an request a moderator remove.

cache-query-results question

Similar Messages

Maybe you are looking for