We have DS jobs in aix server which are running fine. Small job with 1800 rows take about 5 sec to complete. Simple load (source drs, transformer and target DRS). Source and Target DB's are DB2.
Now, we got a new server and asked our unix admin to install DS. He couldnot find the software so he took the tar file from the old server and installed in this new server.
Now, when we run the same job that runs in 5 sec , it is taking 15 min to run. I worked with our Unix admins, to see if there is any issue, check the ODBC connections they are fine, checked the dsenv file, its same as the one on the other server. Checked our DB2 Connect and it is fine. Donot know what else to look for..
Appreciate if anyone can throw some light on where I can look for to fix this issue.
Thanks
Jobs running slow in new server when compared to old server.
Moderators: chulett, rschirm, roy
You need to find out which part has gotten slower. Measure the speed of the job, then make a copy and repalce everything after the initial DB2 read stage with a sequential file writing /dev/null. Run that new job. If the speed is similar to the original job then most likely the DB2 read is not causing the bottleneck. Make another copy of the job and output to a sequential file, ignore the runtime for the moment. Make yet another copy which only has the sequential file write to DB2. What is that speed compared to the original? If it is the same then the DB2 write isn't the bottle neck. Continue this approach to isolating the elements until you have found the stage that is causing the slowdown.
By the way, 5, 10 or even 30 seconds is a very short interval to use for measuring performance. I usually try for 5 or 10 minute runtimes and several runs in order to get comparable numbers.
By the way, 5, 10 or even 30 seconds is a very short interval to use for measuring performance. I usually try for 5 or 10 minute runtimes and several runs in order to get comparable numbers.
-
- Charter Member
- Posts: 193
- Joined: Tue Sep 05, 2006 8:01 pm
- Location: Australia
firstly i would suggest downloading thesoftware off the IBM site. doing an install from a tar file is not the right thing to do. you might get it to work but that is not a proper installation and is fraught with traps.
if you already have the license keys,then the installing the downloaded copy should be fine. why not do that first before trying too many other things?
btw is your new server the same specs as the old one?
if you already have the license keys,then the installing the downloaded copy should be fine. why not do that first before trying too many other things?
btw is your new server the same specs as the old one?
-
- Premium Member
- Posts: 385
- Joined: Wed Jun 16, 2004 12:43 pm
- Location: Virginia, USA
- Contact:
AIX includes features that allow systems to be logically partitioned. If you are running in a partition, versus the entire system, ensure that the partition is giving you enough resources (CPU, memory, etc). A partition can be as small as 1 percent of a CPU.
Chuck Smith
www.anotheritco.com
www.anotheritco.com
*****************chucksmith wrote:AIX includes features that allow systems to be logically partitioned. If you are running in a partition, versus the entire system, ensure that the partition is giving you enough resources (CPU, memory, etc). A partition can be as small as 1 percent of a CPU.
Hi Chuck,
We are still having issues with the jobs. They are running slower when compared to other servers. We have involved DBA's and Db2 programmers to find out what is taking more time. What we found out is in the server that our jobs running slow,
An insert statement is being executed everytime job is run..
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
INSERT
INTO SYSIBM.SQTTABLES
SELECT NULLIF('A', 'A'), RTRIM(CREATOR), NAME,
CASE
WHEN TYPE = 'A' THEN 'ALIAS'
WHEN TYPE = 'V' THEN 'VIEW'
WHEN TYPE = 'T'
AND CREATOR <> 'SYSIBM' THEN 'TABLE'
WHEN TYPE = 'T'
AND CREATOR = 'SYSIBM' THEN 'SYSTEM TABLE'
WHEN TYPE = 'X' THEN 'AUXILIARY TABLE'
WHEN TYPE = 'G' THEN 'GLOBAL TEMPORARY TABLE'
ELSE TYPE
END, VARCHAR(REMARKS, 254), CAST(NULL AS VARCHAR(128)), CAST(NULL
AS VARCHAR(128)), CAST(NULL AS VARCHAR(128)), CAST(NULL AS VARCHAR
(128)), CAST(NULL AS VARCHAR(128)), RTRIM(DBNAME)
FROM SYSTABLES
WHERE STRIP(CREATOR, T) LIKE :H ESCAPE :H
AND NAME LIKE :H ESCAPE :H
AND STRIP(DBNAME, T) LIKE :H QUERYNO 1
&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&&
But in other servers this isnot being done. The above insert statement is taking almost 10 min. Our Db2 folks are telling that this has to do only once and it should not do everytime. They are asking us to check in the application.
After the above insert statement is done, job takes only a minute to run like in our other server.
Can anyone shed some light !!
Thanks.