Hello,
this is only changed syntax, the behaviour is exactly the same as it
used to be. I think the names for requested function have to differ due
to round trips. I do not think you have to use requested function as
long as you catch login/user name and provide it as procedure parameter.
Function string would solve the issue too, since rep server stores
primary login in its variables, but I am not sure you can use it in MSA
environment.
HTH,
Peter
On 12/15/2011 7:43 AM, Eisen wrote:
> Dear all
> I've built a MSA environment to replicate database
> ase1.db1=>ase2.db2. Since some procedures has DDL inside
> like 'create procedure ... drop table ... create table...'
> and these DDL can't be replicated to the replicate site. I
> have to use the function replication. Now I found in RS15.6
> the old "create function replication definition" is declared
> to be deprecated, now they are "applied function" and
> "request function", one is executing the procedure with
> maint user, the other is with the same user. Since this
> procedure will record the invoker's dbuser name, like
> "insert tb select suser_name()...". I'd have to use the
> "request function" one. But soon I found when I create
> request function replication definition, the primary
> procedure name must be different to the replicate procedure
> name...
> Of course, I can create another procedure with only one
> "exec proc_name" to solve this problem, anyway, it's not so
> convenient to use. Does anyone know any solution to this?
> Thanks.
>
> Best Regards
> Eisen
|