Table of Contents

Search

  1. Preface
  2. Starting Data Archive
  3. System Configuration
  4. Database Users and Privileges
  5. Source Connections
  6. Target Connections
  7. Archive Store Configuration
  8. Datatype Mapping
  9. Database Optimization
  10. SAP Application Retirement
  11. z/OS Source Data Retirement
  12. Seamless Data Access
  13. Data Discovery Portal
  14. Security
  15. SSL Communication with Data Vault
  16. LDAP User Authentication
  17. Auditing
  18. Running Jobs from External Applications
  19. Salesforce Archiving Administrator Tasks
  20. Upgrading Oracle History Data
  21. Upgrading PeopleSoft History Data
  22. Data Archive Maintenance
  23. Appendix A: Datetime and Numeric Formatting
  24. Appendix B: Data Archive Connectivity

Administrator Guide

Administrator Guide

Changing Database User Passwords

Changing Database User Passwords

Configure the ILM repository connection details and the database user details in a properties file. The script uses the properties file to connect to the ILM repository and to validate the database user login name and password. If the database user login details are valid, the script updates the ILM repository with the new password.
The ILM application server does not need to be running when you run the script.
If a Data Vault user password expires, you can update the ILM repository with a new password only if folders have been created in Data Vault with the Create Archive Folder job.
  1. Navigate to the following directory:
    <ILM installation directory>/optional
  2. Use the
    PasswordChangesSampleProperty
    file to create a property file.
  3. Add the required properties to the property file.
  4. Save and close the property file.
  5. From the same directory, run one of the following files:
    • PasswordChangeEnv.bat
      for Windows.
    • PasswordChangeEnv.sh
      for Linux and UNIX.
  6. Enter the location of the property file that you created.
    The script executes and creates the
    PasswordChangeLog
    log file in the same directory.
  7. View the log file to show the script outcome.

0 COMMENTS

We’d like to hear from you!