8i | 9i | 10g | 11g | 12c | 13c | 18c | 19c | 21c | 23c | Misc | PL/SQL | SQL | RAC | WebLogic | Linux

Home » Articles » Misc » Here

Oracle Application Express (APEX) Patches (4.2, 5.0, 5.1)

From APEX 18.x onward the concept of patching has become irrelevant, as every release is effectively a full upgrade.

Upgrades affecting the first two numbers of the version (4.1 to 4.2, 4.2 to 5.0, 5.0 to 5.1) are done by doing a full installation. The installation process does the actual upgrade of the existing APEX installation. If the first two numbers of the version are not affected (4.2.5 to 4.2.6, 5.0.0 to 5.0.1, 5.1.0 to 5.1.2) you must download and apply a patch, rather than do the full installation.

I'm going to completely ignore installations in the CDB as I think these are a bad idea. APEX installations should be in non-CDB instances or entirely within the PDB in my opinion.

Related articles.

Apply Patch

Log into My Oracle Support and download the relevant patch. In this case it is the 5.1.1 patch.

Unzip it and switch to the "patch" directory.

cd /tmp
#unzip p19595896_426_Generic.zip
#unzip p21364820_501_Generic.zip
#unzip p21805060_502_Generic.zip
#unzip p22298106_503_Generic.zip
#unzip p23192730_504_Generic.zip
#unzip p25341386_511_Generic.zip
#unzip p25786300_512_Generic.zip
#unzip p26359202_513_Generic.zip
unzip p26795231_514_Generic.zip
cd patch

Log in as SYS in the non-CDB instance or in the pluggable database and run the "apxpatch.sql" script.

sqlplus / as sysdba

-- For PDB only.
ALTER SESSION SET CONTAINER=pdb1;

@apxpatch.sql

Update Images

Update the images in the relevant location. If you are using the embedded PL/SQL gateway, you will run the following command, using the correct path to the patch directory.

sqlplus / as sysdba

-- For PDB only.
ALTER SESSION SET CONTAINER=pdb1;

-- May be necessary for databases with NLS_LENGTH_SEMANTICS = CHAR set.
-- ALTER SESSION SET NLS_LENGTH_SEMANTICS = BYTE;

@apxldimg.sql /tmp/patch

If you are using the Oracle HTTP server, you will need to copy the images over your existing ones.

# Switch to the appropriate directory in the HTTP server.
cd /u01/app/oracle/middleware/FR_inst/config/OHS/ohs1/htdocs/images/apex_images

# Copy files from local path.
cp -r /tmp/patch/images/* .

# Copy files from remote path.
scp -r oracle@my-server:/home/oracle/apex/patch/images/* .

If you are running using the Oracle REST Data Services, use the relevant documentation for your release to determine how to update the images.

Post Upgrade

After applying the 5.0.0 to 5.0.1 patch I started to get warnings about images not being configured correctly, even though they were. I cleared the browser cache and this went away. Provided you did the static files configuration correctly during the APEX 5.0 installation, clearing the cache should be all you need to do.

For more information see:

Hope this helps. Regards Tim...

Back to the Top.