My Oracle Support Banner

LSH BA Schema With PTVs In It Breaks Other Enabled BA Schemas (Doc ID 1680829.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Oracle Life Sciences Data Hub - Version and later
Information in this document applies to any platform.


Customer Problem Description

Problem Summary
LSH BA schema with PTVs in it breaks other enabled BA schemas

Problem Description
Customer have noticed an oddity when initializing multiple GVA schema, when one of them includes a table instance that is a "Create table as view" table instance from a pass-through loadset.

They frequently initialize multiple (generally 3-6) GVA schemas as the same time and this seems to work, excluding some intermittent issues that they don't really have enough detail to log a ticket about yet (in which initializing a schema once fails, but running the same command a second time works).

They also have a small number of GVA schemas that contain PTV table instances that are sourced from remote systems.

What they have observed is that they were  unable to initializing both a PTV-containing GVA schema and a non-PTV schema at the same time. If schema A contains PTV TIs and schema B does not, for example, initializing A first and then B will result in the A synonyms containing no data. If they reverse the initialization sequence, the schema A synonyms will contain data but the schema B ones will not. If A and B both contain regular table instances, then they can be initialized in any order and both will work using the same commands.

Is there something about the system context used by PTVs that causes their inclusion in a GVA schema to break the context necessary for other schemas to operate?


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

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