Troubleshooting data access
If you have problems accessing data from an ODBC-enabled application, follow the instructions in this topic. If you’re caching the system catalog, also see Troubleshooting system catalog caching.
For information on troubleshooting problems encountered when generating a system catalog, see Troubleshooting system catalog generation.
Review the repository definitions
If you have problems accessing data, or if data does not display as expected, the problem might be with the way the data is defined in the repository.
- Have you opened up the repository files in S/DE Repository to verify that the structures are assigned to files and that the structures are set up correctly?
- Have you checked the repository definitions for all fields to verify that they are defined as expected?
- Are you able to open the data files in a Synergy application?
See Setting up a repository for more information.
Because environment variables are crucial in enabling xfODBC to locate files, it is important to verify them.
- If you used environment variables in the repository Open filename field, have you also defined them in the connect file, in an environment setup file, or in the environment?
- Is GENESIS_HOME set correctly? For information, see Specifying the connect file location (GENESIS_HOME).
- Have you set variables in an environment setup file? If so, does SODBC_INIFIL point to the directory where the environment setup file is located? For stand-alone configurations, is SODBC_INIFIL set in the environment or in the connect file? For client/server configurations, is it set in the environment on the server?
- Have you set environment variables in the connect file? If so, make sure SODBC_INIFIL is not set in the environment. xfODBC uses environment variables set in the connect file only if SODBC_INIFIL itself is set in the connect file or is not set at all.
Verify file locations
- Is the connect file located in the directory that the GENESIS_HOME environment variable is set to? If not, did you specify the filename and path for the connect file when you configured the DSN?
- If you’re using the datasource line in the connect file to specify the location of your Synergy data files, are all the data files stored in the directory specified on the datasource line?
- Are the system catalog files stored in the directory specified on the dictsource line in the connect file? See System catalog for information on these files.
Verify the system catalog
- Have you used the fcompare utility to compare the system catalog to the data files? For information, see Comparing the system catalog to a database.
- Have you generated the system catalog using the conversion setup file as input? Have you checked the conversion setup file to verify table locations, inclusion, and access?
- Have you made changes to the conversion setup file since generating the system catalog? If so, have you regenerated the system catalog?
Use DBA to verify the system catalog
You can use the xfODBC Database Administrator (DBA) program to verify that the data definitions were converted correctly.
- Have you used the Verify option in DBA to ensure that DBA is able to find and read all the tables, columns, tags, and indexes?
- Have you compared the Repository data with each of the table attributes and column definitions as they appear in DBA?
- Have you ensured that table access levels are set appropriately?
- Have you verified that users have appropriate access levels?
If you have verified environment variables and file locations and you are still unable to connect, check the encryption settings on the client (in net.ini) and on the server (in the vtxnetd or vtxnet2 command line). Make sure these settings match, or for testing, remove the encryption settings in both locations and see if you can connect. Additionally, make sure the net.ini file is in the directory specified by VORTEX_HOME. Mismatched encryption settings, along with the inability to access encryption settings in net.ini, can cause a variety of errors when you try to connect, including “invalid connect syntax,” “invalid user ID and/or password,” and “invalid DSN” errors. For more information, see Setting SQL OpenNet client options in net.ini.
Verify the log-in
- Using DBA, verify usernames and passwords. When entering the connect string, did you type the username and password exactly as stored? They are case sensitive.
- To debug your initial connection, use Synergy DBMS logging. See Error logging for xfODBC for more information.
On Windows you can test a network connection with vtxping (or synxfpng with the -x option). See xfODBC: testing the network connection for client access.
Open your database with a third-party application
Did you generate a system catalog from the Synergy sample database, and were you able to access this data successfully with an ODBC-enabled application?
Note that Synergex does not provide support for other ODBC-enabled applications, and resolving problems particular to a specific third-party application is beyond the scope of this documentation.
If you have followed all the above troubleshooting steps and are still unable to access your database, turn on the ODBC logging options and use the tracing feature. See Error logging for xfODBC for instructions. You may need to call Synergy/DE Developer Support for an interpretation of the log files you generate.
Other sources of information
The Synergy/DE KnowledgeBase is available in the Resource Center on the Synergex website for customers who have purchased a support agreement. The KnowledgeBase includes a wealth of troubleshooting information and answers to frequently asked questions that may help you solve a problem you have encountered. To purchase a support agreement, contact your Synergex account executive.
- Release notes
The REL_CONN.TXT release notes distributed with Connectivity Series include the latest information about new features and restrictions in xfODBC.