Db2

 View Only
  • 1.  DB2 11.5.9 Community Edition Response File

    Posted Thu December 05, 2024 10:26 AM

    Hi all, with DB2 11.1, we could specify LocalSystem in the response file under DB2.USERNAME.

    When running 11.5.9 installer, we get the following:

    1: ERROR:LocalSystem account cannot be used in ESE and AESE admin installation. Specify 
    another account name for the installation.

    I am using the PROD=DB2_SERVER_EDITION, as I cannot find anywhere something that specifically related to Community Edition, as I dont think Community Edition is ESE or AESE, if i understand right?

    Looking in the documentation too for 11.5 it categorically states: 

    You may also use the built-in LocalSystem account as your Service Logon account for all products.

    Required user accounts for installation of Db2 Connect products (Windows)

    Ibm remove preview
    Required user accounts for installation of Db2 Connect products (Windows)
    Before you begin installation tasks you must have an installation user account. During the installation, you can also choose to create one or more setup user accounts, such as a Db2 Administration Server (DAS) user account or a Db2 instance user account.
    View this on Ibm >

    Any help would be much appreciated.



    ------------------------------
    Chris Pressley
    ------------------------------


  • 2.  RE: DB2 11.5.9 Community Edition Response File

    Posted Thu December 05, 2024 04:37 PM

    When installing Db2 11.5.9 Community Edition on Windows using a response file, specifying the LocalSystem account for the DB2.USERNAME parameter can lead to errors, as you've encountered.

    This issue arises because certain editions of Db2, including the Community Edition, may restrict the use of the LocalSystem account for service logon during installation.

    Understanding the Issue:

    The error message:

    ERROR: LocalSystem account cannot be used in ESE and AESE admin installation. Specify another account name for the installation.
    

    indicates that the installer does not permit the LocalSystem account for the specified edition. While the documentation suggests that the LocalSystem account can be used for all products, practical restrictions exist for certain editions.

    Recommended Solution:

    To resolve this issue, specify a valid local or domain user account in the response file:

    1. Create a Local User Account:

      • On your Windows system, create a new local user account intended for Db2 services.
    2. Assign Necessary Permissions:

      • Ensure this account has the required permissions to run Db2 services.
    3. Modify the Response File:

      • Set the DB2.USERNAME parameter to the newly created user account.
      • Provide the corresponding password in the DB2.PASSWORD parameter.

    Example Response File Entries:

    DB2.USERNAME=db2admin
    DB2.PASSWORD=your_password

    Additional Considerations:

    • User Rights: Ensure the specified user has the necessary rights to log on as a service and has administrative privileges on the system.
    • Service Configuration: After installation, verify that Db2 services are configured to run under the specified user account.

    By specifying an appropriate user account in the response file, you can proceed with the installation without encountering the LocalSystem account restriction.

    For more detailed information on response file installations and user account requirements, refer to the IBM Db2 11.5 documentation



    ------------------------------
    Raydo Matthee
    CEO | IBM Certified Facilitator
    Skunkworks (Pty) Ltd
    Johannesburg
    +27833807950
    ------------------------------



  • 3.  RE: DB2 11.5.9 Community Edition Response File

    Posted Fri December 06, 2024 03:49 AM

    Hi Raydo, Thanks for that.

    I would like to install 11.5 Community Edition in the same way we installed 11.1 though, and have the Log on account as LocalSystem, so that DB2 can run without user logon.

    Is that possible? I think the workaround would be to set up DB2 with a new local user for DB2 as outlined above, then manually change the LogOn in service.msc for the affected services. Is this recommended?

    Thanks

    Chris



    ------------------------------
    Chris Pressley
    ------------------------------