I get the next error when I am trying to checkin/checkout in clearcase:
cleartool: Error: To operate on UCM branch, must be set to an activity and a UCM view.
Well as I can see here this happens because there is no activity attached to the view I used. My question is how I can create an engineering activity and associate it with an existing view using Rational Clearcase Explorer.
I need it in order to have an ability to checkin/checkout files using clearcase console.
Simply do a cleartool mkact:
cd /pat/to/your/UCM/view
cleartool mkact aNewAct
That will create and set a new activity to your current view.
Any checkout/checkin after that will use that curent activity.
For Clearquest-enabled projects, see "About creating UCM activities in a project enabled for Rational ClearQuest":
You do not create UCM activity objects directly.
In a project that is enabled for Rational® ClearQuest®, an activity usually refers to two objects that are linked together:
a UCM activity object and
a record in a Rational ClearQuest user database whose record type is enabled for UCM.
The process of creating an activity in a project that is enabled for Rational ClearQuest entails the creation of two objects in a specific order:
You create records (based on a record type that is enabled for UCM) in a Rational ClearQuest user database.
On Windows®, you can create records from the Rational ClearQuest client or, if policy permits, from Rational ClearCase® windows (Check Out, Check In, or Add to Source Control).
On UNIX®, you can create records only from the Rational ClearQuest client.
When you set an activity in a view (which you can do by clicking Actions > WorkOn for a Rational ClearQuest user database record), the following occurs:
An activity object is created in the stream to which the view is attached.
The activity object is linked to the record in the Rational ClearQuest user database whose record type is enabled for UCM.
The name of the Rational ClearCase activity is set to match the Rational ClearQuest record's ID.
Related
I'm using Redgate Source Control to changetrack a database. I have a testing database from which I commit, and a production database which is the final target.
I want to have a different Database Role (the setting found of Database->Security->Roles->Database Roles) in the production database because of specific requirements. I have changed one database on my production server, but every time I deploy to the production database, the Database Role resets to the status it was before I changed it (even though the specific role is not synced).
I found a filter on Comparison Options for user roles and checked the Ignore: "User's permissions and role memberships" and deployed the filter, but the Database role still resets every time I deploy any change to production.
Is there a way to ignore Database roles or is there a workaround I could use?
EDIT:
Larnu's answer is correct.
I had a separate issue here which had to do with the role permissions not being defined in the role, but in the schema.sql file. So I had to commit the whole schema to get the role permissions committed.
In SQL Source Control, there is an option for ignoring roles entirely (or using a rule to ignore certain ones).
Select your source controlled database in the Object Explorer, and then click SQL Source Control in your toolbar. Go to the Setup Page, and then select "Edit filter rules".
Then simply untick Role and the Roles won't be source controlled any more, or you can add rules to exclude/include roles that meet said rule(s). Note you may need to remove the Role details from your Source Control repository as well, as otherwise the position of the role when you stopped Source Controlling it may be used (I suggest checking).
I built an Access DB and placed it in a shared folder where users are to copy and paste directly to their desktops. There are some that are accessing the database directly from the folder; hence locking the database up for any updates to be made.
There are no log in or user credentials used when accessing the database so I can't place any kind of audit trail on it to determine the users that continue to open the database directly from the folder.
Is it possible to close the database; knocking out these individuals that continue to lock it up? Or is it possible to place some sort of an audit trail in the database to capture user data that would identify the individual; i.e. computer address, computer name, etc.
You should leave that setup and arrange for each user to always have their own copy of the frontend - having tables linked from one backend, if they need that.
A script and a shortcut is used for that. It is described in detail in my article:
Deploy and update a Microsoft Access application with one click
(if you don't have an account, browse for the link: Read the full article)
I just installed my Oracle 12c, connected it to database successfully.
I could not create a user (in CDB).
So, i tried to create user name through PDB. But even PDB is not working.
I am new to Oracle.
After DB was connected successfully, We cans see message like,
Connected to: Oracle Database 12c Enterprise Edition Release 12.2.0.1.0 - 64 bit production. But after this i could see some more matter regarding production of OLAP, Data Mining etc......in some of the youtube videos. i could not get it.
With Oracle 12c, when you connect to the root container (as you did above), you are not able to create "typical" users. In the root container, you're only able to create "common" users (based off of a default installation and no parameter changes, users that start with C## - e.g. c##joe). Common users are available in every PDB that you have and create at some later point.
On the other hand, if you switch to a PDB, you can then create your "typical" users.
SQL> show pdbs
Switch to one of them:
SQL> alter session set container=XXXX;
Create your "typical" user should work now:
SQL> create user scott identified by tiger ...
A user created in a PDB is only available to log into the specific PDB it was created in (unlike a common user which can log into all pdbs).
-Jim
I am planning to setup Clearcase for version control in our project, but I am new to Clearcase and has few very basic questions about it.
Some background: we are using Windows platform
Is it possible to install Clearcase server (the VOBS server) in Windows XP?
How do Clearcase authenticate user? Can I logon to my Clearcase client with local account instead of domains account?
Yes, you can. See this "System Requirement" page for ClearCase 7.1.x: Windows Xp (SP2 and SP3) is still supported.
ClearCase will use the login of your current session as credential, and whatever group you will have declared in the CLEARCASE_PRIMARY_GROUP environment variable:
See the "about CLEARCASE_PRIMARY_GROUP variable" technote (if not set, your group will default to "Domain Users").
See this technote for more about permission for a Windows environment with ClearCase object: the creds.exe utility is useful to check one's credential as detected and used by ClearCase.
Possible if you expect users to log on locally...if your going for an enterprise setup,
you should explore the server & domain setup such that you can take advantage of ClearCase's
distributed architecture and all the benefits...having said that :)
Yes its possible (maybe you want to test/experiment/toy with it..)
you will need to create:
clearcase_albd account (clearcase system account)
A ClearCase local group (clearcase_albd as member)
A clearusr local group (normal user group)
During install you will be asked for these values...
Note post install ClearCase doctor will nag you with the fact that its not on a domain...can ignore
But it will work.
Good luck
Jim2
Our ClearCase structure, as it exists now, has several PVOBs. But they do not share a ADMIN VOB. Is there a way to make one of them an Admin VOB, so that all the PVOBs can share components?
Any help is appreciated.
It is better to:
create a new admin pvob
link the other pvobs to that new admin pvob (a special hyperlink)
See this help page.
Any VOB can be linked to an administrative VOB from which it derives definitions of type objects such as branch types and label types. Type objects are a fundamental part of the Rational ClearCase data model.
It is useful to establish an administrative VOB hierarchy into which new VOBs can be placed in order to simplify type administration. For more information about administrative VOBs and global types, see VOB datatypes and administrative VOB hierarchies.
Note:
A PVOB is the administrative VOB for all UCM component VOBs that are included in projects defined in that PVOB.
Every UCM component VOB is created with an AdminVOB hyperlink to its PVOB.
If a project uses multiple PVOBs, they must each have an AdminVOB hyperlink to a common PVOB in which shared components and streams are defined.
With the VOB Creation Wizard, you can specify the administrative VOB for each new VOB that you create. If you create a VOB with mkvob, you must specify the VOB's administrative VOB in a subsequent mkhlink command that creates an AdminVOB hyperlink from the VOB to its administrative VOB.
cleartool mkhlink -c "link to admin VOB" AdminVOB vob:\dev vob:\admin_dev
Created hyperlink "AdminVOB#40#\dev".
Now, the one trick to never forget:
Once you have created your new admin pvob, do not forget to "declare" it (mktag) in the region of your VOB server (usually superregion), as well as your local region for your user.
If the vob server does not "see" that pvob tag, no UCM operations will succeed!