Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase. |
Search for | Operator | Example |
---|---|---|
Two or more words in the same topic |
|
|
Either word in a topic |
|
|
Topics that do not contain a specific word or phrase |
|
|
Topics that contain one string and do not contain another | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- System performance parameters
- Startup parameter: agstackl
- Startup parameter: arraysizelimit
- Parameter: attachmentsegmentsize
- Parameter: memorypollinterval
- Startup parameter: anubisPollInterval
- Startup parameter: cache_clean_interval
- Startup parameter: cache_locks
- Startup parameter: cache_slots
- Startup parameter: dao_sessiontimeout
- Startup parameter: dao_threadsperprocess
- Startup parameter: dashboardquerycache_enable
- Startup parameter: dashboardquerycache_dbtime
- Startup parameter: dashboardquerycache_expire
- Startup parameter: dashboardonreplicatedb
- Special parameters: detectkeyed
- Startup parameter: enableAnubisMonitor
- Parameter: gcthreshold
- Startup parameter: KMSearchEngineTimeout
- Startup parameter: maxgroupsperview
- Startup parameter: maxhttpreqresponse
- Startup parameter: maxKeepAliveRequests
- Startup parameter: maxloginspercluster
- Startup parameter: maxmemoryperthread
- Startup parameter: maxmsgsharedmemory
- Startup parameter: maxpagesize
- Startup parameter: memdebug
- Startup parameter: precision
- Startup parameter: recordlistcount
- Parameter: semaphoreWaitTime
- Startup parameter: shared_memory
- Startup parameter: shared_memory_address
- Startup parameter: shutipc
- Startup parameter: tmpdirectory
- Startup parameter: unlockdatabase
- Startup parameter: usealtsignalstack
- Startup parameter: usemembar
- Parameter: vj_record_limit
- Parameter: vj_record_warning
Startup parameter: shared_memory_address
Startup parameters change the behavior of the HPE Service Manager server. You can always set a startup parameter from the server's operating system command prompt.
Note You should only use this parameter when instructed to do so by HPE Customer Support.
Parameter
shared_memory_address
Description
This parameter can be used on all operating systems to ensure that shared memory allocation is kept in an area that will not interfere with shared libraries, stacks, heaps or other memory related data structures. You can use this parameter to specify a new address that has enough contiguous memory for the HPE Service Manager process.
If you encounter a shared memory allocation failure, the address that the HPE Service Manager process is using does not have enough contiguous memory. On Windows, the sm.log file lists recommendations for possible shared_memory_address parameter values. If the debugvmmap parameter is active, the log also contains a map of virtual memory at the time of the failure.
Valid if set from
Server's operating system command prompt
Initialization file (sm.ini)
Requires restart of the Service Manager server?
Yes
Default value
On Solaris: 0xA0000000
On Linux: 0x50000000
On Windows: Dynamically determined
Possible values
A memory address in a decimal, hexadecimal, or octal format.
Example usage
Command line: sm -httpPort:13080 -shared_memory_address:0x80000000
Initialization file: shared_memory_address:0x80000000
Example sm.log file that is generated when you encounter a shared memory allocation failure
6116( 2716) 03/05/2010 11:06:41 RTE E shmat: MapViewOfFileEx failed 6116( 2716) 03/05/2010 11:06:41 RTE E Error 487 in call MapViewOfFileEx - Attempt to access invalid address. 6116( 2716) 03/05/2010 11:06:41 RTE E sm_init: shmat( 516, 0x73000000, 0 ) failed for size 67108864 and key 0x2A02E500 6116( 2716) 03/05/2010 11:06:41 RTE I List of possible shared_memory_address parameter settings for a shared memory size of 67108864 (64 MB) 6116( 2716) 03/05/2010 11:06:41 RTE I # Free range 0x7FFF0000-0xFFFAD000 size=2147209216 (2047 MB) 6116( 2716) 03/05/2010 11:06:41 RTE I Preferred : shared_memory_address:0x80000000 6116( 2716) 03/05/2010 11:06:41 RTE I Lowest available : shared_memory_address:0x80000000 6116( 2716) 03/05/2010 11:06:41 RTE I Highest available: shared_memory_address:0xFBFA0000 6116( 2716) 03/05/2010 11:06:41 RTE I For a complete list of available shared_mempory_address settings, run with the debugvmmap parameter. 6116( 2716) 03/05/2010 11:06:41 RTE W !!! Use the preferred shared_memory_address parameter above 6116( 2716) 03/05/2010 11:06:41 RTE W !!! or remove the shared_memory_address parameter completely. 6116( 2716) 03/05/2010 11:06:41 RTE E HPE Service Manager is unable to start. Failed to initialize or attach to shared memory environment
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to ovdoc-ITSM@hp.com.
Help Topic ID:
Product:
Topic Title:
Feedback: