Shulou(Shulou.com)06/01 Report--

After oracle10g logs in to em, it prompts "java.lang.Exception: Exception in sending Request:: null"

The interface that appears when logging in to Enterprise Manager when an error occurs

This error usually occurs because the time zone is not set, and the default is agentTZRegion=GMT, that is, GMT. So all you have to do is set this thing and restart dbconsole. The following is the whole process of setting up and restarting dbconsole.

The first step is to find and type the file emd.properties in the Oracle installation directory, D:\ oracle\ product\ 10.2.0\ db_1\ PC-20111014FOHC_orcl\ sysman\ config, where mine is located. It is estimated that everyone can find here D:\ oracle\ product\ 10.2.0\ db_1, and then there is the PC-20111014FOHC_orcl folder, which is my computer name _ database global variable, you just need to find this file named by your computer, then find sysman\ config in turn, and then find the emd.properties file. Then open the file in notepad, and you can see agentTZRegion=GMT on the last line of the file.

The second step is to change the GMT in agentTZRegion=GMT to Asia/Shanghai, that is, agentTZRegion=Asia/Shanghai. There is a problem here, that is, the initials of Asia must be capitalized, and the initials of Shanghai should be larger. You can also use other regions, such as Asia/Beijing, but I have tried that this will not work on my machine, and it will display correctly after changing it to Shanghai. I don't know why. For a list of time zones, refer to 10.2.0\ db_1\ sysman\ admin\ supportedtzs.lst to find the files in the following path. Just save it after you change it.

The third step is to enter this command under cmd, > set oracle_sid=wangdan (wangdan, that is, the database global variable name, that is, the database name). Of course, there is no response after entering enter. As shown below:

The fourth step, continue to enter the command > emctl stop dbconsole (you must pay attention to emctl, the last letter is L, not 1, the author because l into 1, took a lot of effort, I hope you do not make my mistake). This step is to close dbconsole, and press enter as shown below:

The fifth and final step is to start the dbconsole service that was shut down.

Type the command > emctl start dbconsole, and press enter as shown below:

All right, after all this, restart your browser, and then log in to Enterprise Manager again, and you will find that the error java.lang.Exception:Exception in sending Request:: null is gone.

I restart the browser, and the interface after re-login is shown below:

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.