Service Pack 06 на OpenEdge 10.2B
Service Pack 06 на OpenEdge 10.2B
Сервис-пак 10.2B06 доступен для скачивания в Download Center.
Из PROGRESS_OE_10_2B06_READMESP.txt
The LRU skip parameters allow you to specify the number of times a buffer in the buffer pool is accessed before it is placed on the Most Recently Used (MRU) end of the LRU chain. Accessing a buffer a specified number of times eliminates the need to acquire the LRU latch each time a buffer is accessed.
Очень интересная идея - может оказаться полезной опцией.
New startup parameter -IOEverywhere
---------------------------------
Until now, ABL has had a restriction on where an input-blocking statement (UPDATE, SET, PROMPT-FOR, CHOOSE, INSERT, WAIT-FOR, READKEY, or PROCESS EVENTS) could be used. For example, you could not use an input-blocking statement in a user-defined function or a non-void method. There were also some other places with this restriction, like class destructors and some database trigger blocks.
Now, there is a new startup parameter: -IOEverywhere <n> where <n> is either 0 or 1. For service packs of Release 10.2B, the default is 0, which means the new feature is off and everything works as before. But if you specify - IOEverywhere 1, then you will be able to use input-blocking statements in almost every context.
The LRU skip parameters allow you to specify the number of times a buffer in the buffer pool is accessed before it is placed on the Most Recently Used (MRU) end of the LRU chain. Accessing a buffer a specified number of times eliminates the need to acquire the LRU latch each time a buffer is accessed.
Очень интересная идея - может оказаться полезной опцией.
New startup parameter -IOEverywhere
---------------------------------
Until now, ABL has had a restriction on where an input-blocking statement (UPDATE, SET, PROMPT-FOR, CHOOSE, INSERT, WAIT-FOR, READKEY, or PROCESS EVENTS) could be used. For example, you could not use an input-blocking statement in a user-defined function or a non-void method. There were also some other places with this restriction, like class destructors and some database trigger blocks.
Now, there is a new startup parameter: -IOEverywhere <n> where <n> is either 0 or 1. For service packs of Release 10.2B, the default is 0, which means the new feature is off and everything works as before. But if you specify - IOEverywhere 1, then you will be able to use input-blocking statements in almost every context.
Выяснил, что всё время ходил по тонкому льду с idxbuild
Defect OE00219703
Idxbuild fails with error 49
idxbuild run on index area using area [areaname] -i -SG 64 -T [path] -TB 64 -TM 32 -B 256 -rusage -datascanthreads 4 -mergethreads 4
Full stack trace from _proutil on AIX reads:
upsGetInMemoryBlock
upsGetBlockNonSeq
upsWriteNonSeq
upsOutEntry2
Cause
The exact cause is not known at this time.
Resolution
None at this time.
Вы там поосторожнее, хотя пишут, что All Supported Operating Systems &
OpenEdge 10.2B06
Мало того, что idxcompact стремно запускать , так еще и тут подарок )))
Defect OE00219703
Idxbuild fails with error 49
idxbuild run on index area using area [areaname] -i -SG 64 -T [path] -TB 64 -TM 32 -B 256 -rusage -datascanthreads 4 -mergethreads 4
Full stack trace from _proutil on AIX reads:
upsGetInMemoryBlock
upsGetBlockNonSeq
upsWriteNonSeq
upsOutEntry2
Cause
The exact cause is not known at this time.
Resolution
None at this time.
Вы там поосторожнее, хотя пишут, что All Supported Operating Systems &
OpenEdge 10.2B06
Мало того, что idxcompact стремно запускать , так еще и тут подарок )))