I recently upgraded OWB 126.96.36.199 to 188.8.131.52 and within the Design Center, I receive error RTC-5161 when deploying a MAPPING. My process flows and all other objects deploy successfully but the MAPPING pops up the RTC-5161 error
Here is how I went about my upgrade, can anyone tell me if I am missing something?
-Installed OWB 184.108.40.206 on a new server, configured Workspaces, workflow workspace user
-Exported an OWB 220.127.116.11 project MDL and imported into the 18.104.22.168 and the Design Center automatically UPGRADED my project.
-Registered all locations
-Revalidated all locations within the ROPOSITORY BROWSER(the statuses were previously showing UNKNOWN, now they are all valid)
I need help PLEASE, if anyone could point me to something I am overlooking....
AGAIN, ONLY the MAPPING will not deploy, but the Process Flows generates and deploys with no issues.
I tried running the DEPLOYMENT of the Project from the command line(OMBPLUS), here is the error generated:
Processing module LOCATIONS ...
Deploying module name: FFL_DL_BMFENT_FFM_BMFENT
module name is FFL_DL_BMFENT_FFM_BMFENT
Deploying module name: DBL_EFDS_DL_BMFENT_DBM_TGT_EFD
module name is DBL_EFDS_DL_BMFENT_DBM_TGT_EFD
Deploying ... CONNECTOR : DBL_EFDS_DL_BMFENT_DBM_TGT_EFD/CONN_FFL_DL_BMFENT_FFM_BMFENT
Error deploy drop action plan for DBL_EFDS_DL_BMFENT_DBM_TGT_EFD/CONN_FFL_DL_BMFENT_FFM_BMFENT, err msg= "OMB05602: An error occurred during deployment: DeploymentContextImpl.generate WBGeneratedObject is null or length 0 for CONN_FFL_DL_BMFENT_FFM_BMFENT"
Error deploy LOCATIONS : CONNECTOR
I have not done 11gR2 upgrade but this looks like a problem of connector.
Try to drop and deploy all of your connectors first and then do the same for mappings i.e. first drop and then deploy.
Go to your process flow and click on the map. Then on the toolbar select the Edit drop down. Select synchronize. This will bring up the synchronize window. You should see the map you are trying to sync (if not select the map you're trying to sync). Leave "inbound" as selected default. Then try redeploying your process flow.
Let me know how it goes
Fixing this actually entailed going through the repository browser and checking the first optional feature during the configuration of the workspaces etc
thanks for all your help!
Now I have another issue with synchronization:
I noticed that doing an inbound synching of my staging table using replace option and by object name, the preview window that pops up shows my objects to be updated not matching one to one.
Has anyone ran into something like this?
The synchronization preview shows source to target columns NOT MATCHING one to one.....