Introduction
Once you have a TimesTen 18.1 Installation, you can then create an instance.
- An installation is a read only copy of the software from the distribution ZIP file.
- An instance is created via the ttInstanceCreate utility:
- An instance may refer to the running TimesTen daemons
- or the read/write configuration files used by the TimesTen daemons
Configuring shared memory for a TimesTen instance
Unless you have a very small TimesTen Database, you will need to configure the kernel shared memory.
Creating an Instance
It is a good idea to run the ttInstallationCheck utility to verify that the files and permissions are OK before creating an instance. eg
$./ttInstallationCheck
This installation has been verified
The ttInstanceCreate utility can have parameters pass on the command-line,
$./ttInstanceCreate -h
ttInstanceCreate [-name <name>] [-location <path>] [-daemonport <port>] [-csport <port>]
[-tnsadmin <path>] [-serverhost <host>] [-clientonly] [-grid] [-start] [-force] [-batch [<filename>]]
[-record <filename>] [-help] [-verbose]
-name Specifies the target instance name
-location Specifies the target instance directory
-daemonport Specifies the daemon port number
-csport Specifies the server port number
-tnsadmin Specifies a value for TNS_ADMIN
-serverhost Specifies the server hostname (for client DSN’s)
-grid Enable grid mode
-clientonly Install a client instance of TimesTen
-start Start the daemon after instance installation
-force Remove any existing instance (same location) without confirmation
-batch Install TimesTen without having to respond to prompts
If filename is specified, read from the file
-record Install TimesTen and record response to prompts
-help Display this help message
-verbose Display extra instance installation information
or, be run interactively:
./ttInstanceCreate
NOTE: Each TimesTen instance is identified by a unique name.
The instance name must be a non-null alphanumeric string, not longer
than 255 characters.
Please choose an instance name for this installation? [ tt181 ]
Instance name will be ‘tt181’.
Is this correct? [ yes ]
Where would you like to install the tt181 instance of TimesTen? [ /home/dhood ] /scratch/dhood
Creating instance in /scratch/dhood/tt181 …
INFO: Mapping files from the installation to /scratch/dhood/tt181/install
NOTE: If you are configuring TimesTen for use with Oracle Clusterware, the
daemon port number must be the same across all TimesTen installations
managed within the same Oracle Clusterware cluster.
NOTE: All installations that replicate to each other must use the same daemon
port number that is set at installation time. The daemon port number can
be verified by running ‘ttVersion’.
The default port number is 6624.
Do you want to use the default port number for the TimesTen daemon? [ yes ]
The daemon will run on the default port number (6624).
In order to use the ‘TimesTen Application-Tier Database Cache’ feature in any databases
created within this installation, you must set a value for the TNS_ADMIN
environment variable. It can be left blank, and a value can be supplied later
using <install_dir>/bin/ttInstanceModify.
Please enter a value for TNS_ADMIN (s=skip)? [ ] s
What is the TCP/IP port number that you want the TimesTen Server to listen on? [ 6625 ]
Would you like to use TimesTen Replication with Oracle Clusterware? [ no ]
NOTE: The TimesTen daemon startup/shutdown scripts have not been installed.
The startup script is located here :
‘/scratch/dhood/tt181/startup/tt_tt181’
Run the ‘setuproot’ script :
/scratch/dhood/tt181/bin/setuproot -install
This will move the TimesTen startup script into its appropriate location.
The 18.1 Release Notes are located here :
‘/scratch/dhood/TimesTen/tt18.1.2.1.0/README.html’
Starting the daemon …
TimesTen Daemon (PID: 13841, port: 6624) startup OK.
You can verify that the instance is running by checking for the TimesTen main daemon process:
$ ps -ef | grep timestend
dhood 13841 1 0 20:23 ? 00:00:00 /scratch/dhood/tt181/install/bin/timestend -initfd 13 -minsubs 2
dhood 14162 12694 0 20:32 pts/0 00:00:00
Disclaimer: These are my personal thoughts and do not represent Oracle’s official viewpoint in any way, shape, or form.
