Setting variables at the instance level in a partitioned database environment

In a partitioned database environment, the way that you set registry variables in the instance-level profile registry depends on your operating system.

About this task

On Linux® and UNIX operating systems, the instance-level profile registry is stored in a text file in the sqllib directory. Because the sqllib directory is on a file system that is shared by all physical database partitions, you can set a registry variable from any database partition.

On Windows operating systems, the Db2® database manager stores the instance-level profile registry in the Windows registry. As a result, data is not shared across physical database partitions. To set a variable for all database partitions, you must use the rah command to ensure that the command that you use to set the variable is run on all computers. If you set a registry variable from a database partition and do not use the rah command, the variable is set only for that database partition in the current instance.

You can also use the DB2REMOTEPREG registry variable to configure a computer that is not the instance owner to use the values of registry variables on the instance-owning computer.


To set a registry variable for all database partitions of the current instance:

Issue the command for your operating system from any database partition.
  • On Linux and UNIX operating systems, issue the following command:
    db2set registry_variable_name=new_value
  • On Windows operating systems, issue the following command:
    rah db2set registry_variable_name=new_value