-
Title
Whether changing the connection protocol from sql*net to Bequeath and vice versa on source will c -
Description
The connection protocols may sometimes be needed to be changed from sql*net to Bequeath and vice versa. Changing this requires re-running of ora_setup and the credentials of the Shareplex user in the database change as a consequence. Since changing the Shareplex user on source results in loss of current replication, the question arises as to whether changing the connection protocol on source would result in deactivation of the currently active config file.
-
Cause
General information.
-
Resolution
Changing the connection protocol from sql*net to Bequeath and vice versa on source does not result in loss of current activation. This is because such changes only result in the modification of the login entry for Shareplex user. This login entry is in the file named paramdb located in $SP_SYS_VARDIR/data directory. Even though there is a schema change (because of change in credentials of Shareplex user), this does not cause any change in Shareplex internal tables. So the current activation is not impacted.
-
Additional Information
Starting with SharePlex 8.6, the login credentials of SharePlex user are written to and stored in the file named connections.yaml located in /vardir/data subdirectory of SharePlex (where vardir refers to the Variable directory of SharePlex). Here is a sample entry: alvsupu07 # cat connections.yaml o.SYAM: password: 5787d4def4 user: SHA86 In the above, the first line has SID info. The second line has encrypted password and the third line has the name of the SharePlex user that makes connections to the database.