Re: dbspace

Thuc Nguyen <thucn@inconnect.com> wrote in article <32ADA24E.784@inconnect.com>... > Before I was hired, another non-DBA SA wrote a script: > create database coris> that went to rootdbs automatically, I believe > It showed as > Database Name Owner In Dpspace When Created Log Status > coris informix rootdbs 01/24/96 B > > but > It should be > Database Name Owner In Dpspace When Created Log Status > coris informix coris1dbs 01/24/96 B > > coris1dbs is where the data/dbschema information is located in. > How can I change from rootdbs to coris1dbs? > > dbexport> drop rootdbs > create database coris in coris1dbs> new schema > dbimport> > Is there another way to make it easier? > > Thanks for your help The only way I know of to move the "home" dbspace of a database is to export it, drop it, and re-import it. The sequence would go something like this: From UNIX: dbexport coris From dbaccess: drop database coris From UNIX: dbimport coris -d coris1dbs This will re-create "coris" with out logging. If "coris" is small enough and your logs are large enough you might be able to import it with logging using the "-l" option. Otherwise you can turn logging on by doing a level 0 archive such as "ontape -s -B coris" to turn on buffered logging. While you're at it, you might want to check the number of extents and extent sizes for your tables before you export/import. You may want to modify the "dbexport" schema to use different extent sizes before importing. HTH -- Irwin Goldstein Objective Software Systems, Inc. http://www.objectsoft.com