Database Log reports: ORA-27300: OS system related operations: spcdr: 9261: 4200 failed, status: 997

The operating system is Windows 2003 Server.
Database Version: 10.2.0.1

Warning the following error occurs in the log alter_sid.log:

ORA-27300: OS system related operation: spcdr: 9261: 4200 failed, status: 997
ORA-27301: OS fault message: overlapping I/O operations in progress.
ORA-27302: Error occurred at: skgpspawn

Alter_sid.log log:
Bytes --------------------------------------------------------------------------------------------------------------------------

Wed Jul 13 14:55:29 2011
Process startup failed, error Stack:
Wed Jul 13 14:55:29 2011
Errors in file E: \ oracle \ product \ 10.2.0 \ admin \ sxserver \ bdump \ sxserver_psp0_2984.trc:
ORA-27300: OS system dependent operation: spcdr: 9261: 4200 failed with status: 997
ORA-27301: OS failure message: overlapping I/O operations in progress.
ORA-27302: failure occurred at: skgpspawn

Wed Jul 13 14:55:30 2011
Process j001 died, see its trace file
Wed Jul 13 14:55:30 2011
Kkjcre1p: Unable to spawn jobq slave Process
Wed Jul 13 14:55:30 2011
Errors in file E: \ oracle \ product \ 10.2.0 \ admin \ sxserver \ bdump \ sxserver_cjq0_3248.trc:

Wed Jul 13 14:55:35 2011
Process startup failed, error Stack:
Wed Jul 13 14:55:35 2011
Errors in file E: \ oracle \ product \ 10.2.0 \ admin \ sxserver \ bdump \ sxserver_psp0_2984.trc:
ORA-27300: OS system dependent operation: spcdr: 9261: 4200 failed with status: 997
ORA-27301: OS failure message: overlapping I/O operations in progress.
ORA-27302: failure occurred at: skgpspawn

Wed Jul 13 14:55:36 2011
Process j001 died, see its trace file
Wed Jul 13 14:55:36 2011
Kkjcre1p: Unable to spawn jobq slave Process
Wed Jul 13 14:55:36 2011
Errors in file E: \ oracle \ product \ 10.2.0 \ admin \ sxserver \ bdump \ sxserver_cjq0_3248.trc:

Wed Jul 13 14:56:36 2011
Errors in file E: \ oracle \ product \ 10.2.0 \ admin \ sxserver \ bdump \ sxserver_j004241652.trc:
ORA-12012: Error on auto execute of Job 1
ORA-04030: Out of process memory when trying to allocate 8148 bytes (KXS-heap-W, qesaqbinit: buffer)

Wed Jul 13 14:56:36 2011
Errors in file E: \ oracle \ product \ 10.2.0 \ admin \ sxserver \ bdump \ sxserver_j004241652.trc:
ORA-00604: Error occurred at recursive SQL Level 2
ORA-04030: Out of process memory when trying to allocate 44 bytes (KXS-heap-D, Allocator state)
ORA-12012: Error on auto execute of Job 1
ORA-04030: Out of process memory when trying to allocate 8148 bytes (KXS-heap-W, qesaqbinit: buffer)

Wed Jul 13 14:59:26 2011
Errors in file E: \ oracle \ product \ 10.2.0 \ admin \ sxserver \ bdump \ sxserver_j000_876.trc:
ORA-12012: Automatic Execution of Job 1 error
ORA-04030: insufficient process memory when trying to allocate 16428 bytes (PGA heap, kgh stack)

Wed Jul 13 14:59:26 2011
Errors in file E: \ oracle \ product \ 10.2.0 \ admin \ sxserver \ bdump \ sxserver_j000_876.trc:
ORA-00604: recursive SQL Level 1 error
ORA-04030: insufficient process memory when trying to allocate 16092 bytes (PGA heap, kgh stack)
ORA-12012: Automatic Execution of Job 1 error
ORA-04030: insufficient process memory when trying to allocate 16428 bytes (PGA heap, kgh stack)

Wed Jul 13 15:00:45 2011
Process startup failed, error Stack:
Wed Jul 13 15:00:45 2011
Errors in file E: \ oracle \ product \ 10.2.0 \ admin \ sxserver \ bdump \ sxserver_psp0_2984.trc:
ORA-27300: OS system dependent operation: spcdr: 9261: 4200 failed with status: 997
ORA-27301: OS failure message: overlapping I/O operations in progress.
ORA-27302: failure occurred at: skgpspawn

Bytes --------------------------------------------------------------------------------------------------------------------------

It is said that this is an Oracle bug. You can check the official website and find it:

The solution is as follows:

ORA-27300: OS system related operation: spcdr: 9261: 4200 failed, status: 997
Terrible Oracle bug, memory depletion, resulting in Database Failure
It is very common to install oracle10.2.0.1.0 on a 32-bit Windows system. You can find a lot in Google.
Generally, the system runs out of memory and the Oracle database crashes.
Restarting the Oracle database can be solved temporarily, but in a few days the ORA-04030 memory will be exhausted. It is best to install a patch.

When you connect to the database,
ORA-12518: TNS: Listeners cannot distribute client connections

1. Use sysdba to connect to a database instead of a database. The database has crashed.

2. alert_sid.log
Sun Apr 19 10:05:56 2009
Process startup failed, error Stack:
Sun Apr 19 10:05:56 2009
Errors in file E: \ oracle \ product \ 10.2.0 \ admin \ xboms \ bdump \ xboms_psp0_3124.trc:
ORA-27300: OS system related operation: spcdr: 9261: 4200 failed, status: 997
ORA-27301: OS fault message: overlapping I/O operations in progress.
ORA-27302: Error occurred at: skgpspawn

As a result, the following errors are frequently reported:
Sun Apr 19 10:24:08 2009
Errors in file E: \ oracle \ product \ 10.2.0 \ admin \ xboms \ bdump \ xboms_arc0_3032.trc:
ORA-04030: The process memory is insufficient when trying to allocate 82444 bytes (PGA heap, control file I/O buffer)

View: http: // **/viewthread. php? Tid = 129216
And http://www.itpub.net/thread-1146317-1-1.html

This is a bug!
Oracle acknowledges that this is a bug (10 Gb earlier than 10.2.0.2.0), bug 5607984-Oracle does not close TCP connections. Remains in close_wait state. [On Windows 32-bit].
Patch Number 5639232 can be patched, which is larger than 100 MB.

Add '/3g' to the boot. ini file of the operating system, and then reduce the SGA.

 

1. Open the c: \ Boot. ini file in the command line and add "/3 GB" at the end of the file"

For example: C: \ Boot. ini file content:

[Boot loader]
Timeout = 30
Default = multi (0) disk (0) RDISK (0) Partition (1) \ WINDOWS
[Operating systems]
Multi (0) disk (0) RDISK (0) Partition (1) \ Windows = "Windows Server 2003 enterprise x64 Edition"/noexecute = optout/fastdetect/3 GB

 

Metalink is explained as follows:

Changesthe '/3gb' switch was added to the 'boot. ini' file at the OS level but the errors are eventually encountered when the database is under heavy load. causeos resource issue.
The maximum amount of addressable memory by a process ('oracle.exe 'for example) running in
32-bit Windows environment has been reached.

In a 32-bit Windows environment, the total addressable memory by a single process is a 4 GB. on Windows, the OS reserves half of this memory by default for kernel memory, leaving 2 GB of addressable memory for a user process. by placing the '/3gb' switch in the 'boot. INI 'file, this changes the ratio of kernel memory and user memory. when he '/3g' switch is in place, processes (such as 'oracle.exe') can address 3 GB of virtual memory out of the total 4 GB of addressable memory. however, once the 3 GB of virtual memory is depleted, the process will fail. solutionto implement the solution, Please execute the following steps:

Tune the application running on the 32-bit environment so that it will not consume greater than 2.7 GB of virtual memory when the '/3gb' switch is set in the 'boot. INI 'file. in the case of Oracle encountering the OS resource issue, the options are:

1) Reduce the amount of SGA needed to be allocated for the database.
2) Limit the number of dedicated connections to the database and the amount of memory each user process will consume.
3) change from dedicated connections to multi-threaded server (MTS) connections as MTS only uses a fraction of the amount of memory allocated to each user process when initial connection to the database is established.

See Metalink note 225349.1 for an in depth discussion regarding memory usage in a 32-bit Windows Environment

======================================

ORA-27300 ORA-27301 ORA-27302 in Alert Log. Cannot connect to database.
Document ID: Comment: 371074.1 type: Problem
Last revised: 30-Jan-2008 status: moderated

In this document
Symptoms
Changes
Cause
Solution
References

-------------------------------------------------------------------------------

2. Reduce SGA

SGA: data cache, sharing pool, large pool, Java pool...
PGA: stack space, user session data, cursor status...

 

To modify the SGA principles, follow these steps:

1. sga_target cannot be greater than sga_max_size. It can be set to equal.

2. The total memory occupied by other processes such as SGA and PGA must be smaller than the physical memory of the operating system.

Before performing the following operations, you must back up all the files in the DBS directory.

Method 1: directly modify the SQL command line:

SQL> alter system set sga_target = 1400 m scope = spfile;

 

Method 2: Modify through EM:

Log on to em with SYS: Manage-> (Database Configuration) All initialization parameters-> spfile->
You can directly define sga_target and sga_max_size on this interface.
Restart the database!