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. Seamless Access Setup for Oracle R12 in Data Archive
  21. Using the Data Vault Service JDBC Driver to Connect to the Data Vault
  22. Using Multiple Engines in an ILM Environment
  23. Using PowerExchange ODBC Connections in a Data Archive Retirement Project
  24. Discovering Foreign Key Relationships in Enterprise Data Manager

Data Archive How-To Guide

Data Archive How-To Guide

Example: AMQUERY GL Administrator Responsibility

Example: AMQUERY GL Administrator Responsibility

  1. Set all agent related profiles, such as Application Framework Agent, to point to the archive node https://r12dev-amquery.informatica.com:443.
  2. Configure the DBC file on the archive nodes (located in $INST_TOP/appl/fnd/12.0.0/secure).
    Change the following profile options:
    FNDNAM=AMQUERY FND_JDBC_USABLE_CHECK=true FND_JDBC_PLSQL_RESET=true FND_JDBC_CONTEXT_CHECK=true
  3. Create the new concurrent manager for Java concurrent requests on the seamless node:
    • Create a new concurrent manager on the forms Define Concurrent Managers from the System Administrator responsibility ( set the same setup as the Standard Concurrent manager).
    • Click the Specialization Rules button and include the concurrent programs you want to run on this concurrent manager.
    • Query the Standard concurrent manager on the forms Define Concurrent Managers from the System Administrator responsibility.
    • Click the Specialization Rules button and exclude the concurrent programs you included in the previous step for the new concurrent managers.
    • Bounce the concurrent managers.
  4. AMQUERY & COMBINED password should be same as APPS schema password.
    For example:
    FNDCPASS apps/<apps pwd> 0 Y system/manager ORACLE AMQUERY <APPS PWD> FNDCPASS apps/<apps pwd> 0 Y system/manager ORACLE COMBINED <APPS PWD>