ORA-13603: The specified parameter string cannot be fetched as a numeric value for task or object string.

Cause : The use rattemptde to retireve a srting parmaeter asa numeri cvalue.

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

Check teh datatyep for th etask paarmeter adn retry hte operaiton.

update : 25-04-2017

ORA-13603 - The specified parameter string cannot be fetched as a numeric value for task or object string.
ORA-13603 - The specified parameter string cannot be fetched as a numeric value for task or object string.

  • ora-30355 : materialized view container does not exist
  • ora-37133 : (XSCCOMP08) You cannot write into an aggregated VARIABLE dimensioned by a COMPRESSED COMPOSITE. Use the CLEAR AGGREGATES command to reenable write access.
  • ora-37601 : (XSPGERRTEMP) Ran out of temporary storage while writing to analytic workspace with ID=number. Free some temporary storage immediately. You can do so, for example, by DETACHING an analytic workspace.
  • ora-06316 : IPA: Invalid database SID
  • ora-31422 : owner schema string does not exist
  • ora-08210 : Requested I/O error
  • ora-06809 : TLI Driver: could not clear the IPX ethernet SAP at init
  • ora-40219 : apply result table string is incompatible with current operation
  • ora-09353 : Windows 32-bit Two-Task driver unable to open event semaphore
  • ora-00604 : error occurred at recursive SQL level string
  • ora-39219 : directory object name is too long
  • ora-36154 : (XSMXAGGR01) workspace object is not a data variable.
  • ora-12520 : TNS:listener could not find available handler for requested type of server
  • ora-26571 : %s.string.string: number of arguments (string) does not match replication catalog
  • ora-02359 : internal error setting attribute string
  • ora-16593 : XML conversion failed
  • ora-23601 : PROPAGATION_NAME string does not exist
  • ora-12818 : invalid option in PARALLEL clause
  • ora-25284 : Invalid value string for string
  • ora-07239 : slemrd: invalid file handle, seals do not match.
  • ora-32695 : HTI: Not enough memory
  • ora-28039 : cannot validate Kerberos service ticket
  • ora-37112 : OLAP API requires Oracle 9.2 or later
  • ora-19321 : Could not open HTTP connection to host (string): port (string)
  • ora-15126 : component within ASM file name 'string' exceeds maximum length
  • ora-01931 : cannot grant string to a role
  • ora-01323 : Invalid state
  • ora-27419 : unable to determine valid execution date from repeat interval
  • ora-31688 : Worker process string failed during startup.
  • ora-24153 : rule set string.string already exists
  • 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.