|
by Sushma Jagannath
A sound database backup and recovery plan is crucial to protecting data in the event of media loss and physical corruption on production storage systems. Oracle backup and recovery technologies enable data to be recovered from media loss and corruption, as well as from logical errors at the row, table, and database level. This article discusses some of the new backup and recovery features in Oracle Database 11g that improve the manageability of Oracle Database backup and recovery. It also presents sample questions of the type you may encounter when taking the Oracle Database 11g: New Features for Administrators exam, which enables Oracle Certified Professionals (OCPs) certified on Oracle Database 10g to upgrade their certifications to Oracle Database 11g. >Read full article
by Robert Catterall
When I first started working with DB2 on the mainframe platform, back in the mid-1980s, plenty of people were still running a version of the operating system called MVS/370. That OS limited the size of an address space to 16 MB, and the amount that a subsystem such as DB2 actually had to work with was less than that, since some megabytes were occupied by system code and by common storage areas (i.e., areas of virtual storage that were shared across address spaces). Since server memory was tight, people were frugal in their use of it. Early on, it was common to find organizations running DB2 in production with a total buffer pool configuration of 1000 4K buffers (4 MB of virtual storage) — often allocated to a single pool, BP0. >Read full article
by Steven Haines
The best way to avoid performance problems in Java applications is to adopt formal performance testing strategies. This paper presents an overview of CPM and its test-driven development with continuous integration heritage. It then goes on to outline the steps a developer should take from within the context of the Eclipse Java IDE to automatically profile all test cases and analyze the results before checking code into a source code repository. While developing an application, the most advanced performance testing strategy available is Continuous Performance Management (CPM). CPM emphasizes automated performance testing of all test cases every time a developer checks code into a source code repository. >Read full article
by Tom Mochal
A Testing Plan is used to describe your specific approach and the details regarding the testing of your solution. There are literally dozens of tests that can be performed on a project. If you have a large, complex project, you may need to use quite a few of the tests. However, all of the tests will not be applicable to all projects. The Testing Plan is where you define the types of tests that will be performed, what the test scenarios look like, what the expected results are, how you will track errors, who will test, where will the testing will take place, etc. >Read full article
|