FAQ's - APPX Software, Inc. : APPX Utility : APPX Runtime Environment : Other Runtime Questions :
What are the maximum file size(s) in APPX? | |
The maximum file size is dependent on the release of APPX and the operating system. The following chart shows the maximum file sizes allowed for each operating system based on the release level of APPX. Maximum file sizes by release Release Windows AIX Solaris HP/UX Linux ======= ======== ======= ======= ======= ======= 4.2 2 GB 4 GB 4 GB 4 GB 4 GB 4.1.a 2 GB 4 GB 4 GB 4 GB 2 GB 4.1 2 GB 4 GB 4 GB 2 GB 2 GB prior 1 GB 2 GB 2 GB 2 GB 2 GB | |
On AIX and some other Unix platforms, the OS can limit the maximum filesize a user can use, say to something like 1 gig. (1 gig = 1073741824 bytes, a number which came up when diagnosing this problem for one customer.)
Typing "ulimit -a" will tell you (in AIX) your user's current maximum filesize (in blocks). The maximum Appx record length is 32767 bytes, regardless of file type (AppxIO, Oracle, Sybase, ...). | |
A user's export of an Appx file stopped with: Mu.c.6842: "Main[] - cannot write port file - error - unknown appxio status".
The source file verified OK.
Only 41% of a 2+ gig filesystem was used. The Portdata file size was 1,073,740,936 bytes at the time of the error.
==> The problem was that the AIX operating system wouldn't allow files larger than 1 gig to be written to the file system. An OS parameter needed to be changed: the /etc/security/limits file, fsize parameter was set at 2097151. They changed it to -1 and the problem went away.
Prior to this change, executing the 'ulimit -a' command returned: time(seconds) unlimited file(blocks) 2097151 data(kbytes) 131072 stack(kbytes) 32768 memory(kbytes)32768 coredump(blocks) 2048 nofiles(descriptors) unlimitedAfter the change, 'ulimit -a' command returned: time(seconds) unlimited file(blocks) unlimited data(kbytes) 131072 stack(kbytes) 32768 memory(kbytes) 32768 coredump(blocks) 2048 nofiles(descriptors) unlimited
The value for file(blocks) is the limit on the file size in 512k blocks that can be written. After
the change the value is unlimited and the size of file that can be written is limited only by the
available disk space.
| |
The user changed their fsize limit, except that it was for the operating user, not for the appx User.
They changed the fsize limit to -1 for all appx users, and the problem went away.
| |
[Append to This Answer] | |
2005-Dec-27 9:03am |
Previous: | What is dynamic indexing? |
Next: | How to determining who has a file open (Unix OS). |
|