Troubleshooting
The following provides troubleshooting information specific to MySQL.
Link Error
Section titled “Link Error”Error 0 occurs opening the Link and no locks seem to be active in Basic or from an SQL application.
Since the Link header is read internally by Basic when opening the Link, this record needs to be accessible at open time. If it is extracted through Dictionary-IV, for example, the error 0 occurs. Setting the PRM READONLY parameter in the IPLINPUT file will clear this situation.
Server Table Error
Section titled “Server Table Error”Errors opening server tables.
- Verify that the DEV line for the server where the table resides is present in the appropriate IPLINPUT file.
- Verify the user has MySQL credentials for the Database and Table.
- Verify the Link has a Table name. If the associated Format has text fields defined, verify that the Link also has a Text File Name.
Unexpected Sorting Sequence or Errors Accessing SQL Tables
Section titled “Unexpected Sorting Sequence or Errors Accessing SQL Tables”- If a Link header has been configured to access a server table defined on the server as a view, unexpected results ranging from incorrectly sorted data to tsmssql process failures may result. It is suggested that access to the server be limited to objects defined as tables. SQL does not support certain operations on views such as SELECT …FOR UPDATE. This may also occur if a table has no index and the fields in the sort are defined as NULL. This can be resolved by adding an index and/or changing the field constraint to NOT NULL.
- Be sure that the primary key index is present.
Some Access Using Sorts is Very Slow
Section titled “Some Access Using Sorts is Very Slow”Sorts that contain references to substrings of fields may not perform as well as sorts on full fields. This is because MySQL has no facility to define indexes on portions of fields. For more information see the Performance Tuning section of this manual.
From the TS DataServer for MySQL Reference, version 8.9.1. Open this page in the PDF