I'm doing vob migration from Solaris to RHEL, out of 24 vobs 23 vobs migrated successfully except one pvob which is giving following error.
db_dumper.54: Error: Unexpected error from database library (8) in "../db__dump.c" line 2835
db_dumper.54: Error: Error from libdb (8)
cleartool: Error: Could not dump database.
cleartool: Error: Trouble dumping versioned object base "/vobstg/pvob.vbs".
dbcheck status,
Processing delete chain: 0 records on delete chain.
Processing records:
100%
Database consistency check completed
0 errors were encountered in 0 records/nodes
Check for HyperSlink and got following error cleartool checkvob -hlinks -hltype hltype:HyperSlink vob:/vob/pvob
cleartool: Error: Hyperlink type not found: "HyperSlink".
Stuck in the migration
It can help knowing at what stage the dp_dumb was before exiting in error, like in this thread.
But the usual course of action is to compressed a locked pvob content, and send it to IBM for analysis.
The HyperSlinks aren't an issue here (as they would when making a replica).
As mention in this IBM support thread:
IBM support resolved this, one of the activity had spacial character which caused this. Now reformat vob works.
Yet to start the sync with master site.
Issue is with special character in activity, IBM gave me tool to fix it. Now things are normal.
Related
I am getting an error while checking out the file.
Error is: lock on VOB database "\EPAS prevents all write operations.
I tried to unlock the VOB but no luck.
Cleartool: Error: Object is not locked.
Cleartool: Error: Unable to unlock versioned object base "\EPAS_NF".
I even try to run the Protect VOB. still, the VOB is not working.
Please let me know how to unlock the VOB.
It can depend on your:
ClearCase version (an old one would have dbcheck for instance)
(a ClearCase 8 had issue on Vobs idle for too long)
ClearCase usage (a multiSite one can exhibit VOB communication issue)
(a multiSite migrated Vob can have lock issue)
Looking at the Windows Event viewer can help pinpoint the issue (a network communication of some sorts)
I have a vague recollection of seeing something like this come across as a tech support case. Ah, there it is... There were a number of other errors in your VOB server logs as I recall, including the \EPAS_NF or \EPAS VOB not being registered.
I am guessing that \EPAS_NF is an admin VOB to \EPAS, or vice versa. If you are checking out on a VOB where a given global brtype has never been instantiated, and the Admin VOB is locked, you will get an error stating that the admin VOB is locked.
This being said, I would make sure that the VOBs in question are currently fully and correctly registered and tagged, and that both databases are at least basically intact using dbcheck.
If you are getting an error message stating that the VOB is not consistently locked, it stands to reason that there is at least SOME database corruption, that should appear in a dbcheck or in a reformatvob.
The support case does not mention a timeline for the issue. And that may be key to knowing how you got into this mess... And in the case of corrupt databases, having some idea as to the cause would assist in knowing how practical database recovery will be.
Having trouble with an issue I am unable to reproduce in solrcloud. Seems to happen at random.
Underlying file changed by an external force at 2018-09-18T14:55:22Z, (lock=NativeFSLock(path=/path/to/my/shard/index/write.lock,impl=sun.nio.ch.FileLockImpl[0:9223372036854775807 exclusive valid],creationTime=2018-09-18T14:55:22.006973Z)) Caused by: org.apache.lucene.store.AlreadyClosedException: Underlying file changed by an external force at 2018-09-18T14:55:21Z,
the index is schemaless and typically receives many simultaneous updates.
It usually starts with something like this: (in this order before the write.lock error occurs)
Error from server at server3/solr/myshard: Bad Request
Remote error message: Exception writing document id bc04df6e-f29f-4091-ad73-f708a97d28b4 to the index; possible analysis error.
3 Async exceptions during distributed update:
Remote error message: this IndexWriter is closed
Is there anyway to self recover from the indexwriter being closed? After the error occurs, no more documents can be written to the collection. The only solution I have right now is to either delete the write.lock and restart solr or recreate the collection completely.
I am getting below error while updating the view.
Problems were encountered while retrieving view synchronization and data.
Clearcase CM server error: Unable to access "vob name" : unknown error in vob
Clearcase CM server error: Error 2 config spec load rule problems encountered
How to troubleshoot that error message?
You need to access the logs (both locally or on the server) to know more.
It used to be cleartool getlog (ClearCase 7.x, even for CC 8.x)
cleartool: Error: Checkout is currently disabled for element "element_name".
Its config spec rule information is currently unavailable due to either an aborted update or an update in progress
That is similar to an older CC (7.0.x) described in this technote:
Possible cause for symptom 1:
If an update, rebase or deliver operation is not currently in progress for the view in question, the error can often be attributed to the view being out of sync with the stream.
Try:
cd /path/to/snapshot/view
cleartool setcs -stream
Possible cause for symptom 2:
Hijacked nocheckout means that the version hijacked in the view is no longer the version the config spec selects from the VOB.
Rename the hijacked file and update the view.
Check out the version from which the file was hijacked.
Copy the hijacked file over the checked-out version.
Merge from the current version to the checked-out version.
The version can now be checked in.
Possible cause for symptom 3:
Per the error message explanation noted above, the problem may be caused by an issue with the view's config spec or an aborted or incomplete view update.
Try:
cd /path/to/snapshot/view
cleartool setcs -current
(original answer)
It can be a right issue, as illustrated by this thread.
Check group permissions on user and on those two VOBs.
Do you rely on the CLEARCASE_PRIMARY_GROUP environment variable?
If so, check the value of the user performing the update.
Compare the rights of the vob with the ones for your current snapshot view that you are trying to update:
cd /path/to/snapshot/view
cleartool lsview -l -full -pro -cview
If the CLEARCASE_PRIMARY_GROUP is not set properly, it is easier to:
set it to the right group (ie the primary group of the vob, or one of the secondary groups)
delete and recreate your view.
(if you do not want to delete/recreate your view, you can fix_prot it)
I am getting following error post delivery:
We have 2 clearcase servers remote and local once code is delivered to remote SDS for the effect to take place in localclear case we manually execute ct deliver -complete but I am getting below errors .
Errors
user#s007246a ~]$ tailf xxx_sds.deliver.log
activity:deliver.1111111111111111111111111111111111111111111111111111111111111111111"
activity:deliver.2222222222222222222222222222222222222222222222222222222222222222222"
activity:deliver.3333333333333333333333333333333333333333333333333333333333333333333"
activity:deliver.4444444444444444444444444444444444444444444444444444444444444444444"
cleartool: **Error: Unable to read change set entry for activity** "33333333333333333333333".
**cleartool: Error: Unable to convert diffs to elements.
cleartool: Error: Unexpected error in deliver.
cleartool: Error: Unable to perform merge.
cleartool: Error: Unable to do integration.
cleartool: Error: Unable to deliver stream "xxxxxxxxxxxxxxxxxxxxx".**
Error 2.
ct: Warning: A version in the change set of activity "deliver.xxxxxxxxxxxxxxxxxxxx" is currently unavailable.
Query:
can we deliver a particular deliver.xxxxxxx activity from designer stream to integration stream if yes how ??
If above query is achievable can we also deliver some activities say deliver.1111111 deliver.222222222 deliver.33333333 out of deliver.nnnnnnnnn activities from SDS to Integration stream.
Independently of your queries, you must solve first the error message you get on the complete step of your deliver.
See "Unable to deliver stream is returned when completing a UCM Posted deliver"
Cause
The Project VOB may be in sync but the Component VOB(s) at the source and target sites may not be in sync.
The target stream is locked. This can be checked by looking at the properties of the target stream.
When I try to 'rebase' my stream in clear case, I get the 2 options : 'Resume rebase' and 'Undo rebase'.
But both of them give me errors. It seems a previous rebase failed and left the stream in a corrupted state.
How to solve this?
I tried stopping and starting ClearCase but no luck.
EDIT: the error is :
IDispatch error #14083
Execution of a hook failed during the action Complete. It was the ACTION_COMMIT hook attached to the UCMUtilityActivity "CR00155721".
The reason for the failure was:
Trouble communicating with VOB database: "\Alerts_Proj".
Check database log on VOB host "123yyyyy.com".
Could not perform requested operation: a UCM/ClearQuest data
inconsistency may exist:
ClearQuest "UCMUtilityActivity" record "CR00155721" is linked to a UCM object
that can not be found.
Unable to complete the rebase activity in ClearQuest.
Unable to undo set of integration activity.
Unable to complete integration.
FYI I've also seen this happen when the "CQIntSvr11.exe" fails. It seems to occur when you need to use the application on the same machine with different users (e.g. admin and developer account).
If you kill the process using task manager and then retry the operation the IDispatch 14083 should stop and then you can use your stream again.
One solution might be deactivating the trigger, but this could be put by the ClearCase-ClearQuest link and not be possible without severing completely that link.
So you can start by checking out this IBM technote with your ClearCase administrator:
This error occurs because the UCM project VOB and associated activities have been removed, ClearQuest is still looking for this information and needs this information to remove the defect.
This issue is the result the ClearCase items being removed before the ClearQuest defects and project.
Solution
To resolve this issue perform the following to fix the Activity so it can be deleted:
Browse to the ClearCase utils directory:
c:\program files\rational\clearcase\etc\utils
Run the following command from a command prompt:
Note: This command cannot be performed in the GUI
squid_patch <DBNAME> -activity ucm_vob_object ""
Note: It will display an advisory message, but it will change the field in ClearQuest.
Delete the ClearQuest record.
Remove the UCM project with the following command:
squid_patch <DBNAME> -project ucm_vob_object ""