Oracle8 Error Messages Release 8.0.4 A58312-01 |
Library | Product | Contents | Index

## 27000-27299: Unix Messages

##### ORA-27000: skgfqpini: failed to initialize storage subsystem (SBT) layer

Cause: sbtinit returned an error, additional information indicates error.

Action: Verify that vendor's storage subsystem product is operating correctly.

##### ORA-27001: unsupported device type

Cause: The specified device type is supported on this platform.

Action: Verify V$BACKUP_DEVICE for supported device types.

##### ORA-27002: function called with invalid device structure

Cause: This is an internal error. Additional information indicates which function encountered error.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27003: cannot open file on device allocated with NOIO option

Cause: This is an internal error. A file is being created/retrieved on a device allocated with NOIO option. Additional information indicates which function encountered error.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27004: invalid blocksize specified

Cause: This is an internal error. Blocksize specified is incorrect for the device on which file is being created. Additional information indicates blocksize specified, and the function that encountered the error.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27005: cannot open file for async I/O on device not supporting async

Cause: This is an internal error. A file is being opened for async I/O on a device that does not support async I/O. Additional information indicates which function encountered error.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27006: sbtremove returned error

Cause: Additional information indicates error returned by sbtremove, and the function that encountered the error.

Action: Verify that vendor's storage subsystem product is operating correctly.

##### ORA-27007: failed to open file

Cause: sbtopen returned error. Additional information indicates error returned from sbtopen, and the function that encountered the error.

Action: Verify that vendor's storage subsystem product is operating correctly.

##### ORA-27008: function called with invalid file structure

Cause: This is an internal error. Additional information indicates which function encountered error

Action: Look for trace file, and contact Oracle Support.

##### ORA-27009: skgfwrt: cannot write to file opened for read

Cause: This is an internal error.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27010: skgfwrt: write to file failed

Cause: sbtwrite returned error. Additional information indicates error returned from sbtwrite.

Action: Verify that vendor's storage subsystem product is operating correctly.

##### ORA-27011: skgfrd: cannot read from file opened for write

Cause: This is an internal error.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27012: skgfrd: read from file failed

Cause: sbtread returned error. Additional information indicates error returned from sbtread.

Action: Verify that vendor's storage subsystem product is operating correctly.

##### ORA-27013: skgfqdel: cannot delete an open file

Cause: This is an internal error.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27014: skgfqpini: translation error while expanding SS_UDMPDIR

Cause: Failure of sltln in skgfqpini.

Action: Examine additional return error for more information.

##### ORA-27015: skgfcls: failed to close the file

Cause: sbtclose returned error. Additional information indicates error returned from sbtclose.

Action: Verify that vendor's storage subsystem product is operating correctly.

##### ORA-27016: skgfcls: sbtinfo returned error

Cause: Additional information indicates error returned from sbtinfo.

Action: Verify that vendor's storage subsystem product is operating correctly.

##### ORA-27017: skgfcls: media handle returned by sbtinfo exceeds max length(SSTMXQMH)

Cause: Media handle string length exceeds SSTMXQMH.

Action: Verify that vendor's storage subsystem product is operating correctly, and that the platform limit (SSTMXQMH) is at least 64 (the limit specified for sbtinfo). Additional information indicates the media handle string length returned by sbtinfo, and the limit (SSTMXQMH).

##### ORA-27018: skgfidev: blocksize in device parms must be multiple of SSTKBLCK

Cause: User specified a blocking factor that is not a multiple of SSTKBLCK.

Action: Additional information indicates the blocking factor provided by user and the value of SSTKBLCK. Specify a value that is a multiple of SSTKBLCK.

##### ORA-27019: tape filename length exceeds limit (SBTOPMXF)

Cause: Length of tape filename provided to sequential I/O OSD functions is too long.

Action: Additional information indicates in which function this error is encountered, the length of filename provided, and the limit on filename.

##### ORA-27020: named devices not supported

Cause: The platform or the specified device type does not support named devices.

Action: Do not specify device name or use a device type that supports named devices. Use V$BACKUP_DEVICE view to find what device types and names (if any) are available.

##### ORA-27021: sequential file handle must be specified

Cause: The filename which will be passed to sbtopen was not specified.

Action: Specify a filename and continue. If this is a backup set being created via Recovery Manager, use the 'format' option to specify the backup piece handle name.

##### ORA-27031: mirror resilvering functions not supported

Cause: This is an internal error.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27032: skgfrpini: failed to obtain file size limit

Cause: getrlimit system call returned an error.

Action: Examine errno.

##### ORA-27033: skgfrpini: failed to obtain file size limit

Cause: ulimit system call returned an error.

Action: Examine errno.

##### ORA-27034: skgfrcre: maximum length of ORACLE_SID exceeded

Cause: Too many characters in the ORACLE_SID string.

Action: Rename the ORACLE_SID to a string of up to the maximum number of characters specified for system.

##### ORA-27035: logical block size is invalid

Cause: Logical block size for oracle files must be a multiple of the physical block size, and must be less than the maximum.

Action: Block size specified is returned as additional information. Verify init.ora parameters. Additional information also indicates which function encountered the error.

##### ORA-27036: translation error, unable to expand file name

Cause: Additional information indicates sltln/slnrm error, and also indicates which function encountered the error.

Action: Examine additional information.

##### ORA-27037: unable to obtain file status

Cause: Stat system call returned an error. Additional information indicates which function encountered the error.

Action: Examine errno.

##### ORA-27038: skgfrcre: file exists

Cause: Trying to create a database file, but file by that name already exists.

Action: Verify that name is correct. Specify reuse if necessary.

##### ORA-27039: create file failed, file size limit reached

Cause: An attempt was made to create a file that exceeds the process's file size limit. Additional information indicates which function encountered the error.

Action: Raise the file size limit.

##### ORA-27040: skgfrcre: create error, unable to create file

Cause: Create system call returned an error. Failure to create file.

Action: Verify filename and permissions.

##### ORA-27041: unable to open file

Cause: Open system call returned an error. Additional information indicates which function encountered the error.

Action: Examine errno.

##### ORA-27042: skgfrcre: unable to seek to and write the last block

Cause: An attempt was made to seek and write the last block in file. Possibly, there is a shortage of space on device.

Action: Examine errno.

##### ORA-27043: unable to seek to beginning of file

Cause: Seek system call failed. Additional information indicates which function encountered the error.

Action: Examine errno.

##### ORA-27044: unable to write the header block of file

Cause: Write system call failed. Additional information indicates which function encountered the error.

Action: Examine errno.

##### ORA-27045: unable to close the file

Cause: Close system call failed. Additional information indicates which function encountered the error.

Action: Examine errno.

##### ORA-27046: file size is not a multiple of logical block size

Cause: File size as indicated by stat is not correct. Additional information indicates which function encountered the error.

Action: Verify that the file has not been overwritten or truncated.

##### ORA-27047: unable to read the header block of file

Cause: Read system call failed. Additional information indicates which function encountered the error.

Action: Examine errno.

##### ORA-27048: skgfifi: file header information is invalid

Cause: Possibly trying to use a non-database file as a database file.

Action: Verify that file is a database file.

##### ORA-27049: unable to seek to and read the last block

Cause: An attempt was made to seek to and read the last block in file. Additional information indicates which function encountered error.

Action: Examine errno.

##### ORA-27050: function called with invalid FIB/IOV structure

Cause: This is an internal error. Additional information indicates which function encountered error.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27051: I/O error (simulated, not real)

Cause: This is just a simulated error (not a real one). Additional information indicates which function encountered the error.

Action: None.

##### ORA-27052: unable to flush file data

Cause: fsync system call returned error. Additional information indicates which function encountered the error.

Action: Examine errno.

##### ORA-27053: skgfifi: blocksize in file header not a multiple of logical block size

Cause: The logical block size is invalid. Additional information indicates the logical block size and the blocksize in the file header.

Action: Use a different logical block size, or do not reuse file.

##### ORA-27056: skgfrdel: could not delete file

Cause: Unlink system call returned error.

Action: Examine errno.

##### ORA-27057: skgfask: cannot perform async I/O to file

Cause: This is an internal error. Query is being asked about async vector I/O when the file does not support async I/O.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27058: skgfask: question parameter is invalid

Cause: This is an internal error. Invalid query is being asked.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27059: skgfrsz: could not reduce file size

Cause: ftruncate system call returned error.

Action: Examine errno.

##### ORA-27060: skgfofi: could not set close-on-exec bit on file

Cause: fcntl system call returned error.

Action: Examine errno.

##### ORA-27061: skgfospo: waiting for async I/Os failed

Cause: aiowait function returned error.

Action: Examine errno.

##### ORA-27062: skgfospo: could not find pending async I/Os

Cause: This is an internal error. There should have been some async I/Os in the system, but a blocking aiowait indicates that there are no more I/Os.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27063: skgfospo: number of bytes read/written is incorrect

Cause: The number of bytes read/written as returned by aiowait does not match the original number. Additional information indicates both these numbers.

Action: Examine errno.

##### ORA-27064: skgfdisp: cannot perform async I/O to file

Cause: This is an internal error. Asked to perform async I/O when IOV indicates that it cannot be performed on the file.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27065: skgfdisp: cannot perform async vector I/O to file

Cause: This is an internal error. Asked to perform async vector I/O when it cannot be performed on the file.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27066: skgfdisp: number of buffers in vector I/O exceeds maximum

Cause: This is an internal error. Number of buffers in vector I/O exceeds maximum allowed by the OSD. Additional information indicates both these numbers.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27067: skgfdisp: size of buffer is invalid

Cause: This is an internal error. Buffer size is either 0, greater than SSTIOMAX, or not a multiple of logical block size. Additional information indicates where in function the error was encountered and the buffer size.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27068: skgfdisp: buffer is not aligned properly

Cause: This is an internal error. Buffer is not aligned to SSIOALIGN boundary. Additional information indicates where in function the error was encountered and the buffer pointer.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27069: skgfdisp: attempt to do I/O beyond the range of the file

Cause: This is an internal error. The range of blocks being read or written is outside the range of the file. Additional information indicates the starting block number, number of blocks in I/O, and the last valid block in the file.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27070: skgfdisp: async read/write failed

Cause: aioread/aiowrite system call returned error. Additional information indicates starting block number of I/O.

Action: Examine errno.

##### ORA-27071: skgfdisp: unable to seek to desired position in file

Cause: lseek system call returned error. Additional information indicates block number in file to which seek was attempted.

Action: Examine errno.

##### ORA-27072: skgfdisp: I/O error

Cause: Read/write/readv/writev system call returned error. Additional information indicates starting block number of I/O.

Action: Examine errno.

##### ORA-27073: skgfcfi: async I/Os remaining to be dequeued for this file

Cause: This is an internal error. The file is being closed, but not all async I/Os to the file have been dequeued. Additional information indicates number of I/Os pending on the file.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27074: skgfrofl: unable to determine limit for open files

Cause: getrlimit system call returned error.

Action: Examine errno.

##### ORA-27075: skgfrofl: SSTMOFRC constant too large

Cause: This is an internal error.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27076: skgfrofl: unable to set limit for open files

Cause: setrlimit system call returned error.

Action: Examine errno.

##### ORA-27077: skgfofi: too many files open

Cause: This is an internal error. The number of files opened through skgfofi has reached the limit.

Action: Look for trace file, and contact Oracle Support.

##### ORA-27100: shared memory realm already exists

Cause: An attempt was made to either start duplicate instances, or to restart an instance that had not been properly shut down.

Action: Use a different instance name, or cleanup the failed instance's SGA.

##### ORA-27101: shared memory realm does not exist

Cause: Unable to locate shared memory realm.

Action: Verify that the realm is accessible.

##### ORA-27102: out of memory

Cause: Out of memory.

Action: Consult the trace file for details.

##### ORA-27103: internal error

Cause: This is an internal error.

Action: contact Oracle support.

##### ORA-27120: unable to removed shared memory segment

Cause: A call to shmctl() failed.

Action: Check permissions on segment, then contact Oracle Worldwide Support.

##### ORA-27121: unable to determine size of shared memory segment

Cause: A call to shmctl() failed.

Action: Check permissions on segment, then contact Oracle Worldwide Support.

##### ORA-27122: unable to protect memory

Cause: A call to mprotect() call failed.

Action: Contact Oracle Worldwide Support.

##### ORA-27123: unable to attach to shared memory segment

Cause: A call to shmat() call failed.

Action: Check permissions on segment, then contact Oracle Worldwide Support.

##### ORA-27124: unable to detach from shared memory segment

Cause: A call to shmdt() failed.

Action: Contact Oracle Worldwide Support.

##### ORA-27125: unable to create shared memory segment

Cause: A call to shmget() failed.

Action: Contact Oracle Worldwide Support.

##### ORA-27126: unable to lock shared memory segment in core

Cause: Insufficient privileges to lock shared memory segment in core.

Action: Make sure process is running with necessary privileges.

##### ORA-27127: unable to unlock shared memory segment

Cause: Insufficient privileges to unlock shared memory segment.

Action: Make sure process is running with necessary privileges.

##### ORA-27128: unable to determine pagesize

Cause: A call to sysconf() failed.

Action: Contact Oracle Worldwide Support.

##### ORA-27141: invalid process ID

Cause: Process operation attempted using invalid process ID.

Action: Contact Oracle Support.

##### ORA-27142: could not create new process

Cause: OS system call.

Action: Examine errno, and if possible increase the number of processes.

##### ORA-27143: OS system call failure

Cause: OS system call failed.

Action: Examine errno, and contact Oracle Support.

##### ORA-27144: attempt to kill process failed

Cause: OS system call error.

Action: Examine errno, and contact Oracle Support.

##### ORA-27145: insufficient resources for requested number of processes

Cause: OS system call error.

Action: Examine errno, and contact Oracle Support.

##### ORA-27146: post/wait initialization failed

Cause: OS system call failed.

Action: Examine errno, and contact Oracle Support.

##### ORA-27147: post/wait reset failed

Cause: OS system call failed.

Action: Examine errno, and contact Oracle Support.

##### ORA-27148: spawn wait error

Cause: OS system call failed.

Action: Examine errno, and contact Oracle Support.

##### ORA-27149: assignment out of range

Cause: Internal error, requested conversion too large for type.

Action: Contact Oracle Support.

##### ORA-27150: attempt to notify process of pending oradebug call failed

Cause: OS system call.

Action: Examine errno, contact Oracle Support.

##### ORA-27151: buffer not large enough to hold process ID string

Cause: This is an internal error.

Action: Contact Oracle Support.

##### ORA-27152: attempt to post process failed

Cause: OS system call failed.

Action: Examine errno, and contact Oracle Support.

##### ORA-27153: wait operation failed

Cause: OS system called failed.

Action: Examine errno, and contact Oracle Support.

##### ORA-27154: post/wait create failed

Cause: This is an internal error. Multiple post/wait creates attempted simultaneously.

Action: Examine errno, and contact Oracle Support.

##### ORA-27155: could not execute file

Cause: OS system call failed.

Action: Examine errno, and contact Oracle Support.

##### ORA-27156: request for process information failed

Cause: This is an internal error.

Action: Contact Oracle Support.

The messages for this topic are described elsewhere in the Oracle8 Error Messages, Release 8.0.3 error message set.

Prev | Top | Next
| Copyright © 1997 Oracle Corporation. All Rights Reserved. |
Library | Product | Contents | Index