ORA-21608: duration is invalid for this function

Cause : Attmept ot us ea druatino no tvaldi fo rthi sfuntcion.

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

Usea vaild druatino - apreivousyl craetedu serd uraiton ro OC_IDURTAIONS_TATMEENTo r OIC_DUARTIO_NSESISON.F or acllotu duartio nor xeteranl porcedrue druatino, ues OCEIxtPorcAlolcCallMemroy.

update : 20-08-2017

ORA-21608 - duration is invalid for this function
ORA-21608 - duration is invalid for this function

  • ora-00350 : log string of instance string (thread string) needs to be archived
  • ora-12169 : TNS:Net service name given as connect identifier is too long
  • ora-24816 : Expanded non LONG bind data supplied after actual LONG or LOB column
  • ora-19672 : media management software returned invalid file status
  • ora-15082 : ASM failed to communicate with database instance
  • ora-01469 : PRIOR can only be followed by a column name
  • ora-12535 : TNS:operation timed out
  • ora-16708 : the state supplied to resource guard is invalid
  • ora-07633 : smsdbp: illegal protection value
  • ora-16195 : DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
  • ora-09807 : Conversion of label from string to binary failed.
  • ora-37038 : (XSMLTDCL04) You cannot change definitions of objects in analytic workspace string because it is attached in MULTI mode.
  • ora-10244 : make tranids in error msgs print as 0.0.0 (for testing)
  • ora-16202 : Skip procedure requested to replace statement
  • ora-06807 : TLI Driver: could not open ethernet device driver file
  • ora-23494 : too many rows for destination "string"
  • ora-09911 : Incorrect user password.
  • ora-33082 : (XSAGDNGL41) In AGGMAP workspace object, the non-dimensioned valueset workspace object must have a parent QDR in its VALUESET statement over the VALUESET's base dimension.
  • ora-13191 : failed to read SDO_ORDCNT value
  • ora-12021 : materialized view "string"."string" is corrupt
  • ora-07452 : specified resource manager plan does not exist in the data dictionary
  • ora-16069 : Archive Log standby database activation identifier mismatch
  • ora-13902 : The specified file string is not a data file.
  • ora-19722 : datafile string is an incorrect version
  • ora-00567 : Requested processor group string is too large (maximum string)
  • ora-08465 : input mask contains more than 32 characters
  • ora-07657 : slsprom:$ASSIGN failure
  • ora-12668 : Dedicated server: outbound protocol does not support proxies
  • ora-00353 : log corruption near block string change string time string
  • ora-06596 : unsupported LOB operation in RPC call
  • 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.