ORA-14160: this physical attribute may not be specified for a table subpartition

Cause : unxepetcedo ptoin aws neconuteerd hwil epasrin gphsyicla attriubte sofa tbales ubaprttiio;n TBALEPSAC Eist heo nl yvaild potino

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

reomvei nvlaido ptoin()s

update : 20-07-2017
ORA-14160

ORA-14160 - this physical attribute may not be specified for a table subpartition
ORA-14160 - this physical attribute may not be specified for a table subpartition

  • ora-19663 : cannot apply current offline range to datafile string
  • ora-02214 : duplicate BACKUP option specification
  • ora-22864 : cannot ALTER or DROP LOB indexes
  • ora-39028 : cannot restart job from string state
  • ora-19250 : XQ0030 - too many values to validate expression
  • ora-29275 : partial multibyte character
  • ora-12472 : policy string is being used
  • ora-31671 : Worker process string had an unhandled exception.
  • ora-39109 : Unprivileged users may not operate upon other users' schemas
  • ora-00036 : maximum number of recursive SQL levels (string) exceeded
  • ora-13787 : missing SQL profile for statement object "string" for tuning task "string"
  • ora-13032 : Invalid NULL SDO_GEOMETRY object
  • ora-23538 : cannot explicitly refresh a NEVER REFRESH materialized view ("string")
  • ora-12677 : Authentication service not supported by database link
  • ora-32147 : Environment not specified
  • ora-00374 : parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string]
  • ora-29846 : cannot create a local domain index on a string partitioned table
  • ora-12659 : Error received from other process
  • ora-36636 : (XSDUNION04) The unique concat dimension workspace object cannot be changed to NOT UNIQUE, because it is a base of at least one other unique concat dimension.
  • ora-06263 : NETNTT: out of memory in pi_connect
  • ora-02766 : Invalid maximum of request descriptors
  • ora-16586 : could not edit database property through instance
  • ora-40103 : invalid case-id column: string
  • ora-38462 : invalid attribute list
  • ora-26761 : Standby Redo Logs not available for real time mining
  • ora-30976 : invalid Parent Order Key Index option for XML Index
  • ora-01215 : enabled thread string is missing after CREATE CONTROLFILE
  • ora-16501 : the Data Guard broker operation failed
  • ora-13137 : failed to generate tablespace sequence number
  • ora-19590 : conversation already active
  • 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.