[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference iosg::all-in-1_v30

Title:*OLD* ALL-IN-1 (tm) Support Conference
Notice:Closed - See Note 4331.l to move to IOSG::ALL-IN-1
Moderator:IOSG::PYE
Created:Thu Jan 30 1992
Last Modified:Tue Jan 23 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:4343
Total number of notes:18308

3953.0. "Customer's upgrade questions" by UTRTSC::SMEETS (Alpha AXP Compatible LinkWorks Mouse) Wed Mar 09 1994 10:33

Hello,

The Dutch PTT is sheduling the upgrade to ALL-IN-1 V3.0 of all their ALL-IN-1 
V2.4 systems. They already did some test upgrades and have encountered the 
following "problems".

1. After the upgrade the filecabinetserver didn't start because the servertype
   in oafc_server_master.dat was REMOTE instead of LOCAL. This happened on 
   several nodes. For example: 4 node cluster, one node is running ALL-IN-1.
   During the upgrade all nodes are up and running, After the upgrade of the
   ALL-IN-1 node the FCS servertype is REMOTE. FYI SYS$CLUSTER_NODE is not
   defined.
   Workaround: delete en recreate FCS

2. This isn't a problem. During the upgrade customer choose by accident full
   installation instead of upgrade installation. At the end of the installation
   the field CREATE$FAIL in PROFILE.DAT for the Manager's record contained the
   value 3. Normally this field contains the value 0 or 1. Customer would like
   to know what is the meaning of the value 3 in CREATE$FAIL.
   Workaround: restore backup and run upgrade installation

3. The PTT's ALL-IN-1 manager account have more authorize privileges then realy
   are needed. After the upgrade they noticed that the number of privileges in
   Authorize for the ALL-IN-1 account were changed; decreased ! Is this the 
   normal behaviour ? If so, why ?
   

Thank you for your input !

Martin
T.RTitleUserPersonal
Name
DateLines
3953.1Anybody knows something ?UTRTSC::SMEETSAlpha AXP Compatible LinkWorks MouseThu Mar 10 1994 11:3712
> After the upgrade the filecabinetserver didn't start because the servertype
> in oafc_server_master.dat was REMOTE instead of LOCAL. This happened on 
> several nodes. For example: 4 node cluster, one node is running ALL-IN-1.
> During the upgrade all nodes are up and running, After the upgrade of the
> ALL-IN-1 node the FCS servertype is REMOTE. FYI SYS$CLUSTER_NODE is not
> defined

Does anybody know which action during the upgrade could cause such result ?

Thanks,

Martin
3953.2I know nothing but,..AIMTEC::WICKS_AAtlanta's Most (In)famous WelshmanThu Mar 10 1994 15:4410
    martin,
    
    well strictly speaking running ALL-IN-1 on just part of a cluster
    isn't 'officially' supported - having said that loads of people do it.
    What are the SCS thingies defined to and where does OA$PRIMARY_NODE
    point.
    
    regards,
    
    Andrew.D.wicks
3953.3Q2 answered by meUTRTSC::SMEETSAlpha AXP Compatible LinkWorks MouseFri Mar 11 1994 08:168
I'm going to answer Q 2 by myself.

During editing of an user(profile) with PRVAPP privileges the CREATE$FAIL
field will contain the value 3. This value prevents the user to enter CM. If the
user tries to enter CM the message "Your profile is being edited, See your 
System Manager" will appear.

Martin
3953.4Local is hard-codedUTRTSC::SMEETSAlpha AXP Compatible LinkWorks MouseFri Mar 11 1994 09:2534
Helle Andrew,

RE.2 

>    well strictly speaking running ALL-IN-1 on just part of a cluster
>    isn't 'officially' supported - having said that loads of people do it.
>    What are the SCS thingies defined to and where does OA$PRIMARY_NODE
>    point.

I've investigated this problem a bit futher. During the automatic post-
installation the script oa$lib:oafc$server_create_73.scp is executed. This
script adds a server record to oa$data:oafc_server_master.dat.

.label add_server_record

        write add oafc_server_master -
                        server_name_1 = #oafc_server_name, -
                        server_node = #oafc_server_node, -
                        server_object_number = #oafc_server_object_number, -
                        server_process_name = #oafc_server_node -
                                        "$SRV" #oafc_server_object_number, -
                        server_type = "LOCAL", -
                        server_startup_state = "ENABLED", -
                        server_start_queue = #oafc_server_start_queue, -
                        server_config_file =  "OA$DATA_SHARE:" -
                                        #oafc_server_node "$SERVER" -
                                        #oafc_server_object_number ".DAT"

As you can see the server_type (LOCAL) is hardcoded in the script. So I wonder 
how the servertype could be changed to REMOTE.

Regards,

Martin
3953.5Confirm y/n ?UTRTSC::SMEETSAlpha AXP Compatible LinkWorks MouseMon Mar 14 1994 12:4613
Hi,


> The PTT's ALL-IN-1 manager account have more authorize privileges then realy
> are needed. After the upgrade they noticed that the number of privileges in
> Authorize for the ALL-IN-1 account were changed; decreased ! Is this the 
> normal behaviour ? If so, why ?
   
Can someone please confirm that an upgrade installation will remove privileges,
which are not needed e.g. could cause problems, from the ALL-IN-1's authorize 
entry ?

Martin 
3953.6ConfirmedODIXIE::WOLFEJohn Wolfe - (404)-924-6463Mon Mar 14 1994 16:556
	FWIW, I have been complaining about .5 for ages.  I am told it will be 
fixed in a PFR.  I believe that in order to be sure we have the required 
privileges and quotas (and some are new or increased) the installation will 
rewrite the UAF record.

John
3953.7Changing MANAGER's UAF entry during upgradeIOSG::HALLCDenser than a Black Hole SingularityWed Mar 16 1994 14:365
Hi John,

Yes this is still on my fix list for the PFR!  

Chris.