The Power of the Oracle APEX Repository

I have finally translated the presentation I have done at the DOAG SIG APEX workshop into English.

Just read a blog posting by Jan from iAdvice, who had the same idea about using the dictionary views for QA checks as I also describe it in my presentation. But there are also a lot of other examples for which you can use them.

Download the presentation from Sourceforge in the Misc / Presentation section.

Hope you like it!

PS: If you have other good examples for the usage of the views, let me know.

8 thoughts on “The Power of the Oracle APEX Repository

  1. Patrick,

    Very complete overview on the possible usages of the Apex dictionary views. Nice …

    I am more reserved when it comes to direct updates on the wwv_flow_xxx tables.

    It would be interesting to have a complete API to manipulate the dictionary metadata, like Oracle Designer had/has. Maybe an extension for future releases ?!

  2. Yes an official API, at least for create would be nice enhancement.

    On the other side, compared to the data model of Designer, the APEX data model is quite simple.

    Also with an official API you are still able to destroy your applications meta data if you don’t know what you are doing. Updates are fine for me, don’t need an API, but it would be good if the steps to do it would be documented somewhere in the manual.


  3. Hi Patrick, my name is Alejandro Suarez, and i am an Apex Developer and a loyal reader of your blog!
    I have a little question for you. I am trying to use a collection in a procedure called by ajax, and it is giving my an error about the session id, and the flow id. I thought i was hopeless, but after reading you PPT: “The power of the Oracle Apex Repository” i thought maybe you could have some info to help me.


  4. Hi Alejandro,

    the best would be if you would write a posting on OTN and send me the URL in an e-mail (can be found in the blog profile). That way others can also participate from a solution.


  5. Patrick,

    Thanks for sharing the presentation. The application export file is a good reference for manipulating the APEX Repository. Also importing the application export files of Application Express itself give useful information how meta data is stored and which routines are called. Look at the following OTN Thread Programmatically adding a schema to a workspace for an example.

    With kind regards,


  6. Dietmar did a very good presentation there too. He also demonstrating how to add additional schemas to a workspace, because in XE you have by default a 1 to 1 assignment. The APIs make a lot possible.

    Hope he makes his presentation available.


  7. Thank you for translating the presentation into English. I learned some great new Apex tricks and will be putting them to good use. I particularly like the ability to query up errors encountered by users and will be sending myself a nightly summary. I also really like the quality/consistency check report idea. Thank you for the great posts.


Comments are closed.