My Oracle Support Banner

Objectel Metadata Editor is generating wrong table name in Cache script after adding new type (Doc ID 1454090.1)

Last updated on APRIL 27, 2021

Applies to:

Oracle Communications Objectel - Version 2.10.2 and later
Information in this document applies to any platform.

Symptoms

Customer created a Equipment on table OBJ_FE. Now Customer is extending by using new table named Data_Power to store some of new attributes which are not present in OBJ_FE Table. In the metadata Customer have Database mapped accordingly to Table Data_Power.When creating the CacheWOTS script, the following hierarchy insert statement is created:
 

INSERT INTO Hierarchy(ObjectID, ParentID, Name, TypeCd, Path, Category,  Flag) SELECT X.AG2ObjectId, X.AG2ParentID, trim(X.FEAlias), 'RECTIFIE',  H.Path || to_char(X.AG2ParentID) || '.', 196, 3 FROM Data_Power X, Hierarchy  H WHERE X.TypeCode = 'RECTIFIE' AND X.AG2ParentID = H.ObjectID;  COMMIT;

 
As you can see, the insert for the special equipment select elements from Data_power and not from OBJ_FE. 
Customer is expecting, as OBJ_FE is base table always values need to select from OBJ_FE to Insert into Hierarchy Table. 
But in the MetaData Editor If you generate the cache script It will take the Top Database Map Element table name i.e Data_Power, Not OBJ_FE.

So Customer don't have a option to select the table name(Base table or extended table) for cache script.

Changes

 Customer is extending by using new table named Data_Power to store some of new attributes which are not present in OBJ_FE Table.

Cause

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
Symptoms
Changes
Cause
Solution
References


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