Re: Message 2100 not found; No message file for product=RDBMS

spraveen2001_at_yahoo.com (Praveen) wrote in message news:<98d8ec76.0302272258.4febc713_at_posting.google.com>...
> Hi All,
>
> I'm running shell script using cronjob, in that shell script, i'm
> running sqlldr..but getting this problem.
>
> Message 2100 not found; No message file for product=RDBMS,
> facility=ULMessage 2100 not found; No message file for product=RDBMS,
> facility=UL
>
> my oracle home is : /usr/oracle/ora81
> running sqlldr using : /usr/oracle/ora81/bin/sqlldr....
>
> I Searched in net for help, some one said that, it is installation
> problem,we have to set environment varaibles. If yes, which are all
> the env variables we need to set to get rid of the above problem.
> Please Help
>
> Thanks in Advance,
> Praveen

Praveen, if you set your Oracle environment and run sqlldr from the comand line does it work correctly? If so, then you have not properly set the Oracle environment with the shell script. Because sqlldr will fork a new shell you must set and export the necessary Oracle environment variables within the cron script.

# Korn example
export ORACLE_HOME=/ora/v817
export ORACLE_SID=PROD
export TWO_TASK=OURDB <== if you are connecting to db on different mach
sqlldr control=x ....

OR
#
. outenviron_script
sqlldr control ....

If you cannot execute sqlldr correctly from the command line then either the install is not correct, your environment is not set correctly, or you are on a different machine that your target db and no Oracle rdbms is installed on the local machine. I have seen error messages similar to what you displayed on client machines where the message files stored under $ORACLE_HOME/rdbms/mesg are not available. The actual Oracle error is probably 02100. Both ora-02100 and sql-02100 have to do with lack of memory (from 8.1.7 oerr), which could imply a ulimit settings problem.

$ oerr ora 2100
02100, 00000, "PCC: out of memory (i.e., could not allocate)" $ oerr sql 2100
02100, 00000, "Out of memory (i.e., could not allocate)"

// *Cause:  SQLLIB was unable to allocate enough memory to execute 
//          the program.
// *Action: Allocate more memory to the user session, then rerun the
program.
//          If the error persists, call customer support for

HTH -- Mark D Powell -- Received on Fri Feb 28 2003 - 16:17:43 CET