Eric Lehti
VIP Member
How do you deal with SVR (Software Version Repository) during A92 upgrade Test Phases and go-live?
We keep SVR files F9801, F9802, F98012, F98013) in our security libray so that all environments have access to SVR.
We are in phase 3 of A92 upgrade to ALT* test environment. Loaded A92 source to JDFSRCALT library. Therefore, the SVR files in ALTSEC (F9801, F9802, F98012, F98013) is a complete snapshot of SVR from our current production and the new A92 objects and source.
And because I like the production SVR to be the central repository for all source and objects, I have purged the production SVR files and copied the ALT* data with *REPLACE onto production F9801, F9802, F98012, F98013.
I will review the upgrade guides and programmer guides and check with Oracle Tech Support to learn what impact this action will on SVR when we go live with A92.
We keep SVR files F9801, F9802, F98012, F98013) in our security libray so that all environments have access to SVR.
We are in phase 3 of A92 upgrade to ALT* test environment. Loaded A92 source to JDFSRCALT library. Therefore, the SVR files in ALTSEC (F9801, F9802, F98012, F98013) is a complete snapshot of SVR from our current production and the new A92 objects and source.
And because I like the production SVR to be the central repository for all source and objects, I have purged the production SVR files and copied the ALT* data with *REPLACE onto production F9801, F9802, F98012, F98013.
I will review the upgrade guides and programmer guides and check with Oracle Tech Support to learn what impact this action will on SVR when we go live with A92.
