During the setup of a new replication you follow the Administrators Guide: "Synchronizing data using an Oracle hot backup on a quiet database".
In Step 10 you activate the config on the source and get this error message:
06/26/07 12:03 Logging user command: oracle activate config filename
06/26/07 12:03 Process launched: sp_tconf (for o.ORA10g) [pid = 24215]
06/26/07 12:03 Notice: Oracle env - ORA10g:/ora_home/app/oracle/product/10.2.0 [sp_tconf(pdb)/24215]
06/26/07 12:03 Error: 12032 - OCIServerAttach failed with ORA-12526. [sp_tconf(osp)/24215]
06/26/07 12:03 Bad config file: file - unknown; Oracle Error: connect failed for database o.ORA10g - ORA-12526: TNS:listener: all appropriate instances are in restricted.
06/26/07 12:03 Process exited sp_tconf (for o.ORA10g) [pid = 24215] - exit(1)
In previous releases such as Oracle 9iR2, an instance in restricted mode could be connected to via the listener with an account that had been granted the sys_priv "restricted session". In Oracle 10gR1 the behavior changed. If an instance is in restricted mode, then PMON instructs the listener to block ALL connections to the instance.
If you don't have tables with LOB data in your config file, you don't need to put the database in restricted mode.
Do not put the database restricted mode, restart db (to make sure nobody is on the database), stop listener, start extra listener (on a port unknown to users) for SharePlex, switch the redo logs, activate config then stop your extra listener again and start the normal listener.
Run ora_setup on the source without using the tns_alias, this way SharePlex uses the beq protocol and doesn't use sqlnet.