Re: Exporting Domain Index PTG.CTRY_SPATIAL_IDX results in ORA-39127 and ORA-06512

From: sumit Tyagi <dba.tyagisumit_at_gmail.com>
Date: Tue, 27 May 2014 22:15:35 +0530
Message-ID: <CAFW4NVxTcQ6XdcqZii2yXcqSGSpBzJXo77ezR-TKu20iSVH9yA_at_mail.gmail.com>



have you checked the "status, domidx_status and domidx_opstatus" of your domain index from the dba_indexes view.

Please share the status. Status shold be valid and not failed.

On Tue, May 27, 2014 at 7:15 PM, Rajesh Aialavajjala < r.aialavajjala_at_gmail.com> wrote:

> I am encountering the following errors during the use of data pump to
> migrate an EBS instance following instructions in "Export/import process
> for 12.0 or 12.1 using 11gR1 or 11gR2 (Doc ID 741818.1)" - specifically
>
> expdp "'/ as sysdba'" parfile=auexpdp.dat
>
> Processing object type
> DATABASE_EXPORT/SCHEMA/TABLE/INDEX/DOMAIN_INDEX/INDEX
> ORA-39127: unexpected error from call to local_str :=
> SYS.DBMS_EXPORT_EXTENSION.GET_DOMAIN_INDEX_METADATA('CTRY_SPATIAL_IDX','PTG','SDO_INDEX_METHOD_10I','MDSYS',11.02.00.00.00,newblock,0)
> ORA-01403: no data found
> ORA-01403: no data found
> ORA-06512: at "SYS.DBMS_EXPORT_EXTENSION", line 270
> ORA-06512: at line 1
> ORA-06512: at "SYS.DBMS_METADATA", line 8360
>
>
> To isolate - I picked one failing table - PTG.COUNTRY and a standalone
> export produces the same error
>
> expdp "'/ as sysdba'" directory=dbadmpdir dumpfile=ptg_country.dmp
> full=no tables=PTG.COUNTRY logfile=exp_ptg_country.log
>
> Processing object type TABLE_EXPORT/TABLE/STATISTICS/TABLE_STATISTICS
> ORA-39127: unexpected error from call to local_str :=
> SYS.DBMS_EXPORT_EXTENSION.GET_DOMAIN_INDEX_METADATA('CTRY_SPATIAL_IDX','PTG','SDO_INDEX_METHOD_10I','MDSYS',11.02.00.00.00,newblock,0)
> ORA-01403: no data found
> ORA-01403: no data found
> ORA-06512: at "SYS.DBMS_EXPORT_EXTENSION", line 270
> ORA-06512: at line 1
> ORA-06512: at "SYS.DBMS_METADATA", line 8360
> Processing object type TABLE_EXPORT/TABLE/INDEX/DOMAIN_INDEX/INDEX
> . . exported "PTG"."COUNTRY" 0 KB 0
> rows
>
> Oddly enough - on a VISION environment - this error fails to reproduce
>
> Any thoughts on what might be causing this ? I'd appreciate any insights...
>
> Thanks,
>
> --Rajesh
>

-- 

*--*
*BR*
*Sumit Tyagi*
*+91-7829543355*

--
http://www.freelists.org/webpage/oracle-l
Received on Tue May 27 2014 - 18:45:35 CEST

Original text of this message