Symptom
- Change the dsi_isolation_level to different value
- Now set back the value to the default value
- Post that when you try to suspend and resume the connection you get the below error:
I. 2018/02/24 15:25:38. The DSI thread for database 'dsname.dbnameP' is shutdown.
I. 2018/02/24 15:25:48. The DSI thread for database 'dsname.dbname' is started.
E. 2018/02/24 15:25:48. ERROR #1028 DSI(228 dsname.dbname) - /generic/useful/cm.c(5209)
Message from server: Message: 2179, State 0, Severity 16 -- 'ORA-02179: valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
'.
E. 2018/02/24 15:25:48. ERROR #13045 DSI(228 dsname.dbname) - /generic/useful/cm.c(5213) - in the screen window you can see the messages as below:
State 0, Severity 16 -- 'ORA-02179: valid options: ISOLATION LEVEL { SERIALIZABLE | READ COMMITTED }
attempt to rollback configuration dsi_isolation_level set '0' or dsi_isolation_level set 'default' couldn't help to avoid the same error after resume connection
Read more...
Environment
-
SAP Adaptive Server Enterprise (ASE) 16.0
-
SAP Replication Server (SRS) 15.7.1
Product
SAP Replication Server 15.7 ; SAP Replication Server 16.0 ; SAP Sybase Replication Server 15.7, option for Oracle ; SY REP SERVER MESSAGING 15.7
Keywords
CR783519, CR#783519, 783519, rs_configure, DCO, DSI , KBA , BC-SYB-REP , Sybase Replication Server (standalone) , Bug Filed
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.