Errors running dual instances of SAPR3

Question

Hello,
We've migrated our SAP environment to a new server in QA and are adapting Cronacle to run jobs in the two (old and new) envirnoments simultaneously for the next three weeks. That said, we have installed the new process server, and it's up and running. We have created a new instance and client. We have the RFC agent running for both. However, we are getting errors when trying to shut down the new RFC agent. Please see the error below. We had previously gotten this error when trying to start the old RFC agent, but it was resolved when we reinstalled SAPR3 module to the old server. Now we're seeing it again. Any ideas? The port for the old RFC agent is 20810, but we setup the new RFC agent to use 20820 using RW_MAINTAIN_INSTANCES.
ORA-04061: existing state of  has been invalidated
ORA-04061: existing state of package body "SYSJCS.RSISYS" has been invalidated
ORA-04065: not executed, altered or dropped package body "SYSJCS.RSISYS"
ORA-06508: PL/SQL: could not find program unit being called: "SYSJCS.RSISYS"
JCS-00270: master agent is not able to start running this job
Any help is appreciated. Thanks!!
Renee
Edited by: Renee Allred on Apr 28, 2009 11:04 AM

Answer 1

Thanks for your quick reply!
Yes we have run RW_SAPR3_INSTALL once for the new SAP server and once for the old. After running the install, we recompiled from RS prompt, then compiled all invalid objects, then ran many grants and created synonyms to allow SYSJCS access to RSI objects (and vice versa). When we run a job in the new SAP instance we get the below error. Maybe this helps?
RSI-00001: unable to connect to localhost port 20810; error -1
OS-22: Invalid argument
Error when connecting to host null on port 20810
Here are the grants/synonyms/etc that were run once as SYSJCS and once as RSI user.
revoke priv create_any_script from bechtel_operator_q;
grant execute on rsireg to IM;
grant execute on rsivar to IM;
create public synonym rsireg for sysjcs.rsireg;
create public synonym rsivar for rsi.rsivar;
grant execute on sysjcs.rsisys to RSI;
drop public synonym RSI_XBP_VARIANT_CREATE;
create public synonym RSI_XBP_VARIANT_CREATE for rsi.RSI_XBP_VARIANT_CREATE;
grant execute on RSI_XBP_VARIANT_CREATE to IM;
drop public synonym RSI_XBP_VARIANT_CHANGE;
create public synonym RSI_XBP_VARIANT_CHANGE for rsi.RSI_XBP_VARIANT_CHANGE;
grant execute on RSI_XBP_VARIANT_CHANGE to IM;
commit;
I can try running RW_SAPR3_INSTALL again for the new server but I'm afraid it will break the old instance just like it did before.
Renee