IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Add a new idea Subscribe
Status Future consideration
Workspace Storage Protect Family
Categories Product functionality
Created by Guest
Created on Dec 6, 2019

RELATED IDEAS

Need larger DB2 active log file size

While working on HADR, a DB2 specialist noted that DB2 under SP was archiving the active log at a higher than normal rate and recommended increasing the current DB2 LOGFILSIZ to make it ten (10) times larger. However, the customer was unable to make that change because SP will override the setting. We would like SP to increase that LOGFILSIZ setting or allow us to set it. While discussing this with development, they stated "For LOGBUFSZ we have a server option, but it is currently limited to 131070 (which was the MAX value for DB2 9.5 or 9.7) . Since this variable is also checked every time the TSM server starts, any attempts to change it will be lost when you next start the server. We would need a code change to bump up the limit, which is easy enough to do, but won't help this customer now"

Idea priority High
  • Guest
    Reply
    |     Jan 15, 2020

    This request may not be delivered within the release currently under development, but the theme is aligned with the current multi-year strategy. IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting. IBM will update this request in the future.

  • Guest
    Reply
    |     Dec 8, 2019

    I'm not with TSM DEV, but you can increase LOGFILSIZE 4x by increasing your ACTIVELOGSIZE to the maximum supported size. Most people find that if theyr active logs turn over quickly, they also need a larger active log.

    You may also want to consider whether your log shipping network is fast enough, or whether your server load is high enough to warrant a larger system. DB2 log manager will always archive a log once it is full or closed. Typically, having a huge archive log and a tiny active log is not the best option.

    To get a change like this, you would probably need to justify better than simply log change is rolling over faster than you'd like. There would need to be a negative impact that affects enough customers to really justify the risk and effort for the change.

    I can see a couple of ways they might enable this. One would be increasing the limit on ACTIVELOGSIZE, which would be fairly simple, but can affect the time required for crash recovery. The other would be adding logic around LOGPRIMARY to have a divisor added to the target, but then check for minimum useful number of logs, and maximum supported LOGFILSIZ. This all might tie into server sizing, performance, etc. It would increase risk, and with 7 votes, might be tough to get on the board.

    As to LOGBUFSZ, that looks variable already, and has no real impact to log archiving, but could affect performance. It looks like this is already set to a percentage of the DBHEAP, which is already scaled based on system memory available.

    See this for details on how TSM expands LOGFILSIZ:
    https://www.ibm.com/support/pages/value-activelogsize-server-option-affects-settings-logfilsiz-logprimary-and-numlogspan-database-parameters

    Supporting docs for the TSM document:
    https://www.ibm.com/support/knowledgecenter/SSEQVQ_8.1.8/srv.reference/r_opt_server_activelogsize.html
    https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.5.0/com.ibm.db2.luw.admin.config.doc/doc/r0000240.html
    https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.5.0/com.ibm.db2.luw.admin.config.doc/doc/r0006019.html

    See this for info on the DB2 parameters LOGFILSIZ and LOGBUFSZ:
    https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.5.0/com.ibm.db2.luw.admin.config.doc/doc/r0000243.html
    https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.5.0/com.ibm.db2.luw.admin.config.doc/doc/r0000239.html

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.