Oracle9i数据库异常关闭后的启动
Oracle9i数据库异常关闭后的启动
正在看的ORACLE教程是:Oracle9i数据库异常关闭后的启动。Oracle shutdown的时候突然断电,导致使用sql/plus启动时无法连接到数据库,具体描述为:connection can not permitted, shut in progress.
到dos 提示符 键入:
c:\> sqlplus /nolog
显示:
sql/plus: Realease9.0.2……..all rights reserved
sql> connect /as sysdba
显示已连接至空闲例程
sql>startup 显示shutdown in progress.
到sqlplus 里面连接:
sys/manager@orcl92 显示信息连接成功。
Sql: select * from tab;
显示norows selected;
表明:没有启动数据库。 后来查阅相关资料:得出解决方法:
到dos 提示符 键入:
c:\> sqlplus /nolog
显示 sql/plus: Realease9.0.2……..all rights reserved
sql> connect /as sysdba
显示已连接至空闲例程
sql> startup force
显示:已启动。数据库已正常启动。
也可以先将 windows services中将oraclehome92 service 停止,再启动oracle enterprise manager console,选择独立启动,选择数据库,点击orcl(全局数据库名),弹出对话框,输入用户名system密码password,连接身份:sysdba,选择例程,配置,在一般信息标签下将例程状态先改为关闭,在打开。如果提示oraclehome92 service 停止,则将这个服务启动起来,再启动数据库,也可解决问题。
附:startup force 强制启动一个没有关闭或没能正常启动的数据库;过程:先关闭实例,再启动。
Startup restrict 以限制模式启动数据库,从而限制访问数据库,只有具有 restricted session 权限的用户能与数据库连接
alter system [enable/disable] restricted session 在数据库打开后,该语句启动或关闭访问限制功能。如果相对主结构做更改或想得到导出一致性,应将数据库设置为限制模式。 只有具有alter system权限,才可以用alter system [enable/disable] restricted session 命令改变数据库的可用性。
当一个实例以nomount状态启动时,只能访问sga读取数据的视图。关于 v$thread,v$controlftle等信息从sga 读取数据的词典视图。当数据库被装配时,关于 v$thread,v$controlftle等信息从控制文件中被读出。
分析,当数据库异常关闭时,shutdown在程序里没有退出,因此启动实例时检测到shutdown,则系统报错。因此需要先关闭数据库,再启动数据库。

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Full table scanning may be faster in MySQL than using indexes. Specific cases include: 1) the data volume is small; 2) when the query returns a large amount of data; 3) when the index column is not highly selective; 4) when the complex query. By analyzing query plans, optimizing indexes, avoiding over-index and regularly maintaining tables, you can make the best choices in practical applications.

InnoDB's full-text search capabilities are very powerful, which can significantly improve database query efficiency and ability to process large amounts of text data. 1) InnoDB implements full-text search through inverted indexing, supporting basic and advanced search queries. 2) Use MATCH and AGAINST keywords to search, support Boolean mode and phrase search. 3) Optimization methods include using word segmentation technology, periodic rebuilding of indexes and adjusting cache size to improve performance and accuracy.

Yes, MySQL can be installed on Windows 7, and although Microsoft has stopped supporting Windows 7, MySQL is still compatible with it. However, the following points should be noted during the installation process: Download the MySQL installer for Windows. Select the appropriate version of MySQL (community or enterprise). Select the appropriate installation directory and character set during the installation process. Set the root user password and keep it properly. Connect to the database for testing. Note the compatibility and security issues on Windows 7, and it is recommended to upgrade to a supported operating system.

The difference between clustered index and non-clustered index is: 1. Clustered index stores data rows in the index structure, which is suitable for querying by primary key and range. 2. The non-clustered index stores index key values and pointers to data rows, and is suitable for non-primary key column queries.

MySQL is an open source relational database management system. 1) Create database and tables: Use the CREATEDATABASE and CREATETABLE commands. 2) Basic operations: INSERT, UPDATE, DELETE and SELECT. 3) Advanced operations: JOIN, subquery and transaction processing. 4) Debugging skills: Check syntax, data type and permissions. 5) Optimization suggestions: Use indexes, avoid SELECT* and use transactions.

In MySQL database, the relationship between the user and the database is defined by permissions and tables. The user has a username and password to access the database. Permissions are granted through the GRANT command, while the table is created by the CREATE TABLE command. To establish a relationship between a user and a database, you need to create a database, create a user, and then grant permissions.

MySQL supports four index types: B-Tree, Hash, Full-text, and Spatial. 1.B-Tree index is suitable for equal value search, range query and sorting. 2. Hash index is suitable for equal value searches, but does not support range query and sorting. 3. Full-text index is used for full-text search and is suitable for processing large amounts of text data. 4. Spatial index is used for geospatial data query and is suitable for GIS applications.

MySQL and MariaDB can coexist, but need to be configured with caution. The key is to allocate different port numbers and data directories to each database, and adjust parameters such as memory allocation and cache size. Connection pooling, application configuration, and version differences also need to be considered and need to be carefully tested and planned to avoid pitfalls. Running two databases simultaneously can cause performance problems in situations where resources are limited.
