Hello, We are inserting data into 9.5 on AIX through Datastage. After runstats, the data being inserted was fast. It's been 3 weeks since runstats has been done and the new set of inserts have already been started. The inserts are very slow now and I want to do runstats with 'allow write access'. As per IBM's documentation,
ALLOW WRITE ACCESSSpecifies that other users can read from and write to the tables while statistics are calculated. For statistical views, these are the base tables referenced in the view definition.
The ALLOW WRITE ACCESS option is not recommended for tables that will have a lot of inserts, updates or deletes occurring concurrently. The RUNSTATS command first performs table statistics and then performs index statistics. Changes in the table's state between the time that the table and index statistics are collected might result in inconsistencies. Although having up-to-date statistics is important for the optimization of queries, it is also important to have consistent statistics. Therefore, statistics should be collected at a time when inserts, updates or deletes are at a minimum.
In our case, there are no other applications using those tables except this Datastage job doing sequential inserts. Is it a good idea to do runstats in our scenario?