Easily find issues by searching: #<Issue ID>
Example: #1832
Easily find members by searching in: <username>, <first name> and <last name>.
Example: Search smith, will return results smith and adamsmith
Operating Environment: Linux (3.19.0-15-generic, amd64) / UTF-8 / en / US / Oracle Corporation 1.8.0_102-b14
Memory: Max=704,643,072; Total=359,661,568; Free=218,370,256; CPUs=8
Connect DB2-LUW-10.1
Create buffer pool using below script.
CREATE BUFFERPOOL TEST_BUFFER IMMEDIATE
SIZE AUTOMATIC
PAGESIZE 4 K
GO
Go to Buffer pool tree-node
Right click on TEST_BUFFER and select script object to window as->CREATE
Selected buffer pool script generated on QA.
Actual Result:
- You can see that Buffer pool size is extracted in Created buffer pool script.
- Drop created TEST_BUFFER from buffer pool tree node.
- Again execute created "TEST_BUFFER" script
Displayed error message "An unexpected token "AUTOMATIC" was found following "R IMMEDIATE
SIZE -2". Expected tokens may include: "<space>".. SQLCODE=-104, SQLSTATE=42601, DRIVER=3.67.28 "
Expected Result:
Buffer pool size should be ignored when select "Enable self Tuning".
|
|
327 KB
| DB2-LUW-10.5/9.1/9.5/9.7/11.1/10.1 | ||
| Windows | Ubuntu | |
| ADS 18-Preview-60 | Y | Y |
| ADS v17(17.0.10) | Y | Y |
| ADS v16 | Y | Y |
| ADS v15 | Y | Y |
| ADS v14 | Y | Y |
|
Y:-Same issue we have seen. N:-This issue is not reproducible |
||
@ajinkya: if we don't address this in ADS v18, what impact would it have on schema sync?
@ajinkya: if we don't address this in ADS v18, what impact would it have on schema sync?
@sachin sir,
@ajinkya: if we don't address this in ADS v18, what impact would it have on schema sync?
In DB2 LUW, BUFFERPOOLS are used while creating tablespaces.
In schema synchronization we do not support deployment of tablespaces and BUFFERPOOLS. Hence the CREATE DDL for BUFFERPOOLS will never be generated through schema synchronization. This will not affect schema synchronization if we don't address this issue in V-18 or any future versions.
The thing is that when we enable 'self tuning', it is expected to script the SIZE of pool as 'AUTOMATIC' and in rest of the cases we should script the actual user provided value which is stored in _npages. I've gone through the ScriptBufferPool#scriptCREATE() and observed that we are always scripting the value of 'size' irrespective self tuning value.
I was not able to debug the codes in standalone environment.
theSelect.append("SIZE " + theBufferpool._nPages); <---- issue cause if (bEnableSelftuning) { theSelect.append(" AUTOMATIC"); }
@sachin sir,
@ajinkya: if we don't address this in ADS v18, what impact would it have on schema sync?
In DB2 LUW, BUFFERPOOLS are used while creating tablespaces.
In schema synchronization we do not support deployment of tablespaces and BUFFERPOOLS. Hence the CREATE DDL for BUFFERPOOLS will never be generated through schema synchronization. This will not affect schema synchronization if we don't address this issue in V-18 or any future versions.
The thing is that when we enable 'self tuning', it is expected to script the SIZE of pool as 'AUTOMATIC' and in rest of the cases we should script the actual user provided value which is stored in _npages. I've gone through the ScriptBufferPool#scriptCREATE() and observed that we are always scripting the value of 'size' irrespective self tuning value.
I was not able to debug the codes in standalone environment.
theSelect.append("SIZE " + theBufferpool._nPages); <---- issue cause if (bEnableSelftuning) { theSelect.append(" AUTOMATIC"); }
Issue #15010 |
| New |
Completion |
| No due date |
| No fixed build |
| No time estimate |
N:-This issue is not reproducible