Find in this Blog

Saturday, September 23, 2017

ORA-38880: Cannot Advance Compatibility From 12.1.0.2.0 To 12.2.0.1.0 Due To Guaranteed Restore Points

PROBLEM:
After successful db upgrade, I tried to update the compatible parameter and restart the database. I got below error.
 
 
 
SQL>  alter system set compatible="12.2.0.1" scope=spfile;
 
System altered.
 
 
 
 
SQL> startup force
ORACLE instance started.
 
Total System Global Area 1.4663E+10 bytes
Fixed Size                 15697000 bytes
Variable Size            8455723928 bytes
Database Buffers         6140461056 bytes
Redo Buffers               51404800 bytes
ORA-38880: Cannot advance compatibility from 12.1.0.2.0 to 12.2.0.1.0 due to guaranteed restore points
 
 
 
 

SOLUTION:
The error is because, I have enabled flashback and created a guaranteed restore point, before the upgrade. So while trying to update the compatible parameter, it is not allowing. Because ,once compatible parameter is changed, we can’t downgrade.
To fix it, we need to drop the restore point. Follow below steps:
 
Set to the old existing compatible.
 
SQL> alter system set compatible="12.1.0.2.0" scope=spfile;
 
System altered.
 
SQL> startup force
ORACLE instance started.
 
Total System Global Area 1.4663E+10 bytes
Fixed Size                 15697000 bytes
Variable Size            8455723928 bytes
Database Buffers         6140461056 bytes
Redo Buffers               51404800 bytes
Database mounted.
Database opened.
 
Check the flashback restore point and drop it:
 
SQL> select GUARANTEE_FLASHBACK_DATABASE,NAME from v$restore_point;
 
GUARANTEE_FLASHBACK_DATABASE     NAME
-------------------------------- -----------------------------
YES                              GRP_1487689238734
 
SQL> select flashback_On from v$database;
 
FLASHBACK_ON
------------------
YES
 
SQL> alter database flashback off;
 
Database altered.
 
SQL> select flashback_On from v$database;
 
FLASHBACK_ON
------------------
RESTORE POINT ONLY
 
SQL> drop restore point GRP_1487689238734;
 
Restore point dropped.
 
SQL>  select flashback_On from v$database;
 
FLASHBACK_ON
------------------
NO

 
 
 Now update the compatible parameter in spfile and restart
 
SQL> show parameter comp
 
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
cell_offload_compaction              string      ADAPTIVE
compatible                           string      12.1.0.2.0
db_index_compression_inheritance     string      NONE
nls_comp                             string      BINARY
noncdb_compatible                    boolean     FALSE
plsql_v2_compatibility               boolean     FALSE
SQL> alter system set compatible="12.2.0.1" scope=spfile;
 
System altered.
 
SQL> startup force;
ORACLE instance started.
 
Total System Global Area 1.4663E+10 bytes
Fixed Size                 15697000 bytes
Variable Size            8455723928 bytes
Database Buffers         6140461056 bytes
Redo Buffers               51404800 bytes
Database mounted.
Database opened.
SQL> show parameter comp
 
NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
cell_offload_compaction              string      ADAPTIVE
compatible                           string      12.2.0.1
db_index_compression_inheritance     string      NONE
nls_comp                             string      BINARY
noncdb_compatible                    boolean     FALSE
plsql_v2_compatibility               boolean     FALSE
 

 
 
 
 
 
 
 
 
 
 

Thursday, June 8, 2017

Windows Server 2016 Volume Activation Tips


,
 
  • Updating your existing KMS hosts to support Windows Server 2016
  • Setting up a new Windows Server 2016 KMS host
  • Activating Windows 10 Enterprise 2016 LTSB

Updating existing KMS Hosts

If your KMS host is Windows Server 2012 you need to install the following updates
If your KMS host is Windows Server 2012 R2 you need to install the following updates:
Once updated you need to obtain a Windows Server 2016 CSVLK. Do the following
  1. Log on to the Volume Licensing Service Center (VLSC).
  2. Click License.
  3. Click Relationship Summary.
  4. Click License ID of their current Active License.
  5. After the page loads, click Product Keys.
  6. Look for a key called “Windows Srv 2016 DataCtr/Std KMS”
If you are unable to locate your product key please contact the Volume licensing service center
Once you have the key then run the following commands at elevated cmd prompt
1. Install the Windows Server 2016 CSVLK
    Cscript.exe %windir%\system32\slmgr.vbs /ipk <insert Windows Srv 2016 DataCtr/Std KMS CSVLK here>
2. Activate the Windows Server 2016 CSVLK
    Cscript.exe %windir%\system32\slmgr.vbs /ato
 
Windows Server 2008 R2 is not supported as a KMS Host for Windows Server 2016 or Windows 10 Enterprise 2016 LTSB edition

Setting up new Windows Server 2016 KMS host

If you want to setup a new Windows Server 2016 KMS host normally you can use the Volume Activation services role wizard or command line to configure the KMS host.
We are aware of issue where when you run the Volume Activation Services role wizard, it will report the error “vmw.exe has stopped working” during the product key management phase of the wizard
W2016 KMS Error
W2016 KMS Error-2
Microsoft is investigating this issue and will update this blog when a fix is available but in meantime you will need to configure it using the steps below
1. Open elevated cmd prompt
2. Install the Windows Server 2016 CSVLK
    cscript.exe %windir%\system32\slmgr.vbs /ipk <insert Windows Srv 2016 DataCtr/Std KMS CSVLK here>
3. Activate the Windows Server 2016 CSVLK
    Cscript.exe %windir%\system32\slmgr.vbs /ato
 
If system does not have internet connectivity do the following to activate via the command line:
1. Open an elevated command prompt
2. Obtain the Installation ID
    Cscript.exe %windir%\system32\slmgr.vbs /dti
3. Look up Microsoft phone activation number using phone number listed in %windir%System32\SPPUI\Phone.inf
4. Call the number and follow the prompts to obtain the confirmation ID
5. Apply the confirmation ID (do not include hyphens)
    Cscript.exe %windir%\system32\slmgr.vbs /atp <ConfirmationID>
6. Wait for a success message (numbers blurred on purpose)
W2016 KMS Success Message
7. Verify that the license status shows licensed:
    Cscript.exe %windir%\system32\slmgr.vbs /dlv
clip_image004

Windows 10 Enterprise 2016 LTSB Edition volume activation

Note: In addition to activating Windows Server 2016 the “Windows Srv 2016 DataCtr/Std KMS” KMS host(CSVLK) key also activates Windows 10 Enterprise 2016 LTSB edition