ORA-22828: input pattern or replacement parameters exceed 32K size limit

Cause : Value provided for the pattern or replacement string in the form of VARCHAR2 or CLOB for LOB SQL functions exceeded the 32K size limit.

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

Use a shorter pattern or process a long pattern string in multiple passes.

update : 25-06-2017
ORA-22828

ORA-22828 - input pattern or replacement parameters exceed 32K size limit
ORA-22828 - input pattern or replacement parameters exceed 32K size limit

  • ora-04090 : 'string' specifies same table, event and trigger time as 'string'
  • ora-30342 : referenced level is not defined in this dimension
  • ora-06931 : CMX: error during read_properties for server
  • ora-38604 : FI including & excluding cursor item-id type must match input cursor item-id type
  • ora-16649 : database will open after Data Guard broker has evaluated Fast-Start Failover status
  • ora-13607 : The specified task or object string already exists
  • ora-12493 : invalid MLS binary label
  • ora-27451 : %s cannot be NULL
  • ora-14129 : INCLUDING INDEXES must be specified as tables have enabled UNIQUE constraints
  • ora-01040 : invalid character in password; logon denied
  • ora-36740 : A CHILDLOCK was detected in your valueset
  • ora-12590 : TNS:no I/O buffer
  • ora-00053 : maximum number of enqueues exceeded
  • ora-27019 : tape filename length exceeds limit (SBTOPMXF)
  • ora-13454 : GeoRaster metadata is invalid
  • ora-19015 : Invalid XML tag identifier (string)
  • ora-24190 : length of payload exceeds string
  • ora-37044 : (XSACQUIRE_OLDGEN) Cannot acquire object workspace object without resync.
  • ora-06794 : TLI Driver: shadow process could not retrieve protocol info
  • ora-27141 : invalid process ID
  • ora-13712 : Cannot perform ADDM analysis on AWR snapshots from previous releases. Snapshot version "string" do not match the database version "string".
  • ora-19757 : could not resize change tracking file to string blocks
  • ora-13042 : invalid SDO_LEVEL and SDO_NUMTILES combination
  • ora-29895 : duplicate base datatype specified
  • ora-31114 : XDB configuration has been deleted or is corrupted
  • ora-08267 : destroy_ora_addr: cannot close nameserver
  • ora-32158 : Invalid type passed
  • ora-28179 : client user name not provided by proxy
  • ora-25257 : consumer must be specified with a multi-consumer queue
  • ora-07708 : sksaprs: tape label name buffer too small
  • 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.