Skip to main content

Spring cleaning your APEX instance

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). 
1 comment

Popular posts from this blog

Showing a success message after closing a modal dialog

APEX 5 comes with Modal Dialogs out of the box. Very neat. Especially for adding and changing data. And to minimise the number of time a user has to click, it could be useful to add a "Close Dialog" process after the actual data processing. When the data processing fails, the Dialog stays on top showing the error. When data processing runs fine, the Dialog is closed ... without any confirmation. And this might be scary for a shaky user.

So how can we provide the user some feedback? On Page 4 of the Sample Dialog Application you can see one solution: up on a Dialog Closed Event on the parent page it does a redirect to refresh the parent page appending the success message of the "Close Dialog" process. This has two drawbacks. First, it probably refreshes more than necessary. And second, if you're using multiple layers of dialogs (dialogs that open other dialogs) the message appears in the "parent dialog".
As an alternative you could follow these steps: 1…

It's happening again ... running for the ODTUG Board of Directors 😉

For the third time in a row I'll be running for ODTUG's Board of Directors. But after ending as a runner up twice, I am sure I'm going to make it this time! But not without your help!

My campaign statement this year is:
I have been attending and presenting at Kscope conferences since 2007. This not only resulted in a vast amount of knowledge, but also - and even more important - a huge number of friends from all over the globe.  I want to see ODTUG grow and spread this community feeling even more! 
My experience as an attendee, presenter and content lead has provided the basic foundation to be a director. Next to that, my personality and (global) network will be beneficial to the whole board and organization. 
Since March I have served on the Board of Directors in a limited term for a Director who stepped down due to a career change. This has allowed me to have unique insight of all the things that are going on in and around the ODTUG organization. As the train was already ro…

APEX 5 New Static File Features

In APEX 4 you could upload files - like CSS files, JavaScript files, Images and whatever else you like - into the APEX Repository. When you navigate to Shared Components, there is a Files section that offers three different options:
CSS Files are always uploaded (and changed !) for the whole Workspace. For Images and Static Files (usually JavaScript) you could choose whether they should be available for the whole Workspace or for a specific Application only. And if you had a lot of files - e.g. a lot of images - then you had to go through the upload process one-by-one. But that's usually a one time only thing. If you make changes to the CSS and JavaScript files - and that's a continuous process in development - then you had to delete the existing file and upload the new one. Over and over again. And meanwhile fighting the cache of the webserver and your browser.  And another irritating issue: You couldn't use relative references in your CSS or JavaScript files as they just…