We have Pervasive SQLv8.70 running wonderfully on both SCSI and iSCSI san's in 2-node Netware 6.5sp7 clusters.  The problem we have always had in both is creating DSNs on the clustered volume VOL1.  Our work around has always been to create the DSN on the SYS volume, move it to the clustered VOL1 volume, then change the Configuration pointers in PCC Maintain Databases from SYS to VOL1, and everything worked perfect.  That still works but we need to solve the problem now:

With full admin rights to the entire Netware tree and everything below we can not figure out how to create Pervasive DSN's through PCC on the clustered volume VOL1.  In PCC during Create DSN, when we attempt to set the destination folder to anywhere on SYS it works.  If we point to VOL1 where we really need it we get the message "Cannot create database name. You do not have sufficient access rights for the operation or the destination directory does not exist".  Bummer...

How do we get Pervasive to know that VOL1 is a 100% valid destination?  I would very much appreciate help to solve this.  We have newly created DBNAMES.CFG (so that's not it),  it is not set R/O, and again we are attempting this with all rights.    Many thanks.  Jim.

You may be running into problems with long directory names.  To use long name space, you MUST have the data volume mounted BEFORE you load the database engine!  With a clustered environment, this is often not the case, as the clustered volume can mount any time.

Verify your cluster scripts.  When a server becomes the cluster host, it should be shutting down the database engine BEFORE mounting the volume, then mount the volume, and then restart the engine.  This will look something like this:

    MGRSTOP
    BSTOP
    MOUNT VOL1:
    MGRSTART

Test the script first to make sure that the engine shuts down all the way.  You may need a BTRV UNLINK command in there, still.  (Haven't ever tried with v9.5.)

 

I believe my cluster load script lines up as you suggest (see below).  On a fresh cluster start with the script working properly PCC is still telling me I do not have sufficent rights when I attempt to create a new database on the clustered volume.  I very much appreciate your help and further ideas.  I have worked many hours on this.  Many thanks, Jim

==================

mgrstop
bstop

nss /poolactivate=VOL1_POOL
mount VOL1 VOLID=254
CLUSTER CVSBIND ADD M3C_CLUSTER_VOL1_POOL_SERVER 192.168.2.107
NUDP ADD M3C_CLUSTER_VOL1_POOL_SERVER 192.168.2.107
CIFS ADD .CN=M3C_CLUSTER_VOL1_POOL_SERVER.O=main.T=M3C.
add secondary ipaddress 192.168.2.107

bstart
mgrstart

=================

 OK -- it may sound backwards, but can you create the DB on SYS and then move it?

The best way top debug this one is probably to enable MKDE Tracing on the server and then see what falls out of it as an error.  It may point to something a bit more useful than the generic error message. 

Yes,  That is how we have been suriviving these last years - creating the DSN on SYS then changing the folder pointer in PCC "Maintain Databases" to VOL1 after we physically move the database to VOL1 (see my original post).  I need to get this right now.  I will enable MKDE tracing, see what is there and post again.  Many thanks. Jim

I found the answer:

When specifying the location of the new Database do not use a server reference as the PCC {Browse] button defaults to inserting. 

Instead of using (in my case) \\M3C_CLUSTER_VOL1_POOL_SERVER\VOL1:\MYFOLDER,

just use \VOL1:\MYFOLDER. 

Thanks for you help