1.0.3.4 New Features ================== 1. New Metrics, Gauges and Reactions - Archive logs and archive log destinations are now monitored - Oracle option usage (focusing on advanced compression and advanced security options) is now tracked and alerts are produced when such a feature is used - dba_feature_usage_statistics is now archived and kept 2. Blackout! This version introduces fully implemented blackouts. Two modes are available: SILENT: A silent blackout will cause the framework to continue running as normal. Metrics are collecting data, gauges are checking the data and are creating alerts. But, reactions do not fire, and instead alerts are auto-acknowledged. FULL: A full blackout will cause all processes to shut down, with two exceptions: SYNC and STATE_CHECK. Those two run at a reduced frequency (1/minute vs once every 5 or 10 seconds), since they are needed to bring the framework back up once the blackout ends. Blackouts are automatically archived (whether they are cleared / removed manually, or whether they expire naturally) and the history is retained. 3. Smarter reports Reports now automatically have access to any other reactions that were fired in before they were triggered (if part of the same reaction chain). This allows for example a session report to easily access the data collected by high-speed sampling on v$session_wait's underlying table x$kslwt. 4. Unique PGA usage report zztat is now aware of 680 Oracle kernel areas and their purpose. This information is applied to PGA memory reports, based on the view v$process_memory_detail. This is a unique feature and a prime example of where we want zztat to go. We want it to go the extra mile: - It will tell you that a session uses 2GB PGA and that's potentially a problem. But it won't stop there. - It will also tell you that the memory used by the session is used for e.g. SQL/PLSQL/Other. But it won't stop there. - It will even tell you which area of the Oracle code is using the memory, for example pmuccst or pmucalm. But it won't stop there, either! - It will then use its internal library of Oracle kernel areas to tell you that "pmucalm means: support for pl/sql handling of collections", for example. That way, you know right away what you need to look for, and where your memory is going. 5. Automated Error Reports We have blogged about this here: http://zztat.net/blog/index.php/2017/11/26/beta-progress-update/ This is disabled by default, but you can easily enable it by running: "exec zz$manage.reaction_config(parameter=>'SEND_ERROR_REPORT',value=>’YES’);” on the repository database as user$repo. 6. zztat eye (ZYE the interactive alert handler) functionality added to the framework. 7. Automatic Patching system added to the framework. Patches are applied to repository and automatically replicated to targets. 8. Bug fixes Lots of bug fixes and enhancements in this release as well. Review the full changelog at http://zztat.net/changelog 1.0.3.4 Installation ================== 1. You'll need an Oracle 12.1 database with XDB and APEX 5.1 installed. For a step-by-step guide how to setup APEX 5.1, please see this post which you can follow until the section in "Embedded PL/SQL Gateway" is completed. https://oracle-base.com/articles/misc/oracle-application-express-apex-5-0-installation 2. Review the installation pre-requisites at http://zztat.net/prereqs 3. Extract the software package on the database server mkdir /u00/app/zztat cp zztat 1.0.3.4.tar.gz /u00/app/zztat tar -zxvf zztat 1.0.3.4.tar.gz 4. If UTLMAIL is not installed on your database please run the following commands as SYS SQL> @$ORACLE_HOME/rdbms/admin/utlmail.sql SQL> @$ORACLE_HOME/rdbms/admin/prvtmail.plb SQL> ALTER SYSTEM SET smtp_out_server = 'localhost' SCOPE=both; 5. If not using ASM, please ensure to set the parameter DB_CREATE_FILE_DEST properly as per the example bellow: SQL> ALTER SYSTEM SET DB_CREATE_FILE_DEST = '/u01/app/oracle/oradata/ORCLREPO/ORCLREPO' SCOPE=both; 6. If using Oracle Cloud or AWS please ensure the parameter ENCRYPT_NEW_TABLESPACES is set to DDL, if not, please execute the command bellow: ALTER SYSTEM SET ENCRYPT_NEW_TABLESPACES = 'DDL' SCOPE=both; 7. Take a look at setup.sql and edit the values for your environment, such as tablespace and ASM diskgroup name / datafile path, passwords, etc. The file is highly documented and should be self-explanatory. If something isn't clear, please let me know! 8. Run the installer to create the zztat repository: sqlplus / as sysdba @install_repo.sql 9. You can now access the zztat UI at http://server:port/apex/f?p=100043 http://server:port/apex/f?p=100043 https://129.158.74.147/ords/pdb1/f?p=100043 Login credentials in the UI will be the username ZZTAT_ADMIN and the password of the zztat repository user as configured in setup.sql 10. Distribute the software to any target database servers you want to integrate (be monitored by the repository) 11. Make sure you edit the setup.sql file to configure the database link to connect to the repository database before running the installer. It's also a good idea to test the link to make sure it works. 12. Make sure to follow steps 3,4,5,and 6 on the target database 13. Run the target installer sqlplus / as sysdba @install_target.sql 14. You can start / stop the framework by running @start.sql and @stop.sql on either a target or the repository database. Please note that the framework on the repository must be started for target databases to function (this includes target registration as well as synchronization). ZZTAT CHANGELOG =============== The zztat changelog is public and can be reviewed for the full list of changes: http://zztat.net/changelog for the framework and http://zztat.net/ui_changelog. CREDITS & ACKNOWLEDGMENTS ========================= Special thanks go out to our supporters and investors : Adrian Shepherd, David Whiting, Francisco Alvarez, Thomas Mulcahy, Vlatko Janceski. Thank you, your contributions and support are greatly appreciated. The zztat UI includes SQL Formatter by Uku Pattak (Licensed under MIT License - https://github.com/zeroturnaround/sql-formatter).