Db2 10.5 permissions reset db2iupdt5/20/2023 Create the nf file with new connect user ID and new password. Passwd: all authentication tokens updated root]#ĥ. Change the OS password for connect user and SIDadm (if required) using passwd command with root user. Create the connect user ID as OS user on DBhost (SIDadm should be created already, if not create).Ĥ. Find out the connect user /schema at environ mental variable: on DB server with env commandĬompare the connect user found out in above 2 steps, if it is not same then decide on which one to keep as connect user and Please proceed as below to resolve the issues related to connect user ID/schema, SIDadm and db2SID.ģ. Find out the connect user that used in db2 client: open the nf file from the location. sapmnt/SID/global/nfĢ. R3trans –d –v" will ends with Return Code=0012ġ.SQL1092N "USERID does not have the authority to perform the requested command or operation. SQL0551N "SAPSID" does not have the required authorization or privilege etc.Issues due to changes in SID, OS User IDs and SAP connect ID/ Schema.Īfter every system copy, refresh and migration there might be changes required in SAP SID, db schema (sap connect ID), SIDadm and db2SID. Port issues must be solved by now if the real port is opened at DB host.ī. The service name from above screen should be same as real port we find in above step with the command grep /etc/services. Find the port used in DB2 Clinet : login into SAP application host with SIDADM and open /sapmnt/SID/global/db6/db2cli.ini as shown below.ģ. The above command will give us the exact real port that is allowed By DB to connect.Ģ. TCP/IP Service name (SVCENAME) = sapdb2SIDĭ) If required, look up the real port number for the logical port name using the following command: Find the connection port (Service Name) used at DB level.Ī) Log on to the database server as user db2.ī) To display the instance configuration for the communication port, enter the following command:Ĭ) Search for the line like, for example: We may face this issues mainly when there are changes at OS level configurations after system copy/migration,ġ. The issues might occur because of change in connecting port, change in SAP connect ID (i.e schema), changes in SIDadm, db2SID users at OS level due to change in SID and changes in privileges at DB level for SAP connect ID, SIDadm, db2SID users This document mainly talks about the connectivity issues that are expected after System copy, DB refresh, and System migration.
0 Comments
Leave a Reply. |