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 : 25-05-2017

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

  • ora-12483 : label not in OS system accreditation range
  • ora-31445 : invalid lock handle while acquiring lock on string
  • ora-01755 : Must specify an extent number or block number
  • ora-29397 : cannot grant/revoke switch privilege for string
  • ora-07482 : snlmini: cannot create lock manager instance.
  • ora-38855 : cannot mark instance string (redo thread string) as enabled
  • ora-02456 : The HASH IS column specification must be NUMBER(*,0)
  • ora-02801 : Operations timed out
  • ora-24794 : no active DTP service found
  • ora-28353 : failed to open wallet
  • ora-01681 : max # extents (string) reached in LOB segment in tablespace string
  • ora-27011 : skgfrd: cannot read from file opened for write
  • ora-21301 : not initialized in object mode
  • ora-04076 : invalid NEW or OLD specification
  • ora-24322 : unable to delete an initialized mutex
  • ora-06503 : PL/SQL: Function returned without value
  • ora-07704 : error in archive text: need ':' after device name
  • ora-01494 : invalid SIZE specified
  • ora-12497 : maximum combined categories exceeds string
  • ora-01918 : user 'string' does not exist
  • ora-12566 : TNS:protocol error
  • ora-17505 : ksfdrsz:string Failed to resize file to size string blocks
  • ora-06574 : Function string references package state, cannot execute remotely
  • ora-27163 : out of memory
  • ora-25304 : Cannot use priority order queues for capture LCRs
  • ora-06002 : NETASY: port read failure
  • ora-27016 : skgfcls: sbtinfo returned error
  • ora-14051 : invalid ALTER MATERIALIZED VIEW option
  • ora-37603 : (XSPGERRTEMPSYSTEM) Ran out of temporary storage while writing to a system temporary analytic workspace. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-31103 : Resource locked in shared mode. Cannot add exclusive lock
  • 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.