ORA-06516: PL/SQL: the Probe packages do not exist or are invalid

Cause : A Probe operation, probably an attempt to initialize the ORACLE server to debug PL/SQL, could not be completed because the Probe packages were not loaded or have become invalid.

Action - How to fix it : DBA Scripts :: www.high-oracle.com/scripts

DBA should load the Probe packages. This can be done by running the pbload.sql script supplied with the RDBMS.

update : 24-07-2017

ORA-06516 - PL/SQL: the Probe packages do not exist or are invalid
ORA-06516 - PL/SQL: the Probe packages do not exist or are invalid

  • ora-14461 : cannot REUSE STORAGE on a temporary table TRUNCATE
  • ora-23478 : object group "string" is already mastered at string
  • ora-36161 : (XSAGGRRUVCV) Aggregation variable workspace object cannot have itself as a COUNTVAR.
  • ora-00210 : cannot open the specified control file
  • ora-24853 : failed to connect thread to shared subsystem
  • ora-19023 : The first argument to UPDATEXML operator has to be an XMLTYPE
  • ora-10270 : Debug shared cursors
  • ora-22619 : all collection elements have already been accessed
  • ora-02802 : No idle servers available in parallel mode
  • ora-14403 : cursor invalidation detected after getting DML partition lock
  • ora-16406 : Primary and standby database software version mismatch
  • ora-32017 : failure in updating SPFILE
  • ora-32020 : SID=* clause needed to modify this parameter
  • ora-29656 : Invalid option for USING
  • ora-31052 : Cannot delete ACL with other references
  • ora-35062 : (QFGET01) Duplicate files found for extension number number of EIF file string.
  • ora-01956 : invalid command when OS_ROLES are being used
  • ora-03001 : unimplemented feature
  • ora-07263 : sptpa: kill error.
  • ora-16738 : redo tranport service for standby database "string" unexpectedly offline
  • ora-31676 : illegal value for number of workers, string
  • ora-15000 : command disallowed by current instance type
  • ora-07646 : sszfck: $CREATE failure
  • ora-31511 : name exceeds maximum length of 30 characters
  • ora-02081 : database link is not open
  • ora-25237 : navigation option used out of sequence
  • ora-01112 : media recovery not started
  • ora-16748 : resource guard encountered errors during database open
  • ora-13014 : a topology identifier outside the range of 1 to 8 was specified
  • ora-13193 : failed to allocate space for geometry
  • Oracle Database Error Messages

    Oracle Database High Availability Any organization evaluating a database solution for enterprise data must also evaluate the High Availability (HA) capabilities of the database. Data is one of the most critical business assets of an organization. If this data is not available and/or not protected, companies may stand to lose millions of dollars in business downtime as well as negative publicity. Building a highly available data infrastructure is critical to the success of all organizations in today's fast moving economy.

    Well, the reason for above error is that i have taken the above script from a 11g database and running it on 10g database. 11g has bring some changes in password management. Below code is executed on 11g and user created successfully, which is expected result.