All oracle database versions. Scripting of tablespace option blocksize is not always correctly stating the size. Extraction of the information from the database is coming back in bytes. In our GUI we are converting the bytes into kilobytes and then sending the object to script. In the scripting we are always forcing blocksize specification in kilobyte. We need to script the option in bytes and not convert bytes to kilo bytes in the GUI object.
Scripting will no longer use KiloBytes for blocksize, instead it will always use bytes.
Issue #12716 |
Closed |
Fixed |
Resolved |
Completion |
No due date |
Fixed Build 15.0.10-5 |
No time estimate |
Scripting will no longer use KiloBytes for blocksize, instead it will always use bytes.