Sponsored Content
Operating Systems Solaris Where is my memory? How to fix it ? Post 303037773 by gull04 on Tuesday 13th of August 2019 08:29:52 AM
Old 08-13-2019
Hi,

I'm not really a great fan of trying things out on production servers, it always seems to come back and bite you from an other direction. If your environment is anything like most of the ones I have worked in over the years, test and development machines seem to be scarce and if they exist - getting testing resource is like finding a winning lottery ticket.

It's a difficult call for me, I don't know anything about your environment other than you are using Solaris 11.2, one server has 36Gb of memory, the other has 16Gb of memory and they could be whole root zones. And of course the fact that both servers are reporting almost 90% memory utilisation which will trigger an alert.

Much of this is going to come down to a few things here;
  1. Can you do this on a Test/Dev sever?
  2. Does going ove 90% memory utilisation cause a problem with the application.
  3. Can you live with the alert generated at the 90% threshold, can it be ignored or the threshold changed.
  4. Do you have to try this change in a production environment, if there are problems whats the regression?
  5. How critical is the production server, if it's critical could you test on the DR server?
  6. Will your boss back you up if you take the iteritive approach and set "user_reserve_hint_pct" to 60% as Oracle suggest.

I know the above isn't overly helpful, but asking someone with no experience of the environment in which you work just opens up many more questions than can't be easilly answered in a forum such as this.

My preferred approach to this would be to run an explorer over the system and raise a support ticket (case) with Oracle support, in the ticket you should cite your concerns - please be aware that Oracle may well come back and suggest things like the patching is brought up to date for the systems.

Regards

Gull04

Last edited by gull04; 08-13-2019 at 09:37 AM.. Reason: Can't Spell
This User Gave Thanks to gull04 For This Post:
 

9 More Discussions You Might Find Interesting

1. Programming

how to round up a memory address(memory alignment problem)

Hi, I try to marshal a unsigned int and a char * into a buffer, and then unmarshal them later to get them out. I need to put the char * in the front and unsigned int at the end of the buffer. However, my system always give me "BUS ERROR". I am using Sun Sparcs Sloris 2.10. My code to marshal... (6 Replies)
Discussion started by: nj302
6 Replies

2. HP-UX

How can I get memory usage or anything that show memory used from sar file?

Refer from title: How can i get memory used or anything that can show memory from sar file example on solaris:- we can use sar with option to show memory used at time that sar crontab run. on HP-UX, it not has option to see memory used. But i think it may be have some parameter or some... (1 Reply)
Discussion started by: panithat
1 Replies

3. AIX

ulimits max locked memory virtual memory

Hi, Would any one be so kind to explain me : are ulimits defined for each user seperately ? When ? Specialy what is the impact of : max locked memory and virtual memory on performance of applications for a user. Many thanks. PS : this is what I can see in MAN : ulimit ] ... (5 Replies)
Discussion started by: big123456
5 Replies

4. Solaris

How to find Total and Free Physical Memory and Logical Memory in SOLARIS 9

Hi, Im working on Solaris 9 on SPARC-32 bit running on an Ultra-80, and I have to find out the following:- 1. Total Physical Memory in the system(total RAM). 2. Available Physical Memory(i.e. RAM Usage) 3. Total (Logical) Memory in the system 4. Available (Logical) Memory. I know... (4 Replies)
Discussion started by: 0ktalmagik
4 Replies

5. Programming

How to deal with lots of data in memory in order not to run out of memory

Hi, I'm trying to learn how to manage memory when I have to deal with lots of data. Basically I'm indexing a huge file (5GB, but it can be bigger), by creating tables that holds offset <-> startOfSomeData information. Currently I'm mapping the whole file at once (yep!) but of course the... (1 Reply)
Discussion started by: emitrax
1 Replies

6. Solaris

restrcit physical memory with zone.max-locked-memory

Is it possible to restrict physical memory in solaris zone with zone.max-locked-memory just like we can do with rcapd ? I do not want to used rcapd (1 Reply)
Discussion started by: fugitive
1 Replies

7. UNIX for Advanced & Expert Users

Out of Memory error when free memory size is large

I was running a program and it stopped and showed "Out of Memory!". at that time, the RAM used by this process is around 4G and the free memory size of the machine is around 30G. Does anybody know what maybe the reason? this program is written with Perl. the OS of the machine is Solaris U8. And I... (1 Reply)
Discussion started by: lilili07
1 Replies

8. Solaris

relationship or difference between entitled memory and locked memory

Hello solaris experts, Being new to solaris containers, from Linux, feeling difficulty in understanding certain concepts. Hope somebody can help me here. I understand that, & some questions .... Locked memory -- memory which will not be swapped out at any cause. is this for... (0 Replies)
Discussion started by: thegeek
0 Replies

9. Solaris

[DOUBT] Memory high in idle process on Solaris 10 (Memory Utilization > 90%)

Hi Experts, Our servers running Solaris 10 with SAP Application. The memory utilization always >90%, but the process on SAP is too less even nothing. Why memory utilization on solaris always looks high? I have statement about memory on solaris, is this true: Memory in solaris is used for... (4 Replies)
Discussion started by: edydsuranta
4 Replies
KINIT(1)						      General Commands Manual							  KINIT(1)

NAME
kinit - obtain and cache Kerberos ticket-granting ticket SYNOPSIS
kinit [-5] [-4] [-V] [-l lifetime] [-s start_time] [-r renewable_life] [-p | -P] [-f | -F] [-A] [-v] [-R] [-k [-t keytab_file]] [-c cache_name] [-S service_name] [principal] DESCRIPTION
kinit obtains and caches an initial ticket-granting ticket for principal.Thetypicaldefaultbehavioristoacquireonly Kerberos 5 tickets. How- ever, if kinit was built with both Kerberos 4 support and with the default behavior of acquiring both types of tickets, it will try to acquire both Kerberos 5 and Kerberos 4 by default. Any documentation particular to Kerberos 4 does not apply if Kerberos 4 support was not built into kinit. OPTIONS
-5 get Kerberos 5 tickets. This overrides whatever the default built-in behavior may be. This option may be used with -4 -4 get Kerberos 4 tickets. This overrides whatever the default built-in behavior may be. This option is only available if kinit was built with Kerberos 4 compatibility. This option may be used with -5 -V display verbose output. -l lifetime requests a ticket with the lifetime lifetime. The value for lifetime must be followed immediately by one of the following delim- iters: s seconds m minutes h hours d days as in "kinit -l 90m". You cannot mix units; a value of `3h30m' will result in an error. If the -l option is not specified, the default ticket lifetime (configured by each site) is used. Specifying a ticket lifetime longer than the maximum ticket lifetime (configured by each site) results in a ticket with the maximum lifetime. -s start_time requests a postdated ticket, valid starting at start_time. Postdated tickets are issued with the invalid flag set, and need to be fed back to the kdc before use. (Not applicable to Kerberos 4.) -r renewable_life requests renewable tickets, with a total lifetime of renewable_life. The duration is in the same format as the -l option, with the same delimiters. (Not applicable to Kerberos 4.) -f request forwardable tickets. (Not applicable to Kerberos 4.) -F do not request forwardable tickets. (Not applicable to Kerberos 4.) -p request proxiable tickets. (Not applicable to Kerberos 4.) -P do not request proxiable tickets. (Not applicable to Kerberos 4.) -A request address-less tickets. (Not applicable to Kerberos 4.) -v requests that the ticket granting ticket in the cache (with the invalid flag set) be passed to the kdc for validation. If the ticket is within its requested time range, the cache is replaced with the validated ticket. (Not applicable to Kerberos 4.) -R requests renewal of the ticket-granting ticket. Note that an expired ticket cannot be renewed, even if the ticket is still within its renewable life. When using this option with Kerberos 4, the kdc must support Kerberos 5 to Kerberos 4 ticket conversion. -k [-t keytab_file] requests a host ticket, obtained from a key in the local host's keytab file. The name and location of the keytab file may be speci- fied with the -t keytab_file option; otherwise the default name and location will be used. When using this option with Kerberos 4, the kdc must support Kerberos 5 to Kerberos 4 ticket conversion. -c cache_name use cache_name as the Kerberos 5 credentials (ticket) cache name and location; if this option is not used, the default cache name and location are used. The default credentials cache may vary between systems. If the KRB5CCNAME environment variable is set, its value is used to name the default ticket cache. Any existing contents of the cache are destroyed by kinit. (Note: The default name for Kerberos 4 comes from the KRBTKFILE environment variable. This option does not apply to Kerberos 4.) -S service_name specify an alternate service name to use when getting initial tickets. (Applicable to Kerberos 5 or if using both Kerberos 5 and Kerberos 4 with a kdc that supports Kerberos 5 to Kerberos 4 ticket conversion.) ENVIRONMENT
Kinit uses the following environment variables: KRB5CCNAME Location of the Kerberos 5 credentials (ticket) cache. KRBTKFILE Filename of the Kerberos 4 credentials (ticket) cache. FILES
/tmp/krb5cc_[uid] default location of Kerberos 5 credentials cache ([uid] is the decimal UID of the user). /tmp/tkt[uid] default location of Kerberos 4 credentials cache ([uid] is the decimal UID of the user). /etc/krb5.keytab default location for the local host's keytab file. SEE ALSO
klist(1), kdestroy(1), krb5(3) KINIT(1)
All times are GMT -4. The time now is 09:09 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy