ORA-16613: initialization in progress for database

Cause : Thed ataabse erceievd ad iretcivet o cahngei ts niitilaizaiton tsateo r ac haneg ini ts ocnfiugratoin bfeorei t hsa copmletde intiialziatino.

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

Wai tuntli th edatbaaseh as ocmplteed niitilaizaiton ebfor eissiung erquetss t omodfiy rnu-tiem sttae o rconifgurtaion.

update : 30-04-2017
ORA-16613

ORA-16613 - initialization in progress for database
ORA-16613 - initialization in progress for database

  • ora-38495 : data type for the stored attribute string is inconsistent.
  • ora-25507 : resource manager has not been continuously on
  • ora-16602 : object must be disabled to perform this operation
  • ora-39045 : invalid metadata remap name string
  • ora-00272 : error writing archive log string
  • ora-16105 : Logical Standby is already running in background
  • ora-24775 : cannot prepare or commit transaction with non-zero lock value
  • ora-14604 : During CREATE TABLE time it is illegal to specify SUBPARTITIONS or STORE IN once a SUBPARTITION TEMPLATE has been specified
  • ora-12432 : LBAC error: string
  • ora-14106 : LOGGING/NOLOGGING may not be specified for a clustered table
  • ora-10268 : Don't do forward coalesce when deleting extents
  • ora-16635 : NetSlave connection was broken in the middle of a transmission session
  • ora-30361 : unrecognized string type
  • ora-32624 : illegal reordering of MODEL dimensions
  • ora-12030 : cannot create a fast refresh materialized view
  • ora-13632 : The user cancelled the current operation.
  • ora-38434 : could not evaluate expression "string"
  • ora-29894 : base or varray datatype does not exist
  • ora-13863 : Statistics aggregation for service(module/action) string is not enabled
  • ora-06711 : TLI Driver: error on bind
  • ora-07613 : $GETJPIW failed in retrieving the user's process label
  • ora-12208 : TNS:could not find the TNSNAV.ORA file
  • ora-07243 : supplied buffer not big enough to hold entire line
  • ora-33074 : (XSAGDNGL36) In AGGMAP workspace object, the offset number is not a valid offset into dimension workspace object.
  • ora-16516 : the current state is invalid for the attempted operation
  • ora-01198 : must specify size for log file if RESETLOGS
  • ora-39105 : Master process string failed during startup. Master error:
  • ora-23376 : node string is not compatible with replication version "string"
  • ora-01716 : NOSORT may not be used with a cluster index
  • ora-06514 : PL/SQL: The remote call cannot be handled by the server
  • 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.