ORA-13619: The procedure argument string is greater than the maximum allowable length of string characters.

Cause : Teh sue rattepmtde ot aps sac hraatce ragruemn ttahti st o olnog.

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

Sohretnt h esepcfiide hcaarcetra rugmneta n drter yteh poeartoin.

update : 28-05-2017
ORA-13619

ORA-13619 - The procedure argument string is greater than the maximum allowable length of string characters.
ORA-13619 - The procedure argument string is greater than the maximum allowable length of string characters.

  • ora-29274 : fixed-width multibyte character set not allowed for a URL
  • ora-01982 : invalid auditing option for tables
  • ora-12001 : cannot create log: table 'string' already has a trigger
  • ora-19033 : schema specified in the XML document does not match the schema parameter
  • ora-06544 : PL/SQL: internal error, arguments: [string], [string], [string], [string], [string], [string], [string], [string]
  • ora-32037 : unsupported use of LEVEL in membership condition
  • ora-32331 : type "string"."string" is incompatible with the master site
  • ora-16789 : missing standby redo logs
  • ora-33003 : (XSAGDIMDROP) workspace object, to be transformed during data load, must be a base dimension and not otherwise referenced in the AGGMAP.
  • ora-29258 : buffer too small
  • ora-07591 : spdde: $GETJPIW failure
  • ora-28334 : column is already encrypted
  • ora-06975 : X.25 Driver: connect to host failed
  • ora-12042 : cannot alter job_queue_processes in single process mode
  • ora-01516 : nonexistent log file, datafile, or tempfile "string"
  • ora-01222 : MAXINSTANCES of string requires MAXLOGFILES be at least string, not string
  • ora-01763 : update or delete involves outer joined table
  • ora-00308 : cannot open archived log 'string'
  • ora-16714 : the value of property string is inconsistent with the database setting
  • ora-19232 : XQ0012 - imported schemas violate validity rules
  • ora-22921 : length of input buffer is smaller than amount requested
  • ora-24383 : Overflow segment of an IOT cannot be described
  • ora-13913 : The threshold cannot be set when SYSAUX is offline.
  • ora-22130 : buffer size [string] is less than the required size [string]
  • ora-01198 : must specify size for log file if RESETLOGS
  • ora-02076 : sequence not co-located with updated table or long column
  • ora-13614 : The template string is not compatible with the current advisor.
  • ora-31399 : Cannot contact LDAP server string at port number
  • ora-12070 : cannot offline instantiate materialized view "string"."string"
  • ora-15094 : attempted to write to file opened in read only mode
  • 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.