Syntax
ALTER CREDENTIALSTORE {
ADD USER userid |
REPLACE USER userid |
DELETE USER userid }
[PASSWORD password]
[ALIAS alias]
[DOMAIN domain]
ADD USER
userid
Adds the specified user and its alias to the credential store. If the ALIAS
option is not used, the alias defaults to the user name. A credential can only be entered once unless the ALIAS
option is used to specify a different alias for each one. Unless the PASSWORD
option is used, the command prompts for the password of the specified user. The user can be an actual user name or a SQL*Net connect string.
REPLACE USER
userid
Changes the password of the specified user. If the ALIAS
option is not used, the alias defaults to the user name. You cannot change the alias or domain of a user with this option, but you can use the ADD USER
option to add a new entry for the user under the desired ALIAS
or DOMAIN
. Unless the PASSWORD
option is used, the command prompts for the new password for the specified user.
DELETE USER
userid
Removes the credential for the specified user from the credential store. If the ALIAS
option is not used, the alias defaults to the user name.
PASSWORD
password
The user’s password. The password is echoed (not obfuscated) when this option is used. If this option is omitted, the command prompts for the password, which is obfuscated as it is typed (recommended as more secure).
ALTER CREDENTIALSTORE ADD USER scott
Password: ********
ALIAS
alias
Specifies an alias for the user name. Use this option if you do not want the user name to be in a parameter file or command. If ALIAS
is not used, the alias defaults to the USER
name, which then must be used in parameter files and commands where a login is required. You can create multiple entries for a user, each with a different alias, by using the ADD USER
option with ALIAS
.
DOMAIN
domain
Saves the credential user under the specified domain name. Enables the same alias to be used by multiple Oracle GoldenGate installations that use the same credential store. The default domain is Oracle GoldenGate
. For example, the administrators of system 1 might not want system 2 to have access to the same credentials that are used on system 1. Those credentials can be stored as ALIAS extract
, for example, under DOMAIN system1
, while a different set of credentials can be stored for ALIAS extract
under DOMAIN system2
. See ADD CREDENTIALSTORE for information about how to use a shared credential store.
Examples
Example 1
This example adds a user named scott
but omits the PASSWORD
specification, so the command prompts for Scott’s password.
ALTER CREDENTIALSTORE ADD USER scott
Password: ********
Example 2
This example adds the user scott
with his password tiger
and specifies an alias for scott
that is named scsm2
.
ALTER CREDENTIALSTORE ADD USER scott PASSWORD tiger ALIAS scsm2
Example 3
This example adds the user scott
under the domain of support
.
ALTER CREDENTIALSTORE ADD USER scott ALIAS scsm3 DOMAIN support
Password: ********
Example 4
This example issues two ALTER CREDENTIALSTORE
commands, each of which adds a scott
entry, but with a different alias.
ALTER CREDENTIALSTORE ADD USER scott ALIAS scsm2
Password: ********
ALTER CREDENTIALSTORE ADD USER scott ALIAS scsm3
Password: ********
Example 5
The following shows how the DELETE USER
option works with and without the ALIAS
option.
The following command deletes the user1
entry for which the ALIAS
is the same as the user name.
ALTER CREDENTIALSTORE DELETE USER user1
Alias: user1
Userid: user1
The following command deletes the entry for user user1
that is associated with the alias alias1
.
ALTER CREDENTIALSTORE DELETE USER user1 ALIAS alias1
Alias: alias1
Userid: user1
Example 6
This example uses a SQL*Net connect string as the user value. In this case, the PASSWORD
option is omitted. The person issuing the command will be prompted for the password, which is obfuscated.
ALTER CREDENTIALSTORE ADD USER oggext1@ora1 ALIAS ora1