DB Partition on windows environment

Question

Dear Expert,
I am trying to add a database partition server on our BI server using db2ncrt command. The logical partition was created on the same db instance (one machine).
The issue appears when running the following command:
E:\Program Files\IBM\SQLLIB\BIN>db2ncrt /n:2 /i:DB2_01 /o:ides01 /g:10.2.1.54 /u:DB2ADMIN,tds123
The message is:
DBI1918N  An error occurred when accessing the Windows NT registry.
Explanation:
DB2 encountered an error when attempting to read or update the Windows
NT registry of the target machine.
User response:
Ensure that the current logon user account has sufficient authority to
access the Windows NT registry of the target machine. If the problem
persists, contact your IBM service representative for assistance.
Please assist me to fix the above issue.
Thank you in advance.
Regards,
Rudi

Answer 1

I used DB2 control center to add database partition, however the following error showed up:
SQL1042C  An unexpected system error occurred.
Explanation:
A system error occurred. Some possible reasons for this error are:
The database manager is not installed correctly or the environment is
   not set up correctly.
On UNIX-based systems, db2iupdt may need to be run in order to update
   the DB2 instance to enable acquisition of a new system configuration
   or access to function associated with the installation or removal of
   certain product options, FixPaks, or modification levels.
The command cannot be processed.
User response:
To update the instance to acquire a configuration or access to
   function run DB2IUPDT <InstName>.
If the error occurred while trying to connect to a database, get a
   trace (instructions below) and call IBM support.
If the problem falls outside of the above suggestions, ensure that the
system time and date is correctly set, and make sure your system has
enough memory and swapping/paging space available.
Resubmit the current command.
If the error continues, stop the database manager and restart it.
If the error still continues, reinstall the database manager.
If trace was active, invoke the Independent Trace Facility at the
operating system command prompt. Contact your technical service
representative with the following information:
Required information:
Problem description
SQLCODE or message number
SQLCA contents if possible
Trace file if possible.
Federated system users: if necessary isolate the problem to the data
source rejecting the request (see the Troubleshooting Guide for
procedures to follow to identify the failing data source). If the
problem is with a data source follow the problem determination
procedures for that data source.
sqlcode: -1042
sqlstate: 58004
Please advice.
Thanks and Regards,
Rudi