Changing owner of objects in a database

I would like to know if there is another way of changing the ownership of all objects (tables, indexes, constraints, etc) from one specific user to another, besides using dbexport-changing sql-dbimport. We want to avoid export and import of the database to do this quickly. Would an update of system catalog tables update sysmaster internally and make them in sync? We are running IDS 7.30.FC7. Thanks, Shehla

im pretty sure nobody would suggest you muck with the system catalog for any reason whatsoever. i think you can rename tables and specify ownership. "Arshad, Shehla" wrote: > I would like to know if there is another way of changing the ownership of > all objects (tables, indexes, constraints, etc) from one specific user to > another, besides using dbexport-changing sql-dbimport. We want to avoid > export and import of the database to do this quickly. > > Would an update of system catalog tables update sysmaster internally and > make them in sync? > > We are running IDS 7.30.FC7. > > Thanks, > > Shehla

"Arshad, Shehla" wrote: > I would like to know if there is another way of changing the ownership of > all objects (tables, indexes, constraints, etc) from one specific user to > another, besides using dbexport-changing sql-dbimport. We want to avoid > export and import of the database to do this quickly. > > Would an update of system catalog tables update sysmaster internally and > make them in sync? > > We are running IDS 7.30.FC7. Do not do it! The system catalog is COMPLETELY independent of the disk structures that are mirrored in the SMI tables. Changing the OWNER column in systables will just S^%@W thinks up. There are very few columns in the catalog tables that you can safely muck with. Owner is not one. Art S. Kagel