Description:
Mangled passwords for the username that the EMS server uses to access a database are still unsupported for the Schema export utility (tibemsd_util.jar).



Symptoms:
Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (10). Last acquisition attempt exception: java.sql.SQLException: ORA-28000: the account is locked
Cause:

1). Run "tibemsadmin -mangle "database_password" " to mangle the database password for the username that the EMS server uses to access the database.

2). dbstore_driver_password is in mangled form in stores.conf .

3). Start the Export Schema Utility.

java -jar /opt/tibco/ems/8.0/bin/tibemsd_util.jar -tibemsdconf /opt/tibco/ems/8.0/samples/config/tibemsd.conf -createall -export

This operation will fail with an error depending upon the database used because the mangled passwords are still unsupported for the Schema export utility (tibemsd_util.jar). You will see an error like the following in case of an Oracle database is used. 

Acquisition Attempt Failed!!! Clearing pending acquires. While trying to acquire a needed new resource, we failed to succeed more than the maximum number of allowed acquisition attempts (10). Last acquisition attempt exception: java.sql.SQLException: ORA-28000: the account is locked.

The following enhancement request gas been logged: EMS-5407

"The ability for tibemsd_util.jar (the tool used for creating database schemas/tables) to work with mangle password/usernames provided in the stores.conf."

A database mangled password is recognized by EMS so the EMS server will run but tibemsd_util.jar will have problems exporting the mangled passwords.

Does the Schema export utility (tibemsd_util.jar) support mangled passwords?