Hi Suresh,
Besides the interesting links provided, please take into account that there is a version restriction actually: there is yet no SRS support for SAP systems based on SAP ASE 16.0.
You may refer to SAP Note 1891560 - Disaster Recovery Setup with SAP Replication Server
Best regards,
Victoria.
Hello,
The above link doesn't apply in a Business Suite environment.
The information you are looking for is HADR with Replication Server in a Business Suite environment.
The main information about it is documented in SAP Note 1891560 - Disaster Recovery Setup with SAP Sybase Replication Server
To access the official documentation to install Replication Server for HADR in a Business Suite environment:
Also, in this SCN space we have also published the last HADR User's Guide (HADR Users Guide ) and an additional topology supported (HADR Installation in a Nutshell - Part II )
Additionnally, all documentation about HADR is documented in KBA 2175528 - FAQ HADR: Frequently Asked Questions for HADR with SAP Replication Server certified for Business Suite
However, regarding your specific environment, note that HADR is still not supported with ASE 16.
So you will have to check for alternatives, detailed in SAP Note 1650511 - SYB: High Availability Offerings with SAP Adaptive Server Enterprise
HTH
Regards,
Cris
Hi!
I have just installed ASE 16 on Oracle linux 6.7. I managed to change the password for the user "sa". Is there a GUI tool that can be used to start server? How do I stop/start the database? I know about the startserver -f $SYBASE/ASE-16_0/install/RUN_SYBASE and RUN_SYBASE_BS but I would like a GUI tool for a start. I am trying to configure Commvault Simpana to work with Sybase.
Regards
Hi Maria,
Thank you for detailed information.
Could you please provide the correct media for installing Replication Server on ECC6 EHP 7. (As per guides ASE replication server support till 15.7 patch136 only so I have downloaded 133 )
Thank you in advance.
Regards
Suresh
Dear colleagues,
The issue was solved by Service SAP Support. I did raise a support ticket and after many investigations they have recommended the procedure below to resolve the issue.
The solution for this message is the SAP note 2201556, but the manual procedure to apply it changes did not work and SAP intervene to cancel SPAM update queue and allow me to work with SNOTE before restart SPAM import queue.
Solution procedure:
Regards,
Herman Arancibia
Hello,
It looks like you have downloaded SAP ASE media, nor SAP Replication Server media.
They're not the same product
You have to search Replication Server product from Marketplace. Ensure you are downloading a version compatible with your ASE version (see compatibility matrix in SAP Note 1891560 - Disaster Recovery Setup with SAP Sybase Replication Server), and with the mention 'Certified for Bus.Suite'.
HTH
Regards,
Cris
Hello,
You can get the System Copy guide from SAP Marketplace:
http://service.sap.com/sltoolset -> Software Logistics Toolset 1.0-> Documentation -> got to Documentation/Guides section and you will find the documentation System Copy: Systems Based on SAP NetWeaver 7.1 and Higher.
The two options above in your screenshot are optional, you can find details in the doc, and regarding your second question, doc states:
=====================
Caution: Make sure that you shut down all SAP application servers before the export. The database must still be running. Otherwise, the target system might be inconsistent.
=====================
HTH
Regards,
Cris
Thanks, I had the same issue, and solved it by the same method you have mentioned.
Definitely saved my time. Iam pretty sure the support could have taken two more days to come up with an answer on this.
Dear Colleagues,
One of the scheduled UPDATE STATISTICS job, failed to run.
Hence I was trying to execute it manually.
1> update index statistics 'S30.SAPSR3./BI0/F0SMD_PE2H'
2> go
Msg 102, Level 15, State 181:
Server 'S30', Line 1:
Incorrect syntax near 'statistics'.
My table name is S30.SAPSR3./BI0/F0SMD_PE2H. Though it looked very simple, but i spend a day, with all possible ways to get rid of the syntax error, but all in vain. I wanted to run with sampling option so as to improve the time consumption.
Please give me some helping hand on this. I am running on ASE 15.7 , SP134.
Thanks Bret !!!! That was very explanatory answer....
So ideally there should be NO HARM, to kill the spid associated with this? It is running with 'recv sleep' status. for couple of days.
fid spid status loginame origname hostname blk_spid dbname tempdbname cmd block_xloid threadpool
------------ ---------------- ---------------------------------------- -------------------------------- -------------------------------- -------------------------------- -------------------------------- ------------------------ ---------------------------------------- ---------------------------------------------------------------- -------------------------------------------- ----------------------------------------------------------------
0 217 recv sleep SAPSR3 SAPSR3 s30ci1 0 S30 saptempdb AWAITING COMMAND 0 syb_default_pool
(1 row affected)
Hello Ajith,
Please use following commands
1> set quoted_identifier on
2> go
1> update index statistics SAPSR3."/1CN/CPASAP00001"
2> go
1>
If you have any doubt refer following sap note:-
1757691 - SYB: How to manually update index statistics of a table using isql
Regards
Anand
Thanks a lot Anand. That worked !!!
I was wondering, why it did not improve the value of datachange() function even after running update stats successfully. The value still looks very unhealthy.
1> set quoted_identifier on
2> go
1> update index statistics SAPSR3."/BI0/F0SMD_PE2H" with sampling = 2 percent
2> go
1> select datachange ('S30.SAPSR3./BI0/F0SMD_PE2H',null,null)
2> go
---------------------------
48377.814731
(1 row affected)
1> update all statistics SAPSR3."/BI0/F0SMD_PE2H" with sampling = 2 percent
2> go
1> select datachange ('S30.SAPSR3./BI0/F0SMD_PE2H',null,null)
2> go
---------------------------
50181.052529
1> sp_recompile 'S30.SAPSR3./BI0/F0SMD_PE2H'
2> go
Each stored procedure and trigger that uses table 'S30.SAPSR3./BI0/F0SMD_PE2H' will be recompiled the next time it is executed.
(return status = 0)
1> select datachange ('S30.SAPSR3./BI0/F0SMD_PE2H',null,null)
2> go
---------------------------
50181.052529
(1 row affected)
Any idea about this?
Ajith,
Good to know that you were able to address the issue.
Coming to your next question i believe...there is a difference between
Update index statistics and Update All statistics.Hence there is a difference in value.
Regards
Anand
True Anand, but the point where I am concerned is the datachange() value ( for the table) should have ideally come down ( after the update stats ran successfully) . Whereas it did not. Why didn't it....
I still get a feeling, It was unable to write statistics for that object. 
Ajith,
Usually The update stats is executed when the datachange value is greater than 5% in order for us to see the difference.
I believe if the values does not change the datachange value could be lesser than 5%.
Hence we dint not observe any difference.
Regards
Anand
Dear Anand and other dear colleagues
My datachange() shows 50181.052529% , after running Update stats without errors. What does it actually mean? Following are my concerns.
1.) Does Update Statistics reset the datachange() ?
2.) What else other than ( moddate, datachange() ) can confirm the necessity of Update Stats ?
Kind Regards,
Ajith Prabhakaran
Hi Guillaume,
I didn't saw this discussion when it was created. The problem has been reported by others customers around the same time actually and SAP Note 2242937 - SYB: Solution Manager upgrade with SUM fails in phase PARCONV_UPG_DS has been released last month to address this issue and how to solve it. The problem was the column name "TYPE" which should by on lower case 'type' in a specific form of SDB2FSYB program as you mentioned. In ASE the object names from system tables are all in lower case, case-sensitive, so that's why error 207 was returned here. This has been identified only when target is SAP_BASIS 7.02 SP17.
Best regards,
Victoria.
Hi All,
Greetings of the day..!!
Can anyone have idea, Why I am getting this error ??
I am getting this error while connecting SAS application using ODBC .
Am I using wrong file as driver ??
Thanks
pankaj
Hi Guillaume,
You are welcome
There were around 7 incidents opened between end of October and beginning of November for the same issue. And yes for some errors / specific situations, the Notes are released based on customer incident reporting the issue (just for reference https://support.sap.com/notes ). Hopefully after that, any other customer facing the same problem has the solution available. On others situations Notes are released without necessarily being linked to a specific incident, as corrections collections / preventive action for technical issues or some instructions for improvements.
Best regards,
Victoria.