Error Cannot Read System Catalog Sysprocplan
Sep 13 - telecompaper - Shaspa and Tatung have shown a new smart home platform at Ifa in Berlin. Powered by the IBM Informix software... Read 06 Sep 13 - IBM data magazine - Mission Accomplished - Miami, Florida will be the backdrop for the 2014 IIUG Informix Conference... Read 01 Feb 13 - IBM Data Magazine - Are your database backups safe? Lester Knutsen (IBM Champion) writes about database back up safety using "archecker"... Read 14 Nov 12 - IBM - IBM's Big Data For Smart Grid Goes Live In Texas... Read 3 Oct 12 - The Financial - IBM and TransWorks Collaborate to Help Louisiana-Pacific Corporation Achieve Supply Chain Efficiency... Read 28 Aug 12 - techCLOUD9 - Splunk kicks up a SaaS Storm... Read 10 Aug 12 - businessCLOUD9 - Is this the other half of Cloud monitoring?... Read 3 Aug 12 - IBM data management - Supercharging the data warehouse while keeping costs down IBM Informix Warehouse Accelerator (IWA) delivers superior performance for in-memory analytics processing... Read 2 Aug 12 - channelbiz - Oninit Group launches Pay Per Pulse cloud-based service... Read 28 May 12 - Bloor - David Norfolk on the recent Informix benchmark "pretty impressive results"... Read 23 May 12 - DBTA - Informix Genero: A Way to Modernize Informix 4GL Applications... Read 9 Apr 12 - Mastering Data Management - Upping the Informix Ante: Advanced Data Tools... Read 22 Mar 12 - developerWorks - Optimizing Informix database access... Read 14 Mar 12 - BernieSpang.com - International Informix User Group set to meet in San Diego... Read 1 Mar 12 - IBM Data Management - IIUG Heads West for 2012 - Get ready for sun and sand in San Diego... Read 1 Mar 12 - IBM Data Management - Running Informix on Solid-State Drives.Speed Up Database Access... Read 26 Feb 12 - BernieSpan.com - Better results, lower cost for a broad set of new IBM clients and partners... Read 24 Feb 12 - developerWorks - Informix Warehouse Accelerator: Continuous Acceleration during Data Refresh... Read 6 Feb 12 - PRLOG - Informix port delivers unlimited database scalability for popular SaaS application ... Read 2
(FAQ) Question You are designing an application against Informix Dynamic Server (IDS) that calls a stored procedure during a transaction. You are concerned that a stored procedure recompile during the transaction will lock the record in sysprocplan for the entire transaction, and other calls to the stored procedure will fail because of the lock. Cause The object dependency list for a stored procedure is checked just prior to procedure http://www.iiug.org/forums/ids/index.cgi/noframes/read/15286 execution. If the check detects any changes in the objects after the last procedure compile, the stored procedure is recompiled. Procedure compile places a lock on the sysprocplan table. Execution of the procedure from another session can fail because of the lock, with error: 211: Cannot read system catalog (sysprocplan). and an accompanying http://www.ibm.com/support/docview.wss?uid=swg21447888 ISAM error showing the failure is because of a lock. Answer IDS was modified in fixpaks 10.00.xC7 and 11.10.xC2 to minimize the effect of sysprocplan locking during a transaction. A child transaction is spawned from the parent transaction for the purpose of updating sysprocplan. The child transaction commits and releases locks on sysprocplan when the sysprocplan update completes. You can confirm the transaction behavior by examining the logical log records using the onlog utility. You will see nested BEGIN and COMMIT records. You can also observe the locks at various stages in the transaction using the onstat -k command. Related information Stored procedures - sysprocplan - dependency list Document information More support for: Informix Servers Software version: 10.0, 11.1, 11.5, 11.7 Operating system(s): AIX, HP-UX, Linux, OS X, Solaris, Windows Reference #: 1447888 Modified date: 2014-06-26 Site availability Site assistance Contact and feedback Need support? Submit feedback to IBM Support 1-800-IBM-7378 (USA) Directory of worldwide contacts Contact Privacy Terms of use Accessibility
von GoogleAnmeldenAusgeblendete FelderNach Gruppen oder Nachrichten suchen
one of these important tables, a serious error results. Check the accompanying ISAM error code for more information. The effect of the error depends on the statement that is being executed and the particular table, as follows: * CREATE TABLE statement, systabauth not read; the table is created, but PUBLIC is not granted authorization as it normally is.
* DROP TABLE statement, systables not read; no action taken. * DROP TABLE statement, sysviews not read; the table is dropped but any views that depended on the table were not automatically dropped. * DROP VIEW statement, sysviews not read; no action taken. * DROP INDEX statement, sysindexes or systables not read; no action taken. * DROP SYNONYM statement, systables or syssynonyms not read; no action taken. * DROP DATABASE statement, systables not read; no action taken. * START DATABASE statement, systables not read; no action taken. * DATABASE statement, systables or sysusers not read; the database was not selected (no current database; for subsequent operations, see error -349). Other statements might be partially complete before the error is detected. Roll back the current transaction and then investigate the cause of the error. Use the oncheck utility (secheck with IBM Informix SE or oncheck with IBM Informix OnLine) to check and repair indexes. If necessary, restore the database from backup and logical-log tapes. Copyright Privacy