ODBC 6 install on Centos7

Hi everyone. I have a Facts customer who is upgrading to 9.3 on a new Centos7 box. From what I researched, the recommended odbc version 6, is not specifically supported for

Centos7 (only lists up to version 6). I have installed the odbc server many times. I do notice a few changes including a catalog entry which I haven't seen before,but my main

issue is after doing the install and changing of the conf file, when I go to run the server which is the same command as I'm used to, I get back to the cursor, no error, but I see

no server process running. I turned on logging and the entry says it' started, don't see an error, but it is not running. I guess I'm not sure if it's something I'm missing in the install

or is it truly an issue with odbc and centos version 7. Does anyone have Facts and odbc running on linux 7? Downgrading to 6 is being considered, but I'm hoping it's something

simple to resolve this !!

Thanks, Bob

Daily Support Tasks.docx

Find more posts tagged with

Accepted answers

All comments

Deepak Mehra

Hi Bob,

If this is the ODBC 6.1 server version, they introducted the new catalog functionality which I believe has to be setup in order for the service to start successfully (we have this running on a RHEL7 system successfully)

In the config file, you need to set up at least one catalog entry for it to be able to start correctly. Here's an example of one of ours running a FACTS live environment in the /usr/infor/facts93/ directory:

catalogs:
facts_live=facts_live=*[/usr/infor/facts93][/usr/infor/facts93/dict/FACTSDD.INI][/usr/infor/facts93/]

Then in the ODBC client DSN configuration, you would just specify the catalog name of "facts_live" rather than specifying the directory paths.

jeff-christie

thanks for the reply Ryan. I did see the catalog entry needed and added an entry. Actually, I think I got those right based on your screenshot. Just didn't have the last / on the 3rd entry. Changed that but it still won't start. It's weird. I'm pretty positive I did the install correctly. I've done the odbc server install dozens of times on previous versions. But when I do the start command, it just returns to the #, no error, but the process isn't there nor the .pid file that gets created.

[root@erp pxpsqlsvr]# pwd
/usr/pxpsqlsvr
[root@erp pxpsqlsvr]# ls
install.txt license.txt pxpsqlsvr.conf pxpsqlsvr.log
libpxpio.so pxpsqlsvr pxpsqlsvr.conf.sample readme.txt
[root@erp pxpsqlsvr]# /usr/pxpsqlsvr/pxpsqlsvr
[root@erp pxpsqlsvr]#
[root@erp pxpsqlsvr]# ps -ef |grep pxpsql
root 9587 9352 0 09:21 pts/0 00:00:00 grep --color=auto pxpsql
[root@erp pxpsqlsvr]# ls
install.txt license.txt pxpsqlsvr.conf pxpsqlsvr.log
libpxpio.so pxpsqlsvr pxpsqlsvr.conf.sample readme.txt
[root@erp pxpsqlsvr]#

Legacy Contributor

Bob,

Does the content of the .log file provide any insight?

Deepak Mehra

Hi Bob,

Would you be able to paste/include the contents of your pxpsqlsvr.conf file?

(Also I'm assuming that the libpxpio.so file has been copied to the /usr/lib64 directory?)

jeff-christie

I will paste it shortly, but I have copied that file to /usr/lib64 several times now!! Just in case I had messed that up somehow! And Chris I did start it with -d a few times and I will paste the log too, but from what I recall it looked normal, saying that the server had started..but I will include that too

jeff-christie

here's the files i left the serial= line off, but I have tried it with the serial number and without one just to see if that mattered but it made no difference:

[root@erp pxpsqlsvr]# cat pxpsqlsvr.log

Opened Log file
PxPlus SQL Server: server is started.
[root@erp pxpsqlsvr]#

# PxPlus UNIX/Linux SQL Server
# Configuration Settings
#
# TCP/IP Port Number:
#
# TCP Port number that the Server will listen on
# The default value is port 20222
#
port=20222
#
#
# Activation Information:
#
# Activation information for the SQL Server must be supplied in the
# format of: serial=SerialNumber-UserCount-ActivationKey
#
# For those users purchasing a Professional or eCommerce edition
# of PxPlus that includes SQL ODBC support, you must use the
# SerialNumber, UserCount, and TEMPORARY activation key of your
# PxPlus Professional or E-Commerce License.
#
# For those persons who purchase SQL ODBC separately use the information
# given with your purchase.
#
# To run the SQL Server in Demonstration mode, set the serial= entry to a
# blank value. This will allow one user to access the server with Demo
# messages appearing periodically on the client's screen.
serial=
#
#
# View Library Path:
#
# Path to the libpvx.so library usually found in the PxPlus install directory.
#
# The PxPlus needs to be properly activated in order for views to work.
ViewLib=/erp/facts93/pvx
#
#
# Catalog Definitions:
#
# Define sets of data that the SQL server can access. The client will use the
# catalog name to tell the server what data it wants to access.
#
# The format for a catalog definition is:
# CatalogName=*[DDPath][INIPath][Prefix]
# Where:
# CatalogName is the name of the catalog. It can entered into the DSN
# config on the client.
#
# * indicates the default catalog. There can be only one default.
#
# DDPath is the location of the PxPlus Data Dictionary file (providex.ddf).
#
# INIPath is the path and name of the INI file used to define the data
# dictionary manually.
#
# Prefix is the search paths to be inserted in front of all relative file
# references used in Data Dictionary or INI definitions. Use a comma as
# the separator between multiple prefixes.
#
#catalogs:
facts93=*[/erp/facts93][/erp/facts93/dict/FACTSDD.INI][/erp/facts93/]
#
#
# File Access Security Policies:
#
# The PxPlus SQL Server provides customizable security for users and
# files. The format for a security policy entry is:
# UserID/CompanyCode=[Mode][Type][DDPaths][INIPaths]
# Where:
# UserID is the UserID entered into the DSN config on the client,
# An Asterisk (*) signifies all UserID's
#
# CompanyCode is the Company entered into the DSN config
# An Asterisk (*) signifies all CompanyCode's
#
# Mode is either A or D for Access or Denied. Denied mode allows
# an administrator to temporarily deny access without removing the
# policy entry.
#
# Type is either R for read-only or RW for read-write
#
# DDPaths is a comma separated list of DDPaths which may be used
# in the clients DSN setup. An Asterisk signifies any DDPath.
#
# INIPaths is a comma separated list of INIPaths which may be
# used in the clients DSN setup. An Asterisk signifies any INIPath.
#
# Security Policies are applied by evaluating all of the available rules
# from the maximum restriction to lowest restriction, The application order
# for security policies are:
# UserID/Company (Specific UserID with a specific CompanyCode)
# UserID/* (A specific UserID with any CompanyCode)
# */Company (Any UserID with a specific CompanyCode)
# */* (Any UserID, Any CompanyCode
#
# Unless specifically granted in a security policy configuration line, ACCESS
# TO ALL ODBC RESOURCES IS DENIED.
#
# To aid in installation and setup, the following policy is included in this
# sample configuration file:
# */*=[A][R][*][*]
# This translates to Any UserID and Any Company Code is granted Read-only
# Access to any DDPath and any INIPath given in the DSN configuration screen
# on the Client Workstation.
#
# We STRONGLY recommend that the Server administrator remove this policy prior
# to operating the Server in a live environment.
#
# Note, Access policies are currently kept only by UserID/CompanyCode, which
# means that only one UserID/CompanyCode may only have one policy entry. It
# is not currently possible to specify that a specific UserID/CompanyCode has
# read access to one set of entries, and read-write access to a different set
# of entries.
#
# Examples:
# John/ABC=[a][r][/myapp/apdata][*]
# Sherry/DEF=[a][rw][/myapp/ardata,/myapp/apdata][*]
#
# This example shows that all users are denied access to everything, except
# John from Company ABC who has read access to the dictionary in the apdata
# directory, and Sherry who has read-write access to the dictionaries in the
# ardata and apdata directories.
#
security:
*/*=[a][r][*][*]

Copyright © 2025 Infor. All rights reserved.