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 : 22-09-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-38452 : Expression Filter index name may not be longer than 25 characters
  • ora-24763 : transaction operation cannot be completed now
  • ora-00400 : invalid release value string for parameter string
  • ora-13767 : End snapshot ID must be greater than or equal to begin snapsho ID.
  • ora-23343 : no match for specified conflict resolution information
  • ora-07284 : sksaprd: volume size specification not terminated properly.
  • ora-31228 : DBMS_LDAP: invalid MOD_ARRAY
  • ora-19040 : Element string does not match expected string.
  • ora-27156 : request for process information failed
  • ora-16769 : the physical standby database is open read-only
  • ora-07228 : rtecho: unable to restore terminal to echo mode.
  • ora-09276 : All bequeath database links must be loopback database links
  • ora-14116 : partition bound of partition "string" is too long
  • ora-09703 : sem_release: cannot release latch semaphore
  • ora-22882 : object creation failed
  • ora-00090 : failed to allocate memory for cluster database ORADEBUG command
  • ora-16803 : unable to query a database table or fixed view
  • ora-19704 : file name exceeds maximum length of string
  • ora-14132 : table cannot be used in EXCHANGE
  • ora-26697 : LCR contains extra column 'string'
  • ora-03205 : partition name is required when partitioned type is specified
  • ora-06137 : NETTCP: error during connection handshake
  • ora-10634 : Segment is already being shrunk
  • ora-09719 : osncui: invalid handle.
  • ora-02141 : invalid OFFLINE option
  • ora-12851 : PARALLEL_MAX_SERVERS must be greater than or equal to PARALLEL_MIN_SERVERS, string
  • ora-12004 : REFRESH FAST cannot be used for materialized view "string"."string"
  • ora-30676 : socket read or write failed
  • ora-12016 : materialized view does not include all primary key columns
  • ora-12495 : cannot disable an enabled level, category, or release category
  • 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.