This page contains all of Logger's Change Logs. Starting in version 3.0.0 onwards, only major tickets will be listed here. To see a complete list of all the issues for each version, review the appropriate release page.
Download
Release Page
Release Articles
| Issue# | Feature | Articles |
| 136 | ORA-1031 on install |
Download
Release Page
Release Articles
| Issue# | Feature | Articles |
| 29 | Allow level to be passed to other functions | Adding Level to Additional Procedures |
| 50 | Deprecate levels Timing, APEX, and Context. | Deprecate Levels Timing, APEX, and Sys Context |
| 54 | Enhance log_apex_items | log_apex_items Enhancements |
| 57 | Secure Logger schema setup | Restrict Logger's Access to Your Data |
| 73, 75 | Bug fix: Timing issues | |
| 78 | Bug fix: NO_OP installer references Logger objects | NO_OP Install Changes |
| 94 | Best practices guide | Logger Level Best Practices |
| 103 | Custom Preferences set_cust_pref del_cust_pref |
Custom Preferences |
| 108 | Grants and Synonyms script | Restrict Logger's Access to Your Data |
| 109 | Bug fix: Length doesn't factor multi byte characters | |
| 110 | Bug fix: Level changes don't propagate to sessions with client_identifer |
Download
Release Page
Release Articles
- Logger 3.0.0 EA1: this contains a list of the top ten features of 3.0.0.
| Issue# | Feature | Articles |
| 25 | Add CLIENT_INFO to logger_logs | New fields CLIENT_INFO and SID |
| 32 | printf type support for substitution strings (printf) | printf support |
| 42 | ok_to_log takes in both name or number of logger level | |
| 43 | Reference new global constants for names | |
| 44 | Global Constants for Logger Level Names | Global Level Names |
| 47 | Support for both logger level name and number | |
| 46 | Plugins for Logger | Plugins |
| 51 | Add SID to logger_logs | New fields CLIENT_INFO and SID |
| 56 | Updated documentation format to use Flatdoc | Flatdoc Documentation |
| 57 | Modify build script so that no_op code is auto generated as part of build | |
| 59 | Allow security check to be bypassed for client specific logging level | |
| 68 | Added TOCHAR function | Explicit Conversions Using logger.tochar |
| 80 | Added log_warn and log_info shortcuts | log_warn and log_info shortcuts |
| 88 | Developer Guide | Developer's Guide |
| 89 | Include docs with each release | |
| 90 | Change License | New License |
| Issue# | Feature | Articles |
| 39 | Bug setting client level multiple times. | |
| 41 | Bug viewing logger.status when client_id is defined. |
| Issue# | Feature | Articles |
| 37 | Bug compiling logger_configure fixed. |
Download
Release Page
Release Articles
Note: Review Issue #31 as it may impact your application if you manually inserted into the LOGGER_LOGS table.
| Issue# | Feature | Articles |
| 17 | Allow for large text (> 4000 chars) to be passed into p_text parameter. If > 4000 then will be appended to the EXTRA column. In future may not be necessary with 12c large varchar2 column support (see issue #30) | Text Length > 4000 Characters |
| 20 | Restructured documentation:
|
Documentation Overhaul |
| 24 | Open ok_to_log as public. | ok_to_log |
| 26 | Fixed error compiling in 10g (or any 11gR1 and below). | 10g Sequence Fixed |
| 27 | Generate demo scripts and add them to build. More demo scripts to come during future releases. Avoids the need to regenerate for presentations and learning. | Demo Scripts |
| 28 | Include wiki documents as part of build. Wiki is technically part of a different git repository. By adding documentation with release developers will maintain history on API documentation etc. | |
| 31 | Remove trigger on LOGGER_LOGS. For performance issues and to resolve the large text issue the trigger on LOGGER_LOGS has been dropped. In its place, all insert commands should now use ins_logger_logs. Performance improvement as part of disabling the trigger. Initial tests show ~15% performance improvement for instances that are using APEX. Part of the speed improvement is how the USER is logged. |
ins_logger_logs |
Download
Release Page
Release Articles
| Issue# | Feature | Articles |
| New | Moved to GitHub and restructured / updated documentation | |
| New | Added p_params support and append_params functions. | Logging Parameters |
| 4 | Client specific level setting (to enable logging based on client_id) | Enable Session Specific Logging Session Specific Logging - Advanced Features |
| 8 | New build script which will allow for future versions of logger to be updated. This was built off a 1.4.0 release. |
| Issue# | Feature | Articles |
| Fix | Fixed an issue detecting 11.2 RAC installations | |
| New | APEX no longer supported from a web-only installation if the schema was provisioned by APEX. Essentially the APEX team removed the "create any context" privelege when provisioning a new workspace, likely for security reasons. I (Tyler) agree with their choice, it unfortunately impacts logger. |
| Issue# | Feature | Articles |
| Fix | Fixed major flaw in time calculation used in time_start/time_stop | |
| New | Changed implementation of LOG_APEX_ITEMS to use the APEX views so explicit privs on wwv_flow_data are not required. Thanks to Scott Spendolini for this suggestion. |
| Issue# | Feature | Articles |
| Fix | Fixed an error with the admin security check reported by John Flack | |
| New | It is now possible to install logger in multiple schemas as the global context is now prefixed with the schema name. So, the global context name in the LOGGER schema would be LOGGER_LOGCTX and the SCOTT schema would be SCOTT_LOGCTX. Thanks to Bill Wheeling for reporting this one. |
| Issue# | Feature | Articles |
| New | PROTECT_ADMIN_PROCS preference which is TRUE by default, protects set_level, purge and purge_all. This means that only someone logged into the schema where logger is installed can call these procedures. The idea is that you could grant execute on logger to other schemas, but want to prevent them from changing the levels or purging the logs. | |
| New | Preference called INCLUDE_CALL_STACK allows you to enable / disable logging of the full call stack for LEVELS greater than ERROR (such as debug). Logging the call stack does take additional resources and also requires additional storage per row. So, you can still read your debug messages, but you simply won't see the full call stack. The value is TRUE by default. | |
| New | CLOB parameter of "P_EXTRA" was added to call LOG... procedures. This populates a CLOB column in LOGGER_LOGS called "EXTRA". This column is also used by several new functions / procedures where the values are relatively large. | |
| New | logger.log_userenv procedure logs information obtained through sys_context('userenv'...), such as IP Address, NLS info, schema / user information. It's use is documented here. | |
| New | logger.log_cgi_env procedure grabs all output from owa_util.print_cgi_env and logs it to logger_logs.extra. Useful in debugging some APEX issues. It's use is documented here. | |
| New | logger.log_character_codes procedure supplements the output of the SQL DUMP() function, great for finding hidden carriage return / line feeds or other non-printable characters.It's use is documented here. | |
| Fix | set_level, purge and purge_all so they are now autonomous transactions (thanks Tony). |
Download
Release Page
Release Articles
| Issue# | Feature | Articles |
| TODO_TITLE | TODO | TODO_TITLE |
| TODO_TITLE | TODO | TODO_TITLE |
| TODO_TITLE | TODO | TODO_TITLE |
| TODO_TITLE | TODO | TODO_TITLE |
| TODO_TITLE | TODO | TODO_TITLE |