Archiving log ORA-16032 error Solution

Database environment:

Oracle 10.2.0 + Windows 2003 Server

Fault description:

After the Oracle service and listener are started on Windows, the following error is reported when you log on to SQL * Plus as sysdba and start ORACLE:

Error:
A ORA-01034: Oracle not available
ORA-27101: Shared Memory realm does not exist

Then try

Sqlplus nolog as sysdba logon reports the following error

Enter the password:
Error:
ORA-01031: insufficient privileges

Then, specify set oracle_sid = orcl in the window.

Use sqlplus nolog as sysdba to log on

Enter the password:
Already connected to the idle routine.

SQL> startup;
ORA-32004: obsolete and/or deprecated par
ORA-16032: parameter log_archive_dest_1 D.
ORA-09291: sksachk: Invalid device specif
OSD-04018 :??????????????????????????
O/s-error: (OS 2 )??????????????????????

Solution:

According to the error message, this error is generated because the log_archive_dest_1 parameter in the parameter file cannot be read ., That is, the address of log_archive_dest_1 is specified to a non-existent path. In the process of starting the Oracle database, first read the parameter file to read the initialization parameters, start the instance and background process accordingly, and allocate the memory. Because some parameters cannot be found, an error is reported, this is the cause of this error.

After knowing the root cause and cause of the fault, the solution is simple. Since there is a problem with a parameter in the parameter file, you can click it in the parameter file. If the database uses a static parameter file, you can directly modify the log_archive_dest_1 parameter in the parameter file, save the file, and restart the database. If the database uses spfile, you can generate pfile from spfile, modify the log_archive_dest_1 parameter in pfile, and then generate spfile from pfile, save and restart.

Fault summary:

Errors of this parameter file often occur in the database. Even accidental operations or unexpected shutdown may cause parameter errors. This warns us that the backup parameter file is uncertain.

When you manually set log_archive_start to true, a ORA-32004 or an obsolete parameter is set at startup to cause a ORA-32004 Error

Oracle automatically starts the archiving process when the database is in archive mode after 10 Gb. You do not need to set the log_archive_start parameter.

Alter system resetlog_archive_start scope = spfile

SQL> alter system reset log_archive_start scope = spfile SID = '*';

The system has been changed.

SQL> shutdown immediate;
The database has been closed.
The database has been detached.
The Oracle routine has been disabled.
SQL> startup Mount;
The Oracle routine has been started.

Total system global area 612368384 bytes
Fixed size 1250428 bytes
Variable Size 197135236 bytes
Database buffers 406847488 bytes
Redo buffers 7135232 bytes
The database has been loaded.

You can also delete *. SQL _trace = true in the spfile parameter file.