Shulou(Shulou.com)05/31 Report--

This article mainly introduces the sqlplus prelim / as sysdba downtime and can not enter how to do, the article is very detailed, has a certain reference value, interested friends must read it!

A system was encountered and the database could not run properly. The process of viewing the database found that the database was down. The result is as follows:

[oracle@xiaowu ~] $ps-ef | grep ora_

Oracle 6218 6161 0 09:39 pts/2 00:00:00 grep ora_

When you log in to the database with a Super Admin user, the system reports an error of ORA-00020. Strangely, the database does not start and the number of processes exceeds the upper limit.

[oracle@xiaowu ~] $sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Wed Oct 23 10:48:12 2013

Copyright (c) 1982, 2009, Oracle. All rights reserved.

ERROR:

ORA-00020:maximum number of processes (500) exceeded

Enter user-name:

To solve the ORA-00020 error, you can increase the parameter value of processes, but you need to start the database normally and log in successfully before you can modify it. But now the database cannot be started normally, so you can't think of a solution. Finally, you can turn to the senior DBA to solve the problem. The method is as follows:

First of all, log in to the database successfully by adding the parameter "- prelim"

[oracle@xiaowu ~] $sqlplus-prelim / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Wed Oct 23 11:10:09 2013

Copyright (c) 1982, 2009, Oracle. All rights reserved.

SQL >

At this point, you can shut down and open the database normally, and install the following command to solve the problem:

Shutdown immediate

Startup

Show parameter processes

Alter system set processes=1000 scope=spfile

Startup force

Show parameter processes

Exit

*

Resolution of ORA-01012: not logged caused by incomplete database shutdown

First of all, use SHUTDOWN NORMAL to shut down the database, when the database is not closed, CTRL+Z stops execution, exit and log in again with SQLPLUS, an error occurs: ORA-01012: not logged on

The experiments are as follows:

First execute

SYS@bys1 > shutdown

ORA-01013: user requested cancel of current operation

[oracle@bys001 ~] $sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Sat Sep 7 09:05:08 2013

Copyright (c) 1982, 2009, Oracle. All rights reserved.

Connected.

ERROR:

ORA-01012: not logged on

Process ID: 0

Session ID: 0 Serial number: 0

SYS@bys1 > startup

ORA-01012: not logged on

SYS@bys1 > conn / as sysdba

Connected to an idle instance.

ERROR:

ORA-01012: not logged on

Process ID: 0

Session ID: 0 Serial number: 0

SYS@bys1 > conn bys/bys

ERROR:

ORA-01090: shutdown in progress-connection is not permitted

Process ID: 0

Session ID: 0 Serial number: 0

Warning: You are no longer connected to ORACLE.

Solution:

If you find the process, just drop kill.

[oracle@bys001 ~] $ps-ef | grep ora_dbw0_

Oracle 6519 1 0 Sep06? 00:00:15 ora_dbw0_bys1

Oracle 20947 20924 0 09:08 pts/0 00:00:00 grep ora_dbw0_

[oracle@bys001] $kill-9 6519

[oracle@bys001 ~] $ps-ef | grep ora_dbw0_

Oracle 20949 20924 0 09:08 pts/0 00:00:00 grep ora_dbw0_

[oracle@bys001 ~] $sqlplus / as sysdba

SQL*Plus: Release 11.2.0.1.0 Production on Sat Sep 7 09:08:22 2013

Copyright (c) 1982, 2009, Oracle. All rights reserved.

Connected to an idle instance.

SYS@bys1 > startup

ORACLE instance started.

Total System Global Area 631914496 bytes

Fixed Size 1338364 bytes

Variable Size 264242180 bytes

Database Buffers 360710144 bytes

Redo Buffers 5623808 bytes

Database mounted.

Database opened.

SYS@bys1 >

These are all the contents of the article "what to do if prelim / as sysdba in sqlplus is down and unable to enter". Thank you for reading! Hope to share the content to help you, more related knowledge, welcome to follow the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.