Hi Team,
Windows 10, EDBServer 64bit.  32bit Apps.
I have a couple of tables that verify as follows..
Live - 280259 Records - Verify - Structure+ - Approx 5 sec.
Archive - 6462 Records - Verify - Structure+ - Approx .5 sec.
If I Archive some records from the Live to the Archive using the following script..
{sql}
SCRIPT (IN EndDate Date)
BEGIN
  EXECUTE IMMEDIATE 'insert into aChangesLog
  select * from ChangesLog
  WHERE
  (CAST(DateTime AS DATE) < ?)
  AND
  (
  (KeyValue is NULL)
  OR
  ((Trim(BOTH '' '' FROM KeyValue) NOT IN (SELECT CAST(JobNo AS VARCHAR) FROM JobTickets))))' USING EndDate;

  EXECUTE IMMEDIATE 'delete from ChangesLog
  WHERE
  (CAST(DateTime AS DATE) < ?)
  AND
  (
  (KeyValue is NULL)
  OR
  ((Trim(BOTH '' '' FROM KeyValue) NOT IN (SELECT CAST(JobNo AS VARCHAR) FROM JobTickets))))' USING EndDate;
END
{sql}
Then if I try to Verify again I get the following..
After Archive:
Live - 164019 Records - Verify - Structure+ - 5 minutes and still no sign of any progress.  Now 10 minutes.
Archive - 122702 Records - Verify - Structure+ - Approx 17 sec.
See relevant attached pictures.

Anybody got any thoughts as to what is going on, or not?

Regards & TIA,
Ian

There should be 3 pictures..

and another.

More info.
I have discovered the EDBServer is running/fluctuating around 30% CPU and 200MB.

Pity there is no edit.
The server is EDBServer 64bit.  There is plenty of RAM available.  I7 processor.

OK.  Fully stopped the server and restarted.  Ran the verify process again, only running at 10-11% around 50MB.
Aborted the App, Server still running, presumably with the verify.  Still at 10-11%.
I suspect the earlier figures were a result of retrying.
Been 10 minutes now and the verify is ostensibly still running on the server.
Aborting the Server service.

Ian


The only thing I can think of as a first attempt is to run REPAIR TABLE on the live file and see if that fixes it.

Before you do it copy the live and archive files and the catalog to one side to send to Tim.

Roy Lambert

Ian


Second thought - what happens if you try locally rather than c/s?

Roy Lambert

On 8/26/2019 5:21 AM, Ian Branch wrote:
> OK.  Fully stopped the server and restarted.  Ran the verify process again, only running at 10-11% around 50MB.
> Aborted the App, Server still running, presumably with the verify.  Still at 10-11%.
> I suspect the earlier figures were a result of retrying.
> Been 10 minutes now and the verify is ostensibly still running on the server.
> Aborting the Server service.


Outside of disk caching i don't think verify can really use much (ram)
anyways - i always thought of it as serial operation of reading pages
and index and data, doing some hashing or validation and moving on.

1. Do you have progress reporting enabled ? That also helps with any
idle session timeouts

2. Are you using Global I/O buffering ?

Raul

Same result.