E2419 Cmd Rej: Point code does not exist in the remote point code table

For the ent-gta and ent-gtt commands, if a final GTT is specified with the ri=ssn and xlat=dpc parameters, and the force=yes parameter is not specified, then the point code must already exist in the Remote Point Code/MAP Table.

For the chg-gta and chg-gtt commands, if the new or existing value of the xlat parameter is dpc, the new or existing value of the ri parameter is ssn, and the pc/pca/pci/pcn parameter is specified, then the new point code must already exist in the Remote Point Code/MAP table.

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

For the ent-gsmmap-scrn and ent-gsms-opcode commands, if the Flexible GTT Load Sharing feature is not enabled and the ssn parameter is not specified or has a value of none, then the specified PC must already exist in the MAP table.

Recovery

1. Display the entries in the MAP table. Enter the rtrv-map command.
2. If necessary, display the current 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 Flexible GTT Load Sharing 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).