April 2016 »

Uncategorized

Be careful when setting the DBTIMEZONE!

Why you should not set the DBTIMEZONE to a “Location Time Zone” format in Oracle. First of all, the DBTIMEZONE does not control at what time scheduler jobs exactly starts. When I have been taking care of my scheduler jobs recently I was wondering how do I now configure these, I came across a very simple question. After what time zone will “by hour 23” executed which I have planned here? In addition to the well known SYSDATE, I came across the DBTIMZONE parameter. What would make more sense that the database time zone controls when my >database!< scheduler jobs

Be careful when setting the DBTIMEZONE! Blogbeitrag lesen »

By Johannes Ahrends • 24. April 2016 • 3 minutes of reading

Second SCAN-Listener

Since Oracle 12c you create and use a second (or even more) SCAN-Listener for Load-Balancing, Failover, etc. This can be useful to separate Network traffic e.g. for Dataguard or Shareplex replication. Like the ordinary SCAN-Listener you need two additional VIP- and three additional SCAN-Addresses. In the following example I want to separate the Dataguard traffic between a RAC Database with two nodes (morrison and manzarek) and a single node (daltrey) RAC Database as standby.