file too large ulimit exceeded

[Omar Alvi_1]

Hi,

We have a customer having the Baan software installed upon Oracle. Baan is similar to SAP.

When the customer copies (using the Baan GUI) the oracle tablespaces and data to a flat file, he gets the error "file too large, check ulimit" in a Baan logfile. By the time this error message appears 2.1 GB has already been copied.

largefiles setting for the vxfs filesystem as well as in /etc/fstab are fine.

ulimit values for user root are as follows

/baan/bse/patches root (K) > ulimit -a
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 1048576
stack(kbytes) 204800
memory(kbytes) unlimited
coredump(blocks) 4194303
nofiles(descriptors) 1024

Apart from this copying largefiles using Unix commands within the filesysatems and to tape is successful. So effectively extracting from databse file to flat file is causing the error.

There's one unrelated query regarding ulimit. Tghe man page states nothing about its usage ... man page shows it as a system call. Where do we get info on ulimit (the command's) functionality and usage.

Thanks and Regards,

Omar Alvi

[Umapathy S]

Omar,
You can change ulimit for sh-posix shells. For ksh you cannot change it. ulimit is the shell intrinsic command. Check man page of sh-posix for ulimit details.

HTH,
Umapathy

[Steven E. Protter]

Whats the shell for the user running the script?

echo $SHELL

Don't change it without checking with the application vendor.

You might be able to merely change the shell in the script and then use ulimit as noted in the prior post.

SEP

[Tomek Gryszkiewicz]

I understand that this application is running as root user? If no, check ulimit for specified user.

-Tomek

[Massimo Bianchi]

Hi,
i would check the following:

- the shell: only posix sh and csh really and fully supports large files

- the executable: what is baan using to copy the files ? for example, the unix command cp does not work with largefiles

- the fs options: is largefiles enabled ? triple check, even if you say that is OK!

- the exp from oracle is limited to 2G, if that's the case you must use a pipe

"So effectively extracting from databse file to flat file is causing the error." leads to previous consideration......

Massimo

[A. Clay Stephenson]

I suspect that this is actually a limit imposed by the application itself. It may not have been written to take advantage of largefiles. You can probably "out-bushwhack" it by using a named pipe.


mknod /tmp/mypipe p
Now start your dump but use /tmp/mypipe as the output file. It will block until the next step is done.

In another window, cat < /tmp/mypipe > myoutputfile.