" `  !)1lͼ"O}device full encountered during write to a fileillegal identifier length, argn:%s, len:%s, lim:%sattempting to create a file that already existsattempting to open a file that does not existopening of a symbolic link is disallowedinvalid input for the full path specificationinvalid lock parameters for get file lock [%s]error encountered when attempting to tell the file positionrequested file lock is busy, [%s] [%s] Duɼ . Y file descriptor has already been opened [%s] [%s]invalid file descriptor state for operation, %s, %s, %suninitialized file descriptordirectory already exists [%s]uninitialized file handleinvalid directory name input for client addressinvalid input to ADR initialization routinethe specified ADR Base directory does not exist [%s]error creating directory during ADR initialization [%s]invalid permissions input for change permissions8]Euerror changing permissions for a fileerror encounted while performing standard file I/Oinvalid seek location, [%s], [%s]missing read, write, or exec permission on directory during ADR initialization [%s] [%s]invalid home location specification for ADR, [%s], [%s], [%s]error encountered when attempting to move a fileerror encountered when attempting to copy a fileerror encountered with set current working directory Jxü<\ !error getting operating system time for a filelock table is fullerror encountered when getting ADR base directory defaultreached end of file for alert logerror encountered when read alert log [%s]Alert log purge has occurred - retry operationnull input to ADR initializationinvalid input for ADR base directoryinvalid input for ADR product typeinvalid input for ADR product idinvalid input for ADR instance id"8#o$%ܼ&-'t()string buffer too small to hold input, [%s], [%s], [%s]error concatenating directory onto path, [%s], [%s], [%s]error concatenating file onto path, [%s], [%s], [%s]user missing read, write, or exec permission on specified ADR Base directory [%s]error with opening ADR block file because file does not exist [%s] [%s]invalid argument for checking ADR initializationthe ADR sub-system is not initializedincorrect arguments to ADR deferred initialization*8+\,-./0K1unable to lock file - already in useunable to get share lock - file not readableunable to find a valid ADR baseerror checking directory existence during ADR initialization [%s]error encountered with get current working directorythe path name must not contain the string '..'.error translating a path name into its full path namefile name with full path information [%s] not allowed 2J345Լ67 8'9B:b;<error encountered while reading an ADR block file during ADR initialization [%s]OS file synchronization failureOS open system call failureOS write system call failureOS read system call failureOS close system call failureOS seek system call failureOS file size system call failureOS check file exists system call failurespecified directory does not existuser missing read, write, or exec permission on specified directory =J>o?@üABC.DUEFGOS command to create directory failedOS unlink system call failureuser missing read or write permission on specified fileOS command to move a file failedOS command to open a directory failedOS command to close a directory failedOS command to remove a directory failedOS command to release advisory lock failedOS command to get the file status failedOS command to change the file permissions failedOS command to copy a file failed HVIqJKLμMNO@PWQqRSTIllegal Input Argument [%s]Field Length Exceeds Maximum [%s] [%s] [%s]Illegal Identifier [%s] [%s]Illegal Data Type [%s]Illegal Identifier Length [%s] [%s] [%s]Record Length too Big [%s] [%s] [%s]Ilegal Number of Fields [%s] [%s] [%s]Illegal Field Name [%s]Duplicate Field Names [%s]Relation Already ExistsRelation Not FoundIllegal Access Mode [%s] [%s]Open Record Access Not Done UJVwWXYZ[#\J]i^_Incorrect Access Mode for Operation [%s] [%s]Sequence Overflow [%s] [%s] [%s]Sequence Invalid Operation [%s] [%s]Field Len Exceeds Max Field Length [%s] [%s] [%s] [%s]Out of Space on DeviceDuplicate Key Name [%s] [%s]Key Name Doesn't Match Any Existing KeyToo Many Keys Defined [%s] [%s]Key Exceeds Maximum Allowed Length [%s] [%s] [%s]Predicates/Order By Not AllowedInterrupt Requested - Fetch Aborted - Return Code [%s] [%s] `Pabcdef&gKhaijkDDL has occurred since parse - reparse [%s] [%s] [%s]No More Space in Order By BufferNo Fetch in ProgressInvalid Relation File - [%s] [%s] [%s] [%s]Missing Define Call [%s]Invalid Relation Handle Provided [%s] [%s]Expression arguments must match typesPredicate syntax errorDebug command syntax error [%s]Invalid Field Handle [%s] [%s] [%s]Create Field of Field Name [%s] FailedOperation [%s] on Relation [%s] Failed l>monoʼpqrQstOperation [%s] on Relation [%s] Field [%s] FailedOperation [%s] on Relation [%s] Key [%s] FailedInvalid Surrogate Length Specified [%s] [%s]Invalid Predicate Handle Provided [%s] [%s]Field is NOT NULL but NULL value suppliedFile is at wrong version [file = %s] [current = %s]Fields that are NOT NULL can not use surrogatesAdditional Fields must be declared nulls allowedPurge for Retention can't be called while in an Query uDvhwxyz{'|U}x~Attempt to Update/Delete when at EOFIllegal Operation on External RelationPredicate Conversion Error %sFunction %s type check error; ityp = %s typ = %s arg = %sType mismatch - lhs = %s, rhs = %s, result = %s, op = %sDetails: %sFailed to open relation due to following errorRelation does not require migrationRelation Being Migrated - Can't be openedMigration Error [%s] [%s] [%s] [%s] [%s] [%s] Dwü켄#VChanges not supported on relations opened read-onlyHaving by not allowedGrouping function (%s) used - but no group by specifiedAMS Corrupt Page Found - Rebuild RelationAMS Relation not Created CorrectlyFunction %s not foundGrouping Function %s not allowed in a having clauseSequence references not allowed in predicatesCurrval not set yet - use nextvalInternal Application Function Failure Jȼ,JnIncorrect number of arguments (%s) provided - expected (%s)Xaction Control General FaultField name %s can't be unique resolvedCan't use outer join syntax mixed with inner join syntaxOuter join syntax not allowed without a joinIncident Record Already ExistsAn Invalid Incident ID was specifiedIncident Directory does not existExceeded max Incident Sequence Valueincident staging file not foundincident ID range is too large Jxɼ༹;]lIllegal input parameter: [prm = %s] [pos = %s]illegal incident state transition, [%s] to [%s]Incident %s staging file not foundInvalid field name [%s]Sweep incident %s staging file failedUpdates not allowed on ADR relation [%s] of Version=%sInvalid ADR Control parameter [%s]ADR unavailablerelation [%s] unavailable or cannot be createdADR Relation [%s] of version=%s is obsoleteADR Relation [%s] of version=%s cannot be supported J{ EqUpdate operation on ADR relation [%s] not allowedToo many incidents to reportADR Relation [%s] not foundRelation [%s] of ADR V[%s] incompatible with V[%s] toolSpecified pathname [%s] must be inside current ADR homeIncompatible staging file encounteredStaging File Validation Error [%s] line [%s]Illegal Staging File Type %sIllegal Staging Status Type %sView already exists - use replace optionCreate View Fails with the following errors JhƼ Q|Expected Clause (%s) not foundViews only allowed %s relations to be specifiedinvalid relation-field name [%s] in select listselect field name [%s] not foundambiguous select field name [%s] foundillegal function reference to more than one field [%s], relation [%s]missing Alias name for function column [%s]Invalid function argumentview [%s] does not existoperation not supported on view [%s]Field [%s] not a grouping field Py : a   Field [%s] cannot be mixed with %s fieldsinvalid field [%s] reference in %s clauseInvalid Name [%s] specifiedTimeout encountered during operationToo many fieldsField %s not found in objectField (%s) conversion error - type %s value %sField (%s) exceeds maximum length of %sField (%s) is declared as NOT NULLIncident Range Function Only Available on DualInvalid range supplied - valid range is [%s.%s]Range must be a numeric constant D_}3sADRCI initialization failedSET command requires argumentsVariable is not definedDEFINE or UNDEFINE command has no argumentsRUN or @ command has no argumentsThe option in the command is invalidECHO or TERMOUT status must be set to ON or OFFDESCRIBE and QUERY commands need at least relation name argumentThe incident number exceeds the maximum number [%s]The ADR homes exceeds the maximum number [%s] DrϽE u!"Ľ#The trace path exceeds the maximum number [%s]The trace files exceeds the maximum number [%s]The parameters exceeds the maximum number [%s]The number of orderby fields exceeds maximum number [%s]The string in the execution option exceeds maximum length [%s]Syntax error found in string [%s] at column [%s]Variable value [%s] must be single or doulbe quotedSHOW command needs argumentsThe variable [%s] is not definedIllegal arguments $J%r&'ѽ()*9+`,o-.EXPORT command must have a relation namePredicate string in the command must be single or double quotedInvalid relation field type [%s]IMPORT command must have a filenameSHOW TRACE command needs argumentADRCI environment is not initializedThe initialization filename is too longUnknown commandInput command string exceeds max length [%s]Variable name [%s] is an invalid identifierCannot read the parameter /P0w123Ž4׽567"8U9u:Must specify at least one ADR home pathThe ADR home path [%s] is not validUnknown help topicNo DDE commands are inputInput a trace fileFile [%s] does not existNo IPS commands are input[%s] is not a valid numberThe input path name exceeds the maximum length [%s]Variable [%s] is already definedThe function parameter number exceeds the maximum number [%s]The control parameter number exceeds the maximum number [%s] ;D<w=>?@5AeBCDTrace Record type appears in the middle of the pathThe single "." and "*" cannot appear in the middle of the pathPath expression only supports one bucket dump typeThe command needs path inputThe input path [%s] does not contain any ADR homesThis command does not support multiple ADR homesTail alert can only apply to single ADR homeSyntax: adrci [-help] [-script script_filename] Options Description (Default) E8FzGHI:JKK}L----------------------------------------------------------------- script script file name (None) help help on the command options (None) ----------------------------------------------------------------- ADRCI core dumped"show incident" failed due to the following errors"describe" command only supports one ADR home pathThe home path [%s] is not valid MJNwOPƽQRSUTUVW"describe" failed due to the following errorsFatal error encountered in [%s]The value buffer reached the maximum length [%s]The predicate buffer reached the maximum length [%s]The specified type [%s] is undefinedInternal failure, the report context is not initialized"%s" for the keyword "%s" is not a valid number"%s" is not a valid keywordKeyword "%s" cannot be duplicatedUnknown "%s" command"%s" is not a valid shell command XDYXZ[\н]Y^_`aInvalid product nameInternal failure, unknown return code [%s]Syntax error specifying product, must not be NULL[%s] is not a valid timestampCannot write the results out to a file, please check if the environment variable TMPDIR is set or the current directory is not writableThe input path does not contain any valid ADR homesNo alert messages are createdNo HM runs are createdNo incidents are createdReport is not availableb8cOdefgDhiReport is not generatedSpooling failed, it may be because the spool file cannot be created due to a permission issueRun script failed, it may be because the script file does not existThe file exceeds the maximum length [%s]The file [%s] exceeds the maximum length [%s]The internal predicate string exceeds the maximum length [%s]The predicate string exceeds the maximum length [%s]The input exceeds the maximum length [%s] jDktlmٽno6pIqtstThe field number exceeds the maximum number [%s]The program name is too long, exceeds the maximum length [%s]The report component name is not definedSweep command needs parametersADR home is not set, the corresponding operation cannot be doneInterrupt requested"%s" is a mandatory keyword for the command"%s" is an invalid product typeThe value of the keyword "%s" exceeds the maximum length %sFile Write Error [%s] [%s] uDv]wxy̽z{(|K}~File Read Error [%s] [%s]Invalid Command Line - Missing Required ElementsInvalid Parameter SpecifiedRelation Parameter Must be SpecifiedFile Parameter Must be SpecifiedExisting Relation at different version than export [%s] [%s]Predicate Not Allowed during ImportExport File Version [%s] Can Not be Used by Import [%s]Error occurred during operation. See the following errorsCan not export an in memory relation JqȽ<bRepair Schema currently not implementedHM run with name [%s] already existsHM run id[%s] not foundHM finding id [%s] not foundHM recommendation id [%s] not foundAlloc Function Pointer should not be NULL Argument [%s] value should not be NULLArgument [%s] value should not be ZERONot valid(supported) parameter typeInfo list object doesn't have spaceParam [%s] was not found in the infolist object Dkν"DZ<=Format of info list text is not correctMessage object doesn't have space for new messageInfo list object doesn't have space for new paramsFinding set object doesn't have space for new findingHM run with name [%s] not foundParameter [%s] value not specifiedParameter [%s] is NULLParameter [%s] value [%s] length exceeds the maximum limit [%s]DBG initialization out of sequenceDBG initialization : bad Library Group ID >Dn~op̾qrsAthuvDBG initialization : no callbacks specified to disable ADRDBG context management internal failureDBG context management internal failureDBG context management internal failureDBG context management internal failureDBG context management internal failureDBG context management internal failureDBG context management internal failureDBG context management internal failureDBG context management internal failure wDxkyz{꾠VsDBG context management internal failureDBG context management internal failureDBG context management internal failureDBG context notification service internal failureDBG memory corruption for thread local root"%s" for the keyword "%s" is not in the right format of timestampThe option "%s" is duplicatedThe options "%s" and "%s" are mutual exclusiveThe keyword "%s" is not defined for this commandThe command needs at least one file input Vɿ 6 _ z  ˿BEGIN BACKUP issued already - must do an END BACKUP firstUnknown Function Reference (%s)Illegal Input Argument [%s]Empty component specificationString [%s] is not a valid library nameString [%s] is not a valid component nameString [%s] is not a valid operation nameParser context is not validThe end of file is reachedNo trace files are foundScan context is not initializedFetch already startedThe parent node does not exist Dl̿*UkThe specified trace filename is too longWriting into trace file failed, file size limit [%s] reachedFile position is not in right formatThe output format is not supportedCannot open the output file with path [%s] and filename [%s]Fail to seek to the requested file positionInterruption is caughtEnd of Fetch is reached in the trace navigatorThe merge context is not initializedThe begin timestamp cannot be larger than the end timestamp JtԿ !""c#$The input homepath is not a valid ADR homeThere is no file to be mergedThe merge is doneThe incident does not existThe offset is not validThe requested line number does not existThe predicate exceeds the max limit %sThe trace record size exceeded the max size that can be read [%s]Cannot allocate memory for processing tracesThe metadata header of file [%s] is not validThe data offset is not in non-decreasing order at byte [%s] %D&f'(ٿ) *9+pFail to switch to ADR default homeinvalid input for the file name identifierbucket snapshotting error: [%s], [%s], [%s], [%s], [%s], [%s], [%s], [%s]The number of relations exceeds maximum number [%s]Feature (%s) currently not allowed for SELECTView select column count differs from select alias listSelect * not allowed in a CREATE VIEWFailed to process event statement [%s] Failed to parse action [%s]Action definition for [%s] not found Do޿4nMissing Mandatory argument [%s] for %s [%s][%s] is not a valid argument for %s [%s]Too many arguments specified for %s [%s]Parameter value [%s] is invalidPassed end of string while parsingEvent Name [%s] not foundLibrary Name [%s] not foundParameter value [%s] length is longer than maximum allowedParsing failed because memory allocation failedParameter value [%s] is not one of allowed values Dɿ"EScope event limit exceeded, scoped events may work incorrrectlyTarget not specified for scope [%s]Target not specified for event [%s]SQL ID string [%s] is invalidParameter NULL for this call [%s]Event group not initialisedEvent parse context not initializedEvent group sync failed, parent[%s] is not parent of child[%s]Failed to initialize parse context in [%s]Failed to initialize event group in [%s] Jq  ) B x Failed to destroy parse context in [%s]Syncing failed, parent and child are same groupEmpty Filter SpecificationToo many filters specifiedScope or Filter cannot be specified for mapped event, use [%s]Usage for event %s : %s[%s] is not a valid scopeEvent string must begin with a valid event name/numberEvent number is invalidToo many arguments for event %sKeyword IMMEDIATE must be at the beginning of event string Ju0123#4E5h6Invalid value of parameter [%s] for %s [%s]Missing value for name-value pairEvent [%s] is not a valid filterDDE Internal ErrorArguments not valid for DDE invocationDDE global context not initialized for DDE invocationToo many recursive DDE invocationsRecursive DDE invocation at Phase IDDE async action error [%s] [%s] [%s] [%s] [%s] [%s] [%s] [%s]No DDE async actions in queueDDE User Actions Internal Error >YB}Illegal input argument [%s]Invalid action/invocation specified [%s] [%s] [%s]Invalid action specified (action not defined) [%s]Invalid action/invocation/parameter specified [%s] [%s] [%s] [%s]Invalid parameter specified (action parameter not defined) [%s] [%s]Invalid parameter length specified, argn:%s, len:%s, lim:%sInvalid length in user credentials, argn:%s, len:%s, lim:%sUnable to read ADR record [%s]Action failed [%s] [%s] [%s] Du[Invalid command string length [%s] [%s] [%s] [%s]Command processor not found (system call returned null value) [%s] [%s]No incident provided and no default incident setSpecified parameter cannot be modified [%s] [%s]Specified action is in status INCOMPLETE and cannot be executedInvalid incident type specified [%s]IPS Internal ErrorIllegal input argument [%s]Invalid length specified [%s] [%s] [%s]No such package [%s] Dh?nCannot change package name [%s] [%s]Undefined configuration parameter specified [%s]No unpacking history in this homeInvalid home specified [%s]Incremental package provided when complete expectedNot an IPS packageIncompatible package version [%s] [%s]Package ID does not match existing ID [%s] [%s]Package name does not match existing name [%s] [%s]Package sequence later than expected [%s] [%s] Jz &Bc~Package sequence earlier than expected [%s] [%s]Earlier package sequence applied with FORCE option [%s] [%s]Cannot modify already generated packagePackage too large [%s] [%s]Maximum number of package files generated [%s]File outside ADR not allowedDirectory outside ADR not allowedFile inside ADR not allowedDirectory inside ADR not allowedNo such file or file not accessible [%s]No such directory or directory not accessible [%s] J1 K!*File already exists and OVERWRITE option not specified [%s]No such problem [%s]No such incident [%s]Problem not part of package [%s]Incident not part of package [%s]Invalid date formatFlood-controlled incident not allowed here [%s]Date conversion error [%s]Warnings while unpacking package, details in file %sWarnings while finalizing package, details in file %sNon-zero return code from archiving utility [%s] [%s] +J,p-./0HGIlJKRArchive file structure error [%s] [%s]Archiving utility out of memory [%s] [%s]Invalid command invoking archiving utility [%s] [%s]Archive is missing or empty [%s] [%s]Archive I/O failed [%s] [%s]Operation failed due to insufficient disk space [%s] [%s]Starting to finalize package contentsFinished finalizing package contentsStarting package generationFinished package generationGetting additional informationS\TsUV\]^_ `$aRbjGetting CRS informationGetting OCM informationGetting RDA informationGetting OSS informationInvalid Transient LifeTime[%s]Invalid Critical Factor[%s]Invalid Warning Factor[%s]Invalid Weight Factor[%s]Incident meter configuration record not found Problem record not foundIncident record not found,syntax error: found "%s": expecting one of: "%s" etc..attempt recovery: symbol "%s" inserted before "%s". >d Wattempt recovery: symbol "%s" ignored.attempt recovery: symbol "%s" substituted for "%s".error: got NULL for lexer callback.file "%s", line "%s".error: got NULL for debug callback when debug flag is set.fatal: internal errorerror: too many errors at token %s. cannot recover.. bye!error: got NULL for one of memory callbacks and not otherserror: lexer callback doesn't handle PZLEXERRGET. J89:;<=&>K?y@Awarning: no 'error' token lookahead for any state on parse stack.HM framework error: [%s] [%s]check [%s] not found in HM catalogToo many parametersrun parameters not formatted correctlyCheck doesn't take any input paramsrun params missing the parameter nameunexpected delimter ';' in the run params textparameter [%s] not registered with this check parameter [%s] value is not a proper numberparameter [%s] value type not supported yetB\CqDEFGHIJOKvLMNO NULL context passed NULL Info passed Param not found default message not found Checker Run got Timed Out dummy HM failure with [%s] as argumentsdummy HM recommendation with [%s] as argumentsdummy HM damage description with [%s] as argumentlist parameter values are of wrong typeunsupported list parameter typeparameter [%s] not found in infoElement list fullInvalid element positionParam type mismtach PVQkRSTUVW3XKY^Zo[\unsupported info typecheck name should be non NULL valueDiag ADR not enabled, can't run checkRun name should be non NULL valueReport type should be non NULL valueReport type should be non NULL valueUnsupported report typeUnsupported report levelcheck name too longrun name too longpseudo context not allowedinvalid timeout valuecheck [%s] can only be executed in database instance ]>ǜmǝǞǟǠ#ǡIǢxǣcheck [%s] can only be executed in ASM instanceControl file is older than datafiles and/or log filesNOARCHIVELOG mode restore datafile %scannot change priority of a critical failure %scannot change priority of a closed failure %sNOARCHIVELOG mode restore datafiles %scannot change priority of a failure to CRITICALcheck failed to complete due to an error. See error belowfailures are changing too rapidly - retry command ǤVǥǦǧ2?Vlunable to access diagnostic repository - retry commandrepair script file is too largebuffer size [%s] is too small - [%s] is neededfailure revalidation timed outInternal error [%s], [%s] from DBMS_IRToo many files openedFile not openinvalid parameter value%s %s has invalid sizeDatabase cannot be mountedControl file %s is missingControl file %s is corruptControl file needs media recovery >m  + v Control file %s does not belong to the databaseControl files are mutually inconsistentInsufficient kernel memory to access %s %sDatabase might be unrecoverable or become unrecoverableRedo log file %s is missingRedo log file %s is corrupt%s %s cannot be opened because of limit on number of open files per processRedo log group %s is unavailable%s %s cannot be accessed because of an ASM Failure DAd%s %s cannot be opened because of system limit on number of open filesArchived redo log file %s is missingArchived redo log file %s is corruptDatabase cannot be opened%s %s cannot be accessed because of NFS mount errorSystem datafile %s: '%s' is missingSystem datafile %s: '%s' is corruptSystem datafile %s: '%s' needs media recoverySee impact for individual child failures%s %s cannot be accessed because of invalid partitioning of raw volume Dp6\ !One or more non-system datafiles are missingOne or more non-system datafiles are corruptOne or more non-system datafiles need media recovery%s %s does not have correct access permissionsDatafile %s: '%s' is missingDatafile %s: '%s' is corruptDatafile %s: '%s' needs media recoverySome objects in tablespace %s might be unavailableDatafile %s: '%s' contains one or more corrupt blocksBlock %s in datafile %s: '%s' is media corrupt ">#h$%&'(F)c*Object %s owned by %s might be unavailableRedo log group %s is corrupt near change %sArchived redo log file %s is corrupt near change %sRecovery cannot be completedPerform block media recovery of block %s in file %sUse a multiplexed copy to restore control file %sRestore a backup control fileIf this is a primary database and you have a CREATE CONTROLFILE script, use it to create a new control fileRestore and recover datafile %s +J,j-}./01B2p345Restore and recover datafiles %sRecover datafile %sRecover datafiles %sTake datafile %s offlineTake datafiles %s offlineIf this is a primary database and a standby database is available, then perform a Data Guard failover initiated from the standbyRecover multiple corrupt blocks in datafile %sTable object %s has corrupted dataTable %s.%s may not be accessibleRow %s of table object %s has corrupted dataTable %s.%s may not be accessible 6>7m8:;<=0>G?iTable object %s mismatched with index object %sTable %s.%s is not synchronized with index %sTable row %s of table object %s mismatched with index object %sRestore and recover databaseRecover databaseDrop and re-create redo log group member %sClear redo log group %sClear unarchived redo log group %sClear unarchived redo log group %s using the UNRECOVERABLE DATAFILE clause in the ALTER DATABASE CLEAR LOGFILE statement@2A]BCDE8FtPerform flashback of the database to SCN %sPerform incomplete database recovery to SCN %sThe repair includes complete media recovery with no data lossThe repair includes point-in-time recovery with some data lossThe repair makes some data temporarily unavailableEnsure that all disks and network connections are functionalIf file %s was unintentionally renamed or moved, restore itG HIJqIf you have an export of tablespace %s, then drop and re-create the tablespace and import the data.If you have the correct version of the control file, then replace the old control fileIf the instance failed when file %s was in online backup mode, then issue ALTER DATABASE END BACKUP. This option must not be used for a restored backupIf you re-created inaccessible files in an alternative location, alter initialization parameters in the parameter file appropriatelyK2LtMNO9PxQObtain a copy of redo block from an alternative source (if exists)Drop damaged log group member and add new member%s %s cannot be accessed because file system does not have correct access permissions%s %s cannot be accessed because it is locked by another processBlock %s of %s %s cannot be accessed because of device IO error%s %s is inaccessibleForce a commit of the corrupted transaction whose id is %sR,SfTUVWTransaction %s is corrupted; its undo segment number is %sTransaction %s is not corruptedUndo segment %s is not corruptedDamage analysis of transaction %s can be found in %sTransaction %s seems to be corrupted; its undo segment number is %sCheck corrupt list in V$CORRUPT_XID_LIST for transaction %s. If present, then force commit it. If not, then corruption is likely to happenX,YZ[3\e]If you restored the wrong version of data file %s, then replace it with the correct oneIf you know which copy of the control file is correct, replace other copies with itEnsure that file system is mounted properly and OS kernel resources are adequately configuredIncrease per-process limit on number of open filesIncrease operating system kernel limit on total number of open filesMount NFS with the Oracle-recommended mount options^,_t`abcjEnsure that disk partition provided to Oracle does not start at sector 0Mount your file system with the required access modeChange access permissions for file %sFind process that is holding lock on file %s and resolve lock conflictEnsure that file %s has correct access permissions and is not locked by another processPlease contact Oracle Support Services to resolve failure %s: %sd8efghi=jwkConfigure operating system kernel so that there is enough memory available to open a fileSQL dictionary health check: %s %s on object %s failedDamaged rowid is %s - description: %sillegal check mask value specifiedCheckpoint database and clear redo log group %sCheckpoint database and clear unarchived redo log group %sCheckpoint database and clear unarchived redo log group %s with unrecoverable datafile(s)Undo segment %s is corruptedl,manopq#Restore database and recover with UNTIL CANCEL optionIf you have the correct version of the control file, then replace %s with itEnsure that ASM instance is upEnsure that ASM disk group is mountedName for datafile %s is unknown in the control fileA repair cannot be performed until the database is restarted. Please shutdown, restart database in nomount mode, and retry ADVISE commandr&stuvIf you have the correct version of the control file, then shutdown the database and replace the old control filePerform incomplete database recoveryNo check meta-data found on specified table %sIf the file exists, rename data file %s to the name of the real file using ALTER DATABASE RENAME FILE command. If the file does not exist, create a new data file using ALTER DATABASE CREATE DATAFILE command.The repair includes flashing the database back with some data losswx_yThe repair includes recovery in NOARCHIVELOG mode with some data lossNo backup of block %s in file %s was found. Drop and re-create the associated object (if possible), or use the DBMS_REPAIR package to repair the block corruptionIf possible, drop and re-create the object associated with the logically corrupted block %s in file %s. Otherwise, use the DBMS_REPAIR package to repair the blockz {|%}Contact Oracle Support Services if the preceding recommendations cannot be used, or if they do not fix the failures selected for repairA database state change is required to repair some failures. An automatic repair might be feasible if you mount the database.A database state change is required to repair some failures. An automatic repair might be feasible if you open the databaseBlock %s in datafile %s: '%s' is logically corrupt~ȀDatafile %s: '%s' was not taken offline cleanly. If you do not want to recover it, then take the file OFFLINE FOR DROP and repeat the ADVISE commandThe repair includes clearing unarchived redo log with some data lossBlock %s in control file is corruptȁThe control file cannot be repaired while the database is mounted or open. Please shutdown, restart the database in nomount mode, and retry the ADVISE command. A backup control file or CREATE CONTROLFILE script will be needed for the repair. If you do not have a backup control file, a CREATE CONTROLFILE script can be built by using 'alter database backup controlfile to trace'.ȂȃȄThe control file cannot be repaired while the database is open or mounted. Please shutdown, restart the database in nomount mode, and retry the ADVISE command. A CREATE CONTROLFILE script will be needed for the repair because a backup control file could not be found. If you do not have a script, one can be built by using 'alter database backup controlfile to trace'.Control file contains one or more corrupt blocksDatabase or some of its functionality may not be available ȅDȆRȇȈȉȊ\ȋxȌȍȎOpen resetlogsAutomatic repairs may be available if you shutdown the database and restart it in mount modeInitiate fast-start failoverRedo log %s with block size %s is incompatible with native disk sector sizeMove file %s with block size %s to a disk with a compatible sector sizeDatafile %s: '%s' is offlineOnline datafile %sOne or more non-system datafiles are offlineTablespace %s: '%s' is offlineOnline tablespace %sȏ ȐCȑȒ^System datafile %s: '%s' is offlineIf datafile '%s' is in the current undo tablespace, then bring it online using ALTER DATABASE DATAFILE %s ONLINE commandA database state change is required to repair some failures. An automatic repair might be feasible if you shut down the database and reopen it in read/write mode.An automatic repair was generated for some of the failures selected for repair. More failures might be repaired if you open the database.ȓ ȔȕȖTAn automatic repair was generated for some of the failures selected for repair. More failures might be repaired if you open the database in read/write mode.Open the database read/write to validate and get repair advice for failure %s: %sOpen the database to validate and get repair advice for failure %s: %sMount the database to validate and get repair advice for failure %s: %sȗȘșAn automatic repair was generated for some of the failures selected for repair. More failures might be repaired if you mount the database.A database state change is required to repair the following failures.An automatic repair was generated for some of the failures selected for repair. A database state change is required to repair the following failures.Ț țȜ:ȝIf you have an export of tablespace %s, open the database read/write, then drop and re-create the tablespace and import the data.If you have an export of tablespace %s, offline its data files, open the database read/write, then drop and re-create the tablespace and import the data.Perform a Data Guard role change (using PL/SQL routine DBMS_DG.INITIATE_FS_FAILOVER).Perform a Data Guard role change (using Data Guard broker failover).ȞȟFȠPerform a Data Guard role change (failover).Shut down, mount the database and try flush redo using ALTER SYSTEM FLUSH REDO TO 'standby name' command. Then perform a Data Guard role change (using Data Guard broker failover). Available standbys: %s.Try flush redo using ALTER SYSTEM FLUSH REDO TO 'standby name' command. Then perform a Data Guard role change (using Data Guard broker failover). Available standbys: %s.ȡȢbShut down, mount the database and try flush redo using ALTER SYSTEM FLUSH REDO TO 'standby name' command. Then perform a Data Guard role change (failover). Available standbys: %s.Try flush redo using ALTER SYSTEM FLUSH REDO TO 'standby name' command. Then perform a Data Guard role change (failover). Available standbys: %s.ASM disk group mount failure can result in failure mounting Oracle database.,JDisk missing from the disk group. Disk number: %s Name: %s Path: %s. See trace file %s.ASM extent allocation failed. ASM disk group may be in unbalanced state.Disk group '%s' Imbalance: '%s%'. Partner Imbalance: '%s%'. Size Variance: '%s%'ASM disk not added to disk group as requested.Requested ASM disk(s) not discovered on all nodes where disk group is mounted. See trace file %s.ASM file %s not dropped as requested. V,-. /+0Q1s234Database %s on host %s currently accessing file.Too many offline disks detected.%sInsufficient number of disks to establish quorum.HM Test CheckCheck for health monitor functionalityNumber of failures to be raisedNumber of recommendations to be raisedDamage description parameter valueFailure description parameter valueDummy element listDB Structure Integrity CheckChecks integrity of all database files5b6z789:;<=%>I?o@ABCCF Block Integrity CheckChecks integrity of a control file blockControl file block numberData Block Integrity CheckChecks integrity of a data file blockFile numberBlock numberRedo Integrity CheckChecks integrity of redo log contentSCN of the latest good redo (if known)Logical Block CheckChecks logical content of a blockTablespace numberRelative block addressSegment header relative block addressDhEFGHIJKL0MCNVOePQRSDictionary object numberData object numberTable CheckChecks integrity of a tableTable object numberTable check modeTable-Index Cross CheckChecks cross references between a table and one of its indexesTable object numberIndex object numberTable Row CheckChecks integrity of a table rowTable object numberTable rowidTable-Index Row MismatchChecks the cross references between a table row and an index entryThU{VWXYZ[\]4^G_X`{abcTable object numberIndex object numberTable rowidIndex entry keyTransaction Integrity CheckChecks a transaction for corruptionsTransaction IDUndo Segment Integrity CheckChecks integrity of an undo segmentUndo segment numberNo Mount CF CheckChecks control file in NOMOUNT modeCF Member CheckChecks a multiplexed copy of the control fileControl file nameAll Datafiles CheckdnefghijklmCnSo`prqrstChecks all datafiles in the databaseSingle Datafile CheckChecks a data fileFile numberLog Group CheckChecks all members of a log groupLog group numberLog Group Member CheckChecks a particular member of a log groupLog group numberLog file nameArchived Log CheckChecks an archived logArchived log nameArchived log record IDRedo Revalidation CheckChecks redo log contentunvwxyz{|}~4MɀcɁ{ɂɃɄɅSCN of the latest good redo (if known)IO Revalidation CheckChecks file accessibilityInaccessible file nameInaccessible file numberIO reasonFile block sizeFile block numberBlock IO Revalidation CheckChecks file accessibilityInaccessible file nameInaccessible file numberFile block sizeInaccessible block numberTxn Revalidation CheckRevalidate corrupted transactionTransaction idɆzɇɈɉɊɋɌɍɎɏ(ɐ>ɑMɒ]ɓqɔɕɖɗɘFailure Simulation CheckCreates dummy failuresDummy failure idDummy failure parametersDictionary Integrity CheckChecks dictionary integrityTable nameCheck maskASM Mount CheckDiagnose mount failureASM disk numberASM group numberASM Allocation CheckDiagnose allocation failureASM group nameASM Disk Visibility CheckDiagnose add disk failureASM File Busy CheckDiagnose file drop failureə\ɚiɛyɝɞɟɠɡ ɢHɣWɤgɥɦASM path nameTablespace CheckChecks a tablespaceTablespace numberMount CF CheckChecks control file in mount modeChecks mount failed because there were too many offline disksDiagnose mount failed because there were too many offline disksASM disk numberASM group numberChecks mount failed because there were insufficient disksDiagnose mount failed because there were insufficient disksASM group nameInvalid file URL&EhInvalid file URL or path prefixCould not find file at URL providedMissing tag from HTMLError %s received from XPath engineXML %s error: %s "%s"