Ted Struik - Oracle

Mnemonics for Oracle SQL, PL/SQL & Apex

A collection of notes, ideas, solutions, bug fixes, best practices, thoughts and reminders, related to Oracle SQL, PL/SQL & Application Express (Apex).
I couldn't resist putting in some hobbies as well.
Navigate using the menu, the Site Map, the Search Page, or the Search field in the navigation bar.

IT became a hobby of mine around 1980, and turned into a profession in 1994. Oracle came into view around 2000.
Over the years I have worked on various Oracle related projects all over the world, and am currently employed by Itium.
Contact me at .

Page ID	Page Name	Last Update
1100	Hobbies - Motorcycles - MotoGP	2024-08-31
1151	Hobbies - Motorcycles - '18 Suzuki GSX-S 1000 F	2024-08-31
1107	Apex - General - Database Dependencies	2024-08-28
1140	Apex - Interactive Grid - ERR-1002	2024-08-13
1182	Apex - General - Form Regions	2024-08-08
1149	(PL)SQL - Source Code Search (SQL)	2024-08-01
1135	(PL)SQL - Source Code Search (PL/SQL)	2024-08-01
1075	(PL)SQL - Apex_string.split in SQL	2024-07-31
1002	Apex - Reports - Checkboxes	2024-07-31
1077	DBA - Constraints	2024-07-25

1 - 10 of 172

2024-06-20: I updated the site to Apex 24.1 and that went just fine - up until the point I found a new feature/bug and I had to roll back the whole thing.
Turns out that in Apex 24.1 the Application Export has a new feature "Audit Information":
Specify the Audit Information to include in the export file. Audit information includes the Created By User, Created On Date, Changed By User and Changed On Date.
- By default, no audit information is included.
- Choose Names and Dates to include all audit information.
- Choose Dates Only to include date information and exclude user details.

Because by default "no audit information is included", it is also not included in the backups I make using SQLcl. And as far as I can tell, SQLcl does not have an option (yet) to overrule this option. I need the "Last Update" date, both for use on Page 1 of this site, and also in the Builder for my own reference.
So for now I have created a table and a database job to make a backup of these dates, just in case this bug is never fixed (or returns in the future). Not very elegant (and it will still mean the Builder shows wrong dates after importing a SQLcl export) but at least it works for Page 1.