Results 1 to 3 of 3
  1. #1
    Join Date
    Sep 2002
    Posts
    3

    Unhappy Unanswered: PSQL SP3 Problems

    We've recently installed SP3 on our Netware Server and have been getting continuous Error 2's on our 2 biggest files. They have about 400,000 records in each of them. This is a copy of one of our PVSW.LOG file lines. We are on NW 5 SP6.

    09:49:32 NWMKDE 0000009A NWMKDE.NLM AMD1 I System Error: 116.6.0 File: APP:MAX31/AMD/SOEDET.DAT
    09-04-2002 09:51:08 NWMKDE 0000009A NWMKDE.NLM AMD1 I System Error: 116.6.0 File: APP:MAX31/AMD/SOEDET.DAT

    These error 2's are claiming that they are corrupt tables but at least twice per week we have to get everyone out to rebuild the tables. Once we rebuild them everything is ok for a few days.

    I suspect the problem lies with the BTI.CFG which since I can find no good tuning interface to set the files up I will copy along with this message.

    [InstallInfo]
    InstallDir=p:\PVSW
    SystemDir=p:\system
    InstallIniName=PTKSETUP.INI
    VersionLevel=7.90
    PatchLevel=3
    BuildLevel=230

    [Database Names]
    DBNamesDirectory=SYS:/SYSTEM/mkde

    [MicroKernel]
    MaxFiles=3000
    MaxCursors=6000
    BalancedTrees=NO
    ForceFileVersion=0700
    SystemData=YES
    MaxDatabases=100
    Logging=NO
    CacheSize=110196
    CompressedBufferSize=5
    ExtendedBufferSize=4096
    MergeSortBufferSize=0
    MaxRecSize=63
    CachePartitioning=NO
    TransDurability=YES
    TransLogBufferSize=64
    TransLogFileSize=512
    SysTransBundleLimit=65535
    SysTransTimeLimit=10000
    MaxClients=500
    BackgroundThreads=64
    WaitLockTimeout=1
    TransLogDirectory=SYSYSTEM/MKDE/LOG
    WorkDirectory=
    Trace=NO
    TraceFile=SYS:/SYSTEM\MKDE.TRA
    TraceDataBufferLength=32
    TraceKeyBufferLength=32
    TraceOpsList=ALL
    LoadRouter=NO
    RouterCommBufferSize=63
    RuntimeServerSupportMode=0000

    Use FileIO Mutex=YES
    Validate Request=NO
    [Btrieve Interface]
    Embedded Spaces=NO

    [Btrieve Communications Manager]
    MaxWorkerThreads=100
    MaxRecSize=65116
    MaxClients=4096
    MaxReceivePacketSize=4096
    Use SAP=AUTODETECT

    Supported Protocols=SPX,TCPIP
    Listen IP Address=
    TCP/IP Multihomed=YES
    Enable AutoReconnect=YES
    AutoReconnect Timeout=180


    Any help you give will be greatly appreciated.

  2. #2
    Join Date
    Jan 2002
    Posts
    10
    Two or three possibilities come to mind:

    (1) Novell has a history of "Phantom Status 2" problems. In this case, the status 2 is not 'Real'. It is a result of a problem in Novell's TurboFat.

    To test this - when the error occurs next, copy **WITH DOS/WINDOWS COPY, NOT NCOPY** the data file getting the error 2 to another drive (a local PC drive is ideal). After this is done, delete the original file, and copy the data back to the original location. Now, open and work with the file. Does it return Status 2s? If not, then the TurboFat fix is the most likely to fix the issue.

    You can get the TurboFat fix for Novell NW5 from Novell, but it takes some hunting to find. Get it from Goldstar Software's site:

    TurboDis File Download

    This is for Novell 4/5/ and 6. Read carefully before installing.

    (2) There is a status 2 issue in PSQL SP3 that is fixed in SP4. If you are using SP3, see if this is the issue:

    Pervasive Knowledgebase Article

    (3) Does your server use PIII processors? Is your SP < 2? Read this article, and then hunt around on Novell's site:

    Google Groups Message
    Brendt

    We are the music makers, and We are the dreamers of dreams...

  3. #3
    Join Date
    Sep 2002
    Posts
    3

    Lightbulb

    We'll try it this weekend and see what happens we've tried BTI.CFG changes but the error only happens on large files so it smells like the TurboFat issue. We never got these errors before upgrading to SP3 and NW SP6 though so hopefully the turbodis fix will work. SP4 of Pervasive is supposed to break one of our canned applications so we haven't done it yet. Thank you very much for your help.

    Garrett

    Originally posted by BrendtHess
    Two or three possibilities come to mind:

    (1) Novell has a history of "Phantom Status 2" problems. In this case, the status 2 is not 'Real'. It is a result of a problem in Novell's TurboFat.

    To test this - when the error occurs next, copy **WITH DOS/WINDOWS COPY, NOT NCOPY** the data file getting the error 2 to another drive (a local PC drive is ideal). After this is done, delete the original file, and copy the data back to the original location. Now, open and work with the file. Does it return Status 2s? If not, then the TurboFat fix is the most likely to fix the issue.

    You can get the TurboFat fix for Novell NW5 from Novell, but it takes some hunting to find. Get it from Goldstar Software's site:

    TurboDis File Download

    This is for Novell 4/5/ and 6. Read carefully before installing.

    (2) There is a status 2 issue in PSQL SP3 that is fixed in SP4. If you are using SP3, see if this is the issue:

    Pervasive Knowledgebase Article

    (3) Does your server use PIII processors? Is your SP < 2? Read this article, and then hunt around on Novell's site:

    Google Groups Message

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •