Table of Contents

Search

  1. Preface
  2. Backing Up and Restoring the Data Vault
  3. Configuring Centera as a Remote Data Vault Store
  4. Configuring Data Archive for a Legacy Source Using Legacy Adapters
  5. Data Archive Seamless Access for PeopleSoft
  6. Data Archive Transaction Restore API
  7. Dropping and Truncating Partitions in Data Archive
  8. High Availability Configuration for the Data Archive and File Archive Service Versions 6.1 to 6.3
  9. 0955-High Availability Configuration for the Data Vault Version 6.4 and Later
  10. How to Create Business Rules to Archive and Purge Transactional Data
  11. How to Uninstall Data Archive 5.1
  12. How to Uninstall Data Archive 5.3
  13. How to Use Scripts to Change Database User Passwords in the ILM Repository
  14. IBM DB2 Database Connectivity and Setup for Data Archive
  15. Installing Data Visualization
  16. Integrating Third-Party Schedulers in ILM Engine
  17. Parallel Processing in Data Archive
  18. Seamless Access Configuration for Siebel Applications
  19. Seamless Access Setup for Oracle E-Business Suite
  20. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  21. Using Multiple Engines in an ILM Environment
  22. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  23. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To 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.
Note that the ILM application server does not need to be running when you run the script.
  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!