CA View - Copy partial database content to another database
Article ID: 191173
Updated On:
Products
Deliver
View
Issue/Introduction
In their DR system, the client wants to unload some reports from a View database, to create another database in another system.
They want all of the reports to be on the disk layer, as tape will not be available.
They want all of the reports to be on the disk layer, as tape will not be available.
Environment
Release : 12.2
Component : CA View
Resolution
The client ran the following jobs:
. . SARDBASE Selective UNLOAD
. . SARDBASE ADDDS, to create a new database.
. . SARDBASE LOAD, from the selective UNLOAD.
. . SARBCH /LOAD on all reports, putting all reports to disk, to status of PERM or PTMP.
They then wanted to have that database in another environment, by:
. . Running a SARDBASE UNLOAD on the new database.
. . Running SARDBASE ADDDS, to create a newer database.
. . Running SARDBASE LOAD, from the UNLOAD.
As a result of the above, all of the reports on the newer database will be on disk.
The above is possible ONLY BECAUSE there will not be a SARSTC task or backup run on the newer database, which will be static and only used for retrieval.
. . SARDBASE Selective UNLOAD
. . SARDBASE ADDDS, to create a new database.
. . SARDBASE LOAD, from the selective UNLOAD.
. . SARBCH /LOAD on all reports, putting all reports to disk, to status of PERM or PTMP.
They then wanted to have that database in another environment, by:
. . Running a SARDBASE UNLOAD on the new database.
. . Running SARDBASE ADDDS, to create a newer database.
. . Running SARDBASE LOAD, from the UNLOAD.
As a result of the above, all of the reports on the newer database will be on disk.
The above is possible ONLY BECAUSE there will not be a SARSTC task or backup run on the newer database, which will be static and only used for retrieval.
Feedback
Yes
No
Powered by
