Following is the error while using ClearCase version 7.1.2.6 on windows site. Any suggestions how to fix it.
cleartool ls
cleartool: Warning: Can not update license cache
"C:\Program Files (x86)\IBM\RationalSDLC\ClearCase\var\cache\ClearCase_check\desker".
Please check ownership or permission.
What could cause this error message?
This is similar to PM09741:
Problem summary
ClearCase licensing does not handle account user-ID changes without user name changes.
That means something has changed (like the license server name)
Related
Working in Red Hat Linux trying to build RPMs that are accessed via Clearcase vobs but keep on getting a recurring error which states, 'unable to find albd-server on host ', 'Unable to contact view - clearcase object not found' and 'Unknown host - Name or service not know'. Any guidance would be much appreciated.
I solved the issue in the end by using clearmake -V in the makeall script. Because I'm working with shareable DOs this enabled me to avoid winking in between views. Thankfully it built successfully this time but instead of it being in the build error log it appeared as a test failure. Thanks for the help.
Check first the vobrpc_server_log on the ClearCase Vob Server.
As seen in this technote (for an older version of ClearCase, but still relevant)
Attempts to mount a VOB results in the following error:
ClearCase Object Not Found
This error may get reported in the VOBRPC error log:
01/06/2006 09:24:34 vobrpc_server(5016): Error: vobrpc_server.exe(5016):
Error: Unable to get VOB tag registry information for replica uuid
"db7983f9.052d498a.915f.bb:f9:0e:b0:b4:ea":
ClearCase object not found
This error may get reported in the vob_scrubber log:
vob_scrubber: Error: Unable to get VOB tag registry information
for replica uuid "db7983f9.052d498a.915f.bb:f9:0e:b0:b4:ea":
ClearCase object not found
This error will occur when trying to mount the VOB before the VOB tag creation is complete.
This would be due to a timing issue where the cleartool mkvob and cleartool mount operations are done via a script, and maybe a longer pause is required before the VOB is mounted on a remote host.
This would also be true in an environment where the VOB creation takes several moments to complete, and there is an extended period before the VOB tag is available for users to mount.
Note: This does not occur as a result of the cleartool mount that is executed automatically during the cleartool mkvob operation.
Cause 2: The VOB tag may still exist even though the VOB storage (or VOB server host) are no longer available in the ClearCase network.
This will happen as a result of improper removal of the VOB storage.
Cause 3: The server storage location (network share or export) is not available.
When mounting a VOB, the location that the VOB is stored must be accessible from the host that you are trying to mount the VOB.
Cause 4: If the VOB is not yet tagged in the primary region of the VOB server.
This is applicable to environments that have multiple registry regions.
Is this a clearmake build? Does it complete? (Winkin and shopping failures USUALLY don't cause a build failure.) What is printing those errors? Clearmake? Another ClearCase tool?
What is the exact version of ClearCase? If 9.0.1.x, the patch level and your license type may matter, as some older 9.0.1.x releases had an issue where you would get "extra" errors if you had albd contact failures and you use Rational Common Licensing.
This is a follow on from op - Moving Vobs between Win and AIX
Due to the aix and win vob servers sharing resources (common CC reg & Common Admin PVOB on the Aix box) we need to amalgamate these vob servers onto the AIX server as a precursor to our ultimate move to new servers at CC8.
on the Win VOb Server we have locked the vob, run vob_siddump then a reformat dump of the vob.
Then using xcopy we copied the dumped vob.vbs from Windows to AIX vob server run the fix_prot on the new server.
But when we run the reformatvob -load it goes through it's steps Shows "Loader Done" then shows the following errors
Error from vob database /vobstore/vobs/vobname.vbs.
Error Trouble Opening the VOB Database /vobstore/vobs/vobname.vbs,
Error Trouble Loading versioned object base /vobstore/vobs/vobname.vbs.
Because of the shared registry is this due to the existing registry entry and we need to unregister and then rmtag before registering and tagging fresh or do we need to do anything further?
Clearcase logs on aix vob server show:
DB Log - Error process not running on registery specified hostname (old win vob server)
Vob Log - shows unix UID and GID messange and Warning unable to verify mount options in vob tag registry Clearcase Object not found
David, there are a few things you need to do here:
unregister the VOB and remove all the tags that refer to the old server
reregister and retag the vobs at the new location.
If you can't register the VOB, run fix_prot -r -root ... to reset the ownership and try again.
run vob_sidwalk to remap object ownership.
run it again with -recover_filesystem to reset container ownership. Alternatively run checkvob -pool -protections -fix -force {vob storage dir}.
The last step really needed to be started on the Windows side before this started. Essentially, you needed a sid dump file to turn into the map file that the sidwalk needs (unless you want to remap everything to the VOB owner...)
The complete procedure to follow is at Moving VOBs between Operating system types You may want to start fresh from there if you still have the VOB located in the old location.
I had an issue where the servers D: drive is corrupted completely and D: drive was hosed CearCase application. And we have restored D: drive from backup.
Now the problem is, from local admin account, I am able to launch ccadminconsole.msc without any issue, but from domain user login I am getting below error.
Does anyone know the cause and fix for this ?
The only error I could see from Application log is this:
Log Name: Application
Source: ClearCase
Date: 4/11/2017 11:06:06 AM
Event ID: 1024
Task Category: VOBRPC
Level: Error
Keywords: Classic
User: OIM\cc_albd_sj_agile
Computer: S09CGP.us.oim.com
Description:
vobrpc_server.exe(4980): Error: Trouble opening VOB database: "\Xpedia".
As I mentioned in 2014:
The main documentation for Vob access error is "Error from VOB database and Trouble opening VOB database".
To gather the most information about the issue, it is best to check the logs of the view logs (not just the vobrpc logs). Also check the logs both on the client and the server.
So check both with the cleartool getlog command, both for your own computer, and for the ClearCase VOB server.
Check also the db log, for any db_VISTA database error you could find there. And the mvfs log, just in case.
Typically, especially after a backup restore, the main cause of this problem may be related to the permissions on the VOB storage directory, in which case a cleartool fix_prot (as I do here) is the first thing to try.
Make sure first your local account is part of the right CLEARCASE_PRIMARY_GROUP, which should match the main group for the Vob.
I been working on installing Oracle 12c database on my windows machine. I downloaded the Microsoft Windows x64 (64-bit 2.8GB) file here.
Then I extracted the zip file into a folder in my Desktop and run the setup.exe
But I keep on getting this error and am unable to move forth.
[INS-30131] Initial setup required for the execution of installer validations failed._______________________________________________________________Cause - Failed to access the temporary location. Action - Ensure that the current user has required permissions to access the temporary location. Additional Information:
- PRVG-1901 : failed to setup CVU remote execution framework directory "C:\Users\Taro\AppData\Local\Temp\CVU_12.2.0.1.0_Taro\" on nodes "nayantara-jeyaraj" - Cause: An operation requiring remote execution could not complete because
the attempt to set up the Cluster Verification Utility remote
execution framework failed on the indicated nodes at the
indicated directory location because the CVU remote execution
framework version did not match the CVU java verification
framework version. The accompanying message provides detailed
failure information. - Action: Ensure that the directory indicated exists or can be created and
the user executing the checks has sufficient permission to
overwrite the contents of this directory. Also review the
accompanying error messages and respond to them. Summary of the failed nodes nayantara-jeyaraj - Version of exectask could not be retrieved from node "nayantara-jeyaraj" - Cause: Cause Of Problem Not Available - Action: User Action Not Available - Version of exectask could not be retrieved from node "nayantara-jeyaraj" - Cause: Cause Of Problem Not Available - Action: User Action Not Available
According to the error, I checked the C:\Users\Taro\AppData\Local\Temp folder permissions under its properties panel's security tab. All the users have full access permissions.
This helped me:
setup.exe -ignorePrereq -J"-Doracle.install.db.validate.supportedOSCheck=false"
I also
run the console as administrator
checked whether a REG DWORD named AutoShareWks (in registry Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters) exists. It did not. But if it would, make sure that the value is set to “1” and restart.
Stopped the OracleRemExecServiceV2 service
When I try to check-in an RFT script, I get this error. Undo-checkout and check-out again did not help.
When I try to check-in the rftdef file (a script dependency file) using ClearCase Explorer, I get the same error.
Any ideas?
The problem was that our computer is Win7 Enterprise, but ClearCase v7.0. Uninstalled it, installed CC v7.1.2 and the problems have disappeared.
If the type manager "_rftdef" is an issue, you can try an change it to a simple text file, in order for that same type manager to not be triggered.
cleartool chtype -force text_file FinansBanka.rftdef
That is a workaround solution, which doesn't address while the type manager fails in the first place.
For that, I would recommend to try with a shorter, simpler version of FinansBanka.rftdef, to see if its content got corrupted somehow.
As the Cagin Uludamar reports, a discrepancy between:
the version of the ClearCase client
the version of the ClearCase server
can be the cause of a type manager not functioning properly.
See "About the Rational ClearCase Type Manager":
For operations that create/delete/modify source containers (cleartool/GUI/multitool-import mkelem,mkbranch,checkin,checkout-w/auto-mkbranch,rmver,rmbranch,rmelem), the type manager runs as a child process of cleartool/GUI/multitool-import.
Once that source container (run by an older client) is managed by the view server (on a more recent server), trouble can ensue.
Trigger definitions and magic files are two resources that must be deployed coherently both on the ClearCase server and clients.