Hi Stephen, QUERYOPTimization is an undocumented option. In general, it is only to be used when service suggests it as a way to turn off query optimization as a workaround, if query related issues occur. The option continues to work in the latest release, but it should not be needed. Upgrading to the latest release is the suggested solution to these problems. If it is found to be needed in the latest release, a PMR should be opened. The default is that the option is not used and query optimization is turned on. Query optimization provides better performance which becomes more noticeable as the number of number of databases involved increases.
---------------------------------------------------------------- Angela Robertson IBM Software Group Durham, NC 27703 [email protected] ---------------------------------------------------------------- "ADSM: Dist Stor Manager" <[email protected]> wrote on 08/22/2013 10:43:00 AM: > "Stackwick, Stephen" <[email protected]> > Sent by: "ADSM: Dist Stor Manager" <[email protected]> > > 08/22/2013 10:43 AM > > Please respond to > "ADSM: Dist Stor Manager" <[email protected]> > > To > > [email protected], > > cc > > Subject > > [ADSM-L] queryoptimization - what is it? > > We have 6.3 SQL TDPs that were getting: > > ACO5422E CSqlApi::GetSqlDatabaseInfoOpt3 > > errors, even if we excluded the databases causing the messages. > Short story, the backup still looks like it fails, even though the > databases we care about are getting backed up fine. Following Del's > recommendation on this list, we set QUERYOPTIMIZATION 0 in the > tdpsql.cfg file, and the messages go away. > > My customer (and I) would like to know what this option does. I > haven't been able to find it mentioned in the manual. > > Thanks! > > STEPHEN STACKWICK | Senior Consultant | 301.518.6352 (m) | > [email protected]<mailto:[email protected]> | icfi.com< > http://www.icfi.com/> > ICF INTERNATIONAL | 410 E. Pratt Street Suite 2214, Baltimore, MD > 21202 | 410.539.1135 (o) >
