Sponsored Content
Full Discussion: UNIX memory problems
Operating Systems HP-UX UNIX memory problems Post 302150761 by denn on Wednesday 12th of December 2007 01:24:45 PM
Old 12-12-2007
You said it wasn't a swap space issue, but as Perderabo suggested take another close look at that, and if you have more than one swap space, there's no real guarantee which one will be selected at any point in time.

The first issue, can't fork, almost sounds like you need to do some kernel tweeking. The database owners should be able to give you some ballpark kernel settings, however thats all dependant of DB size, how much/how often updates, queries take place for your installation; however they should be able to give you some min. settings. If you've not already tweeked these, max_thread_count might be a place to look, however there are many other paramaters worth looking at. Doing in a production envoriment is not ideal. Definately document well, what your original setting were, and exactly what was changed. Best done with someone with some experience with kernel tuning.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

plock() memory locking problems

I'm experiencing some strangeness when using plock(). I'm on a Solaris 5.7/SPARC machine with 64MB of memory. I can show that plock() works by successfully locking down 10 MB of memory. Then, I ask for 40 MB, and I get a failure notice because there is "Not enough memory" available. I... (5 Replies)
Discussion started by: troccola
5 Replies

2. UNIX for Advanced & Expert Users

Program/ Memory Problems

I need some advise. I have an application server running several applications. When I try and start a particular application when the others are running I receive the following. This is appearing in the core file that is created. ... (1 Reply)
Discussion started by: dbrundrett
1 Replies

3. UNIX and Linux Applications

UNIX memory problems w/Progress DB

We are currently running HP-UX 11 as our database server. The database is Progress version 9.1C. As of late, some of our batch processes that run on the UNIX db server are erroring out because of what appear to be memory issues(at least according to Progress). The db error messages indicate... (0 Replies)
Discussion started by: eddiej
0 Replies

4. Programming

[C] Problems with shared memory

Hi everbody, i have a problem with shared memory and child-processes in C (unix). I have a server that do forks to create (N) child processes. This processes work with a shared "stuct" thanks to shared memory and a semaphore. The problem is when a child modify the shared memory and the others... (2 Replies)
Discussion started by: hurricane86
2 Replies

5. Programming

Problems with shared memory and lists

Hi, I need to put in shared memory a list made with object of this structure: typedef struct Obj{ char objname; struct Obj *nextObj; }Object I've filled my list with (for example) 10 elements, but when i try to put it in shared memory to be read by another process i get segmentation fault... (6 Replies)
Discussion started by: BeNdErR
6 Replies

6. Solaris

Memory problems on a -sunfire T2000

I work with a network management tool, which, for various reasons, is installed on a solaris server.This is a Sunfire T2000 server with 16 CPUs and 8GB of RAM. I have installed a Solaris 10 ZFS and 8GB swap. From the beginning I had problems with memory occupation that it rises progressively to 95%... (4 Replies)
Discussion started by: drusa79
4 Replies

7. Shell Programming and Scripting

A bad configured logrotate can cause a problems with memory leak ?

I am newbe to unix. I have a very serious problem on my server. I have a java application running, and all day on Monday morning, the process that is associated with this java is locked. Usually I doing a shutdown by the shutdown java command , you have to kill the process with the kill-kill... (1 Reply)
Discussion started by: jjoottaa
1 Replies

8. Red Hat

Memory problems in NFS client server

Hi all, i have some doubts in a situation that i fail to get an answer in Google. I have a solaris 10 nfs server and 5 centos 6.0 nfs clients. The problem/situation is that in the clients the free memory is "disappearing" along the time (passing to used)..and it gets free if i umount the... (5 Replies)
Discussion started by: blast
5 Replies

9. Solaris

Memory problems in Blade 6340

We have a 6000 chassis with three blades in it. Two of the blades have "Oracle/Sun" memory in them with no complaints. The third blade is populated with Dataram dimms. That 3rd blade continues to flag a slot bad. Oracle has said they would not support the blade with Dataram memory it it. I didn't... (1 Reply)
Discussion started by: brownwrap
1 Replies

10. AIX

Memory problems.

Hi All, Just loaded AIX 6.1 and then got Firefox running on the workstation. To test out I wanted to download some small files from 'Perlz', and during this I'm told there's not enough room in the Downloads folder. What do I do to resize folders from the default and generally move memory around? In... (3 Replies)
Discussion started by: Box_the_Jack_in
3 Replies
MKSWAP(8)                                                      System Administration                                                     MKSWAP(8)

NAME
mkswap - set up a Linux swap area SYNOPSIS
mkswap [options] device [size] DESCRIPTION
mkswap sets up a Linux swap area on a device or in a file. The device argument will usually be a disk partition (something like /dev/sdb7) but can also be a file. The Linux kernel does not look at partition IDs, but many installation scripts will assume that partitions of hex type 82 (LINUX_SWAP) are meant to be swap partitions. (Warning: Solaris also uses this type. Be careful not to kill your Solaris partitions.) The size parameter is superfluous but retained for backwards compatibility. (It specifies the desired size of the swap area in 1024-byte blocks. mkswap will use the entire partition or file if it is omitted. Specifying it is unwise - a typo may destroy your disk.) After creating the swap area, you need the swapon command to start using it. Usually swap areas are listed in /etc/fstab so that they can be taken into use at boot time by a swapon -a command in some boot script. WARNING
The swap header does not touch the first block. A boot loader or disk label can be there, but it is not a recommended setup. The recom- mended setup is to use a separate partition for a Linux swap area. mkswap, like many others mkfs-like utils, erases the first partition block to make any previous filesystem invisible. However, mkswap refuses to erase the first block on a device with a disk label (SUN, BSD, ...). OPTIONS
-c, --check Check the device (if it is a block device) for bad blocks before creating the swap area. If any bad blocks are found, the count is printed. -f, --force Go ahead even if the command is stupid. This allows the creation of a swap area larger than the file or partition it resides on. Also, without this option, mkswap will refuse to erase the first block on a device with a partition table. -L, --label label Specify a label for the device, to allow swapon by label. -p, --pagesize size Specify the page size (in bytes) to use. This option is usually unnecessary; mkswap reads the size from the kernel. -U, --uuid UUID Specify the UUID to use. The default is to generate a UUID. -v, --swapversion 1 Specify the swap-space version. (This option is currently pointless, as the old -v 0 option has become obsolete and now only -v 1 is supported. The kernel has not supported v0 swap-space format since 2.5.22 (June 2002). The new version v1 is supported since 2.1.117 (August 1998).) -h, --help Display help text and exit. -V, --version Display version information and exit. NOTES
The maximum useful size of a swap area depends on the architecture and the kernel version. The maximum number of the pages that is possible to address by swap area header is 4294967295 (UINT_MAX). The remaining space on the swap device is ignored. Presently, Linux allows 32 swap areas. The areas in use can be seen in the file /proc/swaps mkswap refuses areas smaller than 10 pages. If you don't know the page size that your machine uses, you may be able to look it up with "cat /proc/cpuinfo" (or you may not - the con- tents of this file depend on architecture and kernel version). To set up a swap file, it is necessary to create that file before initializing it with mkswap, e.g. using a command like # fallocate --length 8GiB swapfile Note that a swap file must not contain any holes. Using cp(1) to create the file is not acceptable. Neither is use of fallocate(1) on file systems that support preallocated files, such as XFS or ext4, or on copy-on-write filesystems like btrfs. It is recommended to use dd(1) and /dev/zero in these cases. Please read notes from swapon(8) before adding a swap file to copy-on-write filesystems. ENVIRONMENT
LIBBLKID_DEBUG=all enables libblkid debug output. SEE ALSO
fdisk(8), swapon(8) AVAILABILITY
The mkswap command is part of the util-linux package and is available from https://www.kernel.org/pub/linux/utils/util-linux/. util-linux March 2009 MKSWAP(8)
All times are GMT -4. The time now is 07:23 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy