Categories
- All Categories
- Oracle Analytics Learning Hub
- 26 Oracle Analytics Sharing Center
- 18 Oracle Analytics Lounge
- 234 Oracle Analytics News
- 45 Oracle Analytics Videos
- 15.9K Oracle Analytics Forums
- 6.2K Oracle Analytics Idea Labs
- Oracle Analytics User Groups
- 87 Oracle Analytics Trainings
- 15 Oracle Analytics Data Visualizations Challenge
- Find Partners
- For Partners
Codes d'erreur : OPR4ONWY:U9IM8TAC:OI2DL65P
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,
Answers
-
Hello User_10LX7
The official language of these forums is English so that all participants can benefit equally from the questions asked and the responses posted. Please update your question accordingly.
Also you may want to update your user name in order to set it to something more personal rather than the technical string.
0 -
Right, here the message:
After have done some modifications in OBI (added a link between a logical table and a dimension), when launching the query, I have the following 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)
Could you help me understand where the problem is coming from?
What procedure to follow to correct it?
Thank you in advance,
Regards,
0 -
Check your model. It looks like it is inconsistent and your dimension and fact are not related / relatable as you think they are. Do the two entities really possess a relationship? Especially a relationship with regards to the content levels of the entities?
0 -
Hello,
Here the overview of my Business Model and Mapping of DIM_OM (1).
In this case, there are sevral sources for DIM_OM (1), and DIM_OE (1) based on a phsical table, in this table, i can find all informations related to a customer’s order, the primary key are n° oe, indice oe
DIM_OE (2) is a logical table sources DIM_OE (1) and FAIT_OE_ATTENTE
I need this to find if the customer’s order in waiting. Can i use this logical table just to retrieve a column, can i use directly the FAIT_OE_ATTENTE ?
DIM_OE_NOSISREP_REPORT_MOTEUR (3) is also a logical table DIM_OE (1) and FAIT_ NOSISREP_REPORT_MOTEUR
Linked by the foreign key on the FAIT_ NOSISREP_REPORT_MOTEUR (N° oe and idice oe), in the table FAIT_ NOSISREP_REPORT_MOTEUR i need the date data linked to the customer’s order.
But there is not a link between table DIM_OE (1) and FAIT_ NOSISREP_REPORT_MOTEUR at BMD level.
Is it need to add a link ?
When i execute the requery, i have the message
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)
0 -
So you have a logical dimension with more than 20 sources and one source which you show also maps to the fact.
To be frank this doesn't allow any statement on your issue as it only covers a minimal part of your model. A dim is a dim but in terms of modelling it only gets a sense through its relationship with facts.
And having a physical fact table be a part of one of the dim LTSs is not a model. It's part of the dimension content.
0 -
Thank you for the answer !
For the case 3, is it not better to use directly FAIT_ NOSISREP_REPORT_MOTEUR, rather than use the DIM_OE and FAIT_ NOSISREP_REPORT_MOTEUR linked by a foreigne key?
0 -
We can't know. We have no idea of what you're trying to model. You know your entity relation diagram. We don't
In any case adding a physical fact table to a dimension LTS doens't mean you're establishing a relation between the two entities. You do that if you want to use columns from that physical table or if you're snowflaking.
But based on your input we can't know any of those things. There's about 90% of the pertinent information missing.
0 -
Here concerning then Physical model
And Business model
as showing, there isn't link at BMM level, can i have informations from FAIT_ NOSISREP_REPORT_MOTEUR in CASE 3 ?
0 -
What is case 3?
If the first pic is the physical model, then why are there 30 LTSs in the logical dim?
Why are all you r "logical" entities named after physical tables which in the case of the dimension they very clearly do not represent - since the dim is made up of 30 LTS with who-knows-how-many-physical-tables behind those?
Once more: We aren't in front of your RPD nor do we know what you are trying to achieve - the goal you are trying to attain. Your input is simply and purely too convoluted and not enough specific to lead to an exact problem you want to solve.
Simply put with your own images above: IF the picture above is your physical model, then the second pic just needs a relationship between "FAIT_NOSIREP...." and "DIM_OE".
And since that one connection seems to raise the initial error, the message is simply: Your model is wrong because of what you're doing in the LTS and nobody can tell you what you're doing wrong if you
- only show one LTS one of your 30
- never talk about the actual problem you're trying to solve in normal business language
- never talk about the entities which are involved in this (no, not your tables or your logical objects with technical names - the entities )
- etc etc
0 -
Did you give up on this?
0