So if you are filling an OEDA for Exadata deployment there are few things you should take care of. Most of the screens are self explanatory but there are some bits where one should focus little more. I am running the Aug version of it and the screenshots below are from that version.
- On the Define customer networks screen, the client network is the actual network where your data is going to flow. So typically it is going to be bonded (for high availability) and depending upon the network in your data center you have to select one out of 1/10 G copper and 10 G optical.
- If you are going to use trunk VLANs for your client network, remember to enabled it by clicking the Advanced button and then entering the relevant VLAN id.
Also if it is going to be an OVM configuration, you may want to have different VMs in different VLAN segments. It will allow you to change VLAN ids for individual VMs on the respective cluster screens like below
- If all the cores aren’t licensed remember to enable Capacity on Demand (COD) on the Identify Compute node OS screen.
- On the Define clusters screen make sure that you enter a unique (across your environment) cluster name.
- The cluster details screen captures some of the most important details like
- Whether you want to have flash cache in WriteBack mode instead of WriteThrough
- Whether you want to have a role separated install or want to install both GI and Oracle binaries with oracle user itself.
- GI & Database versions and home for binaries. Always good to leave it at the Oracle recommended values as that makes the future maintenance easy and less painful.
- Disk Group names, redundancy and the space allocation.
- Default database name and type (OLTP or DW).
Of course it is important to carefully fill the information in all the screens but the above ones are some of them which should be filled very carefully after capturing the required information from other teams, if needed.
Faced this error while querying v$asm_disk after adding new storage cell IPs to cellip.ora on DB nodes of an existing cluster on Exadata. Query ends with ORA-03113 end-of-file on communication channel and ORA-56841 is reported in $ORA_CRS_HOME/log/<hostname>/diskmon/diskmon.log. Reason in my case was that the new cell was using different subnet for IB. It was pingable from the db nodes but querying v$asm_disk wasn’t working. Changing the subnet for IB on new cell to the one on existing cells fixed the issue.
On a T5 Super Cluster (running 184.108.40.206) I was creating a cascaded standby from an already functional standby using RMAN DUPLICATE and it errored out with
ORA-01671: control file is a backup, cannot make a standby control file
A quick search reveals that it is bug 11715084 that affects most of the 11.x versions except 220.127.116.11. There is a one off patch available for most of the versions or one can install the bundle patch that includes the fix for this patch. I applied BP26 and it worked fine after that.
This was my 6th year at Sangam and as always was good fun. We were a group of 4 people who were traveling from Delhi and we reached Hyderabad on Friday morning. Just wanted to keep a day for visiting Ramoji Film City and also wanted to avoid the rush that morning travel on the conference’s starting day brings. So after dropping the luggage at the hotel we hired a taxi and reached Ramoji Film City. It is a huge place and it is tiring to move around checking everything. But fortunately on that day the weather was very pleasant so moving around was good fun. We took a ride what they call as Space Walk and watched few sets where some movies were shot. Also they have a pretty good bird sanctuary over there where they have pretty good number of beautiful birds. Spending time there was nice and fun.
By 7 PM or so we were done with everything and started back to hotel. As it was dinner time already so we directly headed to Paradise and had some awesome Biryani.
Saturday was the first day of the conference. We reached the venue by 8:30 AM and the registration was pretty quick. Before starting of the technical sessions at 10 AM, we had plenty of time to move around, meet folks especially who we know online but had never met in person. For me it was my chance to meet Tim Hall in person for the first time. Simply put Tim is brilliant. His website is an inspiration for many bloggers. It was great meeting Tim in person and striking few conversations about various technologies.
Also met Kamran for the first time in person. Been connected to him on social media for quite some time now. It was great catching up with you mate.
Had last met Francisco in Sangam 10 and this year got a chance to meet him again. The second question (first was how is job 😉 ) he asked me was “How is your blog going ?” So that calls for some focus on blogging again 🙂
Then we selected the sessions we wanted to attend and moved to respective rooms. I attended most of the sessions around database technology. There was good variety of sessions but I noticed that Engineered Systems part was missing. There could have been some sessions on Exadata, Exalogic and Super Cluster. That would make an interesting topic and would pull good audience.
Start of the second day looked little lazy but with time it caught up. There were some free time slots for me as not all sessions were of my interest. So got some time to chat around with folks there.
In the end there was an excellent motivational session by Dr Rajdeep Manwani that was enjoyed by everyone in the audience. The key take away was that you yourself have to do something about the things that you think need to be fixed. Blaming others for mess up in your life isn’t going to help.
That was the end of the second day and the conference. We met everyone around and decided to leave. Our 9 PM flight to Delhi was delayed by 4 hours and we had plenty of time to reach the airport. So once again we headed to Paradise for dinner. We were having dinner and Kamran and Markus also reached there for checking out some Biryani. Finished our dinner, said good bye to them and left for the airport. Flight was delayed little more and finally reached home at 4 AM next morning. Long day !
Read Tim’s take on Day1 and Day2.
A rather not so great post about an ORA-00600 error i faced on a standby database. Environement was 18.104.22.168 on Sun Super Cluster machine. MRP process was hitting ORA-00600 while trying to apply a specific archive log.
The error message was something like this
MRP0: Background Media Recovery terminated with error 600
Errors in file /u01/app/oracle/product/22.214.171.124/diag/diag/rdbms/xxxprd/xxxprd1/trace/xxxprd1_pr00_6342.trc:
ORA-00600: internal error code, arguments: , , , , , , , , , , , 
Some googling and MOS searches revealed that the error was due to corrupted archive log file. Recopying the archive file from primary and restarting the recovery resolved the issue. The fist argument of the ORA-600 is actually the sequence no of the archive it is trying to apply.