Contents:- Database
Replay Concept , Practical
Requirement
For System changes such
as hardware/software upgrades, Patch application etc need to spend time and
efforts to testing the system changes in test environment before introducing
them into production. Then also after that much changes, many issue often go
undetected until production deployment and negatively impact system performance
and availability.
Problem:- Testing is
done appropriate because of inability of existing tools to test using real
production workloads.
Concept
The database replay
feature(of 11g) allows database workload to be captured on one system and
replayed later on different system.
Database replay is
mainly used to test any system change according to production workload before
deployment it to production.
Replaying Capture
workload can be useful to compare two different systems.
There are 3 Steps to
replay captured workloads on another system
i) Capture
Workload:- This option is used to capture
workload on this database. (Capture files are created during this process)
ii) Preprocess
Captured Workload :- Preprocessing will
prepare a captured workload for replay. (During preprocess creates necessary metadata
needed to database replay)
iii)
Replay
Workload:- This
option is used to replay a preprocessed workload on this system.
iv)
Analysis and
Reporting:- Reports are
provided to enable detailed analysis of the capture and replay.
The primary purpose
of Database Replay is to test the effect
of system changes on a real captured application workload.
Database Replay, is one
of the solution within the oracle real application testing enables realistic
system changes by re-creating the production workload on the test system.
Usages
è Database upgrade.
è Configuration change such as conversion from
single instance to RAC
è Hardware Changes.
No comments:
Post a Comment