ORA-28116: insufficient privileges to do direct path access

Cause : Users with insufficient privileges attempting to do direct path access of tables with fine grain access control policies.

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

Ask the database administrator to do the operation. Note that users can work with security administrator to temporarily drop/disable the policies at time of export, import, or load, but this has security implication, and thus access of the database must be controlled carefully.

update : 22-06-2017
ORA-28116

ORA-28116 - insufficient privileges to do direct path access
ORA-28116 - insufficient privileges to do direct path access

  • ora-13919 : Cannot specify values for parameter "string" and for parameter "string"
  • ora-25180 : PCTTHRESHOLD only valid for certain table organizations
  • ora-24909 : call in progress. Current operation cancelled
  • ora-27035 : logical block size is invalid
  • ora-37178 : column string has no values
  • ora-27507 : IPC error disconnecting from a port
  • ora-14408 : partitioned index contains subpartitions in a different tablespace
  • ora-26040 : Data block was loaded using the NOLOGGING option
  • ora-38796 : Not enough flashback database log data to undo FLASHBACK.
  • ora-28363 : buffer provided not large enough for output
  • ora-25254 : time-out in LISTEN while waiting for a message
  • ora-03288 : both FREELIST GROUP and INSTANCE parameters may not be specified
  • ora-27153 : wait operation failed
  • ora-01624 : log string needed for crash recovery of instance string (thread string)
  • ora-08005 : specified row does not exist
  • ora-19664 : file type: string, file name: string
  • ora-06001 : NETASY: port set-up failure
  • ora-00357 : too many members specified for log file, the maximum is string
  • ora-13633 : The task string was interrupted and needs to be resumed.
  • ora-10900 : extent manager fault insertion event #string
  • ora-12043 : invalid CREATE MATERIALIZED VIEW option
  • ora-13637 : Executing or modifying task string is disallowed until the task is reset to its initial state.
  • ora-30510 : system triggers cannot be defined on the schema of SYS user
  • ora-25231 : cannot dequeue because CONSUMER_NAME not specified
  • ora-14630 : subpartition resides in offlined tablespace
  • ora-23411 : materialized view "string"."string" is not in refresh group "string"."string"
  • ora-31604 : invalid string parameter "string" for object type string in function string
  • ora-16127 : stalled waiting for additional transactions to be applied
  • ora-16159 : Cannot change protected standby destination attributes
  • ora-12835 : No instances are active in the GLOBAL_VIEW_ADMIN_GROUP
  • 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.