Linux
Pervasive PSQL v11 SP1 includes the following support for the Linux operating system:
•
64-bit ODBC Driver
•
Red Hat Enterprise Linux 6
64-bit ODBC Driver
Pervasive PSQL v11 SP1 supports the ODBC interface for 64-bit applications on Linux. The 64-bit ODBC driver is installed with Pervasive PSQL Server 64-bit and Pervasive PSQL Client 64-bit.
On Linux distributions, individual ODBC drivers are loaded through the driver manager UNIXODBC. The driver manager maintains a mapping from Data Source Names (DSNs) to the specific Pervasive PSQL ODBC drivers.
The installation of Pervasive PSQL Server 64-bit or Client 64-bit leaves user-defined, pre-existing 32-bit DSNs as is, meaning they are not immediately accessible from a 64-bit application. For new DSNs, the installation of both products assigns a 32-bit and a 64-bit ODBC driver in odbcinst.ini. This assignment allows a single DSN to be used by both a 32-bit application and a 64- bit application.
If you want pre-existing 32-bit DSNs to be accessible to both 32-bit and 64- bit applications, you must recreate them as new-style DSNs (see Pervasive ODBC Interface in Table 7).
ODBC and Data Source Names (DSNs)
The client application bitness does not have to match the bitness of the Pervasive PSQL Server product. For example, the 64-bit ODBC driver or the 32-bit ODBC driver can be used to connect to either Pervasive PSQL Server 64-bit or Pervasive PSQL Server 32-bit.
For the Pervasive PSQL Client, however, the application bitness does have to match the bitness of the Pervasive PSQL Client on the client machine. That is, if you want to use a 64-bit application on the client, the Pervasive PSQL 64-bit Client must be installed.
Pervasive PSQL v11 provides three ODBC drivers, as explained in the following table.
Table 7
Pervasive PSQL ODBC Driver Descriptions for Linux
ODBC Driver Description in INI Files
PSQL Product Installed With
Behavior for All Products Installed With
Pervasive ODBC Engine Interface
Server 64-bit
Server 32-bit
•
Installation assigns an ODBC driver in odbc.ini for compatibility with pre-existing Engine DSNs
•
Connects to a local named database
•
No longer created by default with dsnadd utility (the -engdsn option must be specified). See also Utilities Affected by ODBC Changes.
•
Visible when viewing “Engine DSNs” in ODBC Administrator running on a Windows client
•
For use by 32-bit applications that are already coded to use Engine DSNs
•
32-bit Engine DSNs deprecated in Pervasive PSQL v11. See What Was New in Pervasive PSQL v11 SP1.
Pervasive ODBC Client Interface
Server 64-bit
Server 32-bit
Client 32-bit
•
Installation assigns an ODBC driver in odbc.ini for compatibility with pre-existing Client DSNs
•
Connects to a local or remote named database or an Engine DSN
•
For use by 32-bit applications that are already coded to use Client DSNs
•
No longer created by default when -host is specified with dsnadd (the -clntdsn option must be specified). See also Utilities Affected by ODBC Changes.
Pervasive ODBC Interface
Server 64-bit
Client 64-bit
•
Installation assigns ODBC drivers in odbcinst.ini for use by new 32-bit and 64-bit DSNs
•
Connects to a local or remote named database
•
The recommended driver description to use for 32-bit and 64-bit applications
•
Created by default with dsnadd utility. See also Utilities Affected by ODBC Changes.
•
Not visible as “Engine DSNs” in ODBC Administrator running on a Windows client
Frequently Asked Questions
The following table answers some frequently asked questions (FAQs) about the ODBC and DSN support for Linux in Pervasive PSQL v11 SP1.
Table 8
FAQs About ODBC and DSN Support for Linux 
Question
Answer
Have 32-bit Engine DSNs been deprecated?
Yes. Pervasive recommends, rather than using Engine DSNs, that new applications or revised 32-bit applications create a DSN that connects to a named database. See also What Was New in Pervasive PSQL v11 SP1.
What is a so called “DSN-less” connection?
A DSN-less connection is one that connects to a named database using the ODBC driver “Pervasive ODBC Client Interface” (for pre-existing 32-bit applications) or the “Pervasive ODBC Interface” driver (for 32-bit or 64-bit applications).
What happens to my existing 32-bit Engine DSNs when I upgrade to Pervasive PSQL v11 SP1 Server or Client?
No migration steps are required. Existing user-defined 32-bit Engine DSNs remain in place and continue to work as configured. Applications on the PSQL Server or Client machine continue to work with 32-bit Engine DSNs.
An exception to this is the DEMODATA sample database installed with Pervasive PSQL Server 64-bit. The DSN for DEMODATA is recreated during installation using “Pervasive ODBC Interface” to connect to a named database.
If you want pre-existing 32-bit DSNs to be accessible to both 32- and 64-bit applications, you must recreate them using “Pervasive ODBC Interface” to connect to a local or remote named database.
What happens to my existing 32-bit Client DSNs when I upgrade to Pervasive PSQL v11 SP1 Client?
No migration steps are required. Existing Client DSNs continue to connect to remote Engine DSNs.
Note, however, the recommendation is that new applications or revised 32-bit applications should connect to a named database, not to an Engine DSN since Engine DSNs are deprecated.
Can I still create Engine DSNs and Client DSNs?
Yes, but you must specify the -engdsn or -clntdsn option with dsnadd. See Utilities Affected by ODBC Changes. DSNs created with either option support only 32-bit applications.
What about connections from PSQL Clients of previous releases (such as a PSQL v10.x Client)?
Pervasive PSQL still supports remote Client DSNs, so clients from previous versions can still connect.
Note, however, Engine DSNs are only 32-bit for both Pervasive PSQL Server 32-bit and 64-bit. 64-bit Engine DSNs cannot be created with Pervasive PSQL.
What are the ODBC connection strings for Pervasive PSQL DSNs?
See ODBC Connection Strings in SQL Engine Reference.
What do I need to do about DSNs if I port my 32-bit application to 64-bit?
You must create new DSNs that connect to a named database using “Pervasive ODBC Interface.”
What about the DSNs for the Demodata sample database installed with the database engine?
The installation of Pervasive PSQL Server 64-bit or Client 64-bit creates the DEMODATA DSN using “Pervasive ODBC Interface” to connect to a named database. This means that clients using Windows ODBC Administrator no longer see DEMODATA in the list of Engine DSNs from the Pervasive PSQL Server. The clients have to view the Database Names list instead. A 64-bit application would not be able to connect to DEMODATA through an Engine DSN.
What if my application uses DTI to manage DSNs?
The DTI functions for DSNs manage only 32-bit Engine DSNs. Therefore, the DTI functions for DSNs are deprecated along with the 32-bit Engine Interface ODBC driver. See What Was New in Pervasive PSQL v11 SP1.
(An alternative to using DTI to manage DSNs is to use SQL and ODBC statements. For example, you could use CREATE DATABASE to create a named database and SQLConfigDatasource to configure the DSNs.)
Does Pervasive PSQL v11 SP1 include new utilities to support 64-bit ODBC and DSNs?
Yes. See Utilities Affected by ODBC Changes.
Are there any changes to existing utilities to support 64-bit ODBC and DSNs?
Yes. See Utilities Affected by ODBC Changes.
Do some descriptor fields that can be set through the various ODBC SQLSet and SQLGet functions accommodate 64-bit values while others are still 32-bit values?
Yes, if you are using the 64-bit ODBC driver. Ensure that you use the appropriate sized variable when setting and retrieving descriptor fields. For more information, see http://www.unixodbc.org/doc/ODBC64.html.
A point of clarification is that SQL_ROWSET_SIZE is supported by both SQLGetStmtOption and SQLGetStmtAttr. If you are using the 64-bit ODBC driver and you call either SQLGetStmtOption or SQLGetStmtAttr, a 64-bit value is returned in *ValuePtr when that attribute parameter is set to SQL_ROWSET_SIZE.
Going forward, is there a recommended strategy for ODBC connections?
Yes. New applications or revised 32-bit applications, local or remote, should connect to a named database.
This positions your application for the future when Engine DSNs will no longer be supported in Pervasive PSQL.
(Note that you can manage DSNs through the use SQL and ODBC statements. For example, you could use CREATE DATABASE to create a named database and SQLConfigDatasource to configure the DSNs.)
ODBC Header Files
The sql.h, sqltypes.h, and sqlext.h header files for ODBC contain differences for the compilation of 32-bit and 64-bit applications. Refer to the ODBC documentation on the UNIXODBC Web site for a discussion of 64-bit ODBC. For example, you may find the following information useful: http://www.unixodbc.org/doc/ODBC64.html.
Utilities Affected by ODBC Changes
•
A 64-bit version of isql, isql64, is installed with Pervasive PSQL Server 64-bit and Client 64-bit. See isql in Pervasive PSQL User's Guide.
•
The dsnadd utility has been changed to create a DSN using “Pervasive ODBC Interface” by default. This style DSN allows a single DSN to be used by both a 32-bit application and a 64- bit application. The DSN is not visible as an Engine DSN in ODBC Administrator, and the string "Pervasive ODBC Engine Interface" is not present in the odbc.ini file.
If you want to create a deprecated, legacy-style Engine DSN or a Client DSN, you must specify the -engdsn or -clntdsn option, respectively. See dsnadd in Pervasive PSQL User's Guide.
•
The option to create a DSN on the New Database dialog Pervasive PSQL Control Center (PCC) is qualified for 32-bit: “Create 32-bit Engine DSN.” See New Database GUI Reference in Pervasive PSQL User's Guide.
PCC is a 32-bit application; a 64-bit version of it is not available. See also What Was New in Pervasive PSQL v11 SP1.
•
The Pervasive ODBC DSN setup GUIs have changed for Windows platforms. See What Was New in Pervasive PSQL v11 SP1.
Red Hat Enterprise Linux 6
Pervasive PSQL supports Red Hat Enterprise Linux 6. Note that, by default, the 64-bit edition of this Linux distribution supports only 64-bit components and executables. The distribution media for 64-bit Red Hat Enterprise Linux 6 includes the 32-bit libraries, but they are not installed by default.
The following table summarizes installation notes specific to Red Hat Enterprise Linux 6, including a discussion of certain 32-bit libraries required for Pervasive PSQL.
Pervasive PSQL Product
Installation Notes for Red Hat Enterprise Linux 6 64-bit
•
64-bit Server
•
32-bit Server
•
32-bit Client
The Pervasive PSQL installation RPM and TAR files check for the existence of the 32-bit GLIBC and LIBSTDC++ libraries. If these libraries are not present, the Pervasive PSQL installation stops and displays a message. To install Pervasive PSQL, you must first install glibc.i686 and libstdc++.i686.
The Pervasive PSQL installation RPM and TAR files also check for the existence of 32-bit GTK. If GTK is not present, Pervasive PSQL displays a warning message. The message informs you that PCC, DDF Builder and GUI Phone Authorization utilities will not function until 32-bit GTK is installed. The Pervasive PSQL installation continues and completes after displaying the message.
To ensure that PCC, DDF Builder and GUI Phone Authorization utilities work, install the following Linux packages:
•
gtk2.i686
•
PackageKit-gtk-module.i686
•
libcanberra-gtk2.i686
•
gtk2-engines.i686.
For example:
yum install gtk2.i686 PackageKit-gtk-module.i686 libcanberra-gtk2.i686 gtk2-engines.i686
Note that, except for the three utilities just mentioned, Pervasive PSQL is functional even if the 32-bit GTK is not present. That is, the database engine is functional, all command line utilities work and the Pervasive PSQL libraries are present and accessible by your applications. Your client applications should still function as long as they do not require the 32-bit GTK.
•
64-bit Server
•
32-bit Server
The Pervasive PSQL installation attempts to configure Samba. However, by default, Samba is only partially installed and is not enabled on Red Hat Enterprise Linux 6.
You may ignore installation errors pertaining to creating the PSQLDATA Samba share (the smb.conf file exists, but nothing is there to support it). The errors are benign and Pervasive PSQL functions normally.