Resolving Upgrade Issue for SCC

SCC stops working after you upgrade from SUP 2.2 SP04 or later to SMP 2.3. You need to run a SQL script at the SCC node to fix the issue documented in SMPONP-3241.

1. Save this SQL script to a file on your local file system (for example, C:\temp\fix_SCC.sql):

   begin 
   
   UPDATE SEC_CONFIG SET SCFG_VALUE='true' WHERE SCFG_KEY='RESKEY_SECOPT_AUTO_CREATE_LOGIN';
   UPDATE SEC_CONFIG SET SCFG_VALUE='true' WHERE SCFG_KEY='RESKEY_SECOPT_AUTO_GRANT_USER_ROLE';
   commit;
   end;
   
   begin
   declare curs2 cursor for 
   select rtv.rtv_id from "DBA"."RES_RESOURCE_TYPE_VER_M" rtv, "DBA"."RES_RESOURCE_TYPE_M" rt 
   where 
    rtv.rtv_rt_id=rt.rt_id and rtv.RTV_SHORT_VER_STR!='Unknown' 
     and (rt.rt_class='com.sybase.uep.admin.agent.plugin'
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.ClusterMO' 
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.ServerMO'
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.DomainMO'
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.PackageMO'
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.PersonalizationMO'
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.SubscriptionMO'
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.UserMO'
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.SecurityMO'
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.ConnectionMO'
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.MessageMO'
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.DeviceUserMO'
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.MonitorMO'
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.MBOMO'
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.OperationMO'
       or rt.rt_class='com.sybase.uep.sysadmin.management.mo.ApplicationMO'
    );
   declare current_rtv_id int;
   open curs2;
   updateVersionLoop:
   loop
    fetch next curs2 into current_rtv_id;
    IF SQLCODE <> 0 THEN LEAVE updateVersionLoop END IF;
   
    update "DBA"."RES_RESOURCE_TYPE_VER_M"
     set  "RTV_VER_A"=2,
          "RTV_VER_B"=3,
          "RTV_VER_C"=0,
          "RTV_SHORT_VER_STR"=replace(RTV_SHORT_VER_STR, (select REGEXP_SUBSTR(RTV_SHORT_VER_STR, '^\d.\d.\d')), '2.3.0'),
          "RTV_DESC"=replace(RTV_DESC, (select REGEXP_SUBSTR(RTV_DESC, '\d.\d.\d')), '2.3.0')
    where "RTV_ID"=current_rtv_id;
   
    end loop updateVersionLoop;
   close curs2;
   commit;
   end;

2. From the command prompt, run: C:\SAP\MobilePlatform\Servers\SQLAnywhere16\BIN32\dbisql.exe -c "uid=dba;pwd=SAP2010_SCC" -host localhost -port 3638 C:\temp\fix_SCC.sql.
   • The dbisql.exe location varies depending on your SMP installation. For single node SMP installations, the SCC database password is "SAP2010_SCC". For cluster SMP installations, the password is your CDB password.
   • You should use the path and name of the SQL file that you saved if you used something other than C:\temp\fix_SCC.sql.
3. Restart SCC.