New Features for DBA’s

Subscribe to Posts by Email


 

Subscriber Count

    705

Disclaimer

All information is offered in good faith and in the hope that it may be of use for educational purpose and for Database community purpose, but is not guaranteed to be correct, up to date or suitable for any particular purpose. db.geeksinsight.com accepts no liability in respect of this information or its use. This site is independent of and does not represent Oracle Corporation in any way. Oracle does not officially sponsor, approve, or endorse this site or its content and if notify any such I am happy to remove. Product and company names mentioned in this website may be the trademarks of their respective owners and published here for informational purpose only. This is my personal blog. The views expressed on these pages are mine and learnt from other blogs and bloggers and to enhance and support the DBA community and this web blog does not represent the thoughts, intentions, plans or strategies of my current employer nor the Oracle and its affiliates or any other companies. And this website does not offer or take profit for providing these content and this is purely non-profit and for educational purpose only. If you see any issues with Content and copy write issues, I am happy to remove if you notify me. Contact Geek DBA Team, via geeksinsights@gmail.com

Pages

ORA-06512: at “SYS.KUPV$FT” – impdp failing

This time, impdp failing to create a job for import and failing with following error:-

ORA-06512: at "SYS.KUPV$FT",

In many cases you sometimes stop data pump job or in case of an abnormal end of the Data Pump job (we call it the orphaned job) or using undocumented parameter KEEP_MASTER=Y, the master table remain in the database.

So lets start digging out for orphaned jobs

Script to check Orphaned Pump Jobs

SET lines 140
COL owner_name FORMAT a10;
COL job_name FORMAT a20
COL state FORMAT a12
COL operation LIKE owner_name
COL job_mode LIKE owner_name
SELECT owner_name, job_name, operation, job_mode,
state, attached_sessions
FROM dba_datapump_jobs;

 

By running above script if any rows returned in “not running “ mode that means you will be having orphaned jobs. Typically orphaned jobs state will be “Not Running” state and but in my case some are even in Executing mode which they shouldn’t

As I got the following jobs running at my nose.

 

DBABATCH SYS_EXPORT_FULL_22 Executing

DBABATCH SYS_EXPORT_FULL_22 Not Running
DBABATCH SYS_EXPORT_FULL_22 Not Running
DBABATCH SYS_EXPORT_FULL_22 Not Running
DBABATCH SYS_EXPORT_FULL_22 Not Running
DBABATCH SYS_EXPORT_FULL_22 Not Running

 

Verify that any data pump sessions are running in the database

Continue reading ORA-06512: at “SYS.KUPV$FT” – impdp failing

September 24th, 2012 | Category: Administration | 2 comments - (Comments are closed)

PMON (ospid: nnnn): terminating the instance due to error 481

 

We got a known issue with ASM not coming up in second and subsequently failed to start crs and other resources.

Review grid alert log & os Logs

  • $GRID_HOME/log/<nodename>/alert<nodename>.log

oifcfg shows

$oifcfg –getif

eth0 192.168.2.10 global_clusterinterconnect

eth1 192.168.10.2 global

usb0 169.254.95.0

eth0:2 169.254.96.0

eth0:3 169.254.95.0

 

From 11g R2 (I believe 11.2.0.2 onwards) there is a cluster resource called HAIP which used to manage the cluster interconnects high availability. Prior to 11gr2 if cluster interconnect goes down there will be hang/node evictions depends on the situation. Where in from 11gr2 onwards we can specify up to 3 (as I known) cluster interconnects for a cluster which internally manages with this non-routable IP’s, Essentially, even if one of the physical interface is offline, private interconnect traffic can be routed through the other available physical interface. This leads to highly available architecture for private interconnect traffic.

 

Nice explanation from Riyaz’s Note:-

HAIP, High Availability IP, is the Oracle based solution for load balancing and failover for private interconnect traffic. Typically, Host based solutions such as Bonding (Linux), Trunking (Solaris) etc is used to implement high availability solutions for private interconnect traffic. But, HAIP is an Oracle solution for high availability. During initial start of clusterware, a non-routeable IP address is plumbed on the private subnet specified. That non-routable IP is used by the clusterware and the database for private interconnect traffic.

 

Now back to the issue:-

As you can see the usb0 is attached to the the internal IP (169.254.X.X is an non routable IP’s range internal to OS) , clusterware will confused with this and unable to start the crs resources promptly.

Continue reading PMON (ospid: nnnn): terminating the instance due to error 481

September 24th, 2012 | Category: GridInfrastructure | 4 comments - (Comments are closed)
« Newer Entries