Informix - Problem description
Problem IT37128 | Status: Closed |
EXCESSIVE READS ON SYSPROCAUTH IF PROCEDURE DOES NOT HAVE 'PUBLIC' EXECUTE PERMISSION OR USER DOES NOT HAVE DBA PRIVILEGE | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
A session will maintain a local cache of stored procedure ids for which the execute or grant with execute permissions are available. This cache only lists those procedures for which public execute permissions are granted meaning that non-dba users will need to query the sysprocauth system catalogue table to determine the execute permission for other procedures. This can result in a high number of reads against that table with a loss of performance. | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 12.10.xC15 and 14.10.xC7. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 12.10.xC15 or 14.10.xC7 (when * * available). * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
**************************************************************** * USERS AFFECTED: * * Users of Informix Server prior to 12.10.xC15 and 14.10.xC7. * **************************************************************** * PROBLEM DESCRIPTION: * * See Error Description * **************************************************************** * RECOMMENDATION: * * Upgrade to Informix Server 12.10.xC15 or 14.10.xC7 (when * * available). * **************************************************************** | |
Comment | |
Fixed in Informix Server 12.10.xC15 and 14.10.xC7. | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 04.06.2021 25.08.2021 25.08.2021 |
Problem solved at the following versions (IBM BugInfos) | |
Problem solved according to the fixlist(s) of the following version(s) |