RTI Real-Time Connect Release Notes
Contents
1. Deliverables You will receive the following with your copy of RTI Real Time Connect 21 RTI Real Time Connect Getting Started Guide RTI RTC GettingStarted pdf This document guides you through the steps of installing RTI Real Time Connect and running a first application LJ RTI Real Time Connect installation file This file includes the RTI Real Time Connect executables library and documentation LJ Oracle TimesTen installation file This file includes the Oracle TimesTen libraries and executables demo programs utilities and documentation If any of these items are missing please contact RTI for support support rti com What s New in Release 4 5c Newer Database Versions RTI Real Time Connect 4 5c works with newer database versions J Oracle TimesTen 11 2 1 LI Oracle 11g Release 2 MySQL 5 1 The previous database versions are no longer supported Release Notes 4 2 4 3 5 1 5 2 5 3 Generation of TypeCodes from Table Schemas There is a new general option attribute called lt typecode_from_table_schema gt that can be used to enable typecode generation from table schemas When RTI Real Time Connect is used for table replication setting this tag to true default allows automatic table creation in the replicas Memory Usage Optimization in Table Replication Scenarios with Oracle TimesTen The amount of memory required for cache initialization when lt enable_table_replication gt is set t2. Assigns an application name to RTI Real Time Connect 1 version Prints the RTI Real Time Connect version For additional information about the new command line options see the RTI Real Time Connect User s Manual The deprecated options are still functional to preserve backwards compatibility How ever they should not be used as they may be removed in future releases 7 Known Issues 6 2 6 2 1 7 1 What s Fixed in Release 4 56 Segmentation Fault in MySQL when Publishing Updates on a Table Where the First Field is Set to NULL In previous releases the publication of a table update in MySOL where the first field was set to NULL caused a segmentation fault For example CREATE TABLE MyTbl field1 VARCHAR 10 field2 VARCHAR 10 fieldKey INTEGER PRIMARY KEY fieldKey If the table MyTbl was published with RTI Real Time Connect by inserting an entry into the RTIDDS PUBLICATIONS meta table the following SOL statement caused a seg mentation fault UPDATE MyTbl set field1 NULL The following SOL statement was executed correctly because the field set to NULL was not the first one UPDATE MyTbl set field2 NULL This problem has been resolved RTI Bug 13143 Known Issues Manual Table Creation in Oracle and MySQL Does Not Trigger Daemon to Create Publication Subscription when Typecode is Unknown If entry is inserted into the RTIDDS PUBLICATIONS RTIDDS SUBSCRIPTIONS t
3. Ves No TimesTen 11 2 1 Yes Yes Windows Windows 7 s pt Oracle 11g Yes Yes MySQL 5 1 Yes Yes TimesTen 11 2 1 No Yes Windows Server 2008 R2 x86 64 Oracle 11g No Yes MySQL 5 1 No Yes 1 Additional platforms not listed in this document may be supported through special development and maintenance agreements Contact your RTI sales representative for details 2 Requires Microsoft Visual Redistributable Package on computers that do not have Visual 2010 installed 2 Compatibility 1 1 2 1 ODBC Driver Requirements The RTI Real Time Connect to MySQL daemon requires the separate installation of the MySQL ODBC 5 1 6 or higher driver For non Windows platforms the installation of UnixODBC 2 2 12 or higher is also required Compatibility Compatibility with RTI Data Distribution Service RTI Real Time Connect 4 5c is not compatible with RTI Data Distribution Service 4 2c and lower RTI Real Time Connect 4 5c is compatible with RTI Data Distribution Service 4 5b 4 4 4 3 and 4 2e except as noted below Compatibility with Older Versions When Sending Large Data The large data format in RTI Data Distribution Service 4 2e 4 3 4 4b and 4 4c is not com pliant with RTPS 2 1 Large data refers to data that cannot be sent as a single packet by the transport This issue has been resolved starting with RTI Data Distribution Service 4 4d As a result by default large data in RTI Real Time
4. is IdentifierseparatorChar Cannot Be for TimesTen Cache Connect to Oracle If your application uses IDL types that contain strings long doubles or hierarchical IDL types the IdentiferSeparatorChar cannot be when using TimesTen Cache Connect to Oracle This is due to a bug in Cache Connect to Oracle that causes quoted column names containing the character such as A B to be handled incorrectly Applications with Disabled Inline Keyhash If the RTI Data Distribution Service application has a keyed data type and has DataWrit erProtocolOosPolicy disable inline keyhash set to TRUE not the default setting RTI Real Time Connect may misinterpret samples as being from the wrong instance or report deserialization errors 8 Contacting RTI for Support 7 7 7 8 7 9 RTI Real Time Connect Daemon with nodaemon Option does not Communicate over Shared Memory with MySQL 5 0 Server or Oracle 10g Server when Running as Windows 2003 or Windows Vista Service On Windows 2003 and Windows Vista systems if the RTI Real Time Connect daemon for MySQL 5 0 and Oracle 10g is run with the nodaemon option it will not communicate with the MySQL and Oracle database servers There are three ways to enable communication 1 Run both the RTI Real Time Connect daemon and the database server as services 2 Run both the RTI Real Time Connect daemon and the database server from the command line 3 Use the RTI Real Time
5. 8 Contacting RTI for Support Manual Table Creation in Oracle and MySQL Does Not Trigger Daemon to Create Publication Subscription when Typecode is Unknown WCHAR and WVARCHAR Not Supported as Primary Keys for MySQL WCHAR and WVARCHAR Not Published Correctly for MySQL IdentifierSeparatorChar Cannot Be for MySQL sss IdentifierSeparatorChar Cannot Be for TimesTen Cache Connect to Oracle Applications with Disabled Inline Keyhash sss RII Real Time Connect Daemon with nodaemon Option does not Communicate over Shared Memory with MySQL 5 0 Server or Oracle 10g Server when Running as Windows 2003 or Windows Vista Service Table Initialization in Database Replication Scenarios May Require Keeping a Copy of the Table In Memory for Oracle and MySQL11 RTI Real Time Connect for Oracle Cannot Be Run as a Windows Service Release Notes This document provides release specific information about RTI Real Time Connect 4 5c I Supported Platforms and System Requirements Section 1 LJ Deliverables Section 3 What s New in Release 4 5c Section 4 LJ Previous Releases Section 6 Known Issues Section 7 I Contacting RTI for Support Section 8 1 Supported Platforms and System Requirements RTI Real Time Connect 4 5c requires RTI Data Distribution Service 4 5c RTI Real Time Connect suppo
6. Connect 4 5b is not compatible with RTI Data Distribution Service 4 4c and earlier You can achieve backward compatibility by setting the following properties to 1 in the XML QoS profiles used to configure the RTI Real Time Connect publications and subscriptions 1 dds data writer protocol use 43 large data format 2 dds data reader protocol use 43 large data format Compatibility with RTI Data Distribution Service 4 2e Out of the box RTI Real Time Connect 4 5c is not compatible with RTI Data Distribution Service 4 2e when the data types contain 8 byte or larger primitive types double long long unsigned long long or long double To enable compatibility RTI Real Time Connect will have to be run with the command line option use42eAlignment Release Notes 2 2 2 3 2 3 1 2 3 2 Compatibility with Other Versions of RTI Real Time Connect RTI Real Time Connect 4 5b is compatible with RTI Real Time Connect 4 4 4 3 and 4 2 with the same exceptions that apply to RTI Data Distribution Service Therefore RTI Real Time Connect 4 5c will not be compatible with an older RTI Real Time Connect version if it is not compatible with the associated RTI Data Distribution Service version Configuration Compatibility Configuration File Format Starting with RTI Real Time Connect 4 5b the format of the configuration file has changed from INI to XML The deprecated format is still functional to preserve backwards compatibility Howe
7. Connect command line option dbtransport 1 to commu nicate using UDPv4 Table Initialization in Database Replication Scenarios May Require Keeping a Copy of the Table In Memory for Oracle and MySQL If RTI Real Time Connect is configured in table replication mode using the INI attribute TableReplicationMode the daemon may end up keeping a copy of the whole table in memory This may be a problem for databases such as Oracle and MySQL where tables may become quite large To avoid the problem disable table initialization by setting dw durability kind in RTIDDS_PUBLICATIONS and dw durability kind in RTIDDS_SUBSCRIPTIONS to VOLATILE_DURABILITY_QOS RTI Real Time Connect for Oracle Cannot Be Run as a Windows Service If RTI Real Time Connect for Oracle is run as a Windows service the following error is reported Error 1053 The service did not respond to the start or control request in a timely fashion Contacting RTI for Support For technical support regarding RTI Real Time Connect please visit http www rti com support html or contact support rti com Release Notes
8. RTI Real Time Connect Release Notes Version 4 5c 2010 Real Time Innovations Inc All rights reserved 277 Printed in U S A First printing 747 June 2010 Trademarks Real Time Innovations and RTI are registered trademarks of Real Time Innovations Inc All other trademarks used in this document are the property of their respective owners Third Party Copyright Notices The Oracle TimeTen In Memory Database and the Oracle Database are products of Oracle Copy and Use Restrictions No part of this publication may be reproduced stored in a retrieval system or transmitted in any form including electronic mechanical photocopy and facsimile without the prior written permission of Real Time Innovations Inc All software and documentation whether in hard copy or electronic form enclosed are subject to the license agreement The software and documentation may be used or copied only under the terms of the license agreement Technical Support Real Time Innovations Inc 385 Moffett Park Drive Sunnyvale CA 94089 Phone 408 990 7444 Email support rti com Website http www rti com support Contents 1 Supported Platforms and System Requirements esent ntn tn tntnn 11 ODBC Driver Requirements nemen rennen terrre er teeth nido aeonrilgtl M 21 Compatibility with RTI Data Distribution Se
9. able arid the typecode for the data type specified in the entry has not yet been discovered by the daemon the daemon will delay the creation of the DDS publication subscription if the table does not already exist in the database When either the daemon discovers the typecode or the user manually creates the table the daemon should create the corresponding DDS publication subscription However for the Oracle 10g and MySQL databases only in the situation described above if you create a table manually for a pending entry the daemon is not triggered to Release Notes 7 2 7 3 7 4 7 5 7 6 create the corresponding publication subscription The workaround is to update the entry by modifying the entry in the corresponding meta table This will trigger the dae mon to create the publication subscription WCHAR and WVARCHAR Not Supported as Primary Keys for MySQL Due to a bug in MyODBC MySQL bug 17983 tables with a WCHAR or WVARCHAR column in the primary key are not supported in conjunction with MySQL WCHAR and WVARCHAR Not Published Correctly for MySQL The contents of WCHAR and WVARCHAR fields are not published correctly by RTI Real Time Connect Publications in MySQL Zero 0 is published instead of the correct value IdentifierSeparatorChar Cannot Be for MySQL When using MySQL the IdentifierSeparatorChar cannot be due to a bug in MyODBC MySQL bug 15547 The default IdentifierSeparatorChar for MySQL
10. etion of the subscription entry interrupted the reception of database changes for even though the publication entry was still present This problem has been resolved RTI Bug 13433 Parser Error when Using false for typedef Boolean_T boolean With a typedef name Boolean_T type boolean gt setting the value of a const can not be false or presumably true For example the following would cause a parser error on false const name IS SWITCH IMMEDIATE type nonBasic nonBasicTypeName DDS primitive Boolean T value false gt This problem has been resolved RTI Bug 13312 Previous Releases What s New in Release 4 5b Table Index Name Change The names of the table indexes created by RTI Real Time Connect no longer need to be enclosed in double quotes they are not quoted identifiers This change facilitates the integration with ODBC tools that do not support quoted identification New Configuration File Format Starting with RTI Real Time Connect 4b the format of the configuration file has changed from INI to XML The deprecated format is still functional to preserve back wards compatibility However it should not be used as it may be removed in future releases For additional information about the new configuration format see the RTI Real Time Connect User s Manual Release Notes Initialization of Meta tables RTIDDS_PUBLICATIONS and RTIDDS_SUBSCRIPTIONS from the Configuration File Startin
11. g with Real Time Connect 4 5b the content of the meta tables RTIDDS_PUBLICATIONS and RTIDDS_SUBSCRIPTIONS can be updated using the tags lt publications gt and lt subscriptions gt in the configuration files For additional information about these new tags see the RTI Real Time Connect User s Manual Type Definition Support in the Configuration File In previous releases the only way to create a database table automatically was by dis covering its associated typecode Starting with this release automatic table creation is also supported by defining the type associated with the table in the XML configuration files The type definition is made within the XML tag lt types gt For additional informa tion about type definition see the RTI Real Time Connect User s Manual Configuration File Loading The way in which configuration files are loaded changed in release 4 5b See Configura tion File Loading Section 2 3 2 New Command Line Options RTI Real Time Connect 4 5b introduced the following command line options LL cfgFile Specifies an XML configuration file for RTI Real Time Connect This option replaces the deprecated inifile option of previous releases l cfgName Selects a RTI Real Time Connect configuration in the XML files This command line option is required 1 verbosity Sets the RTI Real Time Connect verbosity This option replaces the now deprecated loglevel option of previous releases appName
12. o true has been reduced In previous RTI Real Time Connect versions the publications always kept one copy of the table records in memory in addition to the copy maintained by Oracle TimesTen Start ing with RTI Real Time Connect 4 5c the publications store references to the records and not the actual data What s Fixed in Release 4 5c Possible Segmentation Fault When the Cache for Keys Is Enabled In previous releases RTI Real Time Connect may have crashed if the cache for keys was enabled using the fields cache_maximum_size and cache_initial_size in the subscrip tions table This problem has been resolved RTI Bug 13287 Possible Segmentation with Destination Order By Source Timestamp In previous releases RTI Real Time Connect may have crashed when subscriptions were created with the DestinationOrder QoS policy set to by source timestamp This prob lem has been resolved RTI Bug 13240 and 13288 Propagation of Delete Operations May Have Generated Unnecessary Network Traffic The propagation of delete operations may have generated unnecessary network traffic which in turn affected scalability and performance This problem has been resolved RTI Bug 13289 6 Previous Releases 5 4 5 5 Reception of Database Changes Stopped when Entries Deleted from Subscriptions Table Let s assume a table A with associated entries in the subscriptions and publications tables In this scenario the del
13. rts Oracle TimesTen In Memory Database 11 2 1 MySQL 5 1 and Oracle Database 11g Release 2 you must have at least one of these installed Details of the supported platform configurations are specified in Table 1 1 d The RTI Real Time Connect to Oracle TimesTen daemon rtirtc_timesten exe has been built and tested on all supported platform configurations with TimesTen 112 1 The RTI Real Time Connect to Oracle 11g daemon rtirtc oracle exe has been built and tested on all supported platform configurations with Oracle 11 2 0 The RTI Real Time Connect to MySQL daemon rtirtc_mysql exe has been built and tested on all supported platform configurations with MySQL 5 1 44 Release Notes Table 1 1 Supported Platforms Operating System CPU Database 32 bit 64 bit TimesTen 11 2 1 No Yes AIX AIX 5 3 Power class Oracle 11g No Yes MySQL 5 1 No No TimesTen 11 2 1 Yes Yes TimesTen 11 2 1 Yes Yes Red Hat Enterprise Linux 4 0 x86 Oracle 11 Yes Yes 2 6 kernel Linux MySQL 5 1 Yes No TimesTen 11 2 1 Yes Yes 86 Oracle 11g Yes Yes MySQL 5 1 Yes Yes Solaris 2 9 Ultra SPARC TimesTen 11 2 1 Yes No TimesTen 11 2 1 Yes Yes Solaris solaris 2 10 UltraSPARC Oracle 11g No Yes MySQL 5 1 Yes No Windows 2000 Windows 2003 Windows XP Professional x86 Oracle 11g Yes No Windows Vista MySQL 5 1
14. rvice 2 2 Compatibility with Other Versions of RTI Real Time Connect 2 3 Configuration Compatibility eer ugscitoc c What s New in Release 4 5 totos ense setenta inen 4l Newer Database VersiOtis n titii eee eire tarte atteinte 4 2 Generation of TypeCodes from Table Schemas sss 43 Memory Usage Optimization in Table Replication Scenarios with Oracle git 5 Whats Fixed in Release 4 5c eese 51 Possible Segmentation Fault When the Cache for Keys Is Enabled 5 2 Possible Segmentation with Destination Order Source Timestamp 5 3 Propagation of Delete Operations May Have Generated Unnecessary Maso RR RT 5 4 Reception of Database Changes Stopped when Entries Deleted from Subscriptions Table aee tiet here erp t ter ltr EE 5 5 Parser Error when Using false for typedef Boolean T 6 Previous UC EFE isisa 61 What s New in Release 4 5b eee en tt iter iter rete etre 6 2 What s Fixed in Release 4 5b seiner 7 Known Issues 7 1 7 2 7 3 74 7 5 7 6 7 7 7 8 7 9
15. ver it should not be used as it may be removed in future releases Configuration File Loading Starting with RTI Real Time Connect 4 5b the way configuration files are loaded has changed These are the new approaches listed in load order 1 NDDSHOME resource qos profiles 4 5x xml NDDS QOS PROFILES xml J Files in the environment variable NDDS QOS PROFILES 1 working directory gt USER_QOS_PROFILES xml RTI Real Time Connect executable location l resource xml REAL TIME CONNECT xml 1 working directory s USER REAL TIME CONNECT xml 21 File specified using the command line parameter cfgFile The following configuration loading options have been deprecated SRTIRTCHOME resource xml RTI RTC QOS PROFILES xml SRTIRTCHOME resource ini RTI RTC ini I File in the RTIRTC INI environment variable deprecated in 4 44 File specified using the command line parameter inifile Although the old options are still functional to preserve backwards compatibility its usage should be avoided as they may be removed in future releases 3 Deliverables 2 3 3 4 1 Command Line Options Starting with RTI Real Time Connect 4 5b the following command line options have been deprecated l inifile Replaced with cfgFile LI loglevel Replaced with verbosity The deprecated options are still functional to preserve backwards compatibility How ever they should not be used as they may be removed in future releases
Download Pdf Manuals
Related Search