1 TimesTen Installation

Platform support

TimesTen Data Manager and TimesTen Client/Server are supported in these environments:

TimesTen is supported on Oracle VM guest x86 and x86-64 operating systems on Oracle Enterprise Linux 4 and 5 or Red Hat Enterprise Linux 4 and 5 systems.

JDK support

TimesTen supports the following JDKs on the specified platforms:

Client/Server configurations

A TimesTen client on any supported platform can connect to a TimesTen server on any platform where TimesTen is supported.

A TimesTen 6.0 client can connect to a 6.0 TimesTen Server of any patch level. If the -insecure-backwards-compat option is set in the ttendaemon.options file, a TimesTen 6.0 client can connect to a TimesTen 11.2.1 server.

A TimesTen 7.0 or newer client can connect to a TimesTen 6.0 or newer server, under certain configurations.

For configuration details see "Configuring TimesTen Client and Server" in the Oracle TimesTen In-Memory Database Operations Guide.

Oracle In-Memory Database Cache

Oracle In-Memory Database Cache (IMDB Cache) allows you to cache Oracle database data in TimesTen. The TimesTen installation includes Oracle Instant Client, and the following Oracle server releases are supported with this option:

• Oracle Database 10g Release 2 (Oracle 10.2.0.4.0 or above)

• Oracle Database 11g Release 1 on Windows (32-bit), Linux x86, Linux x86-64, Solaris SPARC (64-bit), AIX (PPC64), HP-UX PA-RISC (64-bit) and HP-UX Itanium

Also, see "Setting up the Oracle and TimesTen systems" in Oracle In-Memory Database Cache User's Guide.

Replication configurations

TimesTen-to-TimesTen replication is supported only between identical platforms and bit-levels.

Instance naming

The instance name is the key used to access all necessary information about that particular installation of TimesTen.

On Windows, the TimesTen installation scripts do not prompt you to supply an instance name. The instance name on Windows is tt1121_32 on 32-bit systems and tt1121_64 on 64-bit systems.

On UNIX system, by default, the instance name for this release is tt1121_32 on 32-bit systems and tt1121_64 on 64-bit systems. The default location is the TimesTen directory in the home directory of the user installing TimesTen. The instance name is case-insensitive, must be at least one alphanumeric character and up to 255 characters. The name can include underscores ( _ ) or periods (.), but no other special characters.

If you would like to install a second instance of the same TimesTen release, you must supply a unique instance name and port number. The TimesTen installation script can detect if an instance of the particular release of TimesTen already exists on the machine and prompts you for a new instance name and port number for the main TimesTen daemon.

Instance port numbers

Any time that you install more than one instance of TimesTen on the same machine, specify a unique TCP/IP port number for each TimesTen daemon during the install.

However, all TimesTen data stores that replicate to each other must use the same daemon port number, except when the -remoteDaemonPort option is specified in duplicate operations. This port number is set at install time. You can use the ttVersion utility to verify the port number of your installation of TimesTen.

On UNIX systems, the default port on which the TimesTen main daemon listens is 53384 for 32-bit installations and 53388 for 64-bit applications.

On UNIX systems, the default port on which the TimesTen Server daemon listens is 53385 for 32-bit installations and 53389 for 64-bit applications.

The port on which the TimesTen cache agent listens is determined by the operating system and cannot be configured separately.

Components available on UNIX

On UNIX, you can install the following components. In addition, the installation script prompts you to install the TimesTen Quick Start and documentation.

If you have already installed TimesTen and you would like to add or remove components, you must run the installer and select the option "Upgrade an existing instance," and then select the instance which you would like to change.

Components available on Windows

On Windows you can install one or more of the following components by checking the appropriate boxes during installation.

General UNIX requirements

In general, on UNIX systems, you must configure the following:

• The number of semaphores

• Allowable shared memory

In addition, you may need to perform the following:

• Ensure you have the latest operating system patches

• Configure your file system to allow large files

• Configure your Java environment

• Configure your Client/Server environment

• Configure network settings for replication

The following sections outline some of the changes that may need to be made on any UNIX system. In addition, some of these sections describe changes required for each specific UNIX platform on which TimesTen is supported.

• Filesystem options

• Semaphores

• Java

• Other Client/Server settings

# /usr/sbin/vxtunefs -o discovered_direct_iosz=3145728
# /usr/sbin/vxtunefs -o max_direct_iosz=3145728

set rlim_fd_max = 1080

AIX prerequisites

On AIX, before installation, modify replication to improve the performance of TimesTen on your system. The replication agent requests TCP send and receive buffers of a minimum size of 512KB. To ensure this is granted please ensure the kernel parameter sb_max is set to a minimum of 512KB. The value may be changed using the following command:

# /usr/sbin/no -p -o sb_max=524288

To query the value, use the following command:

# /usr/sbin/no -o sb_max

HP-UX prerequisites

On HP-UX, before installation, the following sections describe steps you can perform to improve the performance of TimesTen on your system:

• Semaphores

• Shared memory

• Large data stores

• Replication

# /usr/sbin/kctune

% /usr/sbin/fsadm -F fstype -o largefiles device_name

% /usr/sbin/fsadm -F hfs -o largefiles /dev/vg02/rlvol1

# /usr/bin/ndd -set /dev/tcp tcp_xmit_hiwater_lfp 524288
# /usr/bin/ndd -set /dev/tcp tcp_recv_hiwater_lfp 524288
# /usr/bin/ndd -set /dev/tcp tcp_xmit_hiwater_lnp 524288
# /usr/bin/ndd -set /dev/tcp tcp_recv_hiwater_lnp 524288
# /usr/bin/ndd -set /dev/tcp tcp_xmit_hiwater_max 524288
# /usr/bin/ndd -set /dev/tcp tcp_recv_hiwater_max 524288

Linux prerequisites

For Linux, TimesTen has been tested with Asianux 2.0 and 3.0, Red Hat Enterprise Linux 4 and 5, the MontaVista Linux Carrier Grade Edition Release 4.0 and 5.0 and SuSE LINUX Enterprise Server 10 minimal configurations. The C development tools are required if you intend to do native development on the machine.

On Linux, before installation, the following sections describe steps you can perform to improve the performance of TimesTen on your system:

• Large pages

• Semaphores

• Shared memory

• IPC Client/Server

• Replication

• IMDB Cache

echo 32 > /proc/sys/vm/nr_hugepages

cat /proc/meminfo

HugePages_Total: 16
HugePages_Free: 16
Hugepagesize: 262144 kB

# /sbin/sysctl -a

kernel.sem = 250 32000 100 128

# /sbin/sysctl -p

kernel.shmmax=2147483648

kernel.shmmax=68719476736
kernel.shmall=4194304

% /sbin/sysctl -w kernel.shmmax=2147483648

% cat /proc/sys/kernel/shmmax

% echo 2147483648 > /proc/sys/kernel/shmmax

kernel.sem = 250 32000 128 100

# /sbin/sysctl -p

net.ipv4.tcp_rmem=4096 4194304 4194304
net.ipv4.tcp_wmem=98304 4194304 4194304
net.core.rmem_default=65535
net.core.wmem_default=65535
net.core.rmem_max=4194304
net.core.wmem_max=4194304
net.ipv4.tcp_window_scaling=1

# /sbin/sysctl -p

net.ipv4.tcp_rmem=4096 4194304 4194304
net.ipv4.tcp_wmem=98304 4194304 4194304
net.core.rmem_default=262144
net.core.wmem_default=262144
net.core.rmem_max=4194304
net.core.wmem_max=4194304
net.ipv4.tcp_window_scaling=1
net.ipv4.ip_local_port_range="1024 65000"

# /sbin/sysctl -p

Solaris prerequisites

On Solaris, before installation, the following sections enable you to improve the performance of TimesTen on your system:

ryps3# modload /kernel/sys/semsys
ryps3# modload /kernel/sys/shmsys

set shmsys:shminfo_shmseg=12

set ufs:ufs_WRITES = 0

set ufs:ufs_HW = desired value

# /usr/sbin/ndd -set /dev/tcp tcp xmit_hiwat=524288
# /usr/sbin/ndd -set /dev/tcp tcp_recv_hiwat=524288

Windows requirements

To work properly, the TimesTen debug libraries depend on Visual Studio 2003, 2005 or 2008. If you intend to use debug libraries, make sure that you have first installed Visual Studio 2003, 2005 or 2008.

On Windows Vista, you must have Administrator privileges to perform certain operations, such as starting and stopping the TimesTen daemon. If User Account Control is enabled, and you are logged in as the local Administrator, then you can successfully run these operations in the usual way. However, if you are logged in as "a member of the Administrator group," then you must explicitly invoke these tasks with Windows Administrator privileges.

To start a command prompt window with Windows Administrator privileges:

1. On your Windows Vista Desktop, create a shortcut for the command prompt window. An icon for that shortcut appears on the Desktop.

2. Right click the icon for the newly created shortcut, and specify "Run as administrator."

When you open this window, the title bar reads Administrator: Command Prompt. Commands run from within this window are run with Administrator privileges.

TimesTen instance administrators and TimesTen users groups

For security, we restrict access to the TimesTen installation to members of a single operating system group, under which TimesTen is installed. We refer to this group as the TimesTen users group. Only users that are members of the TimesTen users group are allowed to perform direct driver connections to TimesTen and perform operations on TimesTen data stores. Any users connecting to a TimesTen data store through a client connection do not need to be members of the TimesTen users group. For a description of ways to connect to TimesTen, see "TimesTen connection options" in the Oracle In-Memory Database Cache Introduction.

The user that installs TimesTen is the instance administrator. The instance administrator must be a member of the TimesTen instance administrators group, and must also be a member of the TimesTen users group.

• On Windows, the TimesTen users group and the TimesTen administrators group are the same operating system group. TimesTen is always installed under the Adminstrators operating system group. Therefore, the instance administrator on a Windows installation must be a member of the Administrators group to install TimesTen. In addition, all users who perform a direct driver connection must also be a member of the Administrators group.

• On UNIX, the TimesTen instance administrators group and the TimesTen users group can be the same or different operating system groups:

  • TimesTen instance administrator group. Any user installing TimesTen must be a member of this group. This group must be granted read and write access to /etc/TimesTen, which contains information about all TimesTen instances installed on the machine.

  • TimesTen users group. The instance administrator must also be a member of this group to install TimesTen. After installation, only members of this operating system group are allowed to make direct driver connections to TimesTen and perform operations on TimesTen data stores.

  The details on how to create both operating system groups on UNIX are included in "Creating UNIX TimesTen administrator and users groups".

Directory and file permissions

When installed, read and write permissions on TimesTen files and directories is limited to only members of the TimesTen users group, unless TimesTen was installed as "world accessible." TimesTen processes use these permissions.

The following sections describe directory and file permissions for Windows and UNIX systems.

Creating UNIX TimesTen administrator and users groups

The following details the pre-installation procedures to create the required operating system groups and set the directory permissions for the UNIX TimesTen install.

• Create the TimesTen users group

• Create the TimesTen instance registry and administrators group

# setprivgrp timesten MLOCK

$ getprivgrp timesten
timesten: MLOCK

Installing TimesTen

To install TimesTen on your UNIX system, follow these steps:

1. Download TimesTen to your system. The download consists of a gzipped tar file that is named timestenrelease.platform.tar.gz, for example, timesten112110.linux86.tar.gz

2. Log in as the TimesTen instance administrator and copy the gzip file to the location from which you wish to install.

3. Unzip the installation file:

   % gunzip timestenrelease.platform.tar.gz
   

4. Extract the TimesTen files:

   % tar -xf timestenrelease.platform.tar
   

5. Change to the platform directory:

   % cd platform
   

6. Run the TimesTen setup script:

   % ./setup.sh
   

   You can run the setup script with the option -install or -uninstall (default is -install). When you use the -uninstall option, the script stops the daemon and Server if they are running and removes all files it had installed.

   Note:

   If a user installs TimesTen as root, the installer gives the following warning: "You are about to install TimesTen as root. TimesTen daemon processes run with root privileges."

   If you click OK to install as root, then the instance administrator is root, and any actions or applications that must be performed by the instance administrator must be run as root.

   The setup.sh script takes these options:

   Option	Description
   -install	Installs TimesTen.
   -uninstall	Uninstalls TimesTen
   -batch filename	Installs or uninstalls TimesTen without having to respond to prompts. If filename is specified, the installation reads all installation prompts from the file. The batch file filename is optional. However, TimesTen recommends that you create the batch file and specifically indicate the instance name of the installation. If no batch file is provided or if the batch file does not contain an instance name, TimesTen installs a default instance, using tt1121_bits for the instance name. If an instance with the same name already exists on the installation machine, the install procedure fails.
   -help	Displays the help message.
   -installDoc	Installs the Quick Start and the TimesTen documentation.
   -record filename	Installs or uninstalls TimesTen and records responses to prompts described in filename. The file can then be used as the parameter to the -batch option.
   -verbose	Displays extra installation information.

   
   

   The installation contains tar files of TimesTen components. If the setup script cannot find the tar files to extract from, it prompts you for their location.

7. Enter your response to the setup script prompts.

The setup script performs these actions (unless your answers resulted in termination of the installation process):

• Prompts you to:

  • Install a new instance

  • Upgrade an existing instance. (This option allows you to upgrade from a release previous to the 11.2.1 release.)

  • Display information about an existing instance

  • Quit the installation.

• Prompts you to choose the default instance name or choose an instance name for your TimesTen instance.

  Note:

  Each TimesTen installation is identified by a unique instance name. The instance name must at least one alphanumeric string and no longer than 255 characters.

• Prompts you to install one of the following components:

  • Client/ Server and Data Manager

  • Data Manager only

  • Client only

• Prompts you for the location of your TimesTen instance. By default installs the instance in $HOME/TimesTen. The TimesTen documentation refers to the installation directory as install_dir.

• Prompts you for the location of the TimesTen daemon home directory.

• Prompts you for the location of TimesTen daemon log files. The default is install_dir/info.

• Prompts you to specify the daemon port number. The default port number is 53384 for 32-bit installations and 53388 for 64-bit applications.

  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 the ttVersion utility.

• Prompts you to set the TimesTen users group or choose world accessibility. For more information on these options, see "Pre-Install requirements for operating system group and file permissions" for details on the TimesTen users group and file permissions. You can:

  1. Restrict access to group default group

  2. Restrict access to a different group

  3. Make the TimesTen instance world accessible (not recommended). Choose this option only if all users on this machine are trusted and you wish to disable all operating system-level access control for this installation.

• Prompts you to determine if PL/SQL should be enabled for the instance. Default answer is "yes." If not enabled at install time, PL/SQL can be enabled for the instance at a later time using the ttmodinstall utility.

  Note:

  Enabling PL/SQL increases the size of some TimesTen libraries.

• Prompts you to set the location to be supplied for the TNS_ADMIN environment variable that specifies the directory where the tnsnames.ora file can be found.

  You can leave this field blank. If you do not specify the value of the TNS_ADMIN environment variable at install time, you can set it at a later time with the ttmodinstall utility. However, before using the In-Memory Database Cache, you must set this environment variable.

• Prompts you to specify the server port number. The default port number is 53385 for 32-bit installations and 53389 for 64-bit applications. Installs the client and server components.

• Prompts you to install Quick Start and the TimesTen documentation. The TimesTen Quickstart applications can take up to 64 Mbytes of disk space. The default directory is install_dir/quickstart and install_dir/doc

• Prompts for the location of where to install the demo data store. This indicates that when you install the QuickStart, the TimesTen demo database files are installed in the DemoDataStore directory that defaults to the install_dir/info/DemoDataStore location.

• Prompts you to indicate if you want to install TimesTen replication with Oracle Clusterware. Prompts you for the path into which to install the Oracle Clusterware installation on this machine and the port number for the TimesTen Clusterware agent.

• The install checks for any nodes where the Oracle Clusterware is currently configured and prompts you to specify a node list for TimesTen replication with Oracle Clusterware.

• Removes any previous installation of this release of TimesTen if you are installing an upgrade.

• Installs the TimesTen components into the appropriate directories.

• Installs the client components.

• Starts the daemon.

4. If you want the TimesTen instance to start each time the machine is rebooted, log in as user root, and run the setuproot script as root. The setuproot script is located in the install_dir/bin directory:

5. # cd install_dir/bin
   # setuproot -install
   

The daemon writes a timestend.pid file into the directory from which the daemon was started. By default, this is install_dir/info. This file contains the daemon's process ID. When you stop the daemon, this ID is used to determine the process to terminate. When the process terminates, the timestend.pid file is removed.

Working with the TimesTen daemon and server on UNIX systems

The TimesTen main daemon (timestend) starts automatically when the operating system is booted and operates continually in the background. Application developers do not interact with timestend directly; no application code runs in the daemon and application developers do not, in general, have to be concerned with it. Application programs that use TimesTen data stores communicate with the daemon transparently by using TimesTen internal routines.

There are situations, however, when you may have to start and stop the daemon manually, using the TimesTen main daemon startup script. This section explains how to start and stop the daemon. If you have installed the TimesTen Server, it starts automatically when the TimesTen daemon is started and stops automatically when the TimesTen daemon is stopped.

To stop the daemon manually, use the utility command:

% ttDaemonAdmin -stop

To start the daemon manually, use the utility command:

% ttDaemonAdmin -start

Informational messages on UNIX systems

As the TimesTen daemon operates, it generates error, warning, informational and debug messages for TimesTen system administration and for debugging applications. At installation time, you determine whether these messages go into a file or to the syslog facility.

If messages are logged using the syslog, the LOG_USER syslog facility is used by default.

To specify the syslog facility used to log TimesTen Daemon and subdaemon messages, on a separate line of the ttendaemon.options file add:

-facility name

Possible name values are: auth, cron, daemon, local0-local7, lpr, mail, news, user, or uucp.

The syslog facility allows messages to be routed in a variety of ways, including recording them to a file. The disposition of messages is under the control of the configuration file, /etc/syslog.conf

Entries in the syslog.conf file contain two columns. The first column contains a list of the types of messages to log to a particular file. The second column contains the name of the log file. A tab appears between the message type and file name. Each entry in the syslog.conf file has the format: message_type file_name. Message types are specified in two parts:

subsystem-facility.severity-level

Depending on the configuration specified in that file, messages can be logged into various files. For the TimesTen daemon, specify the message types: user.debug, user.info, user.warn and user.err. You can also use the wildcard character * to represent the subsystem-facility. Since debug messages are ranked highest, specifying *.debug or user.debug is sufficient in preparing a file for the support or error log. In a message type list, delimit items by semi-colons. For example:

*.debug /var/adm/syslog/syslog.log
user.err; user.warn; user.info /var/adm/messages

To make changes to /etc/syslog.conf, you must have root privileges. Changes only take effect after the syslog daemon (syslogd) process is terminated (with the command kill -1) and restarted.

For further details, see your operating system's documentation for syslog.conf or syslogd for information on configuring this file.

To determine if your syslog configuration file is set up correctly, run the TimesTen ttSyslogCheck utility. Finally, once syslogd has been set up correctly, you may use the TimesTen ttDaemonLog utility to view only those messages in the system log file that TimesTen logged.

Changing the daemon port number on UNIX

Though the instance registry enforces TCP/IP port uniqueness for TimesTen instances, the possibility of the TimesTen main daemon port conflicting with ports used by non-TimesTen applications always exists.

The ttmodinstall utility allows the instance administrator to change the port number on which the main TimesTen daemon listens. If you have not stopped the TimesTen daemon before using ttmodinstall, the utility stops the daemon before changing the port number. After the port change, the daemon is automatically restarted. This feature is useful if you install TimesTen and later find that the port is already in use.

The utility is run from the command line and takes the -port option with the new port number as an argument. For example:

% ttmodinstall -port 12345

See the Oracle TimesTen In-Memory Database Reference for more details on ttmodinstall.

Uninstalling TimesTen on UNIX systems

To uninstall all TimesTen components, follow these steps:

1. Log in as the TimesTen instance administrator.

2. The TimesTen setup script is in the install_dir/bin directory. Run the script with the -uninstall option in a directory outside of the installation directory, by typing:

% install_dir/bin/setup.sh -uninstall

Uninstalling the system removes all TimesTen libraries and executables and also stops and uninstalls the daemon and Server. You can execute ps to verify that all TimesTen processes have terminated. To verify that TimesTen has been successfully uninstalled, verify that the install_dir no longer exists.

Installing TimesTen

An InstallShield program installs your TimesTen instance on Windows systems. To install TimesTen manually, run the setup.exe command:

The TimesTen installation script performs these actions:

• Prompts you for the location of the installation. By default, TimesTen is installed as C:\TimesTen\tt1121_bits.

• Prompts you to select the components that you would like to install:

  • TimesTen Data Manager

  • TimesTen Data Manager Debug Libraries

  • TimesTen Server

  • TimesTen Client

  • Optional Components

    • Timesten Quick Start

    • TimesTen Documentation

  For more information, see "Components available on Windows".

• Prompts for the location to install the demo data store. This indicates that when you install the QuickStart, the TimesTen demo database files are installed in the DemoDataStore directory that defaults to the C:\Documents and Settings\username\Application Data\TimesTen\.

• Prompts you to set the location to be supplied for the TNS_ADMIN environment variable that specifies the directory where the tnsnames.ora file can be found.

  You can leave this field blank. If you do not specify the value of the TNS_ADMIN environment variable at install time, you can set it at a later time with the ttmodinstall utility. However, before using the In-Memory Database Cache, you must set this environment variable.

• Prompts you to select the Program Folder for the Start Menu. Browse to choose the folder that you want for this installation either from existing folders or a new folder. The default is Timesten 11.2.1 (bits).

• Asks if you want permissions on this installation to be readable and writable by anyone who has access to the machine. This is not recommended. If disabled, permissions are restricted to users who are members of the Administrators group. See "Pre-Install requirements for operating system group and file permissions" for details on permissions and world accessibility. Choose this option only if you wish to disable all operating system-level access control for this installation.

• Prompts you to register environment variables. If selected, the installation program adds TimesTen directories to the system environment variables LIB and INCLUDE and sets other appropriate variables. If you decide not to register the environment variables at installation time, you can set the environment variables at any time after installation on a per session basis by running the script install_dir\bin\ttenv.bat. The ttenv script is described in Setting environment variables for TimesTen.

• Prompts you to select the JDK version, if any, to add to the CLASSPATH variable.

• Displays your installation selections before continuing to install TimesTen.

• Prompts you to display the release notes and launch the Quick Start Guide. For information on the Quick Start, see "TimesTen Quick Start".

Installing TimesTen in silent mode

TimesTen allows you to save installation options to a batch file that you can later use to install TimesTen without having to answer each option in a dialog box. To set up silent mode:

• From a command-line, run:

  C:> setup.exe /r
  

  With this option, TimesTen walks you through a normal setup operation. TimesTen saves your responses to the file C:\WINDOWS\setup.iss.

You can now use this file to run an installation in silent mode:

• From a command-line, run: setup.exe -s -fl response_file. For example:

  C:> setup.exe -s -f1C:\WINDOWS\setup.iss
  

  acquires the installation options from the response file. No dialog boxes appear. Some information pop-up dialogs may still appear, such as the one that informs you that the services are being started.

Verifying installation

To verify that TimesTen has been properly installed, check that the driver files are available and that the services are running:

1. Check that the TimesTen 11.2.1 Start menu shortcut has been added to the Windows Desktop Start > All Programs menu.

2. On the Windows Desktop, choose Start > Settings > Control Panel > Administrative Tools > Data Sources (ODBC). This opens the ODBC Data Source Administrator.

3. Click Drivers. Check to see that the correct drivers are installed. You should see the TimesTen Data Manager 11.2.1 driver. If you installed TimesTen Client, you should see the TimesTen Client 11.2.1 driver. Click OK.

4. On the Windows Desktop, choose Start > Settings > Control Panel > Administrative Tools > Services and check that the TimesTen Data Manager 11.2.1 service has the word "Started" in the Status field. At this time, you can also set Recovery options to attempt to restart the service after a failure.

These steps verify that the system has been installed properly.

Verifying TimesTen Client and Server installation

To verify that the Client and Server have been properly installed:

1. On the Windows Desktop, choose Start > Control Panel > Administrative Tools > Data Sources (ODBC). This opens the ODBC Data Source Administrator.

2. Click System DSN.

3. Select the sampledb_1121 sample data source and click Configure.

   Note:

   The sampledb_1121 DSN is used for client applications that use TCP/IP communications with the TimesTen Server. The sampledbCS_1121 DSN is used for Client/Server connections.

   This opens the TimesTen Client Data Source Setup dialog.

4. Click Test TimesTen Server Connection to attempt a connection to the server.

   The ODBC Administrator attempts to connect to the TimesTen Server and display a message to let you know if it was successful. When you click this button, the TimesTen Client verifies that:

   • ODBC, Windows sockets, and the TimesTen Client are installed on the machine.

   • The TimesTen Server you have selected is defined.

   • The host machine for the TimesTen Server is running.

   • The TimesTen Server is running.

5. Click Test Data Source Connection to attempt a connection to the data source on the TimesTen Server.

   The ODBC Data Source Administrator attempts to connect to the TimesTen data source and displays a dialog to let you know if it was successful. When you click Test Data Source Connection, the TimesTen Client verifies that:

   • The data source you have chosen is defined on the server.

   • The TimesTen Client can connect to the data source.

Working with the Data Manager Service and the Server on Windows

The TimesTen Data Manager Service starts automatically when you install the TimesTen Data Manager. In addition, if you installed the TimesTen Server, it is automatically started whenever the TimesTen Data Manager service is started. You can change the startup mode for the TimesTen Data Manager to require manual startup.

To change the startup mode:

1. On the Windows desktop, choose Start > Settings > Control Panel > Administrative Tools >Services. This displays all currently available services.

2. Select TimesTen Data Manager 11.2.1.

3. Choose either Manual or Automatic from the Startup type list. Click OK.

If the TimesTen Data Manager startup mode is Manual, follow these instructions to start and stop the service:

1. On the Windows desktop, choose Start > Settings > Control Panel > Administrative Tools >Services. This displays all currently available services.

2. Select TimesTen Data Manager 11.2.1.

3. Click Start to start the service. If the service is already running, click Stop to stop the service.

Informational messages on Windows systems

TimesTen writes error messages into the tterrors.log file. This file is located in the install_dir\srv\info directory. You can use the ttDaemonLog utility to view messages logged by the TimesTen Data Manager. For a description of the system administration utilities, see "Utilities" in the Oracle TimesTen In-Memory Database Reference.

Uninstalling TimesTen on Windows systems

To uninstall TimesTen for Windows:

• On the Windows Desktop, choose Start > Control Panel > Add/Remove Programs.

To verify that removal was successful, check that:

• The TimesTen 11.2.1 Start menu shortcut has been removed from the Start > Programs menu.

• The TimesTen Data Manager 11.2.1 has been removed from the Services list.

• The TimesTen 11.2.1 drivers have been removed from the ODBC Drivers tab in the ODBC Control Panel.

Setting environment variables for TimesTen

If, after installation, you want to set the environment variables to standard TimesTen settings, use the ttenv script. This includes setting paths so that TimesTen utilities can be executed, among other things. You must invoke this script before starting TimesTen in order for any of the changes to take effect.

For UNIX platforms, use either of the following scripts depending on your shell:

install_dir/bin/ttenv.sh
install_dir/bin/ttenv.csh

For a Windows platform, use the install_dir/bin/ttenv.bat script.

install_dir\bin\ttenv.bat

Execute the following for a description of the command-line options for ttenv:

source ttenv.csh -help

or

. ttenv.sh -help

PATH environment variable

TimesTen provides utilities for managing and debugging TimesTen applications. To make these utilities readily available, include the bin directory found in install_dir in the PATH environment variable.

On Windows, the PATH environment variable must also contain the bin directory of the ORACLE installation, if you are using the IMDB Cache option.

ODBCINI environment variable

TimesTen applications use the odbc.ini file to define data sources and their data store attributes. (For a description of data store attributes, see "Data Store Attributes" in the Oracle TimesTen In-Memory Database Reference.) By default on UNIX platforms, TimesTen first looks for the .odbc.ini file in the home directory of the user running the TimesTen application. To override the name and location of this file at run-time, set the $ODBCINI environment variable to the pathname of an.odbc.ini file before launching the TimesTen application.

If TimesTen cannot locate a user DSN file, TimesTen also looks for the sys.odbc.ini file in install_dir/info. For more information, see "User and system DSNs" in Oracle TimesTen In-Memory Database Operations Guide.

SYSODBCINI environment variable

TimesTen applications use the sys.odbc.ini file to define system data sources and their data store attributes. (For a description of data store attributes, see "Data Store Attributes" in the Oracle TimesTen In-Memory Database Reference.) A system data source can be used by any user on the machine. On Windows, system DSNs are defined from the System DSN tab of the ODBC Data Source Administrator. On UNIX, system DSNs are defined in the file install_dir/info/sys.odbc.ini. To override the name and location of this file at run-time, set the $SYSODBCINI environment variable to the pathname of a sys.odbc.ini file before launching the TimesTen application.

If TimesTen cannot locate a user DSN file, TimesTen also looks for the sys.odbc.ini file in install_dir/info.

For more information, see "User and system DSNs" in Oracle TimesTen In-Memory Database Operations Guide.

SYSTTCONNECTINI environment variable

TimesTen client applications use the sys.ttconnect.ini file to define logical server names. For a description of logical server names, see "Working with the TimesTen Client and Server" in the Oracle TimesTen In-Memory Database Operations Guide. By default on UNIX platforms, TimesTen looks in install_dir/sys.ttconnect.ini. To override the name and location of this file at run-time, set the SYSTTCONNECTINI environment variable before launching the TimesTen Client application.

TimesTen also looks for the sys.ttconnect.ini file under install_dir/info.

On Windows systems, logical server names can be configured using the ODBC Data Source Administrator.

TNS_ADMIN environment variable

On platforms where the IMDB Cache is supported, to work with Oracle data, you must set the TNS_ADMIN environment variable be set to the path of the tsnnames.ora file.

The ttmodinstall utility with the -tns_admin option allows you to set a value for this environment variable after installation. See the Oracle TimesTen In-Memory Database Reference for more details on ttmodinstall.

Shared library path environment variable

On Solaris and Linux systems, add install_dir/lib directory to the LD_LIBRARY_PATH environment variable.

On AIX systems, add install_dir/lib directory to the LIBPATH environment variable.

On HP-UX 32-bit systems, add install_dir/lib to the SHLIB_PATH environment variable.

On HP-UX 64-bit systems, add install_dir/lib to the LD_LIBRARY_PATH environment variable.

Java environment variables

The following sections provide more detail about the environment variables that affect the environment for TimesTen Java applications.

• Set the CLASSPATH variable

• Set the shared library path variable

• Set the THREADS_FLAG variable (UNIX only)

• Set the PATH variable

install_dir/ttjdbcjdk_ver.jar

set CLASSPATH .:install_dir/lib/ttjdbc5.jar

setenv CLASSPATH .:install_dir/lib/ttjdbc5.jar

set CLASSPATH=.;install_dir/lib/ttjdbc5.jar

set CLASSPATH=.;"install_dir/lib/ttjdbc5.jar"

> java -version

install_dir/lib/timestenjmsxla.jar
install_dir/3rdparty/jms1.1/lib/jms.jar
install_dir/lib/orai18n.jar

.:install_dir/lib/ttjdbc5.jar:install_dir/lib/timestenjmsxla.jar
:install_dir/3rdparty/jms1.1/lib/jms.jar:install_dir/lib/orai18n.jar

setenv THREADS_FLAG native

THREADS_FLAG=native
export THREADS_FLAG

Installing TimesTen on HP-UX Memory Windows

An instance of TimesTen can run in a memory window. A separate instance of TimesTen is required for each memory window. During installation, the TimesTen installer prompts you to indicate whether this instance is to be run in a memory window.

For a memory windows installation, the installer appends the instance name and port number of the daemon to /etc/services.window allowing the instance name to be used as a key to the getmemwindow(1M) command. Use the getmemwindow <instance> command to determine which port is being used by the instance.

Using TimesTen in a memory window

To use a TimesTen instance running in a memory window, you must launch your application using the HP-UX setmemwindow(1M) command.

For example, given instance tt1121_32, use:

% setmemwindow -j -i `getmemwindow tt1121_32` <prog>

TimesTen utilities are used without the setmemwindow command, for example:

% ttBackup ...

Address space considerations

The maximum size for any one data store remains 1GB with 32-bit TimesTen.

TimesTen allocates a single shared memory segment per data store. TimesTen may also allocate shared memory segments when configured to use the shared memory IPC mechanism for client/server.

The daemon and utility programs (programs) provided by TimesTen are linked with EXEC_MAGIC, using the -N option to ld(1). You may change the TimesTen programs to be marked SHMEM_MAGIC, enabling 2GB of shared memory within the window. Any single data store is still limited to 1GB.

For example, to use SHMEM_MAGIC, log in as root and use:

# chatr -M tt_instance/bin/timesten* tt_instance/bin/*Cmdtt_instance/bin/ttcserver

To return to EXEC_MAGIC, use:

# chatr -N tt_instance/bin/timesten* tt_instance/ bin/ *Cmdtt_instance/bin/ttcserver

To determine if a program is SHMEM_MAGIC or EXEC_MAGIC, use:

# chatr binary

The chatr(1M) command prints "normal executable" for EXEC MAGIC programs. It prints "SHMEM_MAGIC" for programs so marked.

HP-UX Memory Windows Troubleshooting

TimesTen support may ask for all of the following to diagnose a problem using memory windows.

• How many memory windows do you have configured?

  % /usr/sbin/kmtune -q max_mem_windows
  

• What is the maximum shared memory segment size?

  % /usr/sbin/kmtune -q shmmax
  

• How many windows are you using?

  % cat /etc/services.window
  

• Do you have the correct instance in your path?

  % ttVersion % ttStatus % getmemwindow tt_instance
  

• Can you connect with a utility provided by TimesTen?

  % ttIsql -connStr dsn=my_dsn
  

• If you installed the QuickStart, can you successfully run a demo program? The TimesTen demos are located under install_dir/quickstart/sample_code.

• What other segments are in use?

  % ipcs -m -a
  

• Does setmemwindow(1M) or a TimesTen utility such as ttStatus return silently when you expected output?

• Check the error status from the setmemwindow command.

• What does the memwin_stats tool show?

  % memwin_stats -w
  

  The memwin_stats tool may be downloaded from HP at ftp://contrib:9unsupp8@hprc.external.hp.com/

• What error are you getting when you try to connect?

The following list is not exhaustive but may help sort out the problem.

• Not enough core (ENOMEM, errno=12) indicates a problem allocating the requested amount of shared memory. Can you attach with small PermSize and TempSize attributes?

• Shared memory can be fragmented. Sometimes, you can attach with increasingly larger segments until you allocate what you want. Are you attempting to allocate more than 1GB within your window (2GB if using SHMEM_MAGIC)?

• Permission Denied (EACCES, errno=13) indicates that you are attempting to attach to the wrong instance or are pointing to the wrong memory window. Which -i argument is passed to setmemwindow(1M)?

• Invalid Argument (EINVAL, errno=22) indicates that the shared segment may have been allocated in another quadrant. Did you mark the TimesTen programs SHMEM_MAGIC? Did you also mark your application SHMEM_MAGIC?

• No space left on device (ENOSPC, errno=28) may indicate that the system is not configured for enough shared memory segments or identifiers or that the system may have insufficient swap space to allocate the shared segment. Check the values of shmseg, shmmni, maxswapchunks and run the swapinfo(1M) command.