2974185 - HANA error [258]: insufficient privilege: no whitelisted cross-database communication channels

• Cross database access has been setup and configured as per Enable and Configure Cross-Database Access

• A database user on a HANA database SAPSID makes a cross-database request to another target DB (SAPSID2) holding the requested database object, but fails due to the following error found in the indexserver trace of the source DB making the request  :

[94187]{357298}[67/723275327] 2022-11-17 21:08:46.225100 i TraceContext     TraceContext.cpp(01347) : UserName=SAPHANADB, ApplicationUserName=SAP_SYSTEM, ApplicationName=ABAP:SAPSID, ApplicationSource=CL_SQL_STATEMENT==============CP:703, Client=100, StatementHash=3ca51b80518a37b326c92c524bacb730, 
EppRootContextId=FA163E4728321EED98D4D20795DBA42E, EppTransactionId=4CCD71D71BC501E0E00636FC8BDA08C7, EppConnectionId=6376E202A27C0DEAE10000000AB422D7, EppConnectionCounter=1, EppComponentName=SAPSID/hostname_SAPSID_00, EppAction=RS_SSI_SERVER_STARTUP, StatementExecutionID=3096237693309090
[94187]{357298}[67/723275327] 2022-11-17 21:08:46.225100 e join_eval        JEPlanOperation.cpp(00347) : Caught exception in pop 129
[94187]{357298}[67/723275327] 2022-11-17 21:08:46.225136 e join_eval        JEPlanOperation.cpp(00348) : ERROR [CODE-258] insufficient privilege: no whitelisted cross-database communication channels
exception  1: no.71000258  (MultiDB/impl/RemoteTransactionManagerImpl.cpp:1719) TID: 58471
no whitelisted cross-database communication channels

• The target DB SID and remote local user are referenced here in the same trace file .... (SAPHANADB is the remote identity of USER2 on SAPSID)

[94187]{357298}[67/723275327] 2022-11-17 21:08:46.225197 e join_eval        JEPlanOperation.cpp(00222) : Inputs of failed pop:
[94187]{357298}[67/723275327] 2022-11-17 21:08:46.225209 e join_eval        JEPlanOperation.cpp(00223) : planData 0: JEPlanData; type: ISS: [0, 11139421]; numValidDocs: 0, maxUdiv:11330114, vis: 1; lazy:1; partId:0
, memsize: 16 B, numainfo: [N/A]
planData 1: JEPlanData; type: TupleList [SAPSID2::USER2:xxxx#0/ARBGB, SAPSID2::USER2:xxxx#0/int("MSGNR")]; size: 272864, memsize: 2.18379 MB, numainfo: [NTuple.col0(NumaNode: 0, ByteCount: 1091456), NTuple.col1(NumaNode: 0, ByteCount: 1091456)]
[94187]{357298}[67/723275327] 2022-11-17 21:08:46.225276 e join_eval        JEPlanOperation.cpp(00223) : content of planData 0:
ISS: [0, 11139421]; numValidDocs: 0, maxUdiv:11330114, vis: 1; lazy:1; partId:0
content of planData 1:
head: SAPSID2::USER2:xxxx#0/ARBGB, tail: SAPSID2::USER2:xxxx#0/int("MSGNR"), edgeId:0
    size: 272864; headListInfo: [min: ?, max: ?, sort: ?, unique:?]; tailListInfo: [min: ?, max: ?, sort: ?, unique:?];flags: 49216;maxUdivs: 0

SAP HANA, platform edition 2.0

SAP HANA, platform edition, sap_hana, database, db, saphana , KBA , whitelist , white list , whitelisted , HAN-DB-SEC , SAP HANA Security & User Management , Problem