Results 1 to 15 of 15
  1. #1
    Join Date
    Apr 2006
    Posts
    6

    Unanswered: *-- Database agent STRANGE ERROR

    I had currently encounter the following error and am exhausted of trying to find more ways to solve the following problem. It occurs whenever a connection is made to the local database. However when connection is made to a remote database, the operation will be successfull.

    SOFTWARE:
    VB.NET
    IBM DB2

    ERROR:
    select recordystem.Data.Odbc.OdbcException: ERROR [08001] [IBM][CLI Driver] SQL1224N A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE=55032

    ERROR [IM006] [Microsoft][ODBC Driver Manager] Driver's SQLSetConnectAttr failed

    ERROR happens at
    Try
    da.Fill(ds, "MyTable")

    Catch ex As Exception

    System.Diagnostics.Debug.WriteLine("select record:" & ex.ToString)
    Finally
    sqlConn.Close()
    End Try

    Help!!!
    Thanks
    Last edited by EsOUP; 04-02-06 at 23:35.

  2. #2
    Join Date
    Aug 2002
    Location
    Chennai, India
    Posts
    184
    Check this out...
    $ db2 "? SQL1224N"

    SQL1224N A database agent could not be started to service a
    request, or was terminated as a result of a database
    system shutdown or a force command.

    Explanation: The message may be attributed to any of the
    following cases.

    o The database manager has not been started on the database
    server

    o The database manager was stopped

    o The database manager has already allocated the maximum number
    of agents

    o The database agent was forced off by the system
    administrator

    o The database agent was terminated due to an abnormal
    termination of a key database manager process

    o The application is using multiple contexts with local
    protocol. In this case the number of connections is limited
    by the number of shared memory segments to which a single
    process can be attached. For example, on AIX, the limit is
    ten shared memory segments per process.



    Additional federated server cases are:

    o The maximum number of processes per user (maxuproc on AIX) at
    the operating system level has been exceeded.

    o In the client/server environment using the TCP/IP protocol,
    the port number assigned to the TCP/IP service name on the
    client is not the same as the port number on the server.



    This situation can be detected by federated server or by the data
    source.

    User Response: Reissue the database request. If a connection
    cannot be established, then ensure that the database manager has
    been started successfully. Additionally, ensure that the
    maxagents database manager configuration parameter is
    appropriately configured.

    Federated system users, should also:

    o Isolate the problem to the data source rejecting the request
    (see the problem determination guide for procedures to
    follow to identify the failing data source) and ensure that
    the communication subsystem is active and that the database
    manager and required communication protocol server processes
    have been started on the database server.

    o For AIX operating systems, check the setting of maxuproc and
    change it if needed. maxuproc restricts the number of
    processes that can run under a given federated server. The
    default setting is 40.

    You can check the current setting of maxuproc with the
    command:

    .
    lsattr -E -l sys0

    To view the number of processes currently running under a
    given federated server, use the command:

    ps -ef | grep instdj1 | wc -l

    where "instdj1" is the instance name of the federated
    server.

    To change maxuproc, use the command:

    chdev -l sys0 -a maxuproc='nn'

    where nn is the new integer value of maxuproc.



    If the application is using multiple contexts with local protocol,
    then either reduce the number of connections in the application,
    or switch to another protocol (for example, TCP/IP). For users
    on AIX version 4.2.1 or newer, the environment variable EXTSHM
    can be set to ON to increase the number of shared memory segments
    to which a single process can be attached.

    sqlcode: -1224

    sqlstate: 55032

    $

    HTH.

  3. #3
    Join Date
    Apr 2006
    Posts
    6

    Problem remains

    Yea anyway thanks for replying but had already seen that solution sheet and tried out all the possible solution provided by IBM DB2. Had tried to increase number of agents and logs but it still seem to post the same error. Remote database access is a no-problem but with regards to local DB connection the problem arises.

    I had also tried reinstalling the whole IBM DB2 fearing that i had misconfigured the DB2 somehow but it still prove fruitless. I had also increased my local number of access to a high level to prevent any problem.
    Besides the above, i created a number of catalog and tried all of them out but as long as it is a local connection from vb.net to DB2 it will produce the same error. Also noted that connection between Jbuilder X and DB2 does not carry any error.

    So am wondering, is there any other way i can try to solve the database agent problem.

    Helpppp!!!!
    Cheerz all =P


    ps. I am not using a AIX OS.

  4. #4
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Are there any useful messages in db2diag.log ?

    Set the diaglevel to 4 and retry to get as much info as possible from the diag log

    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  5. #5
    Join Date
    Apr 2006
    Posts
    6

    Database Agent Problem Unsolved

    Thanks sathyaram_s , had tried your proposed solution and set diaglevel to 4 but the problem did not go away. Currently am still looking for ways to solve the problematic 'DB2 database agent not started' error.

    Help still needed!
    Cheerz all =P

    ps. Hope that the final solution is not to bring in a new com lol.

  6. #6
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Setting the diaglevel to 4 will not eliminate the problem ... But will log messages into the db2diag.log file about the problem

    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  7. #7
    Join Date
    Apr 2006
    Posts
    6
    Ok i am kindda new to this DB2 here, so can you guide me as where to find the log file and the log file that i need to look at to find the error?

    Thanks!

  8. #8
    Join Date
    Aug 2001
    Location
    UK
    Posts
    4,650
    Issue the command
    db2 get dbm cfg

    and find the value of DIAGPATH parameter. If it is null then it is C:\program files\ibm\sqllib\db2 (IIRC) .. Otherwise use the 'Search Files' to find db2diag.log

    db2 update dbm cfg using diaglevel 4

    Then db2stop and db2start commands.

    Before issuing db2start, it may be a good idea to move the original db2diag.log and start fresh.

    After the instance is started, do the operation that's causing the errror and look at the db2diag.log file.

    HTH

    Sathyaram
    Visit the new-look IDUG Website , register to gain access to the excellent content.

  9. #9
    Join Date
    Apr 2006
    Posts
    6

    Error Log

    Hi sathyaram_s, I had done the logging as you had mentioned and the following are the error sections which i had filtered out. I m not very sure how to resolve the error. Other than the following main error sections i had found this : SQLJC_ERROR_NOCONNECTION
    "COMMUNICATION ERROR, NO CONNECTION"

    and also : CCI Error

    mainly mostly mentioned that connection failed. What are the possibilities for a local connection to fail other than the reasons mentioned in the help file. I had checked my connection statements, and my passwords and user name are correct.



    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    2006-04-07-08.20.31.093000+480 I1572H925 LEVEL: Error
    PID : 1088 TID : 2016 PROC : db2fmp.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
    DATA #1 : Hexdump, 136 bytes
    0x00FF8710 : 5351 4C43 4120 2020 8800 0000 7E8A FFFF SQLCA ....~...
    0x00FF8720 : 1300 33FF 5041 5353 574F 5244 204D 4953 ..3.PASSWORD MIS
    0x00FF8730 : 5349 4E47 FF20 2020 2020 2020 2020 2020 SING.
    0x00FF8740 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00FF8750 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x00FF8760 : 2020 2020 2020 2020 5351 4C45 5853 4D43 SQLEXSMC
    0x00FF8770 : 3E01 5C80 3E01 0000 0000 0000 0000 0000 >.\.>...........
    0x00FF8780 : 0000 0000 0000 0000 2020 2020 2020 2020 ........
    0x00FF8790 : 2020 2030 3830 3031 08001

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

    2006-04-07-08.20.31.703000+480 I6063H1011 LEVEL: Error
    PID : 400 TID : 3060 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000 DB : NEWDB
    APPHDL : 0-38 APPID: *LOCAL.DB2.060407002028
    FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
    DATA #1 : Hexdump, 136 bytes
    0x020AFAA8 : 5351 4C43 4120 2020 8800 0000 38FB FFFF SQLCA ....8...
    0x020AFAB8 : 0000 2020 2020 2020 2020 2020 2020 2020 ..
    0x020AFAC8 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x020AFAD8 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x020AFAE8 : 2020 2020 2020 2020 2020 2020 2020 2020
    0x020AFAF8 : 2020 2020 2020 2020 5351 4C4A 434D 4E20 SQLJCMN
    0x020AFB08 : 1C00 3681 1C00 0000 0000 0000 0000 0000 ..6.............
    0x020AFB18 : 0000 0000 0000 0000 2020 2020 2020 2020 ........
    0x020AFB28 : 2020 2035 3530 3332 55032

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  10. #10
    Join Date
    Sep 2004
    Posts
    8

    Similar error encountered

    Hi EsOUP,
    Could you figure out any reason why this error is coming?
    Actually even I am facing a similar error. The db2diag.log shows:
    2006-04-07-18.29.14.626636+330 I40093G906 LEVEL: Error
    PID : 11871 TID : 3053331328 PROC : db2bp
    INSTANCE: db2ins25 NODE : 000
    FUNCTION: DB2 UDB, oper system services, sqlofica, probe:10
    DATA #1 : Hexdump, 136 bytes
    0xBFFFDCD8 : 5351 4C43 4120 2020 8800 0000 38FB FFFF SQLCA ....8...
    0xBFFFDCE8 : 2400 2D32 3039 3731 3531 3935 37FF 2AFF $.-2097151957.*.
    0xBFFFDCF8 : 2AFF 2AFF 2AFF FF53 454D 4150 484F 5245 *.*.*..SEMAPHORE
    0xBFFFDD08 : 2057 4149 54FF 2020 2020 2020 2020 2020 WAIT.
    0xBFFFDD18 : 2020 2020 2020 2020 2020 2020 2020 2020
    0xBFFFDD28 : 2020 2020 2020 2020 5351 4C4A 434D 4E20 SQLJCMN
    0xBFFFDD38 : 1C00 3681 1C00 0000 0000 0000 0000 0000 ..6.............
    0xBFFFDD48 : 0000 0000 0000 0000 2020 2020 2020 2020 ........
    0xBFFFDD58 : 2020 2035 3530 3332 55032


    Also there is one more log file which called db2inst1.log:
    2006-04-07-18.29.04.529627 Instance:db2ins25 Node:000
    PID:15466(db2star2) TID:3007166272 Appid:none
    base sys utilities DB2StartMain Probe:911

    ADM7513W Database manager has started.
    ^^
    2006-04-07-18.29.09.613417 Instance:db2ins25 Node:000
    PID:15561(db2agent (TOOLSDB)) TID:3007166976 Appid:none
    oper system services sqloEDUCodeTrapHandler Probe:10 Database:TOOLSDB

    ADM0503C An unexpected internal processing error has occurred. ALL DB2
    PROCESSES ASSOCIATED WITH THIS INSTANCE HAVE BEEN SHUTDOWN. Diagnostic
    information has been recorded. Contact IBM Support for further assistance.
    ^^
    2006-04-07-18.29.09.627095 Instance:db2ins25 Node:000
    PID:15494(db2ipccm) TID:3007166976 Appid:none
    oper system services sqloEDUCodeTrapHandler Probe:10

    ADM0503C An unexpected internal processing error has occurred. ALL DB2
    PROCESSES ASSOCIATED WITH THIS INSTANCE HAVE BEEN SHUTDOWN. Diagnostic
    information has been recorded. Contact IBM Support for further assistance.
    ^^
    2006-04-07-18.29.14.532777 Instance:db2ins25 Node:000
    PID:15480(db2wdog) TID:3007166976 Appid:none
    oper system services sqloRunInstance Probe:490

    ADM0503C An unexpected internal processing error has occurred. ALL DB2
    PROCESSES ASSOCIATED WITH THIS INSTANCE HAVE BEEN SHUTDOWN. Diagnostic
    information has been recorded. Contact IBM Support for further assistance.

  11. #11
    Join Date
    Apr 2006
    Posts
    6
    Hi Sayali, I am unable to help too as i myself is unaware of the solution.

  12. #12
    Join Date
    Jul 2002
    Posts
    48
    What i understood from your question is , you have local database server which you are not able to access. But you are able to connect to other servers through the db2 udb client you have installed.

    On that assumption and checking the log file i feel check who has installed the db2 udb in your machine. Check the password for the startup and services. Password could have been reset, so you have reset the password in the services section also....Thanks

  13. #13
    Join Date
    Jan 2004
    Posts
    49
    I think this is becoz you are not login using "db2admin" user id (administrator id) on local db server. Check it and let me know

  14. #14
    Join Date
    Sep 2004
    Posts
    8

    Unable to resolve the issue

    Hi Bala,
    I have tried using the db2 instance user (which is db2inst1) for logging in and I am still facing this issue for the logs being created. This seems to be some kind of an internal error in the plugin but I am unbale to trace that exactly.

    Thanks for all the help.

    Regards,
    Sayali

  15. #15
    Join Date
    Jul 2002
    Posts
    48
    If you can check through which id db2 process is executing. If it's db2admin, try modifying the password to the existing one.... Should be working...Thanks
    Nagesh

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •