Skip to main content

Spring cleaning your APEX instance

By
While I was working on my (and Marco's) presentation for Kscope11 about the XFILES, I discovered some trash under the XML DB carpet of my database. If I executed the statement 
select * from RESOURCE_VIEW
where under_path( res, 1, '/')=1
I got (amongst others)
So apart from the standard "images" directory, there where three more... 
When you upgrade an APEX instance the old images directory is renamed (a datetime-stamp is added) and a new one is created - just in case you need to fall back on your old stuff. If you use a webserver the presence of that directory is easy to see - and to delete. 
When using the Embedded PL/SQL Gateway (EPG) the same procedure is applied, but now you probably wont notice, until you look for it...
To get rid of the old stuff run (of course use your own images directory instead of mine):
begin
  dbms_xdb.deleteresource( '/images_201102071025'
                         , dbms_xdb.delete_recursive);
  commit;
end;
After running that PL/SQL block three times - for all three old images directory, the number of records returned from RESOURCE_VIEW is dramatically decreased : from 42,349 to 12,268. Doing this clean up  saved me some space and improved performance (on certain queries that is). 
Labels:
Location: Arnhem, The Netherlands

Comments

Marco Gralike said…
Funny. I saw that rename upgrade APEX stuff a while ago. I didn't know that it was that much. Wow! It proves once again that pictures can say a lot more than...

;-)
8:58 pm
Post a Comment

Popular posts from this blog

How to create neatly formatted Excel documents using PL/SQL?

By
If there is a requirement to produce output from an application into Excel, you would probably create a CSV (Comma Separated File) with the data and start Excel to show the data - at least that's what I did...until now. The drawback of this solution is that you could only produce data and no nice layout. But Excel is also capable of opening HTML-files and using this you could create Excel files with data and magnificent layout! Let me give an example: 1. Create a procedure to show the data in formatted in an HTML table. CREATE OR REPLACE PROCEDURE display_emp_list IS v_emp_count NUMBER(5); v_empno NUMBER(8); v_ename VARCHAR2(50); v_job emp.job%TYPE; v_sal emp.sal%TYPE; v_bg_color VARCHAR2(10) := ''; CURSOR c_emp IS SELECT empno, initcap(ename), job, sal FROM emp ORDER BY ename; BEGIN SELECT COUNT(*) INTO v_emp_count FROM emp; owa_util.mime_header('application/ms-excel', FALSE); htp.p('Content...
21 comments
Read more

Refresh selected row(s) in an Interactive Grid

By
In my previous post I blogged about pushing changed rows from the dabatase into an Interactive Grid . The use case I'll cover right here is probably more common - and therefore more useful! Until we had the IG, we showed the data in a report (Interactive or Classic). Changes to the data where made by popping up a form page, making changes, saving and refreshing the report upon closing the dialog. Or by clicking an icon / button / link in your report that makes some changes to the data (like changing a status) and ... refresh the report.  That all works fine, but the downsides are: The whole dataset is returned from the server to the client - again and again. And if your pagination size is large, that does lead to more and more network traffic, more interpretation by the browser and more waiting time for the end user. The "current record" might be out of focus after the refresh, especially by larger pagination sizes, as the first rows will be shown. Or (even wors...
Post a Comment
Read more

APEX ReadOnly Pages - The easy way

By
If your Oracle APEX Application requires different types of access - full access or readonly - for different types of users, you can specify a Read Only Condition on Page level (or Region, Item, Button, etc.).  You can set an Authorization Scheme on Application level, so it'll be applied to all pages. So if you have an Authorization Scheme named 'User Can Access Page' defined by a PL/SQL function like this: return apex_authorization.user_can_access_page ( p_app_id  => :APP_ID , p_page_id => :APP_PAGE_ID , p_user    => :APP_USER );  then you can code all the logic in the database using the APEX Repository, your own tables or a combination to define whether a user has access to that page or not. But alas it is not possible to define something similar Application wide for a Read Only condition. You can specify an Authorization Scheme 'User has Read Only Access' using a similar signature as the one above and use that on each and e...
Post a Comment
Read more