ORA-24324: Service handle not initialized, not allowed, closing-connection Not Allowed

ORA-24324: Service handle not initialized, not allowed, closing-connection not allowed problem <! -- Body start --> C:/Documents and Settings/Administrator> sqlplus "/as sysdba" SQL> startup mount www.2cto.com ORA-01081: unable to start ORACLE that is already running-Please close it first SQL> shutdown -- not closed for a long time, CTRL + CC:/Documents and Settings/Administrator> sqlplus "/as sysdba" connected. SQL> shutdown immediateORA-24324: uninitialized Service handle ORA-24323: not allowed this value ORA-01090: Shutting Down-not allowed to connect SQL> shutdown immediate ORA-24324: not initialized Service handle ORA-24323: this value not allowed ORA-01090: Shutting Down-connection not allowed SQL> shutdown abortORA-01031: insufficient privilegesSQL> quit disconnected C: /clients and Settings/Administrator> sqlplus/nologSQL> conn sys/oracle as sysdba www.2cto.com is connected to the idle routine. SQL> the shutdown abortORACLE routine has been disabled. The SQL> startupORACLE routine has been started. Total System Global Area 1073741824 bytesFixed Size 1253072 bytesVariable Size 281018672 bytesDatabase Buffers 784334848 bytesRedo Buffers 7135232 bytes database loaded. The database has been opened. SQL> from the cause of the problem, we can see that the database is interrupted because the database is closed, and the shutdown command cannot be used to close the database. Therefore, you can think of it, we can use shutdown abort to stop the current database instance when it is disabled normally or cannot work immediately. Www.2cto.com Shutdown abort has the following features: l the Oracle server immediately suspends the SQL statement being processed; l the ORACLE server does not wait for the user currently connected to the database to disconnect; l The data redo log buffer is not written to the disk; l unfinished transactions are not rolled back; l the instance is terminated, but the file is not closed; l ORACLE closes and unmounts the database; l instance recovery is required for the next startup. This is automatic.