googers
Member
Hello
We seem to be getting slow runtimes (20 hours) time when the followong occurs:
Scenario:
We run runbatches on our FAST Unix server that access a lot data (i.e. select * from proddta.F0911 ) from our Oracle 9.2.0.3 database. This is true even if nothing else is running on our Unix application server.
Even more interesting is if we run this same job locally on a Fat client on a SLOW windows PC, the job runs rather fast (2 hours).
TESTING:
We have tested running "Select * from proddta.f0911" using Sqlplus from both the Unix server and the Pc that has the fat client and when this occurs they both run equally fast (about 2 hours). This leads to think it is not in our netwok or sqlnet connection from the Application Server to the Database Server.
We have done oracle traces for the this job running on both scenarios (PC and Unix Server). These traces indicate that Oracle is waiting much longer for a message from the client process for more data (SQL*Net message from client) on the Unix Server than oracle waits for the same job running on the PC. The total time difference between the PC and Unix Server for "SQL*Net message from client" messages is about the total difference in runtimes (17.4 hours).
Possible Reasons:
This makes me think that the unix server is:
A) slow when it comes to processing JDE runbatches do to the JDE code as written.
B) We have some configuration issues
In our JDE.INI on our UNIX (See Below) server we have the folowing parameters set up. Could this be slowing our processing of runbatches on our Unix App server that access large amounts of data?
[DB CACHE INFORMATION]
ODBC Tables=50
Maximum Request Cache=50
Library Cache=15
If anyone has any ideas about how to address this, We woud be most appreciative.
Thank you.
Googers
OneWorld XE SP22_E1/Unix Solaris 8/oracle 9.2.0.3
We seem to be getting slow runtimes (20 hours) time when the followong occurs:
Scenario:
We run runbatches on our FAST Unix server that access a lot data (i.e. select * from proddta.F0911 ) from our Oracle 9.2.0.3 database. This is true even if nothing else is running on our Unix application server.
Even more interesting is if we run this same job locally on a Fat client on a SLOW windows PC, the job runs rather fast (2 hours).
TESTING:
We have tested running "Select * from proddta.f0911" using Sqlplus from both the Unix server and the Pc that has the fat client and when this occurs they both run equally fast (about 2 hours). This leads to think it is not in our netwok or sqlnet connection from the Application Server to the Database Server.
We have done oracle traces for the this job running on both scenarios (PC and Unix Server). These traces indicate that Oracle is waiting much longer for a message from the client process for more data (SQL*Net message from client) on the Unix Server than oracle waits for the same job running on the PC. The total time difference between the PC and Unix Server for "SQL*Net message from client" messages is about the total difference in runtimes (17.4 hours).
Possible Reasons:
This makes me think that the unix server is:
A) slow when it comes to processing JDE runbatches do to the JDE code as written.
B) We have some configuration issues
In our JDE.INI on our UNIX (See Below) server we have the folowing parameters set up. Could this be slowing our processing of runbatches on our Unix App server that access large amounts of data?
[DB CACHE INFORMATION]
ODBC Tables=50
Maximum Request Cache=50
Library Cache=15
If anyone has any ideas about how to address this, We woud be most appreciative.
Thank you.
Googers
OneWorld XE SP22_E1/Unix Solaris 8/oracle 9.2.0.3
