Skip to main content

Ingres resource limiting : Part5 (Screenshots/Log table)

Actual screenshots from operation in action :

Trapped Form
Exception caught
(Admittedly scary message for the user!Not exactly what I was taught once upon a time in the HCI class!!)
Action cancelled

The log table structure :
help qep_abf_log

Name: qep_abf_log
Owner: psnouser
Created: 24/06/2008 09:05:56
Type: user table
Version: II2.5

Column Information:
Column Name Type Length Nulls Defaults Seq
application char 10 no no
dbuser char 10 no no
terminal char 60 no no
entrydate date no no
querytext char 200 no no
errortext char 200 no no

An entry in the table (executing an insert into table (values) select from table1 where...) :
|grk |psuser |/dev/ttyp3 |12/10/2008 12:09:00 |insert into esk300devttyp3 (am_asq, d_kin, c_eid, c_grn) select kin.am_asq, kin.d_kin, kin.c_eid,c_grn=kin.c_grn_pr from kin, mas where mas.am_asq=kin ... |E_QE0203 The estimated number of IO requests to run this query (3982)\n exceeds the IO limit (1000) established for this session. \n The query is aborted with a fatal l error.\n (Wed Jun 25 12:08:44|

Another entry in the table (executing a simple select) :
|grk |psnouser |/dev/ttyp0 |14/10/2008 06:37:00 |select table_name as h_table from iicolumns where (table_owner='psuser' and table_name='esk2520devttyp0' ) |E_QE0203 The estimated number of IO requests to run this query (12)\n exceeds the IO l imit (10) established for this session. \n The query is aborted with a fatal error.\n (Tue Oct 14 06:36:56 |


Popular posts from this blog

Serverless JavaScript

We recently joined in an interesting two-hour long conversation about Serverless JavaScript led by Steve Faulkner of Bustle who answered questions on Bustle, the Shep framework, the mindset behind the AWS Lambda infrastructure, and related topics.

The discussion took place on the Sideway conversation-sharing platform on January 6th. Here we present the best takeaways from the session which really should be taken notice of by anyone working on AWS.

Steve Faulkner:
At Bustle we serve over 50 million unique readers per month through a "serverless" architecture based on AWS Lambda and Node.js.  Of course there are still servers but we don't manage them. This shift has allowed us to develop products faster and decreased the cost of our infrastructure. I'll answer any questions about how we made this transition and how it has worked out. I'll also discuss some of the tools and best practises including our open source framework shep

Eran Hammer:
When would you…

Export your Wunderlist tasks with XPath

As brought up in this ProductHunt thread, the news is that Wunderlist is going to be deprecated in favor of the new Microsoft To-Do note taking platform.

This is what Wunderlist support had to say in response to my inquiry on Wunderlist's future:

"Now that the next evolution of Wunderlist is here, in the form of Microsoft To-Do Preview (, Wunderlist will no longer receive any updates or bug fixes and will eventually be retired. It won’t happen in the next few months and we’ll be sure to give our users plenty of notice beforehand. In the meantime, you can continue to use Wunderlist normally. Of course, we’d also love for you to try To-Do and let us know how you like it – and how we can improve it. While Wunderlist will continue to exist alongside To-Do for the time being, support for Wunderlist will eventually be removed. Not to worry, though! We will inform all Wunderlist users prior to shutting down service. You'll have ample opport…

Google's Cloud Spanner To Settle the Relational vs NoSQL Debate?

Cloud Spanner is a new proposition for database as a service that emphatically offers "Relational with NoSQL scaling". Will Google come to dominate yet another market?

Once upon a time there was only one kind of database management system, the RDBMS, "R" for relational. Despite its resilience and trustworthiness, it had its shortcomings; it did not scale well, and the relational model it served proved inadequate in the dawn of the Big Data era for handling massive amounts of schema-less, unstructured data.
For this and a few other reasons, a new breed of DBMS's emerged, one that could handle the avalanche of big data, based on the notion of the key-value pair, and doing so by scaling horizontally. But, in order to become versatile, this new breed of management systems had to forgo the safety of the ACID and the cosiness of SQL, both long term partners of the relational model. full article on i-programmer