HW/OS2011. 10. 25. 10:08
Posted by [TheWon]
HW/OS2011. 10. 24. 18:05
Posted by [TheWon]
Information2011. 10. 20. 15:39


  • Human error - accidental file deletion, over-writing of files etc.
  • Hardware failure - Disks that are used constantly, or have not been properly maintained may suffer from mechanical failure, over time heavy file-loading or new software can cause the system to shutdown or reboot, alternatively automatic file updates can cause a system to reboot when files are still open and in use.
  • Software corruption can also corrupt data files to make them inaccessible
  • Virus attacks - every day new viruses are released into the open, and anti-virus companies release updates to combat the problem. Virus attacks have been steadily on the increase causing business data to be ever more vulnerable.
  • Natural disasters - even with robust hardware, software and virus protection, the threat from fire and flood remains.


  • - dat roadmap
    저작권































    http://www.dat-mgm.com






    Posted by [TheWon]
    HW/OS2011. 10. 17. 08:51

    A: Check the registry values

    ======================

    1. Click Start, Run and type Regedit.exe
    2. Navigate to the following location

    HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services\ winmgmt

    3. Double-click DependOnService and check if the Value data is RPCSS. If not, please change it to RPCSS

    B: Reset the WMI repository

    ===================

    1. Disable and stop the WMI service.

         sc config winmgmt start= disabled

         net stop winmgmt


    2. Run the following commands.

         Winmgmt /salvagerepository %windir%\System32\wbem      
     

    3. Re-enable the WMI service and then reboot the server to see how it goes.

         sc config winmgmt start= auto


    If the problem continues, let's try to re-register the WMI components

    Re-registering the WMI

    ================

    The .DLL and .EXE files used by WMI are located in %windir%\system32\wbem. You might need to re-register all the .DLL and .EXE files in this directory. 
     

    To re-register the WMI components, run the following commands at the command prompt:

    cd /d %windir%\system32\wbem

    for %i in (*.dll) do RegSvr32 -s %i

    for %i in (*.exe) do %i /RegServer

    Meanwhile, please check if the Svchost.exe process that has the WMI service crashes. If so, please refer to the KB982293 article to fix it.

    http://support.microsoft.com/kb/982293

    http://social.technet.microsoft.com/Forums/en-US/winservergen/thread/57c5ef71-cc95-4ba4-bdf3-10c94e35560e 

    Posted by [TheWon]
    DBMS/Oracle2011. 10. 14. 10:38
    Posted by [TheWon]