Topic
6 replies Latest Post - ‏2012-12-05T02:58:35Z by SystemAdmin
SystemAdmin
SystemAdmin
5837 Posts
ACCEPTED ANSWER

Pinned topic DB2 Express-C 10.1 Failed Instance Validation: Reason Code=7

‏2012-12-03T16:01:01Z |
I just installed DB2 Express-C 10.1 64-bit on Windows 7, and I can't validate the instance. I've looked all over the web, and can't find any references to this problem. Here's the output from DB2VAL.EXE:


C:\Program Files\IBM\SQLLIB\BIN>db2val
DBI1379I The db2val command is running. This can take several minutes.

DBI1333I Installation file validation for the DB2 copy DB2COPY1
was successful.

DBI1338E The validation of instance DB2 failed. Reason
code=7.

Explanation:

1. The default instance is not set.
2. Some files in the instance directory are damaged. The symbolic links
of the files are not pointing to the current DB2 copy installation
path, and the file permission and ownership might have been changed.
3. The DB2 Extended Security setup does not allow the current user to
start an instance. If Extended Security is enabled, the user needs to
be in the DB2ADMNS group.
4. To start the instance, read permission is required to the
/etc/services file.
5. The appropriate authority is required to validate this instance.
6. The partitioned database environment setting is not correct.
7. The instance failed to start because of system errors.
8. An unexpected internal error occurred.

User response:

1. Set the DB2INSTDEF profile registry variable to an instance in the
DB2 copy.
2. Run the db2iupdt or db2nrupdt command with the -k option for the
instance.
3. Add the current user to the DB2ADMNS group and rerun the command.
4. Ensure you have read permission to the /etc/services file.
5. For authorization details, see the db2val command in the DB2
Information Center. Then log on as a user with the appropriate
authority, and retry the command.
6. Check the partitioned database environment validation log file for
details.
7. Check the log file for details.
8. Rerun the db2val command. If this error persists, contact your IBM
service representative.

DBI1382W The database manager of the instance DB2 cannot
be stopped.

Explanation:

The database might still be in use.

User response:

To stop the database manager, run the db2stop command.

DBI1344E The validation tasks of the db2val command failed. For
details, see the log file C:\Users\Scott\DOCUME~1\DB2LOG\db2val-Mon Dec 03
09_33_47 2012.log.


As far as the user responses, I checked #1. Running DB2IUPDT (response #2) completes successfully, but doesn't fix the error. I'm not sure how to add a user to DB2ADMNS (#3), but since I didn't install with operating system security, I don't think this should be necessary. I'm not sure how to perform responses 4 through 7, for one thing because I don't know where the files in question are located.

I've tried the obvious things, like rebooting, uninstalling and reinstalling, and so on. One additional wrinkle is that, after the first couple of installs, the installer now hangs at the very end and has to be killed with Task Manager (after which the report/finish screen comes up), though the installation appears to have been successful.

Other details: I used all the defaults except that I added the two optional components, I used the local administrator account as the user account, and I didn't use operating system security. (I think there was one more non-default setting, but I can't remember it right now.) Also, the first time I installed, I also installed Data Studio and the text search add-on before running DB2VAL.

This is driving me nuts--I'm trying to learn SQL and can't even get started. :) I would really appreciate any help.
Updated on 2012-12-05T02:58:35Z at 2012-12-05T02:58:35Z by SystemAdmin
  • nivanov1
    nivanov1
    53 Posts
    ACCEPTED ANSWER

    Re: DB2 Express-C 10.1 Failed Instance Validation: Reason Code=7

    ‏2012-12-03T19:34:13Z  in response to SystemAdmin
    As the explanation for reason code 7 says, "The instance failed to start because of system errors."

    The file db2diag.log can be found in C:\ProgramData\IBM\DB2\DB2COPY1\DB2. The messages will also appear in the Windows Event Log.
    • SystemAdmin
      SystemAdmin
      5837 Posts
      ACCEPTED ANSWER

      Re: DB2 Express-C 10.1 Failed Instance Validation: Reason Code=7

      ‏2012-12-03T19:57:36Z  in response to nivanov1
      Yeah, I got that, but "system errors" is right up there with "general car fault" as a useful descriptor. Thank you for the pointer to the log file.

      I've attached a log file below--it's showing library load errors, an "'Unexpected System Error'", and "a service-specific error code". I don't think I have the knowledge really to make sense of that.

      I'm going to try one more thing, though.
      • SystemAdmin
        SystemAdmin
        5837 Posts
        ACCEPTED ANSWER

        Re: DB2 Express-C 10.1 Failed Instance Validation: Reason Code=7

        ‏2012-12-03T23:21:18Z  in response to SystemAdmin
        I thought I'd try the 32-bit version, just to see what happens, and I get he same result, including the fact that the install hangs at the very end (which is really odd, since it didn't do that the first couple of times, with the 64-bit version at least).
        • nivanov1
          nivanov1
          53 Posts
          ACCEPTED ANSWER

          Re: DB2 Express-C 10.1 Failed Instance Validation: Reason Code=7

          ‏2012-12-04T14:08:53Z  in response to SystemAdmin
          See if this helps: http://www.ibm.com/developerworks/forums/thread.jspa?threadID=428379
          • nivanov1
            nivanov1
            53 Posts
            ACCEPTED ANSWER

            Re: DB2 Express-C 10.1 Failed Instance Validation: Reason Code=7

            ‏2012-12-04T14:11:28Z  in response to nivanov1
            Or this: http://www-01.ibm.com/support/docview.wss?uid=swg1IC79229
          • SystemAdmin
            SystemAdmin
            5837 Posts
            ACCEPTED ANSWER

            Re: DB2 Express-C 10.1 Failed Instance Validation: Reason Code=7

            ‏2012-12-05T02:58:35Z  in response to nivanov1
            Yes, that first link did the trick. Thanks! Apparently it didn't add the PATH entries for the GSK library directories. My guess is the installation was hanging because it hadn't written the PATH entries and was trying to create the SAMPLE database and couldn't (I had to do this manually--isn't it supposed to be part of installation?), or else it didn't write the PATH entries because it hung, though neither of those explains why it didn't hang the first time or two. At any rate, I've got it working now, so thanks again.