My Oracle Support Banner

pin_virtual_gen Rlated Questions for 7.5 PS11 Upgrade (Doc ID 2026278.1)

Last updated on OCTOBER 03, 2019

Applies to:

Oracle Communications Billing and Revenue Management - Version to [Release 7.5.0]
Information in this document applies to any platform.


This note is to discuss about Generating Virtual Columns on Event Tables related questions raised from 7.5 PS11 upgrade.

DOC reference:


Questions and Answers

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document
Questions and Answers
 The BRM document says the pin_virtual_gen utility checks if you have POID custom type names for your custom storable classes. This step is taking 10 to 12 hours in production size database. Is there any alternate ways to populate the required data if we know the list of custom tables and poid_type?
 What exactly this step does? pin_virtual_gen -gentasks verify_types -execute
There are lots of parallel select statements which does full table scan on EVENT_T. Is it only verification or does any update ?
 If the user knows the list of custom tables and poid_type, is there any way to bypass this step like directly creating dd_types_T?
What is the content of dd_types_t? In which use cases the object type is not present in dd_objects_T, should all pin_deploy should create dd object entry? Any document reference for this table?
If it is only validation, can the user validate that before (may be in copy of production data or backup) and if there is no data issues found then skip this step in actual upgrade?
Is this step is mandatory to run final step? In other words, is there any dependency between this step and final step that is pin_virtual_gen -gentasks create –execute?
 If it correct that -gentasks create -execute does not read any data created in previous steps? If the user is confident that all the objects are there in dd_objects_t, can the user directly run create -execute?
After converting it to virtual column, what if anyone/any program update "xxx", will it internally update dd_types_t or dd_objects_T?
Do you see any issues to fix any errors reported in this verification step before and skip the verification step in actual upgrade? Is there any code issue for doing that?

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.