Showing results for 
Search instead for 
Did you mean: 

SDI Replication issue with Hana from Oracle DB

0 Kudos


We're doing replication of a table in Oracle to Hana Database using SDI and OracleLogReader adapter. We're able to create the replication task in editor and also generated the required procedure, but this procedure upon execution is giving the below error:

Error: (dberror) 256 - sql processing error: "CAPDEV"."sandbox::EMP_DET.START_REPLICATION": line 42 col 3 (at pos 1772): [256] (range 3) sql processing error exception: sql processing error: QUEUE: sandbox::EMP_DET.SUB_VDEV_EMP_DETAILS: Failed to add subscription for remote subscription sandbox::EMP_DET.SUB_VDEV_EMP_DETAILS[id = 175782] in remote source ETLAB_SDI[id = 174974]. Error: exception 151050: CDC add subscription failed: Failed to add the first subscription. Error: Failed to start Log Reader because of failure to initialize Replication Agent. Error:User <SYSTEM> is in the owner filter list and is also specified as the PDS user by the pds_username configuration parameter. Please either remove <SYSTEM> from the owner filter list or change the pds_username configuration parameter setting.

Please help.



Nitish Kumar

Accepted Solutions (0)

Answers (2)

Answers (2)

Active Contributor
0 Kudos

Hi Nitish,


2483495 - Error: Failed to start Log Reader because of failure to initialize Replication Agent. Error: The server is not initialized. Please run server_admin init first

Best Regards,


0 Kudos

I think this is happening because you are using the SYSTEM user, which is marked as the owner for some certain tables. My recommendation would be to create a new Oracle user and give it the needed permissions from oracle_init_example.sql, then update the credentials in the remote source.

As a second question, is the remote source set to table level or database level supplemental logging?

Best regards,
Jeff K

0 Kudos

Hello jeff,

Thanks for your response.

We changed the user in SDI (in place of SYSTEM) to connect to the database, but still getting the same error.

Also, remote source supplemental logging is set to table in the configuration.