Results 1 to 8 of 8

Thread: Sqlcode= -1390

  1. #1
    Join Date
    Apr 2003
    Location
    Florida
    Posts
    79

    Unanswered: Sqlcode= -1390

    I can't find any documentation on this SQLCODE.... -1390
    We had to drop and recreate our db2admin server - we got it restarted ok but I still cannot connect (attach) to it via "Task Center")
    db2 udb v8.1 on Linux.

    Any ideas?
    Thanks!
    Rick

  2. #2
    Join Date
    Jan 2002
    Posts
    165
    On Win2000,in directory SQLLIB there is a folder DB2DAS00 (name
    of db2admin server).Under that,you can find log for db2admin
    server.Try check that log.
    Cheers,Zvonimir

  3. #3
    Join Date
    Apr 2003
    Posts
    191

    Re: Sqlcode= -1390

    Hi,

    did you try:

    db2 "? sql1390n"

    Johann


    Originally posted by Rick-dba
    I can't find any documentation on this SQLCODE.... -1390
    We had to drop and recreate our db2admin server - we got it restarted ok but I still cannot connect (attach) to it via "Task Center")
    db2 udb v8.1 on Linux.

    Any ideas?
    Thanks!
    Rick

  4. #4
    Join Date
    Apr 2003
    Location
    Florida
    Posts
    79

    Red face

    SQL1390N doesn't return anything either.... The actual code is "DBA1177N" which returns:
    DBA1177N A database connection to the Tools Catalog Database database-name cannot be made. SQLCODE sqlcode

    Explanation: A database connection to the Tools Catalog Database database-name cannot be made. SQLCODE sqlcode

    User Response: Refer to the user response for the SQLCODE returned from the connect operation.

    But I can't find a definition of the problem because SQLCODE -1390 is not explained anywhere........
    There is nothing in either log referring to the problem:
    db2dasdiag.log or db2diag.log

    I can connect to the DB and run queries against it - but "Task Center" cannot connect.

  5. #5
    Join Date
    Mar 2003
    Posts
    33

    Re: Sqlcode= -1390

    How about this:

    SQL1390C The environment variable DB2INSTANCE is not defined or is invalid.

    Explanation: The environment variable DB2INSTANCE is not defined
    or is not set to a valid instance owner.

    User Response: Set the DB2INSTANCE environment variable to the
    name of the instance to use. If you do not know the name of the
    instance to use or how to set the DB2INSTANCE environment
    variable to the instance name, refer to the Administration
    Guide.

    Federated system users: refer to the Installation and
    Configuration Supplement for DB2INSTANCE information.

    Ensure your PATH environment variable contains the sqllib/adm
    path in the home directory of the instance you want to use (for
    example, /u/instance/sqllib/adm, where /u/instance is the home
    directory of the instance owner on a UNIX system).




    Originally posted by Rick-dba
    I can't find any documentation on this SQLCODE.... -1390
    We had to drop and recreate our db2admin server - we got it restarted ok but I still cannot connect (attach) to it via "Task Center")
    db2 udb v8.1 on Linux.

    Any ideas?
    Thanks!
    Rick
    -r-

  6. #6
    Join Date
    Apr 2003
    Location
    Florida
    Posts
    79

    Thumbs up

    F.Y.I.
    I got it fixed - but the error message (SQL1390C) did not really explain the problem.... (It did help a lot though - THANKS!)

    The real problem was, when I dropped and recreated the admin server the following scheduler settings were not set:
    Tools Catalog Database (TOOLSCAT_DB) = TOOLSDB
    Tools Catalog Database Instance (TOOLSCAT_INST) = db2inst1
    Tools Catalog Database Schema (TOOLSCAT_SCHEMA) = SYSTOOLS

    They are set right now and everything seems to be working.

    Thanks Everyone! You guys are a Great help!
    Rick

  7. #7
    Join Date
    Jul 2002
    Posts
    86
    Originally posted by Rick-dba
    F.Y.I.
    I got it fixed - but the error message (SQL1390C) did not really explain the problem.... (It did help a lot though - THANKS!)

    The real problem was, when I dropped and recreated the admin server the following scheduler settings were not set:
    Tools Catalog Database (TOOLSCAT_DB) = TOOLSDB
    Tools Catalog Database Instance (TOOLSCAT_INST) = db2inst1
    Tools Catalog Database Schema (TOOLSCAT_SCHEMA) = SYSTOOLS

    They are set right now and everything seems to be working.

    Thanks Everyone! You guys are a Great help!

    Rick
    Could you please explaine How did you set these parameters? let me know the command.
    Thanks

  8. #8
    Join Date
    Apr 2003
    Location
    Florida
    Posts
    79
    DB2 UDB v8.1 on Linux:

    First I issued "db2 get admin cfg" to view the current parameters -
    Then I issued the following:
    "db2 update admin cfg using TOOLSCAT_DB <dbname>"
    "db2 update admin cfg using TOOLSCAT_INST <inst-name>"
    "db2 update admin cfg using TOOLSCAT_SCHEMA <schema>"

    Look for the APPLICATIONS table in the <dbname> and use that schema name.

    I stopped and started everything after setting these, but I'm not sure if I really needed to do that.

    Hope this helps someone -
    Rick

Posting Permissions

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