ORA-12815: value for INSTANCES must be greater than 0

Cause : PRAALLE Lpraaemtre pseicfiyn gnmubre fo nisatnecsm uts eb apsoiitv eitneegro rD EAFUTL

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

sepcfiya opstiiev nitgee ro rDFEALUTf o rISNTNACSE fi aprlalleims carsosi ntsacne si sdseierd.

update : 28-07-2017
ORA-12815

ORA-12815 - value for INSTANCES must be greater than 0
ORA-12815 - value for INSTANCES must be greater than 0

  • ora-02705 : osnpol: polling of communication channel failed
  • ora-39216 : object type "string"."string" hashcode mismatch
  • ora-29845 : indextype does not support local domain index on string partitioned table
  • ora-26566 : Couldn't open connect to string
  • ora-16501 : the Data Guard broker operation failed
  • ora-27057 : cannot perform async I/O to file
  • ora-19906 : recovery target incarnation changed during recovery
  • ora-02832 : Segment deallocation failed - segment not on list
  • ora-23318 : a ddl failure has occurred
  • ora-23538 : cannot explicitly refresh a NEVER REFRESH materialized view ("string")
  • ora-14009 : partition bound may not be specified for a LOCAL index partition
  • ora-12822 : duplicate option in PARALLEL clause
  • ora-12924 : tablespace string is already in force logging mode
  • ora-32109 : invalid column or parameter position
  • ora-27416 : BYDAY= clause in repeat interval or calendar contains an invalid weekday
  • ora-16211 : unsupported record found in the archived redo log
  • ora-30013 : undo tablespace 'string' is currently in use
  • ora-16777 : unable to find the destination entry of a standby database in V$ARCHIVE_DEST
  • ora-36810 : (XSTBLFUNC05) Analytic workspace object number does not exist.
  • ora-04000 : the sum of PCTUSED and PCTFREE cannot exceed 100
  • ora-30557 : function based index could not be properly maintained
  • ora-04099 : trigger 'string' is valid but not stored in compiled form
  • ora-14052 : partition-extended table name syntax is disallowed in this context
  • ora-09284 : sllfop: cannot allocate read buffer
  • ora-36267 : (XSCGMDLAGG09) workspace object has no dimensions, so it cannot have a qualified data reference.
  • ora-19501 : read error on file "string", blockno string (blocksize=string)
  • ora-26030 : index string.string had string partitions made unusable due to:
  • ora-10944 : trace name context forever
  • ora-15065 : hash collision for diskgroup names 'string' and 'string'
  • ora-15076 : Emulating I/O errors on the OSM disk
  • 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.