While staging to rebuild the Oracle DB Console (Oracle Enterprise Manager – OEM), I needed to check something in my MySQL instance and ran into the following error after changing the machine’s
hostname for that OEM test. The message basically says that MySQL Workbench can’t resolve the connection.
The dialog error provides an excellent note, which lists the actual error as the first thing to check. The dialog follows:
Somebody asked how to solve a problem with the
=AVERAGEIFS function and non-contiguous ranges. The solution requires a combination that uses a group of
=SUMIFS function divided by an equivalent group of
Somebody posed a question about starting and stopping the database from within the OEM tool as the
SYSTEM rather than the
SYS user. There’s actually a simple trick to do that, you connect to OEM as the
SYSTEM user but when you startup or shutdown the database, you reconnect for those tasks as the
Many times occur that we can not execute an UPDATE or DELETE statement, because a couple of rows are locked by an other session(s).
We can generate – and handle – exceptions, but this solution sometimes not enough.
Using the SKIP LOCKED clause – officially introduced in Oracle 11g- we can try to solve the problem incrementally.
Let’s suppose that other sessions sooner or later will finish their transactions. During their transactions we can modify the “free” (not locked) rows with this option.
Let’s see a simple case study:
The second Roundtable discussion at the PL/SQL Challenge focuses on an issue that every developer grapples with: how to name our identifiers. That is, what are our naming conventions?
A longtime PL/SQL Challenge player, John Hall, offers a very different approach: