If you have enough space, I would suggest copying all the production data for testing. It will be much easier to administer, it may also be a good opportunity to test your backup (restore from backup to a new instance).
From a developer's point of view, you cannot verify the health of your application without a representative dataset. This data set must have the same properties as the production data (data volume, physical distribution ...). The easiest way to achieve this is to have the same data in the test as in production.
If you can afford downtime, you can stop db production, copy the file to the test server and install both databases. If you can't afford downtime, it might be a good idea to upgrade some of your DBA skills (and, ultimately, learn about hot backups and then restore it to a new instance).
Update: if physical copying of the database is not possible, you should view bulk copies of the data using expdp and impdp (or the old exp / imp ). You can either copy all the schemes or filter the data during export . In this case, you would choose the appropriate WHERE clause. Export and import in bulk will be an order of magnitude faster than copying data line by line.
source share