Snippets and Thoughts of One Oracle Developer

S Sometimes, when I'm working on a new package, it's difficult to keep the specification updated to reflect changes in arguments. Adding new procedures becomes tedious, and when I change the formatting, it's time-consuming to update the specification accordingly. When I reformat a legacy package, I usually copy the whole body into the specification and keep only the declarations. But that also takes some effort. So I created this nifty script, which generates a specification from your package body. It keeps everything that exists in your current package spec before the first procedure or function (like constants, exceptions, comments...). Everything else is replaced. It does not support forward declarations, and your private procedures will get exposed (which is a good thing, because you should be using the ACCESSIBLE BY clause instead). Here is the script: DECLARE in_package_name CONSTANT VARCHAR2(30) := '&PACKAGE_NAME.'; -- v_head...

S Sometimes, you have to modify all triggers, if you were for example using SYSTIMESTAMP and now SYSDATE is enough. To modify all triggers by hand might be a lot of work (it is not just about modifing, you also have to compile all of them in the database). So let's write a script for that (replace LOCALTIMESTAMP with SYSDATE in all triggers), but you can easily modify it to whatever you need to change: DECLARE v_query VARCHAR2(32767); v_modified BOOLEAN; BEGIN FOR c IN ( SELECT t.name, ROWNUM AS r#, d.referenced_name FROM user_source t JOIN user_dependencies d ON d.name = t.name AND d.name LIKE '%' AND d.type = t.type AND d.type = 'TRIGGER' AND d.referenced_type = 'TABLE' WHERE t.line = 1 ORDER BY 1 ) LOOP v_query :=...

A Another issue I faced on each project is data type inconsistency. In this older article I mentioned how to fix data types mismatches on keys . Today, I show you a script, which fix it for you (based on a column name match). Let's explore this issue on the audit columns (who created or updated the row and when). To check the audit columns for user: SELECT c.column_name, c.data_type, c.char_used, c.data_length, c.nullable, c.data_default_vc, COUNT(*) AS count_tables FROM user_tab_cols c JOIN user_tables t ON t.table_name = c.table_name WHERE c.table_name LIKE '%' AND c.column_name LIKE 'CREATED_BY' GROUP BY c.column_name, c.data_type, c.char_used, c.data_length, c.nullable, c.data_default_vc ORDER BY 1, 2, 3, 4; Let's check the audit column for date. This gets more trickier, because we might not have consistent names. To keep the changes low, I am not changing the column names, just ...

I In this article, I will show you a script that deletes all rows from all tables for a specific tenant. You don't need to be familiar with your schema or manually piece together queries to perform the deletion. You can also easily modify this script to delete any entity, not just a tenant. There are several ways to achieve this, and I will show you two of them: To find (even compound) references to a specific table, you can use this query: SET DEFINE ON SELECT r.table_name, c.column_name, r.constraint_name, k.column_name AS primary_column FROM user_constraints r JOIN user_constraints p ON p.constraint_name = r.r_constraint_name AND p.constraint_type IN ('P', 'U') JOIN user_cons_columns c ON c.constraint_name = r.constraint_name AND c.table_name = r.table_name AND c.column_name NOT IN ('TENANT_ID') -- we should match on position JOIN user_constraints s ON s.table_name = r...

T The space on free OCI can sometimes be a bit limiting, especially if you're using table partitions. Even an empty partition consumes 8 MB, and if you have partitions per tenant in every table — and over 100 tables — it can quickly grow with each new tenant. So here is the script which helps you to remove empty partitions and also rename the partitions so you can easily identify specific tenants: DECLARE in_table_like CONSTANT VARCHAR2(128) := '%'; in_partition_prefix CONSTANT VARCHAR2(128) := '__P'; -- v_found PLS_INTEGER; v_high_value VARCHAR2(4000); v_new_name VARCHAR2(128); BEGIN FOR c IN ( SELECT t.table_name, t.partition_name, t.high_value FROM user_tab_partitions t WHERE t.table_name LIKE in_table_like ORDER BY 1, 2 ) LOOP v_found := NULL; v_high_value := c.high_value; -- LONG convers...

T There is another new exam available at Oracle, the Oracle APEX Cloud Developer Professional (1Z0-771) with a free course to get you there at Mylearn . Till March 15th you can get the course and the certification for free! "An Oracle APEX Cloud Developer Professional certification signifies practical expertise and in-depth knowledge in designing, developing, and deploying Oracle APEX applications. Professionals with this certification are skilled in creating modern, secure, scalable, AI-powered enterprise applications equipped with world-class features, deployable both in the cloud and on-premises. This certification assesses a candidate’s comprehensive understanding of low-code application development using Oracle APEX. It also validates their ability to utilize APEX’s advanced capabilities, including Generative AI, to deliver innovative solutions tailored to diverse business requirements. Earning this certification demonstrates proficiency in building robust, user-focused...

T There is a new exam available at Oracle, the Oracle AI Vector Search Professional (1Z0-184-25) . And since the certification is not listed under the Cloud certifications, it wont expire. Correction, it does expire in 2 years. "The Oracle AI Vector Search Professional Certification is designed for Oracle DBAs, AI engineers, and cloud developers to unlock the potential of Oracle Database 23ai to build AI-driven applications. The target candidate for this certification should have basic familiarity in Python and AI/ML concepts. This certification bridges the gap between traditional database management and cutting-edge AI technologies by focusing on leveraging Oracle Database 23ai capabilities for handling vector data and enabling semantic and similarity searches. Through in-depth training, candidates will master techniques like vector data storage, indexing, and generating and storing embeddings, alongside advanced applications such as building Retrieval-Augmented Generation (...

A A year ago I have shared a tip how to use the same mechanism for closing modal dialogs . Today, I would like to share few more tips about levaraging the Global page. When you have a button on page and the action behind is a bit slow or if you have users who are constantly double clicking on everything, you might want to disable clicked button. You can easily fix this with a simple dynamic action. But instead of repeating this DA on each button, you can define it on the Global page. The trick is to use the jQuery selector and CSS class on each of these buttons. So go to your Global page. Create DA called SUBMIT_AND_DISABLE_BUTTON on Click event. Set Selection Type to jQuery Selector Set value to "button.SUBMIT_DISABLE" Switch the default true action to Execute JavaScript code Define the action code: var button_id = this.triggeringElement.getAttribute('id'); console.log('SUBMIT_AND_DISABLE_BUTTON:', button_id, this); docum...

T Today, I will show you how to easily check if your authorization schemes set on pages match the schemes set in the navigation. In my custom navigation (including the multicolumn navigation ), I don't have to set it in two places (which is never a good idea). My navigation gets the schemes from the pages. But the default APEX navigation is not like that. That causes a lot of confusion to users when they see a page in navigation, but can't access it. Or when they have some hidden pages, and they are missing the navigation links. Fortunately, if you combine few APEX views, you can find out: SELECT p.application_id, e.list_name, p.page_id, p.page_name, --p.page_alias, --p.page_group, --p.page_mode, p.authorization_scheme AS auth_scheme_page, e.authorization_scheme AS auth_scheme_nav, e.entry_text, e.entry_target -- FROM apex_application_pages p LEFT JOIN apex_application_lists l ON l.application_id = p.application_...