Patching Oracle True Cache Using Oracle FPP

Use Oracle Fleet Patching and Provisioning (Oracle FPP) to patch Oracle True Cache by moving the Oracle True Cache to a patched Oracle home and restarting Oracle True Cache from that Oracle home.

You can patch Oracle True Cache deployments only on a standalone node.

1. Provision a patched database working copy, on the Oracle True Cache node, that will be used as the destination Oracle home.

   rhpctl add workingcopy -workingcopy workingcopy_name -image image_name 
     -node true_cache_node -path path_to_software_home -user oracle -sudouser sudo_username 
     -sudopath /bin/sudo -oraclebase Oracle_base_path < /tmp/sudopwd.txt

   Note:

   You can use -root or credentials instead of password redirection, depending on your environment and security requirements.
2. Move the Oracle True Cache database from the source working copy to the patched working copy.

   rhpctl move database -dbname true_cache_db_name -sourcewc source_working_copy 
     -patchedwc destination_working_copy -sudouser sudo_username -sudopath /bin/sudo 
     -oraclebase Oracle_base_path < /tmp/sudopwd.txt

   This operation stops the database and then restarts it as part of the move.
3. Verify that Oracle True Cache is running from the patched Oracle home by using one of the following methods:
   1. On the target node, check /etc/oratab and confirm that it reflects the patched Oracle home.

      tcdb:<patched Oracle home>:N

   2. Verify the running binary path for the database process.
      • Get the process ID for the database PMON process:

        ps -ef | grep pmon

      • Confirm the Oracle binary path used by the running process.

        ls -l /proc/<PID>/exe

        Note:

        Replace <PID> with the process ID identified from the pmon output.

   Note:

   The resolved path should correspond to the patched Oracle home. If it points to the old home, then review the move operation output and the /etc/oratab entry.

After you restart Oracle True Cache, cache warm-up might be required, depending on your workload and caching objectives. Warm-up does not run by default during patching because it can be time-consuming and depends on table size and access patterns.