Backups failing in Oracle geodatabase

1694
3
09-23-2019 12:27 PM
TCEQGIS_Team
New Contributor II

Our backups have started failing in our Oracle geodatabase. Below is what we are seeing in the logs. Does anyone know of a solution or can provide any suggestions? 

Error in expdp log:

20-SEP-19 22:31:19.788: Processing object type DATABASE_EXPORT/SCHEMA/TABLE/INDEX/DOMAIN_INDEX/INDEX

20-SEP-19 22:31:21.282: ORA-39127: unexpected error from call to local_str := SYS.DBMS_EXPORT_EXTENSION.GET_DOMAIN_INDEX_METADATA('A784_IX1','GDB_ADM','ST_DOMAIN_METHODS','SDE','12.02.00.00.00',newblock,0)

ORA-20083: No ST_SRID supplied in PARAMETERS clause.

ORA-06512: at "SYS.DBMS_EXPORT_EXTENSION", line 274

ORA-06512: at "SYS.DBMS_ODCI", line 228

ORA-06512: at "SDE.ST_DOMAIN_METHODS", line 2723

ORA-06512: at "SDE.ST_DOMAIN_METHODS", line 2696

ORA-06512: at line 1

ORA-06512: at "SYS.DBMS_SQL", line 1721

ORA-06512: at "SYS.DBMS_ODCI", line 220

ORA-06512: at line 1

ORA-06512: at "SYS.DBMS_SQL", line 1721

ORA-06512: at "SYS.DBMS_EXPORT_EXTENSION", line 250

ORA-06512: at line 1

ORA-06512: at "SYS.DBMS_EXPORT_EXTENSION", line 274

ORA-06512: at "SYS.DBMS_ODCI", line 228

ORA-06512: at "SDE.ST_DOMAIN_METHODS", line 2723

ORA-06512: at "SDE.ST_DOMAIN_METHODS", line 2696

ORA-06512: at line 1

ORA-06512: at "SYS.DBMS_SQL", line 1721

ORA-06512: at "SYS.DBMS_ODCI", line 220

ORA-06512: at line 1

ORA-06512: at "SYS.DBMS_SQL", line 1721

ORA-06512: at "SYS.DBMS_EXPORT_EXTENSION", line 250

ORA-06512: at line 1

ORA-06512: at "SYS.DBMS_METADATA", line 10071

ORA-06512: at "SYS.DBMS_SYS_ERROR", line 95

20-SEP-19 22:31:27.244: Processing object type DATABASE_EXPORT/SCHEMA/TABLE/POST_TABLE_ACTION

0 Kudos
3 Replies
ChristianWells
Esri Regular Contributor

Can you check the "PARAMETERS" and "DOMIDX_OPSTATUS" of the index in Oracle?

select * from all_indexes Where index_name like 'A784_IX1';

If PARAMETERS is blank or DOMIDX_OPSTATUS is marked as "FAILED", we will need to update the index properties in the Geodatabase through ArcCatalog.

0 Kudos
by Anonymous User
Not applicable

Thank you, Christian. It was blank. The index wasn't visible from ArcCatalog, but was visible from Toad. We dropped the index using Toad and then used ArcCatalog to release the locks and create a new index. Thanks for your help.

0 Kudos
ChristianWells
Esri Regular Contributor

I'm glad to hear this resolved the issue, Chris. Have a good day!

0 Kudos