Windows System Error Codes exit codesCode Description 0 The operation completed successfully. 1 Incorrect function. 2 The system cannot find the file specified. 3 The system cannot find the path specified. 4 The system cannot open the file. 5 Access is denied. 6 The handle is invalid. 7 The storage control blocks were destroyed. 8 Not enough storage is available to process this command. 9 The storage control block address is invalid. 1. The environment is incorrect. 1. As an essential part of the life cycle management of a RAC Database, the design, configuration, and management of such a shared storage system is vital for the long. An attempt was made to load a program with an incorrect format. 1. The access code is invalid. 1. The data is invalid. 1. Not enough storage is available to complete this operation. 1. The system cannot find the drive specified. 1. The directory cannot be removed. 1. The system cannot move the file to a different disk drive. 1. There are no more files. 1. The media is write protected. 2. The system cannot find the device specified. 2. The device is not ready. 2. The device does not recognize the command. 2. Data error cyclic redundancy check. 2. The program issued a command but the command length is incorrect. 2. The drive cannot locate a specific area or track on the disk. 2. The specified disk or diskette cannot be accessed. 2. The drive cannot find the sector requested. 2. The printer is out of paper. 2. The system cannot write to the specified device. 3. The system cannot read from the specified device. 3. A device attached to the system is not functioning. 3. The process cannot access the file because it is being used by another process. 3. The process cannot access the file because another process has locked a portion of the file. 3. The wrong diskette is in the drive. Insert 2 Volume Serial Number 3 into drive 1. 3. Too many files opened for sharing. 3. Reached the end of the file. 3. The disk is full. 5. The request is not supported. 5. Windows cannot find the network path. Verify that the network path is correct and the destination computer is not busy or turned off. If Windows still cannot find the network path, contact your network administrator. 5. You were not connected because a duplicate name exists on the network. Go to System in the Control Panel to change the computer name and try again. 5. The network path was not found. 5. The network is busy. 5. The specified network resource or device is no longer available. 5. The network BIOS command limit has been reached. 5. A network adapter hardware error occurred. 5. The specified server cannot perform the requested operation. 5. An unexpected network error occurred. 6. The remote adapter is not compatible. 6. The printer queue is full. 6. Space to store the file waiting to be printed is not available on the server. 6. Your file waiting to be printed was deleted. 6. The specified network name is no longer available. 6. Network access is denied. 6. The network resource type is not correct. 6. The network name cannot be found. 6. The name limit for the local computer network adapter card was exceeded. 6. The network BIOS session limit was exceeded. 7. The remote server has been paused or is in the process of being started. 7. No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. 7. The specified printer or disk device has been paused. 8. The file exists. 8. The directory or file cannot be created. 8. Fail on INT 2. 4. 8. Storage to process this request is not available. 8. The local device name is already in use. 8. The specified network password is not correct. 8. The parameter is incorrect. 8. A write fault occurred on the network. 8. The system cannot start another process at this time. 1. Cannot create another system semaphore. 1. The exclusive semaphore is owned by another process. 1. The semaphore is set and cannot be closed. 1. The semaphore cannot be set again. 1. Cannot request exclusive semaphores at interrupt time. 1. The previous ownership of this semaphore has ended. 1. Insert the diskette for drive 1. 1. The program stopped because an alternate diskette was not inserted. 1. The disk is in use or locked by another process. 1. The pipe has been ended. 1. The system cannot open the device or file specified. 1. The file name is too long. 1. There is not enough space on the disk. 1. No more internal file identifiers available. 1. The target internal file identifier is incorrect. 1. The IOCTL call made by the application program is not correct. 1. The verify on write switch parameter value is not correct. 1. The system does not support the command requested. 1. This function is not supported on this system. 1. The semaphore timeout period has expired. 1. The data area passed to a system call is too small. 1. The filename, directory name, or volume label syntax is incorrect. 1. The system call level is not correct. 1. The disk has no volume label. 1. The specified module could not be found. 1. The specified procedure could not be found. 1. There are no child processes to wait for. 1. The 1 application cannot be run in Win. Attempt to use a file handle to an open disk partition for an operation other than raw disk IO. 1. An attempt was made to move the file pointer before the beginning of the file. 1. The file pointer cannot be set on the specified device or file. 1. A JOIN or SUBST command cannot be used for a drive that contains previously joined drives. 1. An attempt was made to use a JOIN or SUBST command on a drive that has already been joined. 1. An attempt was made to use a JOIN or SUBST command on a drive that has already been substituted. 1. The system tried to delete the JOIN of a drive that is not joined. 1. The system tried to delete the substitution of a drive that is not substituted. 1. The system tried to join a drive to a directory on a joined drive. 1. The system tried to substitute a drive to a directory on a substituted drive. 1. The system tried to join a drive to a directory on a substituted drive. 1. The system tried to SUBST a drive to a directory on a joined drive. 1. The system cannot perform a JOIN or SUBST at this time. 1. The system cannot join or substitute a drive to or for a directory on the same drive. 1. The directory is not a subdirectory of the root directory. 1. The directory is not empty. 1. The path specified is being used in a substitute. 1. Not enough resources are available to process this command. 1. The path specified cannot be used at this time. 1. An attempt was made to join or substitute a drive for which a directory on the drive is the target of a previous substitute. 1. System trace information was not specified in your CONFIG. SYS file, or tracing is disallowed. 1. The number of specified semaphore events for Dos. Mux. Sem. Wait is not correct. 1. Dos. Mux. Sem. Wait did not execute too many semaphores are already set. 1. The Dos. Mux. Sem. Wait list is not correct. 1. The volume label you entered exceeds the label character limit of the target file system. 1. Cannot create another thread. 1. The recipient process has refused the signal. 1. The segment is already discarded and cannot be locked. 1. The segment is already unlocked. 1. The address for the thread ID is not correct. 1. The argument string passed to Dos. Exec. Pgm is not correct. 1. The specified path is invalid. 1. A signal is already pending. 1. No more threads can be created in the system. 1. Unable to lock a region of a file. 1. The requested resource is in use. 1. A lock request was not outstanding for the supplied cancel region. 1. The file system does not support atomic changes to the lock type. 1. The system detected a segment number that was not correct. 1. The operating system cannot run 1. 1. Cannot create a file when that file already exists. 1. The flag passed is not correct. 1. The specified system semaphore name was not found. 1. The operating system cannot run 1. 1. The operating system cannot run 1. 1. The operating system cannot run 1. 1. Cannot run 1 in Win. The operating system cannot run 1. 1. Win. 32 application. 1. The operating system cannot run 1. 1. The operating system cannot run 1. 1. The operating system cannot run this application program. 1. The operating system is not presently configured to run this application. 1. The operating system cannot run 1. 1. The operating system cannot run this application program. 2. The code segment cannot be greater than or equal to 6. K. 2. 01 The operating system cannot run 1. 2. The operating system cannot run 1. 2. The system could not find the environment option that was entered. 2. No process in the command subtree has a signal handler. 2. Administering ASM Disk Groups. ASM Mirroring and Failure Groups. If you specify mirroring for a file, then ASM automatically stores redundant copies of the file extents in separate failure groups. Failure groups apply only to normal and high redundancy disk groups. You can define the failure groups for each disk group when you create or alter the disk group. There are three types of disk groups based on the ASM redundancy level. Table 4 1 lists the types with their supported and default mirroring levels. The default mirroring levels indicate the mirroring level with which each file is created unless a different mirroring level is designated. Table 4 1 Mirroring Options for ASM Disk Group Types. Disk Group Type. Supported Mirroring Levels. Default Mirroring Level. External redundancy. Unprotected noneUnprotected. Normal redundancy. Two way. Three way. Unprotected NoneTwo way. High redundancy. Three way. Three way. The redundancy level controls how many disk failures are tolerated without dismounting the disk group or losing data. Each file is allocated based on its own redundancy, but the default comes from the disk group. The redundancy levels are External redundancy. ASM does not provide mirroring redundancy and relies on the storage system to provide RAID functionality. Any write error cause a forced dismount of the disk group. All disks must be located to successfully mount the disk group. Normal redundancy. ASM provides two way mirroring. By default all files are mirrored so that there are two copies of every data extent. A loss of one ASM disk is tolerated. High redundancy. ASM provides triple mirroring by default. A loss of two ASM disks in different failure groups is tolerated. Failure groups enable the mirroring of metadata and user data. System reliability can diminish if your environment has an insufficient number of failure groups. This section contains these topics ASM Failure Groups. Failure groups are used to store mirror copies of data. When ASM allocates an extent for a normal redundancy file, ASM allocates a primary copy and a secondary copy. ASM chooses the disk on which to store the secondary copy so that it is in a different failure group than the primary copy. Each copy is on a disk in a different failure group so that the simultaneous failure of all disks in a failure group does not result in data loss. A failure group is a subset of the disks in a disk group, which could fail at the same time because they share hardware. The failure of common hardware must be tolerated. Four drives that are in a single removable tray of a large JBOD array should be in the same failure group because the tray could be removed making all four drives fail at the same time. Drives in the same cabinet could be in multiple failure groups if the cabinet has redundant power and cooling so that it is not necessary to protect against failure of the entire cabinet. However, ASM mirroring is not intended to protect against a fire in the computer room that destroys the entire cabinet. There are always failure groups even if they are not explicitly created. If you do not specify a failure group for a disk, then Oracle automatically creates a new failure group containing just that disk. A normal redundancy disk group must contain at least two failure groups. A high redundancy disk group must contain at least three failure groups. However, Oracle recommends using several failure groups. A small number of failure groups, or failure groups of uneven capacity, can create allocation problems that prevent full use of all of the available storage. How ASM Manages Disk Failures. Depending on the redundancy level of a disk group and how you define failure groups, the failure of one or more disks could result in either of the following The disks are first taken offline and then automatically dropped. In this case, the disk group remains mounted and serviceable. In addition, because of mirroring, all of the disk group data remains accessible. After the disk drop operation, ASM performs a rebalance to restore full redundancy for the data on the failed disks. The entire disk group is automatically dismounted, which means loss of data accessibility. Guidelines for Using Failure Groups. The following are guidelines for using failure groups Each disk in a disk group can belong to only one failure group. Failure groups should all be of the same size. Failure groups of different sizes may lead to reduced availability. ASM requires at least two failure groups to create a normal redundancy disk group and at least three failure groups to create a high redundancy disk group. Failure Group Frequently Asked Questions. This section discusses frequently asked questions about failure group under the following topics How Many Failure Groups Should I Create Choosing the number of failure groups to create depends on the types of failures that need to be tolerated without data loss. For small numbers of disks, such as fewer than 2. Using the default failure group creation for small numbers of disks is also applicable for large numbers of disks where your main concern is disk failure. For example, a disk group might be configured from several small modular disk arrays. If the system must continue operating when an entire modular array fails, then a failure group should consist of all of the disks in one module. If one module fails, then all of the data on that module will be relocated to other modules to restore redundancy. Disks should be placed in the same failure group if they depend on a common piece of hardware whose failure must be tolerated with no loss of availability. How are Multiple Failure Groups Recovered after Simultaneous Failures A simultaneous failure can occur if there is a failure of a piece of hardware used by multiple failure groups. This type of failure usually forces a dismount of the disk group if all disks are unavailable. When Should External, Normal, or High Redundancy Be UsedASM mirroring runs on the database server and Oracle recommends to off load this processing to the storage hardware RAID controller by using external redundancy. You can use normal redundancy in the following scenarios Storage system does not have RAID controller. Mirroring across storage arrays. Extended cluster configurations. In general, ASM mirroring is the Oracle alternative to third party logical volume managers. ASM mirroring eliminates the need to deploy additional layers of software complexity in your Oracle database environment. ASM Recovery from Read and Write IO Errors. Read errors can be the result of a loss of access to the entire disk or media corruptions on an otherwise a healthy disk. ASM tries to recover from read errors on corrupted sectors on a disk. When a read error by the database or ASM triggers the ASM instance to attempt bad block remapping, ASM reads a good copy of the extent and copies it to the disk that had the read error. If the write to the same location succeeds, then the underlying allocation unit sector is deemed healthy. This might be because the underlying disk did its own bad block reallocation. If the write fails, ASM attempts to write the extent to a new allocation unit on the same disk. If this write succeeds, the original allocation unit is marked as unusable. If the write fails, the disk is taken offline. One unique benefit on ASM based mirroring is that the database instance is aware of the mirroring. For many types of logical corruptions such as a bad checksum or incorrect System Change Number SCN, the database instance proceeds through the mirror side looking for valid content and proceeds without errors. If the process in the database that encountered the read is in a position to obtain the appropriate locks to ensure data consistency, it writes the correct data to all mirror sides. When encountering a write error, a database instance sends the ASM instance a diskoffline message. If database can successfully complete a write to at least one extent copy and receive acknowledgment of the offline disk from ASM, the write is considered successful. If the write to all mirror side fails, database takes the appropriate actions in response to a write error such as taking the tablespace offline. When the ASM instance receives a write error message from an database instance or when an ASM instance encounters a write error itself, ASM instance attempts to take the disk offline. ASM consults the Partner Status Table PST to see whether any of the disks partners are offline.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
November 2017
Categories |