Oracle A423961 Manual Do Utilizador
Cause
Action
Cause
Action
Cause
Action
E – 9
Messages and Codes
ORA–09341
scumnt: unable to mount database
ORA–09350
Windows NT two–task driver unable to allocate context area
ORA–09351
Windows NT two–task driver unable to allocate shared memory
ORA–09352
Windows NT two–task driver unable to spawn new Oracle task
ORA–09353
Windows NT two–task driver unable to open event semaphore
ORA–09354
Windows NT two–task driver: Oracle task unexpectedly died
Codes 4000–4999: Windows NT–Specific Oracle Messages
The messages in this section are Oracle operating–system–dependent
(OSD) messages that issue in response to an error condition in Windows
NT. Each message in this section triggers an Oracle database message
(listed in the preceding section).
(OSD) messages that issue in response to an error condition in Windows
NT. Each message in this section triggers an Oracle database message
(listed in the preceding section).
File I/O Errors: OSD–4000 to OSD–4099
OSD–04000
logical block size mismatch
The database block size specified in the initialization parameter file does not
match the block size of the actual database files.
match the block size of the actual database files.
Use matching logical block sizes.
OSD–04001
invalid logical block size
The logical block size is not a multiple of 512 bytes, or it is too large.
Change the value of DB_BLOCK_SIZE in the initialization parameter file.
OSD–04002
unable to open file
The specified path or filename is invalid, or the destination device is full. This
error can also be caused by insufficient Windows NT file handles.
error can also be caused by insufficient Windows NT file handles.
Make sure that the path and file exist, and that the device has free space. If this
fails, increase the number of Windows NT file handles.
fails, increase the number of Windows NT file handles.