Results 1 to 2 of 2
  1. #1
    Join Date
    Dec 2003
    Posts
    78

    Question Unanswered: System Error ???!!!

    Hello all,
    we have a production db2 udb server v7.2 fixpack 8 on windows 2000 terminal.
    there is an instance called prod2 there, it was working well for years. i had checked there a week ago,with no problems.Now i just saw that client configuration assistant doesn't see that instance under the server tree.

    but the databases that had already been added to control center are successfully working, all tables etc. are shown, and no problem have been reported about the applications working on prod2's databases.

    i logged on the server and using CLP, used those commands there, see what i got??:

    db2 => quit
    DB20000I The QUIT command completed successfully.


    C:\SQLLIB\BIN>db2 get instance

    The current database manager instance is: DB2


    C:\SQLLIB\BIN>db2ilist
    PROD3
    PROD2
    PROD
    DB2CTLSV
    DB2

    C:\SQLLIB\BIN>
    C:\SQLLIB\BIN>set DB2INSTANCE=prod2

    C:\SQLLIB\BIN>db2 list db directory
    SQL5005C System Error.

    C:\SQLLIB\BIN>
    C:\SQLLIB\BIN>
    C:\SQLLIB\BIN>
    C:\SQLLIB\BIN>db2 connect to pro2db1
    SQL5005C System Error.

    C:\SQLLIB\BIN>
    C:\SQLLIB\BIN>db2 get instance
    SQL5005C System Error.

    C:\SQLLIB\BIN>




    WHAT IS GOING ON???
    PLEASE CAN ANYONE MAKE ANY COMMENTS ON THAT???

  2. #2
    Join Date
    Jul 2003
    Location
    Austin, TX, USA
    Posts
    278

    Clues.

    Hi,

    I faced the same problem yesterday but that was with administration clients on windows. What I observed that when I added/cataloged any instance or database using the Control and subsequently exited and re-logged in to the control center the database tree would dissappear.

    What I observed that it was happening because of the fixpack levels being different on the Server and the Client. So I got them on the same fixpack i.e FixPack 4a.

    I experienced the same on different server and getting that on FixPack 4a, rebinding the databases and packages and a restart solved my problem.

    Hope you can get some pointers from this.
    HTH

    Nitin

    Ask the experienced rather than the learned

Posting Permissions

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