![]() ![]() Close any Sunopsis/ODI GUI such as Designer, Operator, Topology Manager or Security.Stop all your Sunopsis/ODI Agents including the ones launched as Services.Ensure that all Sunopsis/ODI processes (Sunopsis/ODI graphical module or Agent) have been stopped and are not accessing or modifying the Repository content while RCC is analysing the Repository:.The RCC is a Java-based application, and requires a JVM 1.4, 1.5 or 1.6 to be installed on the same machine.Elsewhere, please make sure that your Network and Firewall policies allow the communication between this machine and the server which hosts the ODI (Sunopsis) Repositories to analyse. Ideally, install the RCC on a machine where you are already connecting to the ODI (Sunopsis) environment to be analysed.Depending on the technology hosting the Repositories to be analysed, and prior to running the RCC utility, ensure that the needed appropriate JDBC drivers are present in the “/drivers” directory of the RCC installation.Ensure that the user connected to the Repository database/schema is granted with “create view” privilege.When running the analysis, RCC may need to create several views in the database/schema that hosts the Repository that is analysed:.Contact your DBA to check or expand available storage. Oracle recommends the doubling of the size of this storage prior to launching the RCC utility.Ensure that the database storage for the Repository (data files, log files, tablespaces… – depending on the database schema that hosts the Repository) can grow to store the temporary tables.While running the analysis, RCC creates several temporary tables in the database/schema that hosts the Repository that is analysed:.Ensure that there is sufficient space on disk for the RCC to create the log, and diagnostic data files in the “diag_tools/logs” directory.The user connected to the Operating System must have read and write privileges to the “diag_tools” directory (the RCC installations folder).The Repository Consistency Checker (RCC) utility runs on Windows Operating System only. Regularly for Work Repositories hosted in a Microsoft SQL Server database with multiple concurrent developers.To diagnose Repository data corruptions and inconsistencies.Note if your upgrade requires intermediate steps (such as, for example, an upgrade from Sunopsis v3 to ODI 11g, which requires an intermediate upgrade from Sunopsis v3 to ODI 10g, then from ODI 10g to ODI11g), you should run the RCC prior to the first upgrade operation (in the above example, run the RCC on the Sunopsis v3 Repositories). Prior to upgrading Repositories to a version compatible with ODI 10.1.3.6 or above. ![]() ![]() It is highly recommended to run the RCC utility: Incorrect interactions between design objects.Integration Interfaces which are not in ad-equation with the Topology.Incoherent or inconsistent Internal Identifiers.Detect Repository data issues, such as:.Verify the structure and data integrity of your ODI Repositories in order to guarantee their successful upgrade to ODI 10.1.3.6 or above.The Repository Consistency Checker (RCC) is an Oracle Data Integrator (ODI) utility developed by the ODI Support team to: ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |