I found the reason this is happening. This is due to Bug 3478119. The cause of this behavior. is due to the Oracle Performance Monitor (oraperf.dll) which is a performance DLL that is attempting to connect to the database using incorrect credentials. oraperf.dll and all other performance DLLs are being loaded when nmupm.exe is called by the Management Agent. The install of Oracle Performance Monitor hardcodes the password for the database "SYSTEM" account to "MANAGER". This causes the SYSTEM user to get locked out when the DLL is loaded. This can occur on Windows Platforms. Although I had installed Oracle Counters for Windows Performance Monitor I was not yet using it. In order to resolve The 10g Windows documentation informs customers to run a tool called operfcfg to change the system password. The command is: operfcfg.exe -U system -P {your system password} -D {SID}. I did this yesterday and so far the system account has not locked.
来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/10640532/viewspace-620672/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/10640532/viewspace-620672/