ORA-26017: global indexes not allowed for direct path load of table partition string

Cause : Glboali ndxeesa red efniedo n atalbe hwend ircet apthl oaidnga snigl epatritoin fo teh tbale.

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

noen

update : 20-08-2017
ORA-26017

ORA-26017 - global indexes not allowed for direct path load of table partition string
ORA-26017 - global indexes not allowed for direct path load of table partition string

  • ora-00321 : log string of thread string, cannot update log file header
  • ora-00359 : logfile group string does not exist
  • ora-36740 : A CHILDLOCK was detected in your valueset
  • ora-23431 : wrong state: string
  • ora-12685 : Native service required remotely but disabled locally
  • ora-15180 : Could not open dynamic library string, error [string]
  • ora-09814 : Unable to expand file name
  • ora-00965 : column aliases not allowed for '*'
  • ora-13270 : OCI error string
  • ora-36767 : (XSAGGCNTMOVE05) workspace object cannot be used as an AGGCOUNT while there are permissions applied to it.
  • ora-26502 : error resignal
  • ora-23387 : replication parallel push dequeue error
  • ora-30940 : Cannot resolve prefix 'string' for QName node 'string'
  • ora-25148 : ONLINE option not permitted
  • ora-39708 : component 'string' not a string component
  • ora-33427 : (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.
  • ora-06447 : ssvpstp: Incorrect parameter passed to function call
  • ora-02799 : Unable to arm signal handler
  • ora-07585 : spdcr: $PARSE failure
  • ora-30741 : WITH HIERARCHY OPTION can be specified only for SELECT privilege
  • ora-00116 : SERVICE_NAMES name is too long
  • ora-27416 : BYDAY= clause in repeat interval or calendar contains an invalid weekday
  • ora-32016 : parameter "string" cannot be updated in SPFILE
  • ora-00711 : new tablespace name is invalid
  • ora-36990 : (XSRELGID07) The level relation workspace object should be dimensioned by a level dimension.
  • ora-36766 : (XSAGGCNTMOVE04) workspace object cannot be used as an AGGCOUNT because it has an AGGCOUNT.
  • ora-26534 : collision: tranID number ignored and purged
  • ora-06906 : CMX: cannot get maximum packet size from CMX
  • ora-21523 : functionality not supported by the server (object mode only)
  • ora-28108 : circular security policies detected
  • 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.