Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
db2look fails after fixpack install
464 views
Skip to first unread message
frit...@gmail.com
Jan 26, 2013, 3:58:58 PM1/26/13
to
Just applied fix pack 2 on db2 version 10 partitioned environment and now db2look doesn't work. It fails with this error:
SQL0206N "A.TYPERULES" is not valid in the context where it is used.
SQLSTATE=42703
It appears that the fixpack install did not update the schema. I did do db2iupdt on the instance owning server. The one thing that seems fishy is that the log for the install of the fixpack said that it was not upgrading the instance since it was not the "instance owning server" -- (when it actually was the instance owning server).
I'd think that manually running db2iupdt for the instance would take care of this, but it didn't seem to. Any help would be appreciated.
Greig Wise
SQL0206N "A.TYPERULES" is not valid in the context where it is used.
SQLSTATE=42703
It appears that the fixpack install did not update the schema. I did do db2iupdt on the instance owning server. The one thing that seems fishy is that the log for the install of the fixpack said that it was not upgrading the instance since it was not the "instance owning server" -- (when it actually was the instance owning server).
I'd think that manually running db2iupdt for the instance would take care of this, but it didn't seem to. Any help would be appreciated.
Greig Wise
Helmut Tessarek
Jan 26, 2013, 5:51:28 PM1/26/13
to
On 26.01.13 15:58 , frit...@gmail.com wrote:
> It appears that the fixpack install did not update the schema. I did do
> db2iupdt on the instance owning server. The one thing that seems fishy is
> that the log for the install of the fixpack said that it was not upgrading
> the instance since it was not the "instance owning server" -- (when it
> actually was the instance owning server).
After a fixpak install you are supposed to bind the following packages and run
> It appears that the fixpack install did not update the schema. I did do
> db2iupdt on the instance owning server. The one thing that seems fishy is
> that the log for the install of the fixpack said that it was not upgrading
> the instance since it was not the "instance owning server" -- (when it
> actually was the instance owning server).
db2updv10:
BIND ~/sqllib/bnd/@db2ubind.lst GRANT PUBLIC BLOCKING ALL
BIND ~/sqllib/bnd/@db2cli.lst GRANT PUBLIC BLOCKING ALL
BIND ~/sqllib/bnd/db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue
db2updv10 -d <dbname>
--
Helmut K. C. Tessarek
DB2 Performance and Development
IBM Toronto Lab
shashank...@gmail.com
Jul 24, 2013, 9:43:35 PM7/24/13
to
Yes, db2updv10 -d <DBNAME> should resolve this.
Due to the catalog tables not being updated to the latest fixpack.
We are missing a column in the system catalog views introduced in DB2 V10.1
Fixpack 2.
- Shashank Kharche
Due to the catalog tables not being updated to the latest fixpack.
We are missing a column in the system catalog views introduced in DB2 V10.1
Fixpack 2.
- Shashank Kharche
0 new messages