This content has been marked as final. Show 6 replies
To remove the 1 Message
Start up two Unix sessions.
In session 1 stop adapter.
In Session 2 run ignorErrors (ORA-XXXX)
In Session 1 start adapter once stoped.
Thanks for responding.
But is this applicable to ProcessConnect? I know this is what you do in InterConnect. I can't find the command, ignorErrors, in the ProcessConnect home.
Sorry about that. Not sure how u would do this in ProcessConnect.
BTW, the IC syntax is, for example:
where 20010 here is the error code you want to skip, without the string 'ORA' in front of it.
You also don't stop the adapter, but you need to bounce the adapter once the message is skipped if you don't want to skip future ones.
.... unless the steps you have given is for 904.
These steps I have given here is for 902.
What do you mean by bouncing the adapter. We used the above process to remove 1 message only and we were using 9.0.2.
What I meant by 'bounce' is to STOP and re-START the adapter. This kinda 'clears' what codes are ignored on the fly, so the adapter will not ignore them anymore. Was not aware that you can run the command when the adapter is already stopped. The steps I had given is what we have been doing in 9.0.2. I guess it works both ways. We were not using file persistence, wonder if this made any difference.