We're in the process of migrating from P.SQL V8.6 on a Netware 5.1 SP8
server using a tradational file system to P.SQL V9.5 on an OES/Netware
SP2 server using NSS file system.

Most of this is working fine. We can take a backup of the database from
the old server, restore it onto the new server and access the database.

Appart from data stored in tables with long file names. When I try to
open these in the PCC I get back and error:

[LNA][Pervasive][ODBC Engine Interface][Data Record Manager]The MicroKernel cannot find the specified file(Btrieve Error 12)

I also get the same error when I create a new table on the P.SQL V9.5
server using a command such as

create table guytest using 'guydawson.mkd'
(
....
);

I can create the table without a problem but when I try to access the
data I get error 12 back.

This is a known problem? Is there a work around? I'd like to avoid having
to rename all the long file name tables on the old system...

Guy
-- --------------------------------------------------------------------
Guy Dawson I.T. Manager Crossflight Ltd
gnues (AT) crossflight (DOT) co.uk

It's a known problem, and it's been asked on this forum numerous times.

Make sure that your volume is mounted BEFORE loading either the
database (BSTART) or the network drivers (INITSYS).

This is best done by adding the command "MOUNT ALL" to the AUTOEXEC.NCF
file as soon after the FILE SERVER... line as you can.
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - 03/2007 ***


Guy Dawson wrote:

Bill Bach wrote:
Doh! Probably asked by me too. Double Doh!

Thank you for your help and patience!

Guy


--
Guy
-- --------------------------------------------------------------------
Guy Dawson I.T. Manager Crossflight Ltd
gnues (AT) crossflight (DOT) co.uk

Guy Dawson wrote:
Except that I've moved the MOUNT ALL command:

# WARNING!!
FILE SERVER NAME MUSTANG
# WARNING!!
# If you change the name of this server, you must update
# the server name in all the licenses that are assigned
# to it using iManager.
SERVERID 9D27804
# MOUNT ALL moved earlier in the load sequence. In particular, before
# INITSYS.NCF and BSTART.NCF to work around a problem Btrieve/P.SQL
# has with long file name support
MOUNT ALL

and I'm still have same problem with long file names.

As I understand it, NSS has long file name support built in and does
not need to be enabled with the LONG command that was needed for the TFS.
Could this be tripping P.SQL up?

Guy
-- --------------------------------------------------------------------
Guy Dawson I.T. Manager Crossflight Ltd
gnues (AT) crossflight (DOT) co.uk

Shouldn't be a problem. If you type VOLUMES at the server console, you
should see that the volume has LONG name support already. Are short
filenames working correctly?

Just a suggestion -- try watching the startup process and make sure
that the volumes are actually mounted before the INITSYS fires. It
could be that the volumes are not yet fully operational by the time the
engine starts.
Goldstar Software Inc.
Pervasive-based Products, Training & Services
Bill Bach
BillBach (AT) goldstarsoftware (DOT) com
http://www.goldstarsoftware.com
*** Chicago: Pervasive Service & Support Class - 03/2007 ***

Guy Dawson wrote:

Bill Bach wrote:
Yes, all volumes have LONG name support.

Yes. They're working fine.

Will do.

Thanks for the pointer.


--
Guy
-- --------------------------------------------------------------------
Guy Dawson I.T. Manager Crossflight Ltd
gnues (AT) crossflight (DOT) co.uk