ORA-00600: error in Queue Table SYS.SYS$SERVICE_METRICS_TAB

If this error is coming in Oracle database, then take downtime and do the following:

  Drop the queue table -

exec dbms_aqadm.drop_queue_table( queue_table=>'SYS.SYS$SERVICE_METRICS_TAB', force => TRUE)

select object_name, object_type from dba_objects where object_name like '%SYS$SERVICE_%';

----> no rows should be returned.

Follow the below steps to recreate the queue table.

SQL>STARTUP

SQL>alter system enable restricted session;

SQL>@$ORACLE_HOME/rdbms/admin/catproc.sql

SQL>@$ORACLE_HOME/rdbms/admin/utlrp.sql

SQL>alter system disable restricted session;

Comments

Post a Comment

Popular posts from this blog

Grid Infrastructure network issue on ODA X5-2

I ran into a situation where client I had supported was having network timeouts and a huge amount of packet drops on their network when trying to connect to their ODA from the application stack.  After many hours (2 days to be exact) of troubleshooting, it was discovered that there was an issue with the Grid Infrastructure network configuration vs what the client's network was configured with. The client's default gateway was set to 10.10.10.1 . However when looking at their network configuration set in the GI, it reflected 10.10.0.0 as this is what Oracle was expecting it to be based off of ipcalc. ipcalc -bnm 10.10.40.42 255.255.0.0 NETMASK=255.255.0.0 BROADCAST=10.10.255.255 NETWORK= 10.10.0.0 ################ [root@oraprd1 .ssh]# oifcfg getif ibbond0  192.168.16.0  global  cluster_interconnect,asm bond0  10.10.0.0  global  public ################ # srvctl config network Network 1 exists Subnet IPv4: 10.10.0.0 /255.255.0.0...
Read more

Upgrade from 11gR2 RAC to 12cR1 RAC using cloning methodology

12.1.0.2 Grid Infrastructure Upgrade: From 11.2.0.4 To 12.1.0.2 Using GI Clone I used the following methodology to upgrade from 11.2.0.4 to 12.1.0.2 RAC.  This is particularly useful from a time perspective to avoid having to do a separate patching when it comes to applying bundle patches (Exadata) or PSUs.  I tested this process in my non-production environment and highly advise you to do the same to ensure the process is seamless. A) Prepare SOURCE GI home (In this case it is 12.1.0.2) to be cloned: ******************************** Follow documentation for "Preparing the Oracle Grid Infrastructure Home for Cloning" at https://docs.oracle.com/database/121/CWADD/clonecluster.htm#CWADD92116 Oracle® Clusterware Administration and Deployment Guide 12c Release 1 (12.1) Part Number E16794-16 ******************************** A01) Stop all databases via srvctl (run by oracle) srvctl stop database -d {db_unique_name} A02) Stop CRS (run by root) export ORACLE_HO...
Read more

RMAN-10038: database session for channel prm3 terminated unexpectedly

Problem: I had an issue where I was trying to build a 1.7 TB Data Guard environment and kept receiving the highlighted error below.  I thought it was some type of fluke so I restarted the job 2 more times only to receive the same error. Fix: After researching the issue, I found it was because the sqlnet.ora needed to be configured correctly.  I added the entry " SQLNET.EXPIRE_TIME = 10 " to the sqlnet.ora on both the source and the target database servers under the RDBMS $ORACLE_HOME/network/admin.  Upon restarting the RMAN active database standby build, it was able to move past this error and built successfully. Starting backup at 07-MAY-17 channel prm1: starting datafile copy input datafile file number=00003 name=+DATA/testdb/datafile/undotbs1.262.940412881 channel prm2: starting datafile copy input datafile file number=00129 name=+DATA/testdb/datafile/welldoc1.390.940509955 channel prm3: starting datafile copy input datafile file number=00130 name=+DATA/...
Read more