When you log on to an oracle 11g database with sysdba, A ora-013113 that is connected to an idle routine sysdbaora-013113

When you log on to an oracle 11g database with sysdba, A ora-013113 that is connected to an idle routine sysdbaora-013113

Online thinking:
1. Check your E: \ app \ product \ 11.2.0 \ dbhome_1 \ NETWORK \ ADMIN \ listener. whether the SID number in the ora directory file is correct is the SID number set by yourself when installing the oracle database. Generally, the default value is ORCL,
2. Check whether two services of your oracle database are opened. The two services are OracleServiceORCL and OracleOraDb11g_home1TNSListener.
3. if the preceding statements are correct, you need to re-load the database and open it. The specific SQL statement is: SQL> startup pfile = 'd: \ app \ FuH \ admin \ orcl \ pfile \ init. ora.1118385132113'

Description: the connection between oracle and plsql is suddenly lost. Check that the archive log is full, delete the archive log, restart the database, and it is suspected to be stuck during the restart process. Then, force close the command window, then it cannot be started.

Interim generation error: idle routines connected, ora-03113: End of the file for the communication channel, no login, ora-12514: TNS: The Listener is currently unable to identify the Service requested in the connection descriptor, ora-24324: service handle not initialized, ora-03114: not connected to ORACLE, ora-01034: ORACLE not available, ora-01219: Database not open: Allow queries only in fixed tables/views, ora-32001: requested to write spfile, but no spfile,

I. solve the current problem
Ora-24324: Service handle not initialized
Specify ORACLE_SID

C:\user\admin> set ORACLE_SID=ORCLSQL> sqlplus / as sysdba;SQL> startup mount;

Related content: switching between multiple oracle databases
1. If sqlplus is not exited, enter conn username/password in the command line to complete the switchover.
2. When sqlplus is exited,
In windows: set ORACLE_SID = db_name;
In linux: export ORACLE_SID = db_name;
Log on to the corresponding user to complete the switchover.

Ii. Solve the alert. log problem
Restart and error ora-03113

Oracle errors occur, so go to the error log to find the root cause: D: \ app \ FuH \ diag \ rdbms \ orcl \ trace \ alert_orcl.log

 

There are two errors: ora-19815, ORA-19809: exceeds the limit on the number of recovery files, db_recovery_file_dest_size is also called due to insufficient archive log space, and archive log size is adjusted
Delete archived logs:

Query the archived log space SQL> select * from v $ recovery_file_dest; rman target sys/orcl @ orcl; list archivelog all before manually deleting the trac file; delete archivelog all completed before 'sysdate-7'; manually delete the trac file and use crosscheck archivelog all; delete expired archivelog all;

Set non-archive Mode
Http://blog.csdn.net/fengyifei11228/article/details/6049357

1 SQL> archive log list; # Check whether the archive mode is used. 2 SQL> alter system set log_archive_start = false scope = spfile; # disable automatic archiving SQL> alter system set log_archive_start = false scope = spfile; # enable active archiving; 3 SQL> shutdown immediate; 4 SQL> startup mount; # Open the control file, do not open the data file 5 SQL> alter database noarchivelog; # Switch the database to non-archive mode 6 SQL> alter database open; # open the data file 7 SQL> archive log list; # Check that the file is in non-archive mode.

Error again, ora-32001: spfile requested to be written, but no spfile in use,

SQL> show parameter spfile;

NAME TYPE VALUE
-----------------------------------------------------------------------------
Spfile string
The value is null, indicating that the database is started with pfile.
Switch to spfile to start:

sql> create spfile from pfile;

After the database is created, restart the value column to change the archive log size.

Restart again. startup is successful.