Our test database got the same database schema as the production database.I'd like to have following features:DQL statements should go to the test database. If there's no result, the statement runs on the production environment and returns the result to the test database.DML statements should only work on the test database.If I run update tablename set ... where ...; and the statement finds the result on the production database, the result should return to the test database and insert the updated result into the test database.I think it's called snapshot cloning and is only available for oracle db 12c.Since we've got version 22.214.171.124, is it possible to build up these features manually, e.g. with triggers and views?
why not just refresh development daily with a datapump?
permisssions, roles, tables, constraints, views are the same.
You got a point i didn't think about. If there's an update from PROD on a tuple which is also given on TEST, then we get inconsistency. Also processes could be triggered on PROD while on TEST they wouldn't, because of the data state. So I've got to make a snapshot first. Thank you :)