This section summarizes the new features of Oracle TimesTen In-Memory Database Release 18.1 that are documented in this guide. It provides links to more information.
There is support for automated upgrades of TimesTen. See Chapter 10, "Performing Upgrades" for more information.
In most cases, the Operator can recover TimesTen if both databases in an active standby pair fail. See "Understanding the BothDown state" for information.
In some cases, when the Operator is unable to automatically fix problems with TimesTen, it puts the associated TimesTenClassic object into the ManualInterventionRequired state. The Operator takes no further action on the object. This enables you to manually fix TimesTen. You can later request that the Operator resume management of TimesTen. See:
"Understanding the ManualInterventionRequired state" for an overview.
"Bringing up one database" for an example.
You can suspend the management of your TimesTenClassic object by the Operator. See "Suspending the management of a TimesTenClassic object" for details.
You can run direct mode applications in their own containers inside of the Pods in your TimesTenClassic deployment. See "Using direct mode applications" for more information.
There is support for these CRD syntax elements. See "TimesTenClassicSpecSpec" for more information.
agentGetTimeout
agentPostTimeout
agentTCPTimeout
agentTLSTimeout
bothDownBehavior
daemonLogSidecar
imagePullPolicy
imageUpgradeStrategy
logStorageSelector
reexamine
repCreateStatement
repPort
repReturnServiceAttribute
repStoreAttribute
stopManaging
storageSelector
upgradeDownPodTimeout
waitingForActiveTimeout
There is support for the awtBehindMb field in TimesTenClassicStatus of the TimesTenClassic object type. See "TimesTenClassicStatus" for information.
It is possible to use the Operator in an environment where nothing is allowed to run as root. See Appendix C, "Run Containers as Non-Root" for information.
You can configure and use TimesTen Cache. See Chapter 7, "Working with TimesTen Cache" for details. In addition, there is a complete example of using TimesTen Cache in your Kubernetes environment. See Appendix B, "TimesTen Cache Example" for information.
You can configure Transport Layer Security (TLS) for replication and for Client/Server. See Chapter 8, "Using Encryption for Data Transmission" for more information.
You can upgrade the Operator and the TimesTen full distribution to a new release. See Chapter 10, "Performing Upgrades" for details.
There is support for these metadata files:
You can modify TimesTen connection attributes after you create your TimesTenClassic object. See "Modify TimesTen connection attributes" for details.
If you are using TimesTen Cache, you can specify whether the metadata in the Oracle Database should be cleaned up when the TimesTenClassic object is deleted. See the cacheCleanup entry in the Table 11-2, "TimesTenClassicSpecSpec" and see "Cleaning up the cache metadata on the Oracle Database" for information.
You can specify resources requirements for the tt and the daemonlog containers. See "Resources specification for the tt and the daemonlog containers" for details.
There is support for the pollingInterval and the unreachableTimeout CRD syntax elements. See the pollingInterval and the unreachableTimeout entries in Table 11-3, "TimesTenClassicSpecSpec" for information.
The Operator keeps tracks of the individual health of each Pod in the TimesTenClassic active standby pair object. See "Monitoring the health of each pod in the active standby pair" for details.