What could be the reason that while calling sr_add_message_server('Cons'), I get the following error:
the user Cons is existing and the publish role is granted to him, and a role is created for him! |
I have two databases:
Changing the sql security to invoker has solved the problem in the first database. Wow, a subtle difference with a drastic effect :)
(06 Jul '22, 11:55)
Volker Barth
|
Is there an EXTERNLOGIN entry for the according remote server "dbremote_msgs_server"? AFAIK, this is required unless the directory access server was created with option ALLOW 'ALL' USERS.
As this error appears during the "sr_add_message_server" call, what have you specified as @owner parameter? Because the procedure will do a CREATE EXTERNLOGIN for that username (among others) to "dbremote_msgs_server...
How can I check whether there is EXTERNLOGIN or not?
I call the procedure exactly like in the documentation:
CALL sr_add_message_server( 'cons' );
FWIW, the contents of the SQL Remote management procedures like sr_add_message_server() is available in the SYSPROCEDURE system table, so that may provide further hints.
Was this missed?
See the following: Tutorial: Setting up a Replication System Using the HTTP Message System with the Consolidated Database as the Message Server
No, this is done