TRANSPORT_SET_VIOLATIONS

Is this view (TRANSPORT_SET_VIOLATIONS) present in a fresh installation of oracle? This is created dynamically only when there is a transport set violation - correct me if i'm wrong.
Is there way to create this beforehand? I'd appreciate any pointers on this.

It looks as if its related to transportable tablespaces (of which I don't have any), so I assume its created by default.
Its owned by sys and the query used to create the view is as follows:
select "VIOLATIONS" from sys.tts_error$

Similar Messages

Transport_set_violations during expdp

Good Morning Gurus,
We have oracle 10.2.0.4 on windows.I have a tablespace avw_data which has some Q tables,the tablespace keeps on growing and is not letting me reorganise itself due to Q tables.So for the work around I thought to do expdp of the specified 35 Q tables impdp them in new tablespace and then reorganise this tablespace.But when i run following commad
SELECT * FROM transport_set_violations;
i see 3 tablespace indx,vending,avw_indx have indexes from tables in avw_data tablespace.
Please help as to how can I proceed with export.
Regards
Deepa

Deepa,
Use TRANSPORT_FULL_CHECK for dependecies and see following link for more information.
http://download.oracle.com/docs/cd/B19306_01/server.102/b14215/dp_export.htm#sthref173
Regards

How can I move back the rman convert file from file system to ASM?

I have no idea on pluging-in the data files which were unloaded as follows:
SQL> alter tablespace P_CDDH_DSPGD_V1_2011 read only;
SQL> alter tablespace P_IDX_CDDH_DSPGD_V1_2011 read only;
SQL> exec dbms_tts.transport_set_check('P_CDDH_DSPGD_V1_2011,P_IDX_CDDH_DSPGD_V1_2011',true);
SQL> select * from transport_set_violations;
UNIX> expdp tossadm@pmscdhf1 dumpfile=ttsfy1.dmp directory=trans_dir transport_tablespaces = P_CDDH_DSPGD_V1_2011,P_IDX_CDDH_DSPGD_V1_2011
RMAN> convert tablespace P_CDDH_DSPGD_V1_2011, P_IDX_CDDH_DSPGD_V1_2011 format = '/appl/oem/backup/temp/%I_%s_%t_extbspace.dbf';
Starting conversion at source at 03-OCT-13
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=116 instance=pmscdhf11 device type=DISK
channel ORA_DISK_1: starting datafile conversion
input datafile file number=00079 name=+PMSCDHF1/p_cddh_dspgd_v1_2011_01.dbf
converted datafile=/appl/oem/backup/temp/3536350174_2820_827849001_extbspace.dbf
channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:02:15
channel ORA_DISK_1: starting datafile conversion
input datafile file number=00080 name=+PMSCDHF1/p_idx_cddh_dspgd_v1_2011_02.dbf
converted datafile=/appl/oem/backup/temp/3536350174_2821_827849136_extbspace.dbf
channel ORA_DISK_1: datafile conversion complete, elapsed time: 00:01:45
Finished conversion at source at 03-OCT-13
Starting Control File Autobackup at 03-OCT-13
piece handle=/dbms/oracle/r1110/db_01/dbs/c-3536350174-20131003-02 comment=NONE
Finished Control File Autobackup at 03-OCT-13
SQL> drop tablespace P_CDDH_DSPGD_V1_2011 including contents;
SQL> drop tablespace P_IDX_CDDH_DSPGD_V1_2011 including contents;
Afterward, how can I relocate the backup files "/appl/oem/backup/temp/3536350174_2820_827849001_extbspace.dbf", "/appl/oem/backup/temp/3536350174_2821_827849136_extbspace.dbf" back to the ASM group +PMSCDHF1 ???

The 11.1 documentation only says "Enables you to copy files between ASM disk groups on local instances to and from remote instances" and "You can also use this command to copy files from ASM disk groups to the operating system."
http://docs.oracle.com/cd/B28359_01/server.111/b31107/asm_util.htm#CHDJEIEA
The 11.2 documentation says "Copy files from a disk group to the operating system Copy files from a disk group to a disk group Copy files from the operating system to a disk group"
http://docs.oracle.com/cd/E11882_01/server.112/e18951/asm_util003.htm#CHDJEIEA
I've never tried 11.1
Hemant K Chitale

Transport tablespace related problem

Hi all,
I have a problem i want to export tablespaces as i have to migrate my db from oracle 9.2 to oracle 10.2 from win to RHEL4.......but i am getting an error ,pls suggest me for the same....
SQL> @G:\oracle\ora92\rdbms\admin\dbmsplts.sql;
Package created.
Package created.
Grant succeeded.
Package created.
Grant succeeded.
drop view sys.transport_set_violations
ERROR at line 1:
ORA-00942: table or view does not exist
PL/SQL procedure successfully completed.
drop table sys.transts_error$
ERROR at line 1:
ORA-00942: table or view does not exist
Package created.
SQL> exec sys.dbms_tts.transport_set_check('SRO',true);
BEGIN sys.dbms_tts.transport_set_check('SRO',true); END;
ERROR at line 1:
ORA-04068: existing state of packages has been discarded
ORA-04063: package body "SYS.DBMS_TTS" has errors
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at line 1
SQL> desc dbms_tts
PROCEDURE DOWNGRADE
FUNCTION ISSELFCONTAINED RETURNS BOOLEAN
Argument Name                  Type                    In/Out Default?
TS_LIST                        CLOB                    IN
INCL_CONSTRAINTS               BOOLEAN                 IN
FULL_CHECK                     BOOLEAN                 IN
PROCEDURE KFP_CKCMP
PROCEDURE TRANSPORT_SET_CHECK
Argument Name                  Type                    In/Out Default?
TS_LIST                        CLOB                    IN
INCL_CONSTRAINTS               BOOLEAN                 IN     DEFAULT
FULL_CHECK                     BOOLEAN                 IN     DEFAULT
SQL> exec dbms_tts.transport_set_check('SRO',true);
BEGIN dbms_tts.transport_set_check('SRO',true); END;
ERROR at line 1:
ORA-04068: existing state of packages has been discarded
ORA-04063: package body "SYS.DBMS_TTS" has errors
ORA-06508: PL/SQL: could not find program unit being called
ORA-06512: at line 1

Are you,by any chance, running Oracle 9i installation code in an Oracle 10g database?
If so : why?
As far as I know you can only transport tablespaces to a database of an identical version, so it looks like this is not going to work.
Sybrand Bakker
Senior Oracle DBA

XTTS - problem in copying datafile into ASM

I'm testing the migration of database from AIX to Linux using cross platform transportable tablespaces.
DB version: source: 10.2.0.4
Destination: 10.2.0.5
OS version: source: AIX6.1 - AIX-Based Systems (64-bit)
Destination: RedHat Linux - Linux x86 64-bit
I run the below commands before copying the datafile at destination.
EXECUTE DBMS_TTS.TRANSPORT_SET_CHECK('TBLSP1,TBLSP2', TRUE);
SELECT * FROM TRANSPORT_SET_VIOLATIONS;
no rows selected
alter system archive log current;
alter tablespace TBLSP1 read only;
alter tablespace TBLSP2 read only;
expdp DUMPFILE=xtts_exp.dmp DIRECTORY=DUMP_DIR logfile=xtts_exp.log TRANSPORT_TABLESPACES=TBLSP1,TBLSP2
CONVERT TABLESPACE TBLSP1,TBLSP2
TO PLATFORM 'Linux x86 64-bit'
FORMAT '/dataimport/%U';/dataimport is a shared file system mounted on Linux server and am able to see the datafile over there. But, am receiving the error below when trying to copy the datafile on the linux server. Could someone let me know if I miss something / how to resolve this error.
$rman target /
RMAN> copy datafile '/dataimport/data_D-DBMGRT_I-3320277811_TS-TBLSP1_FNO-26_05m8miia' to '+DATA';
Starting backup at 05-APR-11
using channel ORA_DISK_1
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/05/2011 10:19:44
RMAN-20201: datafile not found in the recovery catalog
RMAN-06010: error while looking up datafile: /dataimport/data_D-DBMGRT_I-3320277811_TS-TBLSP1_FNO-26_05m8miia

I don't think it's related to patchset mismatch. Yes. I moved the dump file and datafile copies to local file system also and got the same error.
Here are the steps once again. The tablespaces are still read only on source side. How can it affect datafile copy on destination side?.
EXECUTE DBMS_TTS.TRANSPORT_SET_CHECK('TBLSP1,TBLSP2', TRUE);
SELECT * FROM TRANSPORT_SET_VIOLATIONS;
no rows selected
alter system archive log current;
alter tablespace TBLSP1 read only;
alter tablespace TBLSP2 read only;
expdp DUMPFILE=xtts_exp.dmp DIRECTORY=DUMP_DIR logfile=xtts_exp.log TRANSPORT_TABLESPACES=TBLSP1,TBLSP2
CONVERT TABLESPACE TBLSP1,TBLSP2
TO PLATFORM 'Linux x86 64-bit'
FORMAT '/dataimport/%U';
impdp DUMPFILE=xtts_exp.dmp DIRECTORY=DUMP_DIR logfile=xtts_imp.log TRANSPORT_DATAFILES='/dataimport/data_D-DBMGRT_I-3320277811_TS-TBLSP1_FNO-26_0bm90rir','/az/dataimport/export/data_D-DBMGRT_I-3320277811_TS-TBLSP2_FNO-39_0dm90sa0'
Job "SYS"."SYS_IMPORT_TRANSPORTABLE_01" successfully completed
$rman target /
RMAN> copy datafile '/dataimport/data_D-DBMGRT_I-3320277811_TS-TBLSP1_FNO-26_0bm90rir' to '+DATA';
Starting backup at 05-APR-11
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=4361 instance=dbmgrt1 devtype=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of backup command at 04/05/2011 12:42:47
RMAN-20201: datafile not found in the recovery catalog
RMAN-06010: error while looking up datafile: /dataimport/data_D-DBMGRT_I-3320277811_TS-TBLSP1_FNO-26_0bm90rir
SQL> select file_name from dba_data_files where tablespace_name='TBLSP1';
/dataimport/data_D-DBMGRT_I-3320277811_TS-TBLSP1_FNO-26_0bm90rir
$ls -l /dataimport/data_D-DBMGRT_I-3320277811_TS-TBLSP1_FNO-26_0bm90rir
-rw-r----- 1 oracle oinstall 32914808832 Apr 5 12:31 /dataimport/data_D-DBMGRT_I-3320277811_TS-TBLSP1_FNO-26_0bm90rir

Running into strange errors when creating a new instance

Hello:
I am running 9.2.0.8 on a Windows 2003 Server.
When I try to create a new instance, I chose a New Database/UTF-8/16KB Block Size. Everything else was default value. However, I get a "ORA-29807: specified operator does not exist" error. When I looked into the Create log file, the file, CreateDBCatalog.log has the following errors:
No errors.
No errors.
drop table AUDIT_ACTIONS
ERROR at line 1:
ORA-00942: table or view does not exist
No errors.
CREATE ROLE exp_full_database
ERROR at line 1:
ORA-01921: role name 'EXP_FULL_DATABASE' conflicts with another user or role name
CREATE ROLE imp_full_database
ERROR at line 1:
ORA-01921: role name 'IMP_FULL_DATABASE' conflicts with another user or role name
drop table system.logstdby$skip_support
ERROR at line 1:
ORA-00942: table or view does not exist
Warning: View created with compilation errors.
Warning: View created with compilation errors.
CREATE ROLE exp_full_database
ERROR at line 1:
ORA-01921: role name 'EXP_FULL_DATABASE' conflicts with another user or role name
CREATE ROLE imp_full_database
ERROR at line 1:
ORA-01921: role name 'IMP_FULL_DATABASE' conflicts with another user or role name
drop synonym DBA_LOCKS
ERROR at line 1:
ORA-01434: private synonym to be dropped does not exist
drop view DBA_LOCKS
ERROR at line 1:
ORA-00942: table or view does not exist
No errors.
drop package body sys.diana
ERROR at line 1:
ORA-04043: object DIANA does not exist
drop package sys.diana
ERROR at line 1:
ORA-04043: object DIANA does not exist
drop table sys.pstubtbl
ERROR at line 1:
ORA-00942: table or view does not exist
drop package body sys.diutil
ERROR at line 1:
ORA-04043: object DIUTIL does not exist
drop package sys.diutil
ERROR at line 1:
ORA-04043: object DIUTIL does not exist
drop procedure sys.pstubt
ERROR at line 1:
ORA-04043: object PSTUBT does not exist
drop procedure sys.pstub
ERROR at line 1:
ORA-04043: object PSTUB does not exist
drop procedure sys.subptxt2
ERROR at line 1:
ORA-04043: object SUBPTXT2 does not exist
drop procedure sys.subptxt
ERROR at line 1:
ORA-04043: object SUBPTXT does not exist
No errors.
No errors.
No errors.
No errors.
drop type dbms_xplan_type_table
ERROR at line 1:
ORA-04043: object DBMS_XPLAN_TYPE_TABLE does not exist
drop type dbms_xplan_type
ERROR at line 1:
ORA-04043: object DBMS_XPLAN_TYPE does not exist
No errors.
DROP TABLE ODCI_SECOBJ$
ERROR at line 1:
ORA-00942: table or view does not exist
DROP TABLE ODCI_WARNINGS$
ERROR at line 1:
ORA-00942: table or view does not exist
No errors.
No errors.
No errors.
No errors.
drop sequence dbms_lock_id
ERROR at line 1:
ORA-02289: sequence does not exist
drop table dbms_alert_info
ERROR at line 1:
ORA-00942: table or view does not exist
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
drop table SYSTEM.AQ$_Internet_Agent_Privs
ERROR at line 1:
ORA-00942: table or view does not exist
drop table SYSTEM.AQ$_Internet_Agents
ERROR at line 1:
ORA-00942: table or view does not exist
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
DROP SYNONYM def$_tran
ERROR at line 1:
ORA-01434: private synonym to be dropped does not exist
DROP SYNONYM def$_call
ERROR at line 1:
ORA-01434: private synonym to be dropped does not exist
DROP SYNONYM def$_defaultdest
ERROR at line 1:
ORA-01434: private synonym to be dropped does not exist
DBMS_DEBUG successfully loaded.
PBUTL     successfully loaded.
PBRPH     successfully loaded.
PBSDE     successfully loaded.
PBREAK     successfully loaded.
DROP TYPE SYS.RewriteMessage FORCE
ERROR at line 1:
ORA-04043: object REWRITEMESSAGE does not exist
DROP TYPE SYS.RewriteArrayType FORCE
ERROR at line 1:
ORA-04043: object REWRITEARRAYTYPE does not exist
DROP TYPE SYS.ExplainMVMessage FORCE
ERROR at line 1:
ORA-04043: object EXPLAINMVMESSAGE does not exist
DROP TYPE SYS.ExplainMVArrayType FORCE
ERROR at line 1:
ORA-04043: object EXPLAINMVARRAYTYPE does not exist
No errors.
drop view sys.transport_set_violations
ERROR at line 1:
ORA-00942: table or view does not exist
drop table sys.transts_error$
ERROR at line 1:
ORA-00942: table or view does not exist
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
No errors.
drop operator XMLSequence
ERROR at line 1:
ORA-29807: specified operator does not exist
What does this mean?
venki
Edited by: thevenkat on Mar 11, 2009 10:17 PM

Venki,
The ORA-00942 is okay because there is no existing object. But what stuck me is the ORA-01921 error which may indicate that this might not be a new database.
CREATE ROLE exp_full_database
ERROR at line 1:
ORA-01921: role name 'EXP_FULL_DATABASE' conflicts with another user or role name
CREATE ROLE imp_full_database
ERROR at line 1:
ORA-01921: role name 'IMP_FULL_DATABASE' conflicts with another user or role name
Are there any existing databases on this server? Have you tried to create it on other machine?I searched on Metalink too and found Doc ID: 237486.1 ORA-29807 Signalled While Creating Database using DBCA which say that eroror could be ignored. You may want to review that as well.
Ittichai

Trasporatble Tablespace issue

SQL> exec DBMS_TTS.TRANSPORT_SET_CHECK('APPS_TS_TX_DATA,APPS_TS_TX_IDX,APPS_TS_SUMMARY,APPS_TS_ARCHIVE,APPS_TS_SEED,APPS_TS_INTERFACE',TRUE)
PL/SQL procedure successfully completed.
SQL> SELECT * FROM TRANSPORT_SET_VIOLATIONS;
VIOLATIONS
Extensible Index APPLSYS.FND_LOBS_CTX not fully contained in the transportable set.
Identify the associated table and list of secondary objects and resolve self containment
SQL> select owner,index_name,table_name,tablespace_name from all_indexes where index_name='FND_LOBS_CTX'
2 /
OWNER                          INDEX_NAME                     TABLE_NAME                     TABLESPACE_NAME
APPLSYS                        FND_LOBS_CTX                   FND_LOBSFND_LOBS table is object of itself APPLSYS user without tablespace how come.
SQL> select owner,object_name,object_type from all_objects where object_name='FND_LOBS'
2 /
OWNER                          OBJECT_NAME                    OBJECT_TYPE
APPLSYS                        FND_LOBS                       TABLE
APPS                           FND_LOBS                       SYNONYMHow can i resolve it i am already taking APPS_TS_TX_DATA which is default tablespace of APPS user
SQL> select username,default_tablespace from dba_users where username='APPS';
USERNAME                       DEFAULT_TABLESPACE
APPS                           APPS_TS_TX_DATA
SQL>Please help me.

Hello,
You may try this query to get the Tablespace name containing the LOB Segment:
select owner, table_name, index_name, segment_name, tablespace_name
from dba_lobs
where table_name = 'FND_LOBS';http://download.oracle.com/docs/cd/E11882_01/server.112/e17110/statviews_1130.htm#i1581211
Hope this help.
Best regards,
Jean-Valentin

TRANSPORTABLE TABLESPACE IN 8.1

제품 : ORACLE SERVER
작성날짜 : 2004-08-16
Oracle8i에서는 tablespace단위로 그 구성 datafile들을 옮겨서 다른
database에 연결시켜 사용할 수 있는 기능이 제공된다.
SCOPE
8i~10g Standard Edition 에서는 Import transportable tablespaces 기능만이 지원이 됩니다.
유용성
1. 전사적 정보시스템내에서 대량의 data의 흐름이 필요할 경우, - 예를 들어,
OLTP database에서 data warehouse database로의 data이전 또는 data
warehouse에서 data mart로의 data이전 등 - 8.1이전까지는 SQL*Loader의
direct path나 parallel DML등의 방법을 이용하여 그 작업속도를
향상시키려고 시도 하였다. 8.1의 Transportable Tablespace기능을
이용한다면 datafile들을 새로운 system으로 copy하는 정도의 시간으로
작업을 완료할 수 있다.
2. 중앙에서 변경, 관리되고 지방(지사)에서 사용되는 data들을 CD-ROM에 담아서
배포하는 등에 이용가능하다.
예를 들어, 제품의 사양, 가격등에 대한 정보를 담는 tablespace를 중앙에서
변경, 저장하여 배포하고, 이 data를 지방의 database에 연결하여 주문
system등에 이용할 수 있다.
3. Contents 사업자들은 자신이 제공하는 contents들을 Transportable
Tablespace형태로 제공 하여 고객들의 database에 바로 연결하여 사용할 수
있도록 할 수 있다.
특성, 제한사항
1. 특정 tablespace내의 전체 data를 이동시킨다.
2. Media recovery를 지원한다.
3. Source database와 target database는
- 동일한 OS에서 구동되고 있어야 한다.
- Oracle8i(8.1)이상의 version이어야 한다.
- 동일한 block size를 이용해야 한다.
- 동일한 characterset을 이용해야 한다.
작업절차
1. 대상 tablespace를 read only 상태로 변경한다.
file을 copy하는 동안 해당 tablespace에 변경작업이 일어나지 않도록
보장한다.
2. Source database에서 metadata를 export한다.
해당 tablespace와 그 안의 object들에 대한 dictionary정보를 dump file에
받는 과정이다.
3. 대상 tablespace의 datafile들을 target system으로 이동시킨다.
4. Export dump file을 이동시킨다.
5. Metadata를 target database에 import한다.
6. 필요하다면 이후에 해당 tablespace를 read-write mode로 변경한다.
SAMPLE
Source database : dbA
Target database : dbB
이동 대상 tablespace : TRANS_TS(/u01/data/trans_ts01.dbf, /u01/data/trans_ts02.dbf 로 구성)
1. dbA에서 TRANS_TS를 read only로 변경
alter tablespace TRANS_TS read only ;
2. dbA에서 metadata를 export한다.
exp sys/manager file=trans.dmp transport_tablespace=y
tablespaces=trans_ts triggers=n constraints=n
version이 8.1.6이상이라면,
exp system/manager 대신에 exp \'sys/manager as sysdba\'와 같이
주여야 한다.
transport_tablespace(Y or N)는 Y로 설정한다.
tablespaces에는 transport의 대상이 되는 tablespace를 지정한다.
대상 tablespace의 table들에 걸려있는 trigger, constraint들도 대상으로
할 것인지를 지정한다.
3. TRANS_TS의 두개의 datafile들을 dbB가 존재하는 system으로 binary
copy한다.
4. 위의 2번 과정에서 export한 dump file을 dbB가 존재하는 system으로
binary copy한다.
5. dbB에 metadata를 import한다.
imp sys/manager file=trans.dmp transport_tablespace=y
datafiles=/disk1/trans_ts01.dbf,/disk2/trans_ts02.dbf
8.1.6이상이라면 이 부분도 sys/manager대신에 \'sys/manager as dba\'
와 같이 적는다.
transport_tablespace(Y or N)는 Y로 설정한다.
datafile의 name은 dbB system에 copy된 filename을 지칭한다.
6. 필요할 경우 tablespace를 read write mode로 변경한다.
alter tablespace TRANS_TS read write ;
TRANSPORT SET
Transport하고자 하는 tablespace set은 self-contained이어야만 한다.
대상이 되는 tablespace set 내에 partitioned table이 존재한다면 해당
table의 모든 partition들이 이들 tablespace 내에 존재해야 하며, 비슷하게
LOB column의 data들도 table의 data들과 함께 이들 tablespace 내에 존재해야
하는데, 이렇게 서로 관련된 object들이 tablespace set내에 모두 존재하는
것을 self-contained라고 지칭한다.
tablespace set이 self-contained하지 않다면 transport할 수 없다.
Transport tablespace set이 self-contained인지의 여부를 확인하기 위해서
DBMS_TTS.TRANSPORT_SET_CHECK procedure를 이용한다.
예를 들어,
DBMS_TTS.TRANSPORT_SET_CHECK(ts_list=>'A,B,C',incl_constraints=>TRUE)
을 수행하면 A, B, C 세개의 tablespace로 구성된 transport tablespace set이
self-contained인지에 대한 정보를 TRANSPORT_SET_VIOLATIONS view에 기록해
준다.
incl_constraints를 설정하면 referencial(foreign key) constraint에
대해서도 self-contained 여부를 check해준다.

you can do the following:
1. export all objects in your tablespace, by using option tables=(x,y,...)
2. drop your tablespace including contents
3. create new tablespace with a desired name using the same datafiles names (you can physically delete them first or use a REUSE option)
4. create objects you exported in the new tablespace.
5. perform your import
By creating objects first, you guarantee that export will populate tables in the tablespace you need.
This is just a general plan, you have to clarify and confirm all details.

@/vobs/oracle/rdbms/admin/catproc.sql error message

After setting up 9i DB manually when i ran this script all went well with few errors , i am wondering these errors are ignoreable ....
@/vobs/oracle/rdbms/admin/catproc.sql
Grant succeeded.
drop package body sys.diana
ERROR at line 1:
ORA-04043: object DIANA does not exist
drop package sys.diana
ERROR at line 1:
ORA-04043: object DIANA does not exist
Package created.
Package body created.
drop package body sys.diutil
ERROR at line 1:
ORA-04043: object DIUTIL does not exist
drop package sys.diutil
ERROR at line 1:
ORA-04043: object DIUTIL does not exist
Package created.
ERROR at line 1:
ORA-04043: object PSTUBT does not exist
Procedure created.
Grant succeeded.
drop procedure sys.pstub
ERROR at line 1:
ERROR at line 1:
ORA-04043: object SUBPTXT2 does not exist
Procedure created.
drop procedure sys.subptxt
ERROR at line 1:
ORA-04043: object SUBPTXT does not exist
ERROR at line 1:
ORA-04043: object DBMS_XPLAN_TYPE_TABLE does not exist
drop type dbms_xplan_type
ERROR at line 1:
ORA-04043: object DBMS_XPLAN_TYPE does not exist
Type created.
ERROR at line 1:
ORA-00942: table or view does not exist
DROP TABLE ODCI_WARNINGS$
ERROR at line 1:
ORA-00942: table or view does not exist
Type created.
Table truncated.
drop sequence dbms_lock_id
ERROR at line 1:
ORA-02289: sequence does not exist
Sequence created.
drop table SYSTEM.AQ$_Internet_Agent_Privs
ERROR at line 1:
ORA-00942: table or view does not exist
drop table SYSTEM.AQ$_Internet_Agents
ERROR at line 1:
ORA-00942: table or view does not exist
Table created.
DROP SYNONYM def$_tran
ERROR at line 1:
ORA-01434: private synonym to be dropped does not exist
DROP SYNONYM def$_call
ERROR at line 1:
ORA-01434: private synonym to be dropped does not exist
DROP SYNONYM def$_defaultdest
ERROR at line 1:
DROP TYPE SYS.ExplainMVMessage FORCE
ERROR at line 1:
ORA-04043: object EXPLAINMVMESSAGE does not exist
Type created.
drop view sys.transport_set_violations
ERROR at line 1:
ORA-00942: table or view does not exist
PL/SQL procedure successfully completed.
drop table sys.transts_error$
ERROR at line 1:
ORA-00942: table or view does not exist
drop operator XMLSequence
ERROR at line 1:
ORA-29807: specified operator does not exist
drop function XMLSequenceFromXMLType
ERROR at line 1:
ORA-04043: object XMLSEQUENCEFROMXMLTYPE does not exist
drop function XMLSequenceFromRefCursor
ERROR at line 1:
drop function XMLSequenceFromRefCursor2
ERROR at line 1:
ORA-04043: object XMLSEQUENCEFROMREFCURSOR2 does not exist
drop type XMLSeq_Imp_t
ERROR at line 1:
ORA-04043: object XMLSEQ_IMP_T does not exist
drop type XMLSeqCur_Imp_t
ERROR at line 1:
ORA-04043: object KU$_IND_PART_T does not exist
drop type ku$_ind_part_list_t force
ERROR at line 1:
ORA-04043: object KU$_IND_PART_LIST_T does not exist
drop type ku$_piot_part_t force
ERROR at line 1:
Grant succeeded.
Synonym created.
Grant succeeded.
Package altered.
Package altered.
PL/SQL procedure successfully completed.

These errors are ignorable, Oracle just trying to drop the package before creating them. If this is the first time you run catproc.sql, the errors are expected.

DB migration from RHEL 5 to Solaris x86(64bit)

DB version : 11.1.0.7
Platform : RHEL 5 (64bit)
We would like to move our non-ASM 11.1 DB which is currently in Linux (RHEL 5) to Solaris 10 x86 (64bit).
Both RHEL 5 (64bit) and Solaris x86 (64bit) are of LITTLE ENDIAN format.
1. I gather that I have to use RMAN's CONVERT DATABASE for this. Any Metalink note or URLs relevant to this migration ?
2. Would the migration be easier if my DB was in 11.2 ? I could upgrade my DB to 11.2 if there are any advangtages from migration point of view?

You can use transportable tablespace option to move database accross platforms.
First, you must check tablespace dependecies.
Check whether your tablespace can transfer or not?
SQL> exec dbms_tts.transport_set_check('TEST_TS',TRUE);
SQL> select * from transport_set_violations;
set status of tablespace which you want to move to Read-only.
SQL>alter tablespace test_ts read only;
Convert datafiles of tablespace
RMAN> convert tablespace test_ts to platform 'HP-UX (64-bit)' format='/tmp/test01.dbf';
Export tablespace metadata using data pump export
expdp talip/talip directory=dump_dir dumpfile=test_ts.dmp transport_tablespaces=test_ts
copy datafile of tablespace to another db.
Import metadata to another db.
impdp talip/talip directory=dump_dir dumpfile=test_ts.dmp transport_datafiles=/data1/testts01.dbf
Talip Hakan Ozturk
http://taliphakanozturken.wordpress.com/

Transport Tablespace export error.

Hello to All.
Oracle Version : 9.2.0.1
Operating System : Windows XP
Sir.
On testing to export a transportable tables space I got the following errors. I am unable to understand the cause of errors. Please guide
The command fired and errors are :
Before this I have made the tablespace users read only by this command :;
sql> alter tablespace users read only;
Tablespace Altered
C:\Documents and Settings\admin>exp \"sys/oracle as sysdba\" transport_tablespace=Y tablespaces=users log=ts_users.log
Export: Release 9.2.0.1.0 - Production on Fri Oct 3 20:23:09 2008
Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
Connected to: Oracle9i Enterprise Edition Release 9.2.0.1.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.1.0 - Production
Export done in WE8MSWIN1252 character set and AL16UTF16 NCHAR character set
Note: table data (rows) will not be exported
About to export transportable tablespace metadata...
EXP-00008: ORACLE error 1001 encountered
ORA-01001: invalid cursor
ORA-06512: at "SYS.DBMS_SYS_SQL", line 819
ORA-06512: at "SYS.DBMS_SQL", line 19
ORA-06512: at "SYS.DBMS_TTS", line 774
ORA-25153: Temporary Tablespace is Empty
ORA-06512: at "SYS.DBMS_PLUGTS", line 1093
ORA-06512: at line 1
EXP-00000: Export terminated unsuccessfully
thanks and regards
Neeraj
Edited by: ora-boy on Oct 3, 2008 8:05 AM
Edited by: ora-boy on Oct 3, 2008 8:06 AM

EXTREMELY sorry for this type of silly blunder.
now the result is
PL/SQL procedure successfully completed.
SQL> SELECT * FROM TRANSPORT_SET_VIOLATIONS;
VIOLATIONS
Default Partition (Table) Tablespace SYSTEM for EMP1 not contained in transportable set
Default Partition (Table) Tablespace SYSTEM for EMP1 not contained in transportable set
Default Partition (Table) Tablespace SYSTEM for EMP1 not contained in transportable set
Default Partition (Table) Tablespace USERS for EMP1 not contained in transportable set
Default Partition (Table) Tablespace USERS for EMP1 not contained in transportable set
Default Partition (Table) Tablespace USERS for EMP1 not contained in transportable set
6 rows selected.
but I am unable to understand this.
thanks

Fully Automated RMAN TSPITR fails

condition:
oracle 11.2&&windows7(32bit)
       I performed Fully Automated RMAN TSPITR yesterday.When the oracle performed the export of the metadata of the recovery set,the following problem appeared.
Performing export of metadata...
   EXPDP> Starting "SYS"."TSPITR_EXP_dbtF":
Removing automatic instance
shutting down automatic instance
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/23/2013 01:01:05
RMAN-06136: ORACLE error from auxiliary database: ORA-01097: cannot shutdown while in a transaction - commit or rollback first
RMAN-06962: Error received during export of metadata
RMAN-06960:    EXPDP> ORA-39123: Data Pump transportable tablespace job aborted
ORA-39187: The transportable set is not self-contained, violation list is
ORA-39906: Constraint FK_PK between table SH.PK in tablespace TEST01 and table SH.FK in tablespace TEST02.
         The message of the problem tells me that the transprotable set is not self-contained.But I remember that I have dropped the constraint FK_PK.And then I run the following code.And the result tells me that the constraint surely be dropped.
       So ,why does the problem occur?
        Thanks!
SQL> select count(*) from dba_constraints where constraint_name ='FK_PK';
COUNT(*)
         0
SQL>    Begin
2         dbms_tts.transport_set_check('TEST02,TEST01',true,true);
3     End;
4 /
PL/SQL procedure successfully completed.
SQL> select * from transport_set_violations;
no rows selected

I just drop the constriant FK_PK.There are no index dropped of the tablespace test02 in the dba_recyclebin.
SQL> select object_name,original_name,type,ts_name from dba_recyclebin;
OBJECT_NAME                    ORIGINAL_N TYPE       TS_NAME
BIN$c96+yjANSE6ThcTovMwoPw==$0 TAB        TABLE      USERS
BIN$MkU0+TSYSJK1qnCAKglJFg==$0 TABLE1     TABLE      USERS
BIN$YCQ2IgKaQDWw6Cxrl6QRaA==$0 TAB        TABLE      TEST01
SQL> show user;
USER is "SH"
SQL> select name from v$database;
NAME
WAREHOUS
And the following code (starting the RMAN---occur the problem):
SQL> $rman target sys/123456@warehouse catalog rman/123456@catalog;
Recovery Manager: Release 11.2.0.1.0 - Production on Fri Aug 23 10:29:47 2013
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: WAREHOUS (DBID=4011143137)
connected to recovery catalog database
RMAN> recover tablespace test02 until scn 1346235 auxiliary destination 'G:\Oracle\TS';
Starting recover at 23-AUG-13
starting full resync of recovery catalog
full resync complete
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=22 device type=DISK
Creating automatic instance, with SID='atmp'
initialization parameters used for automatic instance:
db_name=WAREHOUS
db_unique_name=atmp_tspitr_WAREHOUS
compatible=11.2.0.0.0
db_block_size=8192
db_files=200
sga_target=280M
processes=50
db_create_file_dest=G:\Oracle\TS
log_archive_dest_1='location=G:\Oracle\TS'
#No auxiliary parameter file used
starting up automatic instance WAREHOUS
Oracle instance started
Total System Global Area     292933632 bytes
Fixed Size                     1374164 bytes
Variable Size                100665388 bytes
Database Buffers             184549376 bytes
Redo Buffers                   6344704 bytes
Automatic instance created
Running TRANSPORT_SET_CHECK on recovery set tablespaces
TRANSPORT_SET_CHECK completed successfully
contents of Memory Script:
# set requested point in time
set until scn 1346235;
# restore the controlfile
restore clone controlfile;
# mount the controlfile
sql clone 'alter database mount clone database';
# archive current online log
sql 'alter system archive log current';
# avoid unnecessary autobackups for structural changes during TSPITR
sql 'begin dbms_backup_restore.AutoBackupFlag(FALSE); end;';
# resync catalog
resync catalog;
executing Memory Script
executing command: SET until clause
Starting restore at 23-AUG-13
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=59 device type=DISK
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece G:\ORACLE\BACKUP\WAREHOUSE\LEVEL1_CUMULATIVE_0NOHKRT6_1_1
channel ORA_AUX_DISK_1: piece handle=G:\ORACLE\BACKUP\WAREHOUSE\LEVEL1_CUMULATIVE_0NOHKRT6_1_1 tag=LEVEL1_CUMULATIVE
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=G:\ORACLE\TS\WAREHOUSE\CONTROLFILE\O1_MF_91FLFZYS_.CTL
Finished restore at 23-AUG-13
sql statement: alter database mount clone database
sql statement: alter system archive log current
sql statement: begin dbms_backup_restore.AutoBackupFlag(FALSE); end;
starting full resync of recovery catalog
full resync complete
contents of Memory Script:
# set requested point in time
set until scn 1346235;
# set destinations for recovery set and auxiliary set datafiles
set newname for clone datafile 1 to new;
set newname for clone datafile 3 to new;
set newname for clone datafile 2 to new;
set newname for clone tempfile 1 to new;
set newname for datafile 7 to
"D:\APP\ASUS\ORADATA\WAREHOUSE\TEST02.DBF";
# switch all tempfiles
switch clone tempfile all;
# restore the tablespaces in the recovery set and the auxiliary set
restore clone datafile 1, 3, 2, 7;
switch clone datafile all;
executing Memory Script
executing command: SET until clause
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
renamed tempfile 1 to G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_TEMP_%U_.TMP in control file
Starting restore at 23-AUG-13
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_SYSTEM_%U_.DBF
channel ORA_AUX_DISK_1: restoring datafile 00003 to G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_UNDOTBS1_%U_.DBF
channel ORA_AUX_DISK_1: restoring datafile 00002 to G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_SYSAUX_%U_.DBF
channel ORA_AUX_DISK_1: restoring datafile 00007 to D:\APP\ASUS\ORADATA\WAREHOUSE\TEST02.DBF
channel ORA_AUX_DISK_1: reading from backup piece G:\ORACLE\BACKUP\WAREHOUSE\LEVEL0_0IOHKQV0_1_1
channel ORA_AUX_DISK_1: piece handle=G:\ORACLE\BACKUP\WAREHOUSE\LEVEL0_0IOHKQV0_1_1 tag=LEVEL0
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:55
Finished restore at 23-AUG-13
datafile 1 switched to datafile copy
input datafile copy RECID=5 STAMP=824207618 file name=G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_SYSTEM_91FLGBWL_.DBF
datafile 3 switched to datafile copy
input datafile copy RECID=6 STAMP=824207618 file name=G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_UNDOTBS1_91FLGBYW_.DBF
datafile 2 switched to datafile copy
input datafile copy RECID=7 STAMP=824207618 file name=G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_SYSAUX_91FLGBXY_.DBF
contents of Memory Script:
# set requested point in time
set until scn 1346235;
# online the datafiles restored or switched
sql clone "alter database datafile 1 online";
sql clone "alter database datafile 3 online";
sql clone "alter database datafile 2 online";
sql clone "alter database datafile 7 online";
# recover and open resetlogs
recover clone database tablespace "TEST02", "SYSTEM", "UNDOTBS1", "SYSAUX" delete archivelog;
alter clone database open resetlogs;
executing Memory Script
executing command: SET until clause
sql statement: alter database datafile 1 online
sql statement: alter database datafile 3 online
sql statement: alter database datafile 2 online
sql statement: alter database datafile 7 online
Starting recover at 23-AUG-13
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting incremental datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
destination for restore of datafile 00007: D:\APP\ASUS\ORADATA\WAREHOUSE\TEST02.DBF
destination for restore of datafile 00001: G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_SYSTEM_91FLGBWL_.DBF
destination for restore of datafile 00003: G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_UNDOTBS1_91FLGBYW_.DBF
destination for restore of datafile 00002: G:\ORACLE\TS\WAREHOUSE\DATAFILE\O1_MF_SYSAUX_91FLGBXY_.DBF
channel ORA_AUX_DISK_1: reading from backup piece G:\ORACLE\BACKUP\WAREHOUSE\LEVEL1_CUMULATIVE_0MOHKRRO_1_1
channel ORA_AUX_DISK_1: piece handle=G:\ORACLE\BACKUP\WAREHOUSE\LEVEL1_CUMULATIVE_0MOHKRRO_1_1 tag=LEVEL1_CUMULATIVE
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:07
starting media recovery
archived log for thread 1 with sequence 14 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_18\O1_MF_1_14_911NKBNY_.ARC
archived log for thread 1 with sequence 15 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_19\O1_MF_1_15_912Y0W3B_.ARC
archived log for thread 1 with sequence 16 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_19\O1_MF_1_16_91475BY4_.ARC
archived log for thread 1 with sequence 17 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_19\O1_MF_1_17_9149CJMS_.ARC
archived log for thread 1 with sequence 18 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_18_915MLYR1_.ARC
archived log for thread 1 with sequence 19 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_19_915OR34Z_.ARC
archived log for thread 1 with sequence 20 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_20_916XQMRD_.ARC
archived log for thread 1 with sequence 21 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_21_91715KYK_.ARC
archived log for thread 1 with sequence 22 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_21\O1_MF_1_22_91884645_.ARC
archived log for thread 1 with sequence 23 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_21\O1_MF_1_23_919JV790_.ARC
archived log for thread 1 with sequence 24 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_22\O1_MF_1_24_91D6GRC1_.ARC
archived log for thread 1 with sequence 25 is already on disk as file D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_22\O1_MF_1_25_91D7OOOR_.ARC
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_18\O1_MF_1_14_911NKBNY_.ARC thread=1 sequence=14
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_19\O1_MF_1_15_912Y0W3B_.ARC thread=1 sequence=15
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_19\O1_MF_1_16_91475BY4_.ARC thread=1 sequence=16
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_19\O1_MF_1_16_91475BY4_.ARC thread=1 sequence=16
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_19\O1_MF_1_17_9149CJMS_.ARC thread=1 sequence=17
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_18_915MLYR1_.ARC thread=1 sequence=18
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_19_915OR34Z_.ARC thread=1 sequence=19
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_20_916XQMRD_.ARC thread=1 sequence=20
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_20\O1_MF_1_21_91715KYK_.ARC thread=1 sequence=21
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_21\O1_MF_1_22_91884645_.ARC thread=1 sequence=22
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_21\O1_MF_1_23_919JV790_.ARC thread=1 sequence=23
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_22\O1_MF_1_24_91D6GRC1_.ARC thread=1 sequence=24
archived log file name=D:\APP\ASUS\FLASH_RECOVERY_AREA\WAREHOUSE\ARCHIVELOG\2013_08_22\O1_MF_1_25_91D7OOOR_.ARC thread=1 sequence=25
media recovery complete, elapsed time: 00:00:44
Finished recover at 23-AUG-13
database opened
contents of Memory Script:
# make read only the tablespace that will be exported
sql clone 'alter tablespace TEST02 read only';
# create directory for datapump import
sql "create or replace directory TSPITR_DIROBJ_DPDIR as ''
G:\Oracle\TS''";
# create directory for datapump export
sql clone "create or replace directory TSPITR_DIROBJ_DPDIR as ''
G:\Oracle\TS''";
executing Memory Script
sql statement: alter tablespace TEST02 read only
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''G:\Oracle\TS''
sql statement: create or replace directory TSPITR_DIROBJ_DPDIR as ''G:\Oracle\TS''
Performing export of metadata...
   EXPDP> Starting "SYS"."TSPITR_EXP_atmp":
Removing automatic instance
shutting down automatic instance
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of recover command at 08/23/2013 10:36:08
RMAN-06136: ORACLE error from auxiliary database: ORA-01097: cannot shutdown while in a transaction - commit or rollback first
RMAN-06962: Error received during export of metadata
RMAN-06960:    EXPDP> ORA-39123: Data Pump transportable tablespace job aborted
ORA-39187: The transportable set is not self-contained, violation list is
ORA-39906: Constraint FK_PK between table SH.PK in tablespace TEST01 and table SH.FK in tablespace TEST02.
RMAN>

Transportable tablespace feature

iam trying to use transportable tablespace feature on tablespace size 20gb on my prod.
so i thought i would try it on my dev serever first..i created the database on the dev server ..with a standard block size of 8k..
SQL> EXEC DBMS_TTS.TRANSPORT_SET_CHECK(ts_list => 'EXAMPLE', incl_constraints =>
true)
PL/SQL procedure successfully completed.
SQL> SELECT * FROM transport_set_violations;
VIOLATIONS
Index PM.ONLINEMEDIA_PK in tablespace INDEX_DATA enforces primary constriants o
f table PM.ONLINE_MEDIA in tablespace EXAMPLE
this is wat i got..so how do i resolve this..my require ment would be just to add the example TS..i want the constraints to be with it too...
secondly my standard block size is 16k where as in the production box the the actual tablespace size is 8k..
so wat should i do to successfuly make us of TTS feature
ur ideas would be definitely helpful..
Thanks
we r using oracle10gR2

agreed on moving the the index to the example tablespace..
well how about the block size....infact in the real senario iam trying to move the 8k tablespace size into 16k DEV env..
will it affect or not??
if it affects wat should i do in order to resolve??
Thanks

Transportable tablespace becomes non-transportable

Dear Guru's,
For years we exported and imported our transportable tablespaces, but recently the export fails with the following error message:
EXP-00008: ORACLE error 29341 encountered
ORA-29341: The transportable set is not self-contained
ORA-06512: at "SYS.DBMS_PLUGTS", line 1143
ORA-06512: at line 1
EXP-00000: Export terminated unsuccessfully
We use Oracle9i in RedHat 3.4 on xSeries 336 machine.
The exporting command: exp parfile=export.f
Contents of export.f:
USERID="/ as sysdba"
TRANSPORT_TABLESPACE=y
TABLESPACES=JAFFA_TSB,BLOB_TSP
# Outcommented lines contains default value:
#GRANTS=Y
#CONSTRAINTS=Y
#TRIGGERS=Y
#INDEXES=Y
TTS_FULL_CHECK=TRUE
OBJECT_CONSISTENT=Y
STATISTICS=COMPUTE
FILE=syn_meta.dmp
LOG=syn_meta.log
These attempts were made:
EXECUTE dbms_tts.transport_set_check('BLOB_TSP', TRUE, TRUE);
SELECT * FROM transport_set_violations ==> "no rows selected"
Oracle support service has still no answer to this issue.
How can we find where the problem is? Can anybody help?
Thanks a lot in advance!

Amazing!!!
Thank you very much Chris! We only need to drop the table and we manage to export again. This is the result of the conclusion:
SQL> execute dbms_tts.transport_set_check('JAFFA_TSB,BLOB_TSP',TRUE,TRUE);
PL/SQL procedure successfully completed.
SQL> SELECT * FROM transport_set_violations;
VIOLATIONS
Sys owned object REPAIR_TEST in tablespace JAFFA_TSB not allowed in pluggable set
Thanks again!!!

OATS 9.1 Oracle XE

Guys
I installed OATS 9.1 on Win2003 and couldn't get the OLT or OTM to work (I was getting a 404 errror so Weblogic had installed but the app wasn't deployed properly). There were loads of errors in the logs about deployment failure and messages like:
Task 0 failed: [Deployer:149026]deploy application oats.ear on AdminServer,oats.
Target state: deploy failed on Server AdminServer
javax.naming.NameNotFoundException: Unable to resolve 'OATS_common_DS'. Resolved ''; remaining name 'OATS_common_DS'
Target state: deploy failed on JMS Server oats
javax.naming.NameNotFoundException: Unable to resolve 'OATS_common_DS'. Resolved ''; remaining name 'OATS_common_DS'
I also was getting ORA-27101 errors
The problem was that ORACLE_HOME wasn't set! Don't know why the install didn't do this?? So I set it to C:\OracleATS\oxe\app\oracle\product\10.2.0\server (Control Panel, System, Advanced, Environment Variables, System)
Hope that helps anyone else who has this problem.
After setting the ORACLE_HOME I just restarted the service using the batch file under the program group

the equivalent of MSSQL Server's detach and move the database filesTransporting tablespaces is similar. SYSTEM cannot be transported, all tablespaces must be completely self contained, i.e. you can't transport just one tablespace containing a table that has an index in a different tablespace unless both tablespaces are included in the the transport set.
Also non-data schema objects- procedures, functions, sequences, etc., those are all stored in SYSTEM so a no-rows export (or data pump) is one way to capture those objects for import at the target.
Its pretty simple as long as schema objects are well placed, especially if you are not migrating to a different OS. The source tablespace(s) are placed in read only mode, the datafiles copied to the target database host, and a data pump (or exp) grabs the object metadata for the tablespace into a dump (export) file. Create all the object owners (schemas) at the target, and import the metadata.
There is a procedure that can be run to check if the desired set of tablespaces are self contained:
exec sys.DBMS_TTS.TRANSPORT_SET_CHECK('DATA,INDEXES[,...]', TRUE);
-- takes a few moments, check for violations:
SELECT * FROM sys.TRANSPORT_SET_VIOLATIONS;
... -- should be no rows selected, if ready for the exp or datapump go for it:
alter tablespace data read only;
alter tablespace indexes read only;
alter tablespace ... read only;
select ts# from v$tablespace where name in ('DATA','INDEXES'[,...]);
... list of ts#
select name from v$datafile where ts# in ( <ts#>,<ts#>[,...]);
... the list of datafiles to copy to targethttp://download.oracle.com/docs/cd/B19306_01/backup.102/b14191/dbxptrn.htm#sthref989

TRANSPORT_SET_VIOLATIONS

Similar Messages

Maybe you are looking for