Repository Consistency Checker for ODI

Hello all,
I want to run RCC utility to check for my patch upgrade. Do i need to download RCC utility from My Oracle support or it already exist somewhere in the installation directory?
Thanks

Hello,
I have a problem with the RCC.
Java Version : j2re1.4.2_19.
Path(includes) : C:\Program Files\Java\j2re1.4.2_19\bin.
JDBC Oracle Driver: ojdbc14.jar
Config Properties: OK, no problem; connection successful.
Repository DB: Oracle 10g
Repository DB OS: Sun Solaris 9 or Windows 2003 Server (exactly same issue)
ODIW - ODIM user previlige: Admin ALL
ODI Version: 10.1.3.x
Although everything seems fine, I got an error during the repository consistency check. When I search the net for the error message I could not find anything.
D:\ORACLEDI\diag_tools\bin>rcc.bat
Options:
P r e p a r i n g a R e p o s i t o r y u p g r a d e ? 1
S e t t h e t y p e o f a n a l y z i s 2
S e l e c t t h e M a s t e r R e p o s i t o r y c o n n e c t i o n 1
Resetting the analyzed Models...
Resetting the reference data...
Analyzing the Master Repository...
Updating the RCC data...
Checking the structure and contents of your Repository...
Updating the reference data...
Building the Repository related objects...
Reverse engineering the Repository structure...
Verifying the Repository structure...
Traceback (innermost last):
File "../bin/ODI_consistency_check.py", line 2875, in ?
File "../bin/ODI_consistency_check.py", line 2507, in run_analyze_master
File "../bin/ODI_consistency_check.py", line 1395, in run_analyze_repository
+>>> Master - RUN___ANALYZE_REPOSITORY failed.+
Master - Verify Infrastructure
java.lang.ArrayIndexOutOfBoundsException: 0 >= 0
at java.util.Vector.elementAt(Unknown Source)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.getBindVar(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execCollOrders(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt(SnpSessTaskSql.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt(SnpSessTaskSqlI.java)
at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java)
at com.sunopsis.d
D:\ORACLEDI\diag_tools\bin>
Is this a kind of repository issue? Do RCC utility raise this error because my repository is not consistent? Hard to understand for me...
Any help will be appretiated.
Thanks.
Haluk

Similar Messages

Regarding Repository Consistancy Check

Hi All,
Its very urgent that i have ODI 10.1.3.5 version right now but i am planning to upgrade to 11g. Do i need to Upgrade my ODI to 10.1.3.6 for running RCC or can i directly run RCC on ODI 10.1.3.5.
Thanks

I think, its recommended to be on ODI 10.1.3.6 to have optimal results.
Check with this support doc for more details : How To Use The Oracle Data Integrator (ODI) - Repository Consistency Checker (RCC) Tool [ID 1058107.1]
Regards,
Santy.

-- Failed consistency check for this level

Hi guys,
I'm trying to validate a hierarchy, however, 1 level fails with that error message:
Level Name --> Failed consistency check for this level
I checked the column on physical layer - it has the same name and same datatype as the one in DB. The nullable flag is checked (there're no null values anyway). At the logical level - the key is created and it's the only level key at this level.
What could be a cause?
Thanks

Thomas,
since you've seen this before....did you have a problem doing "Estimate Levels" when you had measures in the hierarchy (usually they get there when you select a level for measure in its settings). I suspect the problem is in the measure - using FILTER function which references the dimension.
Thanks

How to deactivate consistency check for ODS?

Does anyone know if it is possible to deactivate the consistency check for an ODS?

Here is why you would want to do that -
In the ODS I am getting the following error: "InfoObject 0FISCYEAR was deleted for DataStore object ZOFIGL_6. This is not allowed as DataStore object ZOFIGL_6 contains data"
You can resolve this issue in a couple of ways -
The first being delete the data from ODS and reactivate the ODS (I would not like to take this approach as I do not want to delete the production data)
The second approach would be to send in a transport to correct this error but the transport will fail owing to the consistency check it does on the ODS when the transport is moved across. I could deactivate the consistency check, move the transport across and then everything should be okay.
NOTE: As a side not this is the production box and it is set to be non-modifiable which means that I cannot make any changes in the system.

" -- Failed consistency check for this level" when doing Estimate Levels

Hello again,
When you run "Estimate Levels" and you get "<-- Failed consistency check for this level"
What does it really mean? Can this break, because of NULL values in logical keys? Or perhaps anything else? Thanks
Thanks

Thomas,
since you've seen this before....did you have a problem doing "Estimate Levels" when you had measures in the hierarchy (usually they get there when you select a level for measure in its settings). I suspect the problem is in the measure - using FILTER function which references the dimension.
Thanks

Repository Consistency Check 39008 "does not join"?

I'm using Administration Tool 11.1.1.6.0 with a Repository version of 318.
I have imported my star schema metadata from the database using an OCI connection. All the joins were included, so I can go to Physical->Fact Table->Physical Diagram->Object(s) and Direct Joins and it shows my fact table linked to all my dimension tables. I then clicked-and-dragged my schema to the Business layer. I created my dimension by right-clicking on my logical tables in the Business layer and choosing Create Logical Dimension -> Dimension with Level-Based Hierarchy. This worked for all the dimensions that had only one level (a base level and a grand total level), but resulted in some odd errors when done for dimensions with more than one level. I got around these errors by manually creating these dimensions, clicking-and-dragging the logical columns in, and setting up the keys.
Only now when I do I consistency check, I get three of the following warnings, one for each dimension that has more than one level:
WARNINGS:
Business Model [Business Model]:
[39008] Logical dimension table [Logical Table] has a source [Physical Table?] that does not join to any fact source.At least, I think it is referring to the Physical Table, but changing the name of the Physical Table doesn't change the error message, though changing the Logical Table name does, so I'm not really sure what it is referring to. Here is what one looks like precisely:
[39008] Logical dimension table Time has a source TIME that does not join to any fact source.Now, each of the three multi-level dimensions have a base level with a key that is present in the Fact Table. I can even right-click on the Fact Table on the Business Layer and go to Business Model Diagram or Physical Model Diagram and get a diagram of my fact table linked to all of its dimensions, including the three in question. Analysis made in OBIEE work so long as I don't use those three dimensions.
Does anybody have any idea what I'm missing here?

Thanks, it looks like the field for those three logical dimensions was left blank for some reason. So it was because the Logical Dimensions weren't joining to the Fact Table, rather than the Logical Tables?

When do consistency check for a sharepoint content databse : that RBSID in table AllDocStreams registered with RBS is invalid

Hi
In my sharepont farm a web application configured with RBS and its working fine,
when users upload pdfs the no of files are increased in RBS file system folder,
but when i run Consistency check before running RBS maintainer for cleaning garbage dta for this web applications content database , i faced below issue , its saying
C:\Program Files\Microsoft SQL Remote Blob Storage 10.50\Maintainer>Microsoft.Da
ta.SqlRemoteBlobs.Maintainer.exe -ConnectionStringName RBS_2 -Operation Consiste
ncyCheck -ConsistencyCheckMode c
Starting Maintainer tasks.
Starting RBS consistency check with check only.
The column <RbsId> in table <dbo.AllDocStreams>
registered with RBS is invalid.
and also when i repair consistency checks its saying same message, that RBSID in table AllDocStreams registered with RBS is invalid.
and also its recommended to check consistency before cleaning garbage data from content database
adil

http://social.technet.microsoft.com/Forums/sharepoint/en-US/e9bda580-b9e7-48c5-b18c-485e016677a1/rbs-maintainer-not-cleanup-files-in-file-system-sharepoint-2010?forum=sharepointadminprevious
The GC of RBS maintainer just purges BLOBs in SQL Server. And FILESTREAM GC is needed to purge the files in file system.
http://www.sqlskills.com/BLOGS/PAUL/post/FILESTREAM-garbage-collection.aspx : (FILESTREAM GC)... runs as part of the database checkpoint
process. This is what causes some confusion - an old FILESTREAM file will not be removed until after it is no longer needed AND a checkpoint runs.
Yes, In Simple recovery mode, just run SQL statement:
CHECKPOINT;
In Full recovery mode, two transaction log with CHECKPOINT are needed. Detail in the link above.
http://blog.avtex.com/2011/05/16/remote-blob-store-rbs-and-sharepoint-2010-part-2/
If this helped you resolve your issue, please mark it Answered

Consistency Checking Perform

Hi,
what are the minimum criteria to pass consistency checking for a given repository?
Regards
sandhya

hi Sandhya,
If you go thorugh the BI Admin guide CTRL+E-->Options -->help u will find the plenty of information about the best practices we need to follow
Repository metadata must pass a consistency check before you can make the repository available for queries. The Consistency Check Manager allows you to enable and disable rules for consistency checks, navigate to and fix inconsistent objects, and limit the consistency check to specific objects.
The Consistency Check Manager does not check the validity of objects outside the metadata using the connection. It only checks the consistency of the metadata and not any mapping to the physical objects outside the metadata. If the connection is not working or objects have been deleted in the database, the Consistency Check Manager will not report these errors.
The consistency checker returns the following types of messages:
Error. These messages describe errors that need to be fixed. Use the information in the message to correct the inconsistency, and then run the consistency checker again. The following is an example of an error message:
[38082] Type of Hierarchy '"0RT_C41"..."0RT_C41/MDF_BW_Q02"."Product Hierarchy for Material MARA"' in Cube Table '"0RT_C41"..."0RT_C41/MDF_BW_Q02"' needs to be set.
NOTE: If you disable an object and it is inconsistent, you will receive a message asking if you want to make it unavailable for queries.
Warning. These messages indicate conditions that may or may not be errors, depending upon the intent of the Oracle BI Administrator. For example, a warning message about a disabled join may be the result of the Oracle BI Administrator intentionally disabling a join, such as eliminating a circular join condition. The following is an example of a warning message:
[39024] Dimension '"Paint"."MarketDim"' has defined inconsistent values in its levels' property 'Number of elements'.
Best practices. These messages provide information about conditions but do not indicate an inconsistency. The message appears if a condition violates a best practice recommendation. The following is an example of a best practice message:
[89001] The Physical Table '"XLS_Forecast"."Forecast".."Sheet1$"' has no keys defined.
Apart from these joins,content levels,column formulas ,syntax's ....
source Admin guide
thanks,
Saichand.v

TDMS consistency check error

We are having problem at "consistency check for the rules".The
rules have been check and all are in green.i remember that SAP has
asked us to check tables CNVMBTRULEINCL and CNVMBTRULEFIPARS right? im
able to browse table CNVMBTRULEINCL but not CNVMBTRULEFIPARS. the error
message shows this table is not active, and i cant even open the table
in SE11/SE16/sm30.
the error message is as below:
x_ekpo|the rule import paramter im_bstyp will not be available for this object.
the same set of rule was used for first client(miq400), but this time its not working for second client(miq485) ..
the source and destination are the same for the first and second client.
thanks

the issue has been fixed in 0799873 2010

Routing Consistency Check in batch ?

Hey folks!
A business requirement has been raised to perform a consistency check for all Routing Task Lists for a specific plant. I'm aware of the consistency check within the Routing that can be performed online. Anyone know of a batch/background job that can validate routings and report errors?
The business case is as follows: Reference Operation Sets are utilized within Routing Task Lists. If a change is made to the Reference Operation Set (say add additional operations) and these additional operations conflict in the routing this ROS is utilized, this will cause a routing error. Yet there is no way to identify this error until someone checks the routing or writes a production order against.
Any help on the above would be great. Points are waiting to be awarded!

Nathan,
I do not think there is a background program that can run to check for such inconsistency.
However when MRP runs system will detect routing inconsistency & will display exception message against planned order.
So nett result is MRP controller will know about this much before he converts planned order to production order.
They can look for exception messages either under Tcode: MD04/ MD05 or collectively under MD06/MD07 group by exception message.
Message 62 - Scheduling: Master data inconsistent is one such message & it falls under Exception group 4 in standard SAP.
So if MRP controller checks Tcode : MD06 & limits selection criteria by exception group 4 messages he can nail down all such errors in advance.
Thanks,
Ram

CR Consistency check

Hi experts,
I'm trying to transport CRs from our system to another one. Before processing further, I'm making some checks: Syntax check and Request Consistency.
But I have a problem with a task: when I try to make the Consistency Check for that task, I get the following warning message:
Object messages: R3TR TABU BSPC_DL_STXTREP2
Object TABU BSPC_DL_STXTREP2 has object function "K", but no key
Object messages: R3TR TABU PPFTSFFXCU
Object TABU PPFTSFFXCU has object function "K", but no key
Object messages: R3TR TABU PPFTWFCU
Object TABU PPFTWFCU has object function "K", but no key
What is the problem? How can I solve it?
Thanks & Regards
Stefano

Looks like you learned something from this
Consistency Check of RPD without opening it
I expect you mark or update on this before you post any thing.
Try out if you can call any batch files from Answers, I dont think you call them.
Edited by: Srini VEERAVALLI on May 13, 2013 11:19 AM

Time Dimension Consistency Check Failed

Dear all,
Got a issue..
A cube which is found to be active in RSA1, but when we do the consistency check for time dimension in the transaction RSRV, we get the following error.
Unknown, profound errors with instance creation in test "CL_RSRV_CHK_TIM_DIM"
Pl help to resolve this issue.
Thanks,
Ramya

Hi Ramya,
Welcome to SDN...!!
Check with the Correct Error option in RSRV after selecting testing ur cube.
Best Regards,
SG

LiveCache Consistency Check question, OM17

I have a general question about a LiveCache Consistency Check (transaction OM17). I know that it is a data inconsistency b/w the SAP APO database and SAP APO LiveCache. But what does that mean to a functional user? Can someone explain this in layman's terms?

In Layman terms, you can say that this checks the INCONSISTENCY between LiveCache and Database.
Here is a detailed documentation on each of the Object Types
Consistency Check for Setup Matrices
The consistency check for setup matrices contains:
· A check whether the setup matrices exist in liveCache
· A check whether the setup transitions exist in liveCache
· A field comparison between the setup transitions in the database and those in liveCache
When the setup matrices are corrected, the setup matrices in liveCache are completely generated from those in the database. Previously nonexistent setup matrices and setup transitions are newly created in liveCache. Superfluous setup transitions are deleted from liveCache. Setup transitions that differ at the field level are adjusted to match the database status.
Consistency Comparison for Block Basis Definitions
Use
When you set this indicator, checks are performed in liveCache and in the database on characteristic values for block basis definitions:
· The existence of block basis definitions is checked.
· The consistency of the characteristic values is checked.
After the checks you can call a correction function in the check results display. When correcting the error, the system deletes obsolete block basis definitions in liveCache. The system completes or corrects missing or inconsistent block basis definitions in liveCache.
Note
The check is performed independently of the planning version.
Consistency Check for Resources
The consistency check for resources contains:
· A check that the resource and corresponding time stream exist in liveCache
· An check that a resource's characteristic blocks exist in liveCache
· A field comparison between the database resource and the liveCache resource
When correcting the resources, the resources in liveCache are completely generated from the database resources. Previously nonexistent resources are created in liveCache.
Consistency check for downtimes caused by maintenance order
The consistency check for maintenance downtimes contains:
A check that the maintenance downtime has a reference to an existing maintenance order.
A check that the dates of maintenance downtime correspond to the exisiting maintenance order.
When correcting the maintenance downtime errors, downtimes without maintenance order are deleted and wrong dates of downtimes are corrected in relation to the maintenance order.
Consistency Check for Product Location Combinations
Use
If you set this indicator the system executes a consistency check for product location combinations. The consistency check for product location combinations includes:
· A check for the existence of a product location combination in the database and in liveCache
· A field comparison between product location combinations in the database and in liveCache
· The determination of obsolete entries for product location combinations in the database
· A check for the existence of characteristic value assignments for product location combinations in the database and in liveCache
· A field comparison of characteristic value assignments for product location combinations in the database and in liveCache
After the check you can call a correction function from the display of check results. For the correction, the system deletes obsolete product location combinations from the database and in liveCache. The system corrects inconsistent product location combinations and characteristic value assignments for product location combinations in liveCache.
Consistency Check for Stocks
Use
If you set this indicator the system executes a consistency check for stocks. The consistency check for stocks includes:
· A check for the existence of a stock in the database and in liveCache
· A field comparison between stocks in the database and in liveCache
· The determination of obsolete entries for stocks in the database
· A check for the existence of characteristic value assignments in the database and in liveCache
· A field comparison between characteristic value assignments for batch stocks in the database and in liveCache
After the check, you can call a correction function from the display of check results. For the correction, the system attempts to correct inconsistent stocks in the database and in liveCache. If a correction is not possible, the stocks are deleted in the database and in liveCache. The system corrects characteristic value assignments for batch stocks in liveCache.
After inconsistent stocks have been corrected, it may be necessary to start the delta report in order to reconcile SAP APO and SAP R/3.
Consistency Comparison of Configuration/CDP for Orders
Use
When you set this indicator, the system performs a consistency check with regard to configuration or CDP (characteristic value assignments/ requirements) for receipts/requirements belonging to orders:
· In the case of products with variant configuration and product variants, the system checks whether there is a referenced configuration in the database.
· In the case of products with CDP, the system checks whether CDP characteristics exist.
Note
In the area Restrictions, you can use the indicator CDP: Detailed Check to define a detailed check for CDP characteristics. If you set this indicator, the CDP data used for the orders is also compared with the product master.
· For products without configuration/CDP, the system checks whether invalid references to variant configuration or invalid CDP characteristics data exist.
After the check, you can call a correction function in the check results display. When executing the correction, the system tries to adjust inconsistent orders in liveCache.
After inconsistent orders have been corrected, you may need to start the delta report to compare the SAP R/3 system and SAP APO again.
Dependencies
The consistency check for configuration or CDP data is very time-consuming. You should therefore limit the comparison as far as possible to certain products or locations.
Consistency Check for Production Campaigns
If orders are assigned to production campaigns that do not exist in the database, this leads to inconsistent campaigns.
You can correct inconsistent production campaigns by removing all orders from them. That means that the campaign assignments are removed from the orders in liveCache.
Consistency Check for Operations
In the database table of /SAPAPO/OPR operations, there may exist operations that have no orders in liveCache, no orders for a simulation version, orders for deleted simulation versions, or no external operation number. These operations place an unnecessary load on the database table and can hinder system performance.
Consistency Check for Planning Matrices
As planning matrices are not master data, they are only located in liveCache. For each production version, there is a record in the database with information about matrices that must exist for this production version and whether the last matrix explosion was successful.
The consistency check for planning matrices checks:
· Whether the matrices associated with each record on the database exist in liveCache
· Whether the records associated with all the matrices in liveCache exist on the database
· Whether the last matrix explosion was successful.
If inconsistencies are discovered, they can be corrected. As corrections are made by recalculating the inconsistent matrices, the process can take a while and should only be done for large matrices (with many orders or many item variants) at times when it can be guaranteed not to hinder any other system processes.
Consistency Check for Simulation Versions
This is a check for whether simulation versions exist in liveCache.
Correction does not take place automatically. Simulation versions that still exist in the database but no longer exist in liveCache do not influence the running of the system. If necessary, they can be deleted using transaction /SAPAPO/CDPSS0.
Consistency Check for Product Allocations
The consistency check for product allocations checks the data for product allocation assignment from the database and compares this with the incoming orders quantity in Demand Planning. Surpluses or shortages are displayed and can be corrected.
The reconcile is only executed for product allocation groups with a direct connection to the product allocation group in the planning area if the connection is also fully defined.
There may be long runtimes during the consistency check due to the data structure. The following factors can hinder performance:
· Number of characteristics combinations
· Number of periods in a time series
· Number of sales orders that take product allocations from a time stream
Error in the reconcile
If it is not possible to reconcile the incoming orders quantity, the data records are issued again with a relevant error message. Check the following causes and attempt again.
Check:
· If the planning area to be checked is locked
· If the time streams are initialized (after liveCache has been initialized)
· If all characteristics combinations area available in the planning area
· The wildcard indicator for collective product allocation
· The settings for your planning area
Due Delivery Schedules/Confirmations Consistency Check
When a scheduling agreement release is received from a customer for sales and distribution scheduling agreement items, a due delivery schedule is created and stored in liveCache. As soon as a confirmation for a due delivery schedule containing at least one schedule line with a quantity larger than zero is generated, an object is also created for it in liveCache. The transaction data for sales and distribution scheduling agreement items contains, amongst other things, an entry with the key of the due delivery schedule object currently located in liveCache and an entry with the key of the confirmation that is currently valid in the database. During the check, the system checks whether liveCache objects exist for sales and distribution scheduling agreement items and whether the transaction data entries are correct.
The following individual checks are made for active sales and distribution scheduling agreement items:
· Is there an operative scheduling agreement release and/or forecast/planning delivery schedule in the database, but no associated liveCache object?
· Is there a confirmation in the database, but no associated liveCache object?
· Is there a due delivery schedule in liveCache, without at least one existing operative scheduling agreement release and/or forecast/planning delivery schedule?
· Is there a confirmation in liveCache, without an existing confirmation in the database?
· Is the key in the transaction data in the database that shows the current due delivery schedule in liveCache, also that of the actual liveCache object?
· Is there actually a confirmation in the database for the key in the transaction data that shows the currently valid confirmation in the database?
If a sales and distribution scheduling agreement item is inactive, there are not allowed to be any due delivery schedules or confirmations in liveCache. In this case, the following checks are made:
· Is there a due delivery schedule in liveCache for an inactive sales and distribution scheduling agreement item?
· Is there a confirmation in liveCache for an inactive sales and distribution scheduling agreement item?
Consistency Check for Production Backflushes
Partially confirmed orders cannot be deleted from liveCache. For each partially confirmed order of the database table, there must be a corresponding order in liveCache. If no order exists, there is a data inconsistency that can only be rectified by deleting the order from the database tables of the confirmation.
Entries for orders that have already been confirmed exist in the status matrix. The entry in an order's status matrix is deleted when the confirmed order is deleted by the /SAPAPO/PPC_ORD archiving report. Each status matrix entry for which database tables of the confirmation do not exist, present an inconsistency that can only be removed by deleting the status matrix entry.
Consistency Check for iPPE Objects
The iPPE object is not an iPPE master data structure. It is a data extract that is generated for each iPPE access object.
The consistency check for the object checks that it exists in liveCache and also determines its identity using the backup copy in the database. When correcting the object, the copy from the database is written to liveCache.
It is necessary to check the object if the following error message occurs: 'Error while calling COM routines via application program' (/sapapo/om 102) with return code 1601, 1602, or 1603. This does not apply to liveCache initialization.
Consistency Check for Procurement Scheduling Agreement Items
The following three objects represent procurement scheduling agreement items (scheduling agreement in short):
1. Scheduling agreement schedule lines
2. Release schedule lines
3. Confirmations
All these objects are located in liveCache. Release schedule lines and confirmations are also located in the database with a historical record. Depending on the process that was set up for the scheduling agreement, not all objects exist in liveCache or have historical records.
If goods movements exist for an object, there must always be at least one entry in liveCache. If all schedule lines are covered by goods receipts, at least one schedule line will exist in liveCache with the number '0000000000' and an open quantity of 0.
A liveCache crash, operator errors, and program errors can all cause inconsistencies. Below is a list of all the inconsistent statuses that have been identified and that can be removed:
1. The object is not in liveCache but goods receipts exist.
2. The number of input nodes and output nodes is different.
3. There are no input nodes at the order, but the material exists in the source location for the order.
4. The original quantity at the source of an order is different from that at the destination.
5. The accumulated quantities in liveCache are different from those in the database (the cumulative received quantity, for example).
6. The set process is compared with the status in liveCache.
7. A check is made to see whether the scheduling agreement is being planned in APO or in R/3 and whether the schedule lines have the appropriate specification.
If a schedule line inconsistency is identified, no more checks for inconsistencies are made, instead it moves on to the next schedule line.
Consistency Check for MSP Orders
Provides a list of maintenance and slot orders that
·     Exist in the database but have no corresponding orders in the liveCache
·     Exist in the liveCache, but have no corresponding orders in the database
Procedure
From within the list, you can either
·     Correct the inconsistencies
If you choose to do this, the system deletes the selected orders from the database and/or liveCache.
You receive a message that the selected order(s) have been deleted.
·     Leave the inconsistencies in the database and/or liveCache
Such inconsistencies place an unnecessary load on the database and/or liveCache. Moreover, those orders that exist in the liveCache, but have no corresponding orders in the database, influence the scheduling results of subsequent orders in the liveCache
Hope this helps
Regards
Kumar Ayyagari

Hi, Experts,CONSISTENCY CHECK IN QUERY

Hi experts where is the option for consistency check for aquery
Good response will awarded good marks

Hi
In the header of query designer...check for the option ...to check....when u place the mouse over the icon it wil show check query
This wil check query consistency
Regards
N Ganesh

Member consistency check

BPC 5.1 SP1
Multi server: 1 SQL/1 WEB
I have been processing a dimension for about 5 hours. It typically takes about 3 hours. This dimension is our entity dimension and it has an H3. Specifically, it's been on the consistency check for 4+ hours. I do not want to kill the process and start all over at this point.
What occurs during this process?
What happens after this process besides AS processing?
If the dimension is already built, could I kill the process from Admin, process AS from server and be OK?
Thank you in advance.

Received from SAP Support:
From my understanding, the member consistency check checks to make sure
that the members are in their proper hierarchy and that they are
consistent between Analysis services and the database tables. As long asyou did not make any changes to the dimension, you can process AS from
the server and be OK.
Resolution:
I eventually lost my connection with the Admin interface so I was forced to process cubes from SSMS. Before I did this I checked server to se if any SQL process were running and there was not.
I did have hierarchy changes but was able to sucessfully process cubes. All appears to be well with proper member changes in place.
I'm guessing I lost admin connection long before it froze up...

Repository Consistency Checker for ODI

Similar Messages

Maybe you are looking for