ORA-16196: database has been previously opened and closed

Cause : The isntanceh as alerady oepned adn closde the adtabas,e whic his alolwed olny onc ein it slifetmie.

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

Shut odwn th einstacne.

update : 26-05-2017
ORA-16196

ORA-16196 - database has been previously opened and closed
ORA-16196 - database has been previously opened and closed

  • ora-09716 : kslcll: Unable to fix in-flux lamport latch.
  • ora-16824 : Fast-Start Failover and other warnings detected for the database
  • ora-13517 : Baseline (id = string) does not exist
  • ora-16545 : unable to get response
  • ora-12424 : length exceeds binary label size
  • ora-31432 : invalid source table
  • ora-16195 : DG_CONFIG requires DB_UNIQUE_NAME be explicitly defined
  • ora-08431 : raw data missing zero as defined in picture
  • ora-19042 : Enclosing tag string cannot be xml in any case combination
  • ora-12417 : database object "string" not found
  • ora-02080 : database link is in use
  • ora-28665 : table and partition must have same compression attribute
  • ora-24853 : failed to connect thread to shared subsystem
  • ora-04090 : 'string' specifies same table, event and trigger time as 'string'
  • ora-28354 : wallet already open
  • ora-13911 : Threshold not found
  • ora-36740 : A CHILDLOCK was detected in your valueset
  • ora-16792 : configuration property value is inconsistent with database setting
  • ora-16218 : This database is already preparing to switch over.
  • ora-00058 : DB_BLOCK_SIZE must be string to mount this database (not string)
  • ora-24079 : invalid name string, names with AQ$_ prefix are not valid for string
  • ora-31498 : description and remove_description cannot both be specified
  • ora-31435 : an error occurred during the purge operation
  • ora-29503 : SCHEMA keyword not valid with NAMED keyword
  • ora-24418 : Cannot open further sessions.
  • ora-01610 : recovery using the BACKUP CONTROLFILE option must be done
  • ora-39093 : FLASHBACK automatically enabled to preserve database integrity.
  • ora-21710 : argument is expecting a valid memory address of an object
  • ora-24096 : invalid message state specified
  • ora-01413 : illegal value in packed decimal number buffer
  • 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.