1. Manuals
  2. Brands
  3. Oracle Manuals
  4. Software
  5. B31679-01
  6. Installation manual

Oracle B31679-01 Installation Manual

Oracle audio technologies carrying case owner's manual
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Oracle TimesTen
In-Memory Database
Installation Guide
Release 7.0
B31679-01
For last-minute updates, see the TimesTen release notes.

Advertisement

Table of Contents
loading

Related Manuals for Oracle B31679-01

Summary of Contents for Oracle B31679-01

  • Page 1 Oracle TimesTen In-Memory Database Installation Guide Release 7.0 B31679-01 For last-minute updates, see the TimesTen release notes.
  • Page 2 Copyright ©1996, 2007, Oracle. All rights reserved. ALL SOFTWARE AND DOCUMENTATION (WHETHER IN HARD COPY OR ELECTRONIC FORM) ENCLOSED AND ON THE COMPACT DISC(S) ARE SUBJECT TO THE LICENSE AGREEMENT. The documentation stored on the compact disc(s) may be printed by licensee for licensee’s internal use only.

  • Page 3: Table Of Contents

    Contents About this Guide TimesTen documentation ..... 1 Background reading ..... . . 2 Conventions used in this guide .
  • Page 4 Platform support ..... . . 19 JDK support ......20 Client/Server configurations .
  • Page 5 Installing TimesTen on HP-UX Memory Windows ... 54 Use a separate instance for each memory window ..54 Using TimesTen in a memory window ....55 Address Space Considerations .
  • Page 6 3 Data Store Upgrades Introduction ......87 Data store compatibility ....87 Data type compatibility .
  • Page 7 Index Contents...
  • Page 8 viii Oracle TimesTen In-Memory Database Installation Guide...

  • Page 9: About This Guide

    About this Guide This document contains all necessary information for installing the Oracle TimesTen® In-Memory Database (TimesTen) Data Manager, Client and Server components. The TimesTen CD contains a notes. These notes list product information and late changes to the printed documentation. The release notes are also available in PDF format.

  • Page 10: Background Reading

    Oracle TimesTen In-Memory Database SQL Reference Guide Oracle TimesTen In-Memory Database Error Messages and SNMP Traps Oracle TimesTen In-Memory Database TTClasses Guide TimesTen to TimesTen Replication Guide TimesTen Cache Connect to Oracle Guide Oracle TimesTen In-Memory Database Troubleshooting Procedures Guide Background reading For a Java reference, see: •...

  • Page 11: Conventions Used In This Guide

    • Microsoft ODBC 2.0 Programmer’s Reference and SDK Guide, included online in PDF format, provides information on ODBC for UNIX developers. For a conceptual overview and programming how-to of ODBC, see: • Kyle Geiger. Inside ODBC. Redmond, WA: Microsoft Press. 1995. For a review of SQL, see: •...
  • Page 12 TimesTen documentation uses these conventions in command line examples and descriptions: If you see... It means... Variable; must be replaced with an appropriate value. fixed width italics Square brackets indicate that an item in a command line is optional. Curly braces indicated that you must choose one of the items separated by a vertical bar ( | ) in a command line.

  • Page 13: Technical Support

    A sample name for the TimesTen instance administrator. timesten You can use any legal user name as the TimesTen administrator. On Windows, the TimesTen instance administrator must be a member of the Administrators group. Each TimesTen instance can have a unique instance administrator name.
  • Page 14 Oracle TimesTen In-Memory Database Installation Guide...

  • Page 15: Access Control

    Access Control Introduction Access Control With TimesTen you can optionally install a layer of internal security, which throughout the TimesTen documentation set and in the installation scripts is referred to as “Access Control.” The Access Control feature of TimesTen provides an environment of basic control for applications that use the internally defined privileges.

  • Page 16: Cache Connect

    Cache Connect For Cache Connect, the TimesTen internal user must match the Oracle user. External Client/Server users must match the Oracle user. If you are using the Cache Connect Administrator interface, the user must be an internal TimesTen user. Replication If Access Control is enabled, replication daemon administration and replication schema changes are restricted to users having the ADMIN privilege.

  • Page 17: Instance Data Store

    % ttDaemonAdmin -start To stop an instance: % ttDaemonAdmin -stop Instance data store A DSN for a minimal instance-wide data store is defined by TimesTen at install time to guarantee that TimesTen always has something with which to connect. The following is the definition of the instance DSN for a root installation: [TT_instance] Driver=install_dir/lib/libtten.suffix...

  • Page 18: Timesten Instance Users

    Note: All examples in the TimesTen documentation set use the name to represent the instance administrator. timesten For details on establishing the TimesTen instance administrators group, “Create the TimesTen instance administrators group” on page On Windows systems, the user automatically becomes the System TimesTen instance administrator when Access Control is selected at install time.

  • Page 19: Before Installation

    automatically converts the external user name to upper case, rendering it case insensitive. PWDCrypt attribute allows you to encrypt a password rather to use cleartext passwords, and it also provides a way to deal with the special characters and case sensitivity used in passwords that might create difficulties if specified in clear text within the PWD DSN attribute.

  • Page 20: Installation Directories, Files And The Daemon Port

    Installation directories, files and the daemon port Installation of TimesTen must be performed by the chosen instance administrator user. The instance administrator owns all files in the installation directory tree. Only the instance administrator can operate the instance. Installation directories The installer suggests default destination directories, based on the user performing the installation.

  • Page 21: Daemon Port

    been selected. If this file is missing, an error occurs after Access Control is enabled. This file is readable and writable only by the instance administrator. Passwords are stored in encrypted form and are not known to the instance administrator as one way hashes, so they cannot be recovered. Daemon port Though the instance registry enforces portTCP/IP uniqueness for TimesTen instances, the possibility of the TimesTen main daemon port...

  • Page 22: Maintaining Users And Privileges

    Maintaining users and privileges TimesTen allows the instance administrator to create, drop and alter users when Access Control is enabled. It also allows the instance administrator to grant and revoke privileges for users. For details see Chapter 5, “SQL Statements Database SQL Reference Administration of users is done at the instance level by establishing a connection to any data store and using the SQL commands to create and...
  • Page 23 All other changes to the TimesTen instance can only be made by uninstalling and re-installing the same or a differently release of TimesTen. (See “Changing the daemon port number on UNIX” on page “ORACLE_HOME environment variable” on page 77.) Access Control...
  • Page 24 Oracle TimesTen In-Memory Database Installation Guide...

  • Page 25: Timesten Installation

    TimesTen Installation This chapter contains configuration information that you will need to review before installing TimesTen on your system, in the sections: • Platforms and configurations • Installation instances • Choosing the appropriate TimesTen components • Installation prerequisites • Operating system security considerations •...
  • Page 26 • Building and running the demo applications • Viewing the online documentation Finally, this chapter contains information that helps you troubleshoot any problems that may arise during the installation process: • Installation problems Oracle TimesTen In-Memory Database Installation Guide...

  • Page 27: Platforms And Configurations

    Platforms and configurations Platform support Times Ten Data Manager and TimesTen Client/Server are supported in the following environments:. Environment Microsoft Windows 2000, Windows XP and Windows Server 2003 for Intel IA-32 and EM64T and AMD64 CPUs. Solaris 10 for AMD64 CPUs. Solaris 8, 9 and 10 for UltraSparc CPUs.

  • Page 28: Jdk Support

    JDK support Note: TimesTen supports the Sun JVM and the BEA WebLogic JRockit JVM for Linux and Windows x86 systems. For details on JRockit, see www.bea.com TimesTen supports the following JDKs on the specified platforms: Environment Microsoft Windows 2000, Windows XP and Windows Server 2003 for Intel IA-32 and EM64T and AMD64 CPUs...

  • Page 29: Client/Server Configurations

    Environment HP-UX 11i and HP-UX 11i v2 for PA-RISC 32- and 64-bit HP-UX 11i v2 for Itanium2 AIX 5L 5.2 and 5.3 for POWER CPUs Tru64 UNIX 5.1B for Alpha EV68 CPUs Client/Server configurations A TimesTen client on any supported platform can connect to a TimesTen server on any platform where TimesTen is supported.

  • Page 30: Replication Configurations

    Cache Connect is supported on the 32-bit and 64-bit platforms specified in this table: Environment Microsoft Windows 2000, Windows XP and Windows Server 2003 for Intel IA-32 and EM64T and AMD64 CPUs Solaris 10 for AMD64 CPUs systems Solaris 8, 9 and 10 for UltraSparc CPUs SuSE LINUX Enterprise Server 9 and 10 for Intel IA-32, EM64T and...

  • Page 31: Installation Instances

    Installation instances On UNIX, you can install more than one instance of any TimesTen release. By default, the instance name for this release is tt70. If an instance of a particular release of TimesTen already exists on the machine, and you would like to install a second instance of the same TimesTen release, you must supply a unique instance name and port number.

  • Page 32: Choosing The Appropriate Timesten Components

    Choosing the appropriate TimesTen components TimesTen allows you to select the components of TimesTen that you wish to install. Components available on Windows Type Description Compact Installs the TimesTen client, ODBC drivers and examples. Typical Installs the TimesTen Data Manager, TimesTen Client, TimesTen Server, documentation and examples.

  • Page 33: Installation Prerequisites

    Installation prerequisites Before installing TimesTen, make sure the appropriate requirements are met for your operating system. On platforms where JDBC is supported you must have the appropriate version of the JDK installed on your machine to use JDBC. See “Platforms and configurations” on page 19 to learn which JDK is required for your platform.
  • Page 34 Other Client/ The maximum number of concurrent IPC connections to a TimesTen Server Server allowed by TimesTen is 9,999. However, system limits can take Settings precedence on the number of connections to a single DSN. Client/ Server users can increase the file descriptor limit to support a large number of connections and processes.
  • Page 35 Scroll down the list of parameters to minimum of 4096 or greater. For HP-UX 11i systems, also scroll down the list of parameters to and change its value to a maximum of 0x40000000. shmmax Note: The value indicates that the largest shared memory segment that can be created is 1024 MB.
  • Page 36 The C development tools are required if native development will be done on the machine. Large pages Large pages can be enabled only if the running Linux kernel supports large pages (also called “huge pages” in Linux community). If large pages are supported by the kernel, there should be special files in the directory that indicate the number and size of the large /proc...
  • Page 37 When TimesTen uses large pages, the file in HugePages_Free /proc/ changes. meminfo Semaphores To view existing kernel parameter settings, log in as and use: root # /sbin/sysctl -a Shared To increase the shared memory size to 2048 MB, for example, as root memory edit the...
  • Page 38 For Red Hat 3.0, install: compat-libstdc++-7.3-2.96.123 For Red Hat 4.0, install: compat-libstdc++-296-2.96.132.7.2 These packages can be install either using the rpm command or by using the Red Hat GUI installer found in “Legacy Software Development.” Replication For replication, TCP send and receive buffers should be increased to a minimum of 512KB.
  • Page 39 ryps3# modload /kernel/sys/shmsys Increase For Solaris 10 systems, the default semaphore settings should be number of sufficient without entries in semaphores On other Solaris systems, you may need to increase the number of semaphores. TimesTen consumes 1 SEMMNI per active data store, plus one additional SEMMNI per TimesTen instance where Client/Server communication is done through shared memory.
  • Page 40 access 12 data stores, add the following line to before using TimesTen: set shmsys:shminfo_shmseg=12 Other Other changes that you may need to make to your Solaris system changes include the following: • To allow a large number of connections to a data store, add the following lines to set rlim_fd_cur=4096 set rlim_fd_max=4096...
  • Page 41 Replication For replication, TCP send and receive buffers should be increased to a minimum of 512KB. You may need to embed the following commands into a script that can be run at system boot time: # /usr/sbin/ndd -set /dev/tcp tcp xmit_hiwat=524288 # /usr/sbin/ndd -set /dev/tcp tcp_recv_hiwat=524288 Tru64 UNIX Semaphores...

  • Page 42: Default Installation Directories

    To increase the maximum data segment (malloc space) a process may use, change the kernel values max_per_proc_data_size For example, to change all of these values to 10GB: Create a text file, per_proc_address_space = 10737418240 max_per_proc_address_space = 10737418240 per_proc_data_size = 10737418240 max_per_proc_data_size = 10737418240 Log in as root and run the command: # sysconfigdb -m -f kernelparams proc...

  • Page 43: Cache Connect

    The temporary directory is operating system-dependent. Usually it is located in these directories: • On Windows, Settings\Temp • On Solaris, Linux and Tru64 UNIX, • On HP-UX and AIX, You can change the location of your temporary directory by setting the environment variable on Windows.
  • Page 44 segments are ownership and permissions restricted to that of a particular operating system group. This mode only works if TimesTen is installed and running as . See the Oracle TimesTen In-Memory Database root API Reference Guide. Oracle TimesTen In-Memory Database Installation Guide...

  • Page 45: Prerequisites For Non-Root Installations On Unix Systems

    Prerequisites for non-root installations on UNIX systems As discussed in can install TimesTen as a non-root user. This entire section applies to all UNIX platforms on which TimesTen is supported, unless otherwise indicated. However, you may need to perform certain tasks as the user prior to installing TimesTen and after installation.

  • Page 46: Create The Timesten Registry

    # setprivgrp timesten MLOCK getprivgrp group: $ getprivgrp timesten timesten: MLOCK Note: On Linux and Tru64 systems, root privileges are required to use MemoryLock attribute. On Solaris systems, you must be installed as root to use MemoryLock=1 or 2.Data stores in a non-root instance of TimesTen can use settings 3 and 4 for this attribute, on Solaris systems.

  • Page 47: Configure The Syslog Messages

    This step is only necessary if you want the TimesTen instance to start each time the machine is rebooted. Note: If you install these scripts into your system directory, you must manually remove them in the case that you want to uninstall your TimesTen instance, using # setuproot -uninstall Configure the syslog messages...

  • Page 48: Installing Timesten On Windows Systems

    See the TimesTen Developer’s Guide for more information about using TimesTen. Installing TimesTen on Windows systems This section discusses installation and related issues for Windows systems. For a list of Windows platforms supported by TimesTen, see “Platforms and configurations” on page Note: Before beginning installation, be sure that the prerequisites defined in Installing TimesTen...

  • Page 49: Installing Timesten In Silent Mode

    By default, Access Control is not enabled. See Control” for more details. Custom setup also lets you choose other custom options. The installation program adds TimesTen directories to the system environment variables LIB and INCLUDE. In addition, installation prompts you to add a directory to the system environment variable PATH.

  • Page 50: Verifying Installation

    Verifying installation To verify that TimesTen has been properly installed, check that the driver files are available and that the services are running: Check that the TimesTen 7.0 Start menu shortcut has been added to the Windows Desktop Start > Programs menu. On the Windows Desktop, choose Start >...

  • Page 51: Working With The Data Manager Service And 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.

  • Page 52: Uninstalling Timesten

    On the Windows desktop, choose Start > Settings > Control Panel > Administrative Tools > Services. This displays all currently available services. Select TimesTen Data Manager 7.0. Click Start to start the service. If the service is already running, click Stop to stop the service.

  • Page 53: Installing Timesten

    Installing TimesTen To install TimesTen on your Solaris system, follow these steps: Log in as the TimesTen instance administrator or log in as user root. Load the CD-ROM into the CD drive as follows: • If the Volume Manager is installed on the system, you don’t have to explicitly mount the CD;...
  • Page 54 In addition, -batch filename -record filename -doc -help -verbose The CD contains tar files of TimesTen. If the setup script cannot find the tar files to extract from, it prompts you for their location. Enter your response to the setup script prompts. Note: To install or uninstall TimesTen without having to respond to prompts, use the older releases of TimesTen cannot be used to install this release.
  • Page 55 • On 64-bit systems, prompts you to install one of the following releases: – 32-bit (default) – 64-bit • Prompts you to: – Install a new instance – Upgrade an existing instance (This option allows you to incrementally install the Cache Connect option. The major and minor version numbers of the TimesTen release must match exactly.) –...

  • Page 56: Working With The Daemon And Server

    • Copies the daemon scripts into the appropriate directories. • If installed by user when the system boots. • Creates the directory where data stores created by the TimesTen demo applications will reside. By default they reside in TimesTen/ install_dir/info/DemoDataStores •...

  • Page 57: Uninstalling Timesten

    To stop the daemon manually, use the utility command: ttDaemonAdmin -stop To start the daemon manually, use the utility command: ttDaemonAdmin -start Uninstalling TimesTen To uninstall all TimesTen components: Log in as the root, or log in as user root. The TimesTen setup script is in the install_dir the script with the installation directory:...
  • Page 58 # mkdir /cdrom Mount the CD-ROM, as follows: • If your system is configured to mount the CD-ROM at /cdrom # /etc/mount /cdrom • Otherwise, mount the CD-ROM device name to the directory, as follows: # /etc/mount -r cdfs CD-ROM_device_name /cdrom where CD-ROM_device_name Run the setup script by typing the following:...
  • Page 59 Specify the option at the end, outside the quotation marks. In addition, also accepts these options: setup.sh Installs or uninstalls TimesTen without having to -batch filename respond to prompts. If filename is specified, the installation reads all installation prompts from the file.
  • Page 60 • On 64-bit systems, prompts you to install one of the following releases: – 32-bit (default) – 64-bit • Prompts you to: – Install a new instance – Upgrade an existing instance (This option allows you to incrementally install the Cache Connect option. The major and minor version numbers of the TimesTen release must match exactly.) –...

  • Page 61: Working With The Timesten Daemon And Server

    • Copies the daemon scripts into the appropriate directories. • If installed by user , configures the system to start the daemon root when the system boots. • Creates the directory where data stores created by the TimesTen demo applications will reside. By default they reside in TTinstance TimesTen/ •...

  • Page 62: Uninstalling Timesten

    If you installed TimesTen as root, the daemon startup file on HP-UX is: /etc/rc.config.d/tt_TTinstance If you installed TimesTen as a non-root user, It is: install_dir/startup To stop the daemon manually, use the utility command: ttDaemonAdmin -stop To start the daemon manually, use the utility command: ttDaemonAdmin -start Uninstalling TimesTen To uninstall TimesTen, follow these steps:...

  • Page 63: Using Timesten In A Memory Window

    command to determine which port is being used by the <instance> instance. Using TimesTen in a memory window In order 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 , use: tt_ins1...

  • Page 64: Troubleshooting

    application EINVAL, errno=22 If a connection is made to a data store with ExclAccess=1, then memory windows will not be used. In this case, TimesTen does not allocate shared memory but rather space for the data store is allocated from the process' private data space.

  • Page 65: Installing Timesten On Aix Systems

    • Not enough core ( 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 •...
  • Page 66 # mount /usr/cdrom/TimesTen7.0 After the CD-ROM setup is complete, you can install TimesTen as follows: Still logged in as user root or the the setup script by typing: # cd mount_dir # ./setup.sh where mount_dir is the directory where the CD is mounted (e.g.: /usr/cdrom/TimesTen7.0 •...
  • Page 67 Installs documentation. -doc Displays the help message. -help Displays extra installation information. -verbose The CD contains tar files of TimesTen. If the setup script cannot find the tar files to extract from, it prompts you for their location. Enter your response to the setup script prompts. Note: To install or uninstall TimesTen without having to respond to prompts, use the -batch...
  • Page 68 – Data Manager only – Client only • Prompts you for the location of your TimesTen installation and specific files, if installing as a non-root user. • Prompts you to specify the daemon port number. If no instances of TimesTen are installed on the machine, or if no instances use the default port number 17000 for 32-bit installations and 17001 for 64- bit applications, prompts you to use the default port number.

  • Page 69: Working With The Timesten Daemon And Server

    Working with the TimesTen daemon and server The TimesTen daemon 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.

  • Page 70: Installing Timesten On Linux Systems

    Installing TimesTen on Linux systems This section discusses installation and some related topics for Linux systems. Note: Before beginning installation, be sure that the prerequisites defined in Installing TimesTen To install TimesTen on your Linux system, follow these steps: Log in as the or log in as user root.
  • Page 71 removes all files it had installed. In addition, these options: Installs or uninstalls TimesTen without having to -batch filename 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.
  • Page 72 minor version numbers of the TimesTen release must match exactly.) – Display information about an existing instance or – Quit the installation. • Prompts you to chose the default instance name or chose a name for your TimesTen instance. See •...

  • Page 73: Working With The Timesten Daemon And Server

    • If there are other instances of the same patch release of TimesTen installed on the same machine, prompts you to provide a unique port to be used by the TimesTen daemon. • If the TimesTen Server is being installed, prompts you to configure the Server: server name, port number and logging options.

  • Page 74: Installing Timesten On Tru64 Unix Systems

    Log in as the root, or log in as user root. The TimesTen setup script is in the install_dir/ the script with 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 to verify that all TimesTen processes have terminated.
  • Page 75 • You can run the setup script with the option (default is - uninstall option, the script stops the daemon if it is running and removes all files it had installed. Note: To uninstall TimesTen, you must run directory outside of the installation directory that you wish to uninstall. For example to uninstall the default instance run /opt/TimesTen/tt70/bin/setup.sh -uninstall In addition,...
  • Page 76 release are assigned default answers and may produce unexpected results when batch files from different versions are used. The setup script performs these actions (unless your answers resulted in termination of the installation process): • Prompts you to: – Install a new instance –...

  • Page 77: Working With The Timesten Daemon And Server

    • Copies the daemon scripts into the appropriate directories. • If installed by user , configures the system to start the daemon root when the system boots. • Creates the directory where data stores created by the TimesTen demo applications will reside. By default they reside in TTinstance TimesTen/ •...

  • Page 78: Uninstalling Timesten

    To start the daemon manually, use the utility command: ttDaemonAdmin -start Uninstalling TimesTen To uninstall all TimesTen components: Log in as the root, or log in as The TimesTen setup script is in the install_dir/ the script with 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.

  • Page 79: Informational Messages On Windows Systems

    Note: The Cache Administrator will not work if it is running on a Windows machine with the Windows Firewall ON (this is the usual setting). In this case, the Windows Administrator must add an exception to allow the Cache Administrator to connect through the Windows Firewall.

  • Page 80: Informational Messages On Unix Systems

    Click Next or Previous to view additional messages. Note: You can also use the ttDaemonLog utility to view messages logged by the TimesTen Data Manager. For a description of the system administration utilities, see Memory Database API Reference 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.

  • Page 81: Incremental Install And Uninstall Of Cache Connect

    user.err; user.warn; user.info To make changes to or be the after the syslog command For further details, see your operating system's documentation for syslog.conf Note: If the create one according to the syslog.conf manual page so the daemon can log its data to the To determine if your the TimesTen ttSyslogCheck utility.

  • Page 82: Environment Modifications

    Environment modifications This section describes various environment variables that you may need to set, depending on the features of TimesTen that your application uses. The following table summarizes, in alphabetical order, the environment variables detailed in this section and other parts of this guide. Some of these environment variables are platform specific.

  • Page 83: Path Environment Variable

    Environment What to include Variable Set to the location where the SYSODBCINI sys. TimesTen system data stores is to be found. This environment variable should be set in the start-up script. Set to the location where the SYSTTCONNECTINI sys.ttconnect.ini used by TimesTen Client applications to define logical server names.

  • Page 84: Sysodbcini Environment Variable

    application. If TimesTen cannot locate a user DSN file, the system DSN file located in “Defining data sources for the demo applications” on page 83 information on the also looks for the SYSODBCINI environment variable TimesTen applications use the sys. sources and their data store attributes.

  • Page 85: Classpath Environment Variable

    CLASSPATH environment variable On Windows and UNIX platforms, add install_dir /lib/ttjdbc CLASSPATH environment variable. For example, for JDK 5.0, set the CLASSPATH environment variable to: install_dir ttjdbc5.jar ORACLE_HOME environment variable On platforms where the Cache Connect to Oracle option is supported, to work with Oracle data, the TimesTen Oracle agent must be running.
  • Page 86 On HP-UX 64-bit systems, add install_dir/ LD_LIBRARY_PATH Connect to Oracle option, $ORACLE_HOME/lib “ORACLE_HOME environment variable” on page On Tru64 UNIX systems, add install_dir/ LD_LIBRARY_PATH Oracle TimesTen In-Memory Database Installation Guide environment variable. If you are using the Cache must also contain SHLIB_PATH and must not contain $ORACLE_HOME/lib32...

  • Page 87: Web Server Configuration

    Web server configuration The TimesTen daemon contains an embedded web server, that is used for the Cache Administrator if the Cache Connect to Oracle option is installed. If you select to enable the web server at install time, TimesTen enables it by setting the -webserver option in the ttendaemon.options file.

  • Page 88: Migrating Data Stores To Timesten 7.0

    CGIROOT — A subdirectory of located. The path should begin and end with a '/' on all platforms. The default is /cgi-bin/. PERL — The path to the Perl interpreter. The path is set by the TimesTen installation scripts. Do not change the default path unless you are certain that the path is for a Perl version that is compatible with TimesTen and that it contains all the required libraries.
  • Page 89 column and index definitions. When TimesTen restores a table in a new data store, it also restores the table’s indexes. Note: The ttMigrate utility cannot migrate data stores across different hardware platforms. For example, you cannot migrate a Windows data store to a Solaris data store.

  • Page 90: Using The Ttbulkcp Utility

    % /opt/TimesTen/tt70/bin/ttMigrate -rx DSN=Salestt70 sales.dat Using the ttBulkCp utility ttBulkCp and ASCII files. The data files used by from a single table. They also do not store the table’s column or index definitions. Therefore, when migrating from one TimesTen data store to another with ttBulkCp, you must first create the tables and indexes in the new data store manually.

  • Page 91: Building And Running The Demo Applications

    DSN=source600 able able.save % /opt/tt60/32/bin/ttBulkCp -o DSN=source600 baker baker.save Next create a new data source name, data store, and execute the commands: % /opt/TimesTen/tt70/bin/ttIsql -connStr DSN=source_tt70 -f create.sql % /opt/TimesTen/tt70/bin/ttBulkCp -i DSN=source_tt70 able able.save % /opt/TimesTen/tt70/bin/ttBulkCp -i DSN=source_tt70 baker baker.save Building and running the demo applications Source code for several demo applications is provided in the directory as part of the TimesTen Data Manager distribution on UNIX...

  • Page 92: Building The Demo Applications

    A sample file containing definitions for the DSNs required by the TimesTen demo applications is provided in sys.odbc.ini non-root user the file is located in Building the demo applications Source code and makefiles are provided for all the demo applications. See the README file in install_dir demo Problems running the demo programs...

  • Page 93: Building And Running The Jdbc Demo Applications

    • Is the TimesTen service running? To start the service, double-click Control Panel > Administrative Tools > Services, choose the TimesTen Data Manager service, and click Start. Building and running the JDBC demo applications Source code for a demo application is provided in the install_dir /demo/jdbc distribution.

  • Page 94: Installation Problems

    Installation problems To avoid problems during installation, make sure you have met all prerequisites. Using information in the installation guide and the release notes, check that: • You are running a supported version of the OS. • You have sufficient disk space. •...

  • Page 95: Data Store Upgrades

    – Data Store Upgrades Introduction When a TimesTen data store is loaded into shared memory, many of its attributes are fixed, including size, logging options, TimesTen software release number, and the location of its checkpoint and log files on disk. This chapter describes the steps required to change these attributes and to upgrade TimesTen data stores when you install a new version of TimesTen.

  • Page 96: Data Store Character Set

    backward-compatible data types, see “Type specifications” on page 8 Oracle TimesTen In-Memory Database SQL Reference Guide. Because some of the new Oracle data types have the same names as the backward-compatible TimesTen data types, a set of aliases has been added for addressing the data types.

  • Page 97: Data Type Conversion

    the same as the character set specified for the Oracle database that the TimesTen data store connects to. • Replication is not possible between data stores with different character sets. Because data stores created with versions of TimesTen prior to 7.0 do not have a data store character set specified, a special data store character set, TIMESTEN8, has been created, which allows replication compatibility between data stores created by TimesTen 7.0 and those created by earlier releases.

  • Page 98: Converting Data Types To Oracle Data Types

    Converting data types to Oracle data types Note: If you intend to use your data store with TimesTen Cache Connect to Oracle, you must convert your data types to Oracle data types. However, you will not be able to perform an online upgrade using replication.

  • Page 99: Data Store Character Set Conversion

    Data store character set conversion Beginning with TimesTen 7.0, a character set must be specified for each TimesTen data store using the DSN attribute DatabaseCharacterSet. In some cases, you may need to change the configured data store character set as part of the upgrade process. There are two different cases in which a data store character set conversion will be required: •...

  • Page 100: Converting From A Character Set Other Than Timesten8

    Load the data store from the file using -noCharsetConversion no character values are changed when the data is loaded into the DSN using the new character set. For example: ttMigrate -r -noCharsetConversion DSN=SalesData salesdata.mig Note: If you find that you have accidentally converted your data store from TIMESTEN8 to the wrong character set, you can use the same procedure to convert your data store to the correct character set without any accidental modification of the character data.

  • Page 101: Upgrade Modes

    Upgrade modes TimesTen allows you to perform these kinds of upgrades: In-place upgrades In-place upgrades are available for moving to a new patch release of TimesTen, such as moving from the first patch release of 7.0, version 7.0.1.0.0, to the second patch release of 7.0, version 7.0.2.0.0. As long as your TimesTen data stores do not reside in the TimesTen installation directory, you can uninstall an old release of TimesTen, install a new patch release of TimesTen and connect to existing data stores with the...

  • Page 102: Online Upgrades With Replication

    Online upgrades with replication When upgrading to a new major release of TimesTen, you may have a mission critical data store that needs to remain continuously available to your applications. You can use TimesTen replication to keep two copies of a data store synchronized, even when the data stores are from different versions of TimesTen, allowing your applications to stay connected to one copy of the data store while the other one is being upgraded.

  • Page 103: Performing An In-Place Data Store Upgrade

    a Client/Server online upgrade from a TimesTen version prior to 6.0” on page • If you are upgrading from a version of TimesTen that is 6.0 or above, the process is much easier. Starting with 7.0, TimesTen Server is able to talk directly to all versions of TimesTen Client from 6.0 onward.

  • Page 104: Moving To A New Patch Release Of Timesten

    utility. (See Reference Disconnect all applications from the data store. In this example, the data store The data store started, pause replication on the data stores, and then stop replication on the data store that you are unloading from memory, using the commands: ttRepAdmin -receiver -name upgrade -state pause original ttRepAdmin -receiver -name original -state pause upgrade...

  • Page 105: Performing An Offline Upgrade

    Performing an offline upgrade You can do an offline upgrade by exporting the data store into an external file using either the restoring the data store with the desired changes. These update procedures require that all applications be disconnected from the data store and that the data store be unloaded from shared memory.

  • Page 106: Moving To A Different Directory

    Note: After the destination data store have AUTOREFRESH STATE set to OFF, no matter how it was set on the source data store. Reset AUTOREFRESH STATE to ON by using the Moving to a different directory The TimesTen daemon identifies a data store by the full path name of the data store’s checkpoint files.
  • Page 107 Note: Before moving a replicated data store to another machine, you should be experienced with TimesTen replication. We highly advise calling TimesTen customer support for help with this procedure. To copy a data store from one system to another with the same CPU architecture and operating system: Back up the data store on the original system using ttBackup.

  • Page 108: Reducing Data Store Size

    Reducing data store size Once a data store has been defined with a particular size for the permanent partition (indicated by the cannot be loaded at a smaller size, even if tables or rows are deleted. A copy of the data store made with permanent partition size embedded in it.

  • Page 109: Moving Between 32-Bit And 64-Bit Data Stores

    Note: The temporary partition size of a data store may be changed by simply modifying the TempSize data store from memory, and then reconnecting to it. See data store” on page 95 Moving between 32-bit and 64-bit data stores The internal format of a 32-bit TimesTen data store differs from that of a 64-bit data store.
  • Page 110 the steps outlined in page 101. If you need to upgrade two or more data stores that are replicating to each other, you must perform a few extra steps in order to ensure that replication will continue to operate during and after the upgrade. For example, to migrate two replicating data stores, machine subscriberhost...
  • Page 111 Now upgrade data store Perform the following steps: On the machine subscriberhost to stop the replication daemon: ttAdmin -repStop subscriber1 Use the 5.1 release’s ttDestroy , where the data store’s files are located in the directory subscriber1 data_store_path ttDestroy data_store_path/subscriber1 Use the 7.0 release’s ttRepAdmin duplicate data store...

  • Page 112: Performing An Online Upgrade With Replication

    Performing an online upgrade with replication “Performing an offline upgrade” on page 97 perform various maintenance operations on TimesTen data stores that require that all applications be stopped. This section describes how to use the TimesTen replication feature to perform online upgrades for applications that require continuous data availability.
  • Page 113 release data store using reconnecting all applications to the upgraded data store. Note: The data store tables, cannot be used with online upgrades. The general steps in an online upgrade include: • Disconnect all applications from the data store to be upgraded. •...
  • Page 114 Disconnect all applications from the upgrade data store. Wait for updates to propagate to the active system. Stop replication. Back up the data store with ttMigrate Stop the TimesTen daemon for the old release of TimesTen. Install the new release of TimesTen. Create a Data Source Name for the upgraded data store on the new TimesTen release, using the ODBC...

  • Page 115: Limitations

    Reconnect all applications to the upgrade data store. After the above procedures have been carried out on the upgrade system, the active system can be upgraded using the same steps. Limitations Online upgrades can be performed only on data stores for which all the user tables meet the replication requirements.

  • Page 116: Online Upgrade Example

    Online upgrade example This section describes how to do an online upgrade of two bi- directionally replicated TimesTen data stores, using a concrete example. We’ll refer to the two TimesTen systems being upgraded as the upgrade system, on which TimesTen will be upgraded along with the data store, and the active system, which will remain operational and connected to the application for the duration of the upgrade.
  • Page 117 Follow the steps listed here in the order they are presented. The online upgrade procedures are: Step Upgrade System ttIsql to alter the replication scheme repscheme replication port numbers so that the data stores can talk across releases: Command> call ttRepStop; Command>...
  • Page 118 Step Upgrade System Wait for all replication updates to be sent to the data store can verify that all updates have been sent by applying a recognizable update to a table reserved for that purpose on the data store When the update appears in the data store , you know that all active...
  • Page 119 Step Upgrade System ttMigrate to back up the data store . If the data store is upgrade very large, this step could take a significant amount of time. If sufficient disk space is free on the file system, the following /backup ttMigrate command can be used:...
  • Page 120 Step Upgrade System ttMigrate to load the backup created in Step 6 into a new version of the data store upgrade ttMigrate -r "DSN=upgrade;AutoCreate=0" /backup/upgrade.dat If the data store is temporary (Temporary=1), first use -ramLoad ttAdmin -ramLoad upgrade Note: In this step, you must use the ttMigrate utility supplied with the new release of TimesTen to which...

  • Page 121: Performing A Client/Server Online Upgrade From A Timesten Version Prior To

    Step Upgrade System ttAdmin to start the replication agent on the new data store and to begin sending updates to the data store active ttAdmin -repStart upgrade Verify that the data store receiving updates from can verify that updates have been sent by applying a recognizable update to a table reserved for that purpose in the data store...

  • Page 122: Limitations

    release of TimesTen. For example, a 5.0 client can connect to a 7.0 Server DSN. Note: Applications linked to newer TimesTen clients cannot connect to a Server DSN of any older releases. For example, a 5.1 client cannot connect to a 5.0 Server DSN. Note: For security reasons, client/server communication is not normally allowed between TimesTen 7.0 and previous versions.
  • Page 123 The TTCONNECTINI file at the TimesTen 5.1.x client machine contains: [my_server_51] Network_Address=my_server TCP_PORT=15102 Because TCP_PORT 5.1 server dynamically loads the correct driver for the server DSN. .odbc.ini [client_dsn_51] Description=Access to my_server_dsn51 on host "server" TTC_SERVER= my_server_51 TTC_SERVER_DSN= my_server_dsn51 [client_dsn_70] Description= Access to my_server_dsn70 on host "server" TTC_SERVER= my_server_50 TTC_SERVER_DSN= my_server_dsn70 DRIVER=install_dir_70/lib/libtten.so...

  • Page 124: Performing A Client/Server Online Upgrade From Timesten Version 6.0 And Above

    Performing a Client/Server online upgrade from TimesTen version 6.0 and above As of TimesTen 7.0, TimesTen Server is able to talk directly to all user applications linked with TimesTen Client ODBC driver version 6.0 or higher. This makes the procedures for upgrading a TimesTen Client/ Server installation much simpler.

  • Page 125: Client/Server Online Upgrade With Continuous Access To The Data Store

    ttMigrate version. See for an example of this procedure. Start the new version of TimesTen Server, if you have not already. The client applications now have access to the upgraded data stores. Note: Since both versions have TimesTen Server have been configured to listen on the same port in this procedure, if you wish to restart the old version you must first configure it to listen on a different port.
  • Page 126 These tables do not take up much space and are helpful when debugging upgrade problems. However, you can drop these tables if you do not experience problems with replication after running ttMigrate. Example 3.1 For example, after two migrations, the data store might contain tables which look like this: TTREP_SCHEMA_VERSION_004.REPELEMENTS TTREP_SCHEMA_VERSION_004.REPLICATIONS...
  • Page 127 Index Numerics 64-bit platforms, supported Access Control authentication Cache Connect Client/Server daemon home directory daemon port directories and files GroupRestrict instance home directory introduction limitations password file privileges Replication security TimesTen instance administrator TimesTen instance users users 19, 21, 22 installation uninstalling batch installation...
  • Page 128 files GroupRestrict help HP-UX in-place upgrade informational messages installation Oracle TimesTen In-Memory Database Installation Guide .odbc.ini documentation driver, verifying installation on Windows enabling large files header makefiles ODBCINI environment 75, 76 variable online help Access Control online 19, 21, 22 installation supported environment uninstalling...
  • Page 129 to a new patch release names instances non-root installation limitations prerequisites ODBC installation ODBCINI file 75, 76 environment variable 93, 97 off-line upgrade on-line upgrade limitations requirements online documentation online help Oracle Connect Administrator web server configuration working with ORACLE_HOME environment 35, 77 variable PASSWORD_FILE Web Server...
  • Page 130 TimesTen daemon TimesTen instance administrator TimesTen instance users TimesTen registry TimesTen Server timestend process timestend.pid file TMP environment variable TMPDIR environment variable troubleshooting Tru64 ttBackup ttDaemonLog ttDestroy ttIsql ttMigrate TTREP_SCHEMA_VERSION ttRestore ttVersion utility uninstalling UNIX unloading a data store Oracle TimesTen In-Memory Database Installation Guide on AIX external user internal user...

This manual is also suitable for:

Timesten in-memory database 7.0

Table of Contents