404 Resource at '/content/informaticadita-com/en_us/data-integration/metadata-manager/10-5-5/_metadata-manager-administrator-guide_metadata-manager_10-5-5_ditamap/data_integration_resources/powercenter_resources/configuring_powercenter/increasing_the_ibm_db2_for_luw_database_heap_size/jcr:content/header/menupage.nocache.html/informaticadita-com/components/content/menu-hover' not found: No resource found

Resource at '/content/informaticadita-com/en_us/data-integration/metadata-manager/10-5-5/_metadata-manager-administrator-guide_metadata-manager_10-5-5_ditamap/data_integration_resources/powercenter_resources/configuring_powercenter/increasing_the_ibm_db2_for_luw_database_heap_size/jcr:content/header/menupage.nocache.html/informaticadita-com/components/content/menu-hover' not found: No resource found

Cannot serve request to /content/informaticadita-com/en_us/data-integration/metadata-manager/10-5-5/_metadata-manager-administrator-guide_metadata-manager_10-5-5_ditamap/data_integration_resources/powercenter_resources/configuring_powercenter/increasing_the_ibm_db2_for_luw_database_heap_size/_jcr_content/header/menupage.nocache.html/informaticadita-com/components/content/menu-hover on this server

Apache Sling
English
  •        
  • Metadata Manager
  • 10.5.5
  • Metadata Manager Administrator Guide
    • 404 Resource at '/content/informaticadita-com/en_us/data-integration/metadata-manager/10-5-5/_metadata-manager-administrator-guide_metadata-manager_10-5-5_ditamap/data_integration_resources/powercenter_resources/configuring_powercenter/increasing_the_ibm_db2_for_luw_database_heap_size/jcr:content/navigation-bar/breadcrumb/timestamp.nocache.html/informaticadita-com/components/content/timestamp' not found: No resource found

    Resource at '/content/informaticadita-com/en_us/data-integration/metadata-manager/10-5-5/_metadata-manager-administrator-guide_metadata-manager_10-5-5_ditamap/data_integration_resources/powercenter_resources/configuring_powercenter/increasing_the_ibm_db2_for_luw_database_heap_size/jcr:content/navigation-bar/breadcrumb/timestamp.nocache.html/informaticadita-com/components/content/timestamp' not found: No resource found

    Cannot serve request to /content/informaticadita-com/en_us/data-integration/metadata-manager/10-5-5/_metadata-manager-administrator-guide_metadata-manager_10-5-5_ditamap/data_integration_resources/powercenter_resources/configuring_powercenter/increasing_the_ibm_db2_for_luw_database_heap_size/_jcr_content/navigation-bar/breadcrumb/timestamp.nocache.html/informaticadita-com/components/content/timestamp on this server

    Apache Sling
  • Metadata Manager 10.5.5
  • All Products

Table of Contents

Search

  1. Preface
  2. Using Metadata Manager
  3. Configuring Metadata Manager
  4. Application Resources
  5. Business Glossary Resources
  6. Business Intelligence Resources
  7. Custom Resources
  8. Data Integration Resources
  9. Data Modeling Resources
  10. Database Management Resources
  11. Universal Resources
  12. Managing Resources
  13. Loading and Monitoring Resources
  14. Managing Permissions
  15. Resource Migration
  16. Repository Migration
  17. Appendix A: Metadata Manager Login
  18. Appendix B: Metadata Manager Properties Files
  19. Appendix C: Resource Configuration Files
  20. Appendix D: Glossary

Metadata Manager Administrator Guide

Metadata Manager Administrator Guide

Back Next

Increasing the IBM DB2 for LUW Database Heap Size

Increasing the IBM DB2 for LUW Database Heap Size

To increase the IBM DB2 for LUW database heap size, complete the following steps:
  1. Log out of Metadata Manager.
  2. Stop the DB2 database server.
  3. From a DB2 command prompt, connect to the DB2 database.
  4. To determine the current value of the Application Heap Size configuration parameter (APP_CTL_HEAP_SZ), run the following command: 
    db2 get db dfg for <database_name> | find "APP_CTL_HEAP_SZ"
  5. To increase the size of APP_CTL_HEAP_SZ to 16384 or higher, run the following command: 
    db2 update db cfg for <database_name> using APP_CTL_HEAP_SZ <higher_value>
  6. Restart the DB2 database server.
0 COMMENTS
We’d like to hear from you!