Skip to Main Content
IBM Data Platform Ideas Portal for Customers


This portal is to open public enhancement requests against products and services offered by the IBM Data Platform organization. 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

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea


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.

IBM Employees should enter Ideas at https://ideas.ibm.com



Status Under review
Workspace Db2
Components Db2 on-premise
Created by Guest
Created on Jun 15, 2026

Simplify DB2REMOTE log archive path name

When configuring LOGARCHMETH1|2 for a DB2REMOTE Db2 always appends two forward slashes "//" to end of the path even though specifying the slashes isn't required. This makes it more difficult to automate Db2 configuration because while it's possible to not specify the slashes they are appended and must be checked for.

db2 update db cfg for <sample> using logarchmeth1 DB2REMOTE://log-alias/log-container
or
db2 update db cfg for <sample> using logarchmeth1 DB2REMOTE://log-alias/log-container/

Both will result in:

DB2REMOTE://log-alias/log-container//

This is confusing. Ending forward slashes should not need to be defined (following general UNIX path philosophy and also S3 and blob storage conventions).

If Db2 needs them internally, it should add them as required.

This was identified as part of a case and IBM support suggested to open this idea.

Needed By Quarter
  • Admin
    Michael Roecken
    Jun 15, 2026

    Hi, thanks for the suggestion. The name used for DB2REMOTE paths is universal across all Db2 commands, such as, but not limited to backup, restore, log archive/retrieve, load, external tables.

    In regards to LOGARCHMETH1|2, the following is documented at https://www.ibm.com/docs/en/db2/12.1.x?topic=parameters-logarchmeth1-primary-log-archive-method :

    DB2REMOTE

    Specifies that remote storage, such as IBM Cloud Object Storage or Amazon Simple Storage Service (S3), is used to archive the log files. You must follow this value with a colon (:) and specify a remote storage location by using a storage access alias. The syntax for specifying a remote storage location is DB2REMOTE://<alias>/<container>/<object>. This format is supported exclusively for AWS S3 integrations.

    This also includes Azure.

    The format for DB2REMOTE identifiers is documented here: https://www.ibm.com/docs/en/db2/12.1.x?topic=storage-db2remote-identifiers

    Both examples are valid ways to specify a remote path:

    db2 update db cfg for <sample> using logarchmeth1 DB2REMOTE://log-alias/log-container
    db2 update db cfg for <sample> using logarchmeth1 DB2REMOTE://log-alias/log-container/

    The output you see: DB2REMOTE://log-alias/log-container//, follows the documented format: DB2REMOTE://<alias>/<container>/<object>, where:

    alias = log-alias
    container = log-container
    object = / (root)

    This matches our local disk semantics if using / as the archive path ==> db2 update db cfg for mr using logarchmeth1 disk:/ gives DISK:/

    The team will review further and respond back. Thanks.