We have a process that does bulk inserts into a table in our production enviroment to a table, this table is also subject to mass deletes, we will call it table X
Now for development we take the RMAN backup and restore it into a different enviroment, we run the same bulk inserts and the time it takes to run the job is about 1/3 the time. The enviroments are identical. So I am thinking that table X in production when doing the insert is being scanned to try to utilize the empty space given back to the table by the mass deletes. And if this is true then the only thing that would be logical is that when RMAN restores the entire DB the rows are written without these 'holes' of empty space so it simply just appends it to the end of the table causing a much quicker insert
Am I right in my logic here?