Oracle TimesTen In-Memory Database Installation Guide

Connect Administrator, a web-based interface for creating cachegroups.TimesTen documentation is available on the product CD-ROM and onthe TimesTen web site: http://www.timesten.com.Background readingFor a conceptual overview and JDBC development information, see: Hamilton, Cattell, Fisher. JDBC Database Access with Java.Reading, MA: Addison Wesley. 1998.For a Java reference, see: Horstmann, Cornell. Core Java. Palo Alto, CA: Sun MicrosystemsPress. 1999. For the JDBC API specification, refer to java.sql package in theappropriate Java Platform API Specification. If you are working with JDK 1.2, refer to the Java 2 Platform APIspecification at: x.html If you are working with JDK 1.3, refer to the Java 2 Platform APIspecification at: http://java.sun.com/j2se/1.3/docs/api/index.html If you are working with JDK 1.4, refer to the Java 2 Platform APIspecification at: http://java.sun.com/j2se/1.4/docs/api/index.html Siple, Matthew. The Complete Guide to Java DatabaseProgramming: JDBC, ODBC and SQL. McGraw-Hill. 1997.An extensive list of books about ODBC and SQL is in the MicrosoftODBC manual included in your developer’s kit. In addition to thisguide, your developer’s kit includes the appropriate ODBC manual foryour platform:– Microsoft ODBC 3.0 Programmer’s Reference and SDK Guideprovides all relevant information on ODBC for Windowsdevelopers.– Microsoft ODBC 2.0 Programmer’s Reference and SDK Guide,included online in PDF format, provides information on ODBCfor UNIX developers.For a conceptual overview and programming how-to of ODBC, see:2 Oracle TimesTen In-Memory Database Installation and Configuration Guide

Sanders, Roger E. ODBC 3.5 Developer's Guide (McGraw-HillSeries On Data Warehousing and Data Management); McGraw-Hill.1999 Signore, Robert / Stegman, Michael O. / et al. ODBC Solution: OpenDatabase Connectivity in Distributed Environments: Mcgraw-hillSeries On Computer Communications; McGraw Hill. 1995For a review of SQL, see: Melton, Jim and Simon, Alan R. Understanding the New SQL: AComplete Guide. San Francisco, CA: Morgan Kaufmann Publishers.1993. Groff, James R. / Weinberg, Paul N. SQL: The Complete Reference.McGraw-Hill. /1999For information on Unicode, see: The Unicode Consortium, The Unicode Standard, Version 4.0,Addison-Wesley, 2003. The Unicode Consortium Home Page at http://www.unicode.orgConventions used in this guideTimesTen supports multiple platforms. Unless otherwise indicated, theinformation in this guide applies to all supported platforms. The termWindows refers to Windows 2000, Windows XP and Windows Server2003. The term UNIX refers to Solaris, Linux, HP-UX, Tru64 and AIX.TimesTen documentation uses these typographical conventions:If you see.It means.code fontCode examples, filenames, and pathnames.For example, the .odbc.ini.ttconnect.ini file.italic codefontA variable in a code example that you must replace.For example:Driver install dir/lib/libtten.slReplace install dir with the path of yourTimesTen installation directory.About this Guide3

TimesTen documentation uses these conventions in command lineexamples and descriptions:If you see.It means.fixed widthitalicsVariable; must be replaced[ ]Square brackets indicate that an item in a command lineis optional.{ }Curly braces indicated that you must choose one of theitems separated by a vertical bar ( ) in a command line. A vertical bar (or pipe) separates arguments that you mayuse more than one argument on a single command line.An ellipsis (. . .) after an argument indicates that you mayuse more than one argument on a single command line.%The percent sign indicates the UNIX shell prompt.#The number (or pound) sign indicates the UNIX rootprompt.TimesTen documentation uses these variables to identify path, file anduser names:If you see.It means.install dirThe path that represents the directory where the currentrelease of TimesTen is installed.TTinstanceThe instance name for your specific installation ofTimesTen. Each installation of TimesTen must beidentified at install time with a unique alphanumericinstance name. This name appears in the install path. Theinstance name “giraffe” is used in examples in this guide.bits or bbTwo digits, either 32 or 64, that represent either the 32-bitor 64-bit operating system.release or rrTwo digits that represent the first two digits of the currentTimesTen release number, with or without a dot. Forexample, 60 or 5.0 represents TimesTen Release 5.0.jdk versionTwo digits that represent the version number of the majorJDK release. For example 12 for versions of jdk1.2.4 Oracle TimesTen In-Memory Database Installation and Configuration Guide

timestenA sample name for the TimesTen instance administrator.You can use any legal user name as the TimesTenadministrator. On Windows the TimesTen instanceadministrator must be a member of the Administratorsgroup. Each TimesTen instance can have a uniqueinstance administrator name.DSNThe data source name.Technical SupportFor information about obtaining technical support for TimesTenproducts, go to the following Web Email: timesten-support us@oracle.comAbout this Guide5

6 Oracle TimesTen In-Memory Database Installation and Configuration Guide

1Access Control and non-rootinstallationsIntroductionNon-root installationsIn previous releases of TimesTen, only the user root could installTimesTen. This release of TimesTen allows a user to optionally installTimesTen as a user other than root on UNIX systems. This feature isnot available on Windows systems.Access ControlIn addition, this release of TimesTen optionally allows you to installTimesTen with a layer of security, which throughout the TimesTendocumentation set and in the installation scripts is referred to as “AccessControl.”The Access Control feature of TimesTen provides an environment ofbasic control for applications that use the defined privileges. AccessControl does not provide definitive security for all processes that mightbe able to access the data store. For example, this feature does notprotect the data store from user processes that may have sufficientprivileges to connect to the data store when in memory or that canaccess files on disk that are associated with the data store, such as logfiles and checkpoint files.In TimesTen, privileges are granted on a instance wide-basis. Privilegesapply to all data stores in a given TimesTen instance or installation.Your options for installing TimesTen, now include the following:Non-root userRoot UserAccess Control enabledAccess Control enabledAccess Control not enabledAccess Control not enabled7

Limitations of Access Control and non-root installsGeneralRegardless of whether you install TimesTen as root or as a non-rootuser, you must decide whether to enable Access Control at the time youinstall TimesTen. It cannot be enabled or disabled after installation.If Access Control is to be enabled, installation itself must be performedby the chosen instance administrator user. The instance administratorowns all files in the installation directory tree. Only the instanceadministrator is allowed to install and administer the TimesTeninstance. See “TimesTen instance administrator” on page 10. AllTimesTen daemon processes are owned by the instance administrator.Prior to installing TimesTen as non-root, certain tasks must beperformed by the user root. Those tasks are outlined in “Prerequisitesfor non-root installations and Access Control on UNIX systems” onpage 38.Cache ConnectFor Cache Connect, the TimesTen internal user must match the Oracleuser. External Client/Server users must match the Oracle user. If you areusing the Cache Connect Administrator interface, the user must be aninternal TimesTen user.ReplicationIf Access Control is enabled, replication daemon administration andreplication schema changes are restricted to users having the ADMINprivilege. See “Privileges” on page 14.Changes applied to a replication subscriber are made regardless ofaccess controls present on the subscriber.Instance user configuration commands are not replicated.Client/ServerUse of Access Control requires that the Client/Server Authenticateattribute be turned on.To use Access Control with Client/Server applications, when the user isidentified externally, the Client and the Server must be on the samemachine. Remote Client/Server access is only supported by TimesTenwhen Access Control is enabled, if the user is a TimesTen internal user.8 Oracle TimesTen In-Memory Database Installation and Configuration Guide

TimesTen ignores the values of UID, PWD and PWDCrypt if specifiedin the Server DSN. The user name and password must be explicitlydeclared on the Client side.If PWD or PWDCrypt is specified in Client/Server applications,TimesTen assumes that the user is internally identified, otherwiseTimesTen assumes that the user is externally identified andauthenticated by the operating system.Migrating from previous releasesIf you do not enable Access Control and you install as user root, you donot need to make any changes to your application or the installation andadministration of TimesTen to use this release.If you plan to install as a non-root user, but do not plan to enable AccessControl, see “Prerequisites for non-root installations and Access Controlon UNIX systems” on page 38.If you plan to install with Access Control enabled, you will need tochange your application to support authentication of users for specificoperations. See “Authenticating users and privileges” on page 13. Fordetails on each operation, see the Oracle TimesTen In-MemoryDatabase API and SQL Reference Guide and the Oracle TimesTen InMemory Database Operations Guide.Root accessInstance startup/shutdownPermission to start and stop the main TimesTen daemon is restricted tothe TimesTen instance administrator. To provide a uniform interface forinstance operation, the following new functionality has been added tothe ttDaemonAdmin utility:To start the TimesTen main daemon:% ttDaemonAdmin -startTo stop an instance:% ttDaemonAdmin -stopInstance data storeA DSN for a minimal instance-wide data store is defined by TimesTenat install time to guarantee that TimesTen always has something withwhich to connect. The instance DSN looks like:Access Control and non-root installations9

DSN TT instanceDataStore TIMESTEN INFODIR/TT instanceDriver TIMESTEN DIR/lib/libtten.soThis data store gets special treatment from the daemon, and has specialaccess restrictions placed on it. Regular users may connect to theinstance data store, but are restricted to SELECT privileges, except thatany user can change their own password.TimesTen usersTimesTen instance administratorThe owner of a TimesTen installation is the “TimesTen instanceadministrator.” Only a member of the TimesTen administrators groupcan install and administer TimesTen. The user installing the instanceautomatically becomes the administrator for that instance. Only thatuser may start or stop the instance, and only that user may administerthe users in the instance. Use of the GroupRestrict attribute is requiredfor all data stores in an instance using Access Control. Therefore theinstance administrator must have corresponding group membership.Though a specific user name is not required, we recommend the name“timesten.” All examples in the TimesTen documentation set use thename timesten to represent the instance administrator.For details on establishing the TimesTen instance administrators group,see “Create the TimesTen instance administrators group” on page 38.On Windows systems, the user System automatically becomes theTimesTen instance administrator when Access Control is selected atinstall time.On UNIX systems, the user root becomes the TimesTen instanceadministrator when Access Control is selected at install time and theinstallation is performed by user root.TimesTen instance usersTimesTen instance users are user names that have been identified to theinstance. They are defined at the instance level and apply to all datastores in the instance. Initially, only one user name is known to theinstance: the instance administrator.Only the instance administrator has permission to create or delete users.Individual users have permission to change their own passwords.10 Oracle TimesTen In-Memory Database Installation and Configuration Guide

Instance users may have internal user names or external user names.Internal userA user name that has been defined within the TimesTen instance isreferred to as an “internal user.” It has no significance outside of theparticular instance of TimesTen in which it was defined. Internal usersare authenticated by the TimesTen instance. See "CREATE USER"inthe Oracle TimesTen In-Memory Database API and SQL ReferenceGuide. TimesTen user names (ODBC UID attributes) are automaticallyconverted to upper case (case insensitive).External userA user name that is identified by the operating system or some otherexternal mechanism is referred to as an “external user.” In this releaseonly the operating system user name is recognized as an external user.External users are assumed to have been authenticated by their nativemechanism. See "CREATE USER"in the Oracle TimesTen In-MemoryDatabase API and SQL Reference Guide. A password is not required byTimesTen since the user was authenticated by the operating system atlogin time.UNIX external user names are case sensitive. Windows external usernames are not. When connecting from UNIX platforms, TimesTenautomatically converts the external user name to upper case, rendering itcase insensitive.The PWDCrypt attribute provides a way to deal with the specialcharacters and case sensitivity used in passwords that might createdifficulties if specified in cleartext PWD attributes.Before installationSeveral steps must be taken to prepare a machine for TimesTeninstallation. These steps are needed once per machine and require rootpermission. As in previous releases, kernel parameters must beadjusted.See “Installation prerequisites” on page 22. This release ofTimesTen requires that additional steps be performed prior toinstallation if either Access Control is to be enabled or you plan toinstall as non-root.TimesTen administrators groupAn operating system group needs to be defined for those users who willbe allowed to install and administer TimesTen instances. This can be anAccess Control and non-root installations11

existing group, but we suggest that a group named “timesten” be createdspecifically for this purpose. “Create the TimesTen instanceadministrators group” on page 38. The member of the TimesTenadministrators group who installs TimesTen becomes the TimesTeninstance administrator.Instance registry directoryTimesTen maintains a “registry” of all TimesTen instances installed ona given machine. The instance registry itself is not required foroperation. It is only accessed during installation and uninstallation.TimesTen patches the information it contains into the libraries andexecutables of the instances, where it becomes an integral part ofoperation. The “registry” is only accessible by the TimesTen installationscripts. It is not accessible by TimesTen users or the individual who isinstalling TimesTen.On Unix platforms, the instance registry is located in /etc/TimesTen.Initial creation of the /etc/TimesTen directory requires root access.Creation of this directory is a once per machine, pre-installation step.See “Create the TimesTen registry” on page 39. The disk space requiredfor the files in this directory is less than 2k bytes.On Windows the instance registry is contained in the operating systemregistry. No action is required by users or the individual who isinstalling TimesTen.Installation directories, files and the daemon portInstallation itself must be performed by the chosen instanceadministrator user. The instance administrator owns all files in theinstallation directory tree. Only the instance administrator will beallowed to operate the instance.Installation directoriesThe installer suggests default destination directories, based on the userperforming the installation.Instance home directoryThe instance may be installed in any directory to which the instanceadministrator has sufficient permission.On Unix, the installer suggests /opt/TimesTen/tt51 as in previousreleases.12 Oracle TimesTen In-Memory Database Installation and Configuration Guide

On Windows, the installer suggests the directory pattern as used inprevious releases of TimesTen, C:\TimesTen\tt51The TimesTen documentation refers to the directory as install dir.Daemon home directoryThe “home” or current working directory of the running daemon isknown as the daemon home directory. This directory must be owned bythe instance administrator, with rwxr-xr-x permissions. The daemonverifies this when it starts up. This directory can be anywhere on a localdrive, but cannot be on an NFS mounted file system.On UNIX, the installer suggests the use of install dir/info ifinstalled as non-root or /var/TimesTen/tt51 as in previous releases ifrunning as root.On Windows, the install dir\srv\info directory is used for thispurpose, just as in previous releases.Password fileIf access control is selected at installation time, user and password datais stored in the file install dir/info/ttpasswd.Initially, this fi

Sanders, Roger E. ODBC 3.5 Developer's Guide (McGraw-Hill Series On Data Warehousing and Data Management); McGraw-Hill. 1999 Signore, Robert / Stegman, Michael O. / et al. ODBC Solution: Open Database Connectivity in Distributed Environments: Mcgraw-hill Series On Computer Communications;