Summary:
If the IME database account is modified, such as by altering the password or login name of the database account, then IME will not be able to connect to the database until the IME configuration is modified.

Resolution:
Changing the password of the IME database account is quite easy, although it does require a stop/start of the IME application:

The steps below outline updating an Oracle connection for IME installed on Solaris, but the same steps are appropriate for IME installed on a Windows environment referencing Oracle (IME 5.0.5) or SQL Server (IME 5.5) - just update the registry key entries with the same values as below.

1) Stop IME

2) Change the password of the IME database account.
Your values for the account name and password will obviously be different, but the command for Oracle would be:
ALTER USER TUMBLEWEED IDENTIFIED BY my_new_password;

3) Edit the <IME_INSTALL>/config/server.ini (Solaris) or use regedit.exe and browse to HKEY_LOCAL_MACHINE\Software\Tumbleweed\Server (Windows)

In the configuration you see:

[Database]
"Account"=""
"Default Settings"=""
"Name"="IME1"
"Reset Account"="460b27c69255755a4005baf10c9c503b9999"
"Reset Default Settings"="ee4445af2900104a4005ec8decca0dc99997"

On Solaris, the "Name" is your Oracle SID. It may be blank if you have Oracle
installed on the same machine as IME.
For SQL Server on Windows the name entry would be more like:
"Name"="ime.example.com:IME1"
The "Reset Account" is the encrypted IME database user ID.
The "Reset Default Settings" is the encrypted IME database password.

Edit the server.ini so that you enter the user_ID in the "Account" setting, the new password in the "Default Settings", and then clear out the values in the "Reset Account" and the "Reset Default Settings" entries. The new entries should look something like:

[Database]
"Account"="tumbleweed"
"Default Settings"="my_new_password"
"Name"="IME1"
"Reset Account"=""
"Reset Default Settings"=""
"Vendor"="Oracle"

4) Start up IME.
Now if you look in the server.ini or registry, you will see that the settings have changed back to the original format. Now there are new encrypted strings in the "Reset Account" and the "Reset Default Settings" entries, and that now the "Account" and the "Default Settings" are cleared out.

Additional Info:
Reversing these value may cause any IME service to fail when started. On Windows, inserting clear text in the "Reset Account" and "Reset Default Settings" area will cause the IME Naming Service to fail on startup with the following error:

05/07/03 15:18:12 microsec: 419000, TID 932, DEBUG: PostaNamingService.exe, module=APPLICATION: AS015; in file: S:\Shared\Cpp\Crypto\Sources\opCrypto.cpp; at line: 1701

05/07/03 15:18:12 microsec: 450000, TID 932, DEBUG: PostaNamingService.exe, module=APPLICATION: Throwing exception opCryptoExceptionC(opCryptoI::ERROR_INIT, "Unable to init the decrypter object", "Core", __LINE__, __FILE__); in file: S:\Shared\Cpp\Crypto\Sources\opCrypto.cpp; at line: 1344

On Solaris, a similar error will appear when starting the IMEBooter process.

One of the first initialization steps for each IME process is reading the configuration. The IME Naming Service is the first process to start on Windows, the IMEBooter the first (IME) process to start on Solaris. On Solaris, omniNames does not require a service wrapper so runs simply as "omniNames".

Original Author:
Original Submitter: JCHOI
Keywords: Modify Database Login Password IME ID#29316