![\"CaptureReplay002\"](\"https://www.dbi-services.com/blog/wp-content/uploads/sites/2/2022/04/CaptureReplay002.jpg\")
.
\nI have several customers that have cases where Real Application Testing can be interesting, but they don’t use it because it’s an expensive option. Which is why it’s probably the topic listed for OCM 12c exam where I’ve the less experience. And I don’t even know at which level (CDB or PDB) it has to be run in multitenant. So I’ve tested it and came to a surprise.
\n
\nIn Enterprise Manager, when you select Database Replay from a PDB:
It seems that you go back at CDB level:
\n![\"CaptureReplay003\"](\"https://www.dbi-services.com/blog/wp-content/uploads/sites/2/2022/04/CaptureReplay003.jpg\")
From there I’ve run a small capture, using the most simple and the default settings from the OEM wizard, and got a capture that has no reference to the PDB:
\n![\"CaptureReplay004\"](\"https://www.dbi-services.com/blog/wp-content/uploads/sites/2/2022/04/CaptureReplay004.jpg\")
Don’t hesitate to comment here because that looks strange for me that I cannot capture at PDB level.
\nSo while the capture was running, I’ve created the SCOTT schema with utlsampl.sql and I’ve raised all salaries in EMP.
\nNow, to replay in the same state, I’ve re-created the SCOTT schema.
And once again, using all defaults in OEM wizard. But the replay had 2 errors:
\n![\"CaptureReplayError\"](\"https://www.dbi-services.com/blog/wp-content/uploads/sites/2/2022/04/CaptureReplayError.jpg\")
There’s probably a way to see the statements, but first I check the error messages:
\n\n[oracle@VM111 ~]$ oerr ora 01918\n01918, 00000, \"user '%s' does not exist\"\n// *Cause: User does not exist in the system.\n// *Action: Verify the user name is correct.\n[oracle@VM111 ~]$ oerr ora 65049\n65049, 00000, \"creation of local user or role is not allowed in CDB$ROOT\"\n// *Cause: An attempt was made to create a local user or role in CDB$ROOT.\n// *Action: If trying to create a common user or role, specify CONTAINER=ALL.\n//\nAs I know that the capture, running utlsampl.sql, did DROP USER SCOTT and then CREATE USER SCOTT, I can imagine that the replay was running on the CDB$ROOT.
\nI did the replay again, and the reason is clear. Because I’m at CDB level de defaut connection string for replay clients connects to the CDB$ROOT:
\n![\"CaptureReplayErrorCDB\"](\"https://www.dbi-services.com/blog/wp-content/uploads/sites/2/2022/04/CaptureReplayErrorCDB.jpg\")
Let’s change it to PDB service name:
\n![\"CaptureReplayErrorPDB\"](\"https://www.dbi-services.com/blog/wp-content/uploads/sites/2/2022/04/CaptureReplayErrorPDB.jpg\")
There I thought that the workload replay client had to connect to PDB but:
\n\noracle@VM111 ~]$ wrc system/oracle@//vm111/PDB replaydir=/tmp/replay\n \nWorkload Replay Client: Release 12.1.0.2.0 - Production on Sun Dec 20 14:55:02 2015\n \nCopyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.\n \n(wrc_main_6062.trc) ORA-15554: cannot start workload replay client because the database server is not in PREPARE mode\nthen I connect to the CDB$ROOT and everything is ok:
\n\n[oracle@VM111 ~]$ wrc system/oracle replaydir=/tmp/replay\n \nWorkload Replay Client: Release 12.1.0.2.0 - Production on Sun Dec 20 14:55:17 2015\n \nCopyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.\n \nWait for the replay to start (14:55:17)\nReplay client 1 started (14:55:39)\nWith this configuration, the replay had no errors: SCOTT recreated and salaries updated.
\nMy conclusion here is that everything about RAT is done at CDB level (but you can filter to capture only what happens on one PDB).
\n", "protected": false } }