To resolve the problem, run UDF in an unfenced mode or reduce database Shared memory set to no more than 5 segments.
要解决这个问题，可以在unfenced模式下运行udf，或者将数据库共享内存减少至不多于5个段。
Because no party needs to manage memory, buffer-size identification becomes unnecessary (hence there's no possibility of the multi-execution problem identified earlier).
由于没有哪一方需要管理内存，确定缓冲区的大小就变得不必要了(因而也不可能存在前面指出的多次执行问题)。
Creating 100,000 weightless threads is no problem on an older Windows 98 Pentium II laptop with only 64 MB of memory (at one million threads, long disk churning occurs).
在一台比较老的只有64MB内存的Windows 98Pentiumii膝上型电脑上创建100,000个轻便线程是轻而易举的(如果达到了一百万个线程，就会出现长时间的磁盘“猛转”)。
But the problem is that since our minds function on logic and memory, we are always trying to make connections where there are no connections to be made.
但是问题是自从我们的心灵拥有逻辑和记忆功能，我们总是试图连接那些没有联系的事物。
You should have no problem fitting all the DB2 memory sets into this address space.
将所有DB 2内存集放入这个地址空间应该没有问题。
Server Out Of MemoryThere is no memory on the server to run your program. Please contact your administrator with this problem.
服务器内存不足服务器上内存不足，无法运行您的程序。请与管理员联系，以解决此问题。
Server Out Of Memoryis no memory on the server to run your program. Please contact your administrator with this problem.
服务器内存不足服务器上内存不足，无法运行您的程序。请与管理员联系，以解决此问题。
The proposed structure circumvents this problem by creating non-volatile memory cells from standard CMOS transistors. Thus, no additional masking or processing steps are necessary.
这里提出的结构解决了这个问题，它利用标准CMOS晶体管来实现非易失性存储器，这样就不需要额外的掩膜或工艺步骤。
Is equivalent to a number of threads at the same time on a map data changes, there will be no memory conflict, what is the hidden problem?
难道就只有我一个觉得不会出错么？多线程修改数据只要不是同一个地方并不需要锁，楼主只要关键不变不增不减取出值修改应该是没问题的。
Is equivalent to a number of threads at the same time on a map data changes, there will be no memory conflict, what is the hidden problem?
难道就只有我一个觉得不会出错么？多线程修改数据只要不是同一个地方并不需要锁，楼主只要关键不变不增不减取出值修改应该是没问题的。
应用推荐