Blogs >> Technology >>
DB2 Database Corrupt Using Different code pages On Client and Server
DB2 database, although considered a reliable database, can get corrupted due to various reasons, such as, improper server shutdown, virus attack, and creating administrating objects without using characters listed in 7-bit ASCII range. The database records become inaccessible once it gets corrupted due to any of the above reasons. In such cases, an adequate backup acts as a boon and allows the user to access the database records. While in most cases, the user creates a backup of his DB2 database, there might situations, wherein, the user forgets to do so. In these situations, the user can repair his corrupted database using a commercial DB2 Repair software.
To explain the above case, consider a real-time scenario where your client for Windows with Big5 code page = 950 is created on TCH_Windows and DB2 Content Manager Server with code page 1252 is created on German_Windows. Now, if you create a database object on the client machine using Big5 characters, the creation will be successful, but when you try to access that object, it will appear to be blank. Furthermore, all the other objects in the database can not be accessed or deleted after you perform the above operation.
Cause:
You create or update the system administrative objects using characters that are not in the 7-bit ASCII range.
Note: To prevent the corruption of your DB2 database in above scenario, you should always create or update system administrative objects like, run-time objects, users, item types, or ACLs using characters in the 7-bit ASCII range.
Resolution:
To resolve the above issue and to access the database objects, you need to restore all the objects from a valid backup. But if a valid backup of all the database objects is not maintained, then you will need to search for advanced third-party DB2 Database Recovery utility.
A DB2 Recovery software employs intensive scanning techniques to repair corrupt DB2 database post any logical corruption scenario. The tool comes with a detailed documentation that explains the repair procedure in detail.
DB2 Recovery Software is industry's only DB2 Recovery tool that comprehensively repairs
IBM DB2 (UDB) v8 databases. The recovery tool uses powerful, yet safe repairing methods to perform risk-free and complete repair. Designed for Windows 2003, XP, and 2000, the tool recovers almost all DB2 database objects, including tables, triggers, schemas, and views.
To explain the above case, consider a real-time scenario where your client for Windows with Big5 code page = 950 is created on TCH_Windows and DB2 Content Manager Server with code page 1252 is created on German_Windows. Now, if you create a database object on the client machine using Big5 characters, the creation will be successful, but when you try to access that object, it will appear to be blank. Furthermore, all the other objects in the database can not be accessed or deleted after you perform the above operation.
Cause:
You create or update the system administrative objects using characters that are not in the 7-bit ASCII range.
Note: To prevent the corruption of your DB2 database in above scenario, you should always create or update system administrative objects like, run-time objects, users, item types, or ACLs using characters in the 7-bit ASCII range.
Resolution:
To resolve the above issue and to access the database objects, you need to restore all the objects from a valid backup. But if a valid backup of all the database objects is not maintained, then you will need to search for advanced third-party DB2 Database Recovery utility.
A DB2 Recovery software employs intensive scanning techniques to repair corrupt DB2 database post any logical corruption scenario. The tool comes with a detailed documentation that explains the repair procedure in detail.
DB2 Recovery Software is industry's only DB2 Recovery tool that comprehensively repairs
IBM DB2 (UDB) v8 databases. The recovery tool uses powerful, yet safe repairing methods to perform risk-free and complete repair. Designed for Windows 2003, XP, and 2000, the tool recovers almost all DB2 database objects, including tables, triggers, schemas, and views.
|
|
