About Performing a Fast Patch Upgrade
Consider performing a fast patch upgrade when you have large databases and you have both critical uptime requirements and short maintenance windows. During the fast patch upgrade, the static checkpoint operation performed at database stop is optional, and the shared memory segment is preserved after the subdaemon disconnects. When the database is started, the checkpoint operation is not performed and a new subdaemon connects to this preserved shared memory segment. This reduces the time it takes to upgrade an instance, especially if your databases are large, by skipping both the load of the database into memory operation and the checkpoint operation.
To use a fast patch upgrade, the ramPolicy
for the database must be set to enduring
. This keeps the database image in memory after the subdaemon disconnects. See Specifying a RAM Policy in the Oracle TimesTen In-Memory Database Operations
Guide for information on setting a RAM policy.
The size of the TimesTen shared memory segment must remain the same before and after the fast patch upgrade. The TimesTen ttShmSize
utility is provided to calculate the size of the shared memory segment. Run this utility before you upgrade the instance and then run it again after you upgrade the instance to ensure the size of the shared memory segment has not changed after the upgrade. In addition, ensure you do not modify the PermSize
, the TempSize
, the LogBufMB
, and the Connections
connection attributes after the upgrade. These attributes affect the size of the shared memory segment.
See ttShmSize and Connection Attributes in the Oracle TimesTen In-Memory Database
Reference for information on the ttShmSize
utility and the TimesTen connection attributes.
Download and Create the New Installation
To upgrade to a new patch release of TimesTen, you must first create the new installation.
Prepare to Detach the Subdaemon from the Shared Memory Segment
Perform these operations on the instance created with the current release of TimesTen (22.1.1.25.0
, in this example).
Detach the Subdaemon from the Shared Memory Segment
Perform these steps to disconnect the subdaemon from the shared memory segment.