Data Server Manager (DSM) showing SQLCODE=-206 "<name> is not valid in the context where it is used."
Data Server Manager log files are full of SQLCODE=-206 "<name> is not valid in the context where it
is used." error
The symptoms can vary depending on each installation.
Most common scenario, DSM shows Data Pending status for the monitored database.
When you apply a new DB2 fixpack, the db2iupdt command is used to update an instance to a higher level within a release.
But that command does not necessarily update the database system catalog to support the new fix pack that you have installed.
Meaning, just because the db2level shows a higher level, your database can still be using routines from an older DB2 level.
Diagnosing the problem
One way to verify what routine levels your database is using, you can run the following DB2 command on the monitored database:
db2 "select versionnumber from sysibm.sysversions order by 1 desc"
If the results is showing a lower level than the ones DSM supports, that means your environment
is not supported, and you are getting the SQLCODE=-206 error.
To verify what are the DB2 levels supported by DSM, please refer to the links below:
- System requirements for IBM Data Server Manager, version 1.1.2
- System requirements for IBM Data Server Manager, version 2.1
Resolving the problem
Run the db2updvnn command according to the db2level of your monitored database:
More support for:
IBM Data Server Manager
Software version: 1.1, 1.1.1, 1.1.2, 2.1, 2.1.1, 2.1.2, 2.1.3, 2.1.4
Operating system(s): AIX, Linux, Windows
Software edition: All Editions
Reference #: 1983739
Modified date: 11 September 2017