Issue solved.. :)
Hi,
Issue solved...! This was not the issue with WinScp. I was running .sql files through batch files. These batch files were scheduled in windows "scheduled task", which was running by a "local user acccount". Few days before I checked in "Task Manager", there were more than 70 number of sqlplus.exe processes running(which, is because of those batch files). Those sql instances were not terminating. I manually killed all the sqlplus.exe processes from "Task Manager" and put a "exit" command at the end of all the .sql files. Now, these .sql files are closing the DB instances after completing its expected task. So, this was not the problem with WinScp, The no. of processes of a particular "local user account" were consuming all assigned memory to that user account. Because of that whenever I was restarting my server, it was running fine for few days until the no. of sqlplus.exe processes consuming the whole assigned memory. Now its working fine.. :)
Issue solved...! This was not the issue with WinScp. I was running .sql files through batch files. These batch files were scheduled in windows "scheduled task", which was running by a "local user acccount". Few days before I checked in "Task Manager", there were more than 70 number of sqlplus.exe processes running(which, is because of those batch files). Those sql instances were not terminating. I manually killed all the sqlplus.exe processes from "Task Manager" and put a "exit" command at the end of all the .sql files. Now, these .sql files are closing the DB instances after completing its expected task. So, this was not the problem with WinScp, The no. of processes of a particular "local user account" were consuming all assigned memory to that user account. Because of that whenever I was restarting my server, it was running fine for few days until the no. of sqlplus.exe processes consuming the whole assigned memory. Now its working fine.. :)