Oracle 7.3 - Oracle 23c 20+ years of experience Version (Released: )
18 Sep 2023
The visual appearance of KeepTool has been modernized. There are less visible lines cluttering the user interface.
The new Light Style rendering option allows you to display all supported controls without double or thick borders, extra outlines, and other visual noise. Light Style enables extra cell and header paddings, as well as lightweight borders in a control.
When Light Style has been disabled by unchecking the appropriate checkbox in Extras | Settings | Behavior, Data Grids look visually overloaded but fit more data.
You can now establish secure direct TCP/IP connections. In expanded view, the connect dialog now allows you to select a secure connection type:
Direct TCP/IP connection
The connect dialog establishes a regular direct TCP/IP connection without enhanced security.
Direct SSL connection
This is the recommended type in case a secure connection is needed.
Direct SSH connection
There is an entire new page for Oracle Rest Data Services (ORDS). You will find the appropriate button on the “Additional” sheet.
On the bottom of the page is an always-visible data grid for ORDS schemas. Here you can enable ORDS for your schema.
The main area contains the following tabs:
Overview ORDS Modules
ORDS Privileges and associated mappings, roles and modules
ORDS Roles and associated roles and web service mappings
ORDS Objects and members
Now displays the last file change timestamp in the header. Similar to the standalone SQL editor, it is displayed right of the file name.
Recently changed SQL files are now highlighted in green. As time goes by, the green tone fades to the regular white background in three steps.
It is same same logic that has been introduced to database objects in prior versions.
The settings | Other page has an option “Highlight recently changed database objects and SQL files” that controls this behavior.
The tree view displays a slightly changed icon for the currently selected item. It shows a pen in-front of the document symbol.
For large SQL scripts (+10K lines), the “Execute Script” menu item now allows you to optionally disable visual feedback and dbms_output logging.
in order to boost script execution performance.
On the tables overview grid, there is a new submenu item ‘Copy to clipboard | truncate statement.’
Similar to the already existing submenu items, it copies a TRUNCATE statement to the clipboard. The template provides some options in comments.
The modal dialog “Truncate table” has got a new “cascade” option.
On the Constraints tab, both menu items “Enable constraint” and “Disable constraint” have been enabled for multi-select.
There are two new context menu items for indexes. Both are enabled for multi-select:
Make Unusable – makes the index unusable. You may consider dropping indexes or at least switching them unusable before inserting mass data.
Rebuild Online – reverses the unusable operation.
Create INSERT script now creates bulk INSERT ALL statements. You can change the number of records collected into one statement in the settings dialog.
You can set bulk size to “1” to enforce the creation of traditional non-bulk statements.
INSERT scripts are now split in multiple files if the size exceeds a value that can be changed in the settings dialog.
INSERT scripts may use direct path operations, if the appropriate checkbox in the settings dialog has been enabled.
It adds the /*+append*/ hint to INSERT statements and a COMMIT after each.
Script file writing performance has been improved by using buffered streaming technology.
The new dialog “Flat detail data browser” is available from the context menu of the data contents grid.
It opens a tree view that contains the current table and all detail tables according to foreign key relations. Depending on your foreign key hierarchy, a table may appear on more than one node.
The root node shows the same data as the data content browser. It is a good idea to keep the amount of root data small.
You can go down the hierarchy of detail tables and display subordinate data in a flat view that bypasses foreign key relations, i.e. shows all subdetail data of the root node.
That means, you can see all detail data of a subordinate table in a flat view without grouping by master tables.
The main purpose is creating INSERT scripts from a master table and all relating detail tables.
Both Data Content and SQL query result grids as well as the record views show data type icons next to each field caption.
The PL/SQL call interface now lists procedure and function names in mixed case as defined in the source code rather than upper case as queried from the ALL_ARGUMENTS data dictionary view.
This feature can be disabled by unchecking the checkbox “Mixed case procedure names in PL/SQL call interface” on the Settings | Behavior tab.
New menu items “Compile” an “Rename”
The existing “Properties” menu item now drops and re-creates the synonym with changed properties.
Scheduler detail information is now displayed below the master grid rather than inplace.
This results in better performance and improves usability.
The database link properties dialog now gives you more space for entering data.
You can click the button next to the password field to copy the username into the password field. Nevertheless, in most cases this is not recommended for security reasons.
There is a new “Flags” tab on the settings dialog. It allows you to customize the captions of the color tags.
As you may remember, color tags can be assigned to several database objects using the image combo box in the overview data grid.
Data file grids on both tablespaces and database pages now display a percentile usage of the auto-extensible range, similar to the display on the tablespace overview grid.
In version 15, there have been two inplace detail grids within the Tablespace | datafiles grid. A “+” button on the left of each data row opened a detail level for showing information about free space fragmentation and segments stored in the datafile.
Now both detail grids are displayed below the datafiles grid, separated by a slider. Besides some SQL optimization, this results in a better overall performance.
Nevertheless, queries on both DBA_FREESPACE and DBA_EXTENTS dictionary views may be slow on some databases. Purging the recycle bin may help in some situations.
See Queries on DBA_FREE_SPACE are Slow (Doc ID 271169.1) for more information.
The “add datafile” dialog now comes up with new default values:
The filename is a copy of the currently selected datafile including ‘_new’ suffix.
Both ‘initial’ and ‘next’ size parameters are derived from the ‘next’ size of the currently selected datafile.
“Max’ size is assumed to be unlimited.
Sizes are displayed in GByte, if the size represents an integer Gigabyte value
The DDL for tablespace creation now contains the ‘MAXSIZE UNLIMITED’ clause if the size equals the actual maximum datafile size of your database
Unlimited datafile size is assumed for a maxsize of 4194302 * <db_block_size> in case of small data files and 4294967293 * <db_block_size> in case of big data files.
In a trailing comment, you still can see the appropriate numeric value.
You can see tablespace quota on three Hora pages in different contexts: Tablespaces | Utilization by User, Users | Tablespace utilization and Schema | Summary.
The display has been improved and unified as follows:
Quota and current usage are displayed together in one grid. The tab caption is now “Utilization by User” or “Tablespace utilization”, respectively
Unlimited quota is displayed as ‘UNLIMITED’ rather than the internal dictionary representation of ‘-1’
There is a new checkbox that indicates if the user has been granted the UNLIMITED TABLESPACE system privilege that allows bypassing any restrictions given by quota.
The Schema – Summary page now displays tablespace utilization and, if available, quota.
Prior Hora versions did not list tablespaces without quota, e.g. if the unlimited tablespace privilege was been used.
On the CDB page,
there is a new option to open a PDB in restricted mode,
The Create PDB dialog has got two new optional parameters:
PDB max size
The database page now displays the time zone file version from v$timestamp_file on a prominent place. This may help you to avoid ORA-39405: ‘Oracle Data Pump does not support importing from a source database with TSTZ version XX into a target database with TSTZ version YY.’ For more information, look at the DST_ prefixed database properties that are displayed in the data grid on the right.
The SGA page now
Shows component size info from V$SGA_INFO rather than V$SGA.
For backward compatibility, the prior information is still available on the last “deprecated” tab.
Unit of measurement has been changed to MBytes.
The ‘Default Roles’ dialog on the user’s page now evaluates SYS.USER$.DEFROLE and displays the result in a radio group with items NONE, ALL, and selection.
If you change default roles, the selected default roles will be applied if the radio group entry ‘selected’ is active.
For the remaining radio group items NONE and ALL the appropriate attribute will be passed to the ALTER USER statement.
In case the current user has no privileges to query SYS.USER$ table you must select a radio item on your own.
The setup installs Wibu CodeMeter runtime version 7.60c. It is strictly recommended to update the CodeMeter runtime, espacially on your network license server. Download the runtime setup from https://www.wibu.com/support/user/user-software.html . See also Wibu Security Advisories. The minimum allowed CodeMeter runtime version has been changed to 7.20.
KeepTool 220.127.116.11 updates Wibu CodeMeter runtime to version 7.60d that fixes two security issues in third-party libraries.