Operating System - OpenVMS
cancel
Showing results for 
Search instead for 
Did you mean: 

user database

 
umesh_singapore
Occasional Contributor

user database

Can we copy user database ( SYSUAF.DAT, RIGHTSLIST.DAT,NET$PROXY.DAT ) files from OVMS 7.3-2 to v8.3 system,

If yes ? then only these DAT files enough to move database or else .
9 REPLIES 9
Heinz W Genhart
Honored Contributor

Re: user database

Hi Umesh_Singapore

First of all welcome to the ITRC OpenVMS Forum

Yes, you can copy those files. I would recommend to copy also NETPROXY.DAT (old Format Proxy Database). If You copy SYSUAF.DAT, RIGHTSLIST.DAT, NET$PROXY.DAT and NETPROXY.DAT you have moved the user Database.

Regards

Geni
Jan van den Ende
Honored Contributor

Re: user database

umesh_singapore,

Welcome from me too!

In addition to what Geni wrote, if you are using TCPIP, then also copy TCPIP$PROCY.DAT

Success.

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
Wim Van den Wyngaert
Honored Contributor

Re: user database

Jan van den Ende
Honored Contributor

Re: user database

Oops.

TCPIP$PROCY.DAT should have been TCPIP$PROXY.DAT

Proost.

Have one on me.

jpe
Don't rust yours pelled jacker to fine doll missed aches.
Robert Gezelter
Honored Contributor

Re: user database

umesh_singapore,

You can move your users by copying the SYSUAF, RIGHTSLIST, and various proxy files, as has been mentioned by other posters.

There are two cautionary notes:

- (as has been mentioned) check whether the quotas need to be increased, and either change them in the authorization files or increase the system-wide minimums

- please ensure that the various UICs created for layered products are the same in the 8.3 system and the 7.3-2 system that the files are being copied from.

Subject to those two cautions, this is an operation that I have done many times.

- Bob Gezelter, http://www.rlgsc.com
Hoff
Honored Contributor

Re: user database

With specific investigation of your old and your new configuration, and with some likely changes needed, yes, you can do this.

Why do I mention the need for work? There are binary values that can be or are written all over the disks, files, queues, devices, etc., that originate in these files, so you can end up having unintended access blocks, unexpected permits, and unexpected ownership.

If you're just looking to move users over (merge), I'd tend to move over the specific attributes over (username, salt, hashed password, directory, etc) with a duplicate check. (A MERGE/STABLE/NODUPL command can potentially be used here.)

But you need to be aware of the binary values of the identifiers (resource, subsystem, UIC, etc), and where these are used on your old and your new environment.

You'll need to weed out the usual collisions, as the old and newly-minted environments tend not to have the same UIC values for the common server accounts, for instance. Which means you need to pick one of the two UIC values (the one from the new environment tends to be the best choice here) and use that one. TCP/IP Services and DECnet, for instance, can have server accounts, as can many layered products.

It's not quite as transparent or as simple as it should be, if you're looking to deal with all of the pieces related to security.

Here's some related reading material:

http://64.223.189.234/node/169
Hein van den Heuvel
Honored Contributor

Re: user database

Just some additional hints...

Typically those files are in use on a system, so a simple COPY command might not do.

You could use BACKUP/IGNORE=INTERLOCK, but runa minor risk of picking up a bad file.

The best way to copy those actively used indexed files is :
$CONVERT/SHARE x.dat x.copy

You MAY want to convert to a sequential file:
$CONVERT/SHARE/FDL=NL: x.dat x.seq

And on the receiving side, instead of replacing the target file you can ADD the missing records, leaving the 'system' records and original file in place:
$CONVERT/STAT/MERGE/SHARE/EXCEP=x.dups x.seq x.dat

- That MERGE is optional... a new file is preferred.

- That input does not have to be sequential, it can be indexed.

- Many more postings exist on this topic in the official doc as well as ITRC and c.o.v and Hoff's site. Google is your friend.

Hein.
John Gillings
Honored Contributor

Re: user database

There are many other files to consider! just a few extras which might be relevant:

VMSMAIL_PROFILE.DATA
VMS$PASSWORD_HISTORY.DATA
VMS$PASSWORD_DICTIONARY.DATA
SYSALF.DAT
VMS$OBJECTS.DAT

See SYLOGICALS.TEMPLATE and cross reference with the cluster manuals.

This is an area where OpenVMS really is very ugly and clumsy. It's very difficult to work out exactly what files you need to define your environment. I really wish OpenVMS engineering would get its act together and give us decent tools for managing system data bases (creation, maintenance, backup, restore, move, transfer to another system etc...). It's especially important for multi system disk clusters.
A crucible of informative mistakes
Neelmani Pandey
Frequent Advisor

Re: user database

Hi Umesh ,

First of all message me your no on my email,

Neel this side i think u might hav got me.

Waise sab chalegi u can copy.

He he ..