Real Application Testing between Solaris SPARC and Exadata
Hi,
I have an issue where a customer has a legacy database 11.2.0.3 running over Solaris SPARC 10. They captured the production workload with RAT, the replayed it over a new Exadata Cloud at customer Gen2. So far so good, but there is something that I don't know who to explain to them.
When replaying, their application (Peoplesoft) has locking issues related with how PSFT handles versioning (using select ... for update over a table). This issue never showed up when replaying with RAT, just showed up once migration was done, and the Exadata was live.
I think this is because the newer system is a lot faster than the old one so this causes a border situation? Any ideas?