One of the options for cloning an environment with limited disk space involves creating a parameters file for the RMAN clone memory script to run that contains the “skip tablespace” feature. This allows the DBA to retain a working list of tablespaces that contain data that isn’t required in development/test or for other cloning purposes when performing the actual clone. startup auxiliary nomount; run { allocate auxiliary channel c1 device type disk; …so on and so forth for all the channels desired… duplicate target database to SKIP TABLESPACE USERS,TBL_DATA1,TBL_INDX1,….; } This can also be extremely helpful in environments where disk…
-
-
This question seems to pop into my mind consistently over the years as a DBA. I’m a “build it right or don’t build it at all” kind of DBA, but due to my gift for finding problems and fixing them, I find myself more and more often performing the second build on processes/procedures/designs, which I often would like to avoid. I went through this repeatedly at a previous shop and it’s still fresh in my mind, even today… Don’t get me wrong- I think it’s a noble cause when you first come into a new shop and it’s either been neglected or didn’t…