The developerWorks Connections platform will be sunset on December 31, 2019. On January 1, 2020, this blog will no longer be available. More details available on our FAQ.
All posts
- Sort by:
- Date
- Title
- Likes
- Comments ▼
- Views
Rollforward database command failed with SQL1042C
This blog explains a scenario that caused rollforward failure. The following is the rollforward command that failed: $ db2 "rollforward database DB1 to end of backup ON ALL DBPARTITIONNUMS and complete tablespace (TS1) online" SQL1042C An unexpected system error occurred. SQLSTATE=58004 To diagnose the problem, verify db2daig.log: <timestamp> LEVEL: Warning PID : 12345678 TID : 123456 PROC : db2sysc 0 INSTANCE: db2ins1 NODE : 000 DB : DB1 APPHDL : 0-1234 APPID: *N0.db2ins1.12345678 AUTHID : DB2INS1 HOSTNAME: host11 EDUID :... [More]
Tags: rollforward |
How to monitor LOAD progress and improve its performance?
This Blog explains how you can monitor the progress of your load commands and in case there is a performance concern on the load commands, where you can check the cause of the slowness. 1. Monitor Load Progress You can use db2pd -util command to monitor load progress. For instance, the following output has two load commands ongoing: Database Member 0 -- Active -- Up 6 days 05:15:41 -- Date 2016-12-14-03.31.20.222374 Utilities: Address ... [More]
Tags: load |
DB2LUW: Why db2look failed with sql10004c while connect to the same db succeed?
1. db2look failed with following error: $ db2look -d sample -e -o db2look.ddl -- Generate statistics for all creators -- Creating DDL for table(s) -- Output is sent to file: sample.ddl SQL10004C An I/O error occurred while accessing the database directory. SQLSTATE=58031 2. error in db2diag.log 2017-04-11-02.48.11.615491-240 I38860E2300 LEVEL: Error (OS) PID : 28473 ... [More]
Tags: im_support db2luw |
DB2 v9.7 and v10.1 EOS - Upgrade Recommendation
DB2 v9.7 and v10.1 will be EOS(end of support) on Sep. 30, 2017. Customers can upgrade their DB2 v9.7 or v10.1 systems to DB2 v11.1 FP1 directly to skip 11.1 GA version. The first fix pack delivered for DB2 V11.1 changes the modification level of the product to 1 and has the product signature of DB2 11.1.1.1. Subsequent fix packs for the DB2 V11.1 product will be based on this modification level (e.g. the next fix pack will have the signature DB2 11.1.1.2).
Tags: db2 v9.7 v11.1 v10.1 eos upgrade |
DB2 China Newsletter March Edition |
How to change hostname+ipaddress in purescale environment
I am sharing the experience of how to change hostname+ipaddress in existing purescale environment with db2iupdt -drop/-add options. The current existing environment is as followings: ----------------------------------------------------------------------------------------------------- db2sdin1@ps101:~> db2instance -list ID TYPE STATE ... [More]
Tags: db2support imsupport purescale db2luw |
Why SNAPSTORAGE_PATHS admin view returning "-" against some of the columns and how to fix it
SYSIBMADM.SNAPSTORAGE_PATHS administrative view is not returning values against some of the columns. Instead it's showing "-". Example, $ db2 "select FS_TOTAL_SIZE, FS_USED_SIZE, STO_PATH_FREE_SIZE from sysibmadm.snapstorage_paths" FS_TOTAL_SIZE FS_USED_SIZE STO_PATH_FREE_SIZE -------------------- -------------------- --------------------... [More]
Tags: db2luw db2support snapstorage_paths |
SQL1229N in DPF environment
I am sharing one experience where my client moved DPF environment from 2 physical servers - 16 logical nodes to 1 physical server - 16 logical nodes . They had taken an offline backup of their database before this migration. They managed to restore the backup from old setup to new setup. However any command against this restored database in new setup were failing with SQL1229N error - The current transaction has been rolled back because of a system error. The db2diag.log shows entries as follows: 2017-01-01-18.46.04.749624-360... [More]
|
Pure Data System for Analytics Maintenance tasks for Clients
There are several maintenance tasks that are required to keep your IBM PureData System for Analytics appliance running smoothly. Until now, IBM support has occasionally been engaged to assist in the completion of some of these simpler tasks. IBM has prepared documentation to assist clients in completing these simple tasks independently, without the need to engage IBM support. Effective March 15, 2017 should any of the following tasks be requested, IBM Support will refer clients to appropriate documentation to assist in completion of the task.... [More]
|
Restrictions for online fix pack updates in db2 pureScale environment
1. DB2 pureScale instance must be at the required minimum committed code level when performing an online update . Starting with Version 10.5, a DB2 release has an architecture level and a code level. When you apply an online update, your DB2 pureScale instance must be at the required minimum committed code level. A new fix pack level has a different code level than an earlier fix pack release. However, the architecture level can be the same or different from an earlier fix pack release. Figure 1 shows the architecture level and code level for a... [More]
|
