Re: oninit -i refuses to work

At 12:13 AM 8/13/96 GMT, you wrote: >We had an existing database and wanted to drop it. >We shut down the working database and took it offline. > >We just tried oninit -i and got the response > >oninit: Not enough room for ROOT dbspace. >Fatal error initializing shared memory.> >Why? And how can we do oninit -i? > >Martin Haltmayer My initial impression is that something in the onconfig file changed (grew larger) such that the oninit -i cannot fit the new information into theroot dbspace. There are several things which may cause this, among them: Upgrading. The ODS product requires much more disk space than previous versions. See the release notes and New Features Guide. System Admin Changes. Your friendly sysadmin has changed the size of your root dbspace while the engine was down. Onconfig changes. Remember, changes to this file do not take effect until the engine is re-started. The fix is to edit the onconfig file, adjust the parameters that affect the size of the root dbspace downward, and re-try the oninit command. These are some impressions only. In the future, please supply detailed version information, the relevant parts of the actual onconfig file as well as O/S details. (Paradoxically, too much detail will bore the readers of this forum, and they won't help you.) Good luck, ______________________________________________________ Clem Akins (aka clema@informix.com) Informix Software, Inc (Standard disclaimers apply) International Technical Support Last seen: in populous Mexico City!