10.2.1 Explanation of the specification format and options
- Organization of this subsection
(1) Specification format
adbclientdefmang -u authorization-identifier
[-p password]
{--update |[-i output-target-authorization-identifier]}
(2) Explanation of options
- ● -u authorization-identifier
-
~<character string>((1 to 100 bytes))
Specifies the authorization identifier of the HADB user who executes the adbclientdefmang command. To execute the adbclientdefmang command, the user must have the following two privileges:
-
DBA privilege
-
CONNECT privilege
For this option, specify an authorization identifier in the range from 1 to 100 bytes. Note that the byte count (1 to 100 bytes) does not include the double quotation marks used to enclose the authorization identifier.
- Important
-
If the character string used as the authorization identifier includes any lowercase letter or a backslash (\), make sure that you check the rules for specifying authorization identifiers. For the rules for specifying authorization identifiers, see 1.4.2 Rules for specifying authorization identifiers and passwords.
-
- ● -p password
-
~<character string>((1 to 255 bytes))
Specifies the password for the authorization identifier that was specified in the -u option.
- Important
-
If the password includes a character that has a special meaning in the OS or shell, such as a double quotation mark (") or vertical bar (|), make sure that you check the rules for specifying passwords. For the rules for specifying passwords, see 1.4.2 Rules for specifying authorization identifiers and passwords.
If the adbclientdefmang command is executed with this option omitted, a message prompting the user to enter a password is displayed. In an environment in which a password cannot be entered from the standard input, such as when the command is executed in the background, make sure that you do not omit this option.
- ● --update
-
Specify this when you want to change the way the function for centrally managing client definitions is applied, while the HADB server is running.
When you execute the adbclientdefmang command with the --update option specified, the content of the client definition file used by the function for centrally managing client definitions is applied to each HADB client according to the content of the client management definition file ($ADBDIR/conf/adbclientdefmang.def).
However, if the adbclientdefmang command is executed with the --update option specified in the following situations, the function for centrally managing client definitions is disabled:
-
The client management definition file does not exist.
-
The client management definition file is empty.
-
The content of the client management definition file consists entirely of comments.
-
- ● -i output-target-authorization-identifier
-
~<character string>((1 to 100 bytes))
Specify this when you want to check the name of the client definition file used by the function for centrally managing client definitions applied to the authorization identifier of a specific HADB client.
When you execute the adbclientdefmang command with the -i option specified, the authorization identifier of the HADB client specified in the -i option, and the name of the client definition file used by the function for centrally managing client definitions applied to that authorization identifier are displayed.
In this option, specify an authorization identifier for the output target in the range from 1 to 100 bytes. Note that the byte count (1 to 100 bytes) does not include the double quotation marks used to enclose the authorization identifier of the output target.
Specifying a character string that violates the rules for specifying authorization identifiers results in an error.
- Important
-
If the character string used as the authorization identifier includes any lowercase letter or a backslash (\), make sure that you check the rules for specifying authorization identifiers. For the rules for specifying authorization identifiers, see 1.4.2 Rules for specifying authorization identifiers and passwords.
The following is an example of displaying the name of the client definition file used by the function for centrally managing client definitions applied to the HADB client authorization identifier ADBUSER02:
Example execution (when the -i option is specified)
adbclientdefmang -u ADBUSER01 -p '#HelloHADB_01' -i ADBUSER02
Output example
authorization-identifier client-definition-file ADBUSER02 client01.def
Note that if you omit the -i option, the authorization identifiers of HADB clients to be centrally managed, and the list of names of client definition files used by the function for centrally managing client definitions are output.
Example execution (when the -i option is omitted)
adbclientdefmang -u ADBUSER01 -p '#HelloHADB_01'
Output example
authorization-identifier client-definition-file ADBUSER01 client01.def ADBUSER02 client01.def ADBUSER03 client02.def