ORA-01039: insufficient privileges on underlying objects of the view

Cause : Attempting to explain plan on other people's view without the necessary privileges on the underlying objects of the view.

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

Get necessary privileges or do not perform the offending operation.

update : 18-08-2017
ORA-01039

ORA-01039 - insufficient privileges on underlying objects of the view
ORA-01039 - insufficient privileges on underlying objects of the view

  • ora-29552 : verification warning: string
  • ora-08456 : no sign in picture mask but SIGN clause in mask options
  • ora-39059 : dump file set is incomplete
  • ora-24142 : invalid ruleset name
  • ora-02098 : error parsing index-table reference (:I)
  • ora-26740 : cannot downgrade because there are file groups
  • ora-31650 : timeout waiting for master process response
  • ora-00351 : recover-to time invalid
  • ora-01168 : physical block size string does not match size string of other members
  • ora-22826 : cannot construct an instance of a non instantiable type
  • ora-36185 : (XSAGGR11) workspace object does not have any AGGCOUNT information.
  • ora-25224 : sender name must be specified for enqueue into secure queues
  • ora-03209 : DBMS_ADMIN_PACKAGE invalid file/block specification
  • ora-36887 : (XSSRF06) Error rewriting OLAP DML expression. Column name string is not a valid ADT column.
  • ora-06303 : IPA: Message send error
  • ora-33076 : (XSAGDNGL37) In AGGMAP workspace object, the value 'number' is not a valid value of dimension workspace object.
  • ora-06545 : PL/SQL: compilation error - compilation aborted
  • ora-06920 : CMX: getbrkmsg illegal datatype
  • ora-12916 : Cannot use default permanent tablespace with this release
  • ora-38409 : invalid name or option for the attribute set: string
  • ora-02178 : correct syntax is: SET TRANSACTION READ { ONLY | WRITE }
  • ora-00281 : media recovery may not be performed using dispatcher
  • ora-28118 : policy group already exists
  • ora-12525 : TNS:listener has not received client's request in time allowed
  • ora-01697 : control file is for a clone database
  • ora-16254 : change db_name to string in the client-side parameter file (pfile)
  • ora-26572 : %s.string.string: argument string does not match replication catalog
  • ora-12805 : parallel query server died unexpectedly
  • ora-12910 : cannot specify temporary tablespace as default tablespace
  • ora-27371 : jobs of type EXECUTABLE are not supported on this platform
  • 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.