Who's On?

	Membership:
	Latest: Steve G
	Past 24 Hours: 0
	Prev. 24 Hours: 0
	Overall: 5242

	People Online:
	Visitors: 86
	Members: 0
	Total: 86

Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chesca	1042

long running program

4 Replies

0 Subscribed to this topic

17 Subscribed to this forum

Sort:

Author

Messages

Sheila Kendall

New Member

Posts: 0

6/21/2012 10:25 PM

We have two custom programs that read in PMTOUT. One program read the employee table to get the employee status (so was a direct read). On one server/productline, it took 17 minutes. On the other productline (productin unfortunately), it took 1 and 1/2 hours. Then we took the database read out, so that it was just reading in PMTOUT and writing out a revised PMTOUT. It now takes 5 seconds in both productlines.
The second program is similar but we need to keep the database reads in (to read a history table). It takes 1 1/2 hours in one server and 5 hours on the other.

Our system staff do not see any unusual activity. ANy clues anyone?

THis is by the way, since we went to 9.0.1 application and environment, Oracle 11 g and we are on AIX 6

Ragu Raghavan

Veteran Member

Posts: 477

6/21/2012 10:51 PM

did you try running the verifyoraxx utlility ? That may show any missing indices.

Sheila Kendall

New Member

Posts: 0

6/30/2012 1:22 AM

Yes, the dba checked that. We are also having intermittent performance issues with online access. Not sure if they are related or not. We have all of the environment patches in at this point.

JudeBac

Veteran Member

Posts: 129

6/30/2012 1:55 AM

Add the company code, then the employee number. This will help you index

David Arago

Basic Member

Posts: 4

6/30/2012 1:57 AM

I am on vacation until July 9th. If you need help please e-mail the helpdesk.