Copy command fails and the copy status indicates that is is failed.
The sync_clt log indicates the following :
Wed May 14/16:37:03.627:: LogFile = /splex/vardir2200/log/sync_clt_209_zjcis_p595a_p10378.log
Wed May 14/16:37:03.627:: BufferSize = 1048576
Wed May 14/16:37:03.627:: DebugFlag = 0x20000
Wed May 14/16:37:03.627:: <===== END CLIENT_PARAMS =====>
Wed May 14/16:37:03.627:: Getting connections from Launcher
Wed May 14/16:37:03.627:: Sending SYNC version
Wed May 14/16:37:03.627:: Receiving Server configuration and tables
Wed May 14/16:37:03.696:: Using SID: "ORACLE_SID"!
Wed May 14/16:37:03.696:: ERROR: Cannot find oracle login for sid "ORACLE_SID"! at sync/clt/sync_clt_params.cpp:73 at sync/clt/sync_clt_params.cpp:58 at sync/clt/sync_clt_messager.cpp:495
Wed May 14/16:37:03.696:: ERROR: Couldn't handle server config message at sync/clt/sync_clt_messager.cpp:134 at sync/clt/sync_client.cpp:111 at sync/clt/sync_client.cpp:185
Wed May 14/16:37:03.696:: Process Exit
Wed May 14/16:37:03.697:: User Time : 0.16s
Wed May 14/16:37:03.697:: System Time : 0.02s
Wed May 14/16:37:03.697:: Child User Time : 0s
Wed May 14/16:37:03.697:: Child Sys Time : 0s
Paramdb in the SP_SYS_VARDIR/DATA directory has multiple logins .Shareplex copy command looks at the commented logins as well causing the wrong aliases to be used.
Please remove the commented entries from paramdb:
Example:
#SP_ORD_LOGIN_O.SID "579fd983ba1157bec85c062884d7129107f929"
#SP_ORD_OWNER_O.SID "USERNAME"
#SP_ORD_LOGIN_O.SID "579fd983ba1157bec85c062884d7129107f9294ac743216ff7"
#SP_ORD_OWNER_O.SID "USERNAME"
Ensure that only the correct Login is in the Paramdb
Example:
SP_ORD_LOGIN_O.SID "579fd983ba1157bec85c062884d7129107f929"
SP_ORD_OWNER_O.SID "USERNAME"
WORKAROUND STEPS:
1.Stop the launcher
2.Remove all the obsolete logins that are not used.
3.Restart the launcher.
4.Run the copy command.
STATUS
Will be addressed in Shareplex version 6.2 .
Note: The Launcher process has to be restared. When the paramdb file in Vardir/data directory has been modified then the launcher processes has to be restarted for the change to the paramdb to take effect.
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.
