Backup failures for offline COPYING large files
BR0280I BRBACKUP time stamp: 2008-04-11 20.29.38
BR0063I 45 of 94 files processed - 40410.203 MB of 78668.338 MB done
BR0204I Percentage done: 51.37%, estimated end time: 20:56
BR0001I **************************________________________
BR0202I Saving G:\ORACLE\PRD\SAPDATA1\ES620I_1\ES620I.DATA1
BR0203I to F:\oracle\PRD\sapbackup\bdxrhgxf\ES620I.DATA1 ...
BR0278E Command output of 'copy G:\ORACLE\PRD\SAPDATA1\ES620I_1\ES620I.DATA1 F:\oracle\PRD\sapbackup\bdxrhgxf\ES620I.DATA1':
Insufficient system resources exist to complete the requested service. 0 file(s) copied.
BR0280I BRBACKUP time stamp: 2008-04-11 20.31.20
BR0279E Return code from 'copy G:\ORACLE\PRD\SAPDATA1\ES620I_1\ES620I.DATA1 F:\oracle\PRD\sapbackup\bdxrhgxf\ES620I.DATA1': 1
BR0222E Copying G:\ORACLE\PRD\SAPDATA1\ES620I_1\ES620I.DATA1 to/from F:\oracle\PRD\sapbackup\bdxrhgxf\ES620I.DATA1 failed due to previous errors
BR0280I BRBACKUP time stamp: 2008-04-11 20.31.24
http://support.microsoft.com/kb/913872
http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=1444560&SiteID=50
——————————————————————
http://support.microsoft.com/kb/304101/en-us
:
RESOLUTION
Windows Server 2003 and Windows 2000
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 (http://support.microsoft.com/kb/322756/) How to back up and restore the registry in Windows
You may have to change two registry settings. You must always change the first setting. Depending on the configuration of your system, you may also have to change the second setting.
Registry setting 1
| 1. | Click Start, click Run, type regedit in the Open box, and then click OK. |
| 2. | Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management |
| 3. | On the Edit menu, point to New, and then click DWORD Value. |
| 4. | Type PoolUsageMaximum as the entry name, and then press ENTER. |
| 5. | Right-click PoolUsageMaximum, and then click Modify. |
| 6. | Click Decimal. |
| 7. | In the Value data box, type 60, and then click OK.
Important| • | Use 60 as your initial value. If your backup does not succeed, use 40 as your value. If that does not work, you must change the behavior of your backup program to reduce the demand of paged pool. If the value works, you may want to increase the value by approximately 25 percent until the backup does not work. If the backup is unsuccessful, use the second registry setting that is described in this article. | | • | Make sure that the value for this registry setting is not more than 60. | | • | If you are using the /3GB switch, use 40 as your initial setting. Note that this value is a percentage value. |
|
| 8. | Quit Registry Editor. |
| 9. | Restart your computer. |
Because you must test these settings during the most stressful backups, you may have to wait a month for a whole backup cycle to complete if you are not sure which backup consumes the most resources. Because of this situation, Microsoft recommends that you test low values first. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
312362 (http://support.microsoft.com/kb/312362/) Server is unable to allocate memory from the system paged pool
Registry setting 2
| 1. | Click Start, click Run, type regedit in the Open box, and then click OK |
| 2. | Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management |
| 3. | On the Edit menu, point to New, and then click DWORD Value. |
| 4. | Type PagedPoolSize as the entry name, and then press ENTER. |
| 5. | Right-click PagedPoolSize, and then click Modify. |
| 6. | Click Hexadecimal. |
| 7. | In the Value data box, type a value of FFFFFFFF, and then click OK.
Important| • | Setting PagedPoolSize to 0xFFFFFFFF (-1) allocates the maximum paged pool instead of other resources to the computer. This is typically required on a domain controller or a terminal server. By default, most Windows 2000 systems seem to be limited to a paged pool maximum size of 160 MB. You can verify this by downloading the kernel debuggers from the public Web site and opening a kernel dump in the debugger that you want to use. The command to use is !vm. This shows a paged pool maximum of 163840 KB, for example. Adding this value reduces the Page Table Entries (PTEs) that are available on a system and extends the paged pool maximum to 343 MB in Windows 2000. The paged pool maximum size can be extended to a larger value in Windows Server 2003.
Note The default and maximum paged pool values for Windows Server 2003 are much larger than in Windows 2000. Typically, the Windows Server 2003 values are at least 50 percent higher than the values found in Windows 2000. These larger values makes it more unlikely that you will experience the issue where paged pool values contribute to the problem that is described in this article. However, it is still possible that this issue may occur. | | • | This value restricts the system PTEs that are available. PTEs are another unrelated system resource that your system uses. This setting may cause your operating system to stop unexpectedly and to display a stop 0x3F error on a blue screen when it starts. You can recover from this by using the Last Known Good restart option on the system restart menu or recovery console. Use Performance Monitor to view the Free System Page Table Entries counter. You can add the PagePoolSize setting if the observed free values are over 40,000. | | • | If you are running /3GB and /PAE together, do not set this setting without extensive testing and before you establish exactly how many system PTES you must have in your environment. You will probably see values in the range of 10,000-20,000 free. Use the articles to configure paged pool memory but never drop below 10,000 free system PTEs. Do not set this to any other value if you are using the /3GB switch. The only supported values are 0, 0A000000, and FFFFFFFF. |
|
| 8. | Quit Registry Editor. |
| 9. | Restart your computer. |
For more information about how to avoid and resolve this problem, click the following article numbers to view the articles in the Microsoft Knowledge Base:
256004 (http://support.microsoft.com/kb/256004/) How to troubleshoot "STOP 0x0000003F" and "STOP 0x000000D8" error messages in Windows Server 2003, Windows XP, and Windows 2000
missing statistic
BR0969I Checking database administration...
BR0970W Database administration alert - level: WARNING, type: TABLESPACE_FULL, object: PSAPUNDO, value: 100.00% (> 95%)
BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (table) SAPR3.CKMLPP
BR0970W Database administration alert - level: ERROR, type: MISSING_STATISTICS, object: (table) SAPR3.CO2MAP
......
rebuiding index --db02 performance db(table index)
DS400 peer controller enabled
Be care of default password should UPCASE with zero instead of O
Controller A failure
DS400 peer controller enabled -192.168.70.123
124