I'm trying to quickly clone an production database and using the SKIP
TABLESPACE parameter.
Problem is, I'm getting this in RMAN
-- Violation: ORA-39932: Extensible Index XXX.BS_FULDOC_TEMPLATE_IDX3
not fully contained in the transportable set.
-- Violation: ORA-39932: Extensible Index XXX.BS_FULDOC_TEMPLATE_IDX
not fully contained in the transportable set.
-- Violation: ORA-39932: Extensible Index XXX.BS_FULITEMS not fully
contained in the transportable set.
-- Violation: ORA-39932: Extensible Index XXX.BS_FULDOC_TEMPLATE_IDX2
not fully contained in the transportable set.
So, I followed the information in: 1996925.1 about how to check for TTS
violations.
These indexes are CONTEXT INDEXES and I found a note that these are set to
IND$ which is always the SYSTEM tablespace and this can be ignored when
doing a Transportable Tablespace.
HOWEVER, I'm not doing a Transportable Tablespace per se, I'm doing a
point-in-time recover to a backup db to grab one table that was mucked.
But this tablespace contains CTXSYS CONTEXT indexes and I can't seem to get
past it.
*Questions:*
1. Is there anyway to force RMAN to skip the TTS check:
database mounted
Checking that duplicated tablespaces are self-contained
The following errors need to be fixed before peforming this command
Violation: ORA-39932: Extensible Index BSTUPLE.BS_FULDOC_TEMPLATE_IDX3
not fully contained in the transportable set.
Violation: ORA-39932: Extensible Index BSTUPLE.BS_FULDOC_TEMPLATE_IDX
not fully contained in the transportable set.
Violation: ORA-39932: Extensible Index BSTUPLE.BS_FULITEMS not fully
contained in the transportable set.
Violation: ORA-39932: Extensible Index BSTUPLE.BS_FULDOC_TEMPLATE_IDX2
not fully contained in the transportable set.
Oracle instance started
2. Is there some way I can better identify which tablespace RMAN *thinks *is
needed to do the restore? I've included SYSTEM,SYSAUX,USERS,TOOLS but RMAN
still thinks its not self-contained. I really need to get RMAN to ignore
the check.
CTX_REPORT.DESCRIBE_INDEX('XXX.BS_FULDOC_TEMPLATE_IDX3')
--------------------------------------------------------------------------------
===========================================================================
INDEX DESCRIPTION
===========================================================================
index name: "XXX"."BS_FULDOC_TEMPLATE_IDX3"
index id: 1064
index type: context
base table: "XXX"."BS_FULDOC_TEMPLATE_LTR1"
primary key column:
text column: FDT_PDF
text column type: BLOB
language column:
format column:
charset column:
Query Stats Enabled: NO
status: INDEXED
full optimize token:
full optimize count:
docid count: 1095
nextid: 1096
===========================================================================
INDEX OBJECTS
===========================================================================
*datastore: DIRECT_DATASTORE*
filter: AUTO_FILTER
section group: HTML_SECTION_GROUP
lexer: BASIC_LEXER
wordlist: BASIC_WORDLIST
stemmer: ENGLISH
fuzzy_match: GENERIC
stoplist: BASIC_STOPLIST
stop_word: Corp
stop_word: ...
storage: BASIC_STORAGE
r_table_clause: lob (data) store as (cache)
i_index_clause: compress 2