Apex: upgrading Apex to 18.2, Ords to 18.3

Apex 18.2 and Ords 18.3 are now available.

To upgrade these versions in place, for example on an OCI DBsystem, from respectively Apex 18.1 and Ords 18.2:

#1 Download and unzip apex 18.3 in the n/u01/app/oracle/product/apex/18.3


#2 Upgrade apex

cd /u01/app/oracle/product/apex/18.3
sqlplus / as sysdba <<EOF


#3 Change the images symbolic links (quite convenient to handle periodic upgrades)

cd /u01/app/oracle/product/apex/latest
rm images
ln -s ../18.3/images images


#4 Download and unzip the ORDS zip file in the newly created directory



#5 Upgrade the params files

cd /u01/app/oracle/product/ords/18.3/params
cp /u01/app/oracle/product/ords/18.2/params/* .


#6 Upgrade the config directory

cd /u01/app/oracle/product/ords/18.3
java -jar ords.war configdir /u01/app/oracle/product/ords/config


#7 Upgrade the ORDS schema

cd /u01/app/oracle/product/ords/18.3
java -jar ords.war

The end of the process should start the ords server


OCI: ORDS 18.x redirection and logging

The tips below are applicable for ORDS 18.x standalone, for example after a deployment on an OCI dbsystem.

#1 To configure the access.log, update the file standalone.properties available from the /u01/app/oracle/product/ords/config/ords/standalone/standalone.properties configuration file to add the following property


Where /tmp/ords is going to be a directory that will hold the daily logfiles. Then restart the ords standalone process.


#2 To implement some redirect for the internal ords port to be accessible from the standard https port 443, instead of the native port 8443, create the file https (for example) in /etc/xinetd.d, with the following content:

service jetty-https
disable = no
socket_type = stream
protocol = tcp
wait = no
redirect = localhost 8443
port = 443
user = nobody

Then restart the xinetd.d service

service xinetd restart

Check that the firewall and the ingress rules allow inbound access to 443.

APEX: ORA-02291: integrity constraint (APEX_180100.WWV_FLOW_FND_GU_INT_G_FK) violated – parent key not found

Getting the error ORA-02291: integrity constraint (APEX_180100.WWV_FLOW_FND_GU_INT_G_FK) violated – parent key not found while importing an apex workspace.

Issue has to do with users groups that are not part of the import. This is the bug 16781538, still unresolved with 18.1.

Solution is to edit the import file, locate the users that belong to group and change in the www_flow_fnd_user_api. create_fnd_user call(s) that create issues, for example:

  p_group_ids => '1860188076423573:1860279868423578:1860329781423578:'


  p_group_ids => ''