Sunset photo

Photo from sunset at Jane's parents' house.

Comments

Post a Comment

Popular posts from this blog

Using RMAN DUPLICATE when the target system is behind a firewall

My production servers are on the other end of a network link where they can not make connections to any of the servers in my dev/test environment, but connections from dev/test to production are fine.  This is problematic: OEM 12c (housed in dev/test environment) can't monitor production (needs 2-way agent<->OMS comms) RMAN DUPLICATE doesn't work (requires connection from source to destination) No way to push files from production to dev/test And many others... The point of this post is to talk about RMAN DUPLICATE in this situation. As there's no outbound connectivity from prod->dev/test, I initially assumed this wouldn't be possible, however I've tried using SSH tunnels. and while it didn't work due to my previous blog post (RMAN-05531 during duplicate from active standby), the concept is fine. Log in to the shell of the destination database, and follow the usual setup (DocID 452868.1 ) to create a duplicate from active database: C...
Read more

Data Guard with Transparent Application Failover (TAF)

One of the problems with Data Guard is that even after switching/failing over to the standby database, all clients need to be reconfigured to communicate with the new primary. The simplest way to achieve this (if using a centralised tnsnames.ora ), is to modify the file and  add the line " (FAILOVER=YES) ",  and either multiple ( DESCRIPTION=...) or (ADDRESS=...)  lines, one for each of the standby systems, in the order that the client should attempt connections . This tells the client to try each address in turn until one succeeds. Doing so provides basic failover functionality within Oracle Net, and will probably function correctly most of the time.  Though be aware - because both primary and standby can share the same instance name (e.g. the same SID, therefore the same connection string), there is potential for this simple scheme to go wrong. An example in an active data guard environment (where the standby is open read only): a temporary network issue cau...
Read more

DBMS_SCHEDULER and DST - jobs running one hour off expected time

There's an awful lot of stuff written out there about this topic, so this will be relatively brief. However, none of the posts I'll be linking to answered my question or solved my problem, that's why I'm putting this here. DST ended in the UK on Sunday 26th October with the clocks going back one hour.  From that point on, my audit log purge job, which runs daily through DBMS_SCHEDULER has been running an hour early!  I wouldn't normally have noticed as it runs in a quiet time but I happened to be looking at some other logs and spotted it wasn't right. The Oracle DBMS_SCHEDULER docs seem to have the information to sort this out: Repeating jobs with frequencies smaller than daily follow their frequencies exactly across daylight savings adjustments. For example, suppose that a job is scheduled to repeat every 3 hours, the clock is moved forward from 1:00 a.m. to 2:00 a.m., and the last time the job ran was midnight. Its next scheduled time will be 4:00 a.m. ...
Read more