Sinds upgrade naar versie 20.2.125 krijgen we bij het repliceren van Loket de volgende foutmelding:
itgencun016: Fout -20163: Connected as user ACME\JOHN, but should have been connected as ACME
In de procedure staat:
--
-- Check whether the current connected user equal a specific
-- user and data container ID for a specific data container (when specified).
-- When not, raise an error.
--
create or replace procedure xxhosting_check_user
( p_data_container_id varchar2
, p_log_on_code varchar2
, p_alias varchar2 -- default null
)
is
begin
--
-- Check correct user.
--
if sys_context('USERENV', 'CURRENT_USER', p_alias) != p_log_on_code
then
raise_application_error
( -20163 /* xxive001 */
, 'Connected as user '
|| user
|| ', but should have been connected as '
|| p_log_on_code
|| '.'
);
end if;
--
-- Check correct data container ID.
--
if sys_context('USERENV', 'DATA_CONTAINER_ID', p_alias) != p_data_container_id
then
raise_application_error
( -20163 /* xxive002 */
, 'Connected on data container ID '
|| sys_context('USERENV', 'DATA_CONTAINER_ID')
|| ', but should have been connected to '
|| p_data_container_id
|| ' on alias '
|| p_alias
|| '.'
);
end if;
end;
En de aanroep vanuit SQL-script is:
local on error exit failure
local define AGREEMENT_CODE "L1234567"
local define REQUIRED_DATA_CONTAINER_ID "https://api.loket.nl/v2/developer.loket.nl/ACME/4"
local define REQUIRED_USER_ID "ACME"
local define CLOUD_WATCH_PREFIX "ACME"
local remark END OF CONFIGURATION SECTION
@@d:\jobs\hosting\sql\xxhosting.sql
@@d:\jobs\hosting\sql\xxdru.sql
begin
xxhosting_initialize;
xxhosting_check_user('${REQUIRED_DATA_CONTAINER_ID}', '${REQUIRED_USER_ID}', null);
xxhosting_check_agreement('${AGREEMENT_CODE}');
end;
Hoe kunnen we deze foutmelding oplossen?