Results 1 to 7 of 7
  1. #1
    Join Date
    Feb 2004
    Location
    Houston, TX
    Posts
    10

    Unanswered: Error when transporting 9.2.0.4 tablespaces

    I have two 9.2.0.4 tablespaces where I'm trying transport a tablespace from one 2000 server to another 2000 server. The import immediately fails and kills the Oracle service. On the source database I execute (after putting the users tablespace in read only mode)
    exp transport_tablespace=y tablespace=users contraints=n grants=n file=export_tbsp.dmp triggers=n
    I then copy the export dump file and the datafiles that make up the tablespace to the target server. I create the user gcs with the following command:
    create user gcs identified by pwd
    temporary tablespace temp;
    I did not define a default tablespace (which would be users and doesn't exist yet)
    I run the imp command
    imp transport_tablespace=y file=export_tbsp.dmp datafiles=('pathto datafile') tts_owner=gcs fromuser=gcs touser=gcs
    I connect / as sysdba
    Connected to: Oracle9i Enterprise Edition Release 9.2.0.4.0 - Production
    With the Partitioning, OLAP and Oracle Data Mining options
    JServer Release 9.2.0.4.0 - Production

    Export file created by EXPORT:V09.02.00 via conventional path
    About to import transportable tablespace(s) metadata...
    import done in WE8ISO8859P1 character set and AL16UTF16 NCHAR character set
    IMP-00017: following statement failed with ORACLE error 3113:
    "BEGIN sys.dbms_plugts.beginImport ('9.2.0.4.0',31,'2000',NULL,'NULL',3104"
    "7,21001,1); END;"
    IMP-00003: ORACLE error 3113 encountered
    ORA-03113: end-of-file on communication channel
    IMP-00000: Import terminated unsuccessfully

    The 3113 means the service has been killed.
    Any ideas on what my problem is?

  2. #2
    Join Date
    Jan 2004
    Posts
    370
    Any trace files in user_dump_dest?
    Any errors in the alert log?

  3. #3
    Join Date
    Feb 2004
    Location
    Houston, TX
    Posts
    10
    Unfortunately, the alert log and user logs show nothing except that I restarted the service. (Doesn't show it is going down)

  4. #4
    Join Date
    Jan 2004
    Posts
    370
    No trace files in user_dump_dest and nothing in the alert log to work with.

    You need to get more information - I'd switch on tracing while I tried the import. There would definitely be trace files produced and they may provide more in the way of error messages.

  5. #5
    Join Date
    Feb 2004
    Location
    Houston, TX
    Posts
    10
    I turned full tracing on. Nothing useful. I believe the service is killed before it can write to the trace files. (set SQL_TRACE=TRUE)

  6. #6
    Join Date
    Jan 2004
    Posts
    99
    are you sure your transportable tablespace is a SET using the dbms TTS transport package (cant remember the name)?? also did you copy the files over in binary format?

  7. #7
    Join Date
    Feb 2004
    Posts
    1
    the tablespace should be containded itself.
    u should check.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •