E2417 Cmd Rej: Point code does not exist in the routing table

For the ent/chg-gta commands, the point code must exist as a destination in the Route table or reside in a cluster that exists as a destination in the Route table (for global routing) unless the point code is the STP’s true point code.

For the ent/chg-gttact commands, the point code must exist as a destination in the Route table.

For the chg-ppsopts and the inh/unhb-alm commands, the point code must already exist in the Routing Indicator table.

For the ent/chg-gsmmap-scrn and ent/chg-gsms-opcode commands, the point code must exist as a destination in the ordered route entity set or must reside in a cluster (ANSI only) that exists as a destination in the ordered route entity set (for global title routing).

For the ent/dlt/rtrv-pct command, the values specified for the realpc/realpca/realpci/realpcn and filtpc/filtpca/filtpci/filtpcn parameters must already exist in the Route table.

For the chg/dlt-rtx commands, the point code must exist in the Destination table.

For the dbg-ddb, ent-cspc, and ent-rtx commands, the point code must exist in the Route table.

For the dact-rstst and rst-dstn commands, the point code must be provisioned or an X-list entry.

For the rept-stat-cluster command, the point code must already exist.

Recovery

1. Display the entries in the Route or Destination table. Enter the rtrv-rte or rtrv-dstn command, respectively.
2. Add the point codes to the appropriate tables. Refer to the Database Administration - SS7 User's Guide for more information.
3. Re-enter the command that generated this error message.
   Contact My Oracle Support if this error message appears again. See My Oracle Support (MOS).