In this Document

---

Applies to:

Oracle Database - Enterprise Edition - Version 10.1.0.2 to 10.2.0.4 [Release 10.1 to 10.2]
z*OBSOLETE: Microsoft Windows Server 2003
z*OBSOLETE: Microsoft Windows Itanium (64-bit) - 244
z*OBSOLETE: Microsoft Windows XP (64-bit AMD64 and Intel EM64T)
***Checked for relevance on 27-Mar-2013***
Microsoft Windows Server 2003Microsoft Windows XP (64-bit AMD64 and Intel EM64T)Microsoft Windows (64-bit) on Intel Itanium

Symptoms

On windows environments were ASM is used to control the storage for the data files, trying to create a datafile on the diskgroup, the following errors are reported:

This could happen creating a tablespace, adding a datafile, restoring a datafile.

The ASM instance does not report any error in the alert.log, but in the database alert.log the following errors are also reported:

Cause

The errors indicate that the Oracle process do not have write access to the physical disk. In windows environments there is not particular permissions for the physical devices that could avoid the access.

At the ASM side the diskgroup is mounted which means all the disks associated with it were read successfully.

The cause of the problem is the account used to start the services associated to ASM and to the database. In single instance will be created the service OracleCSService which is required to mount the ASM instance. This error is present when the CSS service and the database service are started with different users or the CSS service is not started by the Administrator account.

Changing the service to be started with the Administrator account will fix the problem.

Solution

1. Go to Start -> Settings -> Control Panel -> Administrative Tools -> Services
2. Identify the properties for service OracleCSService
3. Check the Log On folder.
4. Change the Log on as attribute and use Administrator.
5. Stop the database and ASM instances
6. Restart the services and instances
7. Test again the creation of the datafile.