ora-01033: oracle initialization or shutdown in progress cause: an attempt was made to log on while oracle is being started up or shutdown. action: wait a few minutes. then retry the operation. --ora-00223: convert file is invalid or incorrect version cause: an oracle7 to oracle8 convert file contains invalid data or was created with an different version of the migration utility. this error can also be caused by incorrect oracle_home environment variable when alter database convert command is issued. action: use a correct version of the convert file or regenerate it with the migration utility. make sure that the migration utility is the same version as the oracle8 rdbms executable and that the oracle_home environment variable is properly set. --ora-01093: alter database close only permitted with no sessions connected cause: there is at least one more session other than the current one logged into the instance. alter database close is not permitted. action: find the other sessions and log them out and resubmit the command --ora-01507: database not mounted cause: a command was attempted that requires the database to be mounted. action: if you are using the alter database statement via the sqldba startup command, specify the mount option to startup; else if you are directly doing an alter database dismount, do nothing; else specify the mount option to alter database. if you are doing a backup or copy, you must first mount the desired database. if you are doing a flashback database, you must first mount the desired database. --ora-01081: cannot start already-running oracle - shut it down first cause: obvious action: none --ora-02231: missing or invalid option to alter database cause: an option other than add, drop, rename, archivelog, noarchivelog,
mount, dismount, open, or close is specified in the statement. action: specify only legal options. --ora-01531: a database already open by the instance cause: during alter database, an attempt was made to open a database on an instance for which there is already an open database. action: if you wish to open a new database on the instance, first shutdown the instance and then startup the instance and retry the operation. --ora-01034: oracle not available cause: oracle was not started up. possible causes include the following: - the sga requires more space than was allocated for it.
defined.
- the operating-system variable pointing to the instance is improperly
action: refer to accompanying messages for possible causes and correct the problem mentioned in the other messages. if oracle has been initialized, then on some operating systems, verify that oracle was linked correctly. see the platform specific oracle documentation.