|
Problem IC67080
|
Status: Closed |
DB2SET FAILS WITH ERROR: DBI1306N THE INSTANCE PROFILE IS NOT DEFINED. |
| product: |
DB2 FOR LUW / DB2FORLUW / 970 - DB2 |
| Problem description: |
db2set throws the following error:
$ db2set db2_workload=sap
DBI1306N The instance profile is not defined.
Explanation:
The instance is not defined in the target machine registry.
User response:
Specify an existing instance name or create the required
instance.
This problem can be caused by a dirty record in the DB2 global
registry.
You can list the content of the DB2 global registry with this
command: "<DB2DIR>/bin/db2greg -dump"
If, for example, your instance is called "db2inst1" the output
will contain a record like this:
I,DB2,9.7.0.1,db2inst1,/home/db2inst1/sqllib,,1,0,/opt/IBM/v97,,
The error from db2set is triggered because the InstallPath
record (/opt/IBM/v97) is different than the path where your copy
of DB2 is installed. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* db2set throws the following error: *
* *
* *
* *
* $ db2set db2_workload=sap *
* *
* DBI1306N The instance profile is not defined. *
* *
* Explanation: *
* *
* The instance is not defined in the target machine registry. *
* *
* User response: *
* *
* Specify an existing instance name or create the required *
* *
* instance. *
* *
* *
* *
* *
* *
* This problem can be caused by a dirty record in the DB2 *
* global *
* registry. *
* *
* You can list the content of the DB2 global registry with *
* this *
* command: "<DB2DIR>/bin/db2greg -dump" *
* *
* If, for example, your instance is called "db2inst1" the *
* output *
* will contain a record like this: *
* *
* I,DB2,9.7.0.1,db2inst1,/home/db2inst1/sqllib,,1,0,/opt/IBM/v97
* *
* *
* The error from db2set is triggered because the InstallPath *
* *
* record (/opt/IBM/v97) is different than the path where your *
* copy *
* of DB2 is installed. *
* *
* *
* *
* You can fix the issue by running db2iupdt against your *
* instance: *
* <DB2DIR>/instance/db2iupdt <INSTANCE NAME> *
****************************************************************
* RECOMMENDATION: *
* You can fix the issue by running db2iupdt against your *
* instance: *
* <DB2DIR>/instance/db2iupdt <INSTANCE NAME> *
**************************************************************** |
| Local Fix: |
Execute this command as root, where <DB2DIR> is the path where
your DB2 copy is installed:
<DB2DIR>/instance/db2iupdt <INSTANCE NAME> |
| available fix packs: |
DB2 Version 9.7 Fix Pack 2 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 3a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 4 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 5 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 6 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 7 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 8 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9a for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 9 for Linux, UNIX, and Windows
DB2 Version 9.7 Fix Pack 10 for Linux, UNIX, and Windows
|
| Solution |
Problem was first fixed in Version 9.7 Fix Pack 2 |
| Workaround |
not known / see Local fix |
| BUG-Tracking |
forerunner : APAR is sysrouted TO one or more of the following: IC67087
follow-up : |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 10.03.2010
22.04.2010
06.05.2010 |
| Problem solved at the following versions (IBM BugInfos) |
9.7.FP2
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.7.0.2
|
 |
