Category: - clear 
Performance, Tuning 
4Votes
Promote Idea
Vote Up
Demote Idea
Vote Down
D38611   Category: Performance, Tu...     Status: Submitted
Tags:  

Hello,


In some cases we get performance issue due to logging table updates or reads,

These performance issue can be solved by some Oravle Parameter , however, this should be managed from SLT at the table creation.



The idea would be to have an option from SLT, to manage Oracle Parameter of Logging Table:
1. Manage Logging Table Partitioning
2. Manage INITRANS parameter
3. Manage Sequence Cache_Size
4. Create Additional Index


PLease, could you add this option from LTRS transaction in the next DMIS Package ?

More...

comment »  

 
2Votes
Promote Idea
Vote Up
Demote Idea
Vote Down
D36055   Category: Performance, Tu...     Status: Acknowledged
Tags:  

Currently Repserver does not support HVAR/RTL functionality with function string. Hence for large transaction function string operation is very slow.

 

If compilation can be on along with bulk load / update / delete .. performance will improve hence latency will reduce.

comment »  

 
14Votes
Promote Idea
Vote Up
Demote Idea
Vote Down
D35348   Category: Performance, Tu...     Status: Not Planned by SAP
Tags:  ase  kafka  repserver  

We would like to replicate realtime using SAP Replication Server from SAP ASE to Kafka and right now this is not supported by SAP.

 

Oracle GoldenGate supports this but we would like to use SAP Replication server - https://java.net/projects/oracledi/downloads/directory/GoldenGate/Oracle%20GoldenGate%20Adapter%20for%20Kafka%20Connect

 

Thanks

4 comment »  

 
3Votes
Promote Idea
Vote Up
Demote Idea
Vote Down
D35084   Category: Performance, Tu...     Status: Under Review
Tags:  rs_wheretext 
While the following datatypes are acceptable in table/function replication definitions, and can be searched on in subscription 'where' clauses, they currently cannot be reverse engineered by the rs_wheretext stored proc:

 

     numeric, decimal, real, float, date, bigdatetime, time, bigtime, bigint, unsigned smallint/int/bigint

 

Subscription search values for these datatypes are stored in rs_rules, and repserver obviously knows how to 'read' these search values from rs_rules, but for some reason rs_wheretext has not been kept up to date with logic on how to 'read' these same sarch values from rs_rules.

 

As of RS 15.7.1 SP303 the rs_wheretext proc, when reverse engineering these datatypes, responds in one of two manners:

 

1 - spits out a 'Can't convert --datatype--' message, eg, if 'h' is a bigdatetime:

 

original 'where' clause:      where h > '7/16/2016 15:16:17.123456'

rs_wheretext output:         where h > 'Can't convert bigdatetime'

 

or

 

2 - silently prints a 'where'

More...

comment »  

 
7Votes
Promote Idea
Vote Up
Demote Idea
Vote Down
D30176   Category: Performance, Tu...     Status: Not Planned by SAP
Tags:  

Hi,

 

I would love to see SAP release a Developer Edition of Replication Server on all platforms.  A 30-60 day evaluation license may be possible in some cases, but often it takes much longer for customers/prospects to develop and test solutions with SRS. Any comments or opinions would be most welcome.

 

Many thanks and regards,

Mark Bradley

SAP 

3 comment »  

 
5Votes
Promote Idea
Vote Up
Demote Idea
Vote Down
D29625   Category: Performance, Tu...     Status: Not Planned by SAP
Tags:  

Trace flag for DSI buffer are at server level.

While investigating a connection issue you need details about a connection rather than all buffer dumps for all DSIs to all connections on a replication server.

 

This could be a trace flag option or a connection level alter command to turn the trace on or off.

6 comment »  

 
11Votes
Promote Idea
Vote Up
Demote Idea
Vote Down
D29553   Category: Performance, Tu...     Status: Accepted

In a MSA configuration (imagine this is the same for a WarmStandby), if the replication fails to apply SQL on standby, the connection goes down then REP server starts accumulating segments/packets in the queues. This is the normal process.

Now after that we realize that we cannot fix the problem so we want to drop the subscription to stop accumulating packets in the queues. Well...you cannot delete the subscription in one-step process.

You have to:

1- stop the source REP agent (this is ok)

2- try resuming connection but it does not work because it is failing.

3- you should go to hibernate mode to clean the appropriate the queue

4- disable the hibernate mode

5- resuming connection (it no longer fails)

6- drop subscription

7- restart rep agent or disable it

 

When we asked SAP support, they advised to drop subscription by modifying the RSSD system tables...terrible solution that created more problem as the queues were not cleaned up.... 

Could we create a simple and clean way to remove a subscript

More...

8 comment »  

 
5Votes
Promote Idea
Vote Up
Demote Idea
Vote Down
D29496   Category: Performance, Tu...     Status: Not Planned by SAP
Tags:  

Hi,

We depend on the latency at replicate site kept to a minimim  for our replication DR straetegy to work out.

 

So in case there is a disconnect due to any factor  , be it network, replicate site down  or performance issues etc  we need to get DSI to stay down after 5 ( configurable )  retries.

 

This way DBA  can get alerted and intervene immediately.

 

I hope there is serious requirement of DR site latency SLA for customers who continue to deploy and use SAP ( Sybase)  replication server to its fullest feature set and not only basic warm standby or one way  MSA site replication.

 

This way we may prevent wasting costly  hardware infrastructure investment just  to maintain the DR site that is  not even "nearly" in sync  to production primary site.

 

Currently  the DSI will retry infinitely without any alerts.  This  is affecting our core DR site latency for databases.

 

I hope and believe there are some serious deployments of two way replication systems using classical  two

More...

2 comment »  

 
Displaying results 1 - 8 of 8