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

## 07200-07499: UNIX Messages

##### 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 strings were either NULL or 0 length. This is probably an internal error.

Action: Contact Oracle 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. This is possibly an internal error.

Action: Verify output buffer length stored in sercose[0]. Path names are limited to 255 characters.

##### ORA-07205: slgtd: time error, unable to obtain time

Cause: Time() system call returned an error. This is possibly an OS error.

Action: Examine additional information returned. Contact Oracle Support.

##### ORA-07206: slgtd: gettimeofday error, unable to obtain time

Cause: gettimeofday() system call returned an error. This is possibly an OS error.

Action: Examine additional information returned. Contact Oracle 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. This is an internal error.

Action: Contact Oracle Support.

##### ORA-07208: sfwfb: failed to flush dirty buffers to disk

Cause: The fsync system call returned an error. This is possibly an OS error.

Action: Examine additional information returned. Contact Oracle 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. This is possibly an OS error.

Action: Examine additional information returned. Contact Oracle Support.

##### ORA-07211: slgcs: gettimeofday error, unable to get wall clock

Cause: gettimeofday system call returned an error. This is possibly an OS error.

Action: Examine additional information returned in OS reference manual. Contact Oracle Support.

##### ORA-07212: slcpu: times error, unable to get cpu time

Cause: Times system call returned an error. This is possibly an OS error.

Action: Examine additional information returned. Contact Oracle Support.

##### ORA-07213: slgcs: times error, unable to get wall clock

Cause: Times system call returned an error. This is possibly an OS error.

Action: Examine additional information returned in OS reference manual. Contact Oracle Support.

##### ORA-07214: slgunm: uname error, unable to get system information

Cause: uname system call returned an error. This is possibly an OS error.

Action: Examine additional information returned in OS reference manual. Contact Oracle Support.

##### ORA-07215: slsget: getrusage error

Cause: Getrusage system call returned an error. This is possibly an OS error.

Action: Examine additional information returned. Look for information in OS reference. Contact Oracle Support.

##### ORA-07216: slghst: gethostname error, unable to get name of current host

Cause: Gethostname system call returned an error. This is possibly an OS error.

Action: Examine additional information returned in OS reference manual. Contact Oracle 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. The process may have run out of heap space.

Action: Examine additional information returned in OS reference manual. Contact Oracle Support.

##### ORA-07220: slspool: wait error

Cause: Wait returned an error when waiting for spool job to complete. This is possibly a spooler program error.

Action: Examine additional information returned. Refer to the OS reference manual. Contact Oracle Support.

##### ORA-07221: slspool: exec error, unable to start spooler program

Cause: Exec failed when starting line printer spooler command. It is likely that either the default line printer command, or ORACLE_LPPROG, is incorrectly set.

Action: Verify that the 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. Examine exit value returned for additional information.

##### ORA-07223: slspool: fork error, unable to spawn spool process

Cause: Fork system call failed to create additional process. It is probable that the resource limit has been reached.

Action: Examine additional information returned. Retry operation. Contact system administrator.

##### ORA-07224: sfnfy: failed to obtain file size limit; errno = numbers

Cause: The ulimit system call returned an error.

Action: Examine errno. Contact Oracle Support.

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

Cause: Additional information returned is error returned from sltln.

Action: Examine additional information.

##### ORA-07226: rtneco: unable to get terminal mode

Cause: The ioctl call returned an error. The process may have run out of heap space.

Action: Examine additional information for errno. Contact Oracle Support.

##### ORA-07227: rtneco: unable to set noecho mode

Cause: The ioctl call returned an error. The process may have run out of heap space.

Action: Examine additional information for errno. Contact Oracle Support.

##### ORA-07228: rtecho: unable to restore terminal to echo mode

Cause: The ioctl call returned an error. The process may have run out of heap space.

Action: Examine additional information for errno. Contact Oracle Support.

##### ORA-07229: slcpuc: error in getting number of CPUs

Cause: Error in mpcntl system call.

Action: Examine errno. 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. Verify that the 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. This is an internal error.

Action: Contact Oracle Support.

##### ORA-07232: slemcc: fclose error

Cause: An error was encountered when closing the file. The process may have run out of heap space.

Action: Contact system administrator.

##### 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. This is an internal error.

Action: Contact Oracle Support.

##### ORA-07234: slemcw: fseek error

Cause: Failure to seek to desired position in file. The process may have run out of heap space. This is possibly an internal error.

Action: Verify that the error message file is intact. Try to regenerate error message file. Contact Oracle Support.

##### ORA-07235: slemcw: fwrite error

Cause: Failure to write item to file. The process may have run out of heap space. This is possibly a permissions problem.

Action: Retry operation.

##### ORA-07236: slemop: open error

Cause: Failure to open error file. This is possibly a permissions problem.

Action: Verify permission on error message file. Examine 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. This is an internal error.

Action: Contact Oracle Support.

##### ORA-07238: slemcl: close error

Cause: Failure to close file. This is possibly an OS error.

Action: Contact system administrator. Examine 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. This is an internal error.

Action: Contact Oracle Support.

##### ORA-07240: slemrd: seek error

Cause: Failure to seek to desired position in file. This is possibly an OS error.

Action: Verify that error file is still intact. Verify space on device. Contact system administrator. Examine additional information for errno.

##### ORA-07241: slemrd: read error

Cause: Failure to read file. This is possibly an OS error.

Action: Verify that error file is intact. Regenerate error message file. Contact Oracle Support. Examine additional information for errno.

##### ORA-07242: slembfn: translation error, unable to translate error file name

Cause: Additional information indicates error returned from sltln.

Action: Examine additional information.

##### ORA-07243: sftget: supplied buffer not big enough to hold entire line

Cause: The fgets call read only part of the line, because the supplied buffer was not big enough. This is an internal error.

Action: Contact Oracle 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: Examine errno. There may be a lack of space on device.

##### ORA-07246: sfofi: open error, unable to open database file

Cause: sfofi returns an error. This is an internal error.

Action: Contact Oracle Support.

##### ORA-07247: sfrfb: read error, unable to read requested block from database file

Cause: sfrfb returns an error. This is an internal error.

Action: Contact Oracle Support.

##### ORA-07248: sfwfb: write error, unable to write database block

Cause: sfwfb returns an error. This is an internal error.

Action: Contact Oracle Support.

##### ORA-07249: slsget: open error, unable to open /proc/pid

Cause: Open() returns an error. This is an internal error.

Action: Verify that /proc has the correct permissions.

##### ORA-07250: spcre: semget error, unable to get first semaphore set

Cause: An error occurred when trying to get first semaphore set.

Action: Examine 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: Verify that all semaphores are in use. Verify that system is configured to have semaphores. Examine errno.

##### ORA-07252: spcre: semget error, could not allocate semaphores

Cause: semget system call returned an error. There is possibly a resource limit problem.

Action: Examine 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: Verify semaphore sets. This may require manual cleanup. Examine additional information returned. Consult OS reference manual.

##### ORA-07254: spdcr: translation error while expanding $ORACLE_HOME/bin/oracle

Cause: An error occurred while translating the name of the oracle executable.

Action: Examine 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: Examine 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: Examine errno and sercose[0] for the signal number that failed.

##### ORA-07257: spdcr: translation error expanding program name

Cause: Error occurred when expanding program name ora_PNAME_sid. The result of this translation is put in argv[0] of oracle process.

Action: Examine 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: Examine 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() indicates that a child process terminated.

Action: Examine $ORACLE_HOME/dbs directory for trace or core files. Examine errno.

##### ORA-07260: spdcr: wait error

Cause: Wait system call returned an error.

Action: Examine errno.

##### ORA-07261: spdde: kill error, unable to send signal to process

Cause: Kill system call returned an error. This is possibly an attempt to destroy an already gone process.

Action: Examine errno.

##### ORA-07262: sptpa: sptpa called with invalid process ID

Cause: This is an internal error.

Action: Contact Oracle Support.

##### ORA-07263: sptpa: kill error

Cause: Kill system call returned an error. This is possibly an OS error.

Action: Examine 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: Examine 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: Examine errno. Semaphore ID is returned in sercose[0]. Verify 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. This is an internal error.

Action: Contact Oracle Support.

##### ORA-07267: spwat: invalid process number

Cause: Function was passed an invalid oracle process ID. This is an internal error.

Action: Additional information indicates the invalid process ID.

##### ORA-07268: szguns: getpwuid error

Cause: Getpwuid() failed to 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 successfully execed, but died shortly thereafter.

Action: Examine termination code for information about why process exited. Look for core dump or trace file. Additional information indicates exit code and termination status.

##### ORA-07270: spalck: setitimer error, unable to set interval timer

Cause: An error occurred while trying to set an interval timer. This is probably a porting problem.

Action: Examine errno.

##### ORA-07271: spwat: invalid oracle process number

Cause: Function was called with an invalid oracle process number (0). This is an internal error.

Action: Contact Oracle Support.

##### 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. This is an internal error.

Action: Verify semaphore set index. Verify 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. This is an internal error.

Action: Verify semaphore set index. Verify oracle process number.

##### ORA-07274: spdcr: access error, access to oracle denied

Cause: Failure to access oracle program. Verify that $ORACLE_HOME/bin/oracle or $ORABCKPRG exist and are executable.

Action: Examine errno.

##### ORA-07275: unable to send signal to process

Cause: The kill system call returned an error. This is possibly an attempt to signal a process which does not exist.

Action: Examine 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. This is an internal error.

Action: Contact Oracle Support.

##### ORA-07278: splon: ops$username exceeds buffer length

Cause: Splon constructed an ops$username logon which exceeded the allotted buffer space.

Action: Use a shorter UNIX username or use an Oracle username. Contact Oracle Support.

##### ORA-07279: spcre: semget error, unable to get first semaphore set

Cause: An error occurred when trying to get first semaphore set.

Action: Examine 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. This is possibly an OS error.

Action: Examine additional information for errno. Contact Oracle Support.

##### ORA-07281: slsget: times error, unable to get cpu time

Cause: Times system call returned an error. This is possibly an OS error.

Action: Examine additional information returned. Contact Oracle Support.

##### ORA-07282: sksaprd: string overflow

Cause: The internal buffer is not big enough to hold the archive control string. This is an internal restriction.

Action: 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 the 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 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: Examine 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 path name is not a directory.

Action: Verify that the archive destination directory exists.

##### ORA-07300: smscre: translation error while expanding $ORACLE_HOME/dbs/sgadefsid.dbf

Cause: Failure of sltln($ORACLE_HOME/dbs/sgadefsid.dbf) in smscre.

Action: Examine additional return error for more information.

##### ORA-07301: smscre: $ORACLE_HOME/dbs/sgadefsid.dbf file already exists when creating sga

Cause: The sgadef file should not exist when trying to create the SGA. Otherwise a running instance could be clobbered. The error from sltln is stored in sercose[0].

Action: Verify that database is really down, and delete the sgadef file. This should only happen when system has crashed with the database up. Cleaning up sgadef files can be done out of /etc/rc.

##### ORA-07302: smscre: create failure in creating $ORACLE_HOME/dbs/sgadefsid.dbf

Cause: Create() failed when trying to create the sgadef file.

Action: Verify permissions on $(ORACLE_HOME)/dbs directory.

##### ORA-07303: smscre: 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: DB_BLOCK_SIZE parameter is correct in init.ora.

##### ORA-07304: smscre: 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 correct.

##### ORA-07305: sms1sg: ftok error in creating sga

Cause: The ftok() library call failed in sms1sg().

Action: Verify that the $ORACLE_HOME/dbs/sgadefsid.dbf file exists. If it does, then this is a possible system failure. Perhaps System V compatibility is not enabled.

##### ORA-07306: sms1sg: shmget error, unable to get a shared memory segment

Cause: Error in shmget. The code fails to find a single segment large enough for the entire SGA, but cannot continue to the next allocation model because of a fatal error.

Action: Examine errno. Verify that enough shared memory is available on the system to fit the entire SGA.

##### ORA-07307: sms1sg: shmat error, unable to attach sga

Cause: Failed to attach shared memory segment, after having gotten it.

Action: Examine errno. Verify that the SGA attach address is valid.

##### ORA-07308: smscre: write error when writing $ORACLE_HOME/dbs/sgadefsid.dbf file

Cause: Write call failed in smscre. Possibly, the device is out of space.

Action: Examine errno.

##### ORA-07309: smscre: close error, unable to close $ORACLE_HOME/dbs/sgadefsid.dbf file

Cause: Close system call returned an error. This is possibly an operating system failure.

Action: Examine errno.

##### ORA-07310: smscre: unable to create sga

Cause: All SGA allocation models have been tried, but none succeeded. This is possibly an Oracle system error.

Action: Try reconfiguring the UNIX kernel to fit the entire SGA into one segment.

##### ORA-07311: smsdes: name translation failure of sgadef.dbf file name

Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.

Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number from sltln returned for additional error.

##### ORA-07312: smsdes: open error, unable to open sgadef.dbf file

Cause: Open failed when trying to open sgadef.dbf file. This is possibly a permission problem.

Action: Verify errno. Verify that sgadef.dbf file exists.

##### ORA-07313: smsdes: read error, unable to read sgadef.dbf file

Cause: Read system call returned an error when attempting to read $ORACLE_HOME/dbs/sgadefsid.dbf.

Action: Examine errno. Sgadef file may be corrupted or incompatible with Oracle version.

##### ORA-07314: smsdes: shmctl error when trying to destroy shared memory segment

Cause: Shmctl(IPC_RMID) called failed when trying to destroy shared memory segment. This is possibly a permission problem.

Action: Examine errno. Verify that shared exist. It may be necessary to manually remove segments.

##### ORA-07315: smsdes: close error, unable to close sgadef.dbf file

Cause: An error occurred in close(), when closing sgadef.dbf file. This is possibly an operating system error.

Action: Verify that sgadef.dbf file has been deleted.

##### ORA-07316: smsdes: unlink error, unable to destroy sgadef.dbf file

Cause: Unlink() error occurred when attempting to destroy sgadef.dbf file.

Action: Examine errno. Verify that sgadef.dbf file has been destroyed. This may require manual cleanup.

##### ORA-07317: smsget: translation error when expanding sgadef.dbf filename

Cause: Error occurred translating $ORACLE_HOME/dbs/sgadefsid.dbf.

Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are set correctly. Examine error returned from sltln for additional error.

##### ORA-07318: smsget: open error when opening sgadef.dbf file

Cause: Failure to open sgadef.dbf file. This is possibly a permission problem.

Action: Examine errno. Verify that sgadef.dbf file exists.

##### ORA-07319: smsget: read error when trying to read sgadef.dbf file

Cause: Read had an error when reading sgadef.dbf file.

Action: Examine errno. Verify that the file exists and is correct size.

##### ORA-07320: smsget: shmat error when trying to attach sga

Cause: Failure to attach segment. This is possibly an operating system error.

Action: Examine errno. Sercose[0] returns segment ID. Verify that segment exists and that permissions are correct.

##### ORA-07321: smsget: shmat error, unable to attach segment at requested address

Cause: sercose[0] returns segment ID.

Action: Examine errno.

##### ORA-07322: smsget: close error, unable to close sgadef.dbf file

Cause: Failure to close sgadef.dbf file. This is possibly an OS error.

Action: Retry.

##### ORA-07323: smsfre: shmdt error, unable to delete sga

Cause: Problem deleting shared segments.

Action: Retry. Examine errno. This may require manual cleanup of shared memory segments.

##### ORA-07324: smpall: malloc error while allocating pga

Cause: Malloc library routine returned an error. Possibly, it is out of swap space.

Action: Examine errno.

##### ORA-07325: smsacx: malloc error when allocating context area

Cause: Malloc library routine returned an error. Possibly, it is out of swap space.

Action: Examine errno.

##### ORA-07326: smsfre: attempt to free un-mapped sga

Cause: Smsfre was called when the SGA was not mapped. This is an internal error.

Action: Contact Oracle Support.

##### ORA-07327: smpdal: attempt to destroy pga when it was not mapped

Cause: smpdal was called when the PGA had not been previously created. This is an internal error.

Action: Contact Oracle Support.

##### ORA-07328: smsmax: cannot guess the maximum size for a segment

Cause: shmget system call returned a fatal error.

Action: Examine errno. Additional information indicates the SGA model attempted.

##### ORA-07329: smscsg: too many shared memory segments

Cause: The internal data structure which holds segment information is full.

Action: Reconfigure the UNIX kernel to have bigger segments.

##### ORA-07330: smsnsg: unable to allocate the fixed portion of the SGA

Cause: The fixed portion of the SGA is too big to fit contiguously into one segment.

Action: Reconfigure the UNIX kernel to have bigger segments.

##### ORA-07331: smsnsg: unable to allocate the variable portion of the SGA

Cause: The variable portion of the SGA is too big to fit contiguously into one segment.

Action: Reconfigure the UNIX kernel to have bigger segments.

##### ORA-07332: smsnsg: unable to allocate redo buffers

Cause: Redo block size is too big, preventing each buffer from being allocated contiguously.

Action: Reconfigure the UNIX kernel to have bigger segments, or reduce the value of LOG_BUFFER parameter in init.ora.

##### ORA-07333: smsnsg: unable to allocate database buffers

Cause: Database block size is too big, preventing each buffer from being allocated contiguously.

Action: Reconfigure the UNIX kernel to have bigger segments, or reduce the value of DB_BLOCK_SIZE parameter in init.ora.

##### ORA-07334: smsnsg: too many shared memory segments

Cause: The internal data structure which holds segment information is full.

Action: Reconfigure the UNIX kernel to have bigger segments.

##### ORA-07335: smsmat: ftok error in creating sga

Cause: The ftok() library call failed in smsmat().

Action: Verify that sgadef.dbf file exists. If it does, then this is a possible system failure. Perhaps System V compatibility is not enabled. Additional information indicates the SGA model attempted.

##### ORA-07336: smsmat: shmget error, unable to get a shared memory segment

Cause: Error in shmget.

Action: Examine errno. Verify that enough shared memory is available on the system to fit the entire SGA. Additional information indicates the SGA model attempted.

##### ORA-07337: smsmat: shmat error, unable to attach sga

Cause: Failed to attach shared memory segment, after having gotten it.

Action: Examine errno. Verify that SGA attach address is valid. Additional information indicates the SGA model attempted.

##### ORA-07338: smscre: cannot test for existence of the sga file

Cause: The access system call returned an error. This is possibly an OS error.

Action: Examine errno returned and verify the permission on the sga file.

##### 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-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. This is possibly an internal error.

Action: Contact Oracle Support.

##### 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.

##### ORA-07401: sptrap: cannot restore user exception handlers

Cause: The system failed to restore user exception handlers.

Action: Examine errno and sercose[0] for the signal number that failed.

##### ORA-07402: sprst: cannot restore user signal handler

Cause: The system failed to restore user signal handlers.

Action: Examine errno and sercose[0] for the signal number that failed.

##### ORA-07403: sfanfy: db_writers parameter not valid

Cause: The DB_WRITERS parameter in init.ora exceeds the system-dependent maximum, or is less than 0.

Action: Change the DB_WRITERS parameter in init.ora.

##### ORA-07404: sfareq: Timeout occurred waiting for request to complete

Cause: The master database writer timed out waiting for a write or close to complete. One of the database writers may have stopped running.

Action: Examine all database writer trace files. Shut down the database and try to warm start.

##### ORA-07406: slbtpd: invalid number

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.

##### ORA-07407: slbtpd: invalid exponent

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.

##### ORA-07408: slbtpd: overflow while converting to packed decimal

Cause: An impossible request for binary to decimal conversion was made.

Action: This conversion cannot be performed.

##### ORA-07409: slpdtb: invalid packed decimal nibble

Cause: An impossible request for decimal to binary conversion was made.

Action: This conversion cannot be performed.

##### ORA-07410: slpdtb: number too large for supplied buffer

Cause: An impossible request for decimal to binary conversion was made.

Action: This conversion cannot be performed.

##### ORA-07411: slgfn: full path name too big for supplied buffer

Cause: The supplied buffer is not big enough to hold the full path name.

Action: The construction of the full path name cannot be performed.

##### ORA-07412: sfaslv: error getting entry in asynchronous write array

Cause: One of the database writer processes failed to locate its entry in the SGA.

Action: Contact Oracle Support.

##### ORA-07415: slpath: allocation of memory buffer failed

Cause: Malloc() failed to allocate buffer for storing ORACLE_PATH. System has run out of heap space.

Action: Additional information indicates errno.

##### ORA-07416: slpath: pathname construction failed; lack of output buffer space

Cause: The slpath routine is given a maximum length buffer to expand the name into. An overflow of this buffer occurred. This is possibly an internal error.

Action: Examine output buffer length stored in sercose[0] and constructed pathname length in sercose[1].

##### ORA-07417: sfareq: One or more database writers not active

Cause: One or more of the database writer processes is no longer running.

Action: Examine the trace files for the database writers. Shut down the database and try to warm start.

##### ORA-07418: sfareq: database writer got error in timing function

Cause: An error occurred when the database writer called the system timing function.

Action: Examine the database writer trace file. Shut down database and try to warm start.

##### ORA-07419: sfareq: database writer got error in timing function

Cause: An error occurred when the database writer called the system timing function.

Action: Examine the database writer trace file. Shut down database and try to warm start.

##### ORA-07425: sdpri: error names in translating dump file location

Cause: An oracle error occurred when translating the location of the dump file.

Action: Examine the error code.

##### ORA-07426: spstp: cannot obtain the location of dbs directory

Cause: An oracle error occurred when translating the location of the dbs directory.

Action: Examine additional information for the error returned from sltln.

##### ORA-07427: spstp: cannot change directory to dbs

Cause: chdir system call returned an error. This is possibly a permission problem.

Action: Examine additional information for the OS error code.

##### ORA-07428: smsgsg: ftok() returned error in calculating key for sga

Cause: The ftok() library call failed in smsgsg().

Action: Verify that the $ORACLE_HOME/sgadefsid.dbf file exists. If it does, this is a possible system failure. Perhaps System V compatibility is not enabled. The additional information indicates the segment where the error occurred.

##### ORA-07429: smsgsg: shmget() failed to get segment

Cause: A shared memory segment used for all or part of the SGA failed to be retrieved.

Action: Use the system error number in the error message to determine why the segment failed to be retrieved. If it does not exists, shutdown the database using the "abort" option, and then restart it. If the get failed because the permissions are incorrect, verify that the ownership of the oracle executable is the same as that on the shared memory segment.

##### ORA-07430: smsgsg: calculated and stored keys do not match

Cause: When smsgsg() gets a segment, it re-calculates the key for the segment. It then compares the value against the value stored in the sgadef file. If they do not match, then the file is probably corrupt.

Action: Shutdown the database and restart it.

##### ORA-07431: fork failed

Cause: The server process failed to fork a child process.

Action: Verify that there are enough system resources to support another process. The user or system process limit may have been exceeded, or the amount of free memory or swap space may be temporarily insufficient.

##### ORA-07432: unable to perform nested sleep

Cause: An attempt was made to make a process sleep when it was already sleeping. This platform does not support this capability.

Action: Try the SLEEP command when the process is not sleeping.

##### ORA-07440: WMON process terminated with error

Cause: The wakeup monitor process died.

Action: Warm start instance.

##### ORA-07441: function address must be aligned on address byte boundary

Cause: An improperly aligned function address was specified.

Action: Use a properly aligned function address.

##### ORA-07442: function address must be in the range number to number

Cause: An invalid function address was specified.

Action: Use a valid function address.

##### ORA-07443: function function not found

Cause: An invalid function name was specified.

Action: Use a valid function name.

##### ORA-07444: function address address is not readable

Cause: An invalid function name/address was specified.

Action: Use a valid function name/address.

##### ORA-07445: exception encountered: core dump [exception]

Cause: An OS exception occurred which should result in the creation of a core file. This is an internal error.

Action: Contact Oracle Support.

##### ORA-07446: sdnfy: bad value 'value' for parameter name

Cause: The directory specified as the value for the stated parameter failed to be used.

Action: Verify that the directory specified is a valid directory/file specification.

##### ORA-07447: ssarena: usinit failed

Cause: oracle failed to create a shared arena file.

Action: Use sercerrno field to determine cause of failure.

##### ORA-07448: ssarena: maximum number of shared arenas exceeded

Cause: oracle attempted to create more shared arena files than permitted.

Action: Raise the value for MAX_ARENA in init.ora.

##### ORA-07449: sc: usnewlock failed

Cause: oracle failed to acquire a shared arena lock.

Action: Examine result code in sercerrno to determine the cause of failure.

##### ORA-07450: sms1sg: vm_mapmem error, unable to create shared memory

Cause: Error in vm_mapmem. Failed to create SGA as a single shared memory segment.

Action: Examine result code returned in sercose[0].

##### ORA-07451: sms1sg: shared memory attach address incorrect

Cause: The vm_mapmem system call attached the SGA at an incorrect location.

Action: Verify that the SGA attach address is valid.

##### ORA-07452: sms1sg: failed to change SGA inheritance

Cause: The vm_inherit system called failed to change the inheritance of the SGA. This is possibly an operating system failure.

Action: Examine result code returned in sercose[0].

##### ORA-07453: smsmat: vm_mapmem error, unable to create shared memory

Cause: Error in vm_mapmem. Failure to create a segment of the SGA.

Action: Examine result code returned in sercerrno.

##### ORA-07454: smsmat: shared memory attach address incorrect

Cause: The vm_mapmem system call attached an SGA segment at an incorrect location.

Action: Verify that the SGA attach address is valid.

##### ORA-07455: smsmat: failed to change SGA segment inheritance

Cause: The vm_inherit system call failed to change the inheritance of a segment of the SGA. This is possibly an operating system failure.

Action: Examine result code returned in sercerrno.

##### ORA-07456: smsmax: cannot get cluster size

Cause: The cluster_stat system call failed to return status for the cluster. This is possibly an operating system failure.

Action: Examine result code in sercose[0].

##### ORA-07457: smsdes: name translation failure of sgadef.dbf file name

Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.

Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number returned from sltln in sercose[0].

##### ORA-07458: smsdes: close error, unable to close sgadef.dbf

Cause: An error occurred in close while closing the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly an operating system error.

Action: Verify that the sgadef.dbf file has been deleted.

##### ORA-07459: smsvmfcre: name translation failure of sgadef.dbf file name

Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.

Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number returned from sltln in sercose[0].

##### ORA-07460: smsvmfcre: sgadef.dbf already exists when creating SGA

Cause: The file $ORACLE_HOME/dbs/sgadefsid.dbf should not exist when trying to create the SGA; otherwise, a running instance could be clobbered.

Action: Verify that the database is down, and delete the sgadef.dbf file. This should only happen when the machine crashed with the database up.

##### ORA-07461: smsvmfcre: create failure in creating sgadef.dbf file

Cause: Open failed when trying to create the file $ORACLE_HOME/dbs/sgadefsid.dbf.

Action: Verify permissions on the $(ORACLE_HOME)/dbs directory.

##### ORA-07462: smsget: name translation error of sgadef.dbf file name

Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.

Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number returned from sltln in sercose[0].

##### ORA-07463: smsget: open error when opening sgadef.dbf file

Cause: Open failed when opening the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly a permission problem.

Action: Examine errno. Verify that the file $ORACLE_HOME/dbs/sgadefsid.dbf exists.

##### ORA-07464: smsget: vm_mapmem or vm_allocate error when trying to attach SGA

Cause: The vm_mapmem or vm_allocate system call failed when attempting to attach a segment of the SGA.

Action: Examine result code returned in sercerrno. SGA segment number returned in sercose[1].

##### ORA-07465: smsget: shared memory attach address incorrect

Cause: The vm_mapmem system call attached an SGA segment at an incorrect location.

Action: Verify that the segment exists and that the SGA attach address is valid.

##### ORA-07466: smsget: failed to change SGA segment inheritance

Cause: The vm_inherit system call failed to change the inheritance of a segment of the SGA. This is possibly an operating system failure.

Action: Examine result code returned in sercerrno.

##### ORA-07467: smsget: close error, unable to close sgadef.dbf file

Cause: An error occurred in close while closing the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly an operating system failure.

Action: Examine errno.

##### ORA-07468: spwat: mset error, unable to set semaphore

Cause: The mset routine returned an error. Semaphore may not exist.

Action: Examine result code in sercerrno. Semaphore number returned in sercose[0].

##### ORA-07469: sppst: mclear error, unable to clear semaphore

Cause: The mclear routine returned an error. Semaphore may not exist.

Action: Examine result code in sercerrno. Semaphore number returned in sercose[0].

##### ORA-07470: snclget: cannot get cluster number

Cause: The cluster_status system call failed to get status information for the current cluster. This is possibly an operating system failure.

Action: Examine result code in sercose[0].

##### ORA-07471: snclrd: name translation error of sgadef.dbf file name

Cause: Failure to expand out $ORACLE_HOME/dbs/sgadefsid.dbf file name.

Action: Verify that $(ORACLE_HOME) and (ORACLE_SID) are properly set. Examine error number returned from sltln in sercose[0].

##### ORA-07472: snclrd: open error when opening sgadef.dbf file

Cause: Open failed when opening the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly a permission problem.

Action: Examine errno. Verify that the file $ORACLE_HOME/dbs/sgadefsid.dbf exists.

##### ORA-07473: snclrd: read error when trying to read sgadef.dbf file

Cause: Read had an error when reading sgadef.dbf file.

Action: Examine errno. Verify that file exists and is correct size.

##### ORA-07474: snclrd: close error, unable to close sgadef.dbf file

Cause: An error occurred in close, while closing the file $ORACLE_HOME/dbs/sgadefsid.dbf. This is possibly an operating system failure.

Action: Examine errno.

##### ORA-07475: slsget: cannot get vm statistics

Cause: The vm_statistics system call failed to get virtual memory statistics. This is possibly an operating system failure.

Action: Examine result code in sercerrno.

##### ORA-07476: slsget: cannot get mapped memory statistics

Cause: The vm_mapmem system call failed to get mapped memory statistics. This is possibly an operating system failure.

Action: Examine result code in sercerrno.

##### ORA-07477: scgcmn: lock manager not initialized

Cause: Lock manager must be initialized before converting locks. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07478: scgcmn: cannot get lock status

Cause: lm_stat_lock failed. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07479: scgcmn: cannot open or convert lock

Cause: lm_open or lm_open_convert failed. Possible lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07480: snchmod: cannot change permissions on $ORACLE_HOME/dbs/sgalm.dbf

Cause: When creating an instance, snlmini failed to change the permissions on $ORACLE_HOME/dbs/sgalm.dbf.

Action: Contact Oracle Support.

##### ORA-07481: snlmatt: cannot attach to lock manager instance

Cause: lm_attach failed to attach to lock manager instance. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07482: snlmini: cannot create lock manager instance

Cause: lm_create failed to create lock manager instance.

Action: Verify permissions on $ORACLE_HOME/dbs, and remove $ORACLE_HOME/dbs/sgalm.dbf if it exists, then retry.

##### ORA-07483: snlkget: cannot convert(get) lock

Cause: lm_convert failed to convert(get) lock. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07484: snlkput: cannot convert(put) lock

Cause: lm_convert failed to put lock value. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07485: scg_get_inst: cannot open instance number lock

Cause: lm_open failed. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07486: scg_get_inst: cannot convert(get) instance number lock

Cause: lm_convert failed to get lock value. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07487: scg_init_lm: cannot create lock manager instance

Cause: lm_create failed. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07488: scgrcl: lock manager not initialized

Cause: Lock manager must be initialized before releasing locks. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07489: scgrcl: cannot get lock status

Cause: lm_stat_lock failed during lock release/cancel. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07490: scgrcl: cannot convert lock

Cause: lm_convert failed during lock release/cancel. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07491: scgrcl: cannot cancel lock request

Cause: lm_cancel failed during lock release/cancel. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07492: scgrcl: cannot close lock

Cause: lm_close failed during lock release/cancel. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07493: scgrcl: lock manager error

Cause: An error was encountered releasing the lock. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07494: scgcm: unexpected error

Cause: Unknown or unexpected error code. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07495: spwat: lm_wait failed

Cause: lm_wait failed. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07496: sppst: lm_post failed

Cause: lm_post failed. This is possibly a lock manager failure.

Action: Examine result code in sercerrno.

##### ORA-07497: sdpri: cannot create trace file 'file'; errno = error

Cause: The trace file cannot be created for writing.

Action: Verify if the dump directory exists, and whether it is writable.

##### ORA-07498: spstp: unable to open /dev/resched

Cause: The rescheduling driver /dev/resched is not found or is not working properly.

Action: Examine installation of the Oracle rescheduling driver in the AIX kernel.

##### ORA-07499: spglk: cannot reschedule

Cause: The rescheduling driver /dev/resched is not open. This is an internal error.

Action: Contact Oracle Support.

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