Errors when 'Updating Objects' during migration from r2 to 3.1 FP1.8

Question

Has anyone seen errors like this the Update Objects error log file.  I've done 5 or 6 test migrations, and before it was normally working fine, but a couple of times I would get thousands and thousands of rows in the log file such as this:
ID     Object     Path     Error
1000023     1000023     ...     
1000029     1000029     ...     
1000036     1000036     ...     
1000069     1000069     ...     
1000070     1000070     ...     
1000075     1000075     ...     
1000107     1000107     ...     
1000116     1000116     ...
In testing, there doesn't seem to be much of an indication of any problems, except that recurring schedules don't work after the upgrade, which is a big deal for us as we have about 1000 of them.

Answer 1

I can't tell what  the compiler is complaining about. I tried a version of your code sample:
struct Error { Error(int); };
struct Warning : public Error {
    Warning(void) : Error(-8) {}
struct Warning_NoNewMilestones : public Warning {
    Warning_NoNewMilestones(void) { }
int main()
    throw  Warning_NoNewMilestones();
It compiled without complaint using C++ 5.12 (Studio 12.3).
There are always two possibilities: The code is OK and you hit a compiler bug, or the code was always invalid but the earlier compiler did not catch the error. Since you seem to have a variety of error messages, the most likely scenario is that the new compiler is catching more errors in your code.
In general, there is no option to have the compiler accept invalid code. In rare cases, where the error is harmless, or when other compilers typically accept the invalid code, we have an option to allow the code. Please review the list of compiler options in Appendix A of the C++ Users Guide.
Oracle Solaris Studio 12.3 Information Library
If the reason for an error message is not obvious, you can post a (preferably small) example that can be compiled to show the error message. Someone in the forum can then probably explain the error, or verify that you hit a compiler bug.
Here is an example of the badbinaryop error message:
% cat z.cc
struct S { };
int main()
    S s;
    int j = s + 3;
% CC z.cc
"z.cc", line 5: Error: The operation "S + int" is illegal.
1 Error(s) detected.
I hope the reason for the error is obvious in this case.