Please post any database errors present in the alert log when these failures happen.
Did you follow all of the steps from the R12 11g upgrade note?
Interoperability Notes EBS 12.0 and 12.1 with Database 11gR2 (Doc ID 1058763.1)
It is precisely Check Periodic Alert and Check Event Alert concurrent programs that are failing with APP-ALR-04140 Oracle Alert was passed an unknown datatype. ROUTINE=alrrss FILE=...alr/lib/alrupi.c line =298 Same error reference/description for both ALECDC (periodic) and ALECTC (event alert) . Which Patch to use ?
Hi Kandasamy -
we have Oracle Alert - Version 12.1.3 and Oracle Database - Enterprise Edition - Version 126.96.36.199. Patch 13259364 seems maybe can work on our environment. It refers to a different file(aluprf.c) that fails though but everything else - signal11, datat ype problem message, cause - can work for us. You think we should try to apply?
Hi Salazkin Ann,
Please go ahead and apply. Please test it on similar non-prod environment.
Hope this helps to resolve!
because that patch is listed for 188.8.131.52 and we already have a patch set applied for 184.108.40.206 - dba is not installing it.
Related question - because issue happens as a result of the post upgrade step - to change data type from LONG to CLOB - can we just revert back the data type from CLOB to LONG for those 4 tables that related to the ALERTS - alr_alerts, alr_profile_options, alr_response_messages, alr_valid_responses? It seems an optional step in the upgrade... What do you think?
The more we think - it seems the data type change step is an optional - we do not use LONG data type in our custom tables and it does not go well seems like for the standard Oracle tables - could we skip this step altogether?