In this Document
Symptoms
Cause
Solution
References

Applies to:

Symptoms

When a datafile has been configured such that it will autoextend onto a 4GB boundary, any attempt to autoextend the file causes the file the database to crash (when in noarchive log mode). If the database was in archive log mode,will be marked offline recover and access to the database continues.

The following error appears in the alert.log :
.
KCF: write/open error block=0x32002 nline=1
file=11 'E:ORACLEORA92BORGMAXIMO.ORA'
error=27069 txt: 'OSD-4026: Invalid parameter passed. (OS-204802)'
Automatic datafile offline due to write error on
file 11: 'E:ORACLEORA92BORGMAXIMO.ORA'
.
Any attempt to online / recover this file results in :
.
ORA-283: recovery session canceled due to errors
ORA-1115: IO error reading block from file 11 (block # 204802)
ORA-1110: data file 11: 'E:ORACLEORA92BORGMAXIMO.ORA'
ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file
OSD-4026: Invalid parameter passed. (OS-204802)

Cause

Its a Bug specific to NT platform. only. Cannot AUTOEXTEND to 4Gb boundary

Solution

This bug is fixed in 9203. Upgrading the database to the latest relase followed by a recovery will solve this problem.

Here are the steps:

1.Do a clean shutdown of the database

2. Upgrade the database to the latest version ( greater than 9.2.0.3) as this bug is fixed in 9203.

If the database version is below 9i Rel 2(9.2.0.1) then first upgrade to 9iRel2 and then apply the latest available patchset. 
Kindly check metalink for the latest patchset available

3.Mount the database

4.Do a COMPLTE recovery of the dataabse

5.Then start the database in migrate mode and upgrade the database. Refer Note 159657.1: Complete Upgrade Checklist for Manual Upgrades from 8.X / 9.0.1 to Oracle9i

References

Errors