Oracle 11g Error Codes and Solution Suggestions from ORA-07200 to ORA-07400
- ORA-07200: slsid: oracle_sid not set.
- Cause: The environment variable $(ORACLE_SID) is not set.
- Action: Set ORACLE_SID environment variable.
- ORA-07201: slhom: oracle_home variable not set in environment.
- Cause: $(ORACLE_HOME) environment variable not set.
- Action: Set ORACLE_HOME.
- ORA-07202: sltln: invalid parameter to sltln.
- Cause: The sltln name translation routine was called with invalid arguments. The input, or output stings were either NULL or 0 length.
- Action: Probable internal oracle error. Contact customer support.
- ORA-07203: sltln: attempt to translate a long environment variable.
- Cause: A string was passed to sltln containing a long environment variable. sltln accepts environment names of 30 or less characters.
- Action: Shorten environment variable name to less than 30 characters.
- ORA-07204: sltln: name translation failed due to lack of output buffer space.
- Cause: The sltln routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred.
- Action: Possible internal error. Check output buffer length stored in sercose[0]. Pathnames are limited to 255 characters.
- ORA-07205: slgtd: time error, unable to obtain time.
- Cause: Time() system call returned an error. Possible OS error.
- Action: Check additional information returned. Contact customer support.
- ORA-07206: slgtd: gettimeofday error, unable to obtain time.
- Cause: Gettimeofday() system call returned an error. Possible OS error.
- Action: Check additional information returned. Contact customer support.
- ORA-07207: sigpidu: process ID string overflows internal buffer.
- Cause: The sigpidu routine is given a maximum length buffer to hold process ID string. An overflow of this buffer occurred.
- Action: Internal error. Contact customer support.
- ORA-07208: sfwfb: failed to flush dirty buffers to disk.
- Cause: The fsync system call returned an error. Possible OS error.
- Action: Check additional information returned. Contact customer support.
- ORA-07209: sfofi: file size limit was exceeded.
- Cause: The size of the file to be opened exceeded the OS limit imposed on this process.
- Action: Run osh to increase the file size limit.
- ORA-07210: slcpu: getrusage error, unable to get cpu time.
- Cause: Getrusage system call returned an error. Possible OS error.
- Action: Check additional information returned. Contact customer support.
- ORA-07211: slgcs: gettimeofday error, unable to get wall clock.
- Cause: Gettimeofday system call returned an error. Possible OS error.
- Action: Check additional information returned in OS reference manual. Contact customer support.
- ORA-07212: slcpu: times error, unable to get cpu time.
- Cause: times system call returned an error. Possible OS error.
- Action: Check additional information returned. Contact customer support.
- ORA-07213: slgcs: times error, unable to get wall clock.
- Cause: times system call returned an error. Possible OS error.
- Action: Check additional information returned in OS reference manual. Contact customer support.
- ORA-07214: slgunm: uname error, unable to get system information.
- Cause: uname system call returned an error. Possible OS error.
- Action: Check additional information returned in OS reference manual. Contact customer support.
- ORA-07215: slsget: getrusage error.
- Cause: Getrusage system call returned an error. Possible OS error.
- Action: Check additional information returned. Look for information in OS reference. Contact customer support.
- ORA-07216: slghst: gethostname error, unable to get name of current host.
- Cause: gethostname system call returned an error. Possible OS error.
- Action: Check additional information returned in OS reference manual. Contact customer support.
- ORA-07217: sltln: environment variable cannot be evaluated.
- Cause: getenv call returned a null pointer.
- Action: Set the environment variable and try again.
- ORA-07218: slkhst: could not perform host operation
- Cause: Unix system() call failed
- Action: Examine system error message
- ORA-07219: slspool: unable to allocate spooler argument buffer.
- Cause: Malloc failed to allocate space to hold spooler arguments.
- Action: Check additional information returned in OS reference manual. The process may have run out of heap space. Contact customer support.
- ORA-07220: slspool: wait error.
- Cause: Wait returned an error, when waiting for spool job to complete. Possible spooler program error.
- Action: Check additional information returned. Refer to OS reference manual. Contact customer support.
- ORA-07221: slspool: exec error, unable to start spooler program.
- Cause: Exec failed when starting line printer spooler command. Likely that either the default line printer command, or ORACLE_LPPROG, is incorrectly set.
- Action: Verify default line printer command and ORACLE_LPPROG are set correctly. Set ORACLE_LPPROG to working line printer spooler.
- ORA-07222: slspool: line printer spooler command exited with an error.
- Cause: The line printer spooler exited with a non-zero return value. This probably indicates an error in spooling file.
- Action: Verify that line printer spooler is up. Verify that ORACLE_LPPROG, and ORACLE_LPARG are set properly. Check exit value returned as additional informatin.
- ORA-07223: slspool: fork error, unable to spawn spool process.
- Cause: Fork system call failed to create additional process. Probable resource limit reached.
- Action: Check additional information returned. Retry operation. Contact system administrator.
- ORA-07224: sfnfy: failed to obtain file size limit; errno = string.
- Cause: The ulimit system call returned an error.
- Action: Check errno and contact customer support.
- ORA-07225: sldext: translation error, unable to expand file name.
- Cause: Additional information returned is error returned from sltln.
- Action: Check additional information.
- ORA-07226: rtneco: unable to get terminal mode.
- Cause: The ioctl call returned an error. Possible OS error.
- Action: Check additional information for errno. Contact customer support.
- ORA-07227: rtneco: unable to set noecho mode.
- Cause: The ioctl call returned an error. Possible OS error.
- Action: Check additional information for errno. Contact customer support.
- ORA-07228: rtecho: unable to restore terminal to echo mode.
- Cause: The ioctl call returned an error. Possible OS error.
- Action: Check additional information for errno. Contact customer support.
- ORA-07229: slcpuc: error in getting number of CPUs.
- Cause: error in mpcntl system call
- Action: check errno and contact system administrator
- ORA-07230: slemcr: fopen error, unable to open error file.
- Cause: Fopen failed to open file.
- Action: Try to determine which file was not opened. Check that file exists and is accessible.
- ORA-07231: slemcc: invalid file handle, seals do not match.
- Cause: Function was called with an invalid argument. The file handle used was not obtained be slemcr.
- Action: Internal error. Contact customer support.
- ORA-07232: slemcc: fclose error.
- Cause: An error was encountered when closing the file. Possible OS error.
- Action: Contact system administator.
- ORA-07233: slemcw: invalid file handle, seals do not match.
- Cause: Function was called with an invalid file handle. File handle was not obtained by slemcr.
- Action: Internal error. Contact customer support.
- ORA-07234: slemcw: fseek error.
- Cause: Unable to seek to desired position in file. Possible OS error. Possible internal error.
- Action: Verify that error message file is intact. Try to regenerate error message file. Contact customer support.
- ORA-07235: slemcw: fwrite error.
- Cause: Unable to write item to file. Possible OS error. Possible permissions problem.
- Action: Retry operation.
- ORA-07236: slemop: open error.
- Cause: Unable to open error file. Possible permissions problem.
- Action: Verify permission on error message file. Check additional information for errno.
- ORA-07237: slemcl: invalid file handle, seals do not match.
- Cause: Function was called with an invalid file handle. Handle was not obtained by previous call to slemop.
- Action: Internal error.
- ORA-07238: slemcl: close error.
- Cause: Unable to close file. Possible OS error.
- Action: Contact system administator. Check additional information for errno.
- ORA-07239: slemrd: invalid file handle, seals do not match.
- Cause: Function was called with invalid file handle. Handle was not obtained by call to slemop.
- Action: Internal error. Contact customer support.
- ORA-07240: slemrd: seek error.
- Cause: Unable to seek to desired position in file. Possible OS error.
- Action: Check that error file is still intact. Verify space on device. Contact system administrator. Check additional information for errno.
- ORA-07241: slemrd: read error.
- Cause: Unable to read file. Possible OS error.
- Action: Verify that error file is intact. Regenerate error message file. Contact customer support. Check additional information for errno.
- ORA-07242: slembfn: translation error, unable to translate error file name.
- Cause: Additional information indicates error returned from sltln.
- Action: Check additional information.
- ORA-07243: supplied buffer not big enough to hold entire line
- Cause: supplied buffer was not big enough
- Action: Internal error. Contact customer support. Additional information indicates how big the supplied buffer was.
- ORA-07244: ssfccf: create file failed, file size limit reached.
- Cause: An attempt was made to create a file that exceeds the process’s file size limit.
- Action: Run osh to raise the file size limit.
- ORA-07245: sfccf: unable to lseek and write the last block.
- Cause: An attempt was made to move and write to a bad device address.
- Action: Check errno. Possible lack of space on device.
- ORA-07246: sfofi: open error, unable to open database file.
- Cause: sfofi returns an error.
- Action: This is an oracle internal error.
- ORA-07247: skgfrfms, skgfrnms: read error, unable to read block from database file
- Cause: The ioctl() system call returned an error doing VOL_READ_MIRRORS.
- Action: Check errno.
- ORA-07248: sfwfb: write error, unable to write database block.
- Cause: sfwfb returns an error.
- Action: This is an oracle internal error.
- ORA-07249: slsget: open error, unable to open /proc/pid.
- Cause: The open() system call returned an error.
- Action: Check that /proc has the right permissions.
- ORA-07250: spcre: semget error, unable to get first semaphore set.
- Cause: An error occurred when trying to get first semaphore set.
- Action: Check errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested.
- ORA-07251: spcre: semget error, could not allocate any semaphores.
- Cause: Semget failed to even allocate a single semaphore. Either they are all in use or the system is not configured to have any semaphores.
- Action: Check to see if all semaphores are in use. Check to see if system is configured to have semaphores. Check errno.
- ORA-07252: spcre: semget error, could not allocate semaphores.
- Cause: Semget system call returned an error. Possible resource limit problem.
- Action: Check errno. Verify that enough semaphores are available in system. If additional errors occur in destroying the semaphore sets then sercose[0] will be non-zero. If this occurs, remove the semaphore sets using ipcrm.
- ORA-07253: spdes: semctl error, unable to destroy semaphore set.
- Cause: Semctl system call returned an error.
- Action: Check semaphore sets. May require manual cleanup. Check additional information returned. Consult OS reference manual.
- ORA-07254: spdcr: translation error while expanding ?/bin/oracle.
- Cause: An error occurred while translating the name of the oracle executable.
- Action: Check sercose[0] for error returned from sltln. Perhaps $(ORACLE_HOME) is not set correctly.
- ORA-07255: spini: cannot set up signal handler.
- Cause: System failed to set up signal handler.
- Action: Check errno and sercose[0] for the signal number that failed.
- ORA-07256: sptrap: cannot set up signal handler to catch exceptions.
- Cause: System failed to set up signal handler to catch exceptions.
- Action: Check errno and sercose[0] for the signal number that failed.
- ORA-07257: spdcr: translation error expanding program name.
- Cause: Error ocurred when expanding program name ora_PNAME_@. The result of this translation is put in argv[0] of oracle process.
- Action: Check error returned by sltln returned in sercose[0].
- ORA-07258: spdcr: fork error, unable to create process.
- Cause: An error occurred when creating a new process.
- Action: Check errno. Perhaps a system limit on the number of processes has been exceeded.
- ORA-07259: spdcr: exec error, detached process failed in startup.
- Cause: An oracle detached process died shortly after startup. Wait() indicated that a child process terminated.
- Action: Check ?/dbs directory for trace or core files. Check errno.
- ORA-07260: spdcr: wait error.
- Cause: Wait system call returned an error.
- Action: Check errno.
- ORA-07261: spdde: kill error, unable to send signal to process.
- Cause: Kill system call returned an error. Possibly an attempt to destroy an already gone process.
- Action: Check errno.
- ORA-07262: sptpa: sptpa called with invalid process id.
- Cause: This is an internal error.
- Action: This is an oracle internal error.
- ORA-07263: sptpa: kill error.
- Cause: Kill system call returned an error. Possible OS error.
- Action: Check errno. Additional information indicates the process ID tested.
- ORA-07264: spwat: semop error, unable to decrement semaphore.
- Cause: Semop system call returned an error. Semaphore set may not exist.
- Action: Check errno. Semaphore ID is returned in sercose[0]. Verify semaphore set exists. A possible cause for this error is that a “shutdown abort” was done while this process was running.
- ORA-07265: sppst: semop error, unable to increment semaphore.
- Cause: Semop system call returned an error. Semaphore set may not exist.
- Action: Check errno. Semaphore ID is returned in sercose[0]. Check semaphore set existence. A possible cause for this error is that a “shutdown abort” was done while this process was running.
- ORA-07266: sppst: invalid process number passed to sppst.
- Cause: Function was passed an invalid oracle process id.
- Action: Internal error.
- ORA-07267: spwat: invalid process number.
- Cause: Function was passed an invalid oracle process id.
- Action: Internal error. Additional information indicates the invalid process id.
- ORA-07268: szguns: getpwuid error.
- Cause: Getpwuid() could not find an entry in the passwd file for a user.
- Action: Add an entry for the user in the passwd file.
- ORA-07269: spdcr: detached process died after exec.
- Cause: Detached process succesfully execed, but died shortly thereafter. Additional information indicates exit code, and termination status.
- Action: Check termination code for information as to why process exited. Check for core dump or trace file.
- ORA-07270: spalck: setitimer error, unable to set interval timer.
- Cause: An error occurred while trying to set an interval timer. Probable porting problem.
- Action: Check errno.
- ORA-07271: spwat: invalid oracle process number.
- Cause: Function was called with an invalid oracle process number (0).
- Action: Internal oracle error.
- ORA-07272: spwat: invalid semaphore set id.
- Cause: Semaphore ID fetched from SGA was not initialized to valid value. Additional information returned is semaphore set index, and oracle process number.
- Action: Oracle internal error. Check semaphore set index. Check oracle process number.
- ORA-07273: sppst: invalid semaphore id.
- Cause: Semaphore ID fetched from SGA contained an invalid value. Additional information returned is semaphore set index, and oracle process number.
- Action: Oracle internal error. Check semaphore set index. Check oracle process number.
- ORA-07274: spdcr: access error, access to oracle denied.
- Cause: Unable to access “oracle” program. Verify ?/bin/oracle or $ORABCKPRG exist, and are executable.
- Action: Check errno returned.
- ORA-07275: unable to send signal to process
- Cause: The kill system call returned an error. Possibly an attempt to signal a process which does not exist.
- Action: Check errno.
- ORA-07276: no dba group in /etc/group.
- Cause: A group has not been set up for dba users.
- Action: Contact system administrator. Set up dba group in /etc/group.
- ORA-07277: spdde: illegal pid passed as argument.
- Cause: A 0 pid was passed to spdde.
- Action: Internal error. .
- ORA-07278: splon: ops$username exceeds buffer length.
- Cause: Splon constructed an ops$username logon which exceeded the alloted buffer space.
- Action: Use a shorter Unix username, or use an oracle username. Contact customer support.
- ORA-07279: spcre: semget error, unable to get first semaphore set.
- Cause: An error occurred when trying to get first semaphore set.
- Action: Check errno. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Additional information indicates how many semaphores were requested.
- ORA-07280: slsget: unable to get process information.
- Cause: The ioctl call returned an error. Possible OS error.
- Action: Check additional information for errno. Contact customer support.
- ORA-07281: slsget: times error, unable to get cpu time.
- Cause: times system call returned an error. Possible OS error.
- Action: Check additional information returned. Contact customer support.
- ORA-07282: sksaprd: string overflow.
- Cause: The internal buffer is not big enough to hold the archive control string.
- Action: Internal restriction. Try a shorter archive control string.
- ORA-07283: sksaprd: invalid volume size for archive destination.
- Cause: An invalid volume size was specified.
- Action: Specify a valid volume size in archive control string.
- ORA-07284: sksaprd: volume size specification not terminated properly.
- Cause: Some non-numeric text follows the volume size specification.
- Action: Enter a correct archive control string.
- ORA-07285: sksaprd: volume size should not be specified for a disk file.
- Cause: Volume size was specified for a disk file.
- Action: If you are archiving to a disk file, do not specify its volume size.
- ORA-07286: sksagdi: cannot obtain device information.
- Cause: Stat on the log archiving device failed.
- Action: Check the returned OSD error for the reason of failure.
- ORA-07287: sksagdi: unsupported device for log archiving.
- Cause: Log archiving to this device is unsupported.
- Action: Try log archiving to a supported device.
- ORA-07290: sksagdi: specified directory for archiving does not exist.
- Cause: The specified pathname is not a directory.
- Action: Verify that the archive destination directory exists.
- ORA-07303: ksmcsg: illegal database buffer size.
- Cause: The database buffer size must be a multiple of the database block size, and less than the maximum block size.
- Action: Verify that the db_block_size parameter is correct in INIT.ORA.
- ORA-07304: ksmcsg: illegal redo buffer size.
- Cause: The redo buffer size must be a multiple of machine block size.
- Action: Verify that the log_buffer INIT.ORA parameter is correctly set.
- ORA-07305: ksmcsg: illegal database buffer size.
- Cause: The database buffer size must be a multiple of the extended cache mapping size for indirect data buffers to be used.
- Action: Verify that the db_block_size parameter is correct in INIT.ORA, or disable the use_indirect_data_buffers parameter.
- ORA-07324: smpall: malloc error while allocating pga.
- Cause: Malloc library routine returned an error.
- Action: Check errno. Possibly out of swap space.
- ORA-07327: smpdal: attempt to destroy pga when it was not mapped.
- Cause: Smpdal was called when the PGA had not been previously created.
- Action: Internal error.
- ORA-07339: spcre: maximum number of semaphore sets exceeded.
- Cause: The internal buffer is not big enough to hold the number of semaphore set identifiers requested.
- Action: Reconfigure OS to have more semaphores per set.
- ORA-07345: The datafile name must not contain the string ‘..’.
- Cause: The specified datafile name contains ‘..’.
- Action: Correct the datafile name and retry the operation.
- ORA-07346: slnrm: normalized file name is too long
- Cause: After normalizing the specified file name, the resulting file name was too long.
- Action: Specify the shorter file name and retry the operation.
- ORA-07390: sftopn: translate error, unable to translate file name.
- Cause: An error occurred while expanding the file name to open. Additional information returns error generated in translation routine.
- Action: Lookup additional error code for further information.
- ORA-07391: sftopn: fopen error, unable to open text file.
- Cause: Fopen library routine returned an error.
- Action: Verify existence and permissions.
- ORA-07392: sftcls: fclose error, unable to close text file.
- Cause: Fclose library routine returned an error.
- Action: Possible internal oracle error.
- ORA-07393: unable to delete text file
- Cause: An error occurred while deleting a text file.
- Action: Verify that the file exists and check additional errors.
- ORA-07394: unable to append string to text file
- Cause: An error occurred while performing a string put operation.
- Action: This is an internal error. Check additional information.
- ORA-07400: slemtr: translated name for the message file is too long.
- Cause: The name for the message file overflows internal buffer.
- Action: Try making the complete path-name of the message file shorter by reorganizing the directory hierarchy.