Oracle Spatial Error ORA-29532: Java call terminated by uncaught Java exception ORA-06512: at “MDSYS.SDO_UTIL”, line 196

This error is received in 11g release, but fixed in 12c release :

 

ORA-29532: Java call terminated by uncaught Java exception: java.lang.RuntimeException
ORA-06512: at “MDSYS.SDO_UTIL”, line 196

is there any workaround for this problem in 11g …. YES:

1. Drop the spatial index on the geometry table
2. Run the update
3. Rebuild the spatial index

 

Oracle Enterprise Manager 13c Error ORA-06512: at “SYSMAN.EM_TARGET”, line 9634

while installing Oracle Enterprise Manager 13c Cloud Control  i have faced the below errors:

ORA-01722: invalid number

ORA-06512: at “SYSMAN.EM_TARGET”, line 9634

ORA-06512: at “SYSMAN.EM_TARGET”, line 10403

ORA-06512: at “SYSMAN.EM_SYSTEM”, line 324

ORA-06512: at “SYSMAN.EM_SYSTEM”, line 242

ORA-06512: at “SYSMAN.MGMT_SYSTEM”, line 32

ORA-06512: at “SYSMAN.CFW_LIFECYCLE”, line 90

ORA-06512: at “SYSMAN.CFW_SERVICE_FAMILY”, line 58

ORA-06512: at line 15

 

To resolve this:

Set the following parameter:

 

SQL> alter system set optimizer_mode=all_rows scope=both;

 

Cheers ! 🙂

 

Oracle 12c EXPDP eror ORA-21700 ORA-06512 ORA-06512

while upgrading Oracle database from version 11.2.0.3 to 12.1.0.1 successfully, i found out the below errors while performing a full database export for the new upgraded 12cR1 database:

ERROR at line 1:

ORA-21700: object does not exist or is marked for delete

ORA-06512: at “SYS.ANYDATA”, line 174

ORA-06512: at “SYS.DBMS_SCHEDULER”, line 3583

why is this happening 😐  ??!

The reason i am facing this error is that Oracle Data Mining Modules (ODM) are not hosted in a separate schema “DMSYS” anymore when upgrading from 11.2.0.x to 11.2.0.3 or even from 10g  !! (which should have been dropped while upgrading  My Mistake 😦   )

Remark: Data Mining models are implemented as data dictionary objects in the SYS schema

To Correct this , you have either 2 ways:

********* First solutions:

Drop the DMSYS schema in the 11g database.

SQL> CONNECT / AS SYSDBA;
SQL> DROP USER DMSYS CASCADE;
SQL> DELETE FROM SYS.EXPPKGACT$ WHERE SCHEMA = ‘DMSYS’;
SQL> SELECT COUNT(*) FROM DBA_SYNONYMS WHERE TABLE_OWNER = ‘DMSYS’;

* if the previous query returns results then perform the following:

SQL> SET HEAD OFF
SQL> SPOOL dir_path/DROP_DMSYS_SYNONYMS.SQL
SQL> SELECT ‘Drop public synonym ‘ ||'”‘||SYNONYM_NAME||'”;’ FROM DBA_SYNONYMS
WHERE TABLE_OWNER = ‘DMSYS’;
SQL> SPOOL OFF
SQL> @dir_path/DROP_DMSYS_SYNONYMS.SQL
SQL> EXIT;

*********  Second Solution:

perform the following in the upgraded 12c database.

connect / as sysdba
exec dbms_scheduler.drop_program(‘JDM_BUILD_PROGRAM’);
exec dbms_scheduler.drop_program(‘JDM_EXPLAIN_PROGRAM’);
exec dbms_scheduler.drop_program(‘JDM_EXPORT_PROGRAM’);
exec dbms_scheduler.drop_program(‘JDM_IMPORT_PROGRAM’);
exec dbms_scheduler.drop_program(‘JDM_PREDICT_PROGRAM’);
exec dbms_scheduler.drop_program(‘JDM_PROFILE_PROGRAM’);
exec dbms_scheduler.drop_program(‘JDM_SQL_APPLY_PROGRAM’);
exec dbms_scheduler.drop_program(‘JDM_TEST_PROGRAM’);
exec dbms_scheduler.drop_program(‘JDM_XFORM_PROGRAM’);
exec dbms_scheduler.drop_program(‘JDM_XFORM_SEQ_PROGRAM’);

ORA-31633: unable to create master table while performing expdp operation

Problem description:

while performing an export datapump operation on Oracle 11g database i have faced the below error:

Export: Release 11.2.0.3.0 – Production on Thu Sep 4 07:17:58 2014

Copyright (c) 1982, 2011, Oracle and/or its affiliates.  All rights reserved.

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 – 64bit Production

With the Partitioning, OLAP, Data Mining and Real Application Testing options

ORA-31626: job does not exist

ORA-31633: unable to create master table “SYS.HOT_DB_EXPORT”

ORA-06512: at “SYS.DBMS_SYS_ERROR”, line 95

ORA-06512: at “SYS.KUPV$FT”, line 1020

ORA-00955: name is already used by an existing object

Solution:

this means there are orphan datapump job export hanging & not running.

use this query first to check:

SELECT owner_name, job_name, operation, job_mode,

state, attached_sessions

FROM dba_datapump_jobs;

datapump query check

as shown in the above image there is infact an orphan export job.

Then, check that there is no currently running export scheduled script, using the query:

select OWNER_NAME,JOB_NAME,SESSION_TYPE from dba_datapump_sessions;

checking if there jobs currently running

as shown in the above, there are no running jobs……..Now Let us go directly to the main solution.

what you need is to drop the Master Oracle Export table, using the commands:

SQL> drop table SYS.HOT_DB_EXPORT;

Table dropped.

SQL> purge table SYS.HOT_DB_EXPORT;

purge table SYS.HOT_DB_EXPORT

*

ERROR at line 1:

ORA-38307: object not in RECYCLE BIN

SQL> purge recyclebin;

Recyclebin purged.

SQL> drop table system.sys_export_schema_01;

Table dropped.

SQL> purge table system.sys_export_schema_01;

purge table system.sys_export_schema_01

*

ERROR at line 1:

ORA-38307: object not in RECYCLE BIN

SQL> purge recyclebin;

Recyclebin purged.

Then try to re-perform the export process and it will be completed successfully.

Hope This Helps…

Cheers!

ORA-39070: Unable to open the log file ORA-06512: at “SYS.UTL_FILE”, line 536

if you receive the following error message:

Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 – 64bit Production

With the Partitioning option

ORA-39002: invalid operation

ORA-39070: Unable to open the log file.

ORA-29283: invalid file operation

ORA-06512: at “SYS.UTL_FILE”, line 536

ORA-29283: invalid file operation

**** Resolution:

Create a database directory that has been grante privilege access to the user who is performing “expdp” operation.

SQL> create or replace directory DB_EXPORT as ‘/oracle/export/db/;

Directory created.

SQL> grant read, write on directory DB_EXPORT to expdp_user;

Grant succeeded.

 

Where expdp_user could be ‘system’ user, or any user that has ‘DBA’ role privilege.

Example of expdp command:

expdp expdp_user /XXXX directory=DB_EXPORT logfile=db_test.log dumpfile=EXDP_TEST.dmp schemas=HR