Sinan Petrus Toma
As the blog title reveals, I’m passionate about Oracle Database and Oracle Cloud Technologies.
I work as a Solution Engineer at Oracle and focus on Oracle Autonomous Database and Database Cloud Services. My top topics are database migrations, high availability, disaster recovery, consolidation, and a bit of patching, upgrade, and database security. I also deal with further Oracle Cloud Infrastructure (OCI) topics like Networking, Compute, and Storage.
Before joining Oracle, I worked as Oracle DBA, mainly managing RAC databases and looking for heartbeats. In my 12+ years of business experience I have been dealing with databases all the time.
I love traveling (it must be at least 8 hours by plane to count as such), being at the beach, and drinking a beer, or two.
Find more about my career on LinkedIn, and let’s get connected.
Have a nice day!
Awards & Certifications
- Employee of the Year FY20 – EMEA Solution Engineering Hub at Oracle
- Spot Award for exceptional performance, commitment, outstanding agility and extra-dedication at Oracle
- Recognition Award Q2FY21 – German Technical Cloud Engineering at Oracle
database-heartbeat.com is a personal page. The opinions and interests expressed on this blogs are my own and do not necessarily represent the positions, strategies or views of any current or previous employer. There is no explicit or implicit endorsement of any kind from any current or previous employer of the content on this blog.
The content is intended to solely highlighting technical topics I’m personally passionate about, and is not advising or encouraging you to buy any products. All information is offered in good faith and in the hope that it may be of use, but is not guaranteed to be correct, up to date or suitable for any particular purpose. database-heartbeat.com accepts no liability in respect of this information or its use. Before trying anything, especially in production, first test it yourself and refer to the official Oracle Documentation.
Product and company names mentioned in this blog may be the trademarks of their respective owners.