Have you enabled Network Services on your schema? (Not sure if the APEX upgrade changes previously enabled ACL)
This may prevent communication with your BI Publisher server?
yes they are enabled this again after I viewed this article through other threads...below is the script DBA sent they have used for ACL.
DBMS_NETWORK_ACL_ADMIN.CREATE_ACL(acl => 'www.xml',
description => 'ACL for ApEx Printing',
principal => 'APEX_040200'
is_grant => true,
privilege => 'connect');
DBMS_NETWORK_ACL_ADMIN.ADD_PRIVILEGE(acl => 'www.xml',
principal => 'APEX_040200',
is_grant => true,
privilege => 'resolve');
DBMS_NETWORK_ACL_ADMIN.ASSIGN_ACL(acl => 'www.xml',
host => ‘w216706ldbs2017');
I'm no DBA, but I usually have to do it each time I create a new APEX workspace with it's own schema - I have to add the privilege for the specific schema name.
(I am working with Version 4.2.0.00.27)
-- Look for the ACL currently assigned to '*' and give SCHEMA_NAME
-- the "connect" privilege if SCHEMA_NAME does not have the privilege yet.
SELECT ACL INTO ACL_PATH FROM DBA_NETWORK_ACLS
WHERE HOST = '*' AND LOWER_PORT IS NULL AND UPPER_PORT IS NULL;
IF DBMS_NETWORK_ACL_ADMIN.CHECK_PRIVILEGE(ACL_PATH, 'SCHEMA_NAME','connect') IS NULL THEN
DBMS_NETWORK_ACL_ADMIN.ADD_PRIVILEGE(ACL_PATH,'SCHEMA_NAME', TRUE, 'connect');
-- When no ACL has been assigned to '*'.
WHEN NO_DATA_FOUND THEN
DBMS_NETWORK_ACL_ADMIN.CREATE_ACL('power_users.xml','ACL that lets power users to connect to everywhere','SCHEMA_NAME', TRUE, 'connect');
i think it is pretty much same script we ran. do we have to restart database? or reboot the physical servers?
Did you double check that your schema privilege is set to 1 (it should not be null)?
thanks it was resolved as per your previous suggestion to create acl