July 18, 2011 I am surprised at the significant number of unique solutions to the SQL problems that I have previously posed on this blog. For fun I thought that I would give people another chance to demonstrate their unique approaches to solving another problem. Supposed that a transaction table exists with the following definition: CREATE [...]
We have 3 node rac in the below example (racn1, racn2 and racn3), where we are removing racn3 from the cluster
I think Index Organized Tables(IOTs) are a much under-used and yet very useful feature of Oracle. Over the next few postings I’m going to cover some aspect of Index Organised Tables, both good and not-so-good. I am going to cover some benefits of IOTs that I think many people are unaware of. In this first post I am just going to run through the basics of IOTs.
On 11gR2 RAC (Grid Infrastructure), I tests use LISTENER_SCAN* on port 1521 and LISTENER on port 1522. I would like to check what service names are registered in LISTENER. Umm...
[oracle@db01 ~]$ cat /grid/network/admin/listener.ora
LISTENER=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))) # line added by Agent
6.0.06 (16 July 2011)
Seriously Oracle support what is going on here? I have had a service request SR 3-3474803321 open for a very long time. On June 6 2011 I escalated it yet again and provided a reproducible test case. Oracle support at that time noted they were waiting on getting a test machine to verify it and then get a bug opened.
I must say, this has been a busy weekend.
We have been promoting a release to production and a guaranteed restore point was created on Friday as rollback strategy. On Sunday I was called as we started to receive alerts.
Our monitoring system started to send emails and SNMP Traps with the following alerts: