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

• Update: activate Windows 10 from Windows 8 or Windows 8.1, and Windows Server 2012 or Windows Server 2012 R2 KMS hosts
• July 2016 update rollup for Windows Server 2012
• Verify the version of sppsvc.exe and ensure that it is updated to at least version 6.3.9600.18376.

If your KMS host is Windows Server 2012 R2 you need to install the following updates:

• Update: activate Windows 10 from Windows 8 or Windows 8.1, and Windows Server 2012 or Windows Server 2012 R2 KMS hosts
• July 2016 update rollup for Windows 8.1 and Windows Server 2012 R2

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

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)

7. Verify that the license status shows licensed:

    Cscript.exe %windir%\system32\slmgr.vbs /dlv

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

Recover the Database without Archive Log

When we did a cloning/recover the database with noarchivelog mode, we got the problem that some datafile need to be recover. It will be difficulty since no archivelog that can help us to recover it. Otherwise we can copy all datafiles from offline backup of the source database. But it will takes time to copy/ftp/restore especially if the database size are hundreds GB or even TB. But there is a solution to recover the database with noarchivelog mode, please check this out : 
When we did a cloning, startup nomount :  

$ sqlplus '/as sysdba' 
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Apr 13 13:54:43 2010 
Copyright (c) 1982, 2007, Oracle. All Rights Reserved. 
Connected to an idle instance. 
SQL> startup nomount pfile=initMYDB.ora
ORACLE instance started. 
Total System Global Area 5251268608 bytes
Fixed Size 2091368 bytes
Variable Size 1040189080 bytes
Database Buffers 4194304000 bytes
Redo Buffers 14684160 bytes 

 

Create New control File:

      

SQL> @createctl.sql 
Control file created. 

Since the cloning come from offline backup and the SID in target db as same as source db so
we don’t need to resetlogs, but the one of datafile need to recover : 

SQL> alter database open;
alter database open
*
ERROR at line 1:
ORA-01113: file 1 needs media recovery
ORA-01110: data file 1: '/u01/system01.dbf' 

 Try To recover, but we don’t have the archivelog file that needed : 

SQL> recover database using backup controlfile until cancel;
ORA-00279: change 5991183372639 generated at 04/13/2010 13:51:42 needed for
thread 1
ORA-00289: suggestion :
/u02/db/10.2.0/dbs/arch1_1125_714320021.dbf
ORA-00280: change 5991183372639 for thread 1 is in sequence #1125 
Specify log: {=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u01/system01.dbf' 
ORA-01112: media recovery not started 

Try to open resetlogs, we still got the same error  

SQL> alter database open resetlogs;
alter database open resetlogs
*
ERROR at line 1:
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u01/system01.dbf' 

To fix this issue :
1. Shutdown immediate      

SQL> Shutdown immediate 

2. Remark the parameter in initMYDB.ora:   

- UNDO_MANAGEMENT=AUTO
- UNDO_TABLESPACE=OLD_UNDOTS

3. Add the parameter in initMYDB.ora :          

- UNDO_MANAGEMENT=MANUAL
- _ALLOW_RESETLOGS_CORRUPTION = TRUE
- _ALLOW_ERROR_SIMULATION = TRUE

4. Startup database with new init.ora :          

$ sqlplus '/as sysdba' 
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Apr 13 16:06:56 2010 
Copyright (c) 1982, 2007, Oracle. All Rights Reserved. 
Connected to an idle instance. 
SQL> startup mount pfile=initMYDB.ora
ORACLE instance started. 
Total System Global Area 5251268608 bytes
Fixed Size 2091368 bytes
Variable Size 1040189080 bytes
Database Buffers 4194304000 bytes
Redo Buffers 14684160 bytes
Database mounted.
SQL> recover database using backup controlfile until cancel;
ORA-00279: change 5991183372639 generated at 04/13/2010 13:51:42 needed for
thread 1
ORA-00289: suggestion :
/u02/db/10.2.0/dbs/arch1_1125_714320021.dbf
ORA-00280: change 5991183372639 for thread 1 is in sequence #1125 
Specify log: {=suggested | filename | AUTO | CANCEL}
cancel
ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below
ORA-01194: file 1 needs more recovery to be consistent
ORA-01110: data file 1: '/u01/system01.dbf' 
ORA-01112: media recovery not started 
SQL> alter database open resetlogs; 
Database altered. 

5. Now the database already startup with Manual undo management.
6. Create new UNDO Tablespace   

SQL> Create UNDO tablespace NEW_UNDOTS datafile '/u02/undo01.dbf' size 2048M; 

7. Take offline the OLD Undo Tablespace :   

 

 

 

SQL> alter tablespace OLD_UNDOTS offline; 

8. Take online the NEW Undo Tablespace :   

SQL> alter tablespace NEW_UNDOTS ; 

9. Shutdown the database :       

SQL> shutdown immediate; 

10. Edit the initMYDB.ora :   

+ Remark the parameter :

- UNDO_MANAGEMENT=MANUAL
- _ALLOW_RESETLOGS_CORRUPTION = TRUE
- _ALLOW_ERROR_SIMULATION = TRUE

    + Add and edit the parameter : 

UNDO_MANAGEMENT=AUTO
UNDO_TABLESPACE=NEW_UNDOTS  

11. Startup the database : 

 

SQL> startup 

12. The database will startup with the NEW Undo tablespace, change the default undo tablespace :  

 

 

SQL> alter system set undo_tablespace=NEW_UNDOTS; 

13. Then we can drop the OLD Undo tablespace :    

SQL> drop tablespace OLD_UNDOTS including contents and datafiles;

14. Good Luck     

Connection Test MDX PARSER Error

Connection Test MDX PARSER
Connection Type TCP/IP Connection

Logon Connection Error
Error Details Error when opening an RFC connection (CPIC-CALL: 'ThSAPOCMINIT', communication r
Error Details ERROR: timeout during allocate
Error Details LOCATION: SAP-Gateway on host HDBIPRDAPP sapgw00
Error Details DETAIL: no connect of TP mdxsvr from host HDBIPRDAPP after 20 sec
Error Details COMPONENT: SAP-Gateway
Error Details COUNTER: 139
Error Details MODULE: D:/depot/bas/749_REL/src/krn/si/gw/gwr3cpic.c
Error Details LINE: 2210
Error Details RETURN CODE: 242
Error Details SUBRC: 0
Error Details RELEASE: 749
Error Details TIME: Sun May 07 08:54:05 2017
Error Details VERSION: 2


Solution:

Download librfc32.dll  file from SMP and paste in to kernel directory

There is file already exist in as librfc32u.dll, But u need librfc32.dll

Refer Snote: 1032461 - MDX parser does not start