Session auto killed after a period Inactive

A batch job is scheduled to run at 02:00 AM every night taking a hot backup off database. It puts one and one tablespace into backup mode and copies their datafiles to backup area. This is done on NT 4.0 so the sceduler used is AT.
The job fails after putting the larges tablespace into backup, and while copying this tablespace datafiles (8 x 2GB) somehow the database session is killed. So after finishing the copying, an "ORA-00028, Your session has been killed" is recieved when tablespace is attempted to be changed from backup mode to normal mode. Obviousely, the datafiles that are copied after this are useless because datafiles are open when tablespace failes to be taken into backup mode with error "user not logged on" and datafiles are anyway copied to backuparea independent of session status. When batch job is run via terminal server during daytime it succeeds without any problems. Is there a parameter for how long session should be inactive before killed?

Rgds

Kjell Ove Received on Tue Aug 19 2003 - 03:01:07 CDT