At SBB, for some workload we are leveraging the wonderful capabilities of Amazon Web Services. As a result, I have been working a lot more with AWS for the past few months and have decided to go for the SysOps certification. So here we go, I am now an “AWS Certified SysOps Administrator – Associate”:
While some AWS services are not perfect, I enjoy it very much to work with such a great platform. I am even thinking about getting more AWS certifications :).
In preparation for my OCP examination, I am currently playing around with ASM. For this purpose I am using an AWS instance to install and configure my database. So I added my disks, partitioned them using fdisk and installed ASMLib to manage them. But when I wanted to issue the createdisk command, this happened:
[root@ip-10-234-66-103 ~]# oracleasm createdisk DATA0 /dev/xvdc1
Device "/dev/xvdc1" is already labeled for ASM disk ""
So what is the problem here? Before deciding to use ASMLib, I tried to add the disks using only ASM commands from within the ASM instance, which failed for some reason. This is why I then switched to ASMLib.
Read the rest of this entry
While discussing the topic of cloud computing today, my co-worker mentioned the Amazon EC2 service and gave me a quick presentation of the features that are available. Since I am a big fan of virtualisation and the idea of scalable architectures, I immediately thought “This could be great to test some things out and is a wonderful opportunity to play around with different virtual machines”. So I signed up and did some quick tests to look at the IO performance…
I was especially interested in using these machines for storage and maybe some tests with databases. For these tests, my current Virtual Server serves as a reference, simply because EC2 could provide an alternative to that Virtual Server. In my tests, I included the following configurations:
Read the rest of this entry
