Re: replication errors

Look at the roles, system privileges and object privileges for the replication user. The replication user needs to have all of the appropriate permissions to add/update/delete data from another schemas table. The replication user needs select_catalog_role, around 40 system priveleges and around 15 object privleges (execute on sys objects). Please verify these roles and privileges with the documentation. Hopefully that's all it will take.

Later .......
Patrick

Ed_Stevens_at_nospam.noway.nohow (Ed Stevens) wrote in message news:<3b9903a0.85395051_at_ausnews.austin.ibm.com>...
> We are configuring our first replication environment. Worked through
> all replication wizards in DBA Studio to establish master site,
> snapshot site, snapshot group, etc. Don't *think* we missed
> anything. When we created the snapshot group on the snapshot server,
> we
> were plesantly surprised to see that it created and populated the
> tables from the master site. So far so good.
>
> Next, we modified a row in a user table on the master site, waited
> well past the refresh interval and the change never showed up in the
> snapshot database. Looking through the alert logs, we found the
> following in the snapshot side:
>
> Thu Sep 06 08:55:13 2001
> Errors in file e:\oradmin\smsz\bdump\smszSNP2.TRC:
> ORA-12012: error on auto execute of job 41
> ORA-01031: insufficient privileges
> ORA-06512: at "SYS.DBMS_SNAPSHOT", line 617
> ORA-06512: at "SYS.DBMS_SNAPSHOT", line 674
> ORA-06512: at "SYS.DBMS_IREFRESH", line 577
> ORA-06512: at "SYS.DBMS_REFRESH", line 211
> ORA-06512: at line 1
>
> I assume this job failure explains why the change didn't show up in
> the snapshot database. I looked at the referenced trace file, but
> didn't
> see anything any more informative.
Received on Mon Sep 10 2001 - 09:54:28 CDT