Informix

Solaris 10  1/13

Informix 12.10.FC14

Assume that rootdbs has an original chunk, plus one (or more) additional chunks that have been added to the original rootdbs chunk.  Further assume that there are zero user objects in rootdbs, but that databases sysuser, sysutils, sysmaster, and sysadmin do exist there, and that their tables are spread over more than one (the original) chunk.  (This is the state I am hoping to achieve after a current tech support case with IBM is resolved.  The object of that case is to drop a phantom object, as described in this thread.).

I would like to drop all rootdbs chunks except the original chunk.

Might I accomplish this by dropping sysmaster, sysuser, sysutils; then dropping the (now completely empty) additional chunks; and then executing buildsmi, blduser, and blduser to recreate sysmaster, sysuser, and sysutils back in rootdbs (which would then consist of only the original chunk)?

The sysuser and sysutils databases are already empty-- so no data to preserve.  Sysadmin does have data, and would also be by using the admin() API to reset sysadmin, along with data import to load back the data already present.  Art's utilities (myexport and myimport -e) should be great for that.

Seems to me like it should work, but, maybe I am missing something significant.

DG

Sounds like a plan David!

Solaris 10  1/13

Informix 12.10.FC14

Assume that rootdbs has an original chunk, plus one (or more) additional chunks that have been added to the original rootdbs chunk.  Further assume that there are zero user objects in rootdbs, but that databases sysuser, sysutils, sysmaster, and sysadmin do exist there, and that their tables are spread over more than one (the original) chunk.  (This is the state I am hoping to achieve after a current tech support case with IBM is resolved.  The object of that case is to drop a phantom object, as described in this thread.).

I would like to drop all rootdbs chunks except the original chunk.

Might I accomplish this by dropping sysmaster, sysuser, sysutils; then dropping the (now completely empty) additional chunks; and then executing buildsmi, blduser, and blduser to recreate sysmaster, sysuser, and sysutils back in rootdbs (which would then consist of only the original chunk)?

The sysuser and sysutils databases are already empty-- so no data to preserve.  Sysadmin does have data, and would also be by using the admin() API to reset sysadmin, along with data import to load back the data already present.  Art's utilities (myexport and myimport -e) should be great for that.

Seems to me like it should work, but, maybe I am missing something significant.

DG

Thanks, Art.

The reason I even posted this is that the documentation specifically discusses use of buildsmi, bldutil, buildsmi, and task("reset sysadmin"), but makes no mention of blduser.  That caused me to wonder if there was something different about blduser that made it ill-advised to invoke (outside of the initial install of the instance).

Thanks, again.

DG

Sounds like a plan David!

Solaris 10  1/13

Informix 12.10.FC14

Assume that rootdbs has an original chunk, plus one (or more) additional chunks that have been added to the original rootdbs chunk.  Further assume that there are zero user objects in rootdbs, but that databases sysuser, sysutils, sysmaster, and sysadmin do exist there, and that their tables are spread over more than one (the original) chunk.  (This is the state I am hoping to achieve after a current tech support case with IBM is resolved.  The object of that case is to drop a phantom object, as described in this thread.).

I would like to drop all rootdbs chunks except the original chunk.

Might I accomplish this by dropping sysmaster, sysuser, sysutils; then dropping the (now completely empty) additional chunks; and then executing buildsmi, blduser, and blduser to recreate sysmaster, sysuser, and sysutils back in rootdbs (which would then consist of only the original chunk)?

The sysuser and sysutils databases are already empty-- so no data to preserve.  Sysadmin does have data, and would also be by using the admin() API to reset sysadmin, along with data import to load back the data already present.  Art's utilities (myexport and myimport -e) should be great for that.

Seems to me like it should work, but, maybe I am missing something significant.

DG

David:

I just look at the blduser.sh and sysuser.sql scripts and unlike sysmaster there is nothing funky going on there. Just a straightforward create database and a handful of tables. Should be fine. That said, as a good paranoid DBA I'd run that by Informix support just to be absolutely certain.

Art

Thanks, Art.

The reason I even posted this is that the documentation specifically discusses use of buildsmi, bldutil, buildsmi, and task("reset sysadmin"), but makes no mention of blduser.  That caused me to wonder if there was something different about blduser that made it ill-advised to invoke (outside of the initial install of the instance).

Thanks, again.

DG

Sounds like a plan David!

Solaris 10  1/13

Informix 12.10.FC14

Assume that rootdbs has an original chunk, plus one (or more) additional chunks that have been added to the original rootdbs chunk.  Further assume that there are zero user objects in rootdbs, but that databases sysuser, sysutils, sysmaster, and sysadmin do exist there, and that their tables are spread over more than one (the original) chunk.  (This is the state I am hoping to achieve after a current tech support case with IBM is resolved.  The object of that case is to drop a phantom object, as described in this thread.).

I would like to drop all rootdbs chunks except the original chunk.

Might I accomplish this by dropping sysmaster, sysuser, sysutils; then dropping the (now completely empty) additional chunks; and then executing buildsmi, blduser, and blduser to recreate sysmaster, sysuser, and sysutils back in rootdbs (which would then consist of only the original chunk)?

The sysuser and sysutils databases are already empty-- so no data to preserve.  Sysadmin does have data, and would also be by using the admin() API to reset sysadmin, along with data import to load back the data already present.  Art's utilities (myexport and myimport -e) should be great for that.

Seems to me like it should work, but, maybe I am missing something significant.

DG