Could you please tell me how you understand the last sentence of the following paragraph. Please read it more than once and analyze the exacte meaning of each word:
You can skip all tablespaces in the target database except the SYSTEM tablespace, undo tablespaces, and tablespaces containing rollback segments. RMAN does not check for completeness. For example, you can duplicate a data tablespace but not the tablespace containing the index for the data, or duplicate a tablespace that contains only one partition of a partitioned table.
1) Tablespace DATA_ONLY_TBSP has tables only, ( this has no problem to duplicate)
2) Tablespace INDEX_ONLY_TBSP has only indexes of somes tables residing on other tablespace which are not being duplicated , then this is not qualified.
3) Tablespace INDEX_DATA_TBSP has indexes and tables residing on the same tablespace, then this has no problem.
4) Tablespace PART_A_TBSP , this has one of the partitions of a table which is not being duplicated, this cannot be duplicated.
I guess these concepts are closely matching with Transportable tablespaces feature.
Everytime I have duplicated a database using rman, I have duplicated the whole database. In fact, I did not know you could use rman to duplicate part of a database. But it would make sense the the duplicated database must have a complete data dictionary. But it seems that you can duplicate a database without duplicated the indexes if they are in their own tablespace, or it seems that you can duplicates one or more partitions in a partitioned table if the ones skipped are in their own tablespaces.
So unless you are doing an incomplete duplication of a database, this section doesn't matter. IMHO, doing a complete duplication of a database from a backup should be a simple thing to do.
I think that is the important point.
I agree with Gandolf's reading: RMAN duplicates whole tablespaces without worrying about the relationship of the contents.
The sentence you hightlighted just gives two examples, rather badly stated, joined by the OR. I think it is the "can . . . but not" structure that make it look like somthing is forbidden! What they mean is that it is permitted to do one without the other (tables without indexes).
I'd rewrite that sentence as:
For example, you can duplicate a data tablespace and not have to duplicate the tablespace containing the index for the data. You can duplicate a tablespace that contains only one partition of a partitioned table.
Re: Re: How do you understand this Oracle Documentation
Originally posted by gandolf989 ... So unless you are doing an incomplete duplication of a database, this section doesn't matter. IMHO, doing a complete duplication of a database from a backup should be a simple thing to do.
The problem is that our DWH DB has a size of 2.6 TB. To have accurate data on our integration DB we would like to duplicate only the tablespaces containing the most recent data.
The problem is that Oracle has different people write different chapters in these docs and some have a better grip on the language then others.
Notwithstanding, there should be some type of audit in place for some consistency.
No speka di engleesh.
There is a lot to be said for keeping things simple, although some (and you know who you are) would disagree.
Originally posted by mike9 And how does Mr.Hanky understand this sentence? What do they mean with this NOT and OR ?
Me, hell anyone in here will tell you I am a Neanderthal.
Anyhow, the problem is that the “OR” can be bound to interpretation two ways. It is either referring to the fact that you can or can not from the previous sentence.
Clear as mud, as we like to say.
I have read enough Oracle docs to have encountered this type of thing before. There are many a passage that need to be read and re-read over and over until the least common denominator is finally extrapolated. Personally, I feel this is bad documenting.
I threw in a couple of SAT words for Dave, how’d I do?
But this sentence doesnt seem confusing to me. It says RMAN Does not check for completeness when duplicates and gives two possible scenarios (here is the OR)
1. You can duplicate a data tablespace but you dont necessary (you can skip them) need to duplicate the associated indexes if they reside in other tablespaces (here is the BUT NOT)
2. You can duplicate a tablespace containing a single partition, this would be the case where you have a tablespace for a partition