Re: Fill my rootdbspace, please
Red Valsen wrote: > > What happens if some nefarious user fills my rootdbspace? I'm thinking > of the case in which a user, with no connection privileges to any > database, nevertheless creates a new database in the default dbspace, > rootdbs, then procedes to create a table and fill it until the chunk is > at 100% capacity. What happens to the instance then? It's not going to crash your instance, if that's what you mean. Certain operations might fail, namely anything which tries to write to your root dbspace. In a well designed database server, there should be no activity in the root dbspace, thus you can keep it small ensuring that it's the nefarious user who gets all the errors. However, I have yet to find a well designed database server. :-) Moving your logs, databases and tables to other dbspaces is quite straight forward. It's usually temp tables that cause the problem, or in particular logging temp tables. These cannot be created in temp dbspaces. A common suggestion on this list is to create a mix of temp and non-temp dbspaces for temp table creation. You would typically define your DBSPACETEMP variable with alternate dbspace types for optimum performance. Cheers, -- Mark. +----------------------------------------------------------+-----------+ | Mark D. Stock mailto:mdstock@mydas.freeserve.co.uk |//////// /| | http://www.informix.com http://www.informixhandbook.com |///// / //| | http://www.iiug.org +-----------------------------------+//// / ///| | |What year 2000 bug? year 2000 bug? |/// / ////| | |year 2000 bug? year 2000 bug? year |// / /////| | |2000 bug? year 2000 bug? year 1900 |/ ////////| +----------------------+-----------------------------------+-----------+
Mark Stock wrote: > [...sage advice about rootdbs...] > Moving your logs, databases and tables to other dbspaces is quite > straight forward. It's usually temp tables that cause the problem, or in > particular logging temp tables. These cannot be created in temp > dbspaces. Can anyone think of a sound reason for wanting logged temp tables? Why wasn't the default changed to 'WITH NO LOG' once the option was introduced, with the analogous explicit 'WITH LOG [IN (dbspace1, dbspace2, ...)]' being created for those circumstances that someone will describe when a logged temp table is actually of some benefit? -- Jonathan Leffler (jleffler@informix.com, jleffler@earthlink.net) Guardian of DBD::Informix v0.95 -- see http://www.perl.com/CPAN #include <disclaimer.h>