Don't wanna be here? Send us removal request.
Statistics
We looked inside some of the posts by dr-dba-md-blog and here's what we found interesting.
Average Info
Notes Per Post
0
Likes Per Post
0
Reblog Per Post
0
Reply Per Post
0
Time Between Posts
4 months
Number of Posts By Type
Photo
4
Text
1
Last Seen Tumblr Blogs
Fun Fact
The total number of visits Tumblr.com received during January 2021 is 327 million.
Photo
In awe of the City lights on a Christmas night! (at Makati Shangri-La, Manila) https://www.instagram.com/p/Br2dKCRn2K1/?utm_source=ig_tumblr_share&igshid=12j58rias18d9
0 notes
Photo
A quick ramen lunch after visa application. #mendokoro #ramen #shiyo #gyouza #japan #japanesefood (at Mendokoro Ramenba)
0 notes
Photo
CEVA DBA's Team Dinner "Coming together is a beginning, staying together is progress, and working together is success." – Henry Ford (at NIU, SM Aura Premier)
0 notes
Photo
Our last (maybe not) buddy session with my buddies Aqui and Gelo. #cevadba #buddybuddysystem #keepupthegoodwork (at Starbucks Alphaland)
0 notes
Text
Oracle Orphaned Datapump Jobs
Summary/Error: ORA-20011: Approximate NDV failed: ORA-29913: error in executing ODCIEXTTABLEOPEN callout Findings: Checked the alert log from /home/oracle/scripts/data/OLD_ORA_Alert_PROD_GICLI08P, it contains several error messages: ORA-20011: Approximate NDV failed: ORA-29913: errore nell'esecuzione del callout ODCIEXTTABLEOPEN ORA-20011: Approximate NDV failed: ORA-29913: errore nell'esecuzione del callout ODCIEXTTABLEOPEN ORA-20011: Approximate NDV failed: ORA-29913: errore nell'esecuzione del callout ODCIEXTTABLEOPEN ORA-20011: Approximate NDV failed: ORA-29913: errore nell'esecuzione del callout ODCIEXTTABLEOPEN ORA-20011: Approximate NDV failed: ORA-29913: error in executing ODCIEXTTABLEOPEN callout ORA-20011: Approximate NDV failed: ORA-29913: error in executing ODCIEXTTABLEOPEN callout ORA-20011: Approximate NDV failed: ORA-29913: error in executing ODCIEXTTABLEOPEN callout ORA-20011: Approximate NDV failed: ORA-29913: error in executing ODCIEXTTABLEOPEN callout ORA-20011: Approximate NDV failed: ORA-29913: error in executing ODCIEXTTABLEOPEN callout ORA-20011: Approximate NDV failed: ORA-29913: error in executing ODCIEXTTABLEOPEN callout Checked metalink notes to get the solution Temporary Datapump external tables have not been cleaned up properly. These should have been dropped when the DataPump jobs completed. Note: While datapump is running, oracle internally creates a master table for tracking and putting the datapump status. This master table helps to stop or start the datapump jobs. Solution: 1. Login to the database as sysadm [oracle@glpdlsdbc005 data]$ sqlplus / as sysdba SQL*Plus: Release 11.2.0.4.0 Production on Sun Mar 12 07:34:53 2017 Copyright (c) 1982, 2013, Oracle. All rights reserved. Connected to: Oracle Database 11g Enterprise Edition Release 11.2.0.4.0 - 64bit Production With the Partitioning, OLAP, Data Mining and Real Application Testing options 2. Check that there are no Datapump Jobs running at the same time as the DBMS_STATS Job SQL> SELECT owner_name, job_name, operation, job_mode, state, attached_sessions FROM dba_datapump_jobs WHERE job_name NOT LIKE 'BIN$%' ORDER BY 1,2; 3. Identify the External tables SQL> set pagesize 2000 col owner form a30 col created form a25 col last_ddl_time form a25 col object_name form a30 col object_type form a25SQL> SQL> SQL> SQL> SQL> SQL> select OWNER,OBJECT_NAME,OBJECT_TYPE, status, to_char(CREATED,'dd-mon-yyyy hh24:mi:ss') created ,to_char(LAST_DDL_TIME , 'dd-mon-yyyy hh24:mi:ss') last_ddl_time from dba_objects where object_name like 'ET$%' 2 3 4 5 ; OWNER OBJECT_NAME OBJECT_TYPE STATUS CREATED LAST_DDL_TIME ------------------------------ ------------------------------ ------------------------- ------- -------------------------------------------------- SYSTEM ET$000202430001 TABLE VALID 22-apr-2014 19:14:06 22-apr-2014 19:14:06 SQL> select owner, TABLE_NAME, DEFAULT_DIRECTORY_NAME, ACCESS_TYPE from dba_external_tables order by 1,2 2 ; OWNER TABLE_NAME DEFAULT_DIRECTORY_NAME ACCESS_ ------------------------------ ------------------------------------------------------------ ------- SYSTEM ET$000202430001 DATA_PUMP_DIR CLOB 4. Drop the external Temporary datapump tables SQL> drop table SYSTEM.&tbl_name; Enter value for tbl_name: ET$000202430001 old 1: drop table SYSTEM.&tbl_name new 1: drop table SYSTEM.ET$000202430001 Table dropped. 5. Ensure there is no datapump temporary table SQL> select OWNER,OBJECT_NAME,OBJECT_TYPE, status, to_char(CREATED,'dd-mon-yyyy hh24:mi:ss') created ,to_char(LAST_DDL_TIME , 'dd-mon-yyyy hh24:mi:ss') last_ddl_time from dba_objects where object_name like 'ET$%' 2 3 4 ; no rows selected
0 notes