ORA-24272: initialization value must be either F or T

Cause : Teh niiitailztaino avleu ums tb eetihre Fo rT .Av auleo tehrt hna Fo rTw a ssepcfiide.

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

Crorcett h eiintailziaito nvlau eadn ereexctuet h eAIP acl.l

update : 23-06-2017
ORA-24272

ORA-24272 - initialization value must be either F or T
ORA-24272 - initialization value must be either F or T

  • ora-36204 : (XSAGOP04N) In AGGMAP workspace object, the NAOPERATOR string must be HFIRST, HLAST or HEVEN.
  • ora-30485 : missing ORDER BY expression in the window specification
  • ora-12514 : TNS:listener does not currently know of service requested in connect descriptor
  • ora-25404 : lost instance
  • ora-33290 : (DBERR17) Analytic workspace string cannot be attached in the mode you requested because another user has it attached in an incompatible mode.
  • ora-09758 : osnipn: could not check port in name server.
  • ora-12465 : Not authorized for read or write on specified groups or compartments
  • ora-01324 : cannot add file string due to DB_ID mismatch
  • ora-29900 : operator binding does not exist
  • ora-09284 : sllfop: cannot allocate read buffer
  • ora-30043 : Invalid value 'string' specified for parameter 'Undo_Management'
  • ora-30373 : object data types are not supported in this context
  • ora-16635 : NetSlave connection was broken in the middle of a transmission session
  • ora-01254 : cannot end online backup - file string in recovery manager backup
  • ora-02793 : Close of asynchronous I/O failed.
  • ora-27543 : Failed to cancel outstanding IPC request
  • ora-01566 : file specified more than once in ALTER DATABASE
  • ora-01201 : file string header failed to write correctly
  • ora-16516 : the current state is invalid for the attempted operation
  • ora-12807 : process queue could not receive parallel query message
  • ora-30184 : argument type not compatible with a format code
  • ora-32100 : operation invalid on transient object
  • ora-16105 : Logical Standby is already running in background
  • ora-27146 : post/wait initialization failed
  • ora-00364 : cannot write header to new log member
  • ora-28368 : cannot auto-create wallet
  • ora-07272 : spwat: invalid semaphore set id.
  • ora-15066 : offlining disk "string" may result in a data loss
  • ora-15080 : synchronous I/O operation to a disk failed
  • ora-36714 : (XSMXALLOC03) TARGETLOG variable workspace object must have the same data type as TARGET variable workspace object.
  • 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.