ORA-27050: function called with invalid FIB or IOV structure

ORA-27050: function called with invalid FIB or IOV structure

Cause: internal error, aditional information indicates which function encountered error

Action: check for trace file and contact Oracle Support

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

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: check errno

ORA-27048: skgfifi: file header information is invalid

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-27047: unable to read the header block of file

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

Cause: read system call failed, additional information indicates which function encountered the error

Action: check errno

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

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-27045: unable to close the file

ORA-27045: unable to close the file

Cause: close system call failed, additional information indicates which function encountered the error

Action: check errno

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

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

Cause: write system call failed, additional information indicates which function encountered the error

Action: check errno

ORA-27043: unable to seek to beginning of file

ORA-27043: unable to seek to beginning of file

Cause: seek system call failed, additional information indicates which function encountered the error

Action: check errno

ORA-27042: not enough space on raw partition to fullfill request

ORA-27042: not enough space on raw partition to fullfill request

Cause: internal error, file too large for raw partition, additional information indicates which function encountered the error

Action: check for trace file and contact Oracle Support

ORA-27041: unable to open file

ORA-27041: unable to open file

Cause: open system call returned an error, additional information indicates which function encountered the error

Action: check errno

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

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

Cause: create system call returned an error, unable to create file

Action: verify filename, and permissions

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

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-27038: created file already exists

ORA-27038: created file already 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-27037: unable to obtain file status

ORA-27037: unable to obtain file status

Cause: stat system call returned an error, additional information indicates which function encountered the error

Action: check errno

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

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

Cause: additional information indicates sltln or slnrm error, and also indicates which function encountered the error

Action: check additional information

ORA-27035: logical block size is invalid

ORA-27035: logical block size is invalid

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

Action: block size specified is returned as additional information, check init.ora parameters, additional information also indicates which function encountered the error

ORA-27034: maximum length of ORACLE_SID exceeded

ORA-27034: 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 your system

ORA-27033: failed to obtain file size limit

ORA-27033: failed to obtain file size limit

Cause: ulimit system call returned an error

Action: check errno

ORA-27032: failed to obtain file size limit

ORA-27032: failed to obtain file size limit

Cause: getrlimit system call returned an error

Action: check errno

ORA-27031: mirror resilvering functions not supported

ORA-27031: mirror resilvering functions not supported

Cause: internal error

Action: check for trace file and contact Oracle Support

ORA-27030: skgfwrt: sbtwrite2 returned error

ORA-27030: skgfwrt: sbtwrite2 returned error

Cause: sbtwrite2 returned an error. This happens while writing a backup file during a backup operation.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27029: skgfrtrv: sbtrestore returned error

ORA-27029: skgfrtrv: sbtrestore returned error

Cause: sbtrestore returned an error. This happens when retrieving a backup file during a restore operation.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27028: skgfqcre: sbtbackup returned error

ORA-27028: skgfqcre: sbtbackup returned error

Cause: sbtbackup returned an error. This happens when creating a backup file during a backup operation.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27027: sbtremove2 returned error

ORA-27027: sbtremove2 returned error

Cause: sbtremove2 returned an error. This happens when deleting a backup file.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27026: skgfrls: sbtend returned error

ORA-27026: skgfrls: sbtend returned error

Cause: sbtend returned an error. This happens during a backup or restore operation.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27025: skgfqsbi: invalid media manager context area size

ORA-27025: skgfqsbi: invalid media manager context area size

Cause: The media management software requested a context area size which is greater than the maximum allowable size.

Action: This is an internal error in the media management product. Contact the media management vendor.

ORA-27024: skgfqsbi: sbtinit2 returned error

ORA-27024: skgfqsbi: sbtinit2 returned error

Cause: sbtinit2 returned an error. This happens during a backup or restore operation.

Action: This error is returned from the media management software which is linked with Oracle. There should be additional messages which explain the cause of the error. This error usually requires contacting the media management vendor.

ORA-27023: skgfqsbi: media manager protocol error

ORA-27023: skgfqsbi: media manager protocol error

Cause: The media management software which is linked with Oracle to provide backup or restore services did not provide its function pointer structure to Oracle.

Action: This is an internal error in the media management product. Contact the media management vendor.

ORA-27022: skgfqsbi: could not allocate memory for media manager

ORA-27022: skgfqsbi: could not allocate memory for media manager

Cause: Oracle could not allocate memory required by the media management software which is linked with Oracle to provide backup or restore services.

Action: Increase the amount of memory available to the Oracle process and retry the backup or restore.

ORA-27021: sequential file handle must be specified

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-27020: named devices not supported

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 see what device types and names (if any) are available.

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

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

Cause: length of tape filename provided to sequential I or 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-27018: BLKSIZE is not a multiple of the minimum physical block size

ORA-27018: BLKSIZE is not a multiple of the minimum physical block size

Cause: User-specified BLKSIZE (blocking factor) is not a multiple of the minimum block size that is permitted on this platform.

Action: Two ADDITIONAL INFORMATION messages are displayed which show the blocking factor provided by the user and the minimum physical block size. Specify a BLKSIZE that is an integral multiple of the minimum block size.

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

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 atleast 64 (the limit specified for sbtinfo). additional information indicates the media handle string length returned by sbtinfo, and the limit (SSTMXQMH)

ORA-27016: skgfcls: sbtinfo returned error

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-27015: skgfcls: failed to close the file

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-27014: skgfqpini: translation error while expanding SS_UDMPDIR

ORA-27014: skgfqpini: translation error while expanding SS_UDMPDIR

Cause: Failure of sltln in skgfqpini

Action: Check additional return error for more information.

ORA-27013: skgfqdel: cannot delete an open file

ORA-27013: skgfqdel: cannot delete an open file

Cause: internal error

Action: check for trace file and contact Oracle Support

ORA-27012: skgfrd: read from file failed

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-27011: skgfrd: cannot read from file opened for write

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

Cause: internal error

Action: check for trace file and contact Oracle Support

ORA-27010: skgfwrt: write to file failed

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-27009: skgfwrt: cannot write to file opened for read

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

Cause: internal error

Action: check for trace file and contact Oracle Support

ORA-27008: function called with invalid file structure

ORA-27008: function called with invalid file structure

Cause: internal error, aditional information indicates which function encountered error

Action: check for trace file and contact Oracle Support

ORA-27007: failed to open file

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-27006: sbtremove returned error

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-27005: cannot open file for async I or O on device not supporting async

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

Cause: internal error, a file is being opened for async I or O on a device that does not support async I or O, additional information indicates which function encountered error

Action: check for trace file and contact Oracle Support

ORA-27004: invalid blocksize specified

ORA-27004: invalid blocksize specified

Cause: internal error, blocksize specified is incorrect for the device on which file is being created, aditional information indicates blocksize specified, and the function that encountered the error

Action: check for trace file and contact Oracle Support

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

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

Cause: internal error, a file is being created or retrieved on a device allocated with NOIO option, additional information indicates which function encountered error

Action: check for trace file and contact Oracle Support

ORA-27002: function called with invalid device structure

ORA-27002: function called with invalid device structure

Cause: internal error, aditional information indicates which function encountered error

Action: check for trace file and contact Oracle Support

ORA-27001: unsupported device type

ORA-27001: unsupported device type

Cause: the specified device type is supported on this platform

Action: check V$BACKUP_DEVICE for supported device types

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

ORA-27000: skgfqsbi: 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-26765: invalid parameter string for downstream capture string

ORA-26765: invalid parameter string for downstream capture string

Cause: An invalid parameter was specified for the downstream capture process.

Action: Check documentation for valid parameters.

ORA-26764: invalid parameter string for local capture string

ORA-26764: invalid parameter string for local capture string

Cause: An invalid parameter was specified for the local capture process.

Action: Check documentation for valid parameters.

ORA-26763: invalid file type string

ORA-26763: invalid file type string

Cause: An invalid file type was specified for the ASM file.

Action: Check documentation for valid ASM file types.

ORA-26762: Cannot autogenerate name for parameter string because of the following reason: string

ORA-26762: Cannot autogenerate name for parameter string because of the following reason: string

Cause: An error was encountered while attempting to generate a name for a parameter which was passed a NULL value.

Action: If possible, fix the error, otherwise specify the parameter name explicitly.

ORA-26761: Standby Redo Logs not available for real time mining

ORA-26761: Standby Redo Logs not available for real time mining

Cause: Standby Redo Logs required for real time mining by downstream capture process were not available.

Action: Check the configuration of Standby Redo Logs and retry the operation at a later time. To start the capture process without real time mining property, reset DOWNSTREAM_REAL_TIME_MINE parameter of the capture process and retry the operation.

ORA-26754: cannot specify both one-to-one transformation function string and one-to-many transformation function string

ORA-26754: cannot specify both one-to-one transformation function string and one-to-many transformation function string

Cause: Both a one-to-one transformation function and a one-to-many transformation function were specified for a rule.

Action: Remove either the one-to-one transformation function, or the one-to-many transformation function.

ORA-26753: Mismatched columns found in string.string

ORA-26753: Mismatched columns found in string.string

Cause: The columns in the LCR were not the same as the table in the database.

Action: Alter the database table.

ORA-26752: Unsupported LCR received for string . string

ORA-26752: Unsupported LCR received for string . string

Cause: Streams capture process received an LCR with unsupported operation from LogMiner.

Action: If this object is listed in DBA_STREAMS_UNSUPPORTED view, modify rules to prevent changes made to this object from getting captured.

ORA-26748: The one-to-one transformation function string encountered the following error: string

ORA-26748: The one-to-one transformation function string encountered the following error: string

Cause: The specified transformation function encountered an error.

Action: Ensure that the function does not return an LCR that has a different type from the LCR which was passed to the function. Also ensure that the function does not return NULL. For DDL transformation functions, creating and returning a new DDL LCR is not allowed.