Your question is not clear. What do you mean by print out. You couldn't invoke the print option from windows menu or your database was not returning any query output. Are you using any application to connect to the database and generate the output if so what was that? I would also check into the alert_log files to check for any ora errors. on such case, please let us know of the error message too to further suggest any possible solutions.
I did check the alert log file, but there was no ora-errors.
Oracle database is available.
We have developed an application using D2K through which the user's work. One of the module in the application is used for printing.
So when the user tried that he was not getting any output and I tried to check the printer's queue. When I attempted to open the printer's queue (by clicking Start->Control Panel->Printers) the Start menu was not responding.
Once I re-started the system then everything was back to normal.
I have had experience running 24x7 NT boxes and they normally do not require regular reboots.
Are you able to check the Task Manager before you reboot?
This may help you isolate the problem.
You may find that it is the same process causing the problem each time, prehaps the print function within the application needs to be looked at or the other option may be to apply the latest Oracle certified NT service pack.
What I think is that due to load , your server hangs after some days therefore when u reboot it relieves all the memory and then it works fine.I think when the printer was not responding at the same time ur sql would also be not responding.I think you should upgrade your server config.Do correct me if I am wrong .
I would like to add a couple of questions to this.
1. How do I find out the Oracle certified NT version.
2. I don't think that there is any link between the printer failure and the start button not-responding.
Even a couple of developers face this problem.
Would it be due to some installation failure. I even tried searching in Microsoft.com, but I was not able to find any entries related to this.
WinNT sometimes have the memory leak issue as a result the system would require a reboot. One other thing that I would proceed to check was that is the desig version compatible to the Wind NT that you are running and that for any patches