Conference orarep::nomahs::repository

1060.0. "-LIB-F-INSVIRMEM on CDO> VERIFY/ALL/NOFIX" by svrav1.au.oracle.com::AMENDOZA () Mon Mar 03 1997 03:26

Hi,

Our customer has a central cdd repository that they are trying desperately
to verify (verify/all/nofix) with no success.   It always fails with: 

	-LIB-F-INSVIRMEM, insufficient virtual memory

Realising that this error could be only be attributed to the relative size of 
their repository, we tried increasing the process quotas, system page files 
and virtualpagecnt on the machine but still we are getting nowhere.   The 
verify could run for several days without finishing until the job is either 
aborted or the machine simply crash.  RMU/VERIFY/ALL on the CDD$DATABASE 
runs clean however.

Typical quotas used by customer are:
	virtualpagecnt = 800,000
	pgflquota      = 700,000  
	wsquota        =  44,000
	wsextent       = 100,000

I obtained a backup of the same repository and tried verifying it on an 
Alpha 2100 (Main Memory: 128.00Mb) running CDD V6.1-02 and Rdb V6.0-16 
on VMS V6.2.   

CDO verify/fix/orphan has been running now for more than 2 days without
finishing.  The process in virtually in "PFW" state all the time.

	Working set             4096    
	Virtual pages          31768
	CPU time       0 02:22:25.66
	Direct I/O            548016
	Buffered I/O             784
	Page faults        127001763
Quotas:
	VIRTUALPAGECNT 	     1500000   pagelets
	  internal value       93750   pages
	Pgflquo     	      600000
	Bytlm       	     1024000
	JTquota        		4096
	WSdef         	       65000
	WSquo         	       65000
	WSextent      	       65000
	Pgflquo      	      600000

I also tried defining bigger values for cdd$max_objects_in_memory but with
no success.

Is there a limitation on the size of the repository we can successfully
verify?   I did tried to suggest to the customer to break down his repository
into several manageable ones.   However, he told me that it used to be that
they have a dozen repositories before until it was recommended to them
to consolidate these into one because of the external references problems 
that they keep on having at that time.    

Does CDD requires heaps of memory in verifying its objects?   Any suggestion
on what we can do to overcome this problem?


thanks,
albert.

It turned out that the verify finished after almost 4 days processing.
Increasing working set for the process and definition for
cdd$max_objects_in_memory also helped.   

   dd$max_objects_in_memory   50,000

        VIRTUALPAGECNT       1500000   pagelets
          internal value       93750   pages
        Pgflquo               600000
        Bytlm       	     1024000
        JTquota                 4096
        WSdef   	       65000
        WSquo                  65000
        WSextent               65000
        Pgflquo               600000

Accounting information:
 Buffered I/O count:      1034  Peak working set size:      65536
 Direct I/O count:      476260  Peak virtual size:         571584
 Page faults:        129710965  Mounted volumes:                0
 Images activated:  25
 Elapsed CPU time:          0 02:27:03.16
 Connect time:              3 20:34:11.30

Alpha 2100 main memory = 128 Mb

Indeed, verify uses a lot of memory!    

cheers,
albert