Renaming Dbspaces

You can use the onspaces utility to rename a dbspace if you are user informix or have DBA privileges and the database server is in quiescent mode (and not any other mode).

To rename a dbspace use the following onspaces utility command:

onspaces -ren old_dbspace_name-n new_dbspace_name

You can rename standard dbspaces and all other spaces, including blobspaces, smart blobspaces, temporary spaces, and external spaces. However, you cannot rename any critical dbspace, such as a root dbspace or a dbspace that contains physical logs.

You can rename a dbspace and an sbspace:

• When Enterprise Replication is enabled
• On a High-Availability Data Replication (HDR) primary database server

You cannot rename a dbspace and an sbspace on an HDR secondary database server or when the HDR secondary database server is part of the Enterprise Replication configuration

The rename dbspace operation only changes the dbspace name; it does not reorganize data.

The rename dbspace command updates the dbspace name in all places where that name is stored. This includes reserved pages on disk, system catalogs, the ONCONFIG configuration file, and in-memory data structures.

Additional Actions You might Need to Take After Renaming a Dbspace

If you rename a dbspace, you must rewrite and recompile any stored procedure code that references the old dbspace name. For example, if you have a stored procedures that contains the ALTER FRAGMENT keywords and a reference to the dbspace name, you must rewrite and recompile that stored procedure.

If you rename dbspaces that are specified in the DATASKIP configuration parameter, you must manually update the DATASKIP configuration parameter after renaming the dbspace.