COGNOiSe.com - The IBM Cognos Community

Planning & Consolidation => COGNOS Planning => Topic started by: jeffowentn on 08 Jul 2010 01:52:46 PM

Title: create database error when on network path - SQL 2005
Post by: jeffowentn on 08 Jul 2010 01:52:46 PM
Windows 2003
SQL 2005
Cognos 8.4.1

Upgrading contributor applications from 7.3 and 8.1 to a distributed environment.  We are using a polyserve db instance for the applications, and we run into this error:

"is on a network path that is not supported for database files"

The following has been done:

SQL Server
- Grant create and drop table privileges for the database to the user account.
- Ensure that the user account is a member of the db_ddladmin, db_datareader, and db_datawriter roles.
- Ensure that the user is the owner of their default schema

In addition, the account has been assigned to dbcreator.

Any help with this is greatly appreciated.
Title: Re: create database error when on network path - SQL 2005
Post by: SomeClown on 09 Jul 2010 06:17:26 AM
Not enough info, but were I to guess, you specified a file location for the data files/backup files that did not specify a drive local to the database server -- D:\Mysqldata\Backups has to exist on the db server (accessible by the engine)
Title: Re: create database error when on network path - SQL 2005
Post by: jeffowentn on 09 Jul 2010 08:54:35 AM
Let me know what add'l info is needed, but the path I am using is:

D:\SqlServers\Instance__CognosDB1\InstallLUN\Data\

Our DBA provided this path as the path that would point directly to the database instance in the polyserve.
Title: Re: create database error when on network path - SQL 2005
Post by: SomeClown on 11 Jul 2010 06:16:13 AM
Is that directory the local specification for data directory for that instance?  It would seem polyserve does a remapping of drives that may not be compatible with how Planning invokes the db create process.
Title: Re: create database error when on network path - SQL 2005
Post by: jeffowentn on 09 Sep 2010 01:45:20 PM
It turned out to be a security issue...the DBA hadn't granted all the appropriate rights to allow us the correct connection...nothing more than that...thanks for your help!