Sabine Heimsath PL/SQL Monitoren > Messen > Optimieren mit Open Source APEX Connect 2018 APEX Connect Sabine Heimsath

Size: px

Start display at page:

Download "Sabine Heimsath PL/SQL Monitoren > Messen > Optimieren mit Open Source APEX Connect 2018 APEX Connect Sabine Heimsath"

Franklin Blake
6 years ago
Views:

1 Sabine Heimsath PL/SQL Monitoren > Messen > Optimieren mit Open Source APEX Connect 2018

3 Sabine Heimsath Offiziell in der IT unterwegs seit 1999/DB-Version: Mag relationale Datenbanken, Aardman Animations und Earl Grey Selbständig mit its-people Oracle ACE DOAG

4 Sabine Heimsath Twitter: Blog: blog.its-people.de sqldeveloper.de

5 Instrumentation - Definitions I have one AOL friend that says adding lines to code is debug code (meaning bad), while others say it is instrumentation (meaning good) Chet Justice

6 Instrumentation why? Can you answer these questions? What are the response times? Where are the bottlenecks? The systems seems slower than last week why? Was our refactoring successful?

7 Instrumentation why? No matter who you are or how cool you think you are at programming, you can never know exactly what is going on in your code unless you instrument it. Just shut up and do it! Tim Hall

8 We want to know what it s doing, how it s doing it, how long it took and how much it costs

9 We want to know what it s doing, how it s doing it, how long it took and how much it costs Debugging fixing coding errors or logic

10 We want to know what it s doing, how it s doing it, how long it took and how much it costs Debugging Logging a type of auditing operational tracking of events, tasks or sets of tasks

11 We want to know what it s doing, how it s doing it, how long it took and how much it costs Code tracing by Runtime registration setting services, client id, client info, module and action in V$ views extended SQL trace file and AWR and ASH interfaces

12 We want to know what it s doing, how it s doing it, how long it took and how much it costs Metric collection Performance info: CPU and I/O that the users of an application are generating ASH, AWR

13 Instrumentation but It ll make my code run slower This is extra stuff I don t need It takes me longer to write

14 Instrumentation is a technical investment which will pay off sooner and later (and in between, too)

16 5 Open Source/ Public Domain Frameworks Instrumentation Library for Oracle (ILO) + Oracle Logging Framework (OLF) Log4PLSQL Logger PL/SQL Instrumentation Toolkit (PIT) BMC_DEBUG

17 ILO Builds a stack of calls on ILO_TASK.BEGIN_TASK and ILO_TASK.END_TASK Makes information available in v$session DBA or SELECT ANY DICTIONARY privilege needed Writes to trace file with ILO_TIMER.set_mark_all_tasks_interesting

18 OLF Writes information to a logging table Dynamically set log levels depending on module, action, instance, user, sid Uses Query Result Cache for its Config Table Two output modes: table or console (dbms_output) global config and log tables + optional local config and log tables

19 begin ILO/OLF Example ilo_task.begin_task( module => 'module', action => 'action'); dblog.info('before statement'); null; -- something great here dblog.info('after statement'); ilo_task.end_task; exception when others then dblog.error(sqlerrm); ilo_task.end_all_tasks; raise; end;

Logger Ora Open Source project Tip: have a look at their other

production environments if there are concerns Recommendation for

20 Logger Ora Open Source project Tip: have a look at their other projects, too! Recommendation: Install in own schema - because needs CREATE ANY CONTEXT - and doesn t have access to your data NO-OP option for production environments if there are concerns Recommendation for production: Leave full version installed and set log level to ERROR as the performance hit is exceptionally small

21 Logger Example procedure todo_proc_name(p_param1_todo in varchar2) as l_scope varchar2(30) := 'todo_proc_name'; l_params logger.tab_param; begin logger.append_param( l_params, 'p_param1_todo', p_param1_todo); logger.log('start', l_scope, null, l_params); null; -- more great code here logger.log('end', l_scope); exception when others then logger.log_error( 'Drama!', l_scope, null, l_params); raise; end todo_proc_name;

22 Logger Example

23 Log4plsql Many output channels beside the standard ones (table, file, console) through Advanced Queuing and Log4JBackgroundProcess: JDBC, JMS, SMTP, Socket, Telnet Uses DBMS_SYSTEM.ksdwrt to write trace files

24 Log4plsql

25 Log4plsql Example declare cpt number; begin plog.info('select raises ORA-01403:No Data Found'); select id into cpt from tlog where id = -1; exception when others then plog.error; end;

26 PIT Comfortable APEX application for administration Uses utl_call_stack (12c, conditional compile) MSG package with automatically generated constants, error numbers and exceptions Offers many assert functions

27 PIT Example gebabbel := '#1#' procedure my_proc( p_id in number, p_string in varchar2) as begin pit.enter('my_proc', 'block'); pit.info(msg.gebabbel, msg_args(p_string ' and Klaas and Pit!')); null; -- do something smart here pit.leave; end my_proc; exec my_proc( , 'Hello Jan and Hein');

28 PIT Example Console PIT_LOG PIT_CALL_STACK

29 PIT Administration

30 PIT: Administration

31 PIT: Add/Edit Message Types

32 PIT: Change/Edit Output Modules

33 PIT: Change/Edit Parameters

34 PIT: Export Messages/Params for Translation

35 BMC_DEBUG Flexibility through parameter tables (user, session, package) Comprehensive documentation, lots of explanations Provided 'as is' (version 1, )

36 BMC_DEBUG Example procedure quickstart is begin bmc_debug.begincall('procedure','quickstart'); bmc_debug.msg(4,'this is a message'); bmc_debug.endcall('procedure','quickstart'); exception when others then bmc_error.error_handle (); raise; end quickstart; BMC_DEBUG_LOG BMC_DEBUG_CALL_STATS

38 Licenses ILO/OLF GNU Lesser General Public License Log4plsql Logger PIT BMC_DEBUG Apache Software License MIT License MIT License New BSD licence

39 Activity ILO/OLF 2013 OLF being transferred to Github Log4plsql Sourceforge: 2013 Fork in Github has changes March 2016 Logger Still active, very fast responses PIT Still active, very fast responses BMC_DEBUG 2015

40 Conclusion If you use your own instrumentation fine. Maybe you ll want to have a look around for some inspiration? you are currently looking for an easy, ready-to-go open source framework, Logger is a good choice you have special requirements Log4PLSQL might fit for you you have a well-structured instrumentation approach and like a nice APEX App for administration - go for PIT You are looking for a small solution and an easy start, chose BMC_DEBUG

41 Nach der Werbung geht es weiter

42 500+ Technical Experts Helping Peers Globally 3 Membership Tiers Oracle ACE Director Oracle ACE Oracle ACE Associate bit.ly/oracleaceprogram Nominate yourself or someone you know: acenomination.oracle.com Connect: oracle-ace_ww@oracle.com 1/4

43 Call for Papers bis 4. Juni 2018! DOAG CfP DOAG 2018 Konferenz + Ausstellung Infos hier vom 20. bis 23. November 2018 #DOAG2018 2/4

44 und wohin als nächstes? The perfect 12c PL/SQL error handler Sven-Uwe Weller Dienstag, 24. Apr., 14:00 Open Source PL/SQL Utility Tools for Oracle Martin D'Souza Donnerstag, 26. Apr., 14:30 PL/SQL & SQL Was nicht messbar ist, kann man nicht lenken! Jonas Gassenmeyer Donnerstag, 26. Apr., 10:30 3/4

45 SQL Developer Enhancement Request Dim instrumentation code: 4/4

46 SQL Developer Enhancement Request Show/hide instrumentation code: 4/4

SQL Developer Enhancement Request Read more: https://jeffkemponoracle.

47 SQL Developer Enhancement Request Read more: Vote: Free OTN account needed 4/4

48 Zurück zum Thema

49 Instrumentation Some general recommendations

50 1 Wrap your Transaction Control Statements Useful for Long running transformations with several steps that have to be restarted after an error Example

51 1 Wrap your Transaction Control Statements

52 1 Wrap your Transaction Control Statements

53 1 Wrap your Transaction Control Statements How do you find all candidates for replacement? The correct answer for 12.2: PL/Scope

54 1 Wrap your Transaction Control Statements 12.2 only

55 1 Wrap your Transaction Control Statements <= 12.1

56 <= 12.1 Many false posititves. Sorry!

57 2 Wrap DBMS_APPLICATION_INFO calls You There need is no call inherent nesting because ability to set module and action back to DBMS_APPLICATION_INFO.set_module( what module_name they were => null, action_name => null); you have to keep the values might somewhere lose information. yourself! begin end; pit.enter('my_block'); -- do something pit.enter('my_loop'); for... loop -- do some more end loop; pit.leave; -- leave loop -- final task pit.leave; -- leave func

2 Wrap DBMS_APPLICATION_INFO calls Set module & action below the begin statement Update module & action for any subtask Place above all end and return statements!

58 2 Wrap DBMS_APPLICATION_INFO calls Set module & action below the begin statement Update module & action for any subtask Place above all end and return statements! Don t forget: Place inside all exception handlers! begin pit.enter('my_func'); pit.info(...); -- the actual work pit.leave; return x; exception when others then pit.stop; end my_proc;

59 3 Avoid placing instrumentation calls inside loops

60 3 Use DBMS_APPLICATION_INFO in Loops! DEMO (Session_Info progress)

61 4 Don t delete your instrumentation code Keep it production Turn it on/off by changing settings

62 4 Don t delete your instrumentation code You ll find your code easier to tune. You ll find your code easier to maintain over time. Your trace code, like Oracle s should always be there, just waiting to be enabled. Tom Kyte

64 Lesestoff

65 Instrumentation Frameworks Logger PIT Log4plsql ILO BMC_DEBUG

66 PL/Scope Schöner Coden PL/SQL analysieren mit PL/Scope (Artikel von Sabine Heimsath) PL/Scope Blog (diverse Beiträge von Philipp Salvisberg) PL/SQL Blog (diverse Beiträge von Steven Feuerstein)

67 some final words Start instrumenting on Monday Make your customer happy and your DBA and yourself!

How to instrument your code easy and effectively

How to instrument your code easy and effectively 31 maart 2017 APEX World Rotterdam Sabine Heimsath its-people GmbH Sabine Heimsath Client Senior Database Application Developer PL/SQL, SQL Developer, APEX