|Product:||All DB Connectivity Products|
|Summary:||How to drop corrupted Db2 packages and create new ones|
Sometimes errors can be caused by a corrupted Db2 package. To verify whether the problem you are experiencing is caused by a corrupted package, disable the package first and see if this corrects the problem.
If the connection is made using an OLE DB data link, a .NET data source or an ODBC DSN, disable packages by unchecking the "Use Packages" check box on the Performance tab of the configuration dialog in the Toolbox. If you are connecting with an OLE DB or a .NET connection string, you can add the string "Use Packages=False;". If the problem goes away when the package is disabled, the package or packages are corrupted. In this case, you will need to remove the corrupted packages first and then enable the use of packages again before creating new ones.
- Remove all packages created by the ODBC driver, OLE DB provider or .NET provider.
Ritmo/i package names are RITMOPKGx (where x is a digit from 0 to 4.)
For ODBC and OLE DB products, you can customize package names. If not customized, the default names are prefixed by HS, then some characters from the calling application and a final digit 0 to 4, e.g., HSSQLSERV0 for SQL Server or HSEXCEL0 for MS Excel. The digit depends on the isolation level used:
NC No Commit 0 -> Default Value
RS Read Stability 1
UR Uncommitted read 2
CS Cursor Stability 3
RR Repeatable Read 4
- Enable the use of packages via the data link/DSN/data source configuration windows or by removing the string "Use Packages=False;" from the connection string.
This way, new package(s) will be created automatically when you make a connection again.