Getting Started with IBM Data Studio for DB2

More documents

Recommendations

Info

154 Getting Started with IBM Data Studio for DB2 From the Monitor tab of Task Launcher, if you select any one of the view health summary, view alerts list, view application connections or view table space storage usage monitoring tasks, the corresponding page opens in the Data Studio web console Monitor view. From the Administration Explorer, right-click a database and explore the monitoring options. The same Monitor menu is available from the View menu in the Administration Explorer. Figure 4.20 – The embedded Data Studio web console interfaces. 4.10 Exercises In this section, you will create a variety of error scenarios so that you can get a better understanding of how this product works, and how you can take advantage of its features. For the purposes of this exercise, we recommend that you use the GSDB sample database as your test database. For more information on how to install the GSDB database, see Chapter 1. To keep this exercise simple, you will create these error scenarios in a controlled manner, and you will use lower thresholds to quickly cause situations that will be flagged as alerts. This section includes scenarios for the following alert types: • Database Availability: This generates a data server status alert.
• Connections: This generates a connections alert. • Table Space Quiesced: This generates a storage alert. 4.10.1 Adjust the monitoring frequency Chapter 4 – Monitoring the health of your databases 155 First, navigate to the Health Alerts Configuration page in the Data Studio web console and select a database. You will see the default refresh value is 10 minutes, which means that the monitoring of this database will happen every 10 minutes. For this exercise, change this value to 1 minute, so you will not have to wait as long to see the alerts being generated. 4.10.2 Adjust the page refresh rates Navigate to the Health Summary page, and find the option to change refresh intervals. Click the down arrow next to the Recent xx minutes label. A window opens that lets you change how often the Health Summary pages will auto-refresh itself to display recently found alerts. The default is set to 5 minutes. For this exercise, change it to 1 minute to minimize testing wait times. 4.10.3 Database availability The Database Availability Alert checks the following status types for a database: Normal, Quiesce Pending, Quiesced, Rollforward, and Unreachable. By default, a warning alert is generated if the database is in Quiesce Pending or Rollforward state. A critical alert is generated if the database is in Quiesced or Unreachable state. The following error scenario will put the database in Quiesced state, so that a critical alert will be generated. 1. Open a DB2 command window. 2. Connect to the database with the following command: db2 connect to GSDB user db2admin using db2admin 3. Quiesce the database with the following command: db2 quiesce db immediate 4. Navigate to the Health Summary page. Wait for one minute to see the Data Server Status change from Normal (green) status to Critical (red) status. The Critical Count should also now be raised by 1. Click the Critical Status icon, or the Critical Count Number, to get more information on the alert. 4.10.4 Updating the alert configuration In this section, follow these steps to generate a warning for a database in Quiesced state, instead of the currently defined critical alert. 1. Navigate to the Health Alerts Configuration page. 2. Select the database that is in Quiesced state.
Page 1 and 2:
]
Page 3 and 4:
3 Notices This information was deve
Page 5 and 6:
Table of contents 5 Table of conten
Page 7 and 8:
3.3.1 Exporting data...............
Page 9 and 10:
Chapter 7 - Tuning queries ........
Page 11 and 12:
11.4 Community and resources ......
Page 13 and 14:
Preface 13 Keeping your skills curr
Page 15 and 16:
around the world have participated
Page 17 and 18:
17 About the authors Dimple Bhatia
Page 19 and 20:
Contributors 19 The following peopl
Page 21:
21 Acknowledgements The authors owe
Page 24 and 25:
24 Getting Started with IBM Data St
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
100 Getting Started with IBM Data S
Page 103 and 104: 103 Chapter 3 - Maintaining the dat
Page 105 and 106: Chapter 3 - Maintaining the databas
Page 133 and 134: Figure 3.35 - Selecting additional
Page 137: Chapter 3 - Maintaining the databas
Page 140 and 141: 140 Getting Started with IBM Data S
Page 159 and 160: 159 Chapter 5 - Creating SQL and XQ
Page 161 and 162: Chapter 5 - Creating SQL and XQuery
Page 181 and 182: On Success On Error Result Chapter
Page 193 and 194: 193 Chapter 6 - Managing jobs Job m
Page 195 and 196: Chapter 6 - Managing jobs 195 6.3 J
Page 197 and 198: Chapter 6 - Managing jobs 197 6.4 C
Page 199 and 200: Chapter 6 - Managing jobs 199 Figur
Page 201 and 202: Chapter 6 - Managing jobs 201 Comp
Page 203 and 204: Chapter 6 - Managing jobs 203 Figur
Page 205 and 206:
Chapter 6 - Managing jobs 205 Figur
Page 207 and 208:
Chapter 6 - Managing jobs 207 6.5 R
Page 209 and 210:
Chapter 6 - Managing jobs 209 6.6.2
Page 211 and 212:
Chapter 6 - Managing jobs 211 Figur
Page 213 and 214:
213 Chapter 7 - Tuning queries In t
Page 215 and 216:
Chapter 7 - Tuning queries 215 Figu
Page 217 and 218:
Chapter 7 - Tuning queries 217 You
Page 219 and 220:
Chapter 7 - Tuning queries 219 •
Page 221 and 222:
Page 223 and 224:
7.4.2 Run the Statistics Advisor an
Page 225 and 226:
Chapter 7 - Tuning queries 225 7.4.
Page 227 and 228:
Chapter 7 - Tuning queries 227 For
Page 229 and 230:
Page 231 and 232:
Chapter 7 - Tuning queries 231 To s
Page 233 and 234:
Chapter 7 - Tuning queries 233 3. O
Page 235 and 236:
Chapter 7 - Tuning queries 235 7.6
Page 237 and 238:
237 Chapter 8 - Developing SQL stor
Page 239 and 240:
Chapter 8 - Developing SQL stored p
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 298 and 299:
Page 300 and 301:
Page 302 and 303:
Page 304 and 305:
Page 306 and 307:
Page 308 and 309:
Page 310 and 311:
Page 312 and 313:
Page 314 and 315:
Page 316 and 317:
Page 318 and 319:
Page 320 and 321:
Page 322 and 323:
Page 324 and 325:
Page 326 and 327:
Page 328 and 329:
Page 330 and 331:
Page 332 and 333:
Page 334 and 335:
Page 336 and 337:
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 355 and 356:
355 Appendix D - The Sample Outdoor
Page 357 and 358:
Appendix D - The Sample Outdoor Com
Page 359 and 360:
Page 361 and 362:
Page 363 and 364:
Appendix E - Advanced topics for de
Page 365 and 366:
Page 367 and 368:
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Page 389 and 390:
E.5.4 Data web services artifacts A
Page 391 and 392:
References 391 References [1] HAYES
Page 393 and 394:
References 393 Books and articles 1
Page 396:
396 Getting started with IBM Data S
show all

Getting Started with IBM Data Studio for DB2

Create successful ePaper yourself

Delete template?

Save as template?