Parameter tuning - DLThreadswrite DLThreadprepare

To improve the data load performance, we should increase the parameter DLThreadwrite and DLThreadprepare.
However I read from Oracle documentation it seems that the parameter only apply to BSO instead of ASO. Any other parameters can be used to improve ASO data loading?
Thanks!

GlennS_2 wrote:
Perhaps I mistakenly thought that both those parameters seemed to help ASO performance. One thing you can do (If you are on EPM 11 or 9.3.1) is to use multiple data laods at the same time into different load buffers and then commit them together. It willrequire you using multiple MaxL scripts, but is quite doableThanks for your advice. I also checked Oracle documentation that we can perform data load in parallel using different buffer ID to improve the performance. However it requires some changes on the application design to break down the data load into several batch script.

Similar Messages

DB_BLOCK_BUFFERS PARAMETER TUNING(ORACLE7)

제품 : ORACLE SERVER
작성날짜 : 2002-04-12
DB_BLOCK_BUFFERS PARAMETER TUNING(ORACLE7)
==========================================
Purpose
Oracle7 version의 database에서 db block buffer의 값이 적당한 지를
알아보고 Tuning 하는 방법을 알아보자.
Explanation
1. DB_BLOCK_BUFFERS parameter
(1) SGA 내 메모리에 캐쉬되는 데이타베이스 블럭의 수
(2) SGA 사이즈와 데이타베이스 성능을 결정하는 가장 중요한 요소이다.
(3) 높은 값을 갖게 되면 해당 블럭을 메모리에서 찾게 되는 빈도가 많아지기
때문에 디스크 입출력을 줄일 수 있지만, 보다 많은 메모리를 소모하게 된다.
2. 적정한 값 찾기
(1) 다음의 SQL문을 수행시켜 ratio 필드의 평균 값이 92% 이상이어야 한다.
- DBMS가 STARTUP 후부터 현재까지의 누적치를 보여준다.
- 현재의 HIT RATIO를 보려면 두 번 수행하여 차액을 갖고 계산한다.
rem
rem connect as system user id
rem
col logical_reads format 999,999,999,999
col physical_reads format 999,999,999,999
col physical_writes format 999,999,999,999
select a.value + b.value logical_reads,
c.value physical_reads,
round(100*(a.value+b.value-c.value)/(a.value+b.value),2) ratio,
d.value physical_writes
from sys.v_$sysstat a,
sys.v_$sysstat b,
sys.v_$sysstat c,
sys.v_$sysstat d
where a.statistic# = 37 -- db block gets
and b.statistic# = 38 -- consistent gets
and c.statistic# = 39 -- physical reads
and d.statistic# = 40 -- physical writes
(2) 적다고 생각될 때 initSID.ora 화일에서 다음을 고려한다.
DB_BLOCK_LRU_EXTENDED_STATISTICS = 1000
- 이 파라미터를 설정하고 다음의 SQL을 수행시킨다.
단, 값을 너무 크게 설정하면 심각한 퍼포먼스의 영향을 가져온다.
- 위의 1000 값의 의미는 현재보다 1000 까지 DB BLOCK을 더 늘렸을 때
cache hit가 증가하는 값을 알아보기 위함이다.
col Interval format a20
prompt Number of Additional Cache Hits (ACH)
select 200*trunc(indx/200)+1 || ' to ' ||
200*(trunc(indx/200)+1) "Interval",
sum(count) "Additional Buffer Cache Hits"
from sys.x$kcbrbh
group by trunc(indx/200)
Interval Additional Buffer Cache Hits
1 to 200 300
201 to 400 250
401 to 600 180
601 to 800 80
801 to 1000 50
(3) 많다고 생각될 때 init$ORACLE_SID.ora 화일에서 다음을 고려한다.
DB_BLOCK_LRU_STATISTICS=TRUE
- 이 파라미터를 설정하로 아래의 SQL을 실행하여 전체 버퍼에 대해 공헌하는
정도를 알아본다.
- 아래의 경우는 1 부터 600 까지의 버퍼만 사용되고 있음을 알 수 있다.
col Interval format a20
prompt Number of Losing Cache Hits (LCH)
select 200*trunc(indx/200)+1 || ' to ' ||
200*(trunc(indx/200)+1) "Interval",
sum(count) "Losing Buffer Cache Hits"
from sys.x$kcbcbh
group by trunc(indx/200)
Interval Losing Buffer Cache Hits
1 to 200 3915
201 to 400 434
401 to 600 199
601 to 800 0
9801 to 10000 0

To MMM, the hit ratio is currently 100%. We want to lower that to about 95% and save some RAM at the expense of some slower queries.
To KM, no we are not using any stats_pack utilities.
Can anyone tell me the init.ora parameter to set in Oracle 8.1.7.4 to gets measures into the above table?

Kernel parameter tuning in Solaris 10

Hi Guru's
Can you any one help me to find the some good docs for Solaris kernel tuning. How to change the kernel parameter online?
How to do kernel tuning in online and what is the purposre of /etc/system and sysdef command.
How I can search for exisiting kernel value.
Thanks in advance.
Jimbe

There is interesting info at [Solaris Internals|http://www.solarisinternals.com/wiki/index.php/Solaris_Internals] .
have a good day,
Glen

SAP Netweaver parameter tuning for retail systems.

Hi Gurus
I am working in retail. I want to know if there are specific parameters that you must tune for retail systems, that you not usually tune for other businesses?
Info:
OS = AIX 5
Database = Oracle 10.2.0.2.0
System = SAP ECC 6.0
Patch level = 700, 17
ABAP and Java
Any help will be appreciate
Regards,
S.W.

Not that I know.... if there was they'll be stated on the Manual or Best practice guide
Regards
Juan

Inputs to setup an Oracle performance tuning Lab.

Hi All,We are planning to setup a Performance tuning lab at our unit.The key areas which needs to be addresses for this lab is 1)Architecture of the Database 2)Having Large volume of data 3)Producing high volume transactions.
Request you to provide your valuable inputs on how to setup the lab.

user11266214 wrote:
Hi All
Thanks for your responses.We are not doing the load testing.We have a linux server on which Oracle 11g running.We would like to simulate the real time work environment on which we train people to perform the performance tuning tasks.Performance tuning tasks comprise of Server tuning,Oracle parameter tuning and SQL tuning.
Request you to provide inputs on the approach we need to take up for setting up such kind of lab.
Thanks in anticipation.Swingbench as said before

Maximum File size in XI

I have 100 MB file to be transferred through XI.
How to check maximum file size limit in XI server.
Is thier any tcode for the same?

Hi ViJaYaNt JhA ,
File size depends on your Java Heap (Java heap depends on your Hardware Config).Basically SAP recommends a size of 5 Mb.
you can try the quicksizer tool on http://service.sap.com/quicksizer.
Also update the HTTPProvider service on the Java server dispatcher to have the parameter MaxRequestContentLength = 800M
The ABAP parameters icm/HTTP/max_request_size_km set to 2097152, icm/server_port_0 TIMEOUT set to 600. rdisp/max_wprun_time = 3600, ztta/max_memreq_MB =2048.
In SXMB_ADM add the parameter TUNING EO_MSG_SIZE_LIMIT = 40M
Best way would be splitting technique.
Splitting the file before it enters XI would considerably reduce the load on XI.
please refer the following links
The specified item was not found.
Refer this blog
Night Mare-Processing huge files in SAP XI
one more suggestion is:
Increase Current Value of the Parameter Nmame : rdisp/max_wprun_time
using Tcode RZ11 and try to process.
I think it is possible to process files Sizes up to 50 Mb.
Refer Note 807000 ,File Adapter: SAP Note 821267.
Regards,
Vinod.

XI freezes

Dear experts,
we have a customer where our 'dress rehearshal' for go-live failed 3 times.
Scenario
1. IDocs are sent (for outbound deliveries) from backend to a BPM.
2. The BPM works as follows: synch call to an HTTP receiver. Depending on the reply:
 a. If OK, process is completed
 b. In case of application error an alert is thrown and a wait step starts. The BPM allows for a max 3 such 'retries', if 3 is reached then the process is terminated with error.
 c. In case of unknown return code a termination occurs (no retries).
Symptom
No problems occured during our tests. However during the dress rehearshal (about 2000 Idocs fired within 30 minutes from the backend) after some minutes of normal operation the following happened:
1. Messages from SAP backend get stuck in status 'to be delivered' and remain there for days
2. The business process (SAP workflow) timeouts last hours rather than the prescribed 1 minute (we had this for testing, normally should be half a day)
3. It was impossible to launch the integration builder html pages. Java seemed totally 'down'.
4. Occasionally, we could not even log on to the ABAP stack.
5. The logs show an unreasobaly high number of 'rollbacks' being executed.
5. Despite all this:
 that the CPU works at very small percentage !!!
 No storage problem is detected...
Actions taken
WE could not remedy the situationm even after several restarts of XI. We managed to get it again running properly after restarting the server.
We then tried some parameter tuning (including dialog processes and queues) but again after some hours of being happy the same happened.
Our machine is a 4 CPU with 16 GB, should be OK for this.
IDEAS ARE WELCOME...

Hi,
I am sharing my thoughts.
1 ) Might be due to couple of interfaces using BPM in Synchronous, More the BPM the system performance will be slow and more over you are using the calls in Synchronous, Hence it will occupy more memory and wait for the response. assume at particular time couple of interface are waiting for response from the other side... Obviously it will make the system Freeze.
2) Status: TO_BE_DELIVERED
Which means that the message was successfully delivered from Integration Server point of view and it states that the messages is initially handed over to the Messaging System.
TO_BE_DELIVERED occurs while the message is put into the Messaging System receive queue.
Solution:
This is done via the Messaging System receive servlet:
http://<Host>:<PORT>/MessagingSystem/receive/<CONNECTION>
/<PROTOCOL>
Only if this was executed successfully the Messaging System returns HTTP 200 to the Integration Server and the Status TO_BE_DELIVERED moves to DELIVERING
1. Try logging into Sap GUI with two users: XIAPPLUSER & XIAFUSER
to see if they are blocked
2. We can check the messages:
AdapterFramework
com.sap.aii.adapterframework.serviceuser.language
com.sap.aii.adapterframework.serviceuser.name = XIAFUSER
com.sap.aii.adapterframework.serviceuser.pwd
ApplicationSystem
com.sap.aii.applicationsystem.serviceuser.language
com.sap.aii.applicationsystem.serviceuser.name = XIAPPLUSER
com.sap.aii.applicationsystem.serviceuser.pwd
in the exchange profile to make sure the right passwords
Regards
Agasthuri Doss

How to set oracle parameters

Hi all,
how to set oracle parameters in my sap 4.7 server. I need to know the procedure of parameter tune.
Regards,.
satish.
Edited by: satish k on Jun 17, 2008 5:07 AM

Hi
Please try this link.
http://oracle.basisconsultant.com/oracle_tuning_parameters.htm
http://www.orafaq.com/wiki/Oracle_database_Performance_Tuning_FAQ
But before doing this, check for all the probabilities as it requires lots of data and traces to do the parameter tuning.

Slow performance after implementing TREX in CRM

Hi All,
We have recently implemented TREX in our CRM 7.0 system and from that time we are getting performance issue in two things:
u2022Saving a New Contact. > Previously it use to take 15 seconds to 1 minute, but now itu2019s taking minimum of 2minutes to 5min maximum.
u2022Creating Marketing Attributes in a New Contact > Itu2019s taking lot of time. As previously we use to get the option in seconds after selecting the category under > Attribute Set or Attribute Field to get the >u201CValueu201D.
As we are facing this issue after TREX implementation so we expect that because of TREX we are facing the issue.
Please suggest root cause of this error and how can we resolve it , Is there any paramter we need to tune after TREX to make the system working fine or any OSS note which contains information for parameter tuning after TREX implementation.
Please suggest.
Shivam

Hi Shivam,
This is an old post, just wondering how you solve this issue? Do you have any documentation?
Thank you.
Regards,
Edison Wang.

WLS -JDBC sql server 2005, if sql server down bringing down entire cluster

Hi ,
From 4 WLS we connect to 4 indivudual SQL Servers 2005 (non clustered) , if one sql server goes down it is bringing down the 4 WLS servers. Tried all the possible parameter tuning in WLS nothing helped.
Is there any solution, if there is one sql server down can we mark the bad sql server down and don't create STUCK threads to all 4 WLS.
Thanks
Manu

Hi Weinstein,
when one sql server went down we saw the SQL server SHUTDOWN in progress. We use the DRIVER weblogic.jdbc.sqlserver.SQLServerDriver. When one server is going down connection pool is keep going to the same server and creating stuck threads.
<Info> <JDBC> <[ACTIVE] ExecuteThread: '150' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1327597605889> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLException: [OWLS][SQLServer JDBC Driver][SQLServer]SHUTDOWN is in progress.
 at weblogic.jdbc.sqlserverbase.BaseExceptions40.createAppropriateSQLExceptionInstance(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseExceptions40.createSQLException(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseExceptions.createException(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseExceptions.getException(Unknown Source)
 at weblogic.jdbc.sqlserver.tds.TDSRequest.processErrorToken(Unknown Source)
 at weblogic.jdbc.sqlserver.tds.TDSRequest.processReplyToken(Unknown Source)
 at weblogic.jdbc.sqlserver.tds.TDSLoginRequest.processReplyToken(Unknown Source)
 at weblogic.jdbc.sqlserver.tds.TDSRequest.processReply(Unknown Source)
 at weblogic.jdbc.sqlserver.tds.TDSLoginRequest.submitRequest(Unknown Source)
 at weblogic.jdbc.sqlserver.SQLServerImplConnection.open(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseConnection.doConnect(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseConnection.connect(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseConnection.setupImplConnection(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseConnection.open(Unknown Source)
 at weblogic.jdbc.sqlserverbase.BaseDriver.connect(Unknown Source)
 at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:320)
 at weblogic.jdbc.common.internal.ConnectionEnvFactory.refreshResource(ConnectionEnvFactory.java:412)
 at weblogic.common.resourcepool.ResourcePoolImpl.refreshResource(ResourcePoolImpl.java:1717)
 at weblogic.common.resourcepool.ResourcePoolImpl.checkResource(ResourcePoolImpl.java:1606)
 at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1507)
 at weblogic.common.resourcepool.ResourcePoolImpl.checkAndReturnResource(ResourcePoolImpl.java:1496)
 at weblogic.common.resourcepool.ResourcePoolImpl.testUnusedResources(ResourcePoolImpl.java:1942)
 at weblogic.common.resourcepool.ResourcePoolImpl.access$800(ResourcePoolImpl.java:40)
 at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2368)
 at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
 at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
 at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
 at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
>
In .net they have Retry Wait and connection will not go to the failed server until certain time, do we have any parameters like this in weblogic connection pool.
http://support.microsoft.com/kb/169470
1. Q. With ODBC 3.0 Service Pack 1, will the ODBC driver manager try to connect to the database server repeatedly when the server is not available?
A. ODBC 3.0 Service Pack 1 introduced a new API, ODBCSetTryWaitValue, to prevent the ODBC driver manager from connecting to an unavailable server repeatedly. ODBCSetTryWaitValue takes a DWORD parameter and saves the information in the registry at the following location:
HKEY_LOCAL_MACHINE\Software\Odbc\Odbcinst.ini \ODBC Connection Pooling\Retry Wait
Once the diver manager detects a bad database server, it returns an error message and marks the connection with the time. From that point until the RetryWait value expires, the driver manager returns a failure without trying to reconnect to the database server
Thanks for your help.
Thanks
Manu

9I의 SPFILE사용에 대해서

제품 : ORACLE SERVER
작성날짜 : 2004-10-12
9I의 SPFILE 사용에 대해서
========================
PURPOSE
Oracle9i부터는 database의 initial parameter를 지정하는 initSID.ora file외에
server parameter file이라고 불리는 spfileSID.ora가 새로 소개되었다.
이 spfile을 사용하게 되면 alter system을 통해 database가 운영 중에
parameter를 수정할 수 있게 되면서 parameter 수정때마다 database를 restart
시켜야 하는 필요을 줄여주고, 앞으로 소개될 dynamic한 server tuning에
중요한 역할을 할 수 있다.
Explanation
이 문서에서는 이러한 spfile에 대해서 실제 사용하면서 알아두어야 할 다음과
같은 내용에 대해서 정리하였다.
1. spfile을 vi로 직접 변경한 경우의 영향
2. db open시 spfile을 읽었는지 확인하는 방법
3. initSID.ora를 spfileSID.ora로 migration하거나 그 반대의 방법
4. alter system으로 parameter변경시 scope에 대해서
5. v$parameter와 v$spparameter에 대해서 (static parameter 확인)
1. spfileSID.ora 화일을 vi로 직접 변경한 경우의 영향
spfile이 크기 않은 관계로 vi등으로 읽으면 마치 text 화일처럼 parameter가
보이는데 이 화일은 실제로는 binary file로 직접 변경하면 안된다.
특히 이 화일의 header에는 checksum과 기본적인 meta-data 정보등을
포함하여 manual하게 변경하게 되면 이 checksum의 값이 맞지 않게 되면서,
이후 startup시 이 화일을 읽지 않고 initSID.ora file을 읽게 된다.
db를 운영하면서 spfile에 계속 parameter가 변경된 경우라면 이러한 문제로
tuning등을 통해 변경된 parameter value를 모두 잃게될 수 있는것이다.
2. db open 시 spfile을 읽었는지 확인하는 방법
db가 open 시에 참조한 initial parameter file이 무엇인지를 확인하기
위해서는 다음과 같이 조회하면 된다.
SQL> show parameter pfile
NAME TYPE VALUE
spfile string ?/dbs/[email protected]
여기에서 ?는 ORACLE_HOME을 나타내고 @는 SID를 나타낸다.
3. initSID.ora를 spfileSID.ora로 migration하거나 그 반대의 방법
spfile을 사용하다가 그 화일의 내용을 initSID.ora에 backup 차원에서
반영시켜 두거나, 혹은 spfile대신 initSID.ora를 사용하고자 하는 경우,
또는 반대로 initSID.ora를 참조하여 spfileSID.ora를 생성하고 하는
경우 다음과 같이 간단히 작업하면 된다.
SQL>connect / as sysdba
SQL>create pfile='initORA9i.ora' from spfile='spfileORA9i.ora';
SQL>create spfile='spfileORA9i.ora' from pfile='initORA9i.ora';
위 문장에서 화일명 대신 직접 directory까지 절대 path로 지정할 수 있고,
화일명은 임의로 지정 후 나중에 사용시 initSID.ora나 spfileSID.ora 형태로
만들어줄 수 있다.
default인 $ORACLE_HOME/dbs directory이고 SID가 붙는 이름 형태이면 간단히,
다음과 같이 지정하여도 된다.
SQL>create pfile from spfile;
SQL>create spfile from pfile;
sysdba 권한이 없으면 권한 부족 오류가 발생한다.
4. alter system으로 parameter 변경 시 scope에 대해서
spfile을 사용하게 되면 앞에서도 언급한 것과 같이 spfile을 직접 변경하는
대신 alter system command를 통해 initial parameter를 수정할 수 있다.
단 이때 alter system command 뒤에 scope를 지정할 수 있는 데 scope로
지정가능한 값은 memory/spfile/both 세가지가 된다.
memory가 이중 default여서 scope를 지정하지 않으면 memory가 된다.
memory: 변경이 현재 상태에만 영향을 미치며 db가 restartup되면,
변경 이전값으로 돌아간다.
spfile: 변경 내용을 spfile에만 저장하고 현재 상태에는 영향을 미치지
않게 한다.
static parameter의 경우는 이 scope만이 지정가능하다.
즉, spfile을 사용하더라도 static parameter에 대해서는 db
운영중에 바로 값을 변경하여 restartup없이 반영하는 것은 불가능
한 것이다.
both: 변경 내용을 현재상태에도 바로 반영하고, spfile에도 반영시켜,
이후 rebooting시에도 영향을 미치도록 한다.
지정하는 방법은 다음과 같다.
SQL>alter system set open_cursors=300;
SQL>alter system set open_cursors=300 scope=spfile;
SQL>alter system set open_cursors=300 scope=both;
단, spfile을 참조하지 않고 init.ora를 참조하여 db가 open한 경우 이러한
alter system 명령을 통해 initial parameter를 변경하려고 하면
다음과 같은 오류가 발생한다.
특히 spfile에 외부의 변경이 가해져 spfile이 참조되지 않은 경우에 주로
다음 오류를 만날 수 있다.
ORA-02095: specified initialization parameter cannot be modified
5. v$parameter와 v$spparameter에 대해서 (static parameter 확인)
initial parameter의 종류에는 db가 운영 중에는 바로 그 값을 변경하여
반영시킬 수 없고, 다음 startup 후에만 변경된 값이 영향을 주게되는
parameter가 있다.
이러한 parameter를 static parameter라고 부른다.
이 static parameter의 경우는 그래서 alter system으로 변경하더라도,
scope=spfile 로만 지정 가능한 것이다.
이러한 static parameter를 scope를 지정 안 해서 memory로 하거나 both로
하게 되면 4번에서 설명한 ORA-2095 오류가 발생하게 된다.
그럼 static parameter는 어떻게 확인할 수 있는가?
SQL>select name, issys_modifiable from v$parameter;
여기에서 보면, issys_modifiable의 값으로 다음 세 가지가 나타난다.
FLASE: static parameter로 scope=spfile로만 값을 변경 가능하다.
즉 값을 변경해도 이후 startup 시부터 영향을 미치게 된다.
IMMEDIATE: 값을 변경하면 현재 session부터 바로 영향을 받게된다.
DEFERRED: 변경된 값이 이후 접속되는 session부터 영향을 준다.
alter system을 통해 parameter를 변경하는 경우 변경된 값이 반영이 잘
되었는가를 확인하려면 다음과 같이 show parameter나 v$parameter를
조회하고, 현재 반영은 안 되었더라도 spfile에 저장은 되었는지를 확인하
려면 v$spparameter를 조회하면 된다.
SQL>show parameter open_cursors
SQL>select value from v$prameter where name = 'open_cursors';
SQL>select value from v$spparameter where name = 'open_cursors';
즉, scope=spfile로 parameter를 변경한 경우는 v$spparameter에만 변경
된 값이 나타나고, show parameter나 v$parameter에서는 변경 전 값이
나타나게 된다.

Cisco Catalyst 2950/2960/3750 Multicast Traffic Preference

Hello all,
we, as a student company act as an ISP for university dormitories. We would like to (if it's possible) deploy QoS to prefer multicast traffic over all other types of traffic.
Devices used in network:
Acces layer: Cisco Catalyst 2950, 12.1(22)EA14
Dristribution layer: Cisco Catalyst 2960G, 12.2(58)SE1
Core layer: Cisco Catalyst 3750G, 12.2(52)SE
Do you see any possibility to solve this with these devices? We have almost no experience with QoS, therefore any help would be greatly appreciated.
Thanks in advance.

Disclaimer
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
Liability Disclaimer
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
Posting
Hmm, I think it should be doable although the 2950s, if non-E variants, are especially weak in QoS features. I.e. those might create some issues.
With the 2960G and 3750G, you often will create problems when you enable QoS because QoS, by default, allocates its buffers resources for 4 egress queues per port rather than using all for 1 egress queue per port. However, this can be countered by QoS parameter tuning, but that takes some QoS expertize to match to your traffic and your overall QoS policy.

Automatic restart at SXMB_MONI

Hello gurus,
What exactly happens when any of my messages get to the state "Automatic restart" because of any temporary errors like communication failure? How is the system configured to restart these messages; parameters, background jobs? Is there a default mechanism PI uses without any configuration or do I set up anything for these messages to actually be restarted automatically?
All input&links will be very much appreciated and rewarded as well. Thank you.
Regards,
Gökhan

Thank you for all your inputs. Actually I had read the blog here:
/people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
and I got confused. It says:
Option 1
IS_Retry A batch job( internal in XI) is automatically scheduled to reprocess the entry after 2 minutes.
If the maximum number of retries was reached (10 by default; IS configuration parameter
TUNING IS_RETRY_LIMIT), a communication error then causes a SYSFAIL status for a queue.
Option 2 The problem with setting IS_RETRY is that every message with a failure status will be retried every 2minitues till the maximum number of retries is reached. Since there is no control on the retry period , a high retry count could cause excessive load on XI. The other option is to do Mass Restart by scheduling the report RSXMB_RESTART_MESSAGES at a predetermined retry period like 1hr. There is a catch here, RSXMB_RESTART_MESSAGES tries to restart a failed message 800 times by default. So if there is a message that failed due to genuine reasons, we may want to limit the number of retries. It is recommend by SAP to reduce the retry count to 20 restarts. (You can always manually restart a message, from the monitor, up to 990 times).
What I understand from option 2 is that, RSXMB_RESTART_MESSAGES can be scheduled to mass restart all messages with temporary errors, and although Naveen wrote it also in option 1, IS_RETRY_LIMIT parameter is valid for this program.
What I don't understand is Option 1. What is IS_Retry he is talking about? Is there any other mechanisms to restart messages other than reports RSXMB_RESTART_MESSAGES, RSQIWKEX and RSARFCEX? "A batch job( internal in XI) is automatically scheduled to reprocess the entry after 2 minutes" - what job is this?
Thank you,
Gökhan
Edited by: S. Gökhan Topçu on Feb 18, 2009 10:12 AM

Forum for DB2 9?

Hi all,
is this the right forum for DB2 9?
we are migrating from informix 9.4 to DB2 9, we are not spending any time on DB2 V8.
i know there are differences between V8 and V9, i don't want to get confused.....
what is the best source of info for administering DB2 9 under SAP?
I found : Database Administration for DB2 UDB for UNIX and Windows
but this is moreso for V8.
thanks for your thoughts.
NormaJean Sebastian

Hi,
there is no much difference in adminstration between DB2 V8.2.2 and DB2 9.
The OSS note 930487 describes the use of DB2 9 in SAP environments. The note references other OSS notes like
913481 DB6: Archiving log files with DB2 log file management
which is important for decision for log file management and
899322 DB6: DB2 9 Standard Parameter Settings
which is important for correct db and dbm parameter tuning. The new features in DB2 9 and how they can be used in an SAP environment are described in several SDN articles and OSS notes.
Best regards, Jens

Memory warnings in alert log

Hi,
We are using Oracle Enterprise 11.2.0.3 and the dba is reporting memory warnings in the alert log on continual nightly basis over last week.
No difference in volume of data being processed or programs so not sure why this is the case - aplogioes don't have details of error to hand.
We run many processees in parallel - database set for auto-parallelism (PARALLEL_DEGREE_POLICY=AUTO) and 3rd party reporting tool relies on this for spped of reports aganist partitoned tables.
Our data loads complete fine despite these messages.
Dba has asked if we can reduce what being done during these times or reduce the number of proceses
Are there any database parameters which can be set to manage memory such that database doesn't exhaust available memory in this way.
We want the database to manage the workload automatically ( would hope via parameter tuning in partciluar of the parameters related to parallel query this would be possible).
Thanks

user5716448 wrote:
Hi,
Aplogies for delya.
Here is the message from alert log
ORA-04031: unable to allocate 512024 bytes of shared memory ("large pool","unknown object","large pool","PX msg pool")
And this is repeated many times in the log.
On IBM Power Series 7 hardware AIX operating system.
Oracle version 11.2.0.3
Any ideas to allow database to manage memory more effectively when many paralllel queries runing - tuning of parallel-related parameters - which ones?
Thanksresults when reasoning is as follows
Parallel must be faster than no parallel
higher degree of parallel must be faster than lower value.
if/when you reduce parallel activities, then this error no longer occurs.

Parameter tuning - DLThreadswrite DLThreadprepare

Similar Messages

Maybe you are looking for