The forum will be unavailable for maintenance at some point from Friday, April 13 at 19:00 EDT until Sunday, April 15 at 23:59 EDT. Downtime will be minimized but the exact timing is unknown.

  • Server has 160 G RAM available, normal workload at 35 G RAM
  • DB size 80 GB - dbvalid (-fx) takes 10 hours
  • In the last 2 hours (hour 8 to 10) the workload suddenly is going up to 130 G.

Can anyone tell me whats the dbvalid process (with -fx option) do in the last chapter of validation in SB16 EBF 1915? Which part of dbvalid needs suddenly 100 G of cache ??

asked 12 Dec '17, 04:48

pmiller's gravatar image

accept rate: 37%

edited 12 Dec '17, 04:52

I can't tell that but two remarks:

  1. When you use the VALIDATE statements or the sa_validate() procedure, they write their actions to the console log which does also contain messages for cache resizing. That might help to find out what validation step does increase the cache that much.
  2. Build is rather old, current builds are in the range, so in case that is a bug, trying with a newer EBF might help.

This forum has several FAQs on the (not too obvious) connections between DBVALID's options and the according statement variants and parameters, like this one.

permanent link

answered 12 Dec '17, 06:31

Volker%20Barth's gravatar image

Volker Barth
accept rate: 32%

edited 12 Dec '17, 07:41

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here



Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text]( "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:


question asked: 12 Dec '17, 04:48

question was seen: 165 times

last updated: 12 Dec '17, 07:41