Global Data Management Forum

Data Management Global

A hub for collaboration, learning, networking, and cultural exchange, and contributing to positive global engagement

 View Only

  • 1.  [400, Bad Request]

    Posted 03/10/25 09:31 AM

    Hi guys,

    I keep getting the below error message every time I try to create Db2 database instance. 

    Please contact the Service Provider for this error. [400, Bad Request] We were unable to complete your request: version: please add 'version' parameter (only 11 supported). Try again with valid values or contact support if the issue persists.

    Transaction ID: 626c-c378a3a3dbcf4179

    How do I resolve this?



    ------------------------------
    Silas Nwokocha
    ------------------------------


  • 2.  RE: [400, Bad Request]

    Posted 03/11/25 10:29 PM
    Hi Silas,
    1. Where are you trying to create the database ? Is it a procured database from hyperscaler such as Azure, AWS or a standalone database?
    2. Sometimes, the error is misleading. Do you have SYSADM or SYSCTRL privilege ?
    3. What is the command you are running?

    Thanks,
    Kushal
    'The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com'

    Internal - General Use






  • 3.  RE: [400, Bad Request]

    Posted 03/12/25 09:24 AM

    Hi Silas Nwokocha,

    It looks like the error is due to a missing or incorrect version parameter when creating the Db2 database instance. Db2 only supports version 11, so you need to explicitly specify it in your request.


    Steps to Resolve:


    Check Your Request Parameters – Ensure that the version parameter is included and set to 11.
    Modify Your API Call or Configuration 

    Verify with Your Service Provider – If you're using a managed service, check their documentation for the correct way to specify the version.
    Try a Different Interface – If using a web UI, try creating the instance via the CLI or API instead.

    Contact Support – If the issue persists, reach out to your service provider with the Transaction ID for further assistance.

    https://platform3solutions.com/



    ------------------------------
    Aarthy Karuppaiah
    ------------------------------



Related Content