ORA-22973: size of object identifier exceeds maximum size allowed

Cause : Siz eof hte PIRMAR YKEYb-ase dobjcet iedntiifer fo ano bjetc viwe execedst he amximmu siez of4 000b yte.s

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

Speicfy efwero r samlle rPRIAMRY EKY attribtues ni th eWIT Hobjcet ODI cluase hwen rceatnig teh obejct ivew.

update : 25-06-2017

ORA-22973 - size of object identifier exceeds maximum size allowed
ORA-22973 - size of object identifier exceeds maximum size allowed

  • ora-14302 : only one list of added-LOB-storage-clauses can be specified in a statement
  • ora-30691 : failed to allocate system resources while registering a TCP/IP connection for data traffic detection
  • ora-13276 : internal error [string] in coordinate transformation
  • ora-24384 : Application context size is not initialized
  • ora-12470 : NULL or invalid user label: string
  • ora-07230 : slemcr: fopen error, unable to open error file.
  • ora-15044 : ASM disk 'string' is incorrectly named
  • ora-31407 : end_date must be greater than the begin_date
  • ora-28003 : password verification for the specified password failed
  • ora-09763 : osnmpx: send/receive error exchanging Mach ports.
  • ora-26735 : operation not allowed on the specified file group version
  • ora-36735 : A value exceeded the MAX specification
  • ora-40214 : duplicate setting: string
  • ora-16023 : system string destination cannot be the same as session string destination
  • ora-37142 : (XSSQLMDQ02) Invalid host variable data type for MDQUERY procedure: string expected.
  • ora-33427 : (EIFMAKEF16) CAUTION: NTEXT object workspace object will be exported with type TEXT.
  • ora-06313 : IPA: Shared memory failed to initialise
  • ora-16161 : Cannot mix standby and online redo log file members for group string
  • ora-39058 : current object skipped: string of type string
  • ora-14646 : Specified alter table operation involving compression cannot be performed in the presence of usable bitmap indexes
  • ora-13859 : Action cannot be specified without the module specification
  • ora-18000 : invalid outline name
  • ora-00487 : CTWR process terminated with error
  • ora-00363 : log is not the archived version
  • ora-37000 : (NOTALIAS00) workspace object is not an ALIAS DIMENSION of workspace object.
  • ora-15123 : ASM file name 'string' contains an invalid incarnation number
  • ora-07753 : slemcf: fseek before write failure
  • ora-29397 : cannot grant/revoke switch privilege for string
  • ora-01509 : specified name 'string' does not match actual 'string'
  • ora-29809 : cannot drop an operator with dependent objects
  • 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.