We installed UDB 8.2 FixPak 7a on the client machine (the Web server), which
solved the problem. The steps we went through included rolling back .NET
Framework 1.1 SP 1, which eliminated the problem. We reinstalled .NET
Framework 1.1 SP 1, which caused the problem again. Finally, we installed
DB2 8.2 FixPak 7a, which eliminated the problem again.
The moral of the story appears to be that if you're using an
OleDbDataAdapter to talk to a DB2 database, you should apply both .NET
Framework 1.1 SP1 and DB2 8.2 FixPak 7a at the same time to avoid
DB_E_OBJECTOPEN errors
Bind db2schema.bnd to existing databases
After installation on the server, an additional bind file needs to be
bound to existing databases. This requirement does not apply to clients.
Procedure
To bind db2schema.bnd on the server, execute one of these command
sequences:
At a command prompt:
db2 terminate
db2 CONNECT TO <dbname>
db2 BIND <path>/db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue
db2 terminate
或者做以下操作
At the DB2 command line:
TERMINATE
CONNECT TO <dbname>
BIND <path>/db2schema.bnd BLOCKING ALL GRANT PUBLIC sqlerror continue
TERMINATE
where <dbname> represents the name of a database to which the utilities
should be bound, and where <path> is the full path name of the directory
where the bind files are located.