Re: FILE IDENTIFY wait event

[Anjo Kolk]

Daniel, It is not Oracle decision to wait. Basically the file identity means that Oracle will open the file and read the first block to find the name of the file and the size of the file. So two system calls are done. The driver for the file that you will make the decision to return an error. Anjo.   "Daniel W. Fink" wrote: The volume was offline. Once it was back online, Oracle resumed the process of creating a tablespace.Which brings up another question...why did Oracle wait on this condition instead of terminating with an error? If a file-system directory/drive cannot be found, the attempt to create a tablespace will fail. Is there something different in using a raw device?Dan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of Tim Gorman Sent: Tuesday, April 30, 2002 11:24 AM To: Multiple recipients of list ORACLE-L Subject: Re: FILE IDENTIFY wait event   Make sure that the volume group underlying the logical volume is ONLINE? To test, I like to do something quick like "dd if=<raw-device> of=/dev/null count=100" to test the readability of the raw device.  If this fails, you can go to the SysAdmin with something that is pure UNIX... ----- Original Message ----- From: Daniel W. Fink To: Multiple recipients of list ORACLE-L Sent: Tuesday, April 30, 2002 10:41 AM Subject: FILE IDENTIFY wait event  Oracle8.1.7 on Solaris8I am trying to create a tablespace on a raw device and the SQL*Plus session that performs the tablespace creation is waiting on a 'file identify'. A quick search on metalink and other docs did not indicate the root cause of the wait event. I have used the raw device previously and the create tablespace uses the 'REUSE' option.Okay gurus...any clues as to exactly what conditions cause the event?Dan Fink