Page 1 of 1

Oracle Error

Posted: Thu Dec 10, 2009 3:09 am
by deepa_shenoy
Hi All,

I don't know what to do to remove this Fatal Error:

Oracle_Enterprise_3,1: The system(sqlldr CONTROL=ora.2714.131128.1.ctl LOG=ora.2714.131128.1.log BAD=ora.2714.131128.1.log.bad SILENT=header PARFILE=ora.2714.131128.1.par) failed; see the log file for the Oracle specific message.

Only few of the records are getting inserted into the target table.

Any solution?

Thanks in advance.

-Deepa

Posted: Thu Dec 10, 2009 3:47 am
by thanush9sep
Check whether you have handled null.

If your source column is NOT NULL and the Target table is NULL then you might face this type of error.

Posted: Thu Dec 10, 2009 4:10 am
by deepa_shenoy
All are Nullable. All columns in all stages are Nullable.

Posted: Thu Dec 10, 2009 4:21 am
by ray.wurlod
Read ora.2714.131128.1.log - it should reveal the actual problem.

Re: Oracle Error

Posted: Thu Dec 10, 2009 6:13 am
by chulett
deepa_shenoy wrote:see the log file for the Oracle specific message.

Posted: Thu Dec 10, 2009 6:17 am
by deepa_shenoy
I read that too... but I dont know where and how to see the log file!!

Posted: Thu Dec 10, 2009 6:23 am
by chulett
The 'where' would be wherever your config designates as 'scratch' space. As for 'how' it's just a plain old text file.

Posted: Thu Dec 10, 2009 10:07 am
by rupeshg
deepa_shenoy wrote:I read that too... but I dont know where and how to see the log file!!
If you have root access on Unix machine (u could try with your login), a simple find command would help you locate the file.
find / -name ora.2714.131128.1.log

Posted: Thu Dec 10, 2009 10:25 am
by priyadarshikunal
If you have root access on Unix machine (u could try with your login), a simple find command would help you locate the file.
Why you need root priviledge to find and see a file?

You just have to look in to your cofiguration file (which is present in log itself) to see which location is being used for Scratch and the file will be there.

ora.2714.131128.1.log file will have reason why the record got rejected or discarded.

An to see the data discarded look in to ora.2714.131128.1.log.bad file.

Posted: Thu Dec 10, 2009 11:28 am
by rupeshg
priyadarshikunal wrote:Why you need root priviledge to find and see a file?
Locating a file through a FIND command is easier with ROOT login as it does not give you error on Directories that you don't have access to, while searching the file with your user login.

Comment was more specific on searching and locating the file.

Posted: Thu Dec 10, 2009 1:23 pm
by chulett
Still... there's no reason to go find it as the location is well known - your scratch area specified in the job's config file.

Posted: Thu Dec 10, 2009 3:56 pm
by ray.wurlod

Code: Select all

find [ options ] 2>/dev/null

Posted: Fri Dec 11, 2009 3:58 am
by Sainath.Srinivasan
Rather than going through find, wouldn't it be easier to go few lines up in the datastage log to locate the configuration file and its scratch directories ? :roll:

Posted: Fri Dec 11, 2009 2:23 pm
by ray.wurlod
Maybe, but you can go and get a cup of tea while find is running. :wink: