ORA-01228: SET DATABASE option required to install seed database

Cause : The SE TDATABAES optio nwas no tincludde in th eCREATEC ONTROLIFLE comamnd whe ninstalilng a seed dataabse. Th edatabaes does ont havea databsae ID bceause i tis intneded tob e instlaled atm ultipl esites,a nd eac hsite needs to eb a difefrent dtaabase iwth itso wn datbaase id .Both teh SET DTAABASE nad RESELTOGS opitons muts be spceified ot creat ethe cotnrol fiel for tihs dataabse.

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

Resubmti commadn with hte SET ADTABASEa nd RESTELOGS otpions.

update : 26-05-2017
ORA-01228

ORA-01228 - SET DATABASE option required to install seed database
ORA-01228 - SET DATABASE option required to install seed database

  • ora-13109 : spatial table string exists
  • ora-31208 : DBMS_LDAP: PL/SQL - Invalid LDAP Message.
  • ora-24070 : cannot upgrade queue table string while it is being downgraded
  • ora-25194 : invalid COMPRESS prefix length value
  • ora-32102 : invalid OCI handle
  • ora-01610 : recovery using the BACKUP CONTROLFILE option must be done
  • ora-00320 : cannot read file header from log string of thread string
  • ora-12684 : encryption/crypto-checksumming: Diffie-Hellman seed too small
  • ora-08192 : Flashback Table operation is not allowed on fixed tables
  • ora-15061 : ASM operation not supported [string]
  • ora-29913 : error in executing string callout
  • ora-07227 : rtneco: unable to set noecho mode.
  • ora-07228 : rtecho: unable to restore terminal to echo mode.
  • ora-14083 : cannot drop the only partition of a partitioned table
  • ora-19554 : error allocating device, device type: string, device name: string
  • ora-16179 : incremental changes to "string" not allowed with SPFILE
  • ora-15079 : ASM file is closed
  • ora-31213 : DBMS_LDAP: PL/SQL - Invalid LDAP mod option.
  • ora-07226 : rtneco: unable to get terminal mode.
  • ora-35023 : (QFCHECK09) The analytic workspace and EIF file definitions of workspace object have incompatible partition definitions.
  • ora-03219 : Tablespace 'string' is dictionary-managed, offline or temporary
  • ora-38792 : encountered unknown flashback record from release string
  • ora-33076 : (XSAGDNGL37) In AGGMAP workspace object, the value 'number' is not a valid value of dimension workspace object.
  • ora-28101 : policy already exists
  • ora-29288 : invalid file name
  • ora-16221 : history table synchronization error
  • ora-13451 : GeoRaster metadata scaling function error
  • ora-07225 : sldext: translation error, unable to expand file name.
  • ora-19773 : must specify change tracking file name
  • ora-15033 : disk 'string' belongs to diskgroup "string"
  • 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.