So the CREATE VIEW gives joy [though possibly some issues even with
that], not so much the restored VIEW. Any issue with CREATE VIEW
should be treated as a separate issue from the Restore Object activity,
until shown otherwise. At least the specific failure information for
that activity should be presented separately; and clarified if the
apparently same issue from 2013 having gone unreported\unresolved.
When a VIEW is created the /statement text/ is maintained in the
*FILE object and in the catalogs. When the VIEW is restored to a new
library, the qualified table-references must be updated to reflect the
new schema [library] name.
I did not go back to review those topics, but I suppose the current
anomalies with CREATE VIEW are /the same/ as those in the past, and
that issue was never reported, diagnosed, and prevented with a PTF.?
Reporting the error(s) as defects; providing necessary
information\steps for the development to re-create the issue and thus
to investigate corrective [code change] actions.
This mailing list archive is Copyright 1997-2015 by MIDRANGE dot COM and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available here. If you have questions about this, please contact