This content has been marked as final. Show 2 replies
1. taking an export of your current repository using the oaiexport script.
2. Stop the adapters.
3. Kill all connections to the repository (iStudio, SQL*Plus etc.)
4. Stop the repository.
5. Use the hubschema script, using the -drop argument. (This will drop your user e.g. OAIHUB904). You should see "User dropped"
6. Use the hubschema script, using the -create argument. (This will recreate the repo user).
7. Use oaiimport with your recently created *.dmp repository file.
8. Start the repository
9. Start your adapters.
It could be that there was a problem when your AQ's were created, or they have become unstable. The oaiexport / drop / create / oaiimport routine should help clear this problem. If not, let us know.
Initially I would try calling the subscribe package standalone in SQL*plus or TOAD just to check its not somekind of config problem...
The subscribing adapter trys calling the subscribing package passing in the message as an oracle data type.
I would write a small pl/sql wrapper that calls you subscribing package outside of the runtime Interconnect environment. If this all works and you can insert data into the table then it maybe something to do with the metadata in the repository and then i'd go along with Ian's suggestion.
But usually if you can successfully use iStudio to edi things then usually the repository is OK.
Also from your log you can see that it has picked up the message and is trying to call the packaged/procedure so it looks like the adapter is working OK.