Db2 On Premise and Cloud

Expand all | Collapse all

Need Help Setting up the Db2 Developer-C Edition

  • 1.  Need Help Setting up the Db2 Developer-C Edition

    Posted Mon June 03, 2019 08:59 AM
    I'm trying to set up the Db2 Developer-C Edition and I'm stuck at the "Setting up and running containers" part. It jumps from pulling the image to setting up a container with no real instruction between that. I'd like to be told explicitly how I need to write and run this .env_list and what all I need to customize myself.




    Db2 Developer-C Edition | Sat Jun 01 2019

    Summary

    Install and run Db2 Developer-C Edition v11.1.4.4 using Docker and containers running CentOS. The image tag is now 11.1.4.4.

    Highlights

    • Latest: Db2 v11.1 Mod Pack 4 Fix Pack 4
    • Db2 HADR Support
    • Multi-platform support- x86_64, ppc64le, s390x

    Table of Contents

    Prerequisites

    • Docker engine
    • Directory/filesystem for persistent storage (

    Getting Db2 Developer-C image

    1. Login into repository:

      docker login User: <docker> Password: <docker>
    2. Pull the db2server image:
      For 11.1.4.4, we support 3 different architectures. Their respective docker pull commands are:
      docker pull store/ibmcorp/db2_developer_c:11.1.4.4-x86_64
      docker pull store/ibmcorp/db2_developer_c:11.1.4.4-ppc64le
      docker pull store/ibmcorp/db2_developer_c:11.1.4.4-s390x

      • Previous version tags: 11.1.3.3b, 11.1.3.3a, 11.1.3.3x, 11.1.3.3 and 11.1.2.2b

    Setting up and running containers

    1. Below is an example configuration. Save it to an .env_list and edit it if you wish.

      LICENSE=accept
      DB2INSTANCE=db2inst1
      DB2INST1_PASSWORD=password
      DBNAME=testdb
      BLU=false
      ENABLE_ORACLE_COMPATIBILITY=false
      UPDATEAVAIL=NO
      TO_CREATE_SAMPLEDB=false
      REPODB=false
      IS_OSXFS=false
      PERSISTENT_HOME=true
      HADR_ENABLED=false
      ETCD_ENDPOINT=
      ETCD_USERNAME=
      ETCD_PASSWORD=

      • LICENSE is to agree to the terms and conditions of the Db2 software contained in this image
      • DB2INSTANCE is to specify the Db2 Instance name
      • DB2INST1_PASSWORD is to specify the respective Db2 Instance Password
      • DBNAME creates an initial database with the name provided or leave empty if no database is needed
      • BLU can be set to true to enable BLU Acceleration for instance
      • ENABLE_ORACLE_COMPATIBILITY can be set to true to enable Oracle Compatibility on the instance
      • UPDATEAVAIL can be set to yes if there is an existing instance and running a new container with a higher Db2 level. Will be deprecated on next release
      • TO_CREATE_SAMPLEDB can be set to true to create a sample (pre-populated) database
      • REPODB can be set to true to create a Data Server Manager repository database
      • set IS_OSXFS=true if you are running on macOS
      • PERSISTENT_HOME is true by default, only specify to false if you are running Docker for Windows
      • HADR_ENABLED if set to true, Db2 HADR will be configured. The following three env variables depend on HADR_ENABLED to be true
      • ETCD_ENDPOINT is for specifying your own provided ETCD key-value store. Enter your endpoints with a comma as the delimiter and without a space. This env variable is needed if HADR_ENABLED is set to true
      • ETCD_USERNAME specify the username credential for ETCD. If empty, it will use your Db2 instance
      • ETCD_PASSWORD specify the password credential for ETCD. If empty, it will use your Db2 instance password
    2. docker run -h db2server_

      --name db2server --restart=always \ --detach \ --privileged=true \ -p 50000:50000 -p 55000:55000 \ --env-file .env_list \ -v <db dir>:/database \ <image name>
      • where <db dir> is an existing local directory and .env_list is a collection of environment variables.
    3. After the docker run command is executed, a duration will be required until completion. User may run docker logs -f <your_container_name> to tail the docker entry point script. To confirm Db2 container is ready, in the logs we will see the message Setup has completed.

    4. Log on to the container:

      docker exec -ti db2server_<your_container_name> bash -c "su - ${DB2INSTANCE}"
      • where ${DB2INSTANCE} is the name of the instance user used during docker run.

    Running Db2 HADR

    Requirements:

    • Two Db2 Developer-C Edition containers running preferably on different servers. One will automatically configured to be the primary, and the other will be the standby. The takeovers will happen accordingly.
    • An additional shared volume mount -v
    • Include --ipc=host in the docker run command and of course the HADR environment variables mentioned above.
    • Most importantly: You must have your own ETCD distributed key-value store which will be the two Db2 containers source of truth in the event one container goes down. Our governor that resides in both Db2 Docker containers must be able to communicate with the ETCD endpoints provided.

    An example docker run command to include HADR:
    docker run --name db2server --restart=always --privileged --ipc=host -p 50000 -p 55000 --env-file .env_list -v /home/db2server_fs/database:/database -v /home/db2server_fs/shared:/hadr -e HADR_ENABLED=true --net=host store/ibmcorp/db2_developer_c:11.1.4.4-x86_64

    In the event we lose one of the containers, the user must manually start back up the container so the two Db2 containers can HADR connect once again.

    For more information refer to https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.admin.ha.doc/doc/c0011267.html

    Build Your Own

    You can use the Developer-C docker container as a base to build your own custom container. Customizations may include additional setup scripts to execute after Db2 setup has completed, different license activation keys, additional OS packages installed, etc.

    To build your own, create a new Dockerfile and specify the desired Db2 Developer-C base in the FROM line in the Dockerfile. The following example builds a simple container with Db2 Developer-C as a base and copy a custom script into the /var/custom directory. Any script copied into the /var/custom will be automatically executed after main Db2 setup has completed.

    FROM store/ibmcorp/db2_developer_c:11.1.4.4-x86_64 RUN mkdir /var/custom COPY createschema.sh /var/custom RUN chmod a+x /var/custom/createschema.sh

    Change Db2 License Key

    The Db2 Developer-C docker container is licensed with the Db2 Developer-C license, which has limitations on CPU, memory, and database size (4 cores, 16 GB of memory, and 100GB of storage; see https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.licensing.doc/doc/c0058536.html for details).

    You can change the license for the docker container by executing these commands:

    docker cp <new> db2server_<your_container_name>:/database/config

    , where

    docker exec -ti db2server_<your_container_name> bash -c "/opt/ibm/db2/V11.1/adm/db2licm -r db2dec && /opt/ibm/db2/V11.1/adm/db2licm -a /database/config/<new>"

    , where



    ------------------------------
    Rachel Miles
    ------------------------------


  • 2.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Mon June 03, 2019 02:09 PM
    Edited by Rachel Miles Mon June 03, 2019 02:34 PM
    I figured out that an .env_list is a hidden file that you need to write in UNIX.

    I did this:
    cat >.env_list​


    And then typed in what was specified in step one of "Setting up and running containers." 

    This is what I uploaded after I did that:

    LICENSE=accept
    DB2INSTANCE=db2inst1
    DB2INST1_PASSWORD=password
    DBNAME=testdb
    BLU=false
    ENABLE_ORACLE_COMPATIBILITY=false
    UPDATEAVAIL=NO
    TO_CREATE_SAMPLEDB=false
    REPODB=false
    IS_OSXFS=false
    PERSISTENT_HOME=true
    HADR_ENABLED=false
    ETCD_ENDPOINT=
    ETCD_USERNAME=
    ETCD_PASSWORD=


    ------------------------------
    Rachel Miles
    ------------------------------



  • 3.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Mon June 03, 2019 02:34 PM
    I learned from @MKrafick at IDUG some additional terminal commands:

    docker image list
    Which I used to see if I'd even installed Db2 correctly

    docker ps -a
    Which you can use to look at containers and see if you set up a container. Which apparently I did do.

    Now I'm stuck on the next few steps.

    I ran docker logs -f <your_container_name>as docker logs -f db2server but did not get the "Setup has completed" response as the instructions said I would get.

    Then I ran docker exec -ti db2server_<your_container_name> bash -c "su - ${DB2INSTANCE}"as  docker exec -ti db2server bash -c "su - ${DB2INSTANCE}"and got the message "Container dfb44615577361f37d860516e6d866977e24d2c7af1fa305bb92c94350bf1048 is not running"

    I also ran the command docker exec -ti dfb446155773 bash -c "su - ${DB2INSTANCE}" and got the same message.

    I also tried docker exec -ti db2server_db2server bash -c "su - ${DB2INSTANCE}" and docker exec -ti db2server_dfb446155773 bash -c "su - ${DB2INSTANCE}" which is really what the instructions made me think I should do.


    HALP!

    ------------------------------
    Rachel Miles
    ------------------------------



  • 4.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Tue June 04, 2019 09:47 AM
    Hi Rachel,

    your container with Db2 is not running.

    As you can see in the Output form "docker ps -a" the Container has the status "Created" but not running.

    The only Container running on your System is the Orechstartor container with status "Up 7 seconds".

    With "docker exec -it" you get the console of a running container.

    Did you execute the "docker run....." command ? What was the output ?

    Greets
    ferdinand

    ------------------------------
    Ferdinand Prahst
    ------------------------------



  • 5.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Tue June 04, 2019 09:47 AM
    ​Hi Rachel,

    your Db2 Container is noct running. Therefore you cannot open a bash with "docker exec -ti".

    What was the Output from  "docker run" command ?

    It seems that you create a Container but did not run it.

    Regards

    Ferdinand

    ------------------------------
    Ferdinand Prahst
    ------------------------------



  • 6.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Tue June 04, 2019 09:47 AM
    Rachel - I think you are really, really close.

    Notice that you defined what the instance name is in the .env_list file - (DB2INSTANCE=db2inst1). So when you issue the run command and the image is spun up into a container, it says "I should create an instance named 'db2inst1' upon creation".

    Therefore, when you are executing docker commands from the command line (like your exec) you want to swap out "${DB2INSTANCE}" for "db2inst1".

    For example:
    docker exec -ti db2server_dfb446155773 bash -c "su - ${DB2INSTANCE}"

    Should be:
    docker exec -ti db2server_dfb446155773 bash -c "su - db2inst1"

    Does that help?

    P.S.
    Check your PM's on Twitter.


    ------------------------------
    Michael Krafick
    IBM Champion for Analytics
    Twitter: @mkrafick
    ------------------------------



  • 7.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Tue June 04, 2019 09:49 AM
    I think you are very, very close.

    You defined what the db2 instance name was in the .env_list file (DB2INSTANCE=db2inst1). So when you issue your RUN command to spin up a virtual container from an image, docker says "let me create a db2inst1 instance".

    Because you may be in a half state, you may want to try this to get a clean container state ..

    docker stop dfb44615573
    docker rm dfb44615573

    Then create a new container from you image lie you did before
    docker run --name db2server --restart=always --privileged --ipc=host -p 50000 -p 55000 --env-file .env_list -v /home/db2server_fs/database:/database -v /home/db2server_fs/shared:/hadr -e HADR_ENABLED=true --net=host store/ibmcorp/db2_developer_c:11.1.4.4-x86_64

    When you issue a container list "docker ps -a" it should show as running, not just created.

    Then issue your exec command but use the actual name db2inst1.
    docker exec -ti db2server_<your_container_name> bash -c "su - db2inst1"

    I think this will get you where you need to be.

    P.S.

    Check your twitter PM's

    ------------------------------
    Michael Krafick
    ------------------------------



  • 8.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Tue June 04, 2019 10:24 AM
    Edited by Rachel Miles Tue June 04, 2019 11:10 AM
    Okay, so I removed the old container and ran:
    docker run --name db2server --restart=always --privileged --ipc=host -p 50000 -p 55000 --env-file .env_list -v /Users/rachelmiles/db2:/database -v /Users/rachelmiles/db2:/hadr -e HADR_ENABLED=true --net=host store/ibmcorp/db2_developer_c:11.1.4.4-x86_64

    I got the message:
    WARNING: Published ports are discarded when using host network mode
    
    error: LICENSE not set to 'accept'
    Please set '-e LICENSE=accept' to accept License before use the DB2 software contained in this image.
    ​

    Now it says the status is "restarting."

    Looking at the Docker Logs, it looks like it's going in a loop with my license not being accepted, which is odd since I had that in the env file (which I just reran to double check).


    UPDATE: I removed my old container after redoing my .env file and then did the run command.

    This is what I got:
    WARNING: Published ports are discarded when using host network mode
    (*) HADR_ROLE_FOR_SETUP:PRIMARY
    (*) Previous setup has not been detected. Creating the users... 
    (*) Creating users ...
    (*) Creating instance ... 
    DB2 installation is being initialized.
    
     The host name "linuxkit-025000000001" is invalid. Specify a valid host name.
    
    A major error occurred during the execution that caused this program to 
    terminate prematurely. If the problem persists, contact your technical service 
    representative.
    
    For more information see the DB2 installation log at "/tmp/db2icrt.log.70".
    DBI1446I  The db2icrt command is running.
    
    
    DBI1264E  This program failed. Errors encountered during execution were
          written to the installation log file. Program name:
          db2icrt. Log file name: /tmp/db2icrt.log.70.
    
    Explanation: 
    
    This message is returned when some processes and operations have failed.
    Detailed information about the error was written to the log file.
    
    User response: 
    
    Contact IBM support to get assistance in resolving this issue. Keep the
    log file intact as this file is an important reference for IBM support.
    
    
       Related information:
       Contacting IBM Software Support
    
    
    (!) There was a problem configuring the instance. Copying over logs and traces to /database/config ...
    
    
                  _______   D B 2  S u p p o r t   ______
    
    
    This program generates information about a DB2 server, including information
    about its configuration and system environment. The output of this program
    is stored in a file named 'db2support.zip'. If possible, run this program
    while the problem is occurring.
    
    
    For the most complete output, this utility should be invoked with root
    authority. Users with more limited privileges on the system can run this tool,
    however, some of the data collection actions will result in reduced reporting
    and reduced output.
    
    Output file is "/database/config/db2icrt/db2support.zip"
    Time and date of this collection: 2019-06-04-15.04.15.114638
    
    Creating directory /database/config/db2icrt/DB2SUPPORT
    Starting collection on host linuxkit-025000000001
     Creating directory /database/config/db2icrt/DB2SUPPORT/linuxkit-025000000001_IIH
    Collecting resources group information
       The following file was not found or could not be executed during diagnostic
       data collection: /usr/bin/lssam
       The following file was not found or could not be executed during diagnostic
       data collection: /usr/bin/lsrsrc
       The following file was not found or could not be executed during diagnostic
       data collection: /usr/bin/lsrsrc
    Collecting user identity information
    Collecting current process information
    Collecting active interprocess communications facilities information
    Collecting system information
    Collecting detailed data on system and hardware errors
       The following file was not found or could not be executed during diagnostic
       data collection: /usr/bin/errpt
    Collecting registry contents
    Collecting GPFS information
       The following file was not found or could not be executed during diagnostic
       data collection: /usr/lpp/mmfs/bin/gpfs.snap
    Collecting configuration, log and trace information for RSCT
       The following file was not found or could not be executed during diagnostic
       data collection: /usr/bin/ctsnap
    Collecting information about installed DB2 products
    Collecting information about state of db2 instance
    Collecting information about DB2 product prerequisites
    Collecting /etc/services 
    Collecting /tmp/db2icrt.trc.70
    Collecting /tmp/db2icrt.log.70
    Collection on host linuxkit-025000000001 completed
    Compressing files in /database/config/db2icrt/DB2SUPPORT directory 
    Collecting /database/config/db2icrt/db2support.log 
    Collecting db2support.out 
    
    
    db2support is now complete.
     An archive file has been produced: "/database/config/db2icrt/db2support.zip"
    
    "15" warnings found during db2support collection
    ​

    But it seems like I'm logged in? So I'm sort of there, but it seems like something is kind of wrong.

    Guess I'll need to figure out what to do next to test it out!

    ------------------------------
    Rachel Miles
    ------------------------------



  • 9.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Tue June 04, 2019 01:01 PM
    Rachel, does your container show as running and can you EXEC into it? It sounds like the auto configuration with HADR didn't happen. I know Docker, I know HADR, but I never tried to set them up together before. I'm calling in the cavalry and brought this thread to the attention of someone who taught me to see if he can help.

    In between sessions I'll make my way to the main gathering area near registration if you want to sync. In the meantime I am going to try to recreate on my machine.

    ------------------------------
    Michael Krafick
    ------------------------------



  • 10.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Tue June 04, 2019 01:47 PM
    Figured it out. So the problem you are running into is a combination of cutting/pasting some example lines as default and then lines getting crossed between responses. I was able to stand up a 11.1.4.4 default docker image into a container (without HADR) by doing this..

    Need to get to the base docker directory I always work from:
    cd Desktop/Docker

    Logged into Docker so I can pull the image, from my command line:
    docker login
    (Enter ID/Password when prompted; image pulls down and is visible from "docker image list")

    Create a hidden ".env_list" file via "vi" command:
    vi .env_list

    Cut/Paste the following values as is. (If this is a Mac, change IS_OSXFS to "true"
    LICENSE=accept
    DB2INSTANCE=db2inst1
    DB2INST1_PASSWORD=password
    DBNAME=testdb
    BLU=false
    ENABLE_ORACLE_COMPATIBILITY=false
    UPDATEAVAIL=NO
    TO_CREATE_SAMPLEDB=false
    REPODB=false
    IS_OSXFS=false
    PERSISTENT_HOME=true
    HADR_ENABLED=false
    ETCD_ENDPOINT=
    ETCD_USERNAME=
    ETCD_PASSWORD=

    Exited and saved the file with hitting the escape key first before typing " :wq!" followed by enter.

    Used RUN command to create a container from the downloaded image:
    docker run -h db2server_ --name db2server --restart=always --detach --privileged=true -p 50000:50000 -p 55000:55000 --env-file .env_list -v /Users/mxk281/Desktop/Docker:/database 399b96dc7c1b

    • Where "/Users/mxk281/Desktop/Docker" was the directory I was in. You can use "pwd" to show you the full path name of the directory you are in and cut/paste it here instead.
    • "399b96dc7c1b" is the Image name from your "docker image list" output. Change it for what is listed next to your download.

    Execute command to put me inside the newly spun up virtual container (i.e. logging into the server)
    docker exec -ti db2server bash -c "su - db2inst1"



    ------------------------------
    Michael Krafick
    ------------------------------



  • 11.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Wed June 05, 2019 11:14 AM
    Edited by Rachel Miles Wed June 05, 2019 11:16 AM
    That [eventually] worked!!

    I decided to start from scratch and I removed all my docker images and containers because a lot of them had been installed via a GUI wizard for outdated technical previews. I moved my Docker folder to my Documents and followed your instructions.

    Along the way, I ran into a couple errors, but I figured them out.

    1.  One was that db2server is not supposed to have an underscore. So it should really be:
    docker run -h db2server --name db2server --restart=always
    --detach --privileged=true -p 50000:50000 -p 55000:55000 --env-file
    .env_list -v /Users/mxk281/Desktop/Docker:/database 399b96dc7c1b

    2. The instructions by Carlos down below say to install db2_developer_c:11.1.4.4-s390x and I should have realized that ZLinux was not the one I wanted.

    The pull store command that worked for me was this one:
    docker pull store/ibmcorp/db2_developer_c:11.1.4.4-x86_64

    Now, I'm good to go! I need to find a good tutorial on setting up a sample database now :)

    I really appreciate your help! And the how-to on creating an .env file. That went really smoothly.

    ------------------------------
    Rachel Miles
    ------------------------------



  • 12.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Tue June 04, 2019 01:20 PM
    Hi Rachel,
    we from DTE have created a lab on Docker and Db2 warehouse.
    This is a lab you can request. This will give you hopefully successfull impression on working with Db2 in a docker container.

    https://www.ibm.com/cloud/garage/dte/tutorial/ibm-db2-warehouse-docker-lab

    For the Db2 installation we showed the old /new non docker installation.
    Digital Technical Engagement
    video 4

    Joachim

    ------------------------------
    Joachim Stumpf
    ------------------------------



  • 13.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Tue June 04, 2019 09:46 AM
    What is the precise docker run command you are using?

    ------------------------------
    Carlos Mejia Johnson
    ------------------------------



  • 14.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Tue June 04, 2019 09:46 AM
    Sample Installation below:
    (This is for DB2 on ZLinux, change the db2_developer_c:11.1.4.4-s390x to your corresponding platform):

    # docker login
    # docker pull store/ibmcorp/db2_developer_c:11.1.4.4-s390x
    # mkdir /data
    # docker run -h db2server --name db2server --restart=always --detach --privileged=true -p 50000:50000 -p 55000:55000 --env-file .env_list -v /data:/database store/ibmcorp/db2_developer_c:11.1.4.4-s390x
    # docker ps | grep db2
    d3646927e758 store/ibmcorp/db2_developer_c:11.1.4.4-s390x "/var/db2_setup/lib/…" About a minute ago Up About a minute 0.0.0.0:50000->50000/tcp, 22/tcp, 60006-60007/tcp, 0.0.0.0:55000->55000/tcp db2server
    # docker logs d3646927e758
    (*) Creating users ...
    (*) Creating instance ...
    DB2 installation is being initialized.

    Total number of tasks to be performed: 4
    Total estimated time for all tasks to be performed: 309 second(s)

    Task #1 start
    Description: Setting default global profile registry variables
    Estimated time 1 second(s)
    Task #1 end

    Task #2 start
    Description: Initializing instance list
    ls: cannot access /database/data/db2inst1/NODE0000: No such file or directory
    Estimated time 5 second(s)
    Task #2 end

    Task #3 start
    Description: Configuring DB2 instances
    Estimated time 300 second(s)
    Task #3 end

    Task #4 start
    Description: Updating global profile registry
    Estimated time 3 second(s)
    Task #4 end

    The execution completed successfully.

    For more information see the DB2 installation log at "/tmp/db2icrt.log.69".
    DBI1446I The db2icrt command is running.


    DBI1070I Program db2icrt completed successfully.


    (*) Enabling TEXT_SEARCH for instance ...
    DB2 installation is being initialized.

    Total number of tasks to be performed: 4
    Total estimated time for all tasks to be performed: 309 second(s)

    Task #1 start
    Description: Setting default global profile registry variables
    Estimated time 1 second(s)
    Task #1 end

    Task #2 start
    Description: Initializing instance list
    Estimated time 5 second(s)
    Task #2 end

    Task #3 start
    Description: Configuring DB2 instances
    Estimated time 300 second(s)
    Task #3 end

    Task #4 start
    Description: Updating global profile registry
    Estimated time 3 second(s)
    Task #4 end

    The execution completed successfully.

    For more information see the DB2 installation log at
    "/tmp/db2iupdt.log.15631".
    DBI1446I The db2iupdt command is running.


    DBI1070I Program db2iupdt completed successfully.


    06/04/2019 06:57:32 0 0 SQL1032N No start database manager command was issued.
    SQL1032N No start database manager command was issued. SQLSTATE=57019
    (*) Cataloging existing databases
    (*) Applying Db2 license ...

    LIC1402I License added successfully.


    LIC1426I This product is now licensed for use as outlined in your License Agreement. USE OF THE PRODUCT CONSTITUTES ACCEPTANCE OF THE TERMS OF THE IBM LICENSE AGREEMENT, LOCATED IN THE FOLLOWING DIRECTOR
    Y: "/opt/ibm/db2/V11.1/license/en_US.iso88591"
    (*) Saving the checksum of the current nodelock file ...
    (*) Updating DBM CFG parameters ...
    DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed
    successfully.
    DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed
    successfully.
    DB20000I The UPDATE DATABASE MANAGER CONFIGURATION command completed
    successfully.
    No Cgroup memory limit detected, instance memory will follow automatic tuning

    DB2 State : Operable
    DB2 has not been started
    Starting DB2...

    06/04/2019 06:57:47 0 0 SQL1063N DB2START processing was successful.
    SQL1063N DB2START processing was successful.
    (*) Starting TEXT SEARCH service ...
    CIE00001 Operation completed successfully.
    (*) User chose to create testdb database
    (*) Creating database testdb ...
    DB20000I The CREATE DATABASE command completed successfully.
    DB20000I The ACTIVATE DATABASE command completed successfully.
    06/04/2019 06:59:22 0 0 SQL1026N The database manager is already active.
    SQL1026N The database manager is already active.
    ### Enabling LOGARCHMETH1

    Database Connection Information

    Database server = DB2/LINUXZ64 11.1.4.4
    SQL authorization ID = DB2INST1
    Local database alias = TESTDB

    DB20000I The UPDATE DATABASE CONFIGURATION command completed successfully.
    SQL1363W One or more of the parameters submitted for immediate modification
    were not changed dynamically. For these configuration parameters, the database
    must be shutdown and reactivated before the configuration parameter changes
    become effective.
    ### Restarting DB2
    06/04/2019 06:59:30 0 0 SQL1064N DB2STOP processing was successful.
    SQL1064N DB2STOP processing was successful.

    ------------------------------
    Carlos Mejia Johnson
    ------------------------------



  • 15.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Tue June 04, 2019 09:47 AM
    what is precise docker run command you are running?

    docker run -h db2server
    --name db2server --restart=always \
    --detach \
    --privileged=true \
    -p 50000:50000 -p 55000:55000 \
    --env-file .env_list \
    -v <db dir>:/database \
    <image name>

    ------------------------------
    Carlos Mejia Johnson
    ------------------------------



  • 16.  RE: Need Help Setting up the Db2 Developer-C Edition

    Posted Tue June 04, 2019 11:13 AM
    I put that info higher up! Thanks!

    ------------------------------
    Rachel Miles
    ------------------------------