Repository Diagnostic Tool on a cluster system
I ran RDT (only scan) on a development environment and works fine. When I checked some inconsistences, they are real. After this, stop CMS and FRS and run RDT with -repair parameter. It ran succesfull.
Now, I'm running RDT (only scan) on a production environment with cluster and the inconsistences are not real. i.e. Webi object 'XXXX' (Object ID = 12345) is referencing files that do not exist in the FRS (roiw3vfrd9v45f50e3.wid). When I search this file in CMC, the file exists and has a path. When I find on Infoview, I can open the file, no show me any error.
I used the sentence: /business/bobje/boe_reposcan.sh -dbdriver oracledatabasesubsystem -connect "UID=BDuser;PWD=PwdUser;DSN=DSN;PORT=6400" -inputfrsdir /business/bobje/data/frsinput -outputfrsdir /business/bobje/data/frsoutput -outputdir /business/bobje/enterprise120/reposcan
There are some parameters when RDT run on a live system with a clustered CMS database: requestport, numericip, ipv6, port, threads.
Are they necessary to run RDT in this case?
In which case they are needed?
I'm running RDT on BO XI 3.1
Pd. English is not my native language. Sorry for the gramatical errors