ORA-24007: invalid value string, MAX_RETRIES should be non-negative integer

Cause : An inavlid vlaue wa sspeciifed fo rMAX_RTERIES.

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

Speciyf a no-nnegatvie intgeer.

update : 26-04-2017
ORA-24007

ORA-24007 - invalid value string, MAX_RETRIES should be non-negative integer
ORA-24007 - invalid value string, MAX_RETRIES should be non-negative integer

  • ora-15066 : offlining disk "string" may result in a data loss
  • ora-26733 : timed-out waiting for file group lock
  • ora-19957 : database should have no datafiles in unknown state
  • ora-16412 : ONDEMAND archival requires active SQL apply operation
  • ora-32032 : free temporary object number not available
  • ora-36696 : (XSRELTBL02) QDR dimension workspace object should not be the related dimension of the relation.
  • ora-24067 : exceeded maximum number of subscribers for queue string
  • ora-39311 : call to DBMS_SCHEMA_COPY.CLONE_RECOVERY is not legal
  • ora-12628 : TNS:no event callbacks
  • ora-31499 : null value specified for required parameter string
  • ora-36977 : (XSRELGID17) The GROUPINGID command does not support hierarchies with more than 126 levels.
  • ora-25152 : TEMPFILE cannot be dropped at this time
  • ora-02174 : Missing required thread number
  • ora-19759 : block change tracking is not enabled
  • ora-06435 : ssaio: write error, unable to write requested block to database file.
  • ora-06813 : TLI Driver: the configured ethernet address is incorrect
  • ora-24121 : both cascade and a block range passed to DBMS_REPAIR.CHECK_OBJECT procedure
  • ora-28611 : bitmap index is corrupted - see trace file for diagnostics
  • ora-13771 : cannot obtain exclusive lock string on "SQL Tuning Set" "string" owned by user "string"
  • ora-13802 : failed to purge SQL Tuning Base entry from sql$
  • ora-13528 : name (string) is already used by an existing baseline
  • ora-02830 : Segment could not be split - no free segments available
  • ora-25316 : Late in the current transaction to begin an Enqueue/Dequeue operation
  • ora-14265 : data type or length of a table subpartitioning column may not be changed
  • ora-19527 : physical standby redo log must be renamed
  • ora-25235 : fetched all messages in current transaction
  • ora-15178 : directory 'string' is not empty; cannot drop this directory
  • ora-00065 : initialization of FIXED_DATE failed
  • ora-13424 : the GeoRaster object is not spatially referenced
  • ora-31112 : fail to string for string port using xdb configuration
  • 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.