Extracting latest schema version from view tables

Question

Hi
We have a shell script, which runs sql against the oracle designer tables to extract table, column info. This used to run fina against our pre 6i designer version.
eg
select rtrim(lower(t.name))
     from ci_table_definitions t,ci_application_systems a
     where a.latest_version_flag = 'Y'
     and a.name = 'KERNEL_MASTER'
     and t.application_system_owned_by = a.id
     order by t.name asc;
we have upgraded to Designer 6i now and this has resulted in our script not working. The above sql complains about the fields latest_version_flag and application_system_owned_by not existing, which they don't.
Does anyone know what fields we can used to acheive the same result on the designer 6i setup?
Basically we are trying to extract the table definitions for the latest version of a schema ( we called 'KERNEL_MASTER')
Any ideas?

Answer 1

Here's a copy of old Oracle Support note:190516.1 to give you some idea where to start:
Differences in the Repository API between Designer 6.0 and Designer 6i
1) Tables SDD_ELEMENTS and SDD_STRUCTURE_ELEMENTS
In Designer 6.0, all repository elements were hold in 2 main tables called
SDD_ELEMENTS and SDD_STRUCTURE_ELEMENTS. Those tables don't exist anymore.
Any API script that references those tables will fail with the following error:
ORA-00942: table or view does not exist
To avoid this error, replace the reference to SDD_ELEMENTS or
SDD_STRUCTURE_ELEMENTS by the corresponding API view CI_... (as it was
recommended in previous releases of Designer).
2) new Columns IRID and IVID
In Designer 6.0, the elements were uniquely identified by the column ID.
In Designer 6i the column IRID (Internal Repository IDentifier) identifies the
object tree. Every element version has the same IRID, but it has a different
version label and a different version identifier, called the IVID (Internal
Version IDentifier). An IVID is unique over all versions of all elements.
To avoid select statements returning different rows for different versions of
the same object, you should define the Context Workarea before executing
a statement (See next point).
3) Context workarea
The result of a select from a CI_... views may include the same object several
times, because the repository includes several versions of the object.
To avoid this, you should specify the context workarea.
A workarea is a specific view on the repository which contains at most one
version of each element. In other words, a workarea is version resolved.
You can specify the context workarea by using the following PL/SQL call:
jr_context.set_workarea('<workarea_name>');
Once done, you will work within the context of this workarea only.
4) Column APPLICATION_SYSTEM_OWNED_BY
In Designer 6.0, all CI_... views for Primary Access Elements (PACs) included a
column APPLICATION_SYSTEM_OWNED_BY for the reference of the application system
owning the element. This column doesn't exist in Designer 6i anymore.
Any API script that includes this column will fail with the following error:
ORA-00904: invalid column name
With Oracle Repository, the reference to the application of an element can only
be found through the table SDD_FOLDER_MEMBERS. The column MEMBER_OBJECT refers
to the IRID of the element, and the column FOLDER_REFERENCE refers to the IRID
of the folder or application system containing the element:
CI_..............SDD_FOLDER_MEMBERS........CI_APPLICATION_SYSTEMS
....................FOLDER_REFERENCE >--------- IRID
IRID ---------------<MEMBER_OBJECT
Suppose for example the following SQL that worked fine in Designer 6.0:
select ent.name
from ci_entities ent
, ci_application_systems app
where app.name = '&App_Name'
and ent.application_system_owned_by = app.id;
This Select should be re-written like the following to run on Designer 6i:
select ent.name
from ci_entities ent
, sdd_folder_members mem -- the application system reference goes through sdd_folder_members
, ci_application_systems app
where mem.member_object = ent.irid
and mem.folder_reference = app.irid
and app.name = '&App_Name';
Note: this query only returns rows if the user who is executing it has been
granted SELECT privilege on application '&App_Name'