If you can't see those via mminfo - they don't exist. Period. I can't comment how it is done nor why it is done the way it is done, but I think you should get a grip of the things as new responsible person and breath in some fresh air. You already started by using your own script to run cloning.
Now, if you purge 5 days older backups and you do cloning on weekly basis - something will be missed for sure. Unless those 5 days are RMAN catalog only, but why would you remove that if you keep data for 1 year in clone pool? Anyway, I assume Oracle client saved data under same name (or used consistently same NSR_CLIENT value) so mminfo -avot -r ssid,pool,savetime | grep -i <oracleserver hostname> should give you data in date order. If it is missing, stop looking for it - it's not there. You can also verify this by checking logs. Obviously someone before you forgot to do that. Those logs should tell you if data was not cloned and most likely why too.
ble1
4 Operator
•
14.4K Posts
0
February 19th, 2014 03:00
If you can't see those via mminfo - they don't exist. Period. I can't comment how it is done nor why it is done the way it is done, but I think you should get a grip of the things as new responsible person and breath in some fresh air. You already started by using your own script to run cloning.
Now, if you purge 5 days older backups and you do cloning on weekly basis - something will be missed for sure. Unless those 5 days are RMAN catalog only, but why would you remove that if you keep data for 1 year in clone pool? Anyway, I assume Oracle client saved data under same name (or used consistently same NSR_CLIENT value) so mminfo -avot -r ssid,pool,savetime | grep -i <oracleserver hostname> should give you data in date order. If it is missing, stop looking for it - it's not there. You can also verify this by checking logs. Obviously someone before you forgot to do that. Those logs should tell you if data was not cloned and most likely why too.