A19483 2

Podstrony

[ Pobierz całość w formacie PDF ]
.= num_of_locks[EACH]}[:].where filenum is a file number, as listed in V$DBFILE, and num_of_locks is thenumber of PCM locks.ORA 01604 illegal file number range in clause str of GC_FILES_TO_LOCKSCause The range of file numbers specified in a clause of the initialization parameterGC_FILES_TO_LOCKS is invalid.The first file number must be smaller thanthe second file number, and a hyphen must separate the numbers.All numbersin the range must be valid file numbers.Action Correct the value of the GC_FILES_TO_LOCKS parameter before starting theinstance.If other instances are currently accessing the database, use the valuethat they are using.2 146 Oracle7 Server Messages01500 01699: Oracle CommandsORA 01605 missing file numbers in clause str of GC_FILES_TO_LOCKSCause The initialization parameter GC_FILES_TO_LOCKS is specified incorrectly.Each clause should have one or more file numbers or ranges of file numbers, aslisten in V$DBFILE, separated by commas.Use the following syntax:GC_FILES_TO_LOCKS = {filenum[ filenum][,filenum[ filenum]].= num_of_locks[EACH]}[:].Spaces are not allowed within the double quotation marks.Action Correct the value of the GC_FILES_TO_LOCKS parameter before starting theinstance.If other instances are currently accessing the database, use the valuethat they are using.ORA 01606 GC_FILES_TO_LOCKS not identical to that of another mounted instanceCause The initialization parameter GC_FILES_TO_LOCKS is not the same as anotherinstance mounted in parallel mode.This parameter must be the same as thatfor all shared instances.Action Modify the parameter to be compatible with the other instances, then shutdown and restart the instance.ORA 01607 GC_LCK_PROCS num is not the same as other instances numCause The initialization parameter GC_LCK_PROCS is not the same in other instancesthat have the database open.Action Modify the parameter to be compatible with the other instances, then shutdown and restart the instance.ORA 01608 cannot bring rollback segment name online, its status is statusCause The rollback segment may have been brought online previously by the databaseadministrator or could have been left online after a process crashed.The abovestatus can be one of the following: INVALID, IN USE, AVAILABLE, OFFLINE,NEEDS RECOVERY.Action Check the status of the rollback segment in the view DBA_ROLLBACK_SEGS.Take the segment offline, if necessary.ORA 01609 log name is the current log for thread num cannot drop membersCause A member of the current redo log for the given thread cannot be dropped.Action If the thread is opened, request a log switch by the instance that is using thethread.If the thread is not open, disable the thread manually, archive the log orclear it.Oracle7 Server Messages 2 14701500 01699: Oracle CommandsORA 01610 recovery using the BACKUP CONTROLFILE option must be doneCause Either an earlier database recovery session specified BACKUP CONTROLFILEor the control file was recreated with the RESETLOGS option.Only BACKUPCONTROLFILE recovery is allowed, and it must be followed by resetting theonline redo log files when the database is next opened.Action Perform recovery using the BACKUP CONTROLFILE option.ORA 01611 thread number num is invalid must be between 1 and numCause A thread number in a command is greater than the number of threadssupported by the control file.Action Use a thread number that is valid.ORA 01612 thread num is already enabledCause An attempt was made to enable a thread that is already enabled.Action No action is required or enable another thread, if desired.ORA 01613 thread num only has num logs at least 2 logs required to enableCause The thread cannot be enabled because it has less than two online redo log filesassociated with it.Action Add logs to the thread or pick another thread to enable.ORA 01614 thread num is busy cannot enableCause The mount enqueue for the thread could not be acquired when attempting toenable the thread.This probably means that another process has already startedenabling this thread.Action Wait and try again or find another thread to enable.ORA 01615 thread num is mounted cannot disableCause Some instance, possibly this one, has allocated the thread for use.The threadmay not be disabled while in use.Action To disable this thread, cleanly shut down the instance using it.2 148 Oracle7 Server Messages01500 01699: Oracle CommandsORA 01616 thread num is open cannot disableCause The thread is not closed.The last instance to use the thread crashed and left thethread open.A thread cannot be disabled until it is closed.The thread is stillneeded for crash or instance recovery.Action If the database is open, instance recovery should close the thread soon.Wait afew minutes until instance recovery frees the thread.Otherwise, open thedatabase.Crash recovery will close the thread.ORA 01617 cannot mount: num is not a valid thread numberCause The initialization parameter THREAD is not between 1 and the maximumnumber of threads allowed when the database was created.Action Shut down the instance, change the initialization parameter to a valid value,then restart the instance.ORA 01618 thread num is not enabled cannot mountCause The initialization parameter THREAD requests a thread that is not enabled.Athread must be enabled before it can be mounted.Action Shut down the instance, change the initialization parameter to an enabledthread number, then restart the instance.If the database is open in anotherinstance, then the thread may be enabled.ORA 01619 thread num is mounted by another instanceCause The initialization parameter THREAD requests a thread that has been mountedby another instance.Only one instance may use each thread.Action Shut down the instance, change the initialization parameter to an unusedthread, then restart the instance.ORA 01620 no public threads are available for mountingCause The initialization parameter THREAD is zero, its default value.There are noavailable threads that have been publicly enabled.Action Shut down the instance, change the initialization parameter to a thread that isprivately enabled and not mounted, then restart the instance.If the database isopen in another instance, then a thread may be publicly enabled.Oracle7 Server Messages 2 14901500 01699: Oracle CommandsORA 01621 cannot rename member of current log if database is openCause This is a rename command for a member of the current log for an open thread.If the database is open anywhere, the log may be in use, so the rename cannotbe done.Action Wait until the log is not current or mount the database exclusively.ORA 01622 thread number must be specified default not specificCause The thread was not specified when adding a log, and the currently mountedthread was chosen by default.Because the current thread was not specifiedexplicitly, the user cannot know to which thread the log will be added.Action Explicitly specify the thread number either in the initialization parameterTHREAD or in the ADD LOGFILE command.ORA 01623 log num is current log for thread num cannot dropCause A thread s current log cannot be dropped, even if the thread is closed [ Pobierz całość w formacie PDF ]

zanotowane.pl

doc.pisz.pl

pdf.pisz.pl

bezglutenowo.pev.pl