Download Creation of “Content Enrichment” jobs

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Open Database Connectivity wikipedia , lookup

Microsoft Jet Database Engine wikipedia , lookup

PL/SQL wikipedia , lookup

Database wikipedia , lookup

Concurrency control wikipedia , lookup

Relational model wikipedia , lookup

Oracle Database wikipedia , lookup

Astrophysics Data System wikipedia , lookup

Database model wikipedia , lookup

Clusterpoint wikipedia , lookup

Versant Object Database wikipedia , lookup

ContactPoint wikipedia , lookup

Transcript
05/05/2015 – Documented Solution for the creation of Oracle Public Database Links:
Define the reference pattern that will detect the Public Oracle Database Links:
Regular Expression:
([a-zA-Z_0-9\.]+)@[a-zA-Z_0-9]+
Other Reference pattern that was not used
Other Reference pattern that was not used
Creation of “Content Enrichment” jobs
Detect Database Link Usage via Search String
Create Links to Objects referenced by DB links
Creates links between a caller of a database link search string and an object matching the full name through a database
link
Image Continued…
SQL
/* Creates links between a caller of a database link search string and an object matching
the full name through a database link */
/* Creates links between a caller of a database link search string and an object matching
the full name through a database link */
insert into CI_LINKS
(CALLER_ID,
CALLED_ID,
LINK_TYPE,
ERROR_ID)
select distinct a.IdClr,
ofn.IdObj,
'useLink',
0
from (select kst.IdKey,
kst.KeyNam,
upper(substr(kst.KeyNam, 1, strpos(kst.KeyNam, '@') - 1)) as ObjectName,
/* either of the form <SchemaName>.<ObjectName>, or of the form <ObjectName> */
upper(substr(kst.KeyNam, strpos(kst.KeyNam, '@') + 1)) as DBLinkName
from Keys kst
where kst.ObjTyp = 676
) kst
/* 'Search String' object */
join (select kbdl.IdKey,
kbdl.KeyNam
from Keys kbdl
where kbdl.ObjTyp = 138732) kbdl
/* 'Oracle database link' object */
on lower(kbdl.KeyNam) like lower(kst.DBLinkName || '\.%')
join (select od.IdObj,
od.InfVal
from ObjDsc od
where od.InfTyp = 45014
and od.InfSubTyp = 4) od
/* 'connection string' property */
on od.IdObj = kbdl.IdKey
join ObjFulNam ofn
/* search string matching object */
on ofn.FullName like upper(od.InfVal || '\.%')
and ofn.FullName like upper(od.InfVal || '\.%' || kst.ObjectName)
join Acc a
/* search string caller object */
on a.IdCle = kst.IdKey
/
Update CAST System Views
01/12/2014 – AIP 7.3.0 at NYC SCA – workaround to see “Public” schema
Extraction results on PTS_ORA show that the “Public” schema is not seen in the DMT package view.
I re-did the extraction and delivery of the all schemas including the PTS_ORA schema and then copied the PTS_ORA
delivery output to a temp folder.
I then created a PTS_ORA package selecting as source the Oracle delivery files.
At this point, I see that the ‘Public’ schema appears as a possible selection in the DMT.