Problem:
Sometimes Oracle simply flashes the following message or something similar.
Shutting down or initialization in progress.
There's nothing you could do, even after u waited for ages for it to complete its cycle.
Solution:
This is unorthodox, but me being bad programmer, i choose to solve the problem first before looking for detailed explanations.
Log in under SQLPlus with following command.
sqlplus sys/yourpassword as sysdba
Then run the following SQLPLUS commands.
shutdown immediate;
startup;
Sometimes of order of the SQLPlus command needs to be reverse, depending on its state.
Saturday, July 12, 2008
Saturday, March 8, 2008
Dlink DI-624 disconnects
Problem:
DI-624 disconnects every few minutes. The problem escalates with more wireless clients, or when a BitTorrent software runs in the background.
Solution:
It seems that the issue can be resolved by simply disabling the UPnP function in the router.
Note that the router still couldn't handle high amount of simultaneous connections, so please tune your BitTorrent application accordingly.
DI-624 disconnects every few minutes. The problem escalates with more wireless clients, or when a BitTorrent software runs in the background.
Solution:
It seems that the issue can be resolved by simply disabling the UPnP function in the router.
Note that the router still couldn't handle high amount of simultaneous connections, so please tune your BitTorrent application accordingly.
Saturday, March 1, 2008
Sharepoint search crawl failed
Problem:
Sharepoint's indexing service unable to crawl site. Error given as follows.
[To be updated]
Possible Solutions:
1) In my scenario, the problem was caused by a impersonate="false" setting in web.config. Somehow, the Indexing service requires impersonation to be true. However, some custom Sharepoint pages may require impersonation to be disabled. If impersonation cannot be enabled for your application, try the following alternative.
In Sharepoint's Central administration, you can extend the web application. By doing this, you are essentially creating a second web app site (with a different port number) for your application. However, the content source are shared with the original web app. Thus both sites are actually identical. Now, the newly created web app site would have impersonation enabled by default.
In your crawler settings, replace the original site path with the new port number.
Eg: Original is http://mysite, New is http://mysite:2434
The indexing/crawling will now function and search results will be redirected to http://mysite.
[Detailed steps to be updated]
Sharepoint's indexing service unable to crawl site. Error given as follows.
[To be updated]
Possible Solutions:
1) In my scenario, the problem was caused by a impersonate="false" setting in web.config. Somehow, the Indexing service requires impersonation to be true. However, some custom Sharepoint pages may require impersonation to be disabled. If impersonation cannot be enabled for your application, try the following alternative.
In Sharepoint's Central administration, you can extend the web application. By doing this, you are essentially creating a second web app site (with a different port number) for your application. However, the content source are shared with the original web app. Thus both sites are actually identical. Now, the newly created web app site would have impersonation enabled by default.
In your crawler settings, replace the original site path with the new port number.
Eg: Original is http://mysite, New is http://mysite:2434
The indexing/crawling will now function and search results will be redirected to http://mysite.
[Detailed steps to be updated]
Subscribe to:
Posts (Atom)