0 Replies Latest reply on Jul 24, 2013 6:45 PM by amin_adatia

    v4 Last AWR Report

    amin_adatia

      Running as SYS

       

      The job runs for a while and then when I cancel because it has been running for more than 3 minutes, an error message pops up

       

      An error was encountered performing the requested operation:

       

       

      ORA-20019: Database/Instance 1924331302/1 was re-started during specified snapshot interval 3395-3396

      ORA-06512: at "SYS.DBMS_SWRF_REPORT_INTERNAL", line 9875

      ORA-06512: at "SYS.DBMS_SWRF_REPORT_INTERNAL", line 1226

      ORA-06512: at "SYS.DBMS_WORKLOAD_REPOSITORY", line 889

      ORA-06512: at line 1

      ORA-06512: at line 13

       

       

      Vendor code 20019

       

      Don't I want to know what happened to cause the re-start? Something does not make sense; why cannot the job just skip the bad stuff? I realize this may have nothing to do with SQL Developer!

       

      Also can we get a message when the user trying to run the ARW/ASH reports does not have the required privileges instead of just some message like

       

      An error was encountered performing the requested operation:

       

       

      ORA-06550: line 8, column 62:

      PL/SQL: ORA-00942: table or view does not exist

      ORA-06550: line 8, column 1:

      PL/SQL: SQL Statement ignored

      ORA-06550: line 10, column 46:

      PL/SQL: ORA-00942: table or view does not exist

      ORA-06550: line 10, column 1:

      PL/SQL: SQL Statement ignored

      ORA-06550: line 14, column 10:

      PL/SQL: ORA-00904: : invalid identifier

      ORA-06550: line 13, column 13:

      PL/SQL: SQL Statement ignored

      ORA-06550: line 17, column 25:

      PLS-00364: loop index variable 'RC' use is invalid

      ORA-06550: line 17, column 4:

      PL/SQL: Statement ignored

      06550. 00000 -  "line %s, column %s:\n%s"

      *Cause:    Usually a PL/SQL compilation error.

      *Action:

      Vendor code 6550