We value your privacy

We use cookies to enhance your browsing experience, serve personalized ads or content, and analyze our traffic. By clicking "Accept All", you consent to our use of cookies.

Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Powered by Cookieyes logo

xen vs os

while doing my previous tests with _datafile_write_errors_crash_instance with  on a paravirtualized  linux (centos 5.7 64bit)  under xen server 5.5 I had some unexpected behaviour, basically

I removed the datafile and oracle, or better the Dbwriter didn’t see it at all. I even could continue to create tables and data in that datafile.

i went to /proc/PID_OF_THE_DBWR/fd
and there did …

ls -al

lrwx—— 1 oracle oinstall 64 Mar  2 14:44 260 -> /u02/MYDB/undotbs01.dbfsnipped …lrwx—— 1 oracle oinstall 64 Mar  2 14:44 261 -> /u02/MYDB/users01.dbf (deleted)

and it was really deleted, but somehow it wasn’t picked up. I was a bit astonished by this behavior and decided to redo the exercise on a non virtual linux Centos 5.6
there the same action almost immediately got picked up by oracle  and the datafile was brought offline or the instance crashed depending on how you set _datafile_write_errors_crash_instance.
Pretty bizar. 
an strace of the delete  on both systems revealed the same os calls.

My colleagues and I discussed this and our best guess is the Xen Server “optimizes” the data access an causes this behaviour.

We will test this next year with a pure virtualized linux ….
keep you posted

On By phil

Leave a Reply

Related Post