tonydba
asked on
schedule export
How can we schedule export in linux ?
Maybe some of these might help you in findung "your" way ;-)
http://rakeshocp.blogspot.de/2009/11/scheduling-export-shell-script.html
http://arvindasdba.blogspot.de/2013/08/expdp-full-backup-thru-scheduler.html
http://www.dba-oracle.com/oracle_news/2006_8_10_schedule_export.htm
http://rakeshocp.blogspot.de/2009/11/scheduling-export-shell-script.html
http://arvindasdba.blogspot.de/2013/08/expdp-full-backup-thru-scheduler.html
http://www.dba-oracle.com/oracle_news/2006_8_10_schedule_export.htm
Hi Tony, just as background, can you provide:
-- the database version;
-- whether or not you mean export, or its replacement, datapump (expdp);
-- whether or not the database instance is running in ARCHIEVELOG mode (changes captured as REDO, written, saved as archive logs)
Where I'm going with this, is to educate you on having a recoverable backup. Export is good for having copies of stuff, but awkward to restore from.
-- the database version;
-- whether or not you mean export, or its replacement, datapump (expdp);
-- whether or not the database instance is running in ARCHIEVELOG mode (changes captured as REDO, written, saved as archive logs)
Where I'm going with this, is to educate you on having a recoverable backup. Export is good for having copies of stuff, but awkward to restore from.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
fine thanks..
Here is the documentation for the cron file (aka crontab) -> http://www.manpagez.com/man/5/crontab/
If your version of crontab supports it, you should run the "crontab -e". That should bring up the current version of the file and allow you to edit it. Once you save it, it will be loaded for you.
Be sure that whatever script you write sets up the Oracle environment. Command run through cron do not execute your login scripts, so absolutely no environment variables will be set up before the script is run.