TIBCO Kabira® Adapter Factory for Persistence Release Notes

TIBCO Kabira® Adapter Factory for Persistence

Release NotesSoftware Release 5.8.3December 2017

Important Information

SOME TIBCO SOFTWARE EMBEDS OR BUNDLES OTHER TIBCO SOFTWARE. USE OF SUCH EMBEDDED OR BUNDLED TIBCO SOFTWARE IS SOLELY TO ENABLE THE FUNCTIONALITY (OR PROVIDE LIMITED ADD ON FUNCTIONALITY) OF THE LICENSED TIBCO SOFTWARE. THE EMBEDDED OR BUNDLED SOFTWARE IS NOT LICENSED TO BE USED OR ACCESSED BY ANY OTHER TIBCO SOFTWARE OR FOR ANY OTHER PURPOSE.

USE OF TIBCO SOFTWARE AND THIS DOCUMENT IS SUBJECT TO THE TERMS AND CONDITIONS OF A LICENSE AGREEMENT FOUND IN EITHER A SEPARATELY EXECUTED SOFTWARE LICENSE AGREEMENT, OR, IF THERE IS NO SUCH SEPARATE AGREEMENT, THE CLICKWRAP END USER LICENSE AGREEMENT WHICH IS DISPLAYED DURING DOWNLOAD OR INSTALLATION OF THE SOFTWARE (AND WHICH IS DUPLICATED IN THE LICENSE FILE) OR IF THERE IS NO SUCH SOFTWARE LICENSE AGREEMENT OR CLICKWRAP END USER LICENSE AGREEMENT, THE LICENSE(S) LOCATED IN THE “LICENSE” FILE(S) OF THE SOFTWARE. USE OF THIS DOCUMENT IS SUBJECT TO THOSE TERMS AND CONDITIONS, AND YOUR USE HEREOF SHALL CONSTITUTE ACCEPTANCE OF AND AN AGREEMENT TO BE BOUND BY THE SAME.

ANY SOFTWARE ITEM IDENTIFIED AS THIRD PARTY LIBRARY IS AVAILABLE UNDER SEPARATE SOFTWARE LICENSE TERMS AND IS NOT PART OF A TIBCO PRODUCT. AS SUCH, THESE SOFTWARE ITEMS ARE NOT COVERED BY THE TERMS OF YOUR AGREEMENT WITH TIBCO, INCLUDING ANY TERMS CONCERNING SUPPORT, MAINTENANCE, WARRANTIES, AND INDEMNITIES. DOWNLOAD AND USE THESE ITEMS IS SOLELY AT YOUR OWN DISCRETION AND SUBJECT TO THE LICENSE TERMS APPLICABLE TO THEM. BY PROCEEDING TO DOWNLOAD, INSTALL OR USE ANY OF THESE ITEMS, YOU ACKNOWLEDGE THE FOREGOING DISTINCTIONS BETWEEN THESE ITEMS AND TIBCO PRODUCTS.

This document contains confidential information that is subject to U.S. and international copyright laws and treaties. No part of this document may be reproduced in any form without the written authorization of TIBCO Software Inc.

TIBCO, Two-Second Advantage, TIBCO ActiveMatrix BusinessWorks, TIBCO Runtime Agent, TIBCO Administrator, and TIBCO Enterprise Message Service are either registered trademarks or trademarks of TIBCO Software Inc. in the United States and/or other countries.

Enterprise Java Beans (EJB), Java Platform Enterprise Edition (Java EE), Java 2 Platform Enterprise Edition (J2EE), and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle Corporation in the U.S. and other countries.

All other product and company names and marks mentioned in this document are the property of their respective owners and are mentioned for identification purposes only.

THIS SOFTWARE MAY BE AVAILABLE ON MULTIPLE OPERATING SYSTEMS. HOWEVER, NOT ALL OPERATING SYSTEM PLATFORMS FOR A SPECIFIC SOFTWARE VERSION ARE RELEASED AT THE SAME TIME. SEE THE README FILE FOR THE AVAILABILITY OF THIS SOFTWARE VERSION ON A SPECIFIC OPERATING SYSTEM PLATFORM.

THIS DOCUMENT IS PROVIDED “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT.

THIS DOCUMENT COULD INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS. CHANGES ARE PERIODICALLY ADDED TO THE INFORMATION HEREIN; THESE CHANGES WILL BE INCORPORATED IN NEW EDITIONS OF THIS DOCUMENT. TIBCO SOFTWARE INC. MAY MAKE IMPROVEMENTS AND/OR CHANGES IN THE PRODUCT(S) AND/OR THE PROGRAM(S) DESCRIBED IN THIS DOCUMENT AT ANY TIME.

THE CONTENTS OF THIS DOCUMENT MAY BE MODIFIED AND/OR QUALIFIED, DIRECTLY ORINDIRECTLY, BY OTHER DOCUMENTATION WHICH ACCOMPANIES THIS SOFTWARE, INCLUDING BUT NOT LIMITED TO ANY RELEASE NOTES AND "READ ME" FILES.

Copyright © 2010-2017 TIBCO Software Inc. All rights reserved.

| iii

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . v

TIBCO Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Typographical Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Connecting with TIBCO Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Join TIBCOmmunity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Access All TIBCO Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ixHow to Contact TIBCO Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix

Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

New Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.7.9 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.6.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.6.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.6 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Release 5.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Release 5.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Changes in Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 5.8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Release 5.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Deprecated and Removed Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 5.8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Release 5.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Migration and Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 5.8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Release 5.8 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Closed Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Known Issues. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

TIBCO Kabira Adapter Factory for Persistence Release Notes

iv | Contents


| v

Preface

TIBCO Kabira(R) Adapter Factory for Persistence lets you designate objects as implemented in a database management system, causing them automatically to be stored in, and accessed from, a database.

Topics

• TIBCO Product Documentation, page vi

• Connecting with TIBCO Resources, page ix


vi | TIBCO Product Documentation

TIBCO Product Documentation

This section lists the documentation resources you may find useful.

The following documents form the TIBCO Kabira documentation set:

• TTIBCO Kabira® Adapter Factory for Persistence Installation Read this manual for instructions on site preparation and installation.

• TIBCO Kabira® Adapter Factory for Persistence Release Notes Read this manual for a list of new and changed features, steps for migrating from a previous release, and lists of known issues and closed issues for the release.


Preface | vii

Typographical Conventions

The following typographical conventions are used in this manual.

Table 1 General Typographical Conventions

Convention Use

TIBCO_HOME Many TIBCO products must be installed within the same home directory. Thisdirectory is referenced in documentation as TIBCO_HOME. The default value ofTIBCO_HOME depends on the operating system. For example, on Unix systems,

the default value is /tibco.

code font Code font identifies commands, code examples, filenames, pathnames, and output displayed in a command window. For example:

Use MyCommand to start the foo process.

bold code font Bold code font is used in the following ways:

• In procedures, to indicate what a user types. For example: Type admin.

• In large code samples, to indicate the parts of the sample that are of particular interest.

• In command syntax, to indicate the default parameter for a command. For example, if no parameter is specified, MyCommand is enabled: MyCommand [enable | disable]

italic font Italic font is used in the following ways:

• To indicate a document title. For example: See TIBCO Fulfillment Catalog Installation and Configuration.

• To introduce new terms For example: A portal page may contain several portlets. Portlets are mini-applications that run in a portal.

• To indicate a variable in a command or code syntax that you must replace. For example: MyCommand PathName

Key combinations Key name separated by a plus sign indicate keys pressed simultaneously. For example: Ctrl+C.

Key names separated by a comma and space indicate keys pressed one after the other. For example: Esc, Ctrl+Q.

The note icon indicates information that is of special interest or importance, for example, an additional action required only in certain circumstances.


viii | Typographical Conventions

The tip icon indicates an idea that could be useful, for example, a way to apply the information provided in the current section to achieve a specific result.

The warning icon indicates the potential for a damaging situation, for example, data loss or corruption if certain steps are taken or not taken.

Table 1 General Typographical Conventions (Cont’d)

Convention Use


Preface | ix

Connecting with TIBCO Resources

How to Access All TIBCO DocumentationAfter you join TIBCOmmunity, you can access the documentation for all supported product versions here:

http://docs.tibco.com

How to Contact TIBCO SupportFor comments or problems with this manual or the software it addresses, contact TIBCO Support as follows.

• For an overview of TIBCO Support, and information about getting started with TIBCO Support, visit this site:

http://www.tibco.com/services/support

• If you already have a valid maintenance or support contract, visit this site:

https://support.tibco.com

Entry to this site requires a user name and password. If you do not have a user name, you can request one.


http://www.tibco.com/services/support


http://docs.tibco.com/TibcoDoc

x | Connecting with TIBCO Resources


| 1

Release Notes

Check the TIBCO Product Support web site at https://support.tibco.com for product information that was not available at release time. Entry to this site requires a username and password. If you do not have a username, you can request for one. You must have a valid maintenance or support contract to use this site.

Topics

• New Features, page 2

• Changes in Functionality, page 5



2 | Release Notes

New Features

This section lists the features of this product.

Release 5.8.3There are no new features in this release.



Release 5.7.9The following are the new features in this release:

• Add mySQL support

• Upgrade to ODBC 6.0 service pack 1

Release 5.6.6The following are the new features in this release:

• Upgrade to data direct 5.3 service pack 2

• Upgrade to Oracle v11g

Release 5.6.3The following is the new feature in this release:

• Support configurable transaction isolation for OCI.

OCI now supports the "ReadCommitted" transaction isolation level.


New Features | 3

Release 5.6The following are the new features in this release:

• Support Bind Variable in ODBC.

Bind variable support has been added to PAF. This improves database server performance.

• Remove describe to improve result processing performance.

The describe call has been removed from results processing to improve performance.

• 3RDPARTY: Upgrade to ODBC 5.3 . PAF has been upgraded to use ODBC 5.3.

• Doc Impact of 060509-000011: PAF: Map ORA-00604 to deadlock.

• PAF: document transaction isolation configuration.

• PAFDOC: about exceptionResourceUnavailable.

• DOC: PAF: Oracle native error 8177 can't serialize is mapped to deadlock.

• PAFDOCS transaction management details enhancement.

• Doc Impact of 010720-000000: PAF: Support persistent singletons.

• Doc Impact of 001030-000002: RT: Only execute cache never once / transaction.

• Doc Impact of 030102-000000: PAF: Audit against use of key: in createString.

• Doc Impact of 991011-000005: RT: auto flush object cached as NEVER.


• PAF: Support dynamic components.

The code generator was updated to generate dynamic singleton components for persistent objects. This allows generated persistent object components to be in the same engine as application components - eliminating event bus communication. This significantly improves the performance of applications accessing persistent objects.

Previous releases generated static singleton components which required the component to be in a separate engine.

• PAF: Remove describe to improve result processing perf.

The PAF runtime for ODBC has been updated to remove the describe operation that was previously called for all result set processing. The


4 | Release Notes

generated type system is used for binding result sets now eliminating the need for this call.

This improves performance for ODBC result set processing.


• PAF: Upgrade to ODBC 5.1.

PAF was upgraded to use ODBC 5.1.

• PAF: Certify against Oracle 10g.

PAF was certified against Oracle 10g.

• PAF: Map ORA-00604 to deadlock.

The following Oracle error:[ODBC Oracle Wire Protocol driver]

[Oracle]ORA-00604: error occurred at recursive SQL level 1

(ORA-08177: can't serialize access for this transaction)

is now mapped to a KIS deadlock.


Changes in Functionality | 5

Changes in Functionality

This section lists changes in functionality since the last release of this product.

Release 5.8.3There are no changes in functionality in this release.

Release 5.8.2There are no changes in functionality in this release.

Release 5.8.1Sybase ASE 12.0 is not certified anymore.

Release 5.8There are no changes in functionality in this release.


6 | Release Notes

Deprecated and Removed Features

This section describes deprecated features (if any), and lists features, if relevant, that may be useful alternatives to the deprecated features. Any use of a deprecated feature should be discontinued as it may be removed in a future release. You should avoid becoming dependent on deprecated features and become familiar with the suggested alternative features.

This section also lists features that are removed (if any).

Release 5.8.3No features are deprecated in this release.



Release 5.8No features are deprecated in this release.


Migration and Compatibility | 7

Migration and Compatibility

This section explains the impact of migration from a previous release to this release to various parts of the application.

Release 5.8.3There are no migration procedures or compatibility issues in this release.



Release 5.8There are no migration procedures or compatibility issues in this release.


8 | Release Notes

Closed Issues

The table in this section lists issues that were closed in the named releases.

Closed in Release Key Summary

5.7.7 FLUENCY-1955 OracleOCI strips { and } from string.

5.6.5 080320-000000 OCI txn isolation level stay serializable in DEVELOPMENT mode.

5.6.3 080111-000005 Signal 10 when doing a SELECT on a 2 attributes key.

5.6 030211-000005 PAF: Forward-engineered database tables don't support 64 bit OIDs.

5.6 051002-000000 PAFDOCS: Remove informix.

5.6 030128-000002 Persistence: doc that ""InstallDir"" required in ODBC.INI.

5.6 030107-000032 Doc Impact of 021119-000007: PAF: Undetected deadlock with extended persistent.

5.6 030107-000031 Doc Impact of 021113-000000: PAF: Generate static components only.

5.6 020814-000001 DOC: PAF: Default ODBC error mappings can be changed.

5.4 060524-000021 PAF: odbc.ini in PAF.README.

5.4 060814-000008 PAF: DataBasePackage(31982): unaligned access to 0x2000000023afe353, ip=0.

5.3 050313-000003 PAF: Set LD_LIBRARY_PATH to build Oracle OCI.

5.3 050826-000007 PAF: Incorrect Driver info in odbc.ini.

5.3 060330-000027 PAF: Missing part number.

5.3 060118-000008 PAF: Remove informix.

5.3 051213-000004 PAF: Incorrect file names in PAF.3RDPARTY.5.2.2.

5.3 031030-000007 PAF: ODBC 4.2 Oracle Wire Driver not working.

5.3 041222-000004 PAF: README should be more specific on OCI/ODBC support.

5.3 051020-000009 PAF: Database server deadlocks don't dump callstack.


Closed Issues | 9

5.3 050825-000009 PAF: Promotion deadlock traversing relationship.

5.0 030124-000007 PAF: Timer event entities cannot be persistent.

5.0 031128-000018 PAF: Message file is sparsed. Should be generic.

5.0 030903-000010 PAF: Migrate to data direct 4.2 ODBC drivers.

5.0 040429-000004 PAF: Missing dependencies.

5.0 030731-000002 PAF: OCI leaks memory.

5.0 030513-000002 PAF: Add support for Oracle 9i.

4.2 030506-000014 PAF - 3rdparty notes do not list databases tested.

4.2 030306-000006 PAF: Sample ODBC config odbc.ini missing installDir.

4.1 030103-000007 PAF: Trailing [k]|[ke]|[key] in query strings truncated.

4.1 021119-000007 PAF: Undetected deadlock extented persistent entities.

4.1 030107-000004 PAF: Informix wire drivers mangle DECIMAL colums.

4.1 011009-000005 PAF: Crash if database restarted.

4.0.2 020514-000000 PAF: Typo in file $SW_HOME/distrib/sol/cfg/odbc.ini.

4.0.2 020606-000004 PAF: Invalid adapter property causes psplugin crash.

4.0.1 020301-000006 PAF: Cacheing type "never" does not work properly.

4.0.1 011201-000001 PAF: Runtime assertion if [ extentless ] entity.

4.0.1 020123-000010 PAF: FlushRate has no effect.

4.0 000911-000011 PAF: Connection retry causes engine hang.

4.0 010918-000007 PAF: Map [Informix]Unique constraint violated to PSDataError.

4.0 011018-000001 PAF: ostenv.cpp:1850: failed C++ assertion numTriggers >= 1.

4.0 010925-000003 PAF: The structure of DSERegistry.sm changes when use Persistent adapter.



10 | Release Notes

4.0 010304-000005 ODBC driver for sybase not thread safe.



Known Issues | 11

Known Issues

The table in this section lists known issues in this release.

Change Request ID Summary/Workaround

050303-000010 Summary PAF: OCI flushAll with cache once policy does not refresh extent.

Extent reads on extents with a cache policy of "once", will not refresh objects in shared memory if the object was explicitly flushed from memory and the flush type is "flushAll".

Objects configured with a flush type of "flushData" work correctly. Also, accessing objects by key always works.

Workaround None.

030625-000001 Summary PAF: Service descriptions cannot be updated.

Changing the database queries or schema without changing the persistent entity will case an assertion failure in the PAF adapter.

Workaround Build and deploy the component twice. The first time, make an incompatible change to the entity (i.e. add a new attribute). The second time, remove the previous change. This forces the runtime to delete the type each time it is loaded.

020723-000008 Summary PAF: Cannot use cross package inheritance.

The Persistence Adapter Factory incorrectly handles cross-package inheritance. No error is reported at build time, but all attributes inherited from a cross-package parent are ignored.

Workaround There is no work-around to this problem. Do not use cross-package inheritance with persistent entities.

011120-000003 Summary PAF: Auditor does not detect excess bounded string lengths.

The Persistence Adapter Factory auditor does not detect excess bounded string sizes. A bounded string greater than the size of a variable character column in the database will cause incorrect SQL to be generated for table creation when using forward engineering, or a runtime error if using legacy databases.

Workaround Ensure that bounded string sizes do not exceed the maximum variable character column size for the target database.


12 | Release Notes

000822-000000 Summary PAF: Persistence can hang if it runs out of connections.

If the persistence runtime adapter runs out of connections an undetected resource deadlock can occur.

Workaround The only work-around is to increase the number of configured connections and restart the persistence engine.

Contact Support for more details on the generated code modifications.

011102-000003 Summary PAF: OCI Oracle Lib search path invalid.

When building an OCI persistence engine, ensure the environment of the shell used to run swdc -c start for that Design Center is set as follows:

The ORACLE_HOME environment variable must point to the root directory of the Oracle installation.

For Solaris, the LD_LIBRARY_PATH environment variable must include the path to the lib subdirectory within the Oracle installation directory tree.

When deploying an OCI persistence engine to a node, ensure the environment of the shell used to run swstart for that node is set as follows:

The ORACLE_HOME environment variable must point to the root directory of the Oracle installation.

For Solaris, the LD_LIBRARY_PATH environment variable must include the path to the lib subdirectory within the Oracle installation directory tree.

020217-000006 Summary PAF: Assertion shutting down distributed persistent objects.

Shutting down an engine using swbuiltin::EngineServices::stop with active distributed transactions to persistent objects can cause the following assertion in debug builds:

psconmgr.cpp:273: failed assertion 'm_hashList.getNumItems()

For production builds, the following warning may be traced:

conodbc.cpp (2109)|4|P |WARN |ODBC: State(S1010) Code(0)

Msg([MERANT][ODBC lib] Function sequence error)

This assertion prevents the engine from shutting down clean in debug builds.

Workaround None.



Known Issues | 13

990530-000001 Summary PAF: Cannot access all roles in assoc rel in deploy specification.

It is not possible to manage all role of an associate relationship in a component specification for persistence.

Workaround Model associative objects as a third object with simple relationships. When you need to model an associative relationship for persistence, it can be modeled as:package P

{

entity A { };

entity B { };

entity C { };

relationship R1

{

role A toB 1..1 C;

role C toA 1..1 A;

};

relationship R2

{

role C toB 1..1 B;

role B toA 1..1 C;

};

};

011108-000003 Summary PAF: Retry count exceeded doesn't bring down engine.

A persistent component that is configured for a Retry Mode of "Limited Retry" will not exit during initialization if it cannot establish connections to the database. This is incorrect. It should exit after Max Retries number of attempts to establish the database connections.

Workaround None.

000905-000002 Summary PAF: Setting LC_MESSAGES to C causes ODBC errors.

Setting the LC_MESSAGES environmental variable to 'C' (ie export LC_MESSAGES=C) causes ODBC to incorrectly report SQL State information. This causes the persistence adapter to incorrectly detect errors returned by database servers.

This is a bug in the ODBC manager and drivers.

Workaround Unset the LC_MESSAGES variable in the environment of any engine containing persistent objects.



14 | Release Notes

020507-000003 Summary PAF: ODBC failure if LD_LIBRARY_PATH too long.

There is a known bug with ODBC where it crashes if LD_LIBRARY_PATH is set to a value that is too long. This is a bug in the 3rdparty ODBC drivers.

Workaround Ensure that the LD_LIBRARY_PATH only contains paths required to run the KIS persistence engine.

An example of the type of crash that can be seen is:/opt/softwire/os40/objectswitch/users/namon/deploy/distrib/sol/l

ib/libsyssrv.so:void*startFunction(void*)+0x498

/usr/lib/libthread.so.1:_getfp+0x220

/usr/lib/libthread.so.1:_fork+0x850/opt/softwire/os40/objectswitch/3rdparty/odbc40/sol/lib/libDSutl17.so:LoadString+0x2b4 ??:??+0x31abe5f7

thrd.cpp:709: fatal condition in 'signalHandler'

utl_dump_stack: Start of stack trace.



Documents

TIBCO Kabira® Adapter Factory for Persistence Release Notes