nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Oracle Communities

Oracle Analytics and AI

Child Item

Codes d'erreur : OPR4ONWY:U9IM8TAC:OI2DL65P

User_1OLX7

Bonjour Madame, Monsieur,

J'ai fait une modification dans notre OBI (ajout d'un lien entre une table de fait et une dimension), au moment de lancer la requête, j'ai un message suivant:

Codes d'erreur : OPR4ONWY:U9IM8TAC:OI2DL65P

Etat : HY000. Code : 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] Une erreur générale s'est produite. [nQSError: 43113] Message renvoyé par OBIS. [nQSError: 43119] Echec de la requête : [nQSError: 14070] Couverture de source de table logique introuvable pour les colonnes logiques : [Date besoin appro recalée]. Vérifiez que les clés de niveau plus détaillées sont correctement mises en correspondance. (HY000)

Pourriez-vous m'aider pour comprendre d'ou vient le problème? Quelle procédure à suivre pour le corriger?

Merci d'avance,

Cordialement,

Find more posts tagged with

Accepted answers

All comments

User_1OLX7

We have checked all our links without success.

We waited a help to resolved the issue.

Theses reports are very important for our production

Thank by advance

[Deleted User]

The problem is your model. Why does your logical dimension have 30 sources? Where do those sources point to? Why is the physical fact table mapped to a logical dimension source? What's the content of the logical dimension? What's the content of the logical fact? Is the physical fact alias'ed or just used as-is?

You have to think in models. OBI/OA works with models.

User_1OLX7

Hello,

I'll not say yours questions aren't legitimeated, and it's not the time to rebuild a new dimension.

But, the Dimension has been created with such structrure and it works utill a modification has been done and we have so far the error message :

Error codes: OPR4ONWY: U9IM8TAC: OI2DL65P

State: HY000. Code: 10058. [NQODBC] [SQL_STATE: HY000] [nQSError: 10058] A general error has occurred. [nQSError: 43113] Message returned by OBIS. [nQSError: 43119] Query failed: [nQSError: 14070] Logical table source coverage not found for logical columns: [Appropriate need date reset]. Check that the more detailed level keys are correctly mapped. (HY000).

what's now the good option? restauration of OBIEE?

Thanks,

[Deleted User]

If you are not willing to find the root cause of the error, then I can not help you. My points are legitimate since they are the aspects playing into the genesis of that error - i.e. where does it come from.

Alas if you don't try to find the root cause and think about how your model is built and how and what it should support, then nobody can help you.

@Gianni Ceresa kept out of this thread but maybe he is willing to add his 10 cents and convince you that root cause analysis is what's necessary because otherwise you're randomly twisting knobs in the dark without comprehending what's going on.

Gianni Ceresa

As Christian said I was staying away of this because OBIEE in French just doesn't work (not technically): all the messages and errors have little to no meaning in French as things have been translated fairly random (and I do speak French fluently!).

That error is a fairly common one, mainly when adding a new LTS and columns to a dimension. In general it's easy to fix because the dimension has 2-3 LTS, therefore very simple to check the various joins and make sure everything has joins in the physical layer to let OBIEE know how to build a query.

Your screenshots shows at least 27 LTS for a single dimension: how should we randomly be able to tell you the single piece missing to fix the error? Impossible.

When you have 2 LTS it's simple to say "do all the LTS join correctly?" , just as simple to answer and verify (or even see if a screenshot is posted), with 27+ it is just impossible.

Look at https://datacadamia.com/dat/obiee/obis/dimension_fragmentation_filter, the point 5.2. This should be your error, as you see the solution is very simple. But you have 27+ LTS, so the very simple thing when having 2 LTS become a nightmare which can be done only having the RPD in front of you and knowing very well what the build does, in which way, what are all the physical tables used, what they contains, what is their role.

We don't know how the RPD has been built and why you have those 27+ LTS for a dimension: as you say it did work for you so far (correct or not correct, that wasn't the question). The answer to your question about how to fix your issue is in your RPD, you know have all the theoretical elements to find out what is causing that issue and fix it.