Manuale d’uso / di manutenzione del prodotto B31679-01 del fabbricante Oracle
Vai alla pagina of 130
Oracle T imesT en In-Memory Dat abase Inst allation Guide Release 7.0 B31679-01 For last-minute up dates, see the TimesT en release notes..
Copyright ©199 6, 2007, Oracl e. All rights reserved . ALL SOFTW ARE AND DOCUMENT A TION (WHETHER IN HARD COPY OR ELECTRONIC FORM) ENCLOSED AND ON THE COMP ACT DISC(S) ARE SUBJECT T O THE LICENS E AGREEMENT . The documentation stored on the co mp act disc(s) may be pri nted by licensee for licensee’ s internal us e only .
iii Contents About this Guide T imesT en documentation . . . . . . . . . . . . . . . . . . . . . 1 Background reading . . . . . . . . . . . . . . . . . . . . . . . 2 Conventions used in this guide . . . . . . . . . . . . . . . . . . . 3 T echnical Support .
iv Oracle T im esT en In-Memory Database In stallation Guide Platform support . . . . . . . . . . . . . . . . . . . . . . . 19 JDK support . . . . . . . . . . . . . . . . . . . . . . . . . 20 Client/Server configurations . . . . . . . . . . . . . . . .
Contents v Installing TimesT en on HP-UX Memory W indows . . . . . . . . . . . 5 4 Use a separate instance for each memory window . . . . . . . . . . 54 Using T imesT en in a memory window . . . . . . . . . . . . . . . 55 Address Space Considerations .
vi Oracle T im esT en In-Memory Database In stallation Guide 3 Dat a Store Upgrades Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . 87 Data store compatibility . . . . . . . . . . . . . . . . . . . . 87 Data type compatibility . . . .
Contents vii Index.
viii Oracle T imesT en In-Memory Database Install ation Guide.
1 About this Guide This document contains all necessa ry information fo r installing the Oracle T imesT en® In-Memory Database (T imesT en) Data Manager , Client and Server components. The T imesT en CD contains a REA DME.TXT file that hold s th e release notes.
2 Oracle T imesT en In-Memory Database Installation Gui de Background reading For a Java reference, see: • Horstmann, Cay and Gary Cornell. Core Java(TM) 2, Volume I- - Fundamentals (7th Editi on) (Core Java 2) . Prentice Hall P TR; 7 edition (August 17, 2004).
About this Gui de 3 • Microsoft ODBC 2.0 Progra mmer’s Reference and SDK Guide , included online in PDF format, provides inform atio n on ODBC for UNIX developers. For a conceptual overview and pr ogramming ho w-t o of ODB C, see: • Kyle Geiger .
4 Oracle T imesT en In-Memory Database Installation Gui de T imesT en documentation uses thes e conventions in command line examples and descriptions: T imesT en docum entat ion uses these variables to identify path, fi le and user names: If you see..
About this Gui de 5 T echnical Support For information about obtaini ng technical support for T imesT en products, go to the followi ng W eb address: http://www .oracle.com/ support/contact.html timesten A sample name fo r the T imesT en instance admin istrator .
6 Oracle T imesT en In-Memory Database Installation Gui de.
7 1 Access Contr ol Introduction Access Control W ith T imesT en you can optio nally install a layer of internal security , which throughout the TimesT en docum entation set and in the installation scripts is referred to as “Access Control.
8 Oracle T imesT en In-Memory Database Installation Guide Cache Connect For Cache Connect, the T imesT en inte rnal user must match the Oracle user . External Clie nt/Server users mu st match the Oracle user . If you are using the Cache Connect Administrato r interface, the user must be an internal T imesT en user .
Access Contr ol 9 % ttDaemonAdm in -start T o stop an instance: % ttDaemonAdm in -stop Inst ance data store A DSN for a minimal instance-w ide data sto re is defined by T imesT en at install time to guarantee that T i mesT en always has something wit h which to connect.
10 Oracle T imesT en In-Memory Da tabase Installation G uide Note: All examples in the T imesT en documentation set use the name timesten to represent th e in stance administrator . For details on establis hing the T ime sT en instance admini strators group, see “Create the TimesTen instance ad ministrators group” on page 37 .
Access Contr ol 11 automatically converts the external us er name to upper case, rendering it case insensitive. The PWDCrypt attribute allows you to encr ypt a password rather to use cleartext passwor.
12 Oracle T imesT en In-Memory Da tabase Installation G uide Inst allation dir ectories, files and the daemon port Installation of T i mesT en must be performed by the chosen instance administrator user . The instance admi nistrator owns all files in the installation di recto ry tree.
Access Contr ol 13 been selected. If this file is missing , an error occurs after Access Control is enabled. This file is readable and writable onl y by the instance admi nistrator . Passwords are stored in encrypted form and are not known to the instance administrator as one way hashes, so they cannot be recovered.
14 Oracle T imesT en In-Memory Da tabase Installation G uide Maint aining users and privileges T imesT en allows the instance admini strator to create, drop and alter users when Access Control is enable d. It also allows the instance administrato r to grant and revoke pr iv ileges fo r users.
Access Contr ol 15 All other changes to the T imesT en instance can only be made by uninstalling an d re-installing the sam e or a differently release of T imesT en. (See “Changing the daemon port number on UNIX” on page 39 and “ORACLE_HOME environment variable” on pag e 77 .
16 Oracle T imesT en In-Memory Da tabase Installation G uide.
17 2 T imesT en Installation This chapter contains configuration informati on that you will need to review before installin g TimesT en on your system, in the sections: • Platforms and configuration.
18 Oracle T imesT en In-Memory Da tabase Installation G uide • Building and runni ng the dem o appl ications • V iewing t he online document ation Finally , this chapter contai ns inform ation tha.
T imesT en Installation 19 Plat forms and configurations Plat form support T imes T en Data Mana ger and T imesT en Client/Server are supp ort ed in the following environments:. Environ ment 32-bit 64 -bit Microsof t Windows 2000, W indows XP and Windows Ser ver 2003 for Intel IA-32 and EM64T and AM D6 4 CPUs.
20 Oracle T imesT en In-Memory Da tabase Installation G uide JDK support Note: T i mesT en supports the Sun JVM and the BEA W ebLogic JRockit JVM for Linux and W indows x86 system s. For details on JRockit, see www.bea.co m . T imesT en supports the fo llo wing JDKs on the specified platforms: Environment JDK 1.
T imesT en Installation 21 Client/Server configurations A T im esT en client on any support ed platform can connect to a T imesT en server on any platform where T i mesT en is support e d. A T imesT en 6.0 client can connect to a 6.0 TimesT en Server of any patch level.
22 Oracle T imesT en In-Memory Da tabase Installation G uide Cache Connect is supported on the 32-bit and 64-bit platforms specified in this table: Replication configurations T imesT en-t o-T imesT en Replicatio n is supported on ly between identical platforms and bit-levels.
T imesT en Installation 23 Inst allation inst ances On UNIX, you can install m ore than one instance of any T im e sT en release. By default, the instan ce name for this release is tt70.
24 Oracle T imesT en In-Memory Da tabase Installation G uide Choosing the appropria te T imesT en component s T imesT en allows you to select the components of T imesT en that you wish to install.
T imesT en Installation 25 Inst allation prerequisites Before installi ng T imesT en, make su re the appropriate requirements are met for your operating system. On platforms where JDBC is su pporte d you mu st have the appropriate version of the JDK installed on your m achine to use JDBC.
26 Oracle T imesT en In-Memory Da tabase Installation G uide Other Client/ Server Settings The maximum number of concurren t IPC connect ion s to a T im e sT en Server allowed by T imesT en is 9,999. However , system lim its can take precedence on the number of connec tions to a single DSN.
T imesT en Installation 27 3. Scro ll do wn the list of parameters to semmns and change its value to a minimum of 4096 or greater . 4. For HP-UX 11i systems, also scroll down the list of parameters to shmmax and change its value to a max imum of 0x40000000.
28 Oracle T imesT en In-Memory Da tabase Installation G uide The C developmen t tools are required if native developm ent will be done on the machine. Large pa ges Lar ge pages can be enabled only if the running Li nux kernel supports large p ages (also called “huge pages” in Linux community ).
T imesT en Installation 29 When T imesT en uses lar ge pages, the HugeP ages_Free fi le in /proc/ meminfo changes. Semaphores T o view existing kernel parameter settings, log in as roo t and use: # /sbin/sysct l -a Shared memory T o inc rease the shared memory si ze to 2048 MB, for example, as root , edit the /etc/s ysctl.
30 Oracle T imesT en In-Memory Da tabase Installation G uide For Red Hat 3.0, install: compat-lib stdc++-7.3- 2.96.123 For Red Hat 4.0, install: compat-lib stdc++-296- 2.96.132.7 .2 These packages can be install either using the rpm com mand or by using the Red Hat GUI installer found in “Legacy So ftw are Development.
T imesT en Installation 31 ryps3# modloa d /kernel/sys /semsys ryps3# modloa d /kernel/sys /shmsys Increase number of semaphores For Solaris 10 syst ems, the defau lt semaphore settings should be suf ficient without entries in /etc/syst em . On other Solaris systems, you may need to increase the number of semaphores.
32 Oracle T imesT en In-Memory Da tabase Installation G uide access 12 data stores, add the following line to /etc/system and reboot before using T imesT en: set shmsys :shminfo_sh mseg=12 Other chang.
T imesT en Installation 33 Replication For replication, TCP se nd and receive buffers should be increased to a minimum of 512KB. Y ou may need to embed the following commands into a script that can be.
34 Oracle T imesT en In-Memory Da tabase Installation G uide T o increase the maximum data segm ent (malloc space) a process may use, change the kernel values per_proc_data_s ize and max_per_pr oc_data_siz e For example, to change all of these values to 10GB: 1.
T imesT en Installation 35 The temporary directory is operating system-depende nt. Usuall y it is located in these directories: • On W indows, C:Docu ments and Settings%U SERNAME%L ocal SettingsT em.
36 Oracle T imesT en In-Memory Da tabase Installation G uide segments are ownership and permissions restricted to that of a particular operating system group. This mo de only works if T imesT en is installed and running as root . See the Oracle T imesT en In-Memory Dat abase API Refer ence Guide .
T imesT en Installation 37 Prerequisites for non-root inst allations on UNIX systems As discussed in Chapter 1, “Access Control,” on UNIX systems, you can install T imesT en as a non-root us er . This entire section applies to all UNIX platforms on which T ime sT en is supported, unless oth erwise indicated.
38 Oracle T imesT en In-Memory Da tabase Installation G uide # setprivgrp ti mesten MLOCK The getprivgrp command can be used to check the privileges of a group: $ getprivgrp ti mesten timesten: MLO CK Note: On Linu x and Tru64 systems, root privileges are required to use MemoryLock at tribute.
T imesT en Installation 39 This step is o nly necessary if you want the T imesT en instance to start each time the machine is rebooted. Note: If y ou install these scripts into your system directory ,.
40 Oracle T imesT en In-Memory Da tabase Installation G uide See the TimesTen Developer’s Guide for more information about using Ti m e s T e n . Inst alling T imesT en on Windows systems This section discusses installation and related issues for W indow s systems.
T imesT en Installation 41 By default, Access Control is not enabled. See Chapter 1, “Access Control” for more details. Custom setup also lets you choose ot her custo m options. The installation program adds Time sT en directories to the system environment vari ables LIB and IN CLUDE.
42 Oracle T imesT en In-Memory Da tabase Installation G uide V erifying inst allation T o verify that T imesT en has been properly installed, check that the driver files are available and that the services are running: 1. Check that the T imesT en 7.0 St art menu shortcut has been added to the W indows D esktop St a r t > P r o g r a m s menu.
T imesT en Installation 43 The ODBC Administrator attempts to connect to the TimesT en Server and display a message to let you know if it was successful. When you click this button, the T imesT en Client veri fies that : • ODBC, W indows sockets, and the T i mesT en Client are installed on the machine.
44 Oracle T imesT en In-Memory Da tabase Installation G uide 1. On the W indows desktop, choose S tart > Settings > Contro l Panel > Administrative T ools > Services. This displays all currently available services. 2. Select TimesT en Data Manager 7.
T imesT en Installation 45 Inst alling TimesT en T o install T im esT en on your Solaris system , follow these steps: 1. Log in as the T imesT en instance administrator if installing as non-ro ot, or log in as user root.
46 Oracle T imesT en In-Memory Da tabase Installation G uide In addition, setup.sh also accepts these options: The CD contains tar files of T imesT en. If the setup script cannot find the tar files to extract from, it prompts you for their location. 4.
T imesT en Installation 47 • On 64-bit systems, pro mpts you to install on e of the fo llowing releases: – 32-bit (default) – 64-bit • Promp ts you to: – Install a new instance – Upgrade an existing instance (Thi s op tion allows you to incrementally install the Cache Connect option.
48 Oracle T imesT en In-Memory Da tabase Installation G uide • Copies the daemo n scripts into the appropriate directories. • If installed by user root , configures the system to start the daemon when the system boots. • Creates the directory where data stores created by the T imesT en demo applicatio ns will reside.
T imesT en Installation 49 T o stop the daemon manually , use the utility command: ttDaemonAd min -stop T o start the daemon manua lly , use the utility command: ttDaemonAd min -start Uninst alling TimesT en T o uninstall all T imesT en component s: 1.
50 Oracle T imesT en In-Memory Da tabase Installation G uide # mkdir /cdrom Mount the CD-ROM, as follows: • If your system is configured to mount the CD-ROM at /cdrom , type: # /etc/mount /c drom .
T imesT en Installation 51 Specify the option at th e end, ou tside th e quotation marks. In addi tio n, setup.sh also accepts these options: The CD contains tar files of T imesT en. If the setup script cannot find the tar files to extract from, it prompts you for their location.
52 Oracle T imesT en In-Memory Da tabase Installation G uide • On 64-bit systems, pro mpt s you to install one of the follow ing releases: – 32-bit (default) – 64-bit • Promp ts you to: – Install a new instance – Upgrade an existing instance (Thi s op tion allows you to incrementally install the Cache Connect option.
T imesT en Installation 53 • Copies the daemo n scripts in to the appropriate directories. • If installed by user root , configures the system to start the daemon when the system boots. • Creates the directory where data stores created by the T imesT en demo applicatio ns will reside.
54 Oracle T imesT en In-Memory Da tabase Installation G uide If you inst alled T imesT en as root, th e daem on startup file on H P-UX is: /etc/rc.co nfig.
T imesT en Installation 55 <instance> command to determine which port is being used by the instance. Using T i mesT en in a memory window In order to use a T imesT en instance running in a memory win dow , you must launch y our application usi ng the HP-UX setmemwindow(1M) command.
56 Oracle T imesT en In-Memory Da tabase Installation G uide application SHMEM_MAGIC may result with an Invalid Ar gument error ( EINVAL, errno=22 ) when attempting to connect to T i mesT en. If a connection is made to a data store with ExclAccess=1 , then memo ry windows wi ll not be used.
T imesT en Installation 57 • Not enough co re ( ENOMEM, errno=12 ) indicates a problem allocating the request ed amo unt of shared memory . Can you attach with small PermSize and Te m p S i z e attributes? • Shared memory can be fragmented. Sometimes, you can attach with increasingly larger segments until you allocate what you want.
58 Oracle T imesT en In-Memory Da tabase Installation G uide # mount / usr/cdrom/TimesT en7.0 After the CD-ROM setup is complete, yo u can install TimesT en as follows: 5. Still logged in as user root or the T imesT en instance administrator , run the setup script by typing: # cd mount_dir # .
T imesT en Installation 59 The CD contains tar files of T imesT en. If the setu p script cannot find the tar files to extract from, it prompts you for their location. 6. Enter your response to th e setup script p rompts. Note: T o install or uninstal l T imesT en with out hav ing to respond to prompts, use the -b atch flag with the setup.
60 Oracle T imesT en In-Memory Da tabase Installation G uide – Data Manager only – Client o nly • Prompts you for the locati on of your T i mesT en installation and specific files, if insta lling as a non-root user . • Prompts you to specify the daemon port num ber .
T imesT en Installation 61 W orking with the TimesT en daemon and server The T imesT en daemon starts automa tically when the operating system is booted and operates continually in the background .
62 Oracle T imesT en In-Memory Da tabase Installation G uide Inst alling T imesT en on Linux systems This section discusses installation and some related topics for Linux systems. Note: Befo re beginning installation, be sure that the prerequisites defined in “Installation prerequisi tes” on page 25 have been met.
T imesT en Installation 63 removes all files it had installed . In additi on, setup.sh also accepts these options: The CD contains tar files of T imesT en. If the setup script cannot find the tar files to extract from, it prompts you for their location.
64 Oracle T imesT en In-Memory Da tabase Installation G uide minor version numbers of the T imesT en release must match exactly .) – Display information abou t an existing instance or – Quit the installation. • Prompts you to chose the default instance name or chose a name for your T imesT en instance.
T imesT en Installation 65 • If there are other instances of th e same patch release of T imesT en installed on th e same machine, prompts you to provi de a unique po rt to be used by the T imesT en daemon. • If the T imesT en Server is being installe d, prompts you t o configure the Server: server name, port number and logging op tion s .
66 Oracle T imesT en In-Memory Da tabase Installation G uide 1. Log in as the T imesT en instance administrator if you installed as non- root, or log in as user root.
T imesT en Installation 67 • Y ou can run the setup script with the opti on -ins tall or - uninstall (default is - in stall ). When you use the - uninstal l option, the scri pt stop s the daemon if it is ru nning and removes all files it had installed.
68 Oracle T imesT en In-Memory Da tabase Installation G uide release are assigned default answ ers and may produce unexpected results when batch files from different versions are used.
T imesT en Installation 69 • Copies the daemo n scripts in to the appropriate directories. • If installed by user root , configures the system to start the daemon when the system boots. • Creates the directory where data stores created by the T imesT en demo applicatio ns will reside.
70 Oracle T imesT en In-Memory Da tabase Installation G uide T o start the daemon manua lly , use the utility command: ttDaemonAd min -start Uninst alling TimesT en T o uninstall all T imesT en compo nent s: 1. Log in as the T imesT en instance administrator if you installed as non- root, or lo g in as root .
T imesT en Installation 71 Note: The Cach e Administrator will not wo rk if it is running on a W indows machine with the W in dows Firew all ON (this is the usual setting). In this case, the W indows Administrator must add an exception to allow the Cache Administrator to connect through t he W indows Firewall.
72 Oracle T imesT en In-Memory Da tabase Installation G uide 4. Click Next or Pr ev ious to view additional messages. Note: Y o u can also use the ttDaemonLog utilit y to view messages logged by the T imesT en Data Manager .
T imesT en Installation 73 *.debug /v ar/adm/sysl og/syslog. log user.err; use r.warn; user. info /var/adm/m essages T o make changes to /etc/syslo g.conf , you must have roo t privileges or be the TimesT en ins tance administrator .
74 Oracle T imesT en In-Memory Da tabase Installation G uide Environment modifications This section describes various env ironment variables that you may need to set, depending on the features o f T imesT en that your application uses .
T imesT en Installation 75 P A TH environment variable T imesT en provides uti lit ies for managing and debugging T ime sT en applications. T o make these utilit ies readily available, include the bin directory found in install_dir in the P A TH environment variable.
76 Oracle T imesT en In-Memory Da tabase Installation G uide application. If T imesT en cannot locate a u ser DSN file, the syst em DSN file located in /var/TimesTen/ sys.odbc.i ni will be used. Also, see “Defining data sources for th e dem o applications” on page 83 fo r more information on the .
T imesT en Installation 77 CLASSP A TH environment variable On W indows and UNIX platforms, add install_dir /demo and install_dir /lib/ttjdbc jdk_version .jar . to the CLASSP A TH environmen t variable. Fo r example, for JDK 5.0, set the CLASSP A TH enviro nm ent variable to: install_dir /lib/ ttjdbc5.
78 Oracle T imesT en In-Memory Da tabase Installation G uide On HP-UX 64-bit systems, add install_dir / lib to th e LD_LIBRARY _PATH environment variable. If you are using the Cache Connect to Oracle option, SHLIB_PATH must also contain $ORACLE_HO ME/lib and must not contain $ORAC LE_HOME/li b32 .
T imesT en Installation 79 W eb server co nfiguration The T imesT en 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 tim e, T imesT en enables it by setting the -webserver option in the ttendaemon.
80 Oracle T imesT en In-Memory Da tabase Installation G uide CGIROOT — A subdirect ory of WEBROOT where the CGI scripts are located. The path should begin and en d with a '/' on all platforms. The default is /cgi-bin/ . PERL — The path to the Perl interpreter .
T imesT en Installation 81 column and index definitions. When Ti mesT en restores a table in a new data store, it also restores the table’ s in dexes. Note: The ttM igrate utility cannot migrate data stores across dif ferent hardware platforms. For example, you cannot migrate a W indows data store to a Solaris data store.
82 Oracle T imesT en In-Memory Da tabase Installation G uide % /opt/TimesT en/tt70/ bin/ttMigr ate -rx DSN=Sale stt70 sales.dat Using the ttBulkCp utilit y The ttBulkCp utility copies table data between T imesT en data stores and ASCII files. The data files used by ttBulkCp can onl y contain rows from a single table.
T imesT en Installation 83 % /opt/tt60/3 2/bin/ttBu lkCp -o DSN=source6 00 able able. save % /opt/tt60/3 2/bin/ttBu lkCp -o DSN=source6 00 baker bake r.save Next create a new data source name, so urce_ tt70 for the T imesT en 7.0 data store, and execute the commands: % /opt/TimesT en/tt70/ bin/ttIsql -connStr DSN=source_ tt70 -f create.
84 Oracle T imesT en In-Memory Da tabase Installation G uide A sample file containing definitions for the DSN s req uired by the T imesT en demo applications is provided in /var/ TimesTen/ sys.odbc.i ni , if your product was installed as root. If installed by a non-root user the f ile is located in install_dir /info/sys.
T imesT en Installation 85 • Is the T imesT en service running? T o start the service, double-click Contr o l Panel > Administrative T ools > Services , choo se the Ti mesT en Data Manager service, and click S tart .
86 Oracle T imesT en In-Memory Da tabase Installation G uide Inst allation problems T o avoid problems during in stallation, make sure you have met all prerequisites. Using info rmation in the instal lation guide and the release notes, check that: • Y ou are running a supported version of the OS.
87 – 3 Data S tor e Upgrades Introduction When a T imesT en data store is loaded int o sh ared m emory , many of its attributes are fixed, including size, logging options, TimesT en software release number , and the location of its checkpo int and log files on disk.
88 Oracle T imesT en In-Memory Da tabase Installation G uide backward-compatible d ata types, see “Type specifications” on page 8 in the Oracle T imesT en In-Memory Database SQL Refer ence Guide .
Data S tor e Upgrad es 89 the same as the character set speci fied for the Oracle database that the T imesT en data store connects to. • Replication is not possible between data stores with different character sets. Because data s t ores created with versions of T imesT en prior to 7.
90 Oracle T imesT en In-Memory Da tabase Installation G uide Converting dat a types to Oracle dat a types Note: If you int end to use your data store with T imesT en Cache Connect to Oracle, you must convert your data typ es to Oracle data types. However , you will not be able to perform an on line upgrade using replication.
Data S tor e Upgrad es 91 Dat a store character set conversion Beginning with T imesT en 7.0, a char acter set must be specified for each T imesT en data st ore using the DSN attribute DatabaseCharacterSet . In some cases, you may need to change the configured data store character set as part of the upgrad e process.
92 Oracle T imesT en In-Memory Da tabase Installation G uide 4. Load the data store from the file using ttMigrate with the -noCharset Conversion command line option. This option ensures that no character values are changed when the data is loaded into the DSN using the new character set.
Data S tor e Upgrad es 93 Upgrade modes T imesT en allow s yo u to perform th ese kinds of upgrades: In-place upgrades In-place upgrades are av ailable for moving to a new patch release of T imesT en, such as moving from the first patch release of 7.0, version 7.
94 Oracle T imesT en In-Memory Da tabase Installation G uide Online upgrades with replication When upgrading to a new major rel ease of T imesT en, you may h ave a mission critical data store that needs to remain continu ously available to your applications.
Data S tor e Upgrad es 95 a Client/Server online upg rade from a TimesTen version p rior to 6.0” on page 113 . • If you are upgrading from a version of T imesT en that is 6.0 or above, the process is much easier . Starting with 7.0, T imesT en Server is able to talk directly to all versions of Ti mesT en Client from 6.
96 Oracle T imesT en In-Memory Da tabase Installation G uide utility . (See "ttAdmin" in Oracle T imesT en In-Me mory Database API Refer ence Guide .) In order to unload a data store: 1. Disconnect all applications from the data store. 2. In this example, the data store original is from the previous release.
Data S tor e Upgrad es 97 Performing an offline upgr ade Y ou can do an offline upgrade by exporting the data store into an external file using either the ttMigrate or ttBackup utility , then restoring the data store with the desired changes.
98 Oracle T imesT en In-Memory Da tabase Installation G uide Note: After ttMigrate has been used, all autorefresh cache groups in the destination data store have AUTOREFRESH ST A TE set to OFF , no matter how i t was set on the source data stor e. Reset AUT OREFRESH ST A TE to ON by using the ALTER CACHE GROUP statement.
Data S tor e Upgrad es 99 Note: Befo re mo ving a repli cated data store to another machine, you should be experienced with T im esT en replicatio n. W e hig hly advise calling T imesT en customer supp ort for help with this procedure. T o copy a data store from one system to another with the same CPU architecture and operating system: 1.
100 Oracle T imesT en In-Mem ory Database Insta llation Guid e Reducing dat a store size Once a data store has been define d with a particular size for the permanent partition (i ndicat ed by the PermSize DSN attribu te), it cannot be loaded at a smaller size, even if tables or rows are deleted.
Data S tor e Upgra des 101 Note: The temp orary part iti on size of a data store may be changed by simply modifyi ng the Te m p S i z e attribute of th e DSN, unloadin g the data store from memory , and then reconnecting to it. See “Unloading a data store” on page 95 for the steps to unload a data store from memory .
102 Oracle T imesT en In-Mem ory Database Insta llation Guid e the steps outlined in “Moving bet ween 32-bit and 64-bit data stores” on page 101 . If you need to upgrade two or more data stores th.
Data S tor e Upgra des 103 Now upgrade data store subscriber1 from release 5.1 to release 7.0. Perform th e followin g steps: 1. On the machine subscriberhost , use the 5.1 release’ s ttAdmi n utility to stop the replication daemon: ttAdmin -r epStop subs criber1 2.
104 Oracle T imesT en In-Mem ory Database Insta llation Guid e Performing an online upgrade with replication In “Performing an offlin e upgrade” o n page 97 we showed how to perform various maintenance operatio ns on T imesT en data stores that require that all applications be stopp ed.
Data S tor e Upgra des 105 release data store using ttMigrate from the newer release, and then reconnecting all applications to the upgraded data store. Note: The ttMigrate -r -rena me option, used t o rename the owner of data store tables, cannot be used with online upgrad es.
106 Oracle T imesT en In-Mem ory Database Insta llation Guid e 2. Connect all applications to the active data store, if they are not already connected. 3. Disconnect all appl ications from the upgrade data store. 4. Set replication to the upgrade system to the pause state.
Data S tor e Upgra des 107 After the above procedures have be en carried out on the upgrade system, the active system can be upgraded us ing the same steps. Limit ations Online upgrades can be performed only on data stores for which all the user tables meet the replication requi rements.
108 Oracle T imesT en In-Mem ory Database Insta llation Guid e Online upgrade example This section describes how to do an online upgrade of two bi- directionally replicated T imesT en data stores, using a concrete example.
Data S tor e Upgra des 109 Follow the steps listed here in the order they are presented. The onlin e upgrade procedures are: St ep Upgrade System Active System 1.
11 0 Ora cle T imesT en In-Memory Database Installation G uide 3. W ait for all replication updates to be sent to the data store active . Y ou can verify that all updates have been sent by apply ing a recognizable update to a table reserved for th at purpose on the data store upgrade .
Data S tor e Upgra des 111 6. Use ttMigrate to back up the data store upgrade . If the data store is very large, this step could take a significant amount of time. If sufficient disk space is free on the /backup file system , the following ttMigrate command can be used: ttMigrate -c DSN=up grade /backup/up grade.
11 2 Ora cle T imesT en In-Memory Database Installation G uide 9. Use ttMigrate to load the backup created in Step 6 into a new version of the data store upgrade : ttMigrate -r "DSN=upgr ade;AutoCr eate=0" /backup/u pgrade.
Data S tor e Upgra des 11 3 Performing a Client/Server onl ine upgrade from a T imesT en version prior to 6.0 Overview A user application linked wi th a 5.0 or later release of the T imesT en Client ODBC driver can connect to a Server DSN of a newer major 11 .
11 4 Ora cle T imesT en In-Memory Database Installation G uide release of T imesT en. For example, a 5.0 client can connect to a 7.0 Server DSN. Note: Applications linked to newer Ti mesT en clients cannot connect to a Server DSN of any older releases .
Data S tor e Upgra des 11 5 The TTCONNECTINI file at the T imesT en 5.1.x client machine contains: [my_server _51] Network_Ad dress=my_se rver TCP_PORT=1 5102 Because TCP_PORT is set to the T im e sT en 5.1 Server port nu mber , the 5.1 server dynamically loads the co rrect driver for the server DSN.
11 6 Ora cle T imesT en In-Memory Database Installation G uide Performing a Client/Server onl ine upgrade from T imesT en versio n 6.0 and above As of T imesT en 7.0, T imesT en Server is able to talk directly to all user applications linked wit h T i mesT en Cl ient OD BC driver version 6.
Data S tor e Upgra des 11 7 3. Use ttMigr ate to migrate t he data store from the old version to the new version. See “Moving between 32-bit and 64-b it data stores” on page 101 for an example of this procedure. 4. S tart the new version of TimesT en Server , if you have not alread y .
11 8 Ora cle T imesT en In-Memory Database Installation G uide These tables do not take up much space and are helpful when debugging upgrade problems. H owever , you can drop these tabl es if you do not experience problems with replication after running ttMigrate .
11 9 Index Index Numerics 64-bit platforms, supported 19 A Access Control authenticat ion 13 Cache Connect 8 Client/Server 8 daemon home directory 12 daemon port 13 directories and files 12 GroupRestr.
120 Oracle T imesT en In-Memory Database Installation Guide F files .odbc.ini 39 documentation 85 driver, verifying installation on Windows 42 enabling large files 27 header 73 makefiles 84 ODBCINI en.
Index 121 to a new patch release 96 N names instanc es 23 non-root installation limitations 7 prerequisites 37 O ODBC installation 73 ODBCINI file environment variable 75, 76 off-line upgrade 93, 97 o.
122 Oracle T imesT en In-Memory Database Installation Guide TimesTen daemon on AIX 61 TimesTen i nstance administra tor 9 TimesTen insta n ce user s external user 10 internal user 10 overview 10 TimesTen registry creatin g 38 TimesTen Ser ver on AIX 61 on HP-UX 53 on Solaris 48, 6 9 on Windows 43 timestend process 48, 65, 69 timestend.
Un punto importante, dopo l’acquisto del dispositivo (o anche prima di acquisto) è quello di leggere il manuale. Dobbiamo farlo per diversi motivi semplici:
Se non hai ancora comprato il Oracle B31679-01 è un buon momento per familiarizzare con i dati di base del prodotto. Prime consultare le pagine iniziali del manuale d’uso, che si trova al di sopra. Dovresti trovare lì i dati tecnici più importanti del Oracle B31679-01 - in questo modo è possibile verificare se l’apparecchio soddisfa le tue esigenze. Esplorando le pagine segenti del manuali d’uso Oracle B31679-01 imparerai tutte le caratteristiche del prodotto e le informazioni sul suo funzionamento. Le informazioni sul Oracle B31679-01 ti aiuteranno sicuramente a prendere una decisione relativa all’acquisto.
In una situazione in cui hai già il Oracle B31679-01, ma non hai ancora letto il manuale d’uso, dovresti farlo per le ragioni sopra descritte. Saprai quindi se hai correttamente usato le funzioni disponibili, e se hai commesso errori che possono ridurre la durata di vita del Oracle B31679-01.
Tuttavia, uno dei ruoli più importanti per l’utente svolti dal manuale d’uso è quello di aiutare a risolvere i problemi con il Oracle B31679-01. Quasi sempre, ci troverai Troubleshooting, cioè i guasti più frequenti e malfunzionamenti del dispositivo Oracle B31679-01 insieme con le istruzioni su come risolverli. Anche se non si riesci a risolvere il problema, il manuale d’uso ti mostrerà il percorso di ulteriori procedimenti – il contatto con il centro servizio clienti o il servizio più vicino.
