That feeling you have brand new version. Very common setup, after install steps. And surprise!! db2val is yelling „discrepancies found“! 🙂
DB2 is distributed with a very useful utility called db2val – it checks and validate installed DB2 files + proper setup of instance.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 |
[db2inst1@ol67 ~]$ db2val DBI1379I The db2val command is running. This can take several minutes. DBI1335I Installation file validation for the DB2 copy installed at /opt/ibm/db2/V10.5 was successful. DBI1338E The validation of instance db2inst1 failed. Reason code=3. 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. 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. Related information: db2val - DB2 copy validation tool command DBI1344E The validation tasks of the db2val command failed. For details, see the log file /tmp/db2val-150823_181041.log. |
Ok, there are just 2 steps to correct „something“:
A) db2iupdt can a bit tricky one = run only as a root and be sure that affected instance is down.
B) location of db2iupdt is instance directory withing DB2 home:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 |
[root@ol67 j]# cd /opt/ibm/db2/V10.5/instance root@ol67 instance]# ./db2iupdt -k db2inst1 DBI1446I The db2iupdt command is running. DB2 installation is being initialized. Total number of tasks to be performed: 4 Total estimated time for all tasks to be performed: 309 second(s) Task #1 start Description: Setting default global profile registry variables Estimated time 1 second(s) Task #1 end Task #2 start Description: Initializing instance list Estimated time 5 second(s) Task #2 end Task #3 start Description: Configuring DB2 instances Estimated time 300 second(s) Task #3 end Task #4 start Description: Updating global profile registry Estimated time 3 second(s) Task #4 end The execution completed successfully. For more information see the DB2 installation log at "/tmp/db2iupdt.log.6011". DBI1070I Program db2iupdt completed successfully. [root@ol67 instance]# pwd /opt/ibm/db2/V10.5/instance [root@ol67 instance]# su - db2inst1 [db2inst1@ol67 ~]$ db2val DBI1379I The db2val command is running. This can take several minutes. DBI1335I Installation file validation for the DB2 copy installed at /opt/ibm/db2/V10.5 was successful. DBI1339I The instance validation for the instance db2inst1 was successful. DBI1343I The db2val command completed successfully. For details, see the log file /tmp/db2val-150823_185427.log. [db2inst1@ol67 ~]$ |
All done.
-a-