This content has been marked as final. Show 6 replies
If you set max_dump_file_size=10000. without any suffix(M or K)
This represents 10000 x block_size of ur server, e.g block_size for solaris=512bytes
If u really wanted to specify 10mb..
Then use the command below:
ALTER SYSTEM SET MAX_DUMP_FILE_SIZE='10M' scope=both;
The database is running on AIX and the jfs2 filesystem block size is 4096 bytes (block size: 4096).
4096 bytes = 4 kb
4 kb * 20000 = 80000 kb (=78MB)
and not 10MB.... there is something wrong...
We use the default block size of AIX JFS2 filesystems:
Thanks and Regards
The following options are specific to the Enhanced Journaled File System (JFS2):
The default block size is 4096 bytes
I got the same error as your. my max_dump_file_size is 10240 and i got the same message of *** DUMP FILE SIZE IS LIMITED TO 5242880 BYTES ***. I have AIX 5.3L aslo and my /oracleapps fs was created by jfs2, so its block is 4096 (you can check it in smit storage). So did you find out what went wrong on your system? There is a huge trc dump in the udump directory since I began my rman backup process. Did you solve it yet?
Consult Oracle Document if you are not sure,
Report Error if you believe it's wrong Or you are wrong.
You can set the size limit to kilobytes or megabytes instead of OS block number by putting K or M.
MAX_DUMP_FILE_SIZE specifies the maximum size of trace files (excluding the alert file). Change this limit if you are concerned that trace files may use too much space.
A numerical value for MAX_DUMP_FILE_SIZE specifies the maximum size in operating system blocks.
A number followed by a K or M suffix specifies the file size in kilobytes or megabytes.
The special value string UNLIMITED means that there is no upper limit on trace file size. Thus, dump files can be as large as the operating system permits.
if you dont specify a unit like M or K it uses the block size.
I have tested something around with the value and i got the following explanation. Oracle does not interpret the blocksize of the JFS2 filesystem as bytes - it seems like oracle is intepreting it as bits.
In my example i can calculate it to the correct dump size limit:
max_dump_file_size => 20000
And the limit of the dump file was by 10240000 bytes. So lets calculate
20000 x 4096 bits = 81920000 bits => 10240000 bytes :-)
and in your case:
10240 x 4096 bits = 41943040 bits => 5242880 bytes
As you can see if your are running oracle on AIX, it interprets the filesystem block size as bits - not as bytes as you created it or as AIX uses it. Some kind of weird but there is the explanation :)
I hope this helps...