Oracle7 Administrator's Reference for UNIX

Contents Index Home Previous Next

UNIX-Specific Error Messages

ORA-07201 slhom: oracle_home variable not set in environment.

Cause:The $(ORACLE_HOME) environment variable was not set.
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.
Probable internal oracle error. Contact Oracle Worldwide Customer Support Services.

ORA-07203 sltln: attempt to translate a long environment variable.

Cause:A string was passed to sltln containing a long environment variable. The sltln routine accepts environment names of 30 or less characters.
Shorten the 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 may be an Oracle 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:A time() system call returned an error. This may be due to an operating system error.
Check the additional information returned. Contact Oracle Worldwide Customer Support Services.

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

Cause:A gettimeofday() system call returned an error. This may be due to an operating system error.
Check the additional information returned. Contact Oracle Worldwide Customer Support Services.

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 Oracle internal error. Contact Oracle Worldwide Customer Support Services.

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

Cause:The fsync system call returned an error. This may be due to an operating system error.
Check the additional information returned. Contact Oracle Worldwide Customer Support Services.

ORA-07209 sfofi: file size limit was exceeded.

Cause:The size of the file to be opened exceeded the operating system limit imposed on this process.
Run osh to increase the file size limit.

ORA-07210 slcpu: getrusage error, unable to get cpu time.

Cause:A getrusage system call returned an error. This may be due to an operating system error.
Check the additional information returned. Contact Oracle Worldwide Customer Support Services.

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

Cause:A gettimeofday system call returned an error. This may be due to an operating system error.
Check the additional information returned in the operating system reference manual. Contact Oracle Worldwide Customer Support Services.

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

Cause:times system call returned an error. This may be due to an operating system error.
Check the additional information returned. Contact Oracle Worldwide Customer Support Services.

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

Cause:A times system call returned an error. This may be due to an operating system error.
Check the additional information returned in the operating system reference manual. Contact Oracle Worldwide Customer Support Services.

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

Cause:An uname system call returned an error. This may be due to an operating system error.
Check the additional information returned in the operating system reference manual. Contact Oracle Worldwide Customer Support Services.

ORA-07215 slsget: getrusage error.

Cause:A getrusage system call returned an error. This may be due to an operating system error.
Check the additional information returned. Look for information in the operating system reference. Contact Oracle Worldwide Customer Support Services.

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

Cause:A gethostname system call returned an error. This may be due to an operating system error.
Check the additional information returned in the operating system reference manual. Contact Oracle Worldwide Customer Support Services.

ORA-07217 sltln: environment variable cannot be evaluated.

Cause:A getenv call returned a null pointer.
Set the environment variable and try again.

ORA-07218 slkhst: could not perform host operation

Cause:UNIX system() call failed.
Examine system error message.

ORA-07219 slspool: unable to allocate spooler argument buffer.

Cause:The malloc routine failed to allocate space to hold spooler arguments.
Check the additional information returned in the operating system reference manual. The process may have run out of heap space. Contact Oracle Worldwide Customer Support Services.

ORA-07220 slspool: wait error.

Cause:Wait returned an error when waiting for spool job to complete. This may be due to a spooler program error.
Look up the additional information code in your Commands Reference Manual. Contact Oracle Worldwide Customer Support Services.

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.
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 the spooling file.
Verify that line printer spooler is up. Verify that ORACLE_LPPROG and ORACLE_LPARG are set properly. Check exit value returned as additional information.

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

Cause:Fork system call failed to create additional process. Probable resource limit reached.
Look up the additional information code in your Commands Reference Manual and retry the operation. Contact Oracle Worldwide Customer Support Services.

ORA-07224 sfnfy: failed to obtain file size limit; errno = %s.

Cause:The ulimit system call returned an error.
Check error number and contact Oracle Worldwide Customer Support Services.

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

Cause:Additional information returned is error returned from sltln.
Look up the additional information code in your Commands Reference Manual.

ORA-07226 rtneco: unable to get terminal mode.

Cause:The ioctl call returned an error. This may be due to an operating system error.
Check the additional information for error number. Contact Oracle Worldwide Customer Support Services.

ORA-07227 rtneco: unable to set noecho mode.

Cause:The ioctl call returned an error. This may be due to an operating system error.
Check the additional information for an error number. Contact Oracle Worldwide Customer Support Services.

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

Cause:The ioctl call returned an error. This may be due to an operating system error.
Check the additional information for an error number. Contact Oracle Worldwide Customer Support Services.

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

Cause:An error in the mpcntl system call.
Check the error number and contact Oracle Worldwide Customer Support Services.

ORA-07230 slemcr: fopen error, unable to open error file.

Cause:The fopen system call failed to open the file.
Try to determine which file was not opened. Check that the file exists and is accessible.

ORA-07231 slemcc: invalid file handle, seals do not match.

Cause:The function was called with an invalid argument. The file handle used was not obtained by slemcr.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-07232 slemcc: fclose error.

Cause:An error was found when closing the file. This may be due to an operating system error.
Contact your system administrator.

ORA-07233 slemcw: invalid file handle, seals do not match

Cause:A function was called with an invalid file handle. File handle was not obtained by slemcr.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-07234 slemcw: fseek error.

Cause:Unable to seek to desired position in file. This may be due to an operating system error. This may be due to an Oracle internal error.
Verify that error message file is intact. Try to regenerate error message file. Contact Oracle Worldwide Customer Support Services.

ORA-07235 slemcw: fwrite error

Cause:Unable to write item to file. This may be due to an operating system error or a permissions problem.
Retry the operation.

ORA-07236 slemop: open error.

Cause:Unable to open error file. This may be due to a permissions problem.
Verify permission on error message file. Check the additional information for the error number.

ORA-07237 slemcl: invalid file handle, seals do not match.

Cause:A function was called with an invalid file handle. Handle was not obtained by previous call to slemop.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-07238 slemcl: close error.

Cause:Unable to close file. This may be due to an operating system error.
Contact system administrator. Check the additional information for error number.

ORA-07239 slemrd: invalid file handle, seals do not match.

Cause:A function was called with invalid file handle. Handle was not obtained by call to slemop.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-07240 slemrd: seek error.

Cause:Unable to seek to desired position in file. This may be due to an operating system error.
Check that error file is still intact. Verify space on device. Contact system administrator. Check the additional information for the error number.

ORA-07241 slemrd: read error.

Cause:Unable to read file. This may be due to an operating system error.
Verify that the error file is intact. Regenerate the error message file. Contact Oracle Worldwide Customer Support Services. Check the additional information for the error number.

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

Cause:Additional information indicates error returned from sltln.
Look up the additional information code in your Commands Reference Manual and retry the operation

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 Oracle internal error. Contact Oracle Worldwide Customer Support Services. 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 file size limit.
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.
Check the error number. This may be due to a lack of space on the device.

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

Cause:The sfofi routine returns an error.
This is an Oracle internal error.

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

Cause:The sfrfb routine returns an error.
This is an Oracle internal error.

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

Cause:The sfwfb routine returns an error.
This is an Oracle internal error.

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

Cause:An error occurred when trying to get first semaphore set.
Check the error number. Verify that system is configured to have semaphores. Verify that enough semaphores are available. Look up the additional information code in your Commands Reference Manual. Additional information indicates how many semaphores were requested.

ORA-07251 spcre: semget error, could not allocate any semaphores.

Cause:The semget routine failed to allocate any semaphores. Either they are all in use or the system is not configured to have any semaphores.
Check to see if all semaphores are in use. Check to see if system is configured to have semaphores. Look up the additional information code in your Commands Reference Manual.

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

Cause:A semget system call returned an error. This may be due to a resource limit problem.
Check the error number. 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:A semctl system call returned an error.
Check semaphore sets. May require manual cleanup. Look up the additional information code in your Commands Reference Manual.

ORA-07254 spdcr: translation error while expanding ?/bin/oracle.

Cause:An error occurred while translating the name of the oracle executable.
Check sercose[0] for error returned from sltln. The $(ORACLE_HOME) may not be set correctly.

ORA-07255 spini: cannot set up signal handler.

Cause:System failed to set up signal handler.
Check error number 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.
Check the error number and sercose[0] for the signal number that failed.

ORA-07257 spdcr: translation error expanding program name.

Cause:An error occurred when expanding the ora_PNAME_@ program name. The result of this translation is put in argv[0] of oracle process.
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.
Look up the additional information code in your Commands Reference Manual. A system limit on the number of processes may have been exceeded.

ORA-07259 spdcr: exec error, detached process failed in startup

Cause:An oracle detached process died shortly after startup. The wait() system call indicated that a child process terminated.
Check ?/dbs directory for trace or core files.

ORA-07260 spdcr: wait error.

Cause:A wait system call returned an error.
Look up the additional information code in your Commands Reference Manual.

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

Cause:The kill system call returned an error. This is possibly an attempt to destroy a process that is already gone.
Look up the additional information code in your Commands Reference Manual.

ORA-07262 sptpa: sptpa called with invalid process id.

Cause:This is an Oracle internal error.
Contact Oracle Worldwide Customer Support Services.

ORA-07263 sptpa: kill error.

Cause:The kill system call returned an error. This may be an operating system error.
Look up the additional information code in your Commands Reference Manual. Additional information indicates the process ID tested.

ORA-07264 spwat: semop error, unable to decrement semaphore.

Cause:A semop system call returned an error. A semaphore set may not exist.
Look up the additional information code in your Commands Reference Manual. The semaphore ID is returned in sercose[0]. Verify that a semaphore set exists. The error may be due to a shutdown abort while the process was running.

ORA-07265 sppst: semop error, unable to increment semaphore.

Cause:A semop system call returned an error. A semaphore set may not exist.
Look up the additional information code in your Commands Reference Manual. A semaphore ID is returned in sercose[0]. Check semaphore set existence. The error may have occurred because of a shutdown abort while the process was running.

ORA-07266 sppst: invalid process number passed to sppst.

Cause:The sppst function was passed an invalid oracle process ID.
This is an Oracle internal error.

ORA-07267 spwat: invalid process number.

Cause:The spwat function was passed an invalid oracle process ID.
This is an Oracle internal error. Additional information indicates an the invalid process ID.

ORA-07268 szguns: getpwuid error.

Cause:The getpwuid() library routine could not find an entry in the passwd file for a user.
Add an entry for the user in the passwd file.

ORA-07269 spdcr: detached process died after exec.

Cause:Detached process successfully executed, but died shortly thereafter. Additional information indicates exit code and termination status.
Check termination code to determine why the 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. This is probably a porting problem.
Look up the additional information code in your Commands Reference Manual.

ORA-07271 spwat: invalid oracle process number.

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

ORA-07272 spwat: invalid semaphore set id.

Cause:A semaphore ID fetched from SGA was not initialized to a valid value. Additional information returned is semaphore set index and oracle process number.
This is an Oracle internal error. Check the semaphore set index and the oracle process number.

ORA-07273 sppst: invalid semaphore id.

Cause:A semaphore ID fetched from SGA contained an invalid value. Additional information returned is semaphore set index and oracle process number.
This is an Oracle internal error. Check the semaphore set index and the oracle process number.

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

Cause:Unable to access the oracle program. Verify that ?/bin/oracle or $ORABCKPRG exist and are executable.
Look up the additional information code in your Commands Reference Manual.

ORA-07275 unable to send signal to process

Cause:The kill system call returned an error. The error may be due to an attempt to signal a process that does not exist.
Look up the additional information code in your Commands Reference Manual.

ORA-07276 no dba group in /etc/group.

Cause:A group has not been set up for dba users.
Contact your system administrator. Set up a dba group in /etc/group.

ORA-07277 spdde: illegal pid passed as argument.

Cause:A pid equal to 0 was passed to spdde.
This is an Oracle internal error.

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

Cause:The splon routine created an ops$username logon that exceeded the allotted buffer space.
Use a shorter UNIX username or use an Oracle username. Contact Oracle Worldwide Customer Support Services.

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

Cause:An error occurred when trying to set the first semaphore.
Look up the additional information code in your Commands Reference Manual. Verify that the system is configured to have semaphores and that enough semaphores are available. Additional information indicates how many semaphores were requested.

ORA-07280 soarch: malloc of temporary buffer for file-to-file copy failed.

Cause:The malloc() routine failed to allocate buffer for log archiving.
You ran out of heap space on your machine.

ORA-07281 soarch: interrupt received.

Cause:An interrupt was received while archiving the logs.
Retry the operation.

ORA-07282 soaprd: string overflow.

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

ORA-07283 soaprd: invalid volume size for archive destination.

Cause:An invalid volume size was specified.
Specify a valid volume size in archive control string.

ORA-07284 soaprd: volume size specification not terminated properly.

Cause:Non-numeric text follows the volume size specification.
Enter a correct archive control string.

ORA-07285 soaprd: volume size should not be specified for a disk file.

Cause:Volume size was specified for a disk file.
If you are archiving to a disk file, do not specify its volume size.

ORA-07286 soagdi: cannot obtain device information.

Cause:The stat system call on the log archiving device failed.
Check the returned OSD error for the reason the device failure.

ORA-07287 soagdi: unsupported device for log archiving.

Cause:Log archiving to this device is unsupported.
Log archiving to a supported device.

ORA-07288 soabfn: string overflow when constructing filename.

Cause:The internal buffer is not big enough to hold the fully qualified name for archive destination.
This is an internal restriction.

ORA-07289 soafls: write to tape failed.

Cause:The write system call failed on the tape device.
Check addition information for the operating system error. Verify that the tape is mounted correctly.

ORA-07290 soagdi: specified directory for archiving does not exist.

Cause:The specified pathname is not a directory.
Verify that the archive destination directory exists.

ORA-07292 soaotp: tape volume is too small to accommodate the log file.

Cause:The current tape volume cannot accommodate the entire log file.
Increase the tape volume size or decrease the size of the log file. Additional information indicates the size of the log file and tape volume size.

ORA-07293 soaotp: cannot open the current tape volume.

Cause:The open system call failed on the tape device.
Check additional information for the operating system error.

ORA-07294 soaotp: cannot allocate buffer for tape write.

Cause:The malloc() routine failed to allocate buffer for writing to tape.
You have run out of heap space on your machine.

ORA-07295 soaotp: cannot find out the status of log file.

Cause:The stat system call failed to return the status of log file.
Verify that the log file still exists. Check additional information for an operating system error.

ORA-07296 soaotp: lseek error, unable to seek to beginning of log file.

Cause:An lseek failed to seek to the beginning of log file.
Check additional information for an operating system error.

ORA-07297 soaotp: read error, unable to read header block.

Cause:The read system call was unable to read log file and returned an error.
Check additional information for an operating system error.

ORA-07298 soacls: trying to close a file that has been closed.

Cause:The system is trying to close a file with an invalid file descriptor.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-07299 soacls: failed to close the tape device.

Cause:The close system call failed on the tape device.
Verify that the tape is still online. Check additional information for an operating system error.

ORA-07300 smscre: translation error while expanding ?/dbs/sgadef@.dbf.

Cause:There was a failure of sltln(?/dbs/sgadef@.dbf) in smscre.
Check additional return error for more information.

ORA-07301 smscre: ?/dbs/sgadef@.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 destroyed. The error from sltln is stored in sercose[0].
Verify that database is down and delete the sgadef file. This should only happen when system has crashed with the database up. Clean up sgadef files from /etc/rc.

ORA-07302 smscre: create failure in creating ?/dbs/sgadef@.dbf.

Cause:The create() routine failed when trying to create the sgadef file.
Verify permissions on the $(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.
Verify that the db_block_size parameter is correct in the init.ora file.

ORA-07304 smscre: illegal redo buffer size.

Cause:The redo buffer size must be a multiple of the machine block size.
Verify that the log_buffer of the init.ora file is correctly set.

ORA-07305 sms1sg: ftok error in creating sga.

Cause:The ftok() library call failed in sms1sg().
Verify that the ?/dbs/sgadef@.dbf file exists. If it exists, the error may be due to a system failure, such as System V compatibility not being enabled.

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

Cause:There is an 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 due to a fatal error.
Look up the additional information code in your Commands Reference Manual. Verify that enough shared memory is available on the system for the entire SGA.

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

Cause:Got the shared memory segment, but failed to attach it.
Look up the additional information code in your Commands Reference Manual. Verify that the SGA attach address is valid.

ORA-07308 smscre: write error when writing ?/dbs/sgadef@.dbf file.

Cause:A write call failed in smscre.
Look up the additional information code in your Commands Reference Manual. The device may be out of space.

ORA-07309 smscre: close error, unable to close ?/dbs/sgadef@.dbf file.

Cause:A close system call returned an error.
Look up the additional information code in your Commands Reference Manual. The error may be due to an operating system failure.

ORA-07310 smscre: unable to create sga.

Cause:All SGA allocation models were tried, but none succeeded.
This may be an Oracle system error. Try reconfiguring the UNIX kernel to fit the SGA into one segment.

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

Cause:Unable to expand the ?/dbs/sgadef@.dbf filename.
Verify that $(ORACLE_HOME) and $(ORACLE_SID) are properly set. Check the error number returned from sltln in your Commands Reference Manual.

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

Cause:Open failed when trying to open the sgadef.dbf file.
Look up the additional information code in your Commands Reference Manual. Verify that the sgadef.dbf file exists. The error may be due to a permission problem.

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

Cause:The read system call returned an error when attempting to read the ?/dbs/sgadef@.dbf file.
Look up the additional information code in your Commands Reference Manual. The sgadef file may be corrupted or incompatible with the Oracle version.

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

Cause:The shmctl(IPC_RMID) call failed when trying to destroy shared memory segment.
Look up the additional information code in your Commands Reference Manual. Verify that shared memory segments exist. There may be a permission problem; 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 the sgadef.dbf file.
Verify that the sgadef.dbf file was deleted. There may be an operating system error.

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

Cause:An unlink() error occurred when attempting to destroy the sgadef.dbf file.
Look up the additional information code in your Commands Reference Manual. Verify that the sgadef.dbf file has been destroyed. Manual cleanup may be required.

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

Cause:An error occurred translating ?/dbs/sgadef@.dbf.
Verify that $(ORACLE_HOME) and $(ORACLE_SID) are set correctly. Check the error returned from sltln as an additional error.

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

Cause:Unable to open the sgadef.dbf file.
Look up the additional information code in your Commands Reference Manual. There may be a permission problem. Verify that the sgadef.dbf file exists.

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

Cause:The read routine had an error when reading the sgadef.dbf file.
Look up the additional information code in your Commands Reference Manual. Verify that the file exists and is the correct size.

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

Cause:Unable to attach a segment.
Look up the additional information code in your Commands Reference Manual. The sercose[0] routine returns a segment ID. Verify that the segment exists and that the permissions are correct.

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

Cause:The sercose[0] routine returned a segment ID.
Look up the additional information code in your Commands Reference Manual. The error may be due to an operating system error.

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

Cause:Unable to close the sgadef.dbf file.
Retry the operation. The error may be due to an operating system error.

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

Cause:Unable to delete shared segments.
Retry the operation. Look up the additional information code in your Commands Reference Manual. Manual cleanup of shared memory segments may be required.

ORA-07324 smpall: malloc error while allocating pga.

Cause:The malloc library routine returned an error.
Look up the additional information code in your Commands Reference Manual. The system may be out of swap space.

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

Cause:The malloc library routine returned an error.
Look up the additional information code in your Commands Reference Manual. The error may be due to lack of swap space.

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

Cause:The smsfre routine was called when the SGA was not mapped.
This is an Oracle internal error.

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

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

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

Cause:The shmget system call returned a fatal error.
Look up the additional information code in your Commands Reference Manual. Additional information indicates the SGA model attempted.

ORA-07329 smscsg: too many shared memory segments.

Cause:The internal data structure that holds segment information is full.
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.
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.
Reconfigure the UNIX kernel to have bigger segments.

ORA-07332 smsnsg: unable to allocate redo buffers.

Cause:The redo block size is too big, preventing contiguous allocation of buffers.
Reconfigure the UNIX kernel to have bigger segments or reduce the value of the log_buffer parameter in the init.ora file.

ORA-07333 smsnsg: unable to allocate database buffers.

Cause:The database block size is too big, preventing contiguous allocation of buffers.
Reconfigure the UNIX kernel to have bigger segments, or reduce the value of db_block_size parameter in the init.ora.

ORA-07334 smsnsg: too many shared memory segments.

Cause:The internal data structure that holds segment information is full.
Reconfigure the UNIX kernel to have bigger segments.

ORA-07335 smsmat: ftok error in creating sga.

Cause:The ftok() library call failed in smsmat().
Verify that the sgadef.dbf file exists. If it exists, the error may be due to a system failure, such as System V compatibility not being enabled. Additional information indicates the SGA model attempted.

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

Cause:There is an error in shmget.
Look up the additional information code in your Commands Reference Manual. 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:Got a shared memory segment and failed to attach it.
Look up the additional information code in your Commands Reference Manual. 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 may be due to an operating system error.
Look up the additional information code in your Commands Reference Manual. Check 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.
Reconfigure the operating system to have more semaphores per set.

ORA-07340 sfccf: fstat error, unable to obtain file status.

Cause:Unable to obtain the file status. An error closing file is returned as additional information.
Verify that the database files exist and have proper permissions.

ORA-07341 sfsrd: invalid block number.

Cause:The block number requested was out of bounds for the file. Additional information indicates the block number.
Verify the block number.

ORA-07342 sfsrd: lseek error, unable to seek to requested block

Cause:An lseek system call returned an error.
Look up the additional information code in your Commands Reference Manual. Check the block number.

ORA-07343 sfsrd: read error, unable to read requested block.

Cause:A read system call returned an error.
Look up the additional information code in your Commands Reference Manual. Additional information indicates the block number.

ORA-07344 sfsrd: seals do not match.

Cause:A function was called with an invalid argument.
This is an Oracle internal error.

ORA-07347 sfsrd: simulated error for testing purposes.

Cause:An error was generated from internal testing procedures.
This is an Oracle internal error.

ORA-07350 sfccf: 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.
The block size specified is returned as additional information. Check the init.ora parameters.

ORA-07351 sfccf: malloc error, unable to allocate write buffer.

Cause:The malloc library routine returned an error.
Verify that adequate system resources are available.

ORA-07352 sfccf: create error, unable to create file.

Cause:A create system call returned an error because it was unable to create a database file.
Verify the filename and permissions.

ORA-07353 sfccf: close error, unable to close file.

Cause:A close system call returned an error.
Look up the additional information code in your Commands Reference Manual.

ORA-07354 sfccf: open error, unable to open file.

Cause:An open system call returned an error because it was unable to open a database file.
Look up the additional information code in your Commands Reference Manual.

ORA-07355 sfccf: fstat error, unable to obtain file status.

Cause:Unable to obtain file status. An error closing file is returned as additional information.
Verify that the database files exist and have proper permissions.

ORA-07356 sfccf: lseek error, unable to seek to beginning of file.

Cause:An lseek system call returned an error.
Look up the additional information code in your Commands Reference Manual. Additional information indicates if a close also failed.

ORA-07357 sfccf: write error, unable to write database header block.

Cause:A write system call returned an error because it was unable to write a database file.
Look up the additional information code in your Commands Reference Manual.

ORA-07358 sfccf: write error, unable to write to file.

Cause:An sfccf system call returned an error.
Look up the additional information code in your Commands Reference Manual. Additional information indicates if a close failed. The error may be due to a lack of space on the device.

ORA-07359 sfifi: invalid logical block size.

Cause:A blocksize was specified that is incorrect. The logical block size must be a multiple of the physical block size, and smaller than the maximum.
Additional information returns the block size specified. Check block size parameters in the init.ora file.

ORA-07360 sfifi: stat error, unable to obtain information about file.

Cause:A stat system call returned an error.
Look up the additional information code in your Commands Reference Manual. Check to see if the file exists.

ORA-07361 sfifi: malloc error, unable to allocate buffer for header block.

Cause:The malloc library routine returned an error.
This error may be due to an memory resource shortage.

ORA-07362 sfifi: open error, unable to open file.

Cause:The open system call returned an error.
Look up the additional information code in your Commands Reference Manual. Verify that the file exists and check the permissions of the database files.

ORA-07363 sfifi: lseek error, unable to seek to beginning of file.

Cause:An lseek system call returned an error.
Look up the additional information code in your Commands Reference Manual. Additional information indicates if there was an error in closing the file.

ORA-07364 sfifi: read error, unable to read header block.

Cause:The read system call returned an error because it was unable to read a database file.
Look up the additional information code in your Commands Reference Manual.

ORA-07365 sfifi: close error.

Cause:A close system call returned an error.
Look up the additional information code in your Commands Reference Manual.

ORA-07366 sfifi: invalid file, file does not have valid header block.

Cause:This file does not appear to be a valid database file.
Verify that the database files are correct.

ORA-07367 sfifi: logical block size mismatch.

Cause:The logical block size of file is not the expected block size.
Verify that the logical block sizes are correct.

ORA-07368 sfofi: open error, unable to open database file.

Cause:An open system call returned an error.
Look up the additional information code in your Commands Reference Manual. Verify that the file exists and that the permissions of the database files are valid.

ORA-07369 sfcfi: close error, unable to close database file.

Cause:The close system call returned an error.
Look up the additional information code in your Commands Reference Manual.

ORA-07370 sfrfb: invalid block number.

Cause:The block number requested was out of bounds for the file.
Additional information indicates block number. Verify the block number.

ORA-07371 sfrfb: lseek error, unable to seek to requested block

Cause:The sfrfb routine returned an error.
Look up the additional information code in your Commands Reference Manual. Additional information returns block number. Check the block number.

ORA-07372 sfrfb: read error, unable to read requested block from database file.

Cause:The read system call returned an error.
Look up the additional information code in your Commands Reference Manual. Additional information indicates block number.

ORA-07373 sfrfb: read returned incorrect number of bytes.

Cause: This may be due to a truncated read of database file.
Additional information returns the block number and number of bytes read. Check the block number and number of bytes read.

ORA-07374 sfwfb: invalid block number.

Cause:The file block number is out of the range of the file.
Additional information returns the block number. Check the block number.

ORA-07375 sfwfb: lseek error, unable to seek to requested block.

Cause:An lseek system call returned an error.
Additional information indicates the block number. Verify the block number.

ORA-07376 sfwfb: write error, unable to write database block.

Cause:A write system call returned an error.
Additional information returns block number. Look up the additional information code in your Commands Reference Manual. Check the block number.

ORA-07377 sfwfb: write returned incorrect number of bytes.

Cause:A write system call returned an error. This may be due to a truncated write.
Additional information returns block the number and number of bytes. Check the block number and number of bytes written.

ORA-07378 sfcmf: translation error, unable to expand file name.

Cause:Unable to expand filename.
Additional information returns error returned from sltln. Check additional information.

ORA-07379 sfcmf: new file exists.

Cause:Attempt to create a new database file with existing filename. This could destroy a database file.
Check the filename. Verify that new file does not exist.

ORA-07380 sfcmf: translation error, unable to expand old file name.

Cause:Unable to expand old filename.
Additional information indicates a sltln error. Check additional information.

ORA-07381 sfccf: translation error, unable to expand file name.

Cause:Unable to expand filename.
Additional information indicates sltln error. Check additional information.

ORA-07382 sfifi: translation error, unable to expand file name.

Cause:Unable to expand filename.
Additional information indicates an sltln error. Check additional information.

ORA-07383 sfgfs: seals do not match.

Cause:A function was called with an invalid argument.
This is an Oracle internal error.

ORA-07384 sfgfn: seals do not match.

Cause:A function was called with an invalid argument.
This is an Oracle internal error.

ORA-07385 sfcfi: seals do not match.

Cause:A function was called with an invalid argument.
This is an Oracle internal error.

ORA-07386 sfrfb: seals do not match.

Cause:A function was called with an invalid argument.
This is an Oracle internal error.

ORA-07387 sfwfb: seals do not match.

Cause:A function was called with an invalid argument.
This is an Oracle internal error.

ORA-07388 sfccf: reuse specified, but file does not exist.

Cause:The reuse option was specified to create database statement, but file to reuse does not exist.
Verify that the file exists or do not specify reuse.

ORA-07389 sfccf: open error, unable to open file to reuse.

Cause:An open system call returned an error.
Look up the additional information code in your Commands Reference Manual.

ORA-07390 sftopn: translate error, unable to translate file name.

Cause:An error occurred while expanding the filename to open.
Additional information returns error generated in translation routine. Look up additional error code for further information.

ORA-07391 sftopn: fopen error, unable to open text file.

Cause:The fopen library routine returned an error.
Verify that the file exists and that you have the correct permissions.

ORA-07392 sftcls: fclose error, unable to close text file.

Cause:The fclose library routine returned an error
This may be due to an internal Oracle error.

ORA-07393 sfccf: file mismatch, trying to reuse a file with different size.

Cause:The file size does not match.
If the error occurred while closing the file, additional information indicates the error number. Verify that the file size is correct.

ORA-07394 sfccf: file mismatch, trying to reuse a file with different block size.

Cause:The logical block size does not match.
Verify that the logical block size is correct. If the error occurred while closing the file, additional information indicates the error number.

ORA-07395 sfccf: function called with illegal option.

Cause:A function was called with an invalid parameter.
This may be due to an Oracle internal error.

ORA-07396 sfccf: lseek error, unable to seek to beginning of reuse file.

Cause:An lseek system call returned an error.
Look up the additional information code in your Commands Reference Manual.

ORA-07397 sfccf: read error, unable to read header block of file.

Cause:A read system call returned an error.
Look up the additional information code in your Commands Reference Manual.

ORA-07398 sfccf: invalid header information, file is not a valid database file.

Cause:The system encountered invalid header information.
Verify that file is a database file.

ORA-07399 sfccf: file exists.

Cause:Trying to create a database file, but file by that name already exists
Verify that the name is correct; specify reuse if necessary.

ORA-07400 slemtr: translated name for the message file is too long.

Cause:The name for the message file overflows the internal buffer.
Try making the complete pathname 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.
Look up the additional information code in your Commands Reference Manual. Check the error number 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.
Look up the additional information code in your Commands Reference Manual. Check the error number and sercose[0] for the signal number that failed.

ORA-07403 sfanfy: db_writers parameter not valid.

Cause:The db_writers parameter in the init.ora file exceeds the maximum or is less than 0.
Change the db_writers parameter in the init.ora file.

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.
Check all database writer trace files. Shut down the database and try to warm start.

ORA-07405 sfcfi: Close failed in one of the database writers.

Cause:One of the database writer processes got an error when closing a file.
Check the error number in all database writer trace files.

ORA-07406 slbtpd: invalid number.

Cause:An impossible request for binary to decimal conversion was made.
This conversion cannot be performed.

ORA-07407 slbtpd: invalid exponent.

Cause:An impossible request for binary to decimal conversion was made
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.
This conversion cannot be performed.

ORA-07409 slpdtb: invalid packed decimal nibble.

Cause:An impossible request for decimal to binary conversion was made.
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.
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.
The construction of the full pathname cannot be performed.

ORA-07412 sfaslv: Error getting entry in asynchronous write array.

Cause:One of the database writer processes could not locate its entry in the SGA.
Contact Oracle Worldwide Customer Support Services.

ORA-07413 sfcopy: source and destination logical block sizes must match.

Cause:The destination file supplied to sfcopy has a different logical block size than the source file.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-07414 sfcopy: allocation of memory buffer failed.

Cause:The malloc() routine failed to allocate the temporary buffer for copying data from the source file to the destination file.
The system ran out of heap space.

ORA-07415 slpath: allocation of memory buffer failed.

Cause:The malloc() routine failed to allocate a buffer for storing ORACLE_PATH. The system has run out of heap space.
Additional information indicates the error number.

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

Cause:The slpath routine is given a maximum length buffer into which to expand the name. An overflow of this buffer occurred.
This error may be due to an Oracle internal error. Check the output buffer length stored in sercose[0] and the 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.
Check 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.
Check 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.
Check the database writer trace file. Shut down database and try to warm start.

ORA-07420 sfccf: Illegal file type.

Cause:Cannot initialize a file of illegal file type.
Verify that the filename is correct. The supported file types are raw devices and regular files.

ORA-07421 sfcopy: failed to read from the source file during copy.

Cause:An error occurred when reading from the source file.
Check additional information.

ORA-07422 sfcopy: failed to write to the destination file during copy.

Cause:An error occurred while writing to the destination file.
Check additional information.

ORA-07423 sfrfb: read failed because buffer was not aligned properly.

Cause:The I/O buffer was not aligned to the correct boundary.
THis is an Oracle internal error. Keep the trace file and contact Oracle Worldwide Customer Support Services.

ORA-07424 sfwfb: write failed because buffer was not aligned properly.

Cause:The I/O buffer was not aligned to the correct boundary.
This is an Oracle internal error. Keep the trace file and contact Oracle Worldwide Customer Support Services.

ORA-07425 sdpri: error %s in translating dump file location.

Cause:An Oracle error occurred when translating the location of dump file.
Check the Oracle 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.
Check additional information for the error returned from sltln.

ORA-07427 spstp: cannot change directory to dbs.

Cause:A chdir system call returned an error. This may be due to permission problems.
Check additional information for the operating system error code.

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

Cause:A ftok() library call failed in smsgsg().
Verify that the ${ORACLE_HOME}/sgadef${ORACLE_SID}.dbf file exists. If it exists, the error may be due to a system failure, such as System V compatibility not being enabled. The additional information indicates the segment in which the error occurred.

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

Cause:A shared memory segment used for a part of the SGA could not be retrieved.
Use the system error number in the error message to determine why the segment could not be retrieved. If it does not exist, shutdown the database using the abort option, and then restart it. If the get failed because the permissions are incorrect, make sure 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 to the value stored in the sgadef file. If they do not match, the file is probably corrupt.
Shut down the database and restart it.

ORA-07431 fork failed

Cause:The server process was unable to fork a child process.
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.
Try the SLEEP command when the process is not sleeping.

ORA-07433 sfrnms: the mirror side status parameter is invalid

Cause:The mirror side status passed to sfrnms is invalid.
This is an Oracle internal error.

ORA-07434 sfgmsn: the mirror side status parameter is invalid

Cause:The mirror side status passed to sfgmsn is invalid.
This is an Oracle internal error.

ORA-07435 invalid parameter passed to an resilvering testing function *Document: NO

Cause:A parameter passed to resilvering testing functions via the event mechanism is invalid.
Read the alert log for detailed error messages. Specify the correct parameters.

ORA-07440 WMON process terminated with error

Cause:The wakeup monitor process died.
Warm start the instance.

ORA-07441 function address must be aligned on %s byte boundary

Cause:An improperly aligned function address was specified.
Use a properly aligned function address.

ORA-07442 function address must be in the range %s to %s

Cause:An invalid function address was specified.
Use a valid function address.

ORA-07443 function %s not found

Cause:An invalid function name was specified.
Use a valid function name.

ORA-07444 function address %s is not readable

Cause:An invalid function name address was specified.
Use a valid function name address.

ORA-07445 exception encountered: core dump [%s] [%s] [%s] [%s] [%s] [%s]

Cause:An operating system exception occurred that should result in the creation of a core file. This is an Oracle internal error.
Contact Oracle Worldwide Customer Support Services.

ORA-07446 sdnfy: bad value '%s' for parameter %s.

Cause:The directory specified as the value for the stated parameter could not be used.
Make sure the directory you specified has a valid directory and file specification.

ORA-07447 ssarena: usinit failed.

Cause:Oracle failed to create a shared arena file.
Use the sercerrno field to determine the cause of the failure.

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

Cause:Oracle attempted to create more shared arena files than permitted.
Increase the value for max_arena in the init.ora file.

ORA-07449 sc: usnewlock failed.

Cause:Oracle failed to acquire a shared arena lock.
Check the result code in sercerrno to determine the cause of the failure.

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

Cause:There is an error in vm_mapmem. Failed to create SGA as a single shared memory segment.
Check the result code returned in sercose[0].

ORA-07451 sms1sg: shared memory attach address incorrect.

Cause:A vm_mapmem system call attached the SGA at an incorrect location.
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.
Check the result code returned in sercose[0]. This may be due to an operating system failure.

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

Cause:There is an error in vm_mapmem. Failed to create a segment of the SGA.
Check the 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.
Verify that the SGA attach address is valid.

ORA-07455 smsmat: failed to change SGA segment inheritence.

Cause:The vm_inherit system call failed to change the inheritance of a segment of the SGA.
Check the result code returned in sercerrno. This may be due to an operating system failure.

ORA-07456 smsmax: cannot get cluster size

Cause:A cluster_stat system call failed to return the status for the cluster.
Check the result code in sercose[0]. This may be due to an operating system failure.

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

Cause:Unable to expand the ?/dbs/sgadef@.dbf filename.
Verify that $(ORACLE_HOME) and $(ORACLE_SID) are properly set. Check the error number returned from sltln in sercose[0].

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

Cause:An error occurred in the close routine, while closing the ?/dbs/sgadef@.dbf file.
Verify that sgadef.dbf file has been deleted. This may be due to an operating system error.

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

Cause:Unable to expand the ?/dbs/sgadef@.dbf filename.
Verify that $(ORACLE_HOME) and $(ORACLE_SID) are properly set. Check the error number returned from sltln in sercose[0].

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

Cause:The ?/dbs/sgadef@.dbf file should not exist when trying to create the SGA; otherwise a running instance could be destroyed.
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:The open routine failed when trying to create the ?/dbs/sgadef@.dbf file.
Verify the permissions on the $(ORACLE_HOME)/dbs directory.

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

Cause:Unable to expand the ?/dbs/sgadef@.dbf filename.
Verify that $(ORACLE_HOME) and $(ORACLE_SID) are properly set. Check the error number returned from sltln in sercose[0].

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

Cause:Failure opening the ?/dbs/sgadef@.dbf file.
Look up the additional information code in your Commands Reference Manual. The error may be due to an permission problem. Verify that the ?/dbs/sgadef@.dbf file 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.
Check the result code returned in sercerrno. The SGA segment number is 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.
Verify that the segment exists and the SGA attach address is valid.

ORA-07466 smsget: failed to change SGA segment inheritence.

Cause:The vm_inherit system call failed to change the inheritence of a segment of the SGA.
Check the result code returned in sercerrno. This may be due to an operating system failure.

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

Cause:An error occurred while closing the ?/dbs/sgadef@.dbf file.
Look up the additional information code in your Commands Reference Manual. The error may be due to an operating system error.

ORA-07468 spwat: mset wrror, unable to set semaphore.

Cause:The mset routine returned an error. Semaphore may not exist.
Check the 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.
Check the 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.
Check the result code in sercose[0]. This may be due to an operating system failure.

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

Cause:Unable to expand the ?/dbs/sgadef@.dbf filename.
Cause:Verify that the $(ORACLE_HOME) and $(ORACLE_SID) are properly set. Check the error number returned from sltln in sercose[0].
ORA-07472 snclrd: open error when opening sgadef.dbf file.

Cause:Failed to open the ?/dbs/sgadef@.dbf file.
Look up the additional information code in your Commands Reference Manual. The error may be due to a permission problem. Verify that the ?/dbs/sgadef@.dbf file exists.

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

Cause:Unable to read the sgadef.dbf file.
Look up the additional information code in your Commands Reference Manual. Verify that the file exists and is the correct size.

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

Cause:An error occurred while closing the ?/dbs/sgadef@.dbf file.
Look up the additional information code in your Commands Reference Manual. The error may be due to an operating system error.

ORA-07475 slsget: cannot get vm statistics.

Cause:The vm_statistics system call failed to get virtual memory statistics.
Check the result code in sercerrno. The error may be due to an operating system failure.

ORA-07476 slsget: cannot get mapped memory statistics.

Cause:The vm_mapmem system call failed to get mapped memory statistics.
Check result code in sercerrno. The error may be due to an operating system failure.

ORA-07477 scgcmn: lock manager not initialized.

Cause:The lock manager must be initialized before converting locks.
Check the result code in sercerrno. The error may be due to a lock manager failure.

ORA-07478 scgcmn: cannot get lock status.

Cause:A lm_stat_lock failed.
Check the result code in sercerrno. The error may be due to a lock manager failure.

ORA-07479 scgcmn: cannot open or convert lock.

Cause:An lm_open or lm_open_convert failed.
Check the result code in sercerrno. The error may be due to a lock manager failure.

ORA-07480 snchmod: cannot change permissions on ?/dbs/sgalm.dbf.

Cause:When creating an instance, snlmini could not change the permissions on ?/dbs/sgalm.dbf.
Contact Oracle Worldwide Customer Support Services.

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

Cause:An lm_attach failed to attach to lock manager instance.
Check the result code in sercerrno. The error may be due to a lock manager failure.

ORA-07482 snlmini: cannot create lock manager instance.

Cause:An lm_create failed to create lock manager instance.
Check the permissions on the ?/dbs, and remove ?/dbs/sgalm.dbf file, if it exists, then retry.

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

Cause:An lm_convert failed to convert or get a lock.
Check the result code in sercerrno. The error may be due to a lock manager failure.

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

Cause:An lm_convert failed to put lock value.
Check the result code in sercerrno. The error may be due to an lock manager failure.

ORA-07485 scg_get_inst: cannot open instance number lock.

Cause:An lm_open failed.
Check the result code in sercerrno. The error may be due to an lock manager failure.

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

Cause:An lm_convert failed to get lock value.
Check the result code in sercerrno. The error may be due to an lock manager failure.

ORA-07487 scg_init_lm: cannot create lock manager instance.

Cause:An lm_create failed.
Check the result code in sercerrno. The error may be due to an lock manager failure.

ORA-07488 scgrcl: lock manager not initialized.

Cause:The lock manager must be initialized before releasing locks.
Check the result code in sercerrno. The error may be due to an lock manager failure.

ORA-07489 scgrcl: cannot get lock status.

Cause:An lm_stat_lock failed during a lock release or cancel.
Check the result code in sercerrno. The error may be due to an lock manager failure.

ORA-07490 scgrcl: cannot convert lock.

Cause:An lm_convert failed during a lock release or cancel.
Check the result code in sercerrno. The error may be due to an lock manager failure.

ORA-07491 scgrcl: cannot cancel lock request.

Cause:An lm_cancel failed during a lock release or cancel.
Check the result code in sercerrno. The error may be due to an lock manager failure.

ORA-07492 scgrcl: cannot close lock.

Cause:An lm_close failed during a lock release or cancel.
Check the result code in sercerrno. The error may be due to an lock manager failure.

ORA-07493 scgrcl: lock manager error.

Cause:An error occurred while releasing a lock.
Check the result code in sercerrno. The error may be due to an lock manager failure.

ORA-07494 scgcm: unexpected error.

Cause:Unknown or unexpected error code.
Check the result code in sercerrno. The error may be due to an lock manager failure.

ORA-07495 spwat: lm_wait failed.

Cause:An lm_wait failed.
Check the result code in sercerrno. The error may be due to an lock manager failure.

ORA-07496 sppst: lm_post failed.

Cause:An lm_post failed.
Check the result code in sercerrno. The error may be due to an lock manager failure.

ORA-07497 sdpri: cannot create trace file '%s'; errno = %s.

Cause:The trace file cannot be created for writing.
Verify that the dump directory exists is writable.

ORA-07498 spstp: Unable to open /dev/resched.

Cause:The /dev/resched rescheduling driver was not found or is not working properly.
Check the installation of the ORACLE rescheduling driver in the AIX kernel.

ORA-09700 sclin: maximum number of latches exceeded

Cause:Oracle wants to use more latches then available.
Increase the latch_pages parameter in the init.ora file or decrease the amount of shared memory you are using.

ORA-09701 scnfy: maximum number of processes exceeded

Cause:The processes parameter in the init.ora file was exceeded.
Decrease the processes parameter and restart.

ORA-09702 sem_acquire: cannot acquire latch semaphore

Cause:The semaphore used for accessing latches could not be seized.
Send the trace file to Oracle Worldwide Customer Support Services, along with information on reproducing the error.

ORA-09703 sem_release: cannot release latch semaphore

Cause:The semaphore used for accessing latches could not be released.
Send the trace file to Oracle Worldwide Customer Support Services, along with information on reproducing the error.

ORA-09704 sstascre: ftok error in creating test and set pages.

Cause:The ftok() library call failed in sstascre().
Verify that the tasdef@.dbf file exists. If it exists, the error may be due to a system failure, such as System V compatibility not being enabled.

ORA-09705 spcre: cannot initialize latch semaphore

Cause:The semaphore used for accessing latches could not be initialized.
Send the trace file to Oracle Worldwide Customer Support Services, along with information on reproducing the error.

ORA-09706 slsget: get_process_stats error.

Cause:The get_process_stats system call returned an error. This may be due to an operating system error.
Look up the additional information code in your Commands Reference Manual. Contact Oracle Worldwide Customer Support Services.

ORA-09707 sfccf: maximum length of ORACLE_SID exceeded

Cause:Too many characters are in the ORACLE_SID string.
Rename the ORACLE_SID to a string of up to the maximum number of characters specified for your system.

ORA-09708 soacon: failed to bind socket to port.

Cause:The bind system call failed on the socket.
Check additional information for an operating system error. Try connecting again.

ORA-09709 soacon: failed to accept a connection.

Cause:The accept system call failed on the socket.
Check additional information for an operating system error. Try connecting again.

ORA-09710 soarcv: buffer overflow.

Cause:The internal buffer is not large enough to hold the message read.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09711 orasrv: archmon already connected.

Cause:An existing connection has already been made from archmon to orasrv.
Stop trying to connect.

ORA-09712 orasrv: log archiver already connected.

Cause:An existing connection has already been made from the log archiver to orasrv.
Stop trying to connect.

ORA-09713 soadum: cannot do log archiving to tape.

Cause:You are missing the communication driver for the log archiver to communicate with the console process.
Install the communication driver.

ORA-09714 Two Task interface: cannot obtain puname

Cause:The txipx driver cannot obtain the name of the PU. This may be due to an operating system error.
Check if the PUs are named and consistent.

ORA-09715 orasrv: cannot obtain puname

Cause:Cannot obtain the name of the PU. This may be due to an operating system error.
Check if the PUs are named and consistent.

ORA-09716 kslcll: Unable to fix in-flux lamport latch.

Cause:An Oracle process died while holding a lamport latch.
Exit all Oracle user processes. Shut down and restart the Oracle RDBMS kernel.

ORA-09717 osnsui: maximum number of user interrupt handlers exceeded.

Cause:The internal limit on the number of user interrupt handlers was exceeded.
Reduce the number of simultaneous logons or reduce the number of user interrupt handlers.

ORA-09718 osnsui: cannot set up user interrupt handler.

Cause:The malloc() routine failed to allocate space to hold a user interrupt handler.
This may be due to an memory resource shortage.

ORA-09719 osncui: invalid handle.

Cause:The handle passed to osncui is out of the valid range.
Use a valid handle.

ORA-09740 slsget: cannot get virtual memory region statistics.

Cause:The vm_region system call failed to get virtual memory region statistics.
Check the return code in sercerrno. This may be due to an operating system failure.

ORA-09741 spwat: error waiting for a post.

Cause:A msg_receive system call returned an error.
This is an Oracle internal error. Check the return code in sercerrno. The port name is returned in sercose[0].

ORA-09742 sppst: error during a post.

Cause:A msg_send system call returned an error.
This is an Oracle internal error. Check the return code in sercerrno. The port name is returned in sercose[0].

ORA-09743 smscre: could not attach shared memory.

Cause:A mmap or write system call returned an error.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09744 smsget: mmap returned an error.

Cause:A mmap system call returned an error.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09745 smscre: vm_allocate error, unable to create shared memory.

Cause:There was an error in a vm_allocate system call. Failed to create SGA as a single shared memory segment.
Cause:Check the result code returned in sercerrno. Verify that the SGA attach address is valid.
ORA-09746 smscre: shared memory attach address incorrect.

Cause:The vm_allocate system call attached the SGA at an incorrect location.
Verify that the SGA attach address is valid.

ORA-09747 pw_detachPorts: server call pws_detach failed.

Cause:A pws_detach call to the Oracle helper failed.
Make sure the server is still active. Check the error code returned in sercerrno and look for error messages in the server log file.

ORA-09748 pws_look_up: fork failed

Cause:The pws_look_up call could not fork the Oracle helper process.
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-09749 pws_look_up: port lookup failure

Cause:The pws_look_up could not find a port to the Oracle helper.
Make sure the Oracle helper server has been started correctly by pws_look_up and that the network name server is still running.

ORA-09750 pw_attachPorts: port_rename failed.

Cause:The port_rename system call failed.
This may be an Oracle internal error. Check the return code in sercerrno. Contact Oracle Oracle Worldwide Customer Support Services.

ORA-09751 pw_attachPorts: server call pws_attach failed.

Cause:The pws_attach call to the Oracle helper failed.
Make sure the server is still active. Check the error code returned in sercerrno and look for error messages in the server log file.

ORA-09752 pw_attachPorts: port_allocate failed.

Cause:The port_allocate system call failed.
This may be due to a resource exhaustion. Check the return code in sercerrno. Contact Oracle Worldwide Customer Support Services.

ORA-09753 spwat: invalid process number.

Cause:A function was passed an invalid oracle process ID.
This is an Oracle internal error. Additional information indicates the invalid process ID.

ORA-09754 sppst: invalid process number passed to sppst.

Cause:A function was passed an invalid oracle process ID.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09755 osngpn: port allocation failure.

Cause:The port_allocate system call failed.
This may be due to a system resource shortage. Check the error code in sercerrno.

ORA-09756 osnpns: no port in the name server.

Cause:The osnpns could not find the named port in the name server.
Check the error code in sercerrno. Make sure the shadow process and network name server are running.

ORA-09757 osnipn: port allocation failure.

Cause:A port_allocate system call failed.
This may be due to an system resource shortage. Check the error code in sercerrno.

ORA-09758 osnipn: could not check port in name server.

Cause:The netname_check_in call failed.
Check the error code in sercerrno. Make sure the network name server is running.

ORA-09759 osnsbt: bad message received.

Cause:The msg_receive system call failed or received a bad message.
This is an Oracle internal error. Report the error code returned in sercerrno.

ORA-09760 osnpui: cannot send break message

Cause:The pipe driver could not send a break message to the Oracle shadow process break thread.
Contact Oracle Worldwide Customer Support Services.

ORA-09761 pw_destroyPorts: server call pws_stop_instance failed.

Cause:The pws_stop_instance call to the Oracle helper failed.
Make sure the server is still active. Check the error code returned in sercerrno and look for error messages in the server log file.

ORA-09762 sNeXT_instanceName: translation error.

Cause:A failure was detected while translating the value of ORACLE_SID.
Make sure ORACLE_SID is defined and that it is of legal length.

ORA-09763 osnmpx: send/receive error exchanging Mach ports.

Cause:The Mach driver failed to exchange port information with the other side of the connection. Either msg_send ( with sercose[0] = 1) or msg_receive ( with sercose[0] = 2) failed.
Check the return code in sercerrno. Make sure both sides of the connection are running.

ORA-09764 osnmop: access error on oracle executable

Cause:The Mach driver could not access the oracle executable.
Check the permissions on the oracle executable and each component of the ORACLE_HOME/bin path.

ORA-09765 osnmop: fork failed

Cause:The Mach driver could not fork the oracle shadow process.
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-09766 osnmop: buffer allocation failure.

Cause:The Mach driver failed to allocate enough vm space for its I/O buffers.
Decrease the value of buffer_size parameter in the two-task driver host string.

ORA-09767 osnmfs: bad return code from msg_send.

Cause:The msg_send system call failed while flushing the Mach driver send buffer.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09768 osnmgetmsg: could not read a message

Cause:The msg_receive system call returned a failure code while waiting for a message in the Mach driver.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09769 osnmbr: cannot send break message

Cause:The Mach driver could not send a break message to the Oracle shadow process break thread.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09770 pws_look_up: translation failure.

Cause:The pws_look_up routine failed to translate the name of the Oracle helper executable.
Make sure ORACLE_SID and ORACLE_HOME are set and correctly. Additional information gives the translation error code.

ORA-09771 osnmwrtbrkmsg: bad return code from msg_send.

Cause:The msg_send system call failed while sending a Mach driver break.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09772 osnpmetbrkmsg: message from host had incorrect message type

Cause:The Mach driver received a message having an unrecognizable message type.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09773 osnmgetdatmsg: message from host had incorrect message type

Cause:The Mach driver received a message with an unrecognizable message type.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09774 osnmui: cannot send break message

Cause:The Mach driver could not send a break message to the Oracle shadow process break thread.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09775 osnmrs: reset protocol error

Cause:The Mach two-task driver could not reset the connection.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09776 pws_look_up: access error on (Oracle helper) executable

Cause:The pws_look_up call could not access the Oracle helper executable.
Check the permissions on the Oracle helper executable and each component of the ORACLE_HOME/bin path.

ORA-09777 osnpbr: cannot send break message

Cause:The pipe driver could not send a break message to the Oracle shadow process break thread.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09778 snynfyport: failure allocating the notify port.

Cause:The routine failed to allocate or set the task's notify port.
This may be due to an operating system error. Contact Oracle Worldwide Customer Support Services.

ORA-09779 snyGetPort: failure to allocate a port.

Cause:The port_allocate system call failed. System resources may be exhausted.
This may be due to an operating system error. Contact Oracle Worldwide Customer Support Services.

ORA-09780 sfifi: translation error, unable to expand instance name.

Cause:Unable to expand instance name.
Additional information indicates an sltln error. Check the additional information.

ORA-09781 sfifi: bad instance name stored in control file.

Cause:The header block may have been corrupted.
Contact Oracle Worldwide Customer Support Services.

ORA-09782 sfifi: another instance has the same database mounted.

Cause:In non-shared disk systems, a database cannot be mounted as shared.
Shut down the other Oracle instance and try again. The name of the other instance was dumped to the trace file.

ORA-09783 sfifi: Cannot determine if another instance has mounted the same database.

Cause:Because of permission problems, could not check if another instance was up.
Look up the additional information code in your Commands Reference Manual. Additional information indicates an error closing the file.

ORA-09784 sfifi: lseek error, unable to seek to beginning of file.

Cause:An lseek system call returned an error.
Look up the additional information code in your Commands Reference Manual. Additional information indicates error closing the file.

ORA-09785 sfifi: write error, unable to write header block.

Cause:A write system call returned an error.
Look up the additional information code in your Commands Reference Manual.

ORA-09786 sllfop: open error, unable to open file.

Cause:An open system call returned an error.
Look up the additional information code in your Commands Reference Manual.

ORA-09787 sllfop: unrecognizable processing option, incorrect format.

Cause:The processing option passed is in an incorrect format.
Consult the Installation Guide for your product line to see the permissible formats.

ORA-09788 sllfrb: unable to read file.

Cause:A read system call returned an error.
Look up the additional information code in your Commands Reference Manual. Verify that the file exists.

ORA-09789 sllfsk: unable to read file.

Cause:A read system call returned an error.
Look up the additional information code in your Commands Reference Manual. Verify that the file exists.

ORA-09790 sllfcf: unable to close file.

Cause:A close system call returned an error.
Look up the additional information code in your Commands Reference Manual.

ORA-09791 slembdf: translation error, unable to translate error file name.

Cause:Unable to translate the error filename.
Additional information indicates error returned from sltln. Check the additional information.

ORA-09792 sllfop: cannot allocate read buffer.

Cause:A malloc system call returned an error. The system may have run out of heap space.
Check the additional information for the operating system error.

ORA-09793 szguns: length of user name is greater than buffer.

Cause:The length of the name of the user being looked up is longer than the size of the buffer provided by the calling routine.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09794 szrbuild: length of role name is greater than buffer.

Cause:The length of the name of the role being looked up is longer than the size of the buffer provided by the calling routine.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09795 szrbuild: malloc of role structure failed.

Cause:The allocation of memory for an internal structure that holds a role descriptor failed.
Check the UNIX error number for a operating system failure.

ORA-09796 szrbuild: malloc of role name failed.

Cause:The allocation of memory for an internal buffer that holds the name of a role failed.
Check the UNIX error number for a operating system failure.

ORA-09797 Failed to get O/S MAC privileges.

Cause:The operating system would not allow the retrieval of the privileges of a process.
Check the UNIX error number for an operating system failure. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09798 Label comparison failed.

Cause:The comparison of two binary labels failed.
Check the UNIX error number for a operating system failure. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09799 File label retrieval failed.

Cause:Oracle was unable to attach a label to a file.
Check the UNIX error number for an operating system failure. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09800 Process sensitivity label retrieval failed.

Cause:Oracle was unable to get the sensitivity label for a process.
Check the UNIX error number for a operating system failure. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09801 Unable to get user ID from connection

Cause:Oracle was unable to retrieve the user ID number from the SQL*Net connection.
Check the UNIX error number for an operating system error. Also check the additional information field for the SQL*Net error. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09802 Conversion of binary label to string failed.

Cause:Oracle was unable to convert a binary label to a string.
Check the UNIX error number for a operating system failure. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09803 Allocation of string buffer failed.

Cause:A buffer used to hold a filename for which a label was to be obtained could not be allocated.
Check the UNIX error number for an operating system failure. If there is no error, contact Oracle Worldwide Customer Support Services. The number of bytes that ORACLE attempted to allocate is in the additional information field.

ORA-09804 Class conversion from binary to ORACLE failed.

Cause:Oracle was unable to convert a class component from binary format to Oracle format.
Check the UNIX error number for an operating system failure. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09805 conversion of category number to string failed.

Cause:Oracle was unable to translate a category number to its corresponding string representation. If there is no error, contact Oracle Worldwide Customer Support Services.
Check the UNIX error number for an operating system. The number of bytes that Oracle attempted to allocate is in the additional information field.

ORA-09806 Allocation of label string buffer failed.

Cause:A temporary buffer that is used to hold a label could not be allocated.
Check the UNIX error number for an operating system failure. If there is no error, contact Oracle Worldwide Customer Support Services. The number of bytes that ORACLE attempted to allocate is in the additional information field.

ORA-09807 Conversion of label from string to binary failed.

Cause:Oracle was unable to convert the string representation of a label to binary format.
Re-enter a valid label.

ORA-09808 Could not obtain user clearance.

Cause:Oracle was unable to get a user clearance level.
Check the UNIX error number for an operating system failure. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09809 Unable to get user's group ID from connection

Cause:Oracle was unable to retrieve the user group ID number from the SQL*Net connection.
Check the UNIX error number for an operating system error. Also check the additional information field for the SQL*Net error. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09810 Unable to get process ID from connection

Cause:Oracle was unable to retrieve the user process ID number from the SQL*Net connection.
Check the UNIX error number for an operating system error. Also check the additional information field for the SQL*Net error. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09811 Unable to initialize package.

Cause:Oracle was unable to initialize the library used to obtain security information.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09812 Unable to get user clearance from connection

Cause:Oracle was unable to retrieve the user operating system session clearance from the SQL*Net connection.
Check the UNIX error number for an operating system error. Also check the additional information field for the SQL*Net error. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09813 Unable to get directory status

Cause:Oracle was unable to determine if a directory is multilevel.
Check the UNIX error number for an operating system error. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09814 Unable to expand file name

Cause:Oracle was unable to expand a filename in multilevel directory.
Check the UNIX error number for an operating system error. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09815 File name buffer overflow

Cause:The buffer that holds an expanded name is too small.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09816 Unable to set effective privileges

Cause:Could not set privileges.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09817 Write to audit file failed.

Cause:Oracle was unable to write an entry to the file used as the audit trail.
Check the UNIX error number for an operating system error. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09818 Number is too large

Cause:Oracle was unable to convert a component string to a number because the number is larger than the largest possible value for an integer. The additional information field specifies the maximum.
Correct the string and repeat the conversion.

ORA-09819 Number exceeds maximum legal value

Cause:the number specified for a component was greater than the maximum value allowed.
Change the component to a value less than the maximum and repeat the conversion. The maximum component number value is in the additional information field.

ORA-09820 Conversion of class string to numeric representation failed.

Cause:Oracle was unable to convert a class string to a number because all the characters in the string were not numeric.
Change the string to be either all numbers or all non-numeric characters and repeat the conversion.

ORA-09821 Numeric label is not valid

Cause:A label specified in Oracle numeric format was not valid.
Re-enter with a valid label. See your system encodings for valid numeric component values.

ORA-09822 Translation of audit file name failed.

Cause:Oracle was unable to translate the value of the audit_trail_dest initialization parameter.
Check the UNIX error number for an operating system error. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09823 device name is too long

Cause:The name of a device was too long to fit into an internal buffer.
The additional information field contains the length of the device name. This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09824 Unable to enable allowmacaccess privilege.

Cause:Oracle could not turn on the allowmacaccess privilege so it could compare labels.
Check the UNIX error number. If it indicates that Oracle does not have the allowmacaccess privilege, add the allowmacaccess privilege to the potential privilege set of $ORACLE_HOME/bin/oracle using chpriv (1M). If the executable already has the allowmacaccess privilege, contact Oracle Worldwide Customer Support Services.

ORA-09825 Unable to disable allowmacaccess privilege.

Cause:Oracle could not turn off the allowmacaccess privilege after comparing labels.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09826 SCLIN: cannot initialize atomic latch.

Cause:The atomic_op() system call returned an error.
Check the additional information in the trace file.

ORA-09827 SCLGT: atomic latch return unknown error.

Cause:The atomic_op() system call returned an error.
Check the additional information in the trace file.

ORA-09828 SCLFR: atomic latch return error.

Cause:The atomic_op() system call returned an error.
Check the additional information in the trace file.

ORA-09829 pw_createPorts: server call pws_start_instance failed.

Cause:The pws_start_instance call to the Oracle helper failed. System resources may be exhausted.
Make sure the server is still active. Check the error code returned in sercerrno and look for error messages in the server log file.

ORA-09830 snyAddPort: failed to perform a remote procedure call.

Cause:The msg_rpc system call returned an error.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09831 snyStartThread: failed to build the server port set.

Cause:The routine failed to build a port set on which to listen for requests.
This may be due to an operating system failure. Contact Oracle Worldwide Customer Support Services.

ORA-09832 infoCallback: bad message format.

Cause:The routine received an incorrectly formatted request.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09833 addCallback: bad message format.

Cause:The routine received an incorrectly formatted request.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09834 snyGetPortSet: failed to collect info on a port.

Cause:The port_status system called failed.
This may be due to an operating system error. Contact Oracle Worldwide Customer Support Services.

ORA-09835 addCallback: callback port is already in a set.

Cause:The port to be added to the callback list is already in a port set.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09836 addCallback: could not add a port to the callback set.

Cause:The port_set_add system called failed.
This may be due to an operating system error. Contact Oracle Worldwide Customer Support Services.

ORA-09837 addCallback: could not add allocate a callback link.

Cause:The malloc library call failed to allocate space for a callback link.
This may be due to an operating system error. Contact Oracle Worldwide Customer Support Services.

ORA-09838 removeCallback: failure removing the callback port.

Cause:The port_set_remove port system call failed.
This may be due to an operating system error. Contact Oracle Worldwide Customer Support Services.

ORA-09839 removeCallback: callback port is not in the callback set.

Cause:The port to be removed to the callback list is not in the callback port set.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09840 soacon: Name translation failure.

Cause:The sltln() routine could not translate the ?/dbs/mon2arch_@ named pipe.
Make sure that the ORACLE_HOME specified for this ORACLE_SID in oratab is correct.

ORA-09841 soacon: Name translation failure.

Cause:The sltln() routine could not translate the ?/dbs/arch2mon_@ named pipe.
Make sure that the ORACLE_HOME specified for this ORACLE_SID in oratab is correct.

ORA-09842 soacon: Archmon unable to create named pipe.

Cause:The mknod() routine failed to create the ?/dbs/mon2arch_@ named pipe.
The current operating system login may lack write permission for the ORACLE_HOME/dbs directory. Only user IDs in the dba group of a given instance can run archmon for that ORACLE_SID. Make sure the ORACLE_HOME directory is correct in oratab.

ORA-09843 soacon: Archmon unable to create named pipe.

Cause:The mknod() routine failed to create the ?/dbs/arch2mon_@ named pipe.
The current operating system login may lack write permission for the ORACLE_HOME/dbs directory. Only user IDs in the dba group of a given instance can run archmon for that ORACLE_SID. Make sure the ORACLE_HOME directory is correct in oratab.

ORA-09844 soacon: Archmon unable to open named pipe.

Cause:The open() routine failed to open the ?/dbs/mon2arch_@ named pipe. The maximum number of open files may have been exceeded.
Only the Oracle DBA can run archmon. Make sure the current operating system login has owner or group search permission for the ORACLE_HOME/dbs directory.

ORA-09845 soacon: Archmon unable to open named pipe.

Cause:The open() routine failed to open the ?/dbs/arch2mon_@ named pipe. The maximum number of open files may have been exceeded.
Only the Oracle DBA can run archmon. Make sure the current operating system login has owner or group search permission for the ORACLE_HOME/dbs directory.

ORA-09846 soacon: ARCH unable to open named pipe.

Cause:The open() routine failed to open the ?/dbs/mon2arch_@ named pipe. The maximum number of open files may have been exceeded.
Make sure the operating system user ID of the currently running database has search permission for the ORACLE_HOME/dbs directory.

ORA-09847 soacon: ARCH unable to open named pipe.

Cause:The open() routine failed to open the ?/dbs/arch2mon_@ named pipe. The maximum number of open files may have been exceeded.
Make sure the operating system user ID of the currently running database has search permission for the ORACLE_HOME/dbs directory.

ORA-09848 soawrt: Unable to write to named pipe.

Cause:Failed to write to named pipe.
Contact Oracle Worldwide Customer Support Services.

ORA-09849 soarcv: Unable to read from named pipe.

Cause:Failed to write from named pipe.
Contact Oracle Worldwide Customer Support Services.

ORA-09850 soacon: Archmon unable to lock named pipe.

Cause:The fcntl() routine failed to set write lock on the ?/dbs/arch2mon_@ named pipe.
Make sure that archmon is not already active on another terminal for this ORACLE_SID. Only one archmon session is allowed at a time for a given instance.

ORA-09851 soacon: Archmon unable to lock named pipe.

Cause:The fcntl() routine failed to set a read lock on the ?/dbs/mon2arch_@ named pipe.
Make sure that archmon is not already active on another terminal for this ORACLE_SID. Only one archmon session is allowed at a time for a given instance.

ORA-09852 sfgcwd: failed to get the name of the current directory.

Cause:The request to get the name of the current directory failed.
Contact Oracle Worldwide Customer Support Services.

ORA-09853 snyRemovePort: bad return code from request

Cause:The request to remove a port from the callback set returned a failure code.
This may be due to an operating system error. Contact Oracle Worldwide Customer Support Services.

ORA-09854 snyPortInfo: bad return code from request.

Cause:The request to collect info on a port in the callback set returned a failure code.
This may be due to an operating system error. Contact Oracle Worldwide Customer Support Services.

ORA-09855 removeCallback: bad message format.

Cause:The routine received an incorrectly formatted request.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09856 smpalo: vm_allocate error while allocating pga.

Cause:The vm_allocate system call returned an error.
Check the returned error. The system may be out of system resources.

ORA-09857 smprset: vm_protect error while protecting pga.

Cause:The vm_protect system call returned an error.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09870 spini: failure initializing maximum number of open files.

Cause:An ulimit system call returned an error.
Look up the additional information code in your Commands Reference Manual.

ORA-09871 TASDEF_NAME: translation error while expanding ?/dbs/tasdef@.dbf.

Cause:Failure of sltln(?/tasdef@.dbf) while creating test and set pages.
Check additional return error for more information.

ORA-09872 TASDEF_CREATE: create failure in creating ?/dbs/tasdef@.dbf.

Cause:The create() routine failed when trying to create the tasdef file.
Verify the permissions on the $(ORACLE_HOME)/dbs directory.

ORA-09873 TASDEF_OPEN: open error when opening tasdef@.dbf file.

Cause:Unable to open the tasdef@.dbf file.
Look up the additional information code in your Commands Reference Manual. This may be due to a permission problem. Verify that the tasdef@.dbf file exists.

ORA-09874 TASDEF_READ: read error, unable to read tasdef@.dbf file.

Cause:A read system call returned an error while reading the ?/dbs/tasdef@.dbf file.
Look up the additional information code in your Commands Reference Manual. The sgadef file may be corrupted or incompatible with the Oracle version.

ORA-09875 TASDEF_WRITE: write error when writing ?/dbs/tasdef@.dbf file.

Cause:A write call failed. The device may be out of space.
Look up the additional information code in your Commands Reference Manual.

ORA-09876 TASDEF_CLOSE: unable to close ?/dbs/tasdef@.dbf file.

Cause:A close system call returned an error.
Look up the additional information code in your Commands Reference Manual. This may be due to an operating system failure.

ORA-09877 sstascre: shmget error, unable to get a shared memory segment.

Cause:There is an error in the shmget routine.
Look up the additional information code in your Commands Reference Manual. Verify that enough shared memory is available on the system.

ORA-09878 sstascre/sstasat: shmat error, unable to attach tas write page

Cause:There is an error in the shmat routine.
Look up the additional information code in your Commands Reference Manual. Verify that enough shared memory is available on the system.

ORA-09879 sstascre/sstasat: shmat error, unable to attach tas read page

Cause:There is an error in the shmat routine.
Look up the additional information code in your Commands Reference Manual. Verify that enough shared memory is available on the system.

ORA-09880 sstasfre/sstasdel: shmdt error, unable to detach tas write page

Cause:There is an error in the shmdt routine.
Look up the additional information code in your Commands Reference Manual.

ORA-09881 sstasfre/sstasdel: shmdt error, unable to detach tas read page

Cause:There is an error in the shmdt routine.
Look up the additional information code in your Commands Reference Manual.

ORA-09882 sstasfre/sstasdel: shmctl error, unable to remove tas shm page

Cause:There is an error in the shmctl routine.
Look up the additional information code in your Commands Reference Manual.

ORA-09883 Two Task interface: oratab file does not exist

Cause:The oratab file does not exist.
Install oracle before you use it or recreate the oratab file.

ORA-09884 Two Task interface: SID doesn't match current PU

Cause:You are trying to start oracle on a different PU than the one on which you configured oracle or there is no entry for this SID in the oratab file.
Start oracle with this SID on the PU designated in the oratab file or install the new database with SID.

ORA-09885 osnTXtt: cannot create TXIPC channel

Cause:The txipc driver failed to create pipes for two-task communications with the oracle shadow process. You have probably exceeded the maximum number of open file descriptors per user or the system file table is full.
Note the operating system error code and contact your system administrator.

ORA-09886 osnTXtt: translation error while expanding txipc@.trc.

Cause:Failure of the sltln(txipc@.trc) routine while creating a debug channel.
Check the additional return error for more information.

ORA-09887 osnTXtt: Failed to create/open debug channel.

Cause:Unable to create or open a debug channel.
Contact Oracle Worldwide Customer Support Services.

ORA-09888 osnTXtt: txipc channel creation failed

Cause:The txipc driver failed to create channels for two-task communications with the oracle shadow process. You have probably exceeded the maximum number of open file descriptors per user or the system file table is full.
Note the operating system error code and contact your system administrator.

ORA-09889 osnTXtt: access error on oracle executable

Cause:The txipc driver could not access the oracle executable.
Check the permissions on the oracle executable and each component of the ORACLE_HOME/bin path.

ORA-09890 osnTXtt: malloc failed

Cause:The txipx driver failed to allocate enough heap space for its context area buffers.
Contact Oracle Worldwide Customer Support Services.

ORA-09894 sfwrt: Unable to initialize Async Write.

Cause:The DIO_Ainit routine returned an error.
This may be due to an operating system memory resource shortage.

ORA-09895 sfaswr: seals do not match.

Cause:A function was called with an invalid argument.
This is an Oracle internal error.

ORA-09896 sfaswr: invalid block number.

Cause:A file block number is out of range of file. Additional information returns the block number.
Check the block number.

ORA-09897 sfaswr: write error, unable to write database block.

Cause:The sfaswr routine was unable to write a database block. The error may be due to a problem with Async IO.
Look up the additional information code in your Commands Reference Manual to determine the block number. Check the block number.

ORA-09898 sfalck: setitimer error, unable to set interval timer.

Cause:An error occurred while trying to set an interval timer. This is probably a porting problem.
Look up the additional information code in your Commands Reference Manual.

ORA-09899 sfapol: write error, unable to poll async write.

Cause:The DIO_Apoll routine timed out.
Check the I/O device or turn off async_write.

ORA-09900 sfapol: write error, unable to poll async write.

Cause:The DIO_Apoll routine returned an error. This may be due to an Oracle internal error.
Check the I/O device or turn off async_write. Look up the additional information code in your Commands Reference Manual.

ORA-09901 sfapol: write error, unable to write database block.

Cause:The sfapol routine was unable to write a database block.
Look up the additional information code in your Commands Reference Manual. Additional information returns block number. Check the block number.

ORA-09902 sfapol: write returned incorrect number of bytes.

Cause:This may be due to an truncated write.
Additional information returns the block number and number of bytes written. Check the block number and number of bytes written.

ORA-09903 sfwrt: Internal error.

Cause:Failed to write all the requested blocks.
Check the block number and number of bytes written.

ORA-09904 sfotf: temporary file directory name is too long

Cause:The name of the directory where temporary sort files are to reside is longer than the maximum of120 characters.
Set the temporary_sort_file_dest parameter in the initora file so that is shorter than the maximum length.

ORA-09905 sfotf: mktemp() failed

Cause:The routine used to generate the names of the temporary sort files failed because no more names were available.
This is an Oracle internal error. Contact Oracle Worldwide Customer Services.

ORA-09906 sfotf: open of the temporary sort file failed.

Cause:A file that is to be used as temporary sorting file could not be opened.
Check the error number. The temporary_sort_file_dest parameter in the init.ora file may not point to a directory.

ORA-09907 sfotf: unlink of the temporary sort file failed

Cause:As part of the process of creating a temporary sort file, the file was removed while the process has it open. The file still exists because the process has not closed it. The unlink failed.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09908 slkmnm: gethostname returned error code.

Cause:The gethostname system call returned an error.
This is most likely an Oracle internal error. If the gethostname is successful in other contexts, contact Oracle Worldwide Customer Support Services.

ORA-09909 Malloc of scratch buffer failed.

Cause:Memory needed for a temporary buffer could not be allocated. The additional information field contains the number of bytes that Oracle attempted to allocate.
Check the UNIX error number. It is probable that the system ran out of memory. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09910 Unable to find ORACLE password file entry for user.

Cause:No entry exists for the user in the Oracle password file.
Have the database administrator install a password entry by running orapasswd.

ORA-09911 Incorrect user password.

Cause:The password entered by the user was incorrect.
Enter the correct password.

ORA-09912 Malloc of name buffer(s) failed.

Cause:Oracle was unable to allocate memory for one or both of the buffers that are used to hold the name of DBA and the operator users.
Check the UNIX error number. It is probable that the system ran out of memory. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09913 Malloc of dummy name failed.

Cause:Oracle was unable to allocate memory for the user name to be used in the encryption of the user password.
Check the UNIX error number. It is probable that the system ran out of memory. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09914 Unable to open the ORACLE password file.

Cause:Oracle could not open the password file for reading.
Check the UNIX error number. If the error number indicates that the file does not exist, have the database administrator create the file by running orapasswd. If the error number indicates insufficient permissions, ask the database administrator to change the permissions. Otherwise, contact Oracle Worldwide Customer Support Services.

ORA-09915 Password encryption failed.

Cause:Oracle was unable to encrypt a password.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09916 Required password was not specified.

Cause:A user attempted to use CONNECT INTERNAL, but did not specify a password.
Connect as internal again and specify a password.

ORA-09917 DBA group does not exist in system groups file.

Cause:The group that was selected to hold the names of the dba users does not exist in /etc/groups.
Either add an entry for the group to the file or re-install oracle with the proper group name.

ORA-09918 Unable to get user privileges from SQL*Net

Cause:Oracle was unable to retrieve the user privilege set from the SQL*Net connection.
Check the UNIX error number for an operating system error. Also check the additional information field for the SQL*Net error. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09919 Unable to set label of dedicated server

Cause:Oracle was unable to set the label of the dedicated to server to the required value.
Check the UNIX error number for an operating system error. Also, check the privileges on the oracle executable. It should have at least an allowmacaccess privilege.

ORA-09920 Unable to get sensitivity label from connection

Cause:Oracle was unable to retrieve a user sensitivity label from the SQL*Net connection.
Check the UNIX error number for an operating system error. Also check the additional information field for the SQL*Net error. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09921 Unable to get information label from connection

Cause:Oracle was unable to retrieve a user information label from the SQL*Net connection.
Check the UNIX error number for an operating system error. Also check the additional information field for the SQL*Net error. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09922 Can't spawn process - background log directory not created properly

Cause:Oracle was unable to spawn a background process because the directory that will hold trace files of the background processes was not created properly.
Examine the directory pointed to by the background_dump_dest initialization parameter. Make sure all the following are true: 1. The directory exists. 2. The name points to a directory and is not a file. 3. The directory is accessible and writable to the Oracle user.

ORA-09923 Can't spawn process - user log directory not created properly

Cause:Oracle was unable to spawn a background process because the directory that holds the trace files of the dedicated server processes was not created properly.
Examine the directory pointed to by the user_dump_dest initialization parameter. Make sure all the following are true: 1. The directory exists. 2. The name points to a director, and is not a file. 3. The directory is accessible and writable to the Oracle user.

ORA-09924 Can't spawn process - core dump directory not created properly

Cause:Oracle was unable to spawn a background process because the directory that holds the core dumps produced by Oracle processes in the event of exceptions was not created properly.
Examine the directory pointed to by the core_dump_dest initialization parameter. Make sure all the following are true: 1. The directory exists. 2. The name points to a directory and is not a file. 3. The directory is accessible and writable to the Oracle user.

ORA-09925 Unable to create audit trail file

Cause:Oracle was not able to create the file being used to hold audit trail records.
Check the UNIX error number for an operating system error. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09926 Unable to set effective privilege set of the server

Cause:A dedicated server was unable to set its own privilege set.
Check the privileges granted to the oracle executable. It must have at least an allowmacaccess privilege.

ORA-09927 Unable to set label of server

Cause:Oracle was not able to set the label of a server to a new value.
Check the privileges on $ORACLE_HOME/bin/oracle. Make sure that it has an allowmacaccess privilege.

ORA-09928 Unable to restore the label of server

Cause:Oracle was unable to restore the label of the server to the value that it had before raising it to database high.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09929 GLB of two labels is invalid

Cause:The result of a greatest lower bound operation on two labels was not valid.
Repeat the operation with two different labels. See the system encoding file for the values of valid labels.

ORA-09930 LUB of two labels is invalid

Cause:The result of a least upper bound operation on two labels was not valid.
Repeat the operation with two different labels. See the system encoding file for the values of valid labels.

ORA-09931 Unable to open ORACLE password file for reading

Cause:An attempt to open a password file failed.
Make sure that the permissions on the file have not been changed.

ORA-09932 Close of ORACLE password file failed.

Cause:An attempt to close a password file failed.
Check the UNIX error number for the specific reason.

ORA-09933 Deletion of old password file failed.

Cause:An attempt to remove an old password file failed.
Check the UNIX error number for the specific reason.

ORA-09934 Link of current password file to old failed.

Cause:Oracle was unable to create a link so an old password file could be saved.
Check the UNIX error number for the specific reason.

ORA-09935 Unlink of current password file failed.

Cause:Oracle was unable to save the current password file.
Check the UNIX error number for the specific reason.

ORA-09936 Open of ORACLE password file for write failed.

Cause:Oracle was unable to create a password file.
Check the UNIX error number for the specific reason.

ORA-09937 Chmod of ORACLE password file failed.

Cause:Oracle was unable to change a password file to be read only.
Check the UNIX error number for the specific reason.

ORA-09938 Save of signal handlers failed.

Cause:Oracle was unable to save the previous values of selected signal handlers.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09939 Restoration of signal handlers failed.

Cause:Oracle was unable to restore the previous values of selected signal handlers.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09940 ORACLE password file header is corrupt

Cause:The header of one of the password files was not in the format that Oracle expected.
Check the headers of both files. The header should be in the format FILE VERSION: N.N.N.N.N EXECUTABLE VERSION: N.N.N.N.N where N is a number. Remove the corrupt files and rerun orapasswd.

ORA-09941 Version of orapasswd or installer is older than file.

Cause:The version of orapasswd or Oracle Installer that is being run is older than that of the Oracle password file. Since the file version is only changed when the format is changed, this error means that the executable is using a different format than that with which the file was created.
Run a version of orapasswd or Oracle Installer whose version is the same or later than that of the file.

ORA-09942 Write of ORACLE password file header failed.

Cause:The attempt to write out the header of the Oracle password file failed.
Check the operating system error number. The file system may be full.

ORA-09943 Allocation of memory for password list component failed.

Cause:When it is building a list of password file entries, Oracle allocates memory for various components. One of the allocations failed.
Check the operating system error number. The system probably run out of memory.

ORA-09944 Password entry is corrupt.

Cause:An entry in an Oracle password file was not in the expected format.
Remove the corrupt files and rerun orapasswd.

ORA-09945 Unable to initialize the audit trail file

Cause:Oracle was unable to write header information to the file being used as the audit trail.
Check the UNIX error number for an operating system error. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09946 File name too long for buffer

Cause:The buffer that was to be used to hold a filename was too short for the generated name. This happens if the translated name for a trace file or an audit file is longer than the maximum allowed, which on many ports is 256 characters.
Use a shorter file name.

ORA-09947 Unable to allocate connection attributes structure

Cause:Oracle was not able to allocate the memory needed to hold the attributes of the SQL*Net connection. The additional information field holds the number of bytes that Oracle attempted to allocate.
Check the UNIX error number. The system probably ran out of memory. If the system did not run out of memory, contact Oracle Worldwide Customer Support Services.

ORA-09948 Process information label retrieval failed.

Cause:Oracle was unable to get the information label for a process.
Check the UNIX error number for an operating system failure. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09949 Unable to get client operating system privileges

Cause:Oracle was unable to get the operating system privileges for the client process.
Check the UNIX error number for an operating system failure. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09950 Unable to get server operating system privileges

Cause:Oracle was unable to get its privileges from the operating system.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09951 Unable to create file

Cause:Oracle was unable to create a file.
Check the UNIX error number for an operating system failure. If there is no error, contact Oracle Worldwide Customer Support Services.

ORA-09952 scgcmn: lk_open_convert unexpected return: open failed

Cause:The distributed lock manager returned an unexpected value.
Check for a system error message and refer to the distributed lock manager documentation or contact Oracle Worldwide Customer Support Services.

ORA-09953 scggc: unexpected return of a lock convert

Cause:The distributed lock manager returned an unexpected value.
Check for a lock manager error message and refer to the distributed lock manager documentation or contact Oracle Worldwide Customer Support Services.

ORA-09954 scgcc: unexpected return status to callback of lock close

Cause:The distributed lock manager returned an unexpected value.
Check for lock manager error message and refer to the distributed lock manager documentation or contact Oracle Worldwide Customer Support Services.

ORA-09955 scgcan: unexpected return status when canceling a lock

Cause:The distributed lock manager returned an unexpected value.
Check for system error message and see the distributed lock manager documentation or contact Oracle Worldwide Customer Support Services.

ORA-09956 scgcm: unexpected lock status condition

Cause:A global locking system service returned an unexpected value.
Check for system error message and see the distributed lock manager documentation or contact Oracle Worldwide Customer Support Services.

ORA-09957 Unable to send termination request to IMON

Cause:The attempt to send a termination signal to IMON failed.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09958 IMON: two processes with the same ORACLE pid are active

Cause:The IMON process was unable to add an entry for a server process because another active process occupies the slot.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09959 IMON: deletion of a process failed.

Cause:The IMON process was unable to delete a server process from its process ID array because no entry for the process could be found.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09960 Unable to establish signal handler for termination signal

Cause:Oracle was unable to set up a handler for the signal used to notify it that the instance was shutting down.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09961 Unable to restore termination signal handler

Cause:Oracle failed to set the handler for the termination signal to its previous value.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09962 lk_group_create error in scggrc

Cause:The scggrc routine received an error.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09963 lk_group_attach error in scggra

Cause:The scggra routine received an error.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09964 lk_group_detach error in scggrd

Cause:The scggrd routine received an error.
This is an Oracle internal error. Contact Oracle Worldwide Customer Support Services.

ORA-09965 sfsfs: invalid file size.

Cause:An invalid file size was specified. A valid, non-zero logical block size must be specified. The logical block size must be a multiple of the physical block size and less than the maximum block size.
Specify a valid file size.

ORA-09966 sfsfs: unable to open file in read/write mode

Cause:A datafile resize operation failed because the operating system was unable to open the file in read/write mode.
Correct the operating system error and retry the resize operation.

ORA-09967 sfsfs: unable to resize a file larger

Cause:A datafile resize operation failed because the operating system was unable to make the file larger.
Correct the operating system error and retry the resize operation.

ORA-09968 sfsfs: unable to seek to beginning of file

Cause:A datafile resize operation failed because the operating system was unable to seek to the beginning of the file the resize operation.
ORA-09969 sfsfs, sfrfs: malloc error, unable to allocate buffer.

Cause:A datafile resize operation failed because the malloc library routine returned an error.
This may be due to a memory resource shortage.

ORA-09970 sfsfs: read error, unable to read header block.

Cause:A datafile resize operation failed because the operating system was unable to read the datafile header.
Correct the operating system error and retry the resize operation.

ORA-09971 sfsfs: write error, unable to write header block.

Cause:A datafile resize operation failed because the operating system was unable to write the datafile header.
Correct the operating system error and retry the resize operation.

ORA-09972 sfsfs: unable to resize a file smaller

Cause:A datafile resize operation failed because the operating system was unable to make the file smaller.
Correct the operating system error and retry the resize operation.

ORA-09973 sfsfs: close error.

Cause:A datafile resize operation failed because the operating system was unable to close the file.
Correct the operating system error and retry the resize operation.

ORA-09974 skxfidini: Error Initializing SDI Channel

Cause:The process was unable to initialize the SDI channel properly.
Correct the operating system error and retry the operation.

ORA-09975 kxfspini: Error Initializing SDI Process

Cause:The process was unable to attach to the SDI channel.
Verify that the SDI process limits are correctly configured. Correct the operating system error and retry the operation.

ORA-09976 skxfqdini: Error Creating Port

Cause:The process was unable to create a communications endpoint.
Verify that the SDI port limits are correctly configured. Correct the operating system error and retry the operation.

ORA-09977 skxfqhini: Error Connecting

Cause:The process was unable to connect to another endpoint.
Verify that the SDI limits are correctly configured. Check that other nodes are part of the cluster and are operating properly. Correct the operating system error and retry the operation.

ORA-09978 skxfqhdel: Error Disconnecting from another endpoint.

Cause:The process was unable to disconnect cleanly from another endpoint.
Check that other nodes are part of the cluster and are operating properly. Check the instance and processes on the other nodes. Correct the operating system error and retry the operation.

ORA-09979 skxfqhsnd: Error Sending a message to another endpoint

Cause:The process was unable to send a message to an existing endpoint.
Check that the other nodes are part of the cluster and are operating properly. Check the instance and processes on the other nodes. Correct the operating system error and retry the operation.

ORA-09980 skxfqdrcv: Error Receiving a message from another endpoint

Cause:The process encountered an error while trying to receive a message.
Check that the other nodes are part of the cluster and are operating properly. Check the instance and processes on the other nodes. Correct the operating system error and retry the operation.

ORA-09981 skxfqdreg: Error Adding a page to the SDI buffer pool

Cause:The process was unable to add a page to the SDI buffer pool.
Correct the operating system error and retry the operation.

ORA-09982 skxfqddrg: Error Removing a page from the SDI buffer pool

Cause:The process was unable to remove a page to the SDI buffer pool.
Correct the operating system error and retry the operation.

ORA-09983 skxfidsht: Error shutting down SDI channel

Cause:The process was unable shut down the SDI channel.
Check the SDI persistent resources using SDI tools. Verify that all processes exited cleanly and the instance is safely shut down. Delete any remaining SDI channel IDs associated with the current instance.

ORA-09984 SGA file $ORACLE_HOME/dbs/sgadef$ORACLE_SID.dbf does not exist

Cause:The file does not exist or is not accessible.
Restart the instance to create the SGA definition file.

ORA-09985 SGA definition file could not be read

Cause:A UNIX read() operation failed.
Look up the additional information code in your Commands Reference Manual.

ORA-09986 wrong number of bytes read from SGA definition file

Cause:The skgmsdef structure size differs from the number of bytes read from the SGA file.
Compare the two structure definitions and ensure that they are the same size and structure.

ORA-09987 unable to attach to SGA in READ-ONLY mode

Cause:The instance is not up or cannot read SGA segments.
Verify that the instance is up and read permissions for the SGA segments are set.

ORA-09988 error while detaching SGA

Cause:The skgmsdef structure is corrupted or segment addresses are modified.
Safely shut down the instance and remount the SGA segments.

ORA-09989 attempt to use invalid skgmsdef struct pointer

Cause:The pointer to a skgmsdef structure was used without validating it
Assign a valid address to the skgmsdef structure pointer before using it.


Contents Index Home Previous Next