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 : 21-08-2017
ORA-24272

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

  • ora-07479 : scgcmn: cannot open or convert lock.
  • ora-38770 : FLASHBACK DATABASE failed during recovery.
  • ora-01242 : data file suffered media failure: database in NOARCHIVELOG mode
  • ora-07478 : scgcmn: cannot get lock status.
  • ora-01256 : error in locking database file string
  • ora-30204 : buffer is not large enougth
  • ora-19400 : System type conflict with object SYS.string
  • ora-16236 : Logical Standby metadata operation in progress
  • ora-00374 : parameter db_block_size = string invalid ; must be a multiple of string in the range [string..string]
  • ora-22278 : must update the LOB only through the LOB buffers
  • ora-25295 : Subscriber is not allowed to dequeue buffered messages
  • ora-33557 : (MAINTCHK01) You cannot string values of dimension workspace object during a loop over it.
  • ora-01180 : can not create datafile 1
  • ora-35021 : (QFCHECK08) The EIF file definition of workspace object has some partitions that are not present in the existing Analytic Workspace object.
  • ora-24102 : invalid prefix for generate_job_name
  • ora-19862 : backup pieces must be validated before accessing results
  • ora-16169 : LGWR network server invalid parameters
  • ora-31524 : could not find change set string for CDC change table string.string
  • ora-28151 : more than one user name specified for command
  • ora-07209 : sfofi: file size limit was exceeded.
  • ora-02172 : The PUBLIC keyword is not appropriate for a disable thread
  • ora-19256 : XQ0036 - missing type definitions in imported module
  • ora-10865 : Control tracing of notification operations
  • ora-12168 : TNS:Unable to contact LDAP Directory Server
  • ora-06521 : PL/SQL: Error mapping function
  • ora-00706 : error changing format of file 'string'
  • ora-12021 : materialized view "string"."string" is corrupt
  • ora-25191 : cannot reference overflow table of an index-organized table
  • ora-38425 : attribute set used for an index object may not be unassigned
  • ora-30566 : Index maintainence clause not allowed for this command
  • 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.