The next step was to migrate my existing dedicated-memory LPARs to shared-memory LPARs.
下一步是把现有的专有内存LPAR迁移到共享内存 LPAR。
To remove shared-memory segments, use: ipcrm [ -m SharedMemoryID ] [ -M SharedMemoryKey ].
使用ipcrm [ -mSharedMemoryID ] [ -MSharedMemoryKey ]删除共享内存段。
Buffers specifies the maximum number of shared-memory buffers; locks specifies the maximum number of locks available for user sessions.
BUFFERS指定共享内存缓冲区的最大数目；LOCKS指定用户会话可以使用的锁的最大数目。
The shared-memory header contains a description of all other structures in Shared memory, including internal tables and the buffer pool.
共享内存头包含共享内存中所有其他结构的描述，包括内部表和缓冲池。
The purpose and function of those internal tables is to keep track of shared-memory resources status and usage such as buffers, chunks, dbspaces, transactions and so on.
那些内部表的目的和功能是为了记录共享内存资源的状态和使用，例如缓冲区、块、dbspace、事务等。
Inter processor communications or messages portion is allocated during IDS initialization if you configure at least one of your connections as an IPC shared-memory connection.
如果您至少将一个连接配置为IPC共享内存连接，那么在初始化ids时将分配处理器间的通信或消息区。
The size of this portion is pretty small and can be calculated using 12 kilobytes multiplied by the expected number of connections needed for shared-memory communications (NETTYPE ipcshm).
该区的尺寸相当小，可用12kb乘以共享内存通信(NETTYPEipcshm)所需的预期连接数目来计算该尺寸。
Shared-memory header is created when IDS is initialized and can not be tuned.
共享内存头是在初始化IDS时创建的，并且不能进行调优。
Shared memory provides the fastest method of interprocess communication, because it processes read and write messages at the speed of memory transfers.
共享内存提供了最快的进程间通信方法，因为它以内存传输的速度来处理读写消息。
This article explains instance Shared memory and database Shared memory.
本文将介绍实例共享内存和数据库共享内存。
The instance Shared memory and database Shared memory combined is around 3.7gb.
实例共享内存和数据库共享内存合起来大约是3.7GB。
So far we have discussed the instance Shared memory, the database Shared memory, the application group Shared memory and the agent private memory.
至此，我们已经讨论了实例共享内存、数据库共享内存和应用程序组共享内存以及代理私有内存。
This class stores the Shared memory identifier.
这个类存储共享内存标识符。
Application group Shared memory set is not listed because it is allocated from the database Shared memory set.
应用程序组共享内存集没有列出，因为它是从数据库共享内存集中分配的。
Shared memory: Read a primer on Shared memory and learn more about the various implementations available.
共享内存：阅读关于共享内存的基础教程，进一步了解各种实现。
The working storage pages for shared memory regions are not released until the shared memory region is deleted.
对于共享内存区域，直到删除共享内存区域之后，才会释放其工作存储分页。
There is one database Shared memory set per database.
每个数据库有一个数据库共享内存集。
Segment 3 - Reserved for instance Shared memory.
段3-预留给实例共享内存。
Note that the database Shared memory calculations show that we are still within available 1gb Shared memory limit.
注意，对数据库共享内存的计算表明，我们仍然没有超出1gb可用共享内存的限制。
Note this amount includes both the instance Shared memory and database Shared memory, and their memory segments must be contiguous.
注意这个数量同时还包括实例共享内存和数据库共享内存，并且它们的内存段必须是邻接的。
Its constructor creates the Shared memory and objects in it.
它的构造函数创建共享内存及其中的对象。
This is well under the 1.75gb Shared memory limit, and each database Shared memory segment can safely map contiguously to a quadrant.
这低于1.75GB的共享内存限制，并且每个数据库共享内存段可以安全地连续映射到一个象限。
The failover is transparent to the Shared memory partitions.
故障转移对于共享内存分区是透明的。
The LPARs are assigned "logical" shared memory.
给LPAR分配 “逻辑”共享内存。
Quadrant 4 (0.75gb) is reserved for Global Shared memory.
象限4 (0.75GB)被预留给全局共享内存。
Since the end address of the instance Shared memory is not fixed, the starting address for the database Shared memory is not fixed either.
因为实例共享内存的结束地址不固定，所以数据库共享内存的起始地址也是不固定的。
Quadrant 3 (1gb) is reserved for Global Shared memory.
象限3 (1gb)被预留给全局共享内存。
The Shared memory is not deleted when the process exits.
当主进程退出时，并不删除共享内存。
These Settings increase the amount of Shared memory to 32 MB.
这些设置把共享内存总量增加到了32 MB。
All three green segments are used for Shared memory, which includes both instance Shared memory and database Shared memory.
所有3个绿色的段被用于共享内存，包括实例共享内存和数据库共享内存。
应用推荐