Resets the parameters in the database manager configuration file that are relevant to the DB2 Administration Server to the system defaults. The values are reset by node type, which is always a server with remote clients. The DB2 Administration Server is a special DB2 instance that enables remote administration of DB2 servers. The following database manager configuration parameters are reset:
| Note: | It is not recommended that the SVCENAME parameter, set by the installation program, be modified by the user. The administration server service name is set to use the DB2 registered TCP/IP port (523). |
For more information about these parameters, see GET DATABASE MANAGER CONFIGURATION.
Scope
This command resets the database manager configuration file, $HOME/sqllib/db2systm. It affects all nodes that are listed in the $HOME/sqllib/db2nodes.cfg file.
Authorization
sysadm
Required Connection
None or instance. An instance attachment is not required to perform local DBM configuration operations, but is required to perform remote DBM configuration operations. To reset the database manager configuration for a remote instance, it is necessary to first attach to that instance.
Command Syntax
>>-RESET ADMIN----+-CONFIGURATION-+----------------------------><
+-CONFIG--------+
'-CFG-----------'
Command Parameters
None
Usage Notes
To view or print a list of the admin configuration parameters, use GET ADMIN CONFIGURATION.
To change the value of an admin parameter, use UPDATE ADMIN CONFIGURATION.
For more information about these parameters, see the Administration Guide.
Changes to the database manager configuration file become effective only after they are loaded into memory. This occurs during execution of db2start.
If an error occurs, the database manager configuration file does not change.
The database manager configuration file cannot be reset if the checksum is invalid. This may occur if the database manager configuration file is changed without using the appropriate command. If this happens, the database manager must be installed again to reset the database manager configuration file.
See Also