Db2

Db2

Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems.

 View Only
Back to discussions
Expand all | Collapse all

Win 64 drop

  • 1.  Win 64 drop

    Posted Wed March 31, 2021 12:11 PM

    I am trying to install a single partition instance of the DB2 drop on Windows x64.  I am getting "The creation of the process for the partitioned instance failed.  Return value is "2265907380".  not sure what it means.  I am using Windows 7 Enterprise on an i7 (4710MQ) x64 machine.

     

    I was able to create the instance manually using db2icrt so I have a work around... just wondering why this happened during the install


    #Db2
    #Db2EarlyAccessProgram(EAP)Forum


  • 2.  RE: Win 64 drop

    Posted Wed March 31, 2021 12:11 PM

    Yes, the developer said the fix will be delivered in time for the next drop. - Erik

     

    Jan 5/16 - QA confirmed the fix on a recent build. Will be available in the next refresh. - Erik


    Original Message


  • 3.  RE: Win 64 drop

    Posted Wed March 31, 2021 12:11 PM

    never mind about db2icrt getting me by... something is wrong enough so I can't create databases.  The create database command locks up.  I get the following two messages in db2diag.log

    2015-12-15-13.17.36.869000-480 I21811F582           LEVEL: Event
    PID     : 4072                 TID : 13104          PROC : db2syscs.exe
    INSTANCE: DB2_01               NODE : 000           DB   : LOCALNU
    APPHDL  : 0-8                  APPID: *LOCAL.DB2_01.151215211731
    AUTHID  : AGOODMAN             HOSTNAME: USSPNAGOODMAN01
    EDUID   : 13104                EDUNAME: db2agent (instance)
    FUNCTION: DB2 UDB, trace services, pdInvokeCalloutScriptDirect, probe:10
    START   : Invoking E:\tools\IBM\db211\SQLLIB\bin\db2cos_trap.bat from oper syste
    m services sqloEDUExceptionFilter

    2015-12-15-13.17.37.369000-480 I22395F438           LEVEL: Event
    PID     : 4072                 TID : 16432          PROC : db2syscs.exe
    INSTANCE: DB2_01               NODE : 000
    HOSTNAME: USSPNAGOODMAN01
    EDUID   : 16432                EDUNAME: db2pdbe
    FUNCTION: DB2 UDB, RAS/PD component, pdGetDumpFileDescriptor, probe:20
    START   : Check E:\tools\IBM\db211\SQLDATA\IBM\DB2\DB2COPY2\DB2_01\9764.000.db2pd.bin for additional data.

    db2diag invoked with the default set of filtering/formatting options
    on file "E:\tools\IBM\db211\SQLLIB\BIN\db2diag.log".

     

    I have a feeling it is all down to the install difficulties.


    Original Message


  • 4.  RE: Win 64 drop

    Posted Wed March 31, 2021 12:11 PM
    We have contacted developers and we are currently investigating your question. We will let you know as soon as we have a response.
    Original Message


  • 5.  RE: Win 64 drop

    Posted Wed March 31, 2021 12:11 PM

    Adam,

     

    There's been a boundary condition issue discovered recently, would you check to see if your machine name is 15 bytes?

     

    If so, please change the machine name to something shorter and reinstall.


    Original Message


  • 6.  RE: Win 64 drop

    Posted Wed March 31, 2021 12:11 PM

    my machine name is 15 bytes... unfortunately I don't think I can change it since it is set by ITS policy. (technically I -can- change it but I fear I would get yelled at)

    Will this be fixed by the next drop?  If so I can wait till then and try again.


    Original Message


  • 7.  RE: Win 64 drop

    Posted Wed March 31, 2021 12:12 PM

    Yes, the developer said the fix will be delivered in time for the next drop. - Erik

     

    Jan 5/16 - QA confirmed the fix on a recent build. Will be available in the next refresh. - Erik


    Original Message


  • 8.  RE: Win 64 drop

    Posted Wed March 31, 2021 12:12 PM
    Was this issue fixed in yesterdays drop? I am still getting the error.
    Original Message


  • 9.  RE: Win 64 drop

    Posted Wed March 31, 2021 12:12 PM
    Adam - It was in the code base before this level (1512292100) and tested. I will follow up with QA.
    Original Message


  • 10.  RE: Win 64 drop

    Posted Wed March 31, 2021 12:12 PM
    any word from QA?
    Original Message


  • 11.  RE: Win 64 drop

    Posted Mon March 30, 2020 10:28 AM

    Adam,

    To understand why you are seeing the issue can we get the following information:

     - db2level command output

     - Switch on the trace using the following command before you execute the create database command

    db2trc on -f c:\trace1
     - Execute the create database command

     - Switch off the trace & send us the .fmt & .flw files.

    db2trc off

    db2trc fmt c:\trace1 c:\tesce1.fmt

    db2trc flw c:\trace1 c:\tesce1.flw

     

    Thanks

    Roopa M


    Original Message


  • 12.  RE: Win 64 drop

    Posted Mon March 30, 2020 10:33 AM

    Roopa,  

         I didn't get as far as trying the database create because the install failed with "The creation of the process for the partitioned instance failed.  Return value is "2265907380". 

     

    last time I tried db2icrt to get around this, which didn't work...  Should I try that again? 

     

    oh, and db2level gives

    SQL1022C  There is not enough memory available to process the command.

     

    I have also attached the install logDB2-SERVER-Fri Jan 29 06_56_24 2016.logView Details


    Original Message


  • 13.  RE: Win 64 drop

    Posted Mon March 30, 2020 10:30 AM

    Roopa,  

         I didn't get as far as trying the database create because the install failed with "The creation of the process for the partitioned instance failed.  Return value is "2265907380". 

     

    last time I tried db2icrt to get around this, which didn't work...  Should I try that again? 

     

    oh, and db2level gives

    SQL1022C  There is not enough memory available to process the command.

     

    I have also attached the install logDB2-SERVER-Fri Jan 29 06_56_24 2016.logView Details


    Original Message


  • 14.  RE: Win 64 drop

    Posted Mon March 30, 2020 10:33 AM
    this time db2icrt seems to get past the issue. I think perhaps it has to do with text search but I am not sure.
    Original Message


  • 15.  RE: Win 64 drop

    Posted Mon March 30, 2020 10:33 AM
    I think my install problem is because the installer didn't recognize that I had another instance of DB2 with Text Search already installed so it tried to use the same port and name
    Original Message


  • 16.  RE: Win 64 drop

    Posted Mon March 30, 2020 10:33 AM

    Adam,

    It would help if you pass -l & -t parameters to setup.exe to collect the log & trace file to get to the root cause of this issue.

    For eg: setup.exe -l c:\db2log.log -t c:\db2trc.trc


    Original Message


  • 17.  RE: Win 64 drop

    Posted Mon March 30, 2020 10:33 AM
    this time db2icrt seems to get past the issue. I think perhaps it has to do with text search but I am not sure.
    Original Message


  • 18.  RE: Win 64 drop

    Posted Mon March 30, 2020 10:43 AM

    Adam,

    Also, which port number was configured for text search for the previously existing installation. Do you see any issues with entries in your /etc/services file for the ports being used by Text Search. ?


    Original Message


  • 19.  RE: Win 64 drop

    Posted Mon March 30, 2020 10:43 AM

    Gopi,

     

    after an install that gets the 2265907380 error my services file looks unchanged.  These are the db2 entries

    db2j_DB2_01    55001/tcp
    DB2_DB2  60000/tcp
    DB2_DB2_1 60001/tcp
    DB2_DB2_2 60002/tcp
    DB2_DB2_3 60003/tcp
    DB2_DB2_4 60004/tcp
    DB2_DB2_END 60005/tcp
    db2c_DB2    50000/tcp

    I have attached the log and trc generated.  db2trc.trcView Detailsdb2log.logView Details

    Also if I install and change the text search service name (db2j_DB2_02) and port number (56001) the install completes normally.  If I then try to start the text search server with:
    db2ts start for text
    I get
    SQL20427N  An error occurred during a text search administration procedure or command. The error message is "CIE00340 Cannot start executable program "C:\windows\system32\cmd.exe". ". SQLSTATE=38H14

    I saved the trace/log from that install too db2trc2.trcView Detailsdb2log2.logView Details


    Original Message


  • 20.  RE: Win 64 drop

    Posted Mon March 30, 2020 10:43 AM
    any progress on this?
    Original Message


  • 21.  RE: Win 64 drop

    Posted Mon March 30, 2020 10:43 AM

    Adam,

    I reviewed the logs & trace file.

    As per the trace file in case of install failure the cause is "The specified service name or port number conflict with existing values in the TCP/IP services file. Provide a service name and a port number that is available on the system."

    We were also able to re-create the issue when we tried to use a port for text search which was already used by an other application(in our case it was java).

    You can use this command to try and configure a new port for text search

    Eg:

    configTool configureHTTPListener -adminHTTPPort 55512 -configPath C:\ProgramData\IBM\DB2\DB2COPY1\DB2\db2tss\config

    Also, is it possible to check using process explorer which application is already using the port specified.


    Original Message


  • 22.  RE: Win 64 drop

    Posted Mon March 30, 2020 10:43 AM

    >Also, is it possible to check using process explorer which application is already using the port specified.

    Unnecessary, I know what app it is.  It is the OTHER install of DB2 text search.   I have DB2 10.5 install and DB2 beta installed.  The two text searches seem to interfere with each other.

    If I run the configTool command you gave, I can now start both text searches. 

    So, this seems to be an issue with the installer not recognizing that ports are in use.


    Original Message


Related Content