Portal Clear cache job causes lot of archive logging once per hour

Clearing the Cache Invalidation Queue Through SQL*PLUS
Sometimes the cache invalidation queue may grow excessively large as a result of user actions.�

For example, repeated granting of security privileges on a page to a group with a large number of members will place one soft invalidation in the queue per user per grant.

Some soft invalidations may not be necessary but the Portal may not be able to determine this. For example, if a group's privileges on a page were upgraded from 'View' to 'Fully Customize' but no member of the group had yet viewed the page then no invalidation is necessary. However, Portal does not have a record of who has viewed the page so therefore the only choice is to proceed with the soft invalidation associated with the security change.

The Portal administrator can check the number of soft invalidations in the queue by executing the following query in SQL*PLUS as the Portal schema owner

select count(1) from wwutl_cache_inval_msg$ where process_type=2;
The Portal administrator can check the total number of invalidations, hard or soft, in the queue by executing the following query in SQL*PLUS as the Portal schema owner

select count(1) from wwutl_cache_inval_msg$;
The number of rows in the table wwutl_cache_inval_msg$ that can be considered excessive depends to some extent on the speed of the infrastructure running the database. However, typically 50 000 messages will cause the soft invalidation job to take a long time to process and sending 50 000 invalidation messages to Web Cache will introduce network load as Portal communicates with the Web Cache invalidation port.

If the soft invalidations are known to be unnecessary then the Portal administrator can perform the following query in SQL*PLUS as the Portal schema owner

delete from wwutl_cache_inval_msg$ where process_type=2;
This removes soft invalidations from the queue.

If the soft invalidations are necessary but there is an excessively large number then the Portal administrator can clear the cache invalidation queue using the following command:

truncate table wwutl_cache_inval_msg$;
The Portal administrator should then clear the entire cache through the Portal UI as described in the next section.

�to Top

Clearing the Entire Cache Through the Portal UI
The Portal administrator may sometimes want to clear all cached Portal data. This is done as follows:

Navigate to the Portal Builder Administer tab.
Select the Global Settings link.
Select the Cache tab.
Select the 'Clear The Entire Web Cache' checkbox.
Press Apply or OK.
This performs a hard invalidation so that the cache is cleared immediately.