E4543 Cmd Rej: PC/MAPSET does not exist in MAP table

For the chg-gta command, if new or existing ri=ssn and xlat=dpc parameters are specified, and the pc/pca/pci/pcn/pcn24 parameter is not specified, then the existing point code must exist in the Remote Point Code/MAP table, unless the force=yes parameter is specified.

For the chg-gsmmap-scrn and chg-gsms-opcode commands, if the Flexible GTT Load Sharing (FGTTLS) feature is enabled and the new or previously provisioned subsystem number has a value of none, then the new or previously provisioned MAP set and point code combination must already exist in the MAP table.

For the dlt-map command, if the mapset, pc, and all=yes parameters are specified, then at least one entry for the MAPSET/PC combination must exist in the MAP table.

For the ent-gsmmap-scrn and ent-gsms-opcode commands, if the mapset parameter is specified and the ssn parameter is not specified or has a value of none, then the specified MAPSET/PC combination must already exist in the MAP table.

For the rtrv-map command, if the mapset and pc parameters are specified and the ssn parameter is not specified, then at least one entry for that MAPSET/PC combination must exist in the MAP table.

Recovery

1. Display the entries in the MAP table. Enter the rtrv-map command.
2. If necessary, display the GSM MAP Screening and GSM MAP Screening operation code entries. Enter the rtrv-gsmmap-scrn or rtrv-gsms-opcode command, respectively.
3. If necessary, display the status of the FGTTLS feature. Enter the rtrv-ctrl-feat command.
   If the feature does not appear in the output, then the feature is not enabled. If the feature has a status of OFF, then the feature is enabled but is not turned on.
4. Revise the data as necessary. Refer to the Database Administration - GTT User's Guide and to the Database Administration - Features User's Guide for assistance.
5. Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
   Contact My Oracle Support if this error message appears again. See My Oracle Support (MOS).