Skip to main content

Is the Function Result Cache operative on my database?

At a very fine RMOUG Training Days 2015 conference this week (about which I will post later...soon...promise!), an attendee complained that:

1. He'd learned about the function result cache and was really excited about it.
2. Spent two days trying to figure out why it wasn't working.
3. Then discovered that the feature is only enabled for Enterprise Edition.

He wondered if there was a way to have determined this from the start, and saved himself a couple of frustrating days.

So, first of all, if you want to quickly determine if this feature is working, run the following script:

/* Does the function result cache work in my database? */

 CREATE OR REPLACE FUNCTION frc_test
   RETURN VARCHAR2 result_cache
IS
BEGIN
   dbms_output.put_line ('Ran FRC_TEST');

    RETURN 'Return Value';

 END;
/
BEGIN
   dbms_output.put_line (frc_test());
   dbms_output.put_line (frc_test());

 END;
/

If you see this:

Ran FRC_TEST
Return Value
Return Value

then the result cache feature is enabled and working.

If you see this:

Ran FRC_TEST
Return Value
Ran FRC_TEST
Return Value

then you know that it is not. Alternatively, if you have EXECUTE authority on the DBMS_RESULT_CACHE package, you can simply run:

BEGIN
   dbms_output.put_line (dbms_result_cache.status);
END;
/

"ENABLED" means, well, you get the idea.

So: are you running Enterprise Edition? Find out with this query:

select * from v$version;
Beyond that, you can check for availability of specific features of the Oracle Database 11g release here. For Oracle Database 12c, check out this page.

Comments

  1. jaramillAugust 30, 2015 at 9:25 PM

    It is enabled on Personal Oracle Database 12c Release 12.1.0.1.0 - 64bit Production

    ReplyDelete

Post a Comment

Popular posts from this blog

Why DBMS_OUTPUT.PUT_LINE should not be in your application code

A database developer recently came across my  Bulletproof PL/SQL  presentation, which includes this slide. That first item in the list caught his attention: Never put calls to DBMS_OUTPUT.PUT_LINE in your application code. So he sent me an email asking why I would say that. Well, I suppose that is the problem with publishing slide decks. All the explanatory verbiage is missing. I suppose maybe I should do a video. :-) But in the meantime, allow me to explain. First, what does DBMS_OUTPUT.PUT_LINE do? It writes text out to a buffer, and when your current PL/SQL block terminates, the buffer is displayed on your screen. [Note: there can be more to it than that. For example, you could in your own code call DBMS_OUTPUT.GET_LINE(S) to get the contents of the buffer and do something with it, but I will keep things simple right now.] Second, if I am telling you not to use this built-in, how could text from your program be displayed on your screen? Not without a lot o...
4 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch, ...
4 comments
Read more

PL/SQL 101: Three ways to get error message/stack in PL/SQL

The PL/SQL Challenge quiz for 10 September - 16 September 2016 explored the different ways you can obtain the error message / stack in PL/SQL. Note: an error stack is a sequence of multiple error messages that can occur when an exception is propagated and re-raised through several layers of nested blocks. The three ways are: SQLERRM - The original, traditional and (oddly enough) not currently recommended function to get the current error message. Not recommended because the next two options avoid a problem which you are unlikely  to run into: the error stack will be truncated at 512 bytes, and you might lose some error information. DBMS_UTILITY.FORMAT_ERROR_STACK - Returns the error message / stack, and will not truncate your string like SQLERRM will. UTL_CALL_STACK API - Added in Oracle Database 12c, the UTL_CALL_STACK package offers a comprehensive API into the execution call stack, the error stack and the error backtrace.  Note: check out this LiveSQL script if...
5 comments
Read more