Re: imp timeout

In addition to Sybrand's post.
When you write a script for crontab keep in mind that /etc/profile and .profile are not run.
Include them in your script when necessary.

Another solution is to start the command nohup and in the background. Redirection of standard output and standard error makes it complete (without it nohup.out will be the file standard output/error is redirected to). The nohup enables you to logoff without stopping the process. It will become then a child of process 1.
You need to start it in the background (the "&" does that) because bringing it to the background with Ctrl-Z normalley pauses the process. You need the command prompt back to be able to logoff. Example:

     nohup your_script > your_script.log 2>&1 & or

     nohup imp parfile=your_parameterfile.prm 2> imp.log 2>&1 & The parameter file should include every option (the password included) because no interactive action is possible.

Tom <tomNOSPAM_at_teameazyriders.com> schreef in berichtnieuws SWKL9.13823$ny1.110906490_at_news-text.cableinet.net...
| Hi,
|
| Anybody know how to stop an imp timing out when telet'd to a box?
|
| Importing about 5,000,000 rows in 13 tables and just got home and checked
| and it seems to have ground to a halt as doing a ps the time elapsed for
the
| proccess id connected to the imp has been sat at just about an hour for
| about 2.
|
| Oracle 8.1.5 and Solaris 7
|
| would an & after my imp syntax solve this do you think to detach it from
the
| console?
|
| Tom
|
|
Received on Tue Dec 17 2002 - 15:58:20 CST