- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Sql Loader is giving fatal error message when ...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2002 01:14 AM
тАО09-05-2002 01:14 AM
SQL*LOADER EXECUTION ENCOUNTERED A FATAL ERROR.
This is the error message I am getting when I am calling from Cronjob.
Below is the command that we are using to call sql loader
/app/oracle901/oracleapp/bin/sqlldr USERID=$UID/$PD@$DBNAME
CONTROL=$CONTROL_FILE DATA=/nbs/sql-data/$PTLFL_FILE.dat
log=/nbs/sql-data/ptlflog.log direct=TRUE
RETCODE=`echo $?`
case "$RETCODE" in
0) echo "SQL*LOADER EXECUTION SUCCESSFUL" ;;
1) echo "SQL*LOADER EXECUTION EXITED WITH EX_FAIL, SEE LOGFILE" ;;
2) echo "SQL*LOADER EXECTUION EXITED WITH EX_WARN, SEE LOGFILE" ;;
3) echo "SQL*LOADER EXECUTION ENCOUNTERED A FATAL ERROR" ;;
*) echo "UNKNOWN RETURN CODE";;
esac
The same if I execute from / positon also I am able to load the data
successfully.
Remaing all files also have perminssions.(whatever is required)
Attached shell works pretty fine with the same userid if I execute manually from the root location.And it does not need any profile settings also as I am calling every thing through full path.
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2002 02:12 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2002 03:54 AM
тАО09-05-2002 03:54 AM
Re: Sql Loader is giving fatal error message when I try to invoke from crontab
You need to initialise all your environment variables in your cron script.
cf this link
http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xbd25eea29889d611abdb0090277a778c,00.html
Jean-Luc
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2002 04:05 AM
тАО09-05-2002 04:05 AM
Re: Sql Loader is giving fatal error message when I try to invoke from crontab
I want to full points to him ..I dont know how to assign.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-05-2002 04:05 AM
тАО09-05-2002 04:05 AM
Re: Sql Loader is giving fatal error message when I try to invoke from crontab
I want to give full points to him ..I dont know how to assign.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-06-2002 05:45 AM
тАО09-06-2002 05:45 AM
Re: Sql Loader is giving fatal error message when I try to invoke from crontab
So.... whenever I put in a set of cronjobs related to each other, I make a project.env file. I put all of the environment vars in there.
Near the top of all my cronjob script (for the specific project), I put.
#----------
# set env
#----------
. /absolute/path/to/project/projectname.env
Of course third party software could have problems like this too. I had this issue on sybase, unidata, and a thing called redback.
And YOU had the problem with Oracle.
steve