Re: Index advisor and system cross-reference files -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Subject: Re: Index advisor and system cross-reference files
From: satya tiruveedhi <satyatiruveedhi@xxxxxxxxx>
Date: Wed, 2 Sep 2015 01:06:32 +0530
List-archive: <http://archive.midrange.com/midrange-l/>
List-help: <mailto:midrange-l-request@midrange.com?subject=help>
List-id: Midrange Systems Technical Discussion <midrange-l.midrange.com>
List-post: <mailto:midrange-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/options/midrange-l>, <mailto:midrange-l-request@midrange.com?subject=unsubscribe>

Rob,

Thanks for the information. Hopefully, we will get the latest TR with fixes
to Index advisor by the time we upgrade to production LPAR. If the problem
continues, I will ask our AS400 administrator to open PMR.

We use custom ERP package which uses multiple web servers (JBOSS on linux,
ASP.net on windows), all of them use JDBC to connect to the iseries. Also,
we have BI reporting tools (using JDBC) which allow business users to write
their own reports. It is possible that when JDBC is requesting metadata on
result set, it is getting translated into access to syscolumns (QADBIFLD).
I need to investigate further to identify what is causing it.

Thanks..

Satya..

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

Re: Index advisor and system cross-reference files , rob

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.