Table of Contents

Search

  1. Preface
  2. Introduction
  3. Accessing Data Archive
  4. Working with Data Archive
  5. Scheduling Jobs
  6. Viewing the Dashboard
  7. Creating Data Archive Projects
  8. Salesforce Archiving
  9. SAP Application Retirement
  10. Creating Retirement Archive Projects
  11. Integrated Validation for Archive and Retirement Projects
  12. Retention Management
  13. External Attachments
  14. Data Archive Restore
  15. Data Discovery Portal
  16. Data Visualization
  17. Oracle E-Business Suite Retirement Reports
  18. JD Edwards Enterprise Retirement Reports
  19. Oracle PeopleSoft Applications Retirement Reports
  20. Smart Partitioning
  21. Smart Partitioning Data Classifications
  22. Smart Partitioning Segmentation Policies
  23. Smart Partitioning Access Policies
  24. Language Settings
  25. Appendix A: Data Vault Datatype Conversion
  26. Appendix B: Special Characters in Data Vault
  27. Appendix C: SAP Application Retirement Supported HR Clusters
  28. Appendix D: Glossary

Frequently Asked Questions

Frequently Asked Questions

The following list explains how to troubleshoot and resolve issues that might occur during the SAP application retirement process.
When I run the retirement job, the job immediately completes with an error.
The job log includes the following message:
java.lang.NoClassDefFoundError: com/sap/mw/jco/IMetaData
The error occurs because the
sapjaco.jar
file is missing in the ILM application server. Verify that the SAP Java Connector installation is correct.
Perform the following steps to verify the SAP Java Connector installation:
  1. From the command line, navigate to the following directory:
    <Data Archive installation>/webapp/WEB-INF/lib
  2. Enter the following command:
    java –jar sapjco.jar
    If the installation is correct, you see the path to the SAP Java Connector library file, such as
    C:\SAPJCO\sapjcorfc.dll
    .
    If the installation is not correct, you see a
    Library Not Found
    message in the path for to the SAP Java Connector library file.
If the installation is not correct, perform the following steps to resolve the error:
  1. Verify that you installed the SAP Java Connector.
  2. Copy the
    sapjaco.jar
    file from the root directory of the SAP Java Connector installation and paste to the following directory:
    <Data Archive installation>/webapp/WEB-INF/lib
  3. Restart the ILM application server.
When I run the retirement job, I receive an error that the maximum value was exceeded for no results from the SAP system.
For every package of rows that the job processes, the job waits for a response from the SAP system. The job uses the response time configured in the
conf.properties
file and the package size specified in the job parameters. If the SAP system does not respond within the configured maximum response time, the job fails.
The SAP system may not respond for one or more of the following reasons:
  • The maximum amount of SAP memory was exceeded. The SAP system terminated the process. The SAP system may run out of memory because the package size that is configured in the job is too high.
  • The SAP system takes a long time to read the data from the database because of the configured package size.
  • The network latency is high.
To resolve the error, in the SAP system, use transaction
SM50
to verify if the process is still running. If the process is still running, then restart the job in Data Archive.
If the process is not running, perform one or more of the following tasks:
  • Use SAP transactions
    SM37
    ,
    ST22
    , and
    SM21
    to analyze the logs.
  • Decrease the package size in the job parameters.
  • Increase the
    informia.MaxNoResultsIteration
    parameter in the
    conf.properties
    file.
The job log indicates that the Data Vault Loader received an exception due to an early end of buffer and the load was aborted.
The error may occur because the SAP application is hosted on Windows.
Perform the following steps to resolve the error:
  1. Configure the
    informia.isSAPOnWindows
    property to
    Y
    in the
    conf.properties
    file.
  2. Reboot the ILM application server.
  3. Create a new retirement project.

0 COMMENTS

We’d like to hear from you!