Troubleshooting
Problem
This document describes the impact and process of changing the *LOCAL relational database directory entry.
Resolving The Problem
To change the *LOCAL RDB name, it must be removed and re-added.
That action will cause the CHGDDMTCPA parameters to be reset to defaults. So, first display them via:
===> CHGDDMTCPA <F4>Make note of the parameter values so that they can be returned to their original settings after recreating the *LOCAL entry.
Changing the *LOCAL RDBDIRE name may also cause DRDA client applications that currently specify the existing name to fail to connect. Ideally, an administrator knows what RDB name client applications use to connect to DB2 for i and have a valid RDBDIRE name available for them. An RDBDIRE alias may be created which redirects to an existing *LOCAL name (see related URL below). In that manner, both the old and new names may be utilized by different clients simultaneously.
Some DB client applications do not specify the RDB name. Those clients will not be affected by the name change.
To make the change, use the WRKRDBDIRE menu options, or use the RMVRDBDIRE and ADDRDBDIRE commands.
Removing the *LOCAL RDBDIRE causes the following message:
Removing the *LOCAL RDBDIRE causes the following message:
CPA3E01 - Removing the *LOCAL directory entry may cause loss of configuration data.Respond with C to Cancel or G to Go for this message. For additional information, refer to document:
After deleting the existing *LOCAL entry and attempting to add a new one, it is possible to encounter error message:
CPD3EC1 - Entry for local relational database already exists.This is because the DRDA protocol specification requires that client applications identify the local RDB name when making connections to remote databases. If there is a DDM/DRDA client application running on the IBM i, and the *LOCAL entry is missing, the system will automatically create it using the "Current system name" value listed in DSPNETA. This may not be the desired *LOCAL RDB name. In that case, client applications may need to first be ended.
A potential alternative is to open two PC5250/Telnet sessions so that the change can be made quickly, before the system has opportunity to automatically create the *LOCAL entry with an undesired name. In one session, delete the entry and pause before hitting "G" for "Go". In the other session, prepare the command :
===> ADDRDBDIRE RDB(Desired_RDB_Name) RMTLOCNAME(*LOCAL *IP)Hit "G" in the first session and quickly execute ADDRDBDIRE in the second.
After the new entry is added issue CHGDDMTCPA and confirm the settings are set correctly.
The Relational Database Directory Entries are stored in table QSYS/QADBXRDBD
Related Information
[{"Type":"MASTER","Line of Business":{"code":"LOB68","label":"Power HW"},"Business Unit":{"code":"BU070","label":"IBM Infrastructure"},"Product":{"code":"SWG60","label":"IBM i"},"ARM Category":[{"code":"a8m0z0000000CRKAA2","label":"Data Access-\u003EDDM DRDA"},{"code":"a8m0z0000001gLEAAY","label":"IBM i Db2-\u003EDRDA \/ DDM"}],"ARM Case Number":"","Platform":[{"code":"PF012","label":"IBM i"}],"Version":"All Versions"}]
Historical Number
N1018861
Was this topic helpful?
Document Information
More support for:
IBM i
Component:
Data Access->DDM DRDA, IBM i Db2->DRDA / DDM
Software version:
All Versions
Operating system(s):
IBM i
Document number:
643485
Modified date:
12 December 2024
UID
nas8N1018861
Manage My Notification Subscriptions