POUG Workshop - new formula

27.03.2020, Warsaw


POUG (Polish Oracle User Group) was set up by Database Whisperers in 2016. After dozens of meet-ups and four two-days-long international conferences, it's time for new formula -   POUG Workshop.

We know it might sounds cheesy but the truth is YOU were the inspiration for the new idea. It was you who asked us for:

  • longer sessions
  • more case studies
  • precise examples

Our goal is to provide you maximum knowledge in a form of 1,5-hours-long and connected to each other sessions which all together create advanced workshop (run by THE BEST Oracle experts from all over the world).
We offer you something new, but some things will never change. For example:

  • easy going atmospheare
  • knowledge instead of marketing
  • beer:)


Rejestracjarozwiń opis

Sesja sponsorska 1rozwiń opis
Sesja sponsorska 2rozwiń opis

The Heart of Oracle - how the core RDBMS engine worksrozwiń opis
The Oracle database is big, complex, and highly capable. But how the very core of it works is relatively simple - and yet is not often explained.
I will describe the overall architecture of the database, how data is moved from disc to memory *and back*, what blocks are and why their size & distribution is vital to performance. This will include how user data is spread between the SGA nd the PGA and why. Next I will explain the vital role of redo and how it is the most important part of the database. Then I will cover how Oracle maintains a perfect point-in-time view of data and what a "consistent get" really is.
By the end of the talk you will probably understand how the database works better than many experienced DBAs. This knowledge makes all further talks on Oracle performance and features make much more sense.
During the talk you can ask any questions you want. I might even answer them.
Martin Widlake
Systematic Performance Troubleshooting with (free) 3rd Party Toolsrozwiń opis
The speaker frequently faces more and more hurdles during his daily work as an independent Oracle performance consultant because of direct access to the database is restricted for security reasons or a critical performance problem has to be analyzed very fast/remote - especially the latter is a challenge regarding the usual mail-information-ping-pong.
There are several fee-based and free tool-sets on the market that support the DBA and/or external consultant to easily gather all relevant performance and diagnostic data. This talk is focused on the free tool-sets (e.g. SQLd360, Pathfinder and maybe eDB360) that the speaker uses in his daily work with clients. Several - partly uncommon - performance problems will be analyzed and discussed with help of these tools. Please feel free to bring your own SQLd360 reports with you - so we can analyze them live during the talk :-)
Stefan Koehler

Execution Plansrozwiń opis
Jonathan Lewis
Log Writerrozwiń opis
Frits Hoogland

Przerwa obiadowarozwiń opis

Franck Pachotrozwiń opis
Your first sight on your database performance is probably from the Enterprise Manager "Top Activity" or equivalent: the load of the database on the time axis, displayed with colors. Green for CPU, blue for I/O, red for locks... Behind those colors are the wait events which you can also query from many monitoring places: V$ views, Statspack report, SQL Trace. They tell a lot about what the database is doing or waiting on, as long as we understand exactly what they measure. We will get through the most common ones to understand what they tell us, and how we can improve the performance.
10053 + CBO transformation/statsrozwiń opis
Neil Chandler

Beginners' Guide to using the AWRrozwiń opis
In this session we will draw pull together the strands from the three previous sessions as we get to grips with the information that's available in the Automatica Workload Repository (AWR) or (for those without the diagnostic and performance licences, or running Standard Edition) the free Statspack utility.

If a user can tell you exactly where they are having a problem - which report is taking too long to run, which screen is responding very slowly, which drop-down menu is oozing like honey instead of dropping like a stone - then there are high precision strategies you can use to identify the cause of the problem. The AWR is there to help on those occasions when the database appears to be generally "unhealthy", or pushing the limits of the hardware, or showing random variations in performance.

The three previous sessions of the stream will have examined:

* How the core RDBMS engine works
* Wait Events and DB time
* Execution Plans

In this session we learn how the AWR can help us build a picture of what the engine is doing and give us some clues about how we can reduce the core activity cut back on basic resource consumption; we learn to recognise the relationships between the wait events and instance activity stats that tell us why the database is working harder than we expect; and we find easy ways to track down expensive activity and understand why the underlying execution plans may need to be address.

The bottom line on using the AWR is that it allows you to find the worst examples of excessive resource usage caused by one of two key problems

* You're doing something the hard way
* You're doing something too often

The numbers will tell you how to reduce the workload - but you still have to remember that that might not make any visible (response time) difference to the end user
Jonathan Lewis
Full Stack Tracerozwiń opis
Kamil Stawiarski

Zakończenie konferencjirozwiń opis




Jak dojechać

Hotel Indigo Warsaw

Smolna 40, 00-375 Warszawa

After party

POUG Partnership

POUG is not only the official Oracle community – first of all it is the base of very active members, who are engaged in the group development both during the meetings and the preparations to them. Our message gets to the 400 people connected with databases – from the developers to the administrators and from the begginers to the experts with years of experience.

We would like to invite you to be a part of our event – it is a chance to show your brand during and before the meeting. What does it mean?