cancel
Showing results for 
Search instead for 
Did you mean: 

Failure to Export Database

SOLVED
Go to solution
Charles Walton_1
Occasional Visitor

Failure to Export Database

Our DBA reported a problem when he tries to export the databases.

/usr/lib/dld.sl: Call to mmap() failed - TEXT /Oracle/software/8.1.6/lib//libclntsh.sl.8.0
/usr/lib/dld.sl: Not enough space

# swapinfo -ta
Kb Kb Kb PCT START/ Kb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 4194304 0 4194304 0% 0 - 1 /dev/vg00/lvol2
reserve - 2547616 -2547616
memory 6500884 3339280 3161604 51%
total 10695188 5886896 4808292 55% - 0 -
1
7 REPLIES
Helen French
Honored Contributor

Re: Failure to Export Database

This thread may help you:

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xae318f960573d611abdb0090277a778c,00.html

Also do a "search" on the old threads, you will find out a solution !

Life is a promise, fulfill it!
A. Clay Stephenson
Acclaimed Contributor

Re: Failure to Export Database

This is caused by two things: 1) out of swapspace (not in this case) 2) maxdsiz (or maxdsiz_64bit) limit reached - increase and gen a new kernel.
If it ain't broke, I can fix that.
PIYUSH D. PATEL
Honored Contributor

Re: Failure to Export Database

Hi,

The space this error message is referring to is memory. There is no memory available on the system to export the database.

You may have to increase the size of maxdsiz kernel parameter.

Piyush



Charles Walton_1
Occasional Visitor

Re: Failure to Export Database

Thanks for the fast replies, Currently Oracle is running 32bit & the maxdsiz value = 16384 w/ a min-max of 0-655360. Any recommendations on what we should set this to?
1
A. Clay Stephenson
Acclaimed Contributor
Solution

Re: Failure to Export Database

Sysdef displays in 4k pages so that you are current set to 64MB; that is generally a small value. I suggest that 512MB is generous but still leaves a decent value to keep the wild horses in the corral. I would not exceed 1GB in the 32bit world as a general rule.

This value consumes no resources but is intended to act as a safety valve to prevent a process from grabbing all the resources and bringing a box to its knees.

If it ain't broke, I can fix that.
Kawah Cheung
Advisor

Re: Failure to Export Database

Hi,
I may be putting the cat among the pigeons here, but could we be barking up the wrong tree. Picked up an oracle case with the exact problems you are getting and the oracle recommendation was to relink all the oracle binaries. Worth a try? See attached file.

Kind Regards,
Kawah
If in doubt, ask!
Brian Crabtree
Honored Contributor

Re: Failure to Export Database

In this case, it is the memory that is the problem. Relinking can help in some cases, but in this case, you need to have the correct sizes in the kernel. The following kernel parameters should be set (values I normally used are attached)

maxdsiz 1g = 0x40000000
maxsize 200m = 0xC000000
maxtsiz 1g = 0x40000000
shmmax 1g = 0x40000000

These set them all to 1g. Oracle 32bit can go to 4g total SGA, and 64bit can go to +1 terabyte. Overkill on these will not hurt you, however you should still monitor the application and sessions still.

Brian