CRWEB00000119 - after upgrade from bi 4.0 to 4.1
we just upgraded out BI 4 platfrom to BI 4.1
we have a number of reports that had been taken from our XIr2 server to our BI platform 4.0 server
they use an odbc connection to oracle
to get them to work on the 4.0 platform we had to set the connection details (log in to CMC --> folders-->right click---> database config) to "Specify a custom table prefix"
now after upgrading to 4.1 we get an CRWEB0000019 error unless we set it back to "use default table prefix"
the table prefix for both is exactly the same except... the default one has a . (period) at the end and the custom one does not.
will jobs that were scheduled with the custom table prefix fail even after we change the database settings?