New answers tagged db2
I don't know of a way to trace all the plans the optimizer considers. Obviously the EXPLAIN statement gives you the plan the optimizer eventually selects (and the re-written statement), but that doesn't tell you anything about the ones it doesn't select. One way to get a little more info might be to set CURRENT QUERY OPTIMIZATION to different values (the ...
The DB2 for LUW reference does have a section under high availability entitled "Scenario: Changing the system clock" which goes through the implication of moving the system clock forwards or backwards. It is specifically to do with HADR (high availability), but it's worth a look anyway (it's also worth noting that it's talking about moving the clock back ...
That's an extremeley broad question. If your DB's tables use date in the primary keys you could run into duplicate problems. If you query by date range you may have duplicates or holes in your data. You may even have difficulty saying which row was written before another, depending on your design. Reproducing any previous state may become impossible e.g. ...
You'd need to use the UCA (Unicode Collating Algorithm): the COLLATE value would be something like UCA500R1_LPO_CU for Polish and uppercase first. More info here. Note that you cannot change the collating setting of an existing database; you would have to create a new one with the required collation and move your data.
The collate is responsible for the sorting order. See http://www-01.ibm.com/support/knowledgecenter/SSEPGG_9.7.0/com.ibm.db2.luw.admin.nls.doc/doc/c0006812.html for some explanation. Unfortunately, I can't tell you what other sort order you need to choose for polish letters. IBM might know.
db2pd requires Administrator authority on Windows, in the command shell you are executing it. Setting your ID as a member of the Administrators group on the local machine is not sufficient. IBM adds "DB2 Command Window - Administrator" in your Start Menu to give you a DB2 Command Window that has administrator privileges (which is the recommended method). ...
Assuming you have a newer version of DB2 (10.1 or higher, although I want to say a few of these are in 9.7). You have the Monitor views and functions. The MON_CURRENT_SQL view and the MON_GET_ACTIVITY table function look like they could possibly be what you are after.
I'm an open sorcerer and cannot afford MS license fees for SQL Enterprise Edition, which Change Data Capture requires. I developed yact on github that uses simple SQL triggers to store the 5Ws (who, when, where, why and what). It stores before and after images of data as XML.
Whoever told you "When rolling forward to end of logs without specifying overflow log path only active logs will be read" was wrong. When you have LOGARCHMETH1 set to DISK, TSM, USEREXIT or VENDOR, the DB2 log manager EDU (db2logmgr) is responsible for moving log files to and from the archive location. When performing a ROLLFORWARD operation, DB2 will ...
If you archive logs to a location different from the active log directory (logpath database configuration parameter), you need to specify the clause overflow log path /path/to/archived/logs. The ROLLFORWARD command does not do it automatically. PS. You really should start reading manuals -- they are full of useful stuff, including multiple examples...
Yes, you can issue ROLLFORWARD after restoring an offline backup. The ROLLFORWARD command syntax remains the same, regardless of the type of restored backup image.
Top 50 recent answers are included