Now certified! DB1-C01 - AWS Certified Database - Specialty

I finally got the email through from the AWS Training group that I had passed the DB-C01 exam and I am now officially Certified! Hurrah!

It took 2 months to the day to get the results through. I'm very pleased with the result and am looking forward to getting to put some of this knowledge into practise!

Comments

Post a Comment

Popular posts from this blog

Error upgrading 11.2.0.3 to 11.2.0.4: ORA-00942 & ORA-06512

During an upgrade of an 11.2.0.3 DB to 11.2.0.4 using DBUA, this error popped up: Errors - Oracle Workspace Manager . ORA-00942: table or view does not exist . ORA-06512: at "WMSYS.OWM_MIG_PKG", line 1575 . ORA-06512: at "WMSYS.OWM_MIG_PKG", line 1592 . ORA-06512: at line 1 . VALID 11.2.0.1.0 00:00:39 This error is referenced in MOS note  1051991.1 and can be ignored: If DBA_REGISTRY shows the status of (in this case) Workspace Manager is VALID, then this error is safe to ignore. Click Ignore and the upgrade will continue.
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

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