I think the feedback is great, but because you are just starting and do not have a lot of experience in resolving this issue I think it would be beneficial to post your event action code here so the community can give you some direct code suggestions to resolve your issue.Once we see the code and can offer a workaround we can explain what method was used and why.
What a great question. To help provide advice I need to know more about your Oracle instance. These are pretty basic questions, but will give me an idea of how resources are assigned to the database.What version of Oracle? Can you please provide a dump of your Oracle initialization parameters? How much memory is installed on the server? Is this the only database on the server or are there multiple instances?"latch: cache buffers chains" contention is typically encountered because SQL statements read more buffers than they need to, and multiple sessions are waiting to read the same block.If you have high contention, you need to look at the statements that perform the most buffer gets and then look at their access paths to determine whether these are performing as efficiently as you would like. Hopefully we can identify queries that are not utilizing an index, create the index, and thereby decrease the number of blocks that need to be read. We can’t change the query in IFS, but we can ad
Thank you for the update. 4 Billion buffer gets (4,157,385,699) is a high number and the time spent on the query is high at about 1.5 minutes. Can you please provide the definitions for all indexes on the following objects. The explain plan you provided shows that some full scans are being performed.WORK_ORDER_CODING_UIV PURCHASE_REQ_LINE_TAB PURCHASE_PART_GROUP_TAB WORK_ORDER_CONNECTIONAre you able to use base tables in place of WORK_ORDER_CODING_UIV or WORK_ORDER_CONNECTION? These VIEWs might be adding overhead for the columns you are referencing.
You are missing indexes on some objects and the select statement could use improvement. Ideas,Select only the unique records from the last inner select statement.OLDSELECT WC.CONNECTED_WO_NOFROM WORK_ORDER_CONNECTION WCSTART WITH WO_NO = :B1CONNECT BY PRIOR WC.CONNECTED_WO_NO = WO_NONEWSELECT UNIQUE WC.CONNECTED_WO_NOFROM WORK_ORDER_CONNECTION WCSTART WITH WO_NO = :B1CONNECT BY PRIOR WC.CONNECTED_WO_NO = WO_NO Add a non-unique index on the PURCHASE_PART_GROUP_TAB table for the column C_PUR_GRP_CATEGORY. Add a non-unique index on the PURCHASE_REQ_LINE_TAB table for the column ROWTYPE. Change the selection of WORK_ORDER_CODING_UIV to WORK_ORDER_CODING_TAB and the where statement ““WOC.WORK_ORDER_COST_TYPE_DB = :B3”” to “WOC.COST_TYPE = :B3”. This will drive down the cost and number of blocks required by the query. Add a non-unique index on the table WORK_ORDER_CODING_TAB for the following columns; REQUISITION_NO, REQUISITION_LINE_NO, REQUISITION_RELEASE_NO, COST_TYPE, WO_NOLets see what
have you tried setting a password that is in all UPPERCASE?
I’m part of the DSI ScanWorks integration team. I’m happy to answer your questions. What information are you looking for?
If you drop me an email to alan.clark@dsiglobal.com I can setup an introduction to ScanWorks and the integration suite it is built with.
If the issue is resolved by the user running IFS from another laptop logged in as a different Windows account, then the issue is with Windows permissions and not IFS.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.