Why is rdsadmin.rdsadmin_util.show_configuration being executed when it is not an Oracle RDS environment?
Hello,
Hi,
I am testing Qlik Replicate on Oracle (19.30) on-premise source and OCI ADW target environment.
However, in the task log 01766922: 2026-07-14T13:34:44 [TARGET_APPLY ]T: Going to prepare the statement 'BEGIN rdsadmin.rdsadmin_util.show_configuration;END;' Occurs periodically, and in the source Oracle alert log 2026-07-14T16:46:07.799507+09:00 WARNING: too many parse errors, count=1551 SQL hash=0x6e856dc9 PARSE ERROR: ospid=184696, error=6550: Additional information: hd=0x31713a070 phd=0x31e3fd178 flg=0x20 cisid=114 sid=114 ciuid=114 uid=114 sqlid=9zjxcqxr8avf9 ...Current username=ARUSER ...Application: repctl@dpts-cdc-qa-ar01 (TNS V1-V3) Action: Occurs randomly
I am curious why the `rdsadmin.rdsadmin_util.show_configuration` statement is executed even though it is not an RDS environment, and why it is executed on Oracle source code in an on-premise environment. This phenomenon did not occur when using `qlik replicate 2023 Nov 468` in the same source target environment.
I checked task json file and endpoint but I couldn't find anything strange.
In newer versions of Qlik Replicate (after the Nov‑2023 release, build 468), the product introduced an automatic check to determine whether the connected Oracle database is running in Amazon RDS or Oracle Cloud (OCI).
On RDS/OCI systems, the special Oracle package rdsadmin.rdsadmin_util exists and returns configuration details, but on on‑premise Oracle this package does not exist. Replicate still runs the check, which causes Oracle to log harmless ORA‑6550 “parse error” warnings. This explains why you see the statement BEGIN rdsadmin.rdsadmin_util.show_configuration; END; even in your on‑premise environment, and why it did not appear in build 468 — the probe was added later for cloud compatibility.
These warnings have no impact on replication or database performance and can be safely ignored.
In newer versions of Qlik Replicate (after the Nov‑2023 release, build 468), the product introduced an automatic check to determine whether the connected Oracle database is running in Amazon RDS or Oracle Cloud (OCI).
On RDS/OCI systems, the special Oracle package rdsadmin.rdsadmin_util exists and returns configuration details, but on on‑premise Oracle this package does not exist. Replicate still runs the check, which causes Oracle to log harmless ORA‑6550 “parse error” warnings. This explains why you see the statement BEGIN rdsadmin.rdsadmin_util.show_configuration; END; even in your on‑premise environment, and why it did not appear in build 468 — the probe was added later for cloud compatibility.
These warnings have no impact on replication or database performance and can be safely ignored.
Your response has resolved my curiosity. However, due to the Oracle wave error, there has been an unnecessary increase in oracle alert logs, which seems to lead to many inquiries from customers about the Oracle impact.
