2.2 Message Listing and Description
Command rejected messages are listed below in numerical order.
2.2.1 E2001 Cmd Rej: Undefined msg#
The value specified for the cmd parameter must be a valid system command.
Recovery
Re-enter the command that generated this error message, specifying a valid system command. Refer to the command description in Commands User's Guide for assistance.
2.2.2 E2002 Cmd Rej: Authority Violation
The user must be logged on to the EAGLE, and the user ID must have the authorization to access the command class for the selected command before the command can be entered at a system terminal.
Recovery
2.2.3 E2003 Cmd Rej: Terminal Authority Violation
The command can be entered only at a terminal that is authorized for the associated EAGLE command class.
Recovery
Perform one of the following:
- Re-enter the command at a terminal that is authorized for that EAGLE command class.
- Contact the system administrator to discuss EAGLE terminal command access privileges for the original terminal.
- If you have system administration authority, change the privileges for the terminal.
Enter the
chg-secu-trmcommand.Note:
This command cannot be entered the target terminal.
2.2.4 E2004 Cmd Rej: Keyboard is locked. Enter UNLOCK command
The keyboard for the terminal was locked using the lock command.
Recovery
Unlock the keyboard. Enter the unlock command. Anyone attempting to use the keyboard will be prompted to enter the password of the currently logged-on user.
2.2.5 E2005 Cmd Rej: Argument frame overflow
The frame for the argument detected an overflow condition in the command.
Recovery
Re-enter the command that generated this error message, specifying a valid format and combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.6 E2006 Cmd Rej: Missing parameter block separator
Use a colon (:) to separate multiple blocks.
Recovery
Re-enter the command that generated this error message, specifying a colon (:) between the input values. Refer to the command description in Commands User's Guide for assistance.
2.2.7 E2007 Cmd Rej: Too many errors in this command
The command contains too many errors to allow continued processing.
Recovery
Re-enter the command that generated this error message, specifying a valid format and 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.8 E2008 Cmd Rej: Missing command identifier
A keyword must be specified for the command. Keywords identify the principal action to be performed by the system and consist of one to three words. In the following example, dact-slk is the keyword: dact-slk:loc=1101:port=a
Recovery
Re-enter the command that generated this error message, specifying a keyword. Refer to the command description in Commands User's Guide for assistance.
2.2.9 E2009 Cmd Rej: Missing modifier separator
A hyphen (-) must be used to separate multiple values within a parameter block.
Recovery
Re-enter the command that generated this error message, specifying a hyphen (-) between the input values. Refer to the command description in Commands User's Guide for assistance.
2.2.10 E2010 Cmd Rej: Unrecognized command
The EAGLE does not recognize the command that was entered.
Recovery
2.2.11 E2011 Cmd Rej: Missing mandatory parameter - <parm>
All parameters that are required for the command must be specified.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.12 E2012 Cmd Rej: Cannot specify ALL=YES when command given
The all=yes parameter cannot be specified.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.13 E2013 Cmd Rej: Missing argument assignment operator
An argument assignment operator (=) is required in the command.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.14 E2014 Cmd Rej: Unrecognized parameter identifier
The EAGLE does not recognize the specified parameter.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.15 E2015 Cmd Rej: Missing parameter identifier
An identifier is required in the command.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.16 E2016 Cmd Rej: <parm_desc> is out of range - <parm>
The value specified for the parameter must be in the range defined by the command.
Note:
Theflash-card command cannot be used to load flash images for HMUX or HIPR MUX cards. Use the init-flash command.
Recovery
Re-enter the command that generated this error message, specifying a valid value for the parameter. Refer to the command description in Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.17 E2017 Cmd Rej: <parm_desc> is out of range, <min>...<max> - <parm>
The parameter is out of range of the allowed minimum and maximum values
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.18 E2018 Cmd Rej: <parm_desc> is out of range, <min>...<max>, ‘<char>’ - <parm>
The specified value is outside the range of the allowed minimum and maximum values or valid characters for the parameter.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.19 E2019 Cmd Rej: <parm_desc> is out of range, <min>...<max>, ‘<char>’, ‘<char>’ - <parm>
The specified value is outside the range of the allowed minimum and maximum values and characters for the parameter.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.20 E2020 Cmd Rej: Table copy command already in process
If the command is already running, then the command cannot be re-entered until the first execution is complete.
Recovery
Re-enter the copy-meas command that generated this error message after the first execution of the command is complete.
Note:
Under ideal circumstances with minimum system activity, the command requires at least 1 minute to execute.2.2.21 E2021 Cmd Rej: Invalid source table
A valid syntax must be assigned to the source table parameter.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.22 E2022 Cmd Rej: Invalid destination table
A valid syntax must be assigned to the destination table parameter.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.23 E2023 Cmd Rej: Invalid OAM drive
A valid syntax must be assigned to the Operations, Administration and Maintenance (OAM) parameter.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.24 E2024 Cmd Rej: Invalid system
A system error occurred during the execution of a command.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.25 E2025 Cmd Rej: Invalid card location
For the act-lbp command, the value specified for the loc parameter must indicate an HC-MIM, E5-E1T1, or E5-E1T1-B card, provisioned with the LIMT1 card type, running the SS7ANSI or CCS7ITU application.
For the chg-db command, a value of 1113 or 1115 must be specified for the sloc parameter.
For the ent-card command, a type DSM card must be inserted into an odd-numbered card location. The n+1 slot next to the DSM card must be empty, where n is the odd-numbered location (for example, if the DSM is in location 1101, then the 1102 slot must be empty and not provisioned).
For the ent-trace command, values of 1113 - 1118 cannot be specified for the loc parameter.
For the rept-imt-lvl2 command, MUX card locations (xx09 and xx10), E5-TDM card slots 1114 and 1116, and E5-MDAL slots 1117 and 1118 cannot be specified as values for the loc, sloc, and eloc parameters.
For the rept-stat-gedti command, the value specified for the loc parameter must correspond to the location of an IPSM card that is configured as a GEDTI Hub.
For the rept-stat-j1 command, card location 1118 cannot be specified.
For the rept-stat-rtd command, the following card locations cannot be specified: 1114, 1116, 1117, 1118 (E5-TDM, E5-MDAL cards), and all xy09 and xy10 locations where x is the frame and y is the shelf (HMUX or HIPR MUX cards).
For the rtrv-data-rtdb command, the card location slot must be between 1 and 16 and not 9 or 10. The frame location must be 1xxx, 2xxx, 3xxx, 4xxx, 5xxx, or 6xxx. The shelf location must be 11xx, 12xx, 13xx, 21xx, 22xx, 23xx, 31xx, 32xx, 33xx, 41xx, 42xx, 43xx, 51xx, 52xx, 53xx, or 61xx.
For the tst-disk command, the card in the specified location must be an E5-TDM or an E5-MCAP card.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.26 E2026 Cmd Rej: Already logged on
An attempt was made to log on with a user ID that is already logged on to the system.
Recovery
2.2.27 E2027 Cmd Rej: IP Address requires 4 octets in the range 1 . . . 254 - <parm>
The IP address of the value for the specified parameter must contain four octets in the range of 1- 254.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.28 E2028 Cmd Rej: Octet 1 is out of range, 1 . . . 223 - <parm>
A value of 1 - 223 must be specified for octet 1.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.2.2.29 E2029 Cmd Rej: Octet 2 is out of range, 1 . . . 254 - <parm>
A value of 1- 254 must be specified for octet 2.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.30 E2030 Cmd Rej: Octet 3 is out of range, 1 . . . 254 - <parm>
A value of 1 - 254 must be specified for octet 3.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.31 E2031 Cmd Rej: Octet 4 is out of range, 1 . . . 254 - <parm>
A value of 1 - 254 must be specified for octet 4.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.32 E2032 Cmd Rej: Octet 1 missing - <parm>
The specified IP address must contain the first octet.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.33 E2033 Cmd Rej: Octet 2 missing - <parm>
The specified IP address must contain the second octet.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.34 E2034 Cmd Rej: Octet 3 missing - <parm>
The specified IP address must contain the third octet.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.35 E2035 Cmd Rej: Octet 4 missing - <parm>
The specified IP address must contain the fourth octet.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.36 E2036 Cmd Rej: Too many octets specified, only require 4 - <parm>
The specified IP address can contain only four octets.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.37 E2037 Cmd Rej: Invalid character in IP address - <parm>
The specified IP address must contain valid parameters.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.38 E2038 Cmd Rej: <parm_desc> too short, min <min>, max <max>, - <parm>
The specified string that must contain at least the minimum number of required characters.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.39 E2039 Cmd Rej: <parm_desc> too long, min <min>, max <max>, - <parm>
The specified string cannot exceed the maximum number of characters allowed for the parameter.
Recovery
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.
2.2.40 E2040 Cmd Rej: String pattern nonconformance, alphanumeric - <parm>
The specified string pattern must conform to the required alphanumeric content for the parameter.
Recovery
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.
2.2.41 E2041 Cmd Rej: String pattern nonconformance, alphabetic - <parm>
The first character of the translation name must be a letter.
Recovery
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.
2.2.42 E2042 Cmd Rej: String pattern nonconformance, numeric - <parm>
The referenced string pattern must conform to the required numeric content for the parameter.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.43 E2043 Cmd Rej: System error - revert to mandatory in-pattern specification
An unanticipated system error has been detected. Make a note of this error and the attendant situation.
Recovery
Contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.44 E2044 Cmd Rej: <parm_desc> value is undefined - <parm>
The entered command is missing a required parameter value.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.2.2.45 E2045 Cmd Rej: <parm_desc> num digits incorrect, min <min> max <max> - <parm>
A valid number of digits must be entered for the parameter values. The values represented by <min> and <max> specify the valid minimum and maximum number of digits allowed for the command parameter.
Recovery
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.
2.2.46 E2046 Cmd Rej: Argument definition error, bad argument type
An unanticipated system error has been detected. Make a note of this error and the attendant situation.
Recovery
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.47 E2047 Cmd Rej: Missing information unit separator
A hyphen (-) character must be used to separate information units.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.48 E2048 Cmd Rej: Unneeded information found
The command entered contains unnecessary information.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.49 E2049 Cmd Rej: Lower bound exceeds upper bound of range - %
The value specified for the lower bound must be less than or equal to the value specified for the upper bound for the parameter range.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.50 E2050 Cmd Rej: Incorrect information unit, expecting number or range - <parm>
A valid number or range of numbers must be specified for the parameter.
Recovery
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.
2.2.51 E2051 Cmd Rej: Incorrect information unit, expecting number - <parm>
An invalid number was specified for a parameter value. The value represented by <parm> varies according to the specific command entered.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.52 E2052 Cmd Rej: Incorrect information unit, expecting IP address - <parm>
A valid IP address must be specified for the parameter.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.53 E2053 Cmd Rej: Incorrect information unit, expecting string - <parm>
A valid string must be specified for the parameter.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.54 E2054 Cmd Rej: Incorrect information unit, expecting mnemonic - <parm>
A valid mnemonic must be specified for the parameter value.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.55 E2055 Cmd Rej: Incorrect information unit, expecting point code - <parm>
A valid point code must be specified for the parameter value.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.56 E2056 Cmd Rej: Incorrect information unit, expecting number or * - <parm>
A valid number or variable must be specified for the parameter value.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.57 E2057 Cmd Rej: Incorrect information unit, translation type - <parm>
A valid information unit must be specified for the translation type.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.58 E2058 Cmd Rej: Incorrect information unit, expecting card location - <parm>
A valid card location must be specified for the parameter value.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.59 E2059 Cmd Rej: <parm_desc> is out of range, <min>...<max> - <parm>
The specified value must be within the range of the minimum and maximum values allowed for the parameter.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameterss. Refer to the command description in Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.60 E2060 Cmd Rej: Lower bound exceeds upper bound of range - <parm>
The lower bound value of the range must be less than or equal to ihe upper bound value for the parameter range.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.61 E2061 Cmd Rej: Incorrect input, expecting number, * or range - <parm>
The specified value must contain the supported characters (number, variable, or a range of numbers).
Recovery
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.
2.2.62 E2062 Cmd Rej: Incorrect information unit, expecting number or none - <parm>
The specified value must contain a number or the string none.
Recovery
Re-enter the command that generated the 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.63 E2063 Cmd Rej: Try Double Quoting Parameter with ‘_’
An underscore character must be encased in double quotes "_".
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.64 E2067 Cmd Rej: Card location specified must be an SIP card
For the
rept-stat-sip command, the card
location specified must be an SIP card.
For the
rtrv-gttset command, duplicate values cannot be
specified for the
setidx parameter.
Recovery
2.2.65 E2068 Cmd Rej: Only 100 Unique and 1 DFLT PHCTXT allowed
For the
ent-sip-npp command, the SIPPHCXT
table can have a maximum of 101 Phone Contexts which includes 100 Unique and 1
DFLT
Recovery
2.2.66 E2069 Cmd Rej: Card location specified must be an SM card
For the rept-stat-mps command, the card location specified in the loc parameter must contain a Service Module running either the SCCPHC/SCCP64, SIPHC/SIP64, or DEIRHC/DEIR64 GPLs.
Recovery
2.2.67 E2070 Cmd Rej: IP Address invalid for Address Class
A valid IP Address must be specified.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.68 E2071 Cmd Rej: Network Portion Invalid
The specified network numbers cannot contain all 0 bits or all 1 bits.
For the ent-dlk command, the first octet of the IP Address cannot be 127. The 127 value represents an IP address for loopback.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.69 E2072 Cmd Rej: Host Portion Invalid
The specified Host Portion cannot contain all 0 bits or all 1 bits.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.70 E2073 Cmd Rej: SCCP or SIP or DEIR or ENUM not Configured
For the rept-stat-mps command, a Service Module card running the VSCCP, SIPHC, DEIRHC, or ENUMHC application must be configured before this command can be entered.
Recovery
2.2.71 E2074 Cmd Rej: Card location specified must be an DEIR card
The card location specified with this command must contain a Service Module running the DEIRHC/DEIR64 GPL.
Recovery
2.2.72 E2075 Cmd Rej: Speed=1000 can be specified only with ExAP Port
Recovery
Re-enter the chg-ip-lnk command with 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.73 E2077 Cmd Rej: Invalid IPV6 address not in an acceptable format
The IPv6 Address should be in the correct format. Example:
2003:0db8:0000:130F:0000:0000:087C:140B or 2003:db8:0:130F::87C:140B
should be enclosed in double quotes ("").
Recovery
Re-enter the IPv6 address with the correct syntax.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.74 E2080 Cmd Rej: Alarms already inhibited for cluster PC or its member PCs
Recovery
- Use the
rept-stat-almcommand to display alarm status. - Use the
unhb-almcommand to restore reporting of alarms as needed. - Re-enter the
inh-almcommand that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.75 E2083 Cmd Rej: GTTSN parameter mustn't be specified
If the OBSR feature is enabled or the FLOBR feature is turned on, then the gttsn parameter cannot be specified.
Recovery
2.2.76 E2084 Cmd Rej: A-Port or IGM must be turned ON
For the enable-ctrl-feat command, the A-Port or IGM feature must be turned on before the LOCREQ Query Response feature can be enabled.
For the ent-srvsel command, the A-Port or IGM feature must be turned on before the serv=mnp parameter can be specified.
Recovery
2.2.77 E2085 Cmd Rej: A-Port, G-Port or IGM must be turned ON
For the enable-ctrl-feat command, the A-Port, G-Port, or IGM feature must be on before the MNP Circular Route Prevention feature can be enabled.
For the ent/chg-srvsel commands, the A-Port or IGM feature must be turned on, or the A-Port or IGM feature must be enabled and the G-Port feature must be turned on before a value of mnp can be specified for the (n)serv parameter.
Recovery
2.2.78 E2086 Cmd Rej: GTT must be turned ON for A-Port
The GTT feature must be turned on before the A-Port feature can be enabled.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.2.2.79 E2087 Cmd Rej: GTT must be turned ON for G-Port
The GTT feature must be turned on before the G-Port feature can be turned on.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.80 E2088 Cmd Rej: GTT must be turned ON for IGM
Note:
Once a feature that is cotnrolled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.81 E2100 Cmd Rej: Card location already equipped
The card in the location specified by the loc parameter cannot already be provisioned in the database.
Recovery
2.2.82 E2101 Cmd Rej: Card location is unequipped
The card location specified by the loc or the rloc parameter must contain a card that is valid for the command and was defined previously in the database for the specified card location.
A card that contains the specified signaling link must be equipped in the specified card location.
For the init-card command, the shelf and card must be equipped.
For the rept-meas command, if the enttype=sctpcard parameter is specified, a card must be installed in the location specified by the loc parameter.
Recovery
2.2.83 E2102 Cmd Rej: Failed reading the IMT table
The IMT table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.84 E2103 Cmd Rej: Failed reading the link table
The Link table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.85 E2104 Cmd Rej: Failed reading the shelf table
The Shelf table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.86 E2105 Cmd Rej: Invalid card TYPE and APPL load type combination
For the act-upgrade command, if a card with card type DCM is used, then values of ss7ipgw, ipgwi, iplim, and iplimi cannot be specified for the appl parameter.
Caution:
It is strongly recommended that this command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.For the chg-card command, the value specified for the loc parameter must indicate a card with a card type of DCM that is running the IPLIM or IPLIMI application.
For the ent-card command, the values specified for the type and appl parameters must be compatible. Refer to the command description in Commands User's Guide for a list of compatible values.
Recovery
2.2.87 E2106 Cmd Rej: Link is in test mode
The act-slk command cannot be entered while the tst-slk command is in progress.
Recovery
Re-enter the act-slk command that generated this error message after the signal link test is complete.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.88 E2107 Cmd Rej: Link assigned to card
The card in the location specified by the loc parameter cannot be deleted from the database until any signaling link or TCP/IP data link assigned to the card is deleted from the database.
Recovery - SS7 links
- Display the signaling links in the database. Enter the
rtrv-slkcommand. - Delete the signaling links assigned to the card as necessary. Refer to the Database Administration - SS7 User's Guide for assistance.
- Re-enter the
dlt-cardcommand that generated this error message.Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - TCP/IP links
2.2.89 E2108 Cmd Rej: Shelf location not equipped
For the ent/chg-card command, the shelf location, specified by the loc parameter, must be provisioned.
For the rept-imt-info command, the shelf locations, specified by the sshelf and eshelf parameters, must be provisioned.
Recovery
2.2.90 E2109 Cmd Rej: Database maintenance is required
The command failed because the system detects that:
-
The database is incoherent (the command requires that the database be coherent).
-
The levels of source databases, during a duplex backup or repair, are not identical on the active and standby OAM fixed disks.
-
The database is corrupt. An audit has detected a mismatched checksum in a subset.
Recovery
2.2.91 E2110 Cmd Rej: Unable to access DB level
A severe system fault has occurred and the command was rejected.
Recovery
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.92 E2111 Cmd Rej: Database consistency violation - maintenance required
A database inconsistency has been detected.
Recovery
Re-enter the rtrv-rte command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.93 E2112 Cmd Rej: At least one parameter must be changed
At least one valid optional parameter must be specified.
Recovery
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.
2.2.94 E2113 Cmd Rej: CLLI cannot be specified without Point Code
The clli and apc/apca/apci/apcn/apcn24 parameters must be specified together in the command.
Recovery
Re-enter the chg-ls command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide (SS7 linkset) or the Database Administration - IP7 User's Guide (IP linkset) for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.95 E2118 Cmd Rej: IP address already in use
For the chg-snmp-host command, the specified IP address is in use for another SNMP host.
ent-snmp-host command, the specified IP address is in use for another SNMP host.
Note:
The entry for the specified IPADDR can not already exist.Recovery
2.2.96 E2119 Cmd Rej: BPS must be 56000 or 64000
If the card application is SS7ANSI or CCS7ITU, then a value of 56000 or 64000, respectively, must be specified for the bps parameter. If SE-HSL or ST-HSL-A cards are used, then a value of 1984000 or 1536000, respectively, must be specified for the bps parameter.
Recovery
2.2.97 E2121 Cmd Rej: PCRN1 and PCRN2 parameters are invalid if ECM=BASIC
If the ecm=basic parameter is specified, then the pcrn1 and pcrn2 parameters cannot be specified.
Recovery
2.2.98 E2122 Cmd Rej: Failed reading linkset table
The Linkset table is corrupt or cannot be found.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.99 E2123 Cmd Rej: Hostname already in use
ent-snmp-host command, the hostname is used by another SNMP host.
Note:
The entry for the specified HOST name can not already exist.Recovery
2.2.100 E2124 Cmd Rej: All links of LSN must use same error correction method
The same value must be specified for the ecm parameter for all links in a linkset.
Recovery
2.2.101 E2125 Cmd Rej: Links on specified linkset are in-service
If one or more links in a specified linkset are in service, then the apc/apca/apci/apcn/apcn24 and rcontext parameters cannot be specified.
A linkset that still has signaling links assigned to it cannot be changed.
If links in the linkset are in service, then the linkset type cannot be changed.
Recovery
2.2.102 E2126 Cmd Rej: Invalid linkset type for card
The linkset type must be valid for the card:
- The linkset adjacent point code (APC) type must be the same as the card application type (ANSI or ITU).
- IPSG-M2PA linksets cannot contain IPGWx and IPSG-M3UA link types during transition. After the linkset is transitioned to IPSG-M2PA, only IPSG-M2PA and IPLIM links can be added to the linkset.
- IPSG-M3UA linksets cannot contain SS7IPGW, IPGWI, and IPGHC link types during transition. After the linkset is transitioned to IPSG-M3UA, only IPSG-M3UA links can be added to the linkset.
Recovery
2.2.103 E2127 Cmd Rej: L2 timer not valid for the signaling link type
The L2 timer range must be valid for the type of signaling link being provisioned. Refer to the command description in Commands User's Guide for the valid ranges.
Recovery
2.2.104 E2128 Cmd Rej: Linkset assigned to route must have at least one link
For the dlt-slk command, the force=yes parameter must be specified to remove the last signaling link in a linkset that is assigned to a route.
For the ent-rte command, the linkset specified by the lsn parameter contain at least one link or the force= yes parameter must be specified.
Recovery
2.2.105 E2129 Cmd Rej: CDPNPFX must be specified
If the ncdpnpfx or dltpfx parameter is specified, then the cdpnpfx parameter must be specified.
Recovery
Re-enter the chg-inpopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the INP/AINPQ User's Guide for assistance.
2.2.106 E2130 Cmd Rej: Maximum number of links are assigned to this linkset
Links must be available in the linkset that is specified by the lsn parameter.
Recovery
2.2.107 E2131 Cmd Rej: Parameters not valid for card type
For the chg-clkopts command, the parameters entered are not compatible with the card where the clock resides.
For the ent-dlk command, if the type=acmenet parameter is specified (see the ent-card command), then the duplex and auto parameters cannot be specified.
For the ent-slk command, a valid combination of parameters must be specified. Refer to the command description in Commands User's Guide for valid combinations of parameters.
For the inh/unhb-alm commands, the card
specified by the loc parameter must have an IPS,
MCP, EROUTE, VSCCP, IPSG, IPLIM, IPLIMI, SS7IPGW, or IPGWI application.
For the rept-stat-iptps command, the history, link, loc, and tpscost parameters can be specified for only IPSG cards.
Recovery
2.2.108 E2132 Cmd Rej: The specified SLC is in use
The value specified for the slc parameter cannot already be used by a link in the linkset.
Recovery
2.2.109 E2133 Cmd Rej: There is a link already assigned to this port
A link cannot already be assigned to the specified port.
Recovery
2.2.110 E2134 Cmd Rej: SNMP Host table is full
For the ent-snmp-host command, the SNMP host table contains the maximum number of entries allowed.
Recovery
2.2.111 E2135 Cmd Rej: Failure reading SNMP Host table
For the chg-snmp-host command, an error occurred while reading the SNMP Host table.
For the ent-snmp-host command, an error occurred while reading the SNMP Host table.
For the dlt-snmp-host command, an error occurred while reading the SNMP Host table.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.112 E2136 Cmd Rej: At least one optional parameter is required
At least one optional parameter must be specified in the command.
Recovery
Re-enter the command that generated this error message, specifying at least one valid optional parameter. Refer to the command description in Commands User's Guide for assistance.
2.2.113 E2137 Cmd Rej: Port must be inhibited to change comm. attributes
The terminal port must be inhibited before the type, baud, prty, sb, and fc parameters can be changed.
Recovery
2.2.114 E2138 Cmd Rej: Failed reading terminal table
The Terminal table is corrupt or cannot be found by the system.
Recovery
Re-enter the chg-trm command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.115 E2139 Cmd Rej: Invalid BAUD value specified
The value specified for the baud parameter must be within the allowed range. Refer to the description of the chg-trm command in the Commands User's Guide for a list of valid values.
Recovery
Re-enter the chg-trm command that generated this error message, specifying a valid combination of parameters.
2.2.116 E2140 Cmd Rej: Invalid PRTY value specified
A valid value must be specified for the prty parameter. Refer to the chg-trm command description in Commands User's Guide for a list of valid values.
Recovery
Re-enter the chg-trm command that generated this error message, specifying a valid combination of parameters.
2.2.117 E2141 Cmd Rej: Invalid FC value specified
If E5-MASP hardware is used, then a value of hw or both cannot be specified for the fc parameter.
Recovery
2.2.118 E2142 Cmd Rej: TYPE = VT320 and PRTY=NONE combination not allowed
The type=vt320 and prty=none parameters cannot be specified together in the command.
Recovery
- Display the current settings for the terminal. Enter the
rtrv-trmcommand. - Re-enter the
chg-trmcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.119 E2143 Cmd Rej: The terminal state request was unanswered
There is a problem with the E5-OAM cards or the extended bus interface (EBI) between them. This problem is preventing the system from determining what state the specified terminal or port is in. The terminal or port attributes cannot be changed until the state of the terminal or port can be determined. This error message follows other error messages or system troubles.
Recovery
2.2.120 E2144 Cmd Rej: Location invalid for hardware configuration
A card must be equipped and must be in the appropriate location for the card type. Refer to Commands User's Guide for information about the card requirements for a particular command.
For the chg-ee-card and rept-stat-ee commands, the value specified for the loc parameter does not have Eagle Eyes service capability.
For the chg-gedti-card command, the value specified for the loc parameter must correspond to the location of a card provisioned as an IPSM card.
For the dact-gedti command, the value specified for the loc parameter must refer to an equipped card location.
For the disp-tbl and set-tbl commands, the 1117 location is used by E5-MDAL cards, the 1113 and 1115 locations are used by E5-MCAP cards, and the 1114 and 1116 locations are used by E5-TDM cards.
For the ent-card command, the n+1 slot next to the SM or HC-MIM card must be empty, where n is the odd-numbered location (for example, if the SM card is in location 1101, then the 1102 slot must be empty and not provisioned).
For the rept-stat-card command, the card location specified by the loc parameter must be equipped.
For the rept-stat-sflog command, the shelf and card must be equipped.
For the rept-stat-deir command, the card at the specified location does not support this command.
For the rept-stat-enum command, the shelf and card must be equipped, and the card specified by the loc parameter must have an application of enumhc.
For the rtrv-card command, the specified card location must be equipped in the database.
Recovery
- Display the cards in the database. Enter the
rtrv-cardcommand. - Re-enter the command that generated this error message, specifying a valid card location. Refer to Commands User's Guide for more information about the card requirements for each command.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.121 E2145 Cmd Rej: Failed reading MAS configuration table
The MAS Configuration table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.122 E2146 Cmd Rej: BPS value not supported
The value specified for the bps parameter must be supported for the card application. Refer to the command description in Commands User's Guide for a list of valid values.
Recovery
2.2.124 E2148 Cmd Rej: DPC must be a cluster DPC or cluster member
If a DPC is specified, it must be an x-list entry, a cluster DPC, or a member of a provisioned cluster.
Recovery
2.2.125 E2149 Cmd Rej: TYPE = SCCS and PRTY=NONE combination not allowed
The type=sccs and prty=none parameters cannot be specified together in the command.
Recovery
Re-enter the chg-trm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.126 E2150 Cmd Rej: Frame ID out of range
The frame value of the loc parameter must be within the valid range.
Recovery
Re-enter the rept-stat-db 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.127 E2151 Cmd Rej: Failure reading SNMP Options table
For the chg-snmpopts command, an error occurred while reading the SNMP Options table.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.128 E2152 Cmd Rej: Shelf ID out of range
The value specified for the loc parameter is not valid physically. The first and second digits in the loc parameter do not identify a valid shelf.
The frame and shelf portions of the specified card location (loc) can be 11 through 13, 21 through 23; 31 through 33; 41 through 43; 51 through 53; and 61.
The format of the address specified by the loc parameter is XYZZ , where:
X = frame (1, 2, 3, 4, 5, or 6)
Y = shelf within the frame (1, 2, or 3)
ZZ = slot within the shelf range for control shelf,
X = 1, Y = 1, ZZ = 1-8, 11-12
for disc-imt, ZZ = 1-8, 11-13 and 15
for init-card, ZZ = 1-8, 11-13, and 16
for rept-stat-card, ZZ = 1-8, 11-13, and 17
range for extension shelves (all other shelves) is 1-8, 11-18
Recovery
Re-enter the command that generated this error message, specifying a valid shelf ID. Refer to the description for the ent-card command in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.129 E2153 Cmd Rej: Card slot location out of range
The value specified for the loc parameter is physically invalid. The slot portion of the specified card location can be 1- 8 and 11- 18. Slots 09 and 10 cannot be specified. The card location is xyss , where x is the frame, y is the shelf, and ss is the slot.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the Installation Guide and to the command description in Commands User's Guide for assistance.
2.2.130 E2154 Cmd Rej: Card slot reserved by system
For the chg-ee-card command, the loc parameter value specified is reserved for system operation and cannot be specified for the loc parameter.
For the ent/chg/dlt-e1, ent/chg/dlt-j1, and ent/chg/dlt-t1 commands, card locations 1113 - 1118 (E5-OAM cards) cannot be specified as values for the loc parameter.
For the dbg-ddb command, locations 1113 - 1118 cannot be specified as values for the loc or rloc parameters.
For the rept-stat-db command, for E5-OAM cards, locations 1117 and 1118 cannot be specified as values for the loc parameter.
Recovery
Re-enter the command that generated this error message, specifying a valid card location. Refer to the command description in Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.131 E2155 Cmd Rej: Invalid parameter combination specified
An invalid parameter combination has been specified.
Table 2-1 describes the parameter combinations that generate this error message.
Table 2-1 Invalid Parameter Combinations
| Command | Invalid Parameter Combination Entered |
|---|---|
|
|
The loc and sloc/eloc parameters cannot be specified together. The loc parameter or the sloc/eloc parameters must be specified. The gpl parameter must be specified if the sloc/eloc parameters are specified. The sloc and eloc parameters must be specified together. The value specified for the sloc parameter cannot be greater than the value specified for the eloc parameter. If the target card is an HMUX, HIPR, or HIPR2 MUX card, then both card locations specified in the sloc and eloc parameters must contain HMUX, HIPR, or HIPR2 MUX cards on the same IMT bus. The bus is implicit based on the specified location. Location xy09 specifies an HMUX, HIPR, or HIPR2 MUX A Bus, and location xy10 specifies an HMUX, HIPR, or HIPR2 MUX B Bus (x is the frame and y is the shelf). For example, sloc=1109:eloc=6109 specifies all HMUX, HIPR, or HIPR2 MUX cards on the A Bus only; sloc=1110:eloc=6110 specifies all HMUX, HIPR, or HIPR2 MUX cards on the B Bus only. HMUX, HIPR, or HIPR2 MUX cards from both the A bus and B bus cannot be flash downloaded simultaneously. If the target is HC Blade, and if the loc parameter is specified, then the gpl parameter must be specified. |
|
|
The action=getrel and release parameters must be specified together in the command. |
|
|
The loc parameter cannot be specified with the eloc and sloc parameters. Either the loc parameter or the eloc and sloc parameters must be specified. The eloc and sloc parameters must be specified together in the command. The sloc parameter value cannot be greater than the eloc parameter value. The perdata parameter is valid only with the data parameter. |
|
|
If the ddbqp parameter is specified, then the type=ddb parameter must be specified. If the gplqp parameter is specified, then the tblid, ddbqp, and type=ddb parameters cannot be specified. The display and tblid parameters cannot be specified together in the command. |
|
|
The pc or ds parameter must be specified. The parameters cannot be specified together in the command. For the
For the
|
|
|
The status and alarm parameters cannot be specified together in the command. |
|
|
The action=restore and src=server parameters must be specified before the file parameter can be specified. If the src=server parameter is specified, then the file parameter must be specified. The action=restore and src=remove parameters must be specified before the sloc parameter can be specified. |
chg/dlt/rtrv-enum-profsel
|
The ENTITYID parameter cannot be specified with the SDN or EDN parameters. |
chg/ent-enum-prof
|
The RRDOMAIN parameter is valid for SPARM=SIP or SPARM=PSTNSIP. |
chg-gsmopts
|
The eirimsichk parameter and the on or off parameter cannot be specified together in the command. |
|
|
The acn and family parameters cannot be specified together in the command. If the cgssn parameter is specified, then the ecdssn parameter cannot be specified. If the cdssn parameter is specified, then the ecgssn parameter cannot be specified. If the saddr parameter is specified, then the ecgssn/ecdssn parameter cannot be specified. The specified GTT set must have a set type of opcode (see the
The specified GTT set must have a set type of cdssn before the cdssn parameter can be specified. The specified GTT set must have a set type of cgssn before the cgssn parameter can be specified. The specified GTT set must have a set type of cdgta or cggta before the gta parameter can be specified. The specified GTT set must have a set type of opc before the opc parameter can be specified. The specified GTT set must have a set type of cgpc before the cgpc parameter can be specified. The cgpc, cgssn, gta, opc, cdssn, and opcode parameters cannot be specified together in the command. If the xlat=none parameter is specified, then the ri, pc/pca/pci/pcn/pcn24, force, ssn, and ccgt parameters cannot be specified. If the cgssn and cdssn parameters are both specified in the same command (in any order), then only the value for the last of the two parameters specified is used during processing. |
|
|
The nsdd/nsds, npdd/npds, or rdmod parameter cannot be specified together. The four values can be added or changed (but not at the same time). To specify or delete existing values or to change between suffix and prefix manipulations, the rdmod parameter must be used to reset the current values. |
|
|
The nnp, nnai, nsdd, nsds, npdd, and npds parameters cannot be specified with the rmgtt parameter in the command. |
chg-gttact
|
A value of dup or fwd must be specified for the act parameter before the pc/pca/pci/pcn/pcn24/pcn16, cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16, ssn, ri, tt, mrnset, mapset, loopset, cgpcogmsg, cdgtmodid, or cggtmodid parameters can be specified and before a value of useicmsg can be specified for the on or off parameter The act=tcaperr parameter must be specified before the atcaperr or itcaperr parameter can be specified The act=udts parameter must be specified before the udtserr parameter can be specified. The act=fwd/sfthrot/scpval parameter must be specified before the defactid parameter can be specified. The Service Numbering Plan (snp), Service Nature of Address Indicator (snai), Service Name (srvcname), and Service Error Cause (srvcerr) parameters can be specified only when act is set to srvc. The srvc/sflog/sfthrot/scpval GTT Action cannot be changed to any other GTT Action (dup, fwd, tcaperr, disc, udts), and vice versa. The threshold and bursts parameters can be specified only when act is set to sfthrot. The sfthrot GTT Action cannot be changed to any other GTT Action (dup, fwd, tcaperr, disc, udts, srvc, scpval, sflog), and vice versa. The scpval GTT Action cannot be changed to any other GTT Action (dup, fwd, tcaperr, disc, udts, srvc, sfthrot, sflog), and vice versa. The sflog GTT Action cannot be changed to any other GTT Action (dup, fwd, tcaperr, disc, udts, srvc, sfthrot, scpval), and vice versa. The SCCP parameter (sprm), TCAP parameter (tprm) and number of digits to be matched (ndgt) parameters can be specified only when act is set to scpval. |
chg-is41opts
|
The smsreqbypass and locreqrmhrn parameters and the on or off parameter cannot be specified in the same command. |
chg-ls
|
If the sapc, matelsn, rcontext or action parameter is specified, those parameters are the only optional parameters that can be specified. If the action parameter is specified, the sapc, rcontext, or matelsn parameter must be specified. If the ipsg parameter is specified, no other optional parameter can be specified. |
chg-measopts
|
The platformenable and oamhcmeas parameters cannot be specified together in the command. Parameters cannot be specified individually and as options for the on or off parameter in the same command. |
chg-mtc-measopts
|
Parameters cannot be specified individually and as options for the on or off parameter in the same command. |
chg-npp-as, ent-npp-as
|
The ca/caX, fa/faX, and sa/saX parameters cannot be specified together in the command. For the
|
chg-secu-dflt
|
If the clrwrntx=all parameter is specified, then the wrnln and wrntx parameters cannot be specified. |
chg-stpopts
|
If the on or off parameter is specified, then the ansigflex, archbldid, cnvcgda, cnvcgdi, cnvcgdn, cnvcgdn24, gtcnvdflt, critalminh, dispactalms, mtplprst, mtplti, mtprsi, rptlnpmrss, rstrdev, or uimrd parameter cannot be specified. |
copy/init-ext-stats
|
The loc parameter cannot be specified in the same command with the sloc and eloc or bus parameters. |
|
|
The dpc, tidx, lsn, and rloc parameters cannot be specified together in the command. The dpc, tidx, lsn, and link parameters cannot be specified together in the command. The action=disp and tbl=rte parameters must be specified before the dpc parameter can be specified. The action=disp and tbl=ls parameters must be specified before the lsn parameter can be specified. The action=disp and tbl=lnk parameters must be specified before the link parameter can be specified. The action=disp parameter must be specified before the tidx parameter can be specified. The action=aud parameter must be specified before the audtype parameter can be specified. The action=disp and tbl=lnk or theaction=aud and audtype=uc parameters must be specified before the rloc parameter can be specified. if the action parameter has a value of wwa, stats, or rststat, then the loc parameter is the only other parameter that can be specified. |
|
|
The loc and src parameters cannot be specified together in the command. |
|
|
The acn and family parameters cannot be specified together in the command. If the cgssn parameter is specified, then the ecdssn parameter cannot be specified. If the cdssn parameter is specified, then the ecgssn parameter cannot be specified. If the saddr parameter is specified, then the ecgssn/ecdssn parameter cannot be specified. The specified GTT set must have a set type of
opcode
(see the
The specified GTT set must have a set type of cdssn before the cdssn parameter can be specified. The specified GTT set must have a set type of cgssn before the cgssn parameter can be specified. The specified GTT set must have a set type of cdgta or cggta before the gta parameter can be specified. The specified GTT set must have a set type of opc before the opc parameter can be specified. The specified GTT set must have a set type of cgpc before the cgpc parameter can be specified. The cgpc, cgssn, gta, opc, cdssn, and opcode parameters cannot be specified together in the command. If the xlat=none parameter is specified, then the ri, pc/pca/pci/pcn/pcn24, force, ssn, and ccgt parameters cannot be specified. If the cgssn and cdssn parameters are both specified in the same command (in any order), then only the value for the last of the two parameters specified is used during processing. If the opc or dpc parameter is specified, then the (e)gta, (e)cgssn, (e)cdssn, and opcode parameters cannot be specified. |
dlt-map
|
If the mrnset parameter is specified, then the all parameter cannot be specified. |
dlt-mrn
|
If the mapset parameter is specified, then the pc1, pc2, pc3, pc4, and all parameters cannot be specified. |
ent-card
|
The data parameter is not allowed when the APPL=DEIRHC parameter is specified. The sflog=yes parameter can be specified only when the type=ipsm and appl=ips parameters are specified. |
ent-ee-flt
|
If the appl = ip parameter is specified, then the atm and e1t1 parameters must not be specified. If the appl = atm parameter is specified, then the ip and e1t1 parameters must not be specified and the port parameter can only be a, b, or a1. If the appl = e1t1 parameter is specified, then the atm and ip parameters must not be specified. |
ent-enum-profsel
|
The ENTITYID parameter cannot be specified with the SDN or EDN parameters. |
ent-gta
|
The acn and family parameters cannot be specified together in the command. If the cgssn parameter is specified, then the ecdssn parameter cannot be specified. If the gta/egta parameter is specified, then the eaddr parameter cannot be specified. If the saddr parameter is specified, then the ecgssn/ecdssn parameter cannot be specified. If the opcode parameter is specified, then the eaddr/egta/ecgssn/ecdssn parameter cannot be specified. If the cgpc parameter is specified, then the eaddr/eaddr/egta/ecgssn/ecdssn parameter cannot be specified. If the ecgssn/ecdssn parameter is specified, then the eaddr/egta parameter cannot be specified. If the cdssn parameter is specified, then the ecgssn parameter cannot be specified. The specified GTT set must have a set type of
opcode
(see the
The specified GTT set must have a set type of cdssn before the cdssn parameter can be specified. The specified GTT set must have a set type of cgssn before the cgssn parameter can be specified. The specified GTT set must have a set type of cdgta or cggta before the gta parameter can be specified. The specified GTT set must have a set type of opc before the opc parameter can be specified. The specified GTT set must have a set type of cgpc before the cgpc parameter can be specified. The cgpc, cgssn, gta, opc, cdssn, and opcode parameters cannot be specified together in the command. If the cgssn and cdssn parameters are both specified in the same command (in any order), then only the value for the last of the two parameters specified is used during processing. If the xlat=none parameter is specified, then the ri, pc/pca/pci/pcn/pcn24/pcn16, force, ssn, and ccgt parameters cannot be specified. If the opc or dpc parameter is specified, then the (e)gta, (e)cgssn, (e)cdssn, eaddr, and opcode parameters cannot be specified. |
ent-gttact
|
A value of dup or fwd must be specified for the act parameter before the pc/pca/pci/pcn/pcn24/pcn16, cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16, ssn, ri, tt, mrnset, mapset, loopset, cgpcogmsg, cdgtmodid, or cggtmodid parameters can be specified and before a value of useicmsg can be specified for the on or off parameter. The act=tcaperr parameter must be specified before the atcaperr or itcaperr parameter can be specified. The act=udts parameter must be specified before the udtserr parameter can be specified. The act=fwd/sfthrot/scpval parameter must be specified before the defactid parameter can be specified. The Service Numbering Plan (snp), Service Nature of Address Indicator (snai), Service Name (srvcname), and Service Error Cause (srvcerr) parameters can be specified only when act is set to srvc. The threshold and bursts parameters can be specified only when act is set to sfthrot. The SCCP parameter (sprm), TCAP parameter (tprm) and number of digits to be matched (ndgt) parameters can be specified only when act is set to scpval. The scfaddr, hlraddr, tt, failactid and fwdgtt parameters can only be specified if action type is sfapp. |
ent/dlt/rtrv-gttact-path
|
The
acn and
family parameters cannot be specified
together in the command.
The scfaddr, hlraddr, tt, failactid and fwdgtt parameters can only be specified if action type is sfapp. |
ent/chg-lnp-serv
|
For the
If the value specified for the tt parameter is an alias, then the (n)tt, (n)serv, (n)ttn, and (n)dv parameters cannot be specified. If the value specified for the (n)serv parameter is associated with the class, lidb, cnam, isvm, wsmsc, udf1, udf2, udf3, or udf4 service, then a value of lnpqs, lrnqt, ain, in, wnp, or pcs cannot be specified for the (n)serv parameter. The (n)dfltact, (n)gttselid, and on/off=gttrqd parameters cannot be specified with the udf1, udf2, udf3, and udf4 LNP Services. |
ent/dlt/rtrv-pct
|
The ssn and cic parameters cannot be specified together in the command. |
ent-slk
|
The e1loc/t1loc or e1port/t1port parameters cannot be specified together in the command. |
ent/chg-srvsel
|
The (n)dfltact, (n)gttselid, on=gttrqd, and off=gttrqd parameters are supported for only the IDPR, TTR, MNP, GPORT, SMSMR, GFLEX, and INPMR services. |
|
|
The loc and card parameters are mutually exclusive. Only one of the following parameters can be specified in a single MSU trace request: lrn, tn, dn, entityid, imsi, imei, error. |
|
|
The type=fixed parameter must be specified before the prtngrp parameter can be specified. If the prtngrp parameter is specified, then the low=no parameter must be specified. |
|
|
The loc parameter must be specified with a value of 1113 or 1115 before the prtngrp parameter can be specified. |
|
|
The loc and sloc/eloc parameters cannot be specified together. The loc parameter or the sloc/eloc parameters must be specified. The gpl parameter must be specified if the sloc/eloc parameters are specified. The sloc and eloc parameters must be specified together. The value specified for the sloc parameter cannot be greater than the value specified for the eloc parameter. If the target card is an HMUX, HIPR, or HIPR2 MUX card, then both card locations specified in the sloc and eloc parameters must contain HMUX, HIPR, or HIPR2 MUX cards on the same IMT bus. The bus is implicit based on the specified location. Location xy09 specifies an HMUX, HIPR, or HIPR2 MUX A Bus, and location xy10 specifies an HMUX, HIPR, or HIPR2 MUX B Bus (x is the frame and y is the shelf). For example, sloc=1109:eloc=6109 specifies all HMUX, HIPR, or HIPR2 MUX cards on the A Bus only; sloc=1110:eloc=6110 specifies all HMUX, HIPR, or HIPR2 MUX cards on the B Bus only. HMUX, HIPR, or HIPR2 MUX cards from both the A bus and B bus cannot be flash downloaded simultaneously. If the target is HC Blade, and if the loc parameter is specified, then the gpl parameter must be specified. The GPL parameter cannot be specified when the mode=rplcebl or mode=cnvrtbit parameter is used with the E5-class card. The mode=cnvrtbit parameter must be specified with the loc, code, and bits parameter. Any other parameters like force, boot, initclk, and sloc/eloc cannot be specified when the mode=cnvrtbit parameter is specified. The mode=rplcebl parameter must be specified with the loc and bits parameter. Any other parameters like force, boot, initclk, code, and sloc/eloc cannot be specified when the mode= rplcebl parameter is specified. |
|
|
If the loc or port parameter is specified, then the stat parameter cannot be specified. |
|
|
The stat parameter cannot be specified with the dpc/dpca parameter in the command. |
|
|
The db and loc parameters cannot be specified at the same time. The display=except and display=version parameters cannot be specified with the db=gtt parameter. |
rept-stat-ddb
|
The display, list, and filter parameters cannot be specified together in the command. |
rept-stat-deir
|
The mode and loc parameters, the loc and peakreset parameters, and the DCNAME and peakresest parameters can be specified together. No other combination is allowed. |
rept-stat-enum
|
The PEAKRESET and LOC parameters can be specified together. No other combination is allowed. |
|
|
The display=all, gpl, or loc parameters cannot be specified together in this command. |
|
|
Only one of the history, peakreset, and tpscost parameters can be specified in the command. |
|
|
The stat and lsn parameters cannot be specified in this command. |
rept-stat-mfc
|
If the mode or reset parameter is specified, then the service parameter must be specified. The mode=stats and sample parameters must be specified together in the command. If a value of mtp3, snm, or inm is specified for the service parameter, then the mode=act parameter cannot be specified. |
rept-stat-rte
|
If the clrwrntx=all parameter is specified, then the wrnln and wrntx parameters cannot be specified.The pst and mode parameters cannot be specified together in the command. |
rept-stat-sccp
|
The data and loc parameters cannot be specified together; they are mutually exclusive. |
rept-stat-sflog
|
The peakreset and loc parameters cannot be specified together. |
|
|
The stat parameter and either the loc or port parameter cannot be specified in this command. |
rtrv-data-rtdb
|
The tn, lm, and npanxx parameters cannot be specified together in the command. |
|
|
The msar=only parameter cannot be specified with any other parameters in this command. More than one parameter cannot be specified in this command. The only exception is the prx, pctype, and pcst parameters can be specified together. If the prx parameter is specified, then the PPC feature must be turned on. The pctype or pcst parameters cannot be specified with any of the following parameters: aliasa/aliasi/alisan/alisa24, apc, dpc/dpca/dpci/dpcn/dpcn24, clli, ncai, ppc, spc/spca/spci/spcn/spcn24 in this command. |
rtrv-enum-prof
|
The PRN parameter cannot be specified with any other parameter. |
|
|
The acn and family parameters cannot be specified together in the command. If the cgssn parameter is specified, then the ecdssn parameter cannot be specified. If the cdssn parameter is specified, then the ecgssn parameter cannot be specified. The specified GTT set must have a set type of
opcode
(see the The specified GTT set must have a set type of cdssn before the cdssn parameter can be specified. The specified GTT set must have a set type of cgssn before the cgssn parameter can be specified. The specified GTT set must have a set type of cdgta or cggta before the gta parameter can be specified. The specified GTT set must have a set type of opc before the opc parameter can be specified. The specified GTT set must have a set type of cgpc before the cgpc parameter can be specified. The cgpc, cgssn, gta, opc, cdssn, and opcode parameters cannot be specified together in the command. If the cgssn and cdssn parameters are both specified in the same command (in any order), then only the value for the last of the two parameters specified is used during processing. If the xlat=none parameter is specified, then the pc/pca/pci/pcn/pcn24/pcn16, force, ssn, and ccgt parameters cannot be specified. If the opc or dpc parameter is specified, then the (e)gta, (e)cgssn, (e)cdssn, acn, pkgtype, family and opcode parameters cannot be specified. |
rtrv-gtmod
|
If the gtmodid parameter is specified, then only the on=refcnt parameter can be specified. |
rtrv-gttact
|
A value of dup or fwd must be specified for the act parameter before the pc/pca/pci/pcn/pcn24, cgpc/cgpca/cgpci/cgpcn/cgpcn24, ssn, ri, tt, mrnset, mapset, loopset, useicmsg, cgpc,cgpcogmsg, cdgtmodid or cggtmodid parameters can be specified. A value of dup, fwd, or scpval must be specified for the act parameter before a value of useicmsg can be specified for the on or off parameter. The act-tcaperr parameter must be specified before the atcaperr or itcaperr parameters can be specified The act=udts parameter must be specified before the udtserr parameter can be specified. The act=fwd/scpval/sfthrot parameter must be specified before the defactid parameter can be specified. The pc, ssn, ri, mrnset, mapset, loopset, cgpc, cgpcogmsg , defactid, tprm, and sprm parameters cannot be specified in the same command as the atcaperr, itcaperr , or udtserr parameters. Values of useicmsg and uimreqd cannot be specified for the on or off parameters in the same command. The pc, ssn, ri, tt, mrnset, mapset, loopset, useicmsg, cgpc, cgpcogmsg, or defactid parameters cannot be specified with the uimreqd, atcaperr, itcaperr, or udtserr parameters. If the actid parameter is specified, then the ri, pc, ssn, tt, mrnset, mapset, loopset, uimreqd, on, off, atcaperr, itcaperr, udtserr, act, useicmsg, cgpc, cgpcogmsg, defactid, cggtmodid, cdgtmodid, snp, snai, srvcerr, srvcname, sprm, and tprm parameters cannot be specified. The udtserr and srvcerr parameters cannot be specified in the same command as the atcaperr or itcaperr parameters. The pc, ri, ssn, mrnset, mapset, loopset, on/off=useicmsg, cdgtmodid, defactid, cgpc, cgpcogmsg, and cggtmodid parameters cannot be specified in the same command with the on/off=uimreqd, atcaperr, itcaperr, and udtserr parameters. The srvcname, snp, snai and srvcerr parameters can be specified only when act is set to srvc. The sprm and tprm parameters can be specified only when act is set to scpval. |
rtrv-gttaset
|
If the actsn parameter is specified, then the on=refcnt parameter is the only other optional parameter that can be specified. |
|
|
Only 1 optional parameter can be specified in this command, except for the combination of the slsocbit and slsrsb parameters. |
|
|
The pctype and pcst parameters cannot be specified in the same command with the destination point code, alias point code, secondary point code, clli, msar=only, and ncai parameters. |
|
|
Only one of the following parameters may be specified: cic, ilns, opc or si. |
|
|
The spc parameter cannot be specified with the cpc or cpctype parameter. |
|
|
No two optional parameters can be specified together except the following parameter sets {DISPLAY, FRM} and {GPL,VER}. |
|
|
If the action=stop parameter is specified, then the loopback, time, and force parameters cannot be specified. |
Recovery
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.
Caution:
Contact My Oracle Support before entering theformat-disk command. See
unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.132 E2156 Cmd Rej: Cannot allow terminal configured as type=none
The type=none parameter cannot be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.133 E2157 Cmd Rej: Source parameter invalid for upgrade action
If the src=usb or src=server parameter is specified, then the action=getrel parameter must be specified. If the src=fixed parameter is specified, then the action=getrel parameter cannot be specified.
Recovery
Re-enter the
act-upgrade command, specifying a
valid combination of parameters. Refer to the command description in
Commands User's Guide for assistance.
Caution:
It is strongly recommended that this command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.134 E2160 Cmd Rej: Measurements collect must be off
For the act-upgrade command, the Measurements Collection function must be turned off (chg-meas:collect=off) or the Measurements Platform feature must be turned on (chg-measopts:platformenable=on) before a value of convertoam, oamcomplete, or netcomplete can be specified for the action parameter.
Caution:
It is strongly recommended that this command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.For the copy-disk command, OAM measurements collection cannot be in progress when this command is entered.
format-disk command can be executed.
- Do not enter the
chg-measopts:collect=oncommand while theformat-diskcommand is in progress. This results in read and write errors, because the standby disk is not accessible. - Do not enter
format-diskuntil the 30 minute measurements processing or the midnight measurements processing has completed, because inhibiting measurements during these periods results in the loss of measurement data for the period being processed.
Recovery - act-upgrade command
- Determine the status of the Measurements Collection function. Enter the
rtrv-meas-schedcommand. - Determine the status of the Measurements Platform feature. Enter the
rtrv-measoptscommand. - Turn off the Measurements Collection function or turn on the Measurements Platform feature as necessary. Refer to the Database Administartion - Systems Management User's Guide for assistance.
- Re-enter the
act-upgradecommand that generated this error message.
Recovery - copy/format-disk commands
Contact My Oracle Support before entering the copy-disk or format-disk command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.135 E2161 Cmd Rej: Removable drive contains Eagle data (use FORCE=YES)
To format a drive that already contains EAGLE data, the force=yes parameter must be specified.
Recovery
2.2.136 E2162 Cmd Rej: USB drive contains Eagle data (use FORCE=YES)
Recovery
- Ensure that the plug-in flash drive is in the correct location. Refer to Database Administration - System Management User's Guide for assistance.
- Re-enter the
format-diskcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.Caution:
Contact My Oracle Support before entering theformat-diskcommand. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.137 E2163 Cmd Rej: CLLI used by STP
The value specified for the clli parameter cannot be the same as the CLLI that is assigned to the EAGLE.
Recovery
2.2.138 E2164 Cmd Rej: Fixed disk contains Eagle data (use FORCE=YES)
If the media to be formatted contains EAGLE data, then the force=yes parameter must be specified.
Recovery
Contact My Oracle Support before entering the copy-disk command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.139 E2165 Cmd Rej: Removable drive not inserted
For the disp-disk-dir command, a removable drive must be inserted in the location indicated by the loc or src parameter.
format-disk command, the force=yes parameter must be specified if the drive to be formatted is recognized as a system removable drive. Only drives that have a dms.cfg file are recognized as system removable drives. A removable drive must be inserted and provisioned before the type=meas or type=system parameter can be specified.
Caution:
Contact My Oracle Support before entering theformat-disk command.
For the tst-disk command, the removable media must be inserted in the corresponding USB port before loc=1113/1115:disk=remove/usb can be specified.
Recovery
2.2.140 E2166 Cmd Rej: Partial point codes are not allowed
If the Cluster Routing and Management Diversity (CRMD) feature is turned on, then a full point code must be entered. Table 2-2 describes the recovery procedures by command.
Table 2-2 Recovery Procedures for Error Message E2166
| Command | Recovery |
|---|---|
chg-sid
|
|
ent/chg-appl-rtkey
|
|
ent/dlt-rmt-appl
|
|
2.2.141 E2167 Cmd Rej: Point code matches a STP capability point code
For the chg-ppsopts command, the values specified for the pc/pca/pci/pcn parameter cannot be the same as the EAGLE capability point code.
For the ent/chg-ls command, the alias point codes cannot be the same as the EAGLE capability point code.
For the ent-rte command, the value specified for the dpc/dpca/dpci/dpcn/dpcn24 parameter cannot be the same as the EAGLE capability point code.
For the ent/dlt/rtrv-pct command, the values specified for the epc/epca/epci/epcn, filtpc/filtpca/filtpci/filtpcn, and realpc/realpca/realpci/realpcn parameters cannot be same as the EAGLE capability point code.
Recovery
2.2.142 E2168 Cmd Rej: Point code matches a STP point code
For the chg-ppsopts command, the value specified for the pc/pca/pci/pcn parameter cannot be the same as the point code of the system.
For the ent/chg-ls command, the value specified for the apc/apca/apci/apcn/apcn24 parameter cannot match the point code of the system.
For the ent-dstn and ent-rte commands, the value specified for the dpc/dpca/dpci/dpcn/dpcn24 parameter cannot match the point code of the system.
For the ent/dlt/rtrv-pct command, the values specified for the epc/epca/epci/epcn, filtpc/filtpca/filtpci/filtpcn, and realpc/realpca/realpci/realpcn parameters cannot be same as the STP point code.
Recovery
2.2.143 E2169 Cmd Rej: Point code out of range
The specified point code is outside of the valid range of values for the command parameter.
Recovery
Re-enter the command that generated this error message, specifying a valid point code value. Refer to the command description in Commands User's Guide for assistance.
2.2.144 E2170 Cmd Rej: SNMP host table entry not found for specified HOST/IPADDR
For the chg-snmp-host command, the specific IP address or hostname were not found in the SNMP Host table.
For the dlt-snmp-host command, the specific IP address or hostname were not found in the SNMP Host table.
Recovery
2.2.145 E2171 Cmd Rej: Failed reading level 2 timer set table
The Level 2 Timer Set table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.146 E2172 Cmd Rej: Command action is out of phase with expected procedure
For the act-upgrade command, the value specified for the action parameter must correspond to the upgrade phase of the system.
Caution:
It is strongly recommended that this command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.For the act-flash command, the card must be running an inactive GPL.
For the init-flash command the card cannot be running an inactive flash GPL.
Recovery - act-upgrade
- Display the phase of the upgrade process. Enter the
act-upgrade:action=dbstatuscommand.The phase of the upgrade process is shown in the header of the command output.
- Re-enter the
act-upgradecommand that generated this error message, specifying an action that corresponds to the upgrade phase. Refer to the command description in Commands User's Guide for a list of upgrade phases.
Recovery - act-flash
- Display the GPLs running on the cards installed in the system. Enter the
rept-stat-gplcommand.A plus sign (+) in the column between the RUNNING and APPROVED columns indicates an inactive GPL.
- If the GPL is inactive, re-enter the
act-flashcommand that generated this error message.Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - init-flash
2.2.147 E2173 Cmd Rej: Failed reading level 3 timer set table
The Level 3 Timer Set table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.148 E2174 Cmd Rej: May not modify both T20 and IT22 timers
The t20 and it22 parameters cannot be specified together in the command.
Recovery
Re-enter the chg-l3t command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.149 E2175 Cmd Rej: May not modify both T21 and IT23 timers
The t21 and it23 parameters cannot be specified together in the command.
Recovery
Re-enter the chg-13t command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.150 E2176 Cmd Rej: Invalid value for heartbeat interval
For the chg-snmp-host command, the heartbeat interval is not in range.
For the ent-snmp-host command, the heartbeat interval is not in range.
Recovery
Re-enter the command that generated this error message, specifying a valid heartbeat interval. Refer to the command description in Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.151 E2177 Cmd Rej: Destination parameter not supported
If the dest parameter is specified, then the action=backup parameter must be specified.
Recovery
Re-enter the chg-db command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.152 E2178 Cmd Rej: Source parameter not supported
If the src parameter is specified, then the action=restore parameter must be specified.
Recovery
Re-enter the chg-db command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.153 E2179 Cmd Rej: Current actv OAM db is not supported for this upgrade
Caution:
It is strongly recommended that this command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.Recovery
Enter the act-upgrade:action=dbstatus command to verify the version of the database on the active TDM. The version of the database is shown in the VERSION STATUS field.
Contact My Oracle Support for additional assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.154 E2180 Cmd Rej: Current stdby OAM db is not supported for this upgrade
Caution:
It is strongly recommended that this command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.Recovery
Enter the act-upgrade:action=dbstatus command to verify the version of the database on the standby TDM. The version of the database is shown in the VERSION STATUS field.
Contact My Oracle Support for additional assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.155 E2181 Cmd Rej: ANSI PC is identical to ANSI CPC
The specified ANSI point code (pca) cannot match the ANSI capability point code (cpca).
Recovery
2.2.156 E2182 Cmd Rej: Only one of NCPC/A, NCPCI, or NCPCN/N24 may be specified
Only one of the ncpc, ncpca, ncpci, ncpcn, or ncpcn24 parameters can be specified in the command.
Recovery
Re-enter the command that generated this error message specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.157 E2183 Cmd Rej: Capability point code is already being used
The value specified for the new STP capability point code (cpca, cpci, cpcn, cpcn24) cannot be the same as an existing STP capability point code.
Recovery
2.2.158 E2184 Cmd Rej: CLLI is already being used by a route
For the chg-sid command, the specified site CLLI code cannot be the same as an existing route destination CLLI code.
For the chg-dstn command, if the corresponding destination for the specified destination point code (DPC) is an adjacent signaling point (matched a Far End point code in its linkset entity set), the CLLI of the DPC cannot be assigned to any other destination address.
For the ent-dstn command, the value specified for the clli parameter cannot already exist in the Route table.
Recovery
2.2.159 E2185 Cmd Rej: Capability point code matches STP's own point code
The new STP capability point code cannot be the same as the STP destination point code.
Recovery
2.2.160 E2186 Cmd Rej: Capability point code already defined as a route DPC
The value specified for the cpc parameter cannot be already assigned as a route destination point code (DPC).
Recovery
2.2.161 E2187 Cmd Rej: International PC is identical to international CPC
The value specified for the pci parameter cannot be the same as the value specified for the cpci parameter.
Recovery
2.2.162 E2188 Cmd Rej: National PC is identical to national CPC
The value specified for the pcn parameter cannot be the same as the value specified for the cpcn parameter.
Recovery
2.2.163 E2189 Cmd Rej: Site point code is already being used
The value specified for the STP destination point code cannot be the same as an existing route DPC or CPC and cannot be the same type as an existing STP point code.
Recovery
2.2.164 E2190 Cmd Rej: Cannot delete STP self ID if a DPC of same type is defined
If the existing spare ITU-I or spare ITU-N point code is an STP destination point code, then the npci=none or npcn=none parameter (respectively) cannot be specified.
Recovery
2.2.165 E2191 Cmd Rej: Failed reading SLTM table
The Signaling Link Test Message (SLTM) table is corrupt or cannot be found.
Recovery
Re-enter the chg-slt command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.166 E2192 Cmd Rej: Pattern contains invalid characters
The value specified for the pattern parameter can contain only the characters 0 – 9, a – f, and A – F. The first two characters of the value cannot be numeric.
Recovery
Re-enter the chg-slt command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.167 E2193 Cmd Rej: Pattern has odd number of characters
The value specified for the pattern parameter must contain an even number of characters.
Recovery
Re-enter the chg-slt command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.168 E2194 Cmd Rej: SLTSET and ENABLED cannot be specified together
The sltset and enabled parameters cannot be specified together in the command.
Recovery
Re-enter the rtrv-slt command that generated this error message, specifying a valid combination of parameter. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.169 E2195 Cmd Rej: NCDPNPFX already exists in INPOPTS Table
The value specified for the ncdpnpfx parameter cannot already exist in the INPOPTS table.
Recovery
2.2.170 E2196 Cmd Rej: Failed reading the user identification table
The User Identification table is corrupt or cannot be found by the system.
Recovery
- Re-enter the command that generated this error message.
- Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.171 E2197 Cmd Rej: The specified user identification is already defined
The value specified for the nuid parameter or uid parameter cannot already exist in the database.
Recovery
2.2.172 E2198 Cmd Rej: The maximum number of users is already defined
The database can contain a maximum of 100 user IDs.
Recovery
2.2.173 E2199 Cmd Rej: The specified user identification is not defined
The value specified for the uid parameter must already exist in the database.
Recovery
- Display the user IDs in the database. Enter the
rtrv-usercommand. - 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 and to the Database Administration - System Management User's Guide for assistance.
2.2.174 E2200 Cmd Rej: Database maint. in progress - retry later
The command cannot be executed while a database maintenance operation is in progress.
Recovery
Wait for the database maintenance operation to finish, then re-enter the command.
2.2.175 E2201 Cmd Rej: Shelf location 1100 is reserved for the control shelf
The command was entered with the value 1100 for the loc parameter. Shelf 1100 is the control shelf and cannot be deleted from the database.
Recovery
2.2.176 E2202 Cmd Rej: Shelf location already equipped
The shelf specified by the loc parameter cannot already exist in the database.
Recovery
- Display the shelves in the database. Enter the
rtrv-shlfcommand. - Re-enter the
ent-shlfcommand that generated this erorr message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.177 E2203 Cmd Rej: All cards on shelf must be unequipped
Before a shelf can be removed from the database:
-
All affected SS7 signaling links and TCP/IP data links must be deactivated.
-
All signaling links and their routes assigned to cards in the affected shelf must be removed from the database.
-
All cards in the affected shelf must be removed from the database.
Note:
The control shelf (Shelf 1100) cannot be removed from the database.Recovery
2.2.178 E2204 Cmd Rej: Waiting for duplex mode in provisioning subsystem
An attempt was made to update a database immediately following a dual OAM boot, a switchover, or a database repair, and before the detection of an active standby. An active OAM waits for up to five minutes for an available standby before allowing database updates.
Recovery
2.2.179 E2205 Cmd Rej: Invalid destination application ID
A valid value must be specified for the da parameter.
Recovery
Re-enter the send-msg command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.180 E2206 Cmd Rej: Invalid originating application ID
A valid value must be specified for the oa parameter.
Recovery
Re-enter the send-msg command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.181 E2207 Cmd Rej: Location type cannot receive messages
The destination location specified by the loc parameter must be equipped to receive messages.
Recovery
2.2.182 E2208 Cmd Rej: ALL only qualifier allowed with given card type
If any GPL ID other than oamhc is specified, then the all Subsystem ID must be specified.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.183 E2209 Cmd Rej: Both DR and DA parameters cannot be entered
The da and dr parameters cannot be specified together in the command.
Recovery
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.
2.2.184 E2210 Cmd Rej: Byte, WORD or DWORD must be entered
The byte, word, or dword parameter must be specified.
Recovery
Re-enter the set-mem command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.185 E2211 Cmd Rej: Maximum number of CDPNPFXs already provisioned
A maximum of 40 Called Party Number Prefix values is allowed.
Recovery
2.2.186 E2212 Cmd Rej: Invalid card type for this command
The card that is specified cannot be used with this command.
Recovery
2.2.187 E2213 Cmd Rej: Missing parameter - BC
The bc parameter must be specified.
Recovery
Re-enter the disp-mem or ent-bp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.188 E2214 Cmd Rej: Missing parameter - CARD, LOC or IMT
The card, loc, or imt parameter must be specified. Only one of these parameters can be specified in the command.
Recovery
Re-enter the ent/disp/dlt-bp or set/disp-mem command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.189 E2215 Cmd Rej: Missing parameter - DA or DR
The dr or da parameter must be specified
Recovery
Re-enter the ent-bp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.190 E2216 Cmd Rej: CDPNPFX must not be NONE
The cdpnpfx=none parameter cannot be specified.
Recovery
Re-enter the chg-inpopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the INP/AINPQ User's Guide for assistance.
2.2.191 E2217 Cmd Rej: More than one of CARD, LOC and IMT specified
The card, loc, and imt parameters cannot be specified together in the command.
Recovery
Re-enter the ent/disp/dlt-bp or set/disp-mem command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.192 E2218 Cmd Rej: Only one of BYTE, WORD or DWORD may be entered
The byte, word, and dword parameters cannot be specified together in the command.
Recovery
Re-enter the set-mem command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.193 E2219 Cmd Rej: Specified BC exceeds max allowed (96)
The value specified for the bc parameter must be less than or equal to 96.
Recovery
Re-enter the ent-bp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.194 E2220 Cmd Rej: DLTPFX must not be specified, when NCDPNPFX is NONE
The dltpfx and ncdpnpfx=none parameters cannot be specified together in the command.
Recovery
Re-enter the chg-inpopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the INP/AINPQ User's Guide for assistance.
2.2.195 E2221 Cmd Rej: File transfer in progress
The command cannot be entered while another command is already in progress.
Recovery
Re-enter the command after the file transfer is complete.
2.2.196 E2222 Cmd Rej: CDPNPFX doesn't exist in INPOPTS Table
The value specified for the cdpnpfx parameter must already exist in the INPOPTS table.
Recovery
- Display the existing values for the cdpnpfx parameter. Enter the
rtrv-inpoptscommand. - Re-enter the
chg-inpoptscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the INP/AINPQ User's Guide for assistance.
2.2.197 E2223 Cmd Rej: Invalid drive specified
A valid hard drive must be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.198 E2224 Cmd Rej: Only one Source and Destination may be specified
The src and dest parameters can be specified only once in the command.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.199 E2225 Cmd Rej: STBL/DFILE or SFILE/DTBL must be specified
The src and dest parameters must be specified together in the command.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.200 E2226 Cmd Rej: CDPNNAI doesn’t exist in INPOPTS Table
If the chg-inpopts command is entered to delete a Called Party Number Nature of Address value from the INPOPTS table (for example, the cdpnnai=1 and ssnai=none parameters are specified), then the value for the cdpnnai parameter must already exist in the INPOPTS table.
Recovery
2.2.201 E2227 Cmd Rej: Maximum Number of CDPNNAIs already provisioned
A maximum of 5 Called Party Number Nature of Address values is allowed.
Recovery
2.2.202 E2228 Cmd Rej: Unknown copy direction
The source log and destination file combination is not allowed.
Recovery
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.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.203 E2229 Cmd Rej: Use DFILE when specifying STBL
If the stbl parameter is specified, then the dfile parameter must be specified.
Recovery
Re-enter the copy-fta 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.204 E2230 Cmd Rej: Use DTBL when specifying SFILE
If the dtbl parameter is specified, then the sfile parameter must be specified.
Recovery
Re-enter the copy-fta command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.205 E2231 Cmd Rej: Use SFILE when specifying DTBL
If the dtbl parameter is specified, then the sfile parameter must be specified.
Recovery
Re-enter the copy-fta command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.206 E2232 Cmd Rej: Use STBL when specifying DFILE
If the dfile parameter is specified, then the stbl parameter must be specified.
Recovery
Re-enter the copy-fta command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.207 E2233 Cmd Rej: May not specify Filename when ALL=YES
If the all=yes parameter is specified, then the filename parameter cannot be specified.
Recovery
Re-enter thedlt-fta command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.208 E2234 Cmd Rej: Must specify ALL=YES to delete all files
If the filename parameter is not specified, then the all=yes parameter must be specified.
Recovery
Re-enter the dlt-fta command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.209 E2235 Cmd Rej: Card location must be 1113 or 1115, or APPL=E(OAM)
If the initclk parameter is specified with the loc or appl parameter, then:
-
A value of 1113 or 1115 must be specified for the loc parameter
OR
- A value of oam or eoam just be specified for the appl parameter.
Recovery
Re-enter the init-card command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.210 E2236 Cmd Rej: Must specify GPL name and version
For the chg-gpl command, the appl and ver parameters must be specified together. If a value of emap or oap is specified for the appl parameter, then the ver parameter does not have to be specified.
For the rtrv-stp command, if the ver parameter is specified, then the appl parameter must be specified.
Recovery
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.
2.2.211 E2237 Cmd Rej: Card location must be 1114 or 1116
The value specified for the loc parameter must specify an E5-TDM card.
Recovery
2.2.212 E2238 Cmd Rej: The GPL type entered is not currently supported
The value specified for the gpl parameter must be supported.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command definition in the Commands User's Guide for assistance.
2.2.213 E2239 Cmd Rej: Data audit already in progress
The aud-data command cannot be entered while a previously entered aud-data command is running.
Recovery
Re-enter the aud-data command after the previously entered aud-data command finishes running.
2.2.214 E2241 Cmd Rej: No File Transfer Area on removable drive
For the copy-fta command, the removable drive has no File Transfer Area and cannot be used as the source or destination.
For the copy-seculog command, the removable drive has no File Transfer Area and cannot be used as the destination.
Recovery
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.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.215 E2242 Cmd Rej: Destination card invalid
The value specified for the loc parameter cannot indicate a fixed disk or removable drive.
Recovery
2.2.216 E2244 Cmd Rej: INIT=YES only valid with BID record
If the init=yes parameter is specified, then the value of the data parameter must be a Board IDentification (BID) record.
Recovery
Re-enter the chg-bip-rec 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.217 E2245 Cmd Rej: CDPNNAI and SNAI must be specified together
The cdpnnai and snai parameters must be specified together in the command.
Recovery
Re-enter the chg-inopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the INP/AINPQ User's Guide for assistance.
2.2.218 E2246 Cmd Rej: Command Class Management feature must be enabled
These commands or a configurable command class name are not allowed until the Command Class Management feature has been enabled.
Recovery
2.2.219 E2247 Cmd Rej: Bus parameter invalid
For the alw/conn/disc/inh/tst-imt command, an invalid IMT bus was entered. Valid IMT bus entries are A or B.
For the send-msg command, card locations xy09 and xy10 cannot be used with bus B and bus A, respectively.
Recovery
For the alw/conn/disc/inh/tst-imt command, specify a valid IMT bus entry.
For the send-msg command, specify bus=b:loc=xy10 to send a message to the HIPR or HIPR2 MUX card on IMT bus B, and bus=a:loc=xy09 to send a message to the HIPR or HIPR2 MUX card on IMT bus A.
Refer to the command description in Commands User's Guide for assistance. If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.220 E2251 Cmd Rej: Unable to communicate to command handler across IMT
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.221 E2252 Cmd Rej: Day out of range
The value specified for the day parameter must be in the range 01–31. The value must accurately reflect the number of days in the month indicated.
Recovery
Re-enter the rtrv-log, rtrv-seculog, or set-date command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.222 E2253 Cmd Rej: Echo is not set for this terminal
This command stops the echoing of output from a terminal to one or more terminals. Echoing is not set for this terminal.
Recovery
No action required.
2.2.223 E2254 Cmd Rej: Minutes out of range
When the mtpxlet parameter is specified, the value for minutes (mm) must be in the range 00-59.
Recovery
Re-enter the chg-stpopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.224 E2255 Cmd Rej: Month out of range
The system date month value (yymmdd, where yy is the year, mm is the month, and dd is the day) must be in the range 01 - 12.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.225 E2256 Cmd Rej: Terminal is currently inhibited
Terminal output cannot be echoed to a terminal that is inhibited.
Recovery
2.2.226 E2257 Cmd Rej: Terminal is currently out of service
For the act-echo command, terminal output cannot be echoed to a terminal that is out of service.
For the inh/rmv-trm command, only terminals that are in service can be placed out of service
Recovery
2.2.227 E2258 Cmd Rej: NMULTCC and MULTCC parameters must be entered together
The nmultcc and multcc parameters must be specified together in the command.
Recovery
Re-enter the chg-gsmopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the G-Port User's Guide for assistance.
2.2.228 E2259 Cmd Rej: Terminal already echoing to specified terminal
If a terminal is already echoing to a specified terminal, the act-echo command cannot be entered to echo the terminal's output to that same terminal.
Recovery
No action is necessary since the terminal’s output is already being echoed to the specified terminal.
2.2.230 E2261 Cmd Rej: Illegal attempt to delete yourself
The dlt-user command cannot be entered for the user ID of the user logged on the terminal where the command was issued.
Recovery
2.2.231 E2262 Cmd Rej: Password too long, 12 maximum
The password can contain a maximum of 12 alphanumeric characters.
Recovery
Re-enter the command that generated this error message, specifying a password that is less than or equal to 12 characters. Refer to the command description in Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.232 E2263 Cmd Rej: Password does not contain enough characters
The password must contain at least the number of characters specified by the minlin parameter in the chg-secu-dflt command, and no more than 12 alphanumeric characters.
Recovery - login command
Re-enter the command, specifying a larger number of alphanumeric characters. No more than 12 characters can be specified. Refer to the Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
Recovery - chg-pid command
2.2.233 E2264 Cmd Rej: Password verification failed
The value entered for the password verification must match the value entered for the password.
Recovery
Re-enter the chg-pid command. When prompted, specify matching values for the password and password verification.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.234 E2265 Cmd Rej: User currently logged on
If a user is logged on to the system, then changes cannot be made to that user's ID.
Recovery
- Display the users logged on the system. Enter the
rept-stat-usercommand. - Re-enter the
chg-usercommand that generated this error message when the user is not logged on.
2.2.235 E2266 Cmd Rej: Class name is not an existing configurable command class
The arguments specified by the Configurable Command Class names (parameters CC1 to CC8) must be set to default or provisioned to configurable command class names.
Recovery
2.2.236 E2267 Cmd Rej: Init-sys already in progress at another terminal
If an init-sys command is already processing on another port, then another init-sys command cannot be entered.
Recovery
Re-enter the init-sys command that generated this error message after the system finishes initializing.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.237 E2268 Cmd Rej: SNMP feature must be enabled
For the chg-snmp-host command, the SNMP feature must be enabled before SNMP host can be changed.
For the ent-snmp-host command, the SNMP feature must be enabled before SNMP host can be entered.
For the dlt-snmp-host command, the SNMP feature must be enabled before SNMP host can be deleted.
For the chg-snmpopts command, the SNMP feature must be enabled before SNMP options changed.
Recovery
2.2.238 E2269 Cmd Rej: Unable to communicate with card at location
For the disp-disk-dir, disp-tbl, init-imt-gpl, set-lba, or set-tbl command, a keyboarding or hardware error may have occurred.
For the disp-disk-dir command, the card must be connected to at least one IMT bus.
Recovery
2.2.239 E2270 Cmd Rej: Card does not exist or is not an LPE
The card specified by the loc parameter cannot be found in the database or is not allowed by the command. The MUX, E5-TDM, and E5-MDAL cards cannot be initialized by the init-card command.
Recovery
2.2.240 E2271 Cmd Rej: Either LOC or APPL (not both) must be specified
Either the loc or appl parameter, but not both, must be specified in the command.
Recovery
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.
2.2.241 E2272 Cmd Rej: Invalid GPL type for this command
For the alw/rst-card and init-imt-gpl commands, a valid value must be specified or the code parameter or an invalid appl parameter.
For the init-card command, if the serial parameter is specified, then a value of atmansi, ccs7itu, gls, sccp,
ss7ansi, ss7gx25, or all must be specified for the appl
parameter.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.242 E2273 Cmd Rej: Seconds out of range
The value specified for the seconds component in the time, stime, or etime parameter must be in the range 00–59.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.243 E2274 Cmd Rej: TT must be specified when ENTTYPE=TT
If the enttype=tt parameter is specified, then the tt parameter must be specified.
Recovery
Re-enter the rept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.244 E2275 Cmd Rej: Day-to-hour measurement data not yet collected
The time that the command was entered to specify a measurement report for day-to-hour measurements (type=avldth or type=mtcdth) was between midnight (00:00) and 59 minutes past midnight (00:59). Day-to-hour measurement collection starts at midnight and are updated on an hourly basis. A day-to-hour measurement report cannot be generated before the first hour of measurements have been collected.
Recovery
Wait until after 1:00 AM (01:00) and re-enter the rept-ftp-meas or rept-meas command that generated this error message. Refer to the command description in Commands User's Guide for assistance.
2.2.245 E2276 Cmd Rej: Day-to-hour measurement collection in progress
If day-to-hour collection and report processing is in progress, then the type=mtcd and type=mtcdth parameters cannot be specified.
Recovery
Re-enter the rept-ftp-meas or rept-meas command that generated this error message after collection is complete. (The prior period is no longer accessible). Refer to the command description in Commands User's Guide for assistance.
2.2.246 E2277 Cmd Rej: Daily measurement collection in progress
If daily collection and report processing is in progress, then the type=mtcd and type=avid parameters cannot be specified.
Recovery
Re-enter the rept-ftp-meas or rept-meas command that generated this error message after routine collection is complete. Refer to the command description in Commands User's Guide for assistance.
2.2.247 E2278 Cmd Rej: 30-minute measurement collection in progress
Note:
Refer the Measurements Reference for assistance with the recovery procedures.For the chg-ctrl-feat command, if 30 minute measurements collection is in progress, then the 15 Minute Measurements feature cannot be turned on.
For the chg-measopts command, if 30 minute measurements collection is in progress, then the collect15min=on parameter cannot be specified.
For the rept-ftp-meas command, if 30 minute measurements collection is in progress, then a value of comp, systot, avl, or gtwy cannot be specified for the type parameter.
For the rept-meas command, if 30 minute measurements collection is in progress, then a value of systot, comp, or avl cannot be specified for the type parameter.
Recovery - rept-ftp-meas
To get a report before routine collection starts, do one of the following actions:
-
Enter the command, specifying the period=last parameter.
OR
-
Enter the command without specifying the period parameter.
Recovery - all commands
Note:
The prior period is no longer available.Contact My Oracle Support if this error message appears again.
2.2.248 E2279 Cmd Rej: 5-minute measurement collection in progress
If 5-minute collection and report processing is in progress, then the type=nm parameter cannot be specified.
Recovery
Re-enter the rept-ftp-meas or rept-meas command that generated this error message after the 15-minute measurement collection is complete. (The prior period is no longer accessible). Refer to the command description in Commands User's Guide for assistance.
2.2.249 E2280 Cmd Rej: Invalid PERIOD for this TYPE
A valid combination of the period and type parameters must be specified. Refer to the command description in Commands User's Guide for valid parameter combinations.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Measurements Reference for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.250 E2281 Cmd Rej: Invalid ENTTYPE for this TYPE
An invalid parameter combination has been entered.
Recovery
Re-enter the rept-meas or rept-ftp-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Measurements Reference for assistance.
2.2.251 E2282 Cmd Rej: Unknown ENTTYPE
The component specified is not valid. It has to be one of the AVL, AVLD, COMP, GTWY, MTCD, MTCS, NM, SYSTOT, or RBASE parameters.
Recovery
Re-enter the
rept-meas command that generated this
error message, specifying a valid combination of parameters. Refer to the
command description in
Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.252 E2283 Cmd Rej: QH, HH, or DAY cannot be specified when PERIOD=LAST
If the period=last parameter is specified, then the hh, qh, and day parameters cannot be specified.
Recovery
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.
2.2.253 E2284 Cmd Rej: QH, HH, or DAY cannot be specified when PERIOD=ACTIVE
If the period=active parameter is specified, then the hh, qh, and day parameters cannot be specified.
Recovery
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.
2.2.254 E2285 Cmd Rej: QH, HH, or DAY cannot be specified when PERIOD=ALL
If the period=all parameter is specified, then the hh, qh, and day parameters cannot be specified.
Recovery
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.
2.2.255 E2286 Cmd Rej: QH or HH must be specified when PERIOD=SPECIFIC
If the period=specific parameter is specified, then the hh or qh parameter must be specified.
Recovery
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.
2.2.256 E2287 Cmd Rej: ACTIVE not available for type-enttype combination
If the enttype=stp or enttype=tt parameter is specified, then the period=active parameter cannot be specified.
Recovery
Re-enter the command that generated this error message specifiying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.257 E2288 Cmd Rej: Either LSN or LOC and LINK must be specified
If the enttype=link parameter is specified, then the loc and link/port parameters or the lsn parameter must be specified.
Recovery
Re-enter the rept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Measurements Reference for assistance.
2.2.258 E2289 Cmd Rej: LOC and LINK must be specified when PERIOD=ALL
If the type=avl and period=all parameters are specified, then the loc and link/port parameters must be specified.
Recovery
Re-enter the rept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Measurements Reference for assistance.
2.2.259 E2290 Cmd Rej: Hourly measurement collection in progress
If hourly collection and report processing is in progress, then the type=mtch parameter cannot be specified.
Recovery
Re-enter the rept-meas or rept-ftp-meas command that generated thsi error message after collection is complete. (The prior period is no longer accessible).
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.260 E2291 Cmd Rej: PERIOD must be 1 hour boundary for report type
If the period=specific parameter is specified, then the final two digits of the hh or qh parameter must be 00. Day-to-hour measurement collection starts at midnight and is updated on an hourly basis.
Recovery
Re-enter the rept-ftp-meas command that generated this error message specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Measurements Reference for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.261 E2292 Cmd Rej: Card does not exist or is not a LIM (LOC)
The card specified by the loc parameter cannot be found in the database, or is not a LIM card.
The LIMATM, LIME1ATM, LIME1, LIMT1, and DCM card types are the only valid card types for the command. The card must be an E5-ATM, E5-ATM-B, E5-E1T1, E5-E1T1-B, E5-ENET, E5-ENET-B, HC-MIM, or SLIC card.
Recovery
2.2.262 E2294 Cmd Rej: LSN and LOC parms are mutually exclusive
The loc and lsn parameters cannot be specified together in the command.
Recovery
Re-enter the rept-meas or rept-stat-iptps command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.263 E2295 Cmd Rej: LSN and LINK parms are mutually exclusive
The lsn and link parameters cannot be specified together in the command.
Recovery
Re-enter the rept-meas command that generated this error message specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Measurements Reference for assistance.
2.2.264 E2296 Cmd Rej: Both LOC and LINK must be specified
If the link parameter is specified, then the loc parameter must be specified.
Recovery
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.
2.2.265 E2297 Cmd Rej: TT parameter valid only when ENTTYPE=TT
The enttype=tt parameter must be specified before the tt parameter can be specified. If the enttype=tt parameter is specified, then the tt parameter must be specified.
Recovery
Re-enter the command, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.266 E2298 Cmd Rej: LOC parameter not valid for this ENTTYPE
The values specified for the loc and enttype parameters must correspond. Refer to the command description in Commands User's Guide for a list of corresponding loc and enttype values.
Recovery
Re-enter the rept-meas command that generated this error message, specifying a valid combination of parameters.
2.2.267 E2299 Cmd Rej: LINK parameter valid only when ENTTYPE=LINK
The enttype=link parameter must be specified before the link parameter can be specified.
Recovery
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.
2.2.268 E2300 Cmd Rej: LSN must be specified
If the type=gtwy parameter is specified, and a value of lsdestni, lsonismt, or lsorigni is specified for the enttype parameter for an ITU linkset, then only the lsn parameter can be specified.
Recovery
Re-enter the rept-meas 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.269 E2301 Cmd Rej: LSN parameter not valid for type-enttype combination
If the type=systot parameter is specified, or if a value of idpr, origni, origninc, stp, or tt is specified for the enttype parameter, then the lsn parameter cannot be specified.
Recovery
Re-enter the rept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.270 E2302 Cmd Rej: PERIOD must be 1/2 hour boundary
If a value of avl, avld, comp, gtwy, mtcd, or systot is specified for the type parameter, then the value specified for the hh parameter must indicate a half-hour boundary (the end of the requested half-hour for the report).
If the type=mtch parameter is specified, then the value specified for the hh parameter must indicate an hourly boundary (half hours ending in 00, such as 0100, etc).
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.271 E2303 Cmd Rej: Unknown LSN
For the rept-stat-iptps command, the linkset name specified by the lsn parameter must already exist in the database.
For the dbg-ddb command, the linkset specified by the lsn parameter must already exist in the Linkset table.
Recovery
- Display the existing linksets. Enter the
rtrv-lscommand. - Re-enter the command that generated this error message, specifying an existing linkset. Refer to the command description in Commands User's Guide for assistance.
2.2.272 E2304 Cmd Rej: Invalid TYPE
For the rept-meas command, a valid combination of the type and enttype parameters must be specified.
For the rept-stat-lnp command, the only valid value for the card parameter is sccp-all.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.273 E2305 Cmd Rej: On demand report currently being printed
Only one instance of the command can be running at a time.
Recovery
Re-enter the rept-ftp-meas or rept-meas command that generated this error message after the process that is currently running is complete.
2.2.274 E2306 Cmd Rej: NZO is not valid for this TYPE
A value of avl, alvd, or avldh must be specified for the type parameter before the nzo=yes parameter can be specified.
Recovery
Re-enter the rept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Measurements Reference for assistance.
2.2.275 E2307 Cmd Rej: QH or HH is not valid for this TYPE
If a value of avld, mtcd, nm, rbase, or mtcs is specified for the type parameter, then the hh and qh parameters cannot be specified.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.276 E2309 Cmd Rej: NI required
If the nc parameter is specified for enttype=origninc reports, then the ni parameter must be specified.
Recovery
Re-enter the rept-meas 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.277 E2310 Cmd Rej: File already exists
The file being loaded cannot have a name that matches a file that is already in the database.
Recovery
Re-enter the command that generated this error message, specifying the correct file name.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.278 E2311 Cmd Rej: Disk read/config error
Recovery
Re-enter the command that generated this error message.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.279 E2314 Cmd Rej: Invalid filename entered
For the act-upgrade command, the value specified for the release parameter must be at least 11 characters in length and contain a hyphen (-). The format of the value must be xx.xx.xx-yy.yy.yy, where xx.xx.xx is the release number and yy.yy.yy is the engineering build number.
For the chg-db command, the value specified for the file parameter must have the correct extension.
For the chg-tbl command, valid filenames must be in the format filename.extension, with the following requirement:
- File name is 1-8 ASCII characters
For the copy-fta command, file name formats are limited to 8 + 3 DOS-compatible characters.
For the disp-disk-dir command, valid filenames must be in the format filename.extension, with the following requirements:
- File name is 1-8 ASCII characters
- Extension is 0-3 ASCII characters
Wildcards (asterisks) are allowed when the wildcard pattern is enclosed in parentheses:
- *
- Matches all characters in either filename or extension
- ?
- Matches one character in either filename or extension
- file="*.*"
- Matches all files on disk
- file="*.tbl"
- Matches all files on disk with .tbl as the extension
Recovery
Re-enter the command that generated this error message, specifying a valid filename and extension. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.280 E2315 Cmd Rej: Either HOST or IPADDR must be specified, but not both
For the chg-snmp-host command, the target host must be identified either by the IP address or by the hostname, when changing the configuration for an SNMP host.
dlt-snmp-host command, the target host must be identified either by the IP address or by the hostname, when deleting the configuration for an SNMP host.
Note:
Both parameters may not be specified in the same command.Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.281 E2316 Cmd Rej: Class name is not an existing command class name
The argument specified by the class parameter must be a valid configurable or non-configurable command class name.
Recovery
2.2.282 E2317 Cmd Rej: Invalid table Id
For the aud-data command the table specified by the tblid parameter must already exist.
chg-tbl command, the value specified for the id parameter must already exist.
Note:
Before entering thechg-tbl command, contact My Oracle Support.
Recovery
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.283 E2318 Cmd Rej: Invalid file length
A valid value must be specified for the filelength parameter.
Recovery
Contact My Oracle Support before entering the chg-tbl command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.284 E2319 Cmd Rej: New class name cannot be the same as an existing class name
The value specified for the nclass parameter cannot be the same as an existing class name.
Recovery
2.2.285 E2320 Cmd Rej: TYPE can only be set to TELNET, SEAS, EMSALM or NONE
For terminals 17 -40, the value of the type parameter must be telnet, emsalm, seas, or none.
The type=emsalm parameter can be specified for terminal numbers from 1 - 16.
Recovery
Re-enter the chg-trm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.286 E2321 Cmd Rej: Communication Settings are not allowed on TELNET terminals
If the value specified for the trm parameter is 17 or above, or if the type=telnet parameter is specified, then the communication settings cannot be specified.
Recovery
Re-enter the chg-trm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.287 E2322 Cmd Rej: Alias defined as a destination point code
The value specified for the alias parameter cannot already exist as a destination point code, a site point code, or a capability point code.
Recovery
2.2.288 E2323 Cmd Rej: Terminals 1-16 cannot be set to TYPE=TELNET
If a value from 1 - 16 is specified for the trm parmaeter, then the type=telnet parameter cannot be specified.
Recovery
Re-enter the chg-trm command that generated this error message specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.290 E2325 Cmd Rej: Alias type matches DPC type
The alias parameter must be specified with a different point code type than the dpc parameter. A specified alias type cannot already be defined as a destination address.
The aliasa and dpca parameters cannot be specified together in the command. The aliasi and dpci parameters and the aliasn and dpcn parameters cannot be specified together in the command if the prefix subfields are the same (both are spare or both are non-spare).
Recovery
2.2.291 E2326 Cmd Rej: APC not defined as destination point code
The value specified for the adjacent point code must already be defined in the Destination Point Code table.
Recovery
2.2.292 E2327 Cmd Rej: Invalid value for port parameter
For the chg-snmp-host command, the value specified for the cmdport / trapport parameter is not within range for the command.
For the ent-snmp-host command, the value specified for the cmdport / trapport parameter is not within range for the command.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.293 E2328 Cmd Rej: CLLI not defined in route table
The value specified for the clli parameter must already be defined in the Route table.
Recovery
2.2.294 E2329 Cmd Rej: IPSM card not equipped
If a value of telnet, seas, or emsalm, is specified for the type parameter and a Telnet terminal is used (IDs 17-40), then a type IPSM card must be equipped in the system. Parameters for a telnet type terminal cannot be changed unless an IPSM card is used as the target terminal.
Recovery
2.2.295 E2330 Cmd Rej: TIF Selective Screening feature must be enabled
For the chg-npp-srs command, the TIF Selective Screening feature must be enabled before an AS containing the SELSCR Service Action can be specified as a value for the asn parameter.
For the ent-npp-srs command, the TIF Selective Screening feature must be enabled before an AS containing the SELSCR Service Action can be specified as a value for the asn parameter.
Recovery
2.2.296 E2331 Cmd Rej: Cannot specify LSN parameter with ALL=YES
The lsn and all=yes parameters cannot be specified together in the command.
Recovery
Re-enter the dlt-rte command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.297 E2332 Cmd Rej: Point code defined as an alias
The value specified for the destination point code parameter cannot already exist as an alias point code.
Recovery
2.2.298 E2333 Cmd Rej: DPC is already being used
The value specified for the Destination Point Code cannot already exist in the database.
Recovery
2.2.299 E2334 Cmd Rej: DPC defined as linkset APC or SAPC
The specified destination point code cannot already be defined as an adjacent point code or a secondary adjacent point code.
Recovery
2.2.300 E2335 Cmd Rej: CLLI is not identical to that of matching Destination
The value specified for the clli parameter must match the value of the clli parameter specified for for the destination.
Recovery
2.2.301 E2336 Cmd Rej: GWSA, GWSM, GWSD are invalid without SCRSET specified
If the gwsa=on, gwsm=on, or gwsd=on parameters are specified, then the scrn parameter must be specified.
Recovery
Re-enter the ent/chg-ls command that generated this error message specifying a valid combination of parameters. Refer to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.302 E2337 Cmd Rej: If GWSA=OFF then GWSD must also be OFF
The gwsd=on parameter can be specified only if the gwsa=on parameter is specified. If the gwsd=on parameter is specified, then the gwsa=on parameter must be specified.
Recovery
Re-enter the ent/chg-ls command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - SS7 User's Guide (for SS7 linksets) or the Database Administration - IP7 User's Guide (for IP linksets) for assistance.
2.2.303 E2338 Cmd Rej: Invalid CLLI
A valid value must be specified for the to the clli parameter.
Recovery
Re-enter the ent/rtrv-dstn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.304 E2339 Cmd Rej: PC/CLLI does not match current PC/CLLI of the STP
A valid value must be specified for the point code and clli parameters.
Recovery
Re-enter the ent/rtrv-dstn command that generated this error message specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.305 E2340 Cmd Rej: Invalid point code
For the chg/rtrv-sid command, a value of none cannot be specified for the cpc, cpca, cpci, cpcn, and cpcn24 parameters.
For the dlt-dstn command, the specified point code must already exist in the database.
For the ent-dstn command, the value specified for the point code parameter must be a valid point code.
The point code 0-0-0 cannot be specified.
2.2.306 E2341 Cmd Rej: May not change adjacent point code type
The value specified for the new adjacent point code (APC) must have the same point code type as the current APC of the linkset.
Recovery
2.2.307 E2342 Cmd Rej: Links assigned to linkset
For the chg-ls command, if the IPSG linkset contains links, then the adapter parameter cannot be specified.
For the dlt-ls command, all links associated with the linkset must be deleted before the linkset can be deleted.
Recovery
2.2.308 E2343 Cmd Rej: Linkset APC/SAPC is already being used
The specified adjacent point code (APC) or secondary adjacent point code (SAPC) cannot already be assigned to another linkset.
Recovery
2.2.309 E2345 Cmd Rej: Linkset already defined
The specified linkset cannot already exist in the database.
Recovery
- Display the linksets in the database. Enter the
rtrv-lscommand. - Re-enter the
ent/chg-lscommand that generated this error message, specifying a linkset name that does not already exist.
2.2.310 E2346 Cmd Rej: Linkset not defined
Recovery
- Display the linksets in the database. Enter the
rtrv-lscommand. - Re-enter the command that generated this error message, specifying an existing linkset name.
2.2.311 E2347 Cmd Rej: Linkset table full
The Linkset table already contains the maximum 1024 linksets.
Recovery
2.2.312 E2348 Cmd Rej: Linkset referenced by destination historic route
If the linkset is referenced by the historic routeset of any destination, then the linkset cannot be deleted.
Recovery
2.2.313 E2349 Cmd Rej: Linkset Type for Network/Cluster route can't be A or E
If the specified destination address is a network address (ni-*-*), or network cluster address (ni-nc-*), the linkset type (see the chg-ls command) used in the route must be b, c, or d.
Recovery
2.2.314 E2350 Cmd Rej: At most two linksets can be assigned same cost
The 6-Way Loadsharing on Routesets feature must be turned on before more than 2 routes can be provisioned with the same relative cost.
Recovery
2.2.315 E2351 Cmd Rej: Linkset not assigned in route table
The linkset specified by the lsn parameter must already exist in the routeset of the destination table entry.
Recovery
2.2.316 E2352 Cmd Rej: SA SELSCR is mutually exclusive with TIF NS SAs
For the chg-npp-srs command, the TIF Number Substitution Service Action can not be specified in the AS, if the AS contains the SELSCR Service Action.
For the ent-npp-srs command, the TIF Number Substitution Service Action can not be specified in the AS, if the AS contains the SELSCR Service Action.
Recovery
2.2.318 E2354 Cmd Rej: Routeset must be empty
If any routes are assigned to the destination point code (DPC), then the DPC cannot be deleted.
Recovery
2.2.319 E2355 Cmd Rej: Linkset already assigned to route
The specified linkset is already in the specified route. A linkset can be entered only once as a route for each destination or for a routeset.
Recovery
2.2.320 E2356 Cmd Rej: Last route to DPC in use by GTT
The last route cannot be removed if the destination point codes associated are referenced by GTT.
Recovery
2.2.321 E2357 Cmd Rej: Linkset is unequipped
The value specifeid for the lsn parameter must already exist in the Linkset table and must be equipped.
Recovery
- Display the linksets in the database. Enter the
rtrv-lscommand. - Re-enter
ent/chg/dlt/rtrv-rtecommand that generated this error message, specifying a valid combination of parameters. Refer to command description in Commands User's Guide, the Database Administration - SS7 User's Guide, or the Database Administration - IP7 User's Guide for assistance.
2.2.322 E2358 Cmd Rej: Routeset is empty
If the all=yes parameter is specified, then at least one route must be assigned to the routeset.
Recovery
2.2.324 E2361 Cmd Rej: Screen set name not defined
The value specified for the scrn parameter must already exist in the database.
Recovery
2.2.325 E2363 Cmd Rej: SA SELSCR SA(X)VAL values must be none or between 0-127
If the AS specified by the asn parameter contains the SELSCR Service Action, then the two numerical values specified by the numerical values list must each be between 0-127 or none.
Recovery
2.2.326 E2364 Cmd Rej: TELNET cannot be specified unless the IPSM card is equipped
At least one type IPSM card must be equipped before the value specified for the trm parameter can refer to a Telnet or EMSALM terminal.
Recovery
2.2.327 E2365 Cmd Rej: TELNET Feature must be activated first
The Telnet (IP User Interface) feature must be enabled and turned on before the type=telnet parameter can be specified.
For the rtrv-trm command, the IP User Interface feature must be enabled before terminal ports 17 through 40 can be specified for the trm parameter.
Recovery
2.2.328 E2366 Cmd Rej: LOC must be specified
For the inh/unhb-alm commands, if a value of card or dlk is specified for the dev parameter, then the loc parameter must be specified.
For the rept-meas command, if the enttype=sctpcard parameter is specified, then the loc parameter must be specified.
For the rept-stat-card command, if the mode parameter is specified, then the loc parameter must be specified.
For the rept-stat-enum command, if the peakreset parameter is specified, then the loc parameter must be specified.
For the rept-stat-iptps command, if the link parameter is specified, then the loc parameter must be specified.
For the rept-stat-j1 command, if the j1port parameter is specified, then the loc parameter must be specified.
Recovery
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.
2.2.329 E2367 Cmd Rej: May not specify both LOC and STAT
The loc and stat parameters cannot be specified together in the command.
Recovery
Re-enter the rept-stat-card command that generated this error message specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.330 E2368 Cmd Rej: System busy - try again later
The command cannot be entered because another process is occuring. Table 2-3 shows the conditions and recovery procedures for the various commands that can generate this error message.
Table 2-3 Commands that cannot be entered because another process is running
| Commands | Issue and Recovery |
|---|---|
act/dact-ip-lnk |
No other action command can be in progress when this command is entered. Re-enter the command after all other action commands have completed. |
canc-cmd:trm=
|
The command was entered on the same terminal that is running the command to be canceled.
|
rept-stat-xxxx |
No other Wait for all |
tst-imt
|
A related IMT command cannot be in progress. Only one Fault Isolation Test or Extended Bit Rate Extenstion Test (BERT) can be active at a time. An Extended BERT cannot be performed if the Wait for all of the above commands or tests to complete, then re-enter the |
| all other commands using this error |
Heavy disk activity (e.g. database maintenance or measurement collection) may prevent access to the system. Action commands (used to change the state of entities within the system) cannot execute because another action command is in progress. For more information on action commands, refer to the Commands User's Guide.
|
2.2.331 E2369 Cmd Rej: Partition specified invalid for target disk
tst-disk command cannot be entered to test a disk partition that does not exist on the target disk.
A value of 1, 2, 3, 4, or all cannot be specified for the partition parameter to test a disk which has been formatted but does not contain a DOS directory structure (see the copy-disk command).
Note:
The partition=disk parameter can be specified in this situation, as this tests the entire disk and does not care about individual partitions. The partition=disk parameter is used only by Oracle for debug purposes.Recovery
Re-enter the tst-disk command specifying a valid partition parameter value for the disk being tested.
OR
Re-enter the tst-disk command to test the disk.
copy-disk command to create the DOS directory structure of the target disk.
Caution:
Contact My Oracle Support before entering theformat-disk command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Refer to Database Administration - System Management User's Guide for information about formatting and copying a TDM disk.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.332 E2370 Cmd Rej: Terminal Id not entered
The trm parameter must be specified.
Recovery
Re-enter the rst-trm command that generated this error message specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.333 E2371 Cmd Rej: Force parameter required
For the chg-db command, the force=yes parameter must be specified before the action=canceled parameter can be specified.
For the inh-alm command, the force=yes parameter must be specified to inhibit critical alarms.
inh-card command, the force=yes parameter must be specified to:
- inhibit the only remaining MCPM or LIM card
- inhibit a card where the result is a loss of service or where the service is not presently active
- inhibit a Service Module card if the inhibition would cause less than 80% of the in-service normal (IS-NR) LIM cards to have VSCCP service.
- inhibit a card when the card is the only remaining GLS card and the Integrated GLS feature is turned off
For the inh-trm command, the force=yes parameter must be specified to inhibit the last OAP port.
For the init-mux command, if one or more cards are not aligned on the alternate bus, the alternate IMT state will become IS-ANR. If the alternate bus is IS-ANR, then the force=yes parameter must be specified.
For the init-network command, the force=yes parameter must be specified to reset all network cards and override the required four card SS7ANSI or CCS7ITU configuration.
For the rmv-card command, the force=yes parameter must be specified to force the last GLS (if the Integrated GLS feature is not turned on) or the last SCCP card out of service.
For the set-uim-acthresh command the force=yes parameter must be specified to Set the limit=0 parameter for a given interval. Specifying this parameter turns off all occurrences of a specified UIM
Recovery
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.334 E2372 Cmd Rej: Terminal is not equipped
The value specified by the trm parameter must be equipped.
Recovery
2.2.335 E2373 Cmd Rej: Link is unequipped in the database
The entity or link specified by the loc and link parameters must exist in the database and must be equipped. For commands specifying the dev=slk or dev=dlk parameters, the specified link must exist in the database.
Recovery
2.2.336 E2374 Cmd Rej: SCCP Subsystem not Configured
At least one Service Module card running the VSCCP application or a GTT-enabled IPSG card must be configured in the system before the command can be entered.
Recovery
2.2.337 E2375 Cmd Rej: Unknown command
The entered command is invalid.
Recovery
Re-enter the command. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.338 E2376 Cmd Rej: Specified LOC is invalid
The value specified for the loc parameter must be valid for the card type and application. Refer to the command description in Commands User's Guide for valid card types and applications.
Recovery
2.2.339 E2377 Cmd Rej: No test link message is sent
The tst-slk command cannot be entered while another action command is in progress.
The value specified for the loc parameter must indicate a LIM card.
Recovery
- Display the cards in the database. Enter the
rtrv-cardcommand. - Provision a LIM card as necessary. Refer to the Database Administration - SS7 User's Guide (SS7 LIM) or to the Database Administration - IP7 User's Guide (IPLIM) for assistance.
- Re-enter the
tst-slkcommand that generated this error message after all action commands have completed.
2.2.340 E2378 Cmd Rej: The specified card cannot be inhibited
E5-TDM or E5-MDAL cards cannot be inhibited. Card locations 1114, 1116, 1117, xx09, and xx10 cannot be specified as values for the loc parameter.
Recovery
2.2.341 E2379 Cmd Rej: Missing parameter
Table 2-4 describes the parameter combinations that must be entered.
Table 2-4 Required Command and Parameter Combinations
| Command | Missing Parameter |
|---|---|
chg-ee-card |
If the fltid parameter is specified, then the action parameter must be specified. |
dbg-ddb |
If the action parameter has a value of disp, aud, stats, or wwa, then the loc parameter must be specified. If the action=aud and the rloc parameter are specified, then the audtype parameter must be specified. If the action parameter has a value of disp or aud, then the tbl parameter must be specified. |
ent-ee-flt |
If the sctpstr parameter is specified, then the stype=data and ipprot=sctp parameters must be specified. |
ent/chg-gttact |
If a value of dup or fwd is specified for the act parameter, then the pc/pca/pci/pcn/pcn24/pcn16 parameter must be specified. If the ri=ssn parameter is specified, then the ssn parameter must be specified. If the cgpcogmsg=provcgpc parameter is specified, then the cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16 parameter must be specified. The sprm and tprm parameters must be specified when act is set to scpval. |
ent/dlt/rtrv-pct |
If the ssn or ecics parameter is specified, then the si parameter must be specified. If the rcics parameter is specified, then the ecics parameter must be specified. If the ecics, ecice, and rcics parameters are specified, then the rcice parameter must be specified. If the ecics, rcics, and rcice parameters are specified, then the ecice parameter must be specified. For the For the |
ent-slk |
If a card location is specified for a Channel card (card type limch) assigned to an E1 interface, then the e1loc parameter must be specified. If a card location is specified for a Channel card (card type limch) assigned to a T1 interface, then the t1loc parameter must be specified. If a card location is specified for an E1, T1, or Channel card (card type lime1, limt1, or limch), then the ts parameter must be specified for the link. |
rept-stat-slk |
This command can be entered with the stat parameter or the loc and port/link parameters. If the stat parameter is specified, it must be specified by itself. If the loc parameter is specified, the port/link parameter must be specified. If the port/link parameter is specified, the loc parameter must be specified. Class criteria cannot be specified without dpc parameter. |
Recovery
Re-enter the command that generated this error message, specifying a valid set of parameters. Refer to the command description in Commands User's Guide for more information.
2.2.342 E2381 Cmd Rej: Combined total baud rate for all ports cannot exceed 168K
The combined total line speed (baud rate in bits-per-second) for all active terminal ports cannot exceed 168,000 bps.
Recovery
2.2.343 E2382 Cmd Rej: Only 4 ports with sys maint. output group ON are allowed
Only 4 terminals can be configured to receive system maintenance-related unsolicited messages.
Recovery
2.2.344 E2383 Cmd Rej: MCP card must be IS-ANR Restrict to enable Meas Platform
At least one type MCPM card (E5-MCPM-B) must be in the IS-ANR Restrict state before the Measurements Platform collection function can be enabled.
Recovery
2.2.345 E2384 Cmd Rej: Link set is not equipped
For the dact-rstst command, the linkset specified by the lsn parameter must already exist in the database.
For the inh/unhb-alm and rept-stat-ls commands, the linkset specified by the lsn parameter must already be equipped in the database.
For the rept-meas command, either the specified linkset does not exist or no link is configured for it.
Recovery
2.2.346 E2385 Cmd Rej: May not specify both LSN and PST
The lsn and stat parameters cannot be specified together in the command.
Recovery
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.
2.2.347 E2386 Cmd Rej: DPC parameter needed with MODE=FULL
The dpc and mode=full parameters must be specified together in the command.
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.
2.2.348 E2387 Cmd Rej: Card is not in service
For the act/dact-cdl, act-dlk, act/dact-lbp, pass, rept-stat-rtd, and tst-j1 commands, the card specified by the loc parameter must be in service.
The card must be Active before the act/dact-ip-lnk command can be entered.
A type IPSM card must be in service before the act-ftp-trns command can be entered.
For the act-upgrade command, a type IPSM card must be provisioned before a value of getrel or chkrel can be specified for the action parameter.
Caution:
It is strongly recommended that this command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.For the chg-db command, a type IPSM card must be provisioned before the chg-db:action=restore:src=server or chg-db:action=backup:dest=server command can be entered.
Recovery
2.2.349 E2388 Cmd Rej: Point code not equipped
The value specified for the dpc parameter must exist in the database.
Recovery
2.2.350 E2389 Cmd Rej: No troubles to Display
No troubles were located in the trouble log.
Recovery
No further action is necessary for the rtrv-trbl command.
2.2.351 E2390 Cmd Rej: No obits to display
No entries for the obituary log were found.
Recovery
No further action is necessary for the rtrv-obit command.
2.2.352 E2391 Cmd Rej: Echo not allowed for telnet terminals
The value specified for the trm parameter cannot indicate a telnet port.
Recovery
2.2.353 E2392 Cmd Rej: Received wrong display mode
For the aud-data command, if the type=ddb parameter is specified, then the display=except parameter cannot be specified.
For the rept-imt-info command, the report=err parameter must be specified before the mode parameter can be specified.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.354 E2393 Cmd Rej: Terminal is not equipped
The value specified for the trm parameter must indicate an equipped terminal.
Recovery
2.2.355 E2394 Cmd Rej: Number out of range
The value specified for the parameter is either too great or too small.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.356 E2395 Cmd Rej: Removable DB levels don't match, must specify sloc parameter
If E5-MASP hardware is used for a restore procedure, and if the active and standby removable drives installed in the latched USB port have different DB levels, then the sloc parameter must be specified to indicate the removable drive to be used.
Recovery
2.2.357 E2396 Cmd Rej: NSFI must be specified if NISUPMT is specified
Recovery
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.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.358 E2398 Cmd Rej: Standby MASP is unavailable
The card location specified in this command was the standby OAM, and the standby OAM could not be found.
Recovery
2.2.359 E2400 Cmd Rej: Dual ExAP Config feature must be Enabled
For the chg-card command, if the value ELAP or EPAP is specified for the data parameter for VSCCP, the Dual ExAP Config feature must be enabled
For the chg/ent-lnp-serv command, the Dual ExAP Config feature must be enabled before the nrqdtblnop parameter can be specified.
For the chg-sccpopts command, the Dual ExAP Config feature must be enabled before the GTTDIST=EPAP/ELAP parameter can be specified.
For the rept-stat-mfc command, the Dual ExAP Config feature must be enabled before a value of scpepap or scpelap can be specified for the service parameter.
For the rept-stat-sccp command, the Dual ExAP Config feature must be enabled before data=elap/epap/gtt can be specified.
Recovery
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.360 E2401 Cmd Rej: GTA/SADDR range overlaps a current range
The range of global title addresses (GTAs) to be changed, as specified by the start and end GTAs, must match exactly an existing range in the global title translation data for the specified translation type. The specified gta/egta or saddr/eaddr range must exist for the specified GTT set in the STP active database. While an exact match is not required, an overlap with another range cannot be specified.
Recovery
2.2.361 E2402 Cmd Rej: GTA/SADDR range does not exist
For the chg/dlt-gta commands, the specified GTA/SADDR must occur within an existing GTA range in the specified Global Title Translation (GTT) set.
For the chg/dlt-gtt commands, the specified GTA range must already exist in the GTT table.
Recovery
2.2.362 E2403 Cmd Rej: Length of EGTA/EADDR must be equal to length of GTA/SADDR
For the ent/chg/dlt/rtrv-gta commands, if the egta/eaddr parameter is specified, the gta/saddr parameter must be specified. The gta/saddr and egta/eaddr parameters must be the same length, and the value for the egta/eaddr parameter must be greater than the value for the gta/saddr parameter.
For the ent/chg/dlt/rtrv-gtt commands, if the egta parameter is specified, the gta parameter must be specified. The gta and egta parameters must be the same length, and the value for the egta parameter must be greater than the value for the gta parameter.
For the ent/dlt/rtrv-gttact-path command, if the ecggta/ecdgta parameter is specified, then the values of the cggta/cdgta and ecggta/ecdgta parameters must be the same length.
Recovery
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.
2.2.363 E2404 Cmd Rej: GTA does not match translation type’s number of digits
The number of digits in the specified gta parameter must be at least the number of digits provisioned for the given translation type. If the VGTT (variable length GTT) feature is turned on, there can be up to 10 GTA lengths per translation type.
Recovery
2.2.364 E2405 Cmd Rej: GTA/SADDR does not exist in any range
The global title address/start address specified by the gta/saddr parameter must already exist.
The number of digits in the specified gta/saddr parameter must be at least the number of digits provisioned for the GTT set specified by the gttsn parameter. If the VGTT feature is turned on, then up to 10 GTA/SADDR lengths can exist per GTT set. If the VGTT with 16 lengths Support for 16 GTT Lengths in VGTT feature is turned on, then up to 16 GTA/SADDR lengths can exist per GTT set.
Recovery
2.2.365 E2406 Cmd Rej: ADJ required if MPC/MSSN is given or MULT=DOM or SHR
If the mpc/mpca/mpci/mpcn and mssn parameters are specified, or if a value of dom or shr is specified for the mult parameter, then the adj parameter must be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameaters. Refer to the command description in the Commands User's Guide for assistance.
2.2.366 E2407 Cmd Rej: GTA range is already assigned
The range of global title addresses specified cannot already be assigned to this translation type.
Recovery
- Display the current global title addresses. Enter the
rtrv-gttcommand. - Re-enter the
ent-gttcommand that generated this error message, specifying a valid combination of parameters. Refer to the Database Administration - GTT User's Guide and to the command description in Commands User's Guide for assistance.
2.2.367 E2408 Cmd Rej: CSPC broadcast group already exists
If the pc parameter is not specified, then the value entered for the grp parameter cannot already exist.
Recovery
2.2.368 E2409 Cmd Rej: EGTA cannot be specified without GTA
For the ent/chg/rtrv-gtt and rtrv-gta commands, if the egta parameter is specified, then the gta parameter must be specified.
For the ent/dlt/rtrv-gttact-path command, the cggta/cdgta parameter must be specified before the ecggta/ecdgta parameter can be specified.
Recovery
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 and to the Database Administration - GTT User's Guide for assistance.
2.2.369 E2410 Cmd Rej: CSPC broadcast group table is full
The system can contain a maximum of 2550 CSPC broadcast groups.
Recovery
2.2.370 E2411 Cmd Rej: CSPC group does not exist
For the ent/chg-map command, the value specified for the grp parameter must already exist or a value of grp=none parameter must be specified for the chg-map command.
For the dlt-cspc command, the value specified for the grp parameter must already exist.
For the ent-cspc command, if a point code is specified, then the value specified for the grp parameter must already exist.
Recovery
2.2.371 E2412 Cmd Rej: Command already in progress
If the act/chg/copy/rept-stat/rtrv-gpl command is in progress, then no other -gpl command can be entered.
If a chg-ctrl-feat command is in progress, then another chg-ctrl-feat command cannot be entered.
If the copy/init-ext-stats command is in progress, then no other -ext-stats command can be entered.
Recovery
Re-enter the command that generated this error message after the system has completed executing the command in progress.
2.2.372 E2413 Cmd Rej: PC already exists in CSPC group
The specified point code must already exist in the Routing table and cannot already exist in the specified group.
Recovery
2.2.373 E2414 Cmd Rej: PC does not exist in CSPC group
The point code must already exist in the CSPC group specified by the grp parameter.
Recovery
2.2.374 E2415 Cmd Rej: Concerned node table for this group is full
The specified CSPC group is full. Up to 96 point codes can be entered in a CSPC group.
Recovery
2.2.375 E2416 Cmd Rej: Unable to access database. Severe database failure
The database cannot be accessed. There is a severe database failure.
Recovery
Contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.376 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
2.2.377 E2418 Cmd Rej: Mate PC/SSN cannot be given when MULT=SOL
The mult=sol parameter and the mpc and mssn parameters cannot be specified together in the command.
Recovery
Re-enter the ent/chg-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - GTT User's Guide for assistance.
2.2.378 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
2.2.379 E2420 Cmd Rej: EGTA/EADDR must be greater than or equal to GTA/SADDR
For the ent/chg/dlt/rtrv-gta commands, the value specified for the egta/eaddr parameter must be greater than or equal to the value specified for the gta/saddr parameter.
For the ent/chg/dlt/rtrv-gtt commands, the value specified for the egta parameter must be greater than or equal to the value specified for the gta parameter.
For the ent/dlt/rtrv-gttact-path command, the value specified for the ecggta/ecdgta parameter must be greater than or equal to the value specified for the cggta/cdgta parameter.
Recovery
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 and to Database Administration - GTT User's Guide for assistance.
2.2.380 E2421 Cmd Rej: ALL=YES must be specified to delete the entire group
To delete an entire concerned signaling point code group, the all=yes parameter must be specified.
Recovery
Re-enter the dlt-cspc command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.381 E2422 Cmd Rej: ALL=YES must be specified to delete all SSNs for a PC
To delete all subsystem numbers for a given point code, the all=yes parameter must be specified.
Recovery
Re-enter the dlt-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.382 E2423 Cmd Rej: FORCE=YES must be specified for NUM greater than 1000
If the value specified for the num parameter is greater than 1000, then the force=yes parameter must be specified.
Recovery
Re-enter the rtrv-gta or rtrv-gtt command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.383 E2424 Cmd Rej: SRM=YES cannot be entered with ITU point code types
The srm=yes parameter and the ITU point code parameters (pci, pcn, or pcn24) cannot be specified together in the command.
Recovery
2.2.384 E2425 Cmd Rej: Mate PC/SSN cannot be same as PC/SSN
The values specified for the mpc and mssn parameters cannot be the same as the values specified for the pc and ssn parameters.
- If the mssn value is not equal to the ssn value, then the mpc and pc parameters can have the same value.
- If the pc value is not equal to the mpc value, then the ssn and mssn parametes can have the same value.
Recovery
2.2.385 E2426 Cmd Rej: Mnemonic argument is undefined
A valid value must be specified for the ri parameter.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.386 E2427 Cmd Rej: MPC does not exist in routing Table
For the ent/chg-map command, the value specified for the remote mate point code MPC must already exist in the Route table.
For the ent/chg-mrn command and the chg-sccp-serv command, the values specified for the remote MPCs must already exist as destinations in the Ordered Route entity set or reside in a cluster destination for which ordered routes are specified.
Recovery
- Display the entries in the Route table. Enter the
rtrv-rtecommand. - Add values to the Route table as necessary. Refer to the Database Administration - SS7 User's Guide for assistance.
- 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 and to the Database Administration - GTT User's Guide for assistance.
2.2.387 E2428 Cmd Rej: MPC entered, MSSN must also be given
If the mpc parameter is specified, then the mssn parameter must also be specified.
Recovery
Re-enter the chg-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.388 E2429 Cmd Rej: MPC network type does not match PC network type
The apca and pcn24 parameters cannot be specified for the same MAP set. The pci and pcn parameters cannot be specified for a MAP set that contains a true point code.
Recovery
2.2.389 E2430 Cmd Rej: Subsystem table for MPC is full
Each mate remote point code can contain only 10 subsystem numbers.
Recovery
2.2.390 E2431 Cmd Rej: MPC/MSSN pair already exists
The values specified for the mpc and mssn parameters cannot already exist in the MAP table.
Recovery
2.2.391 E2432 Cmd Rej: MSSN or MATERC entered, MPC must also be given
If the mssn or rc parameter is specified, then the mpc parameter must be specified.
Recovery
Re-enter the ent/chg-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.392 E2434 Cmd Rej: Dual ExAP Config or EPAP Data Split must be ON
For the
chg/ent-card command, the
Dual ExAP Config or
EPAP Data Split feature must be
ON before
data=gtt/epap can be specified for
VSCCP.
For the
chg-sccpopts command, the
Dual ExAP Config or
EPAP Data Split feature must be
ON before the
gttdist=epap parameter can be specified.
For the
chg-srvsel command, the
Dual ExAP Config or
EPAP Data Split feature must be
ON before the
nrqdtblnop parameter can be
specified.
For the
chg-ss-appl command, the
Dual ExAP Config or
EPAP Data Split feature must be
ON before the
nrqdtblnop parameter can be
specified.
For the
ent-srvsel command, the
Dual ExAP Config or
EPAP Data Split feature must be
ON before the
rqdtblnop parameter can be
specified.
For the
ent-ss-appl command, the
Dual ExAP Config or
EPAP Data Split feature must be
ON before the
rqdtblnop parameter can be
specified.
For the
rept-stat-mfc command, the
Dual ExAP Config or
EPAP Data Split feature must be enabled before a
value of
scpepap can be specified.
Recovery
2.2.393 E2435 Cmd Rej: New/existing PC does not exist in the remote PC table
If the new or existing xlat parameter value is dpc, the new or existing ri parameter value is ssn, and the pc/pca/pci/pcn parameter is not specified, then the point code must exist in the Remote Point Code/MAP table.
Recovery
2.2.394 E2437 Cmd Rej: New/existing RI must be GT for new/existing XLAT=DPCNGT
If the xlat=dpcngt parameter is specified, then the ri=gt parameter must be specified.
Recovery
Re-enter the chg-gta or chg-gtt command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.395 E2438 Cmd Rej: MPC and MSSN must be defined for new MULT val
If the mult=dom or mult=shr parameter is specified, the mated point code (mpc/mpca/mpci/mpcn/mpcn24) and mssn parameters must be specified.
Recovery
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.
2.2.396 E2439 Cmd Rej: New PC does not exist in the routing table
The value specified for the point code parameter must already exist in the routing table.
Recovery
2.2.397 E2440 Cmd Rej: Primary PC/SSN pair already exists
The primary point code and primary subsystem number pairs must be unique.
If the mapset=dflt parameter is specified, then the specified PC/SSN cannot exist in the default MAP Set.
Recovery
Re-enter the ent-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.398 E2441 Cmd Rej: Dual ExAP Config must be ON and EPAP Data Split must be OFF
For the chg-card command, the Dual ExAP Config feature must be ON and the EPAP Data Split feature must be OFF when data=epap is specifiedfor VSCCP.
For the ent-card command, if the EPAP Data Split feature is ON, a value of dn or imsi must be specified for the data parameter for VSCCP. If ELAP or EPAP is specified for the data parameter for VSCCP, then the Dual ExAP Config feature must be enabled. When data=epap is specified for VSCCP, then the Dual ExAP Config feature must be enabled and the EPAP Data Split feature must be OFF.
For the init-card command, the Dual ExAP Config feature must be ON and the EPAP Data Split feature must be OFF when type=epap is specified for VSCCP.
Recovery
2.2.399 E2442 Cmd Rej: SSN must be specified for new values of XLAT/RI
If the xlat=dpcssn parameter is specified, and the current ssn parameter value has been removed, then a new ssn parameter must be specified.
Recovery
Re-enter the chg-gta or chg-gtt command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.400 E2443 Cmd Rej: IP Link must not be configured for GTT card
For the chg-card command, the data=gtt parameter must not be specified for VSCCP if an IP link is configured for the card.
For the chg-ip-lnk command, a valid IP address can not be configured for the card, if the card is provisioned as a GTT card.
Recovery
2.2.401 E2446 Cmd Rej: SCCPMT must be specified as 9, 10, 17, 18, or *
A valid value must be specified for the sccpmt parameter.
Recovery
Re-enter the ent/chg/dlt/rtrv-scr-cgpa command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.402 E2447 Cmd Rej: NUM exceeds maximum table size
An valid value must be specified for the num parameter.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.403 E2448 Cmd Rej: ALL=YES cannot be specified with a point code
The pc and all parameters cannot be specified together in the command. To delete an entire concerned signaling point code group, specify the all=yes parameter. To delete a single point code from a concerned signaling point code group, specify the pc parameter.
Recovery
Re-enter the dlt-cspc command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.404 E2449 Cmd Rej: CSPC group network type does not match PC network type
The ANSI/ITU SCCP Conversion feature must be enabled before the network type of the specified CSPC group can be different from the network type of the specified point code.
Recovery
2.2.405 E2450 Cmd Rej: PC/SSN does not exist as a mated application
For the ent/chg-gsmmap-scrn and ent/chg-gsms-opcode commands, the values specified for the pc/pca/pci/pcn/pcn24, npc/npca/npci/npcn/npcn24, or (n)ssn parameters must already exist in the MAP table, or the force=yes parameter must be specified/
For the ent/chg-gttact command, the values specified for the pc/pca/pci/pcn/pcn24, npc/npca/npci/npcn/npcn24, or (n)ssn parameters must already exist in the MAP table.
Recovery
2.2.406 E2451 Cmd Rej: Primary remote PC does not exist in routing table
The primary remote point code must already exist in the Route table, or as a destination in the ordered route entity set, or reside in a cluster destination for which ordered routes are specified.
Recovery
2.2.407 E2452 Cmd Rej: Remote point code does not exist in MAP table
For the chg/dlt/rtrv-map command, the value specified for the pc/pca/pci/pcn parameter must already exist in the MAP table.
For the chg-ppsopts command, if the Flexible GTT Load Sharing (FGTTLS) feature is not enabled, and if the ri=ssn parameter is specified, then the value specified for the pc/pca/pci/pcn parameter must exist in the default MAP set of the MAP table.
Recovery
2.2.408 E2453 Cmd Rej: Subsystem table for primary remote point code is full
Each primary remote point code can contain up to 12 subsystem numbers.
Recovery
2.2.409 E2454 Cmd Rej: Remote point code table is full
More than 1024 remote point codes cannot be entered into the Remote Point Code table. If the table is full, then a new remote point code cannot be entered until an exisitng remote point code is deleted.
Recovery
2.2.410 E2455 Cmd Rej: ALL cannot be specified with a subsystem
The all and ssn parameters cannot be specified together in the command.
Recovery
Re-enter the dlt-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.411 E2456 Cmd Rej: SSN does not exist for given remote point code
The value specified for the ssn parameter must already exist.
Recovery
- Display the existing SSN values. Enter the
rtrv-mapcommand. - Enter a new SSN as necessary. Refer to the Database Administration - GTT User's Guide for assistance.
- Re-enter the
chg/dlt/rtrv-mapcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.412 E2457 Cmd Rej: SSN can only be specified when XLAT=DPCSSN
For the ent/chg-gta and ent/chg-gtt commands, the xlat=dpcssn parameter must be specified before the ssn parameter can be specified. If the xlat=dpcssn parameter is specified, then the ssn parameter must be specified.
For the chg-gtt command, if the xlat parameter value is changed from dpcssn to dpc or dpcngt, a new ssn parameter value cannot be specified, and the current ssn parameter value must be removed.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.413 E2458 Cmd Rej: SSN cannot be specified without a point code
If the ssn parameter is specified, then the pc/pca/pci/pcn/pcn24 parameter must be specified.
Recovery
Re-enter the rtrv-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.414 E2459 Cmd Rej: Alias already in use
For the ent/chg-dstn command, the value specified for the aliasa/aliasi/aliasn/aliasn24 parameter cannot already be defined as another destination.
For the ent-tt command, the value specified for the alias parameter cannot already be used as an alias for another translation type.
Recovery
2.2.415 E2460 Cmd Rej: Alias defined as translation type
The value specified for the alias parameter must be associated with the value specified for the type/typea/typei/typen/typen24/typeis/typens parameter and cannot be the value of an existing translation type.
Recovery
2.2.416 E2461 Cmd Rej: Alias not assigned to translation name
The value specified for the ttn parameter must correspond to the value specified for the alias parameter.
Recovery
- Display the existing values for the ttn and alias parameters. Enter the
rtrv-ttcommand. - Re-enter the
rtrv-ttcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.417 E2462 Cmd Rej: GTT table is full
The GTT table can support up to 269,999 entries.
If the XGTT feature is enabled, the GTT table can support up to either 400,000 or 1,000,000 entries, depending on the controlled feature part number that is enabled.
For the dlt-gta or dlt-gtt command, the GTT table cannot be full in case a delete command causes a split requiring more entries to be added.
Recovery
2.2.418 E2463 Cmd Rej: Alias not assigned to translation type
For the dlt-tt command, the alias and ttn parameters must be specified and must already exist in the database for the network type.
For the rtrv-tt command, if the alias parameter is specified with the type and/or ttn parameter, then the alias must exist in the database for the specified network type, and it cannot be a translation type.
Recovery
2.2.419 E2464 Cmd Rej: Translation Type already exists
The translation type specified by type/typea/typei/typen/typen24/typeis/typens cannot already exist in the database containing the ANSI and ITU types.
Recovery
- Display the existing entries in the Translation Type table. Enter the
rtrv-ttcommand. - Re-enter the
ent-ttcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - GTT User's Guide for assistance.
2.2.420 E2465 Cmd Rej: Translation TYPE defined as an alias
For the ent-gta command, the value specified for the ntt parameter cannot have already been specified as a value for the alias parameter.
For the ent/chg/dlt/rtrv-gtt or ent/dlt/rtrv-tt command, the value specified for the type/typea/typei/typen/typen24/typeis/typens parameter cannot have already been specified as a value for the alias parameter.
Recovery
2.2.421 E2466 Cmd Rej: Translation Type specified does not exist
For the ent/chg/dlt/rtrv-gtt or the ent/dlt/rtrv-tt command, the value specified for the type/typea/typei/typen/typen24/typeis/typens parameter must already exist in the database.
For the ent-gta command, the value specified for the ntt parameter must match the value of an existing ANSI GTT selector that is assigned to a GTT set (gttsn parameter).
Recovery
2.2.422 E2467 Cmd Rej: TTN already in use
The value specified for the ttn parameter cannot already exist.
Recovery
- Display the existing ttn parameter values. Enter the
rtrv-ttcommand. - Re-enter the
ent-ttcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.423 E2468 Cmd Rej: TTN specified does not exist
The value specified for the ttn parameter must already exist in the Translation Type table.
Recovery
- Display the entries in the Translation Type table. Enter the
rtrv-ttcommand. - Re-enter the
ent/chg/dlt/rtrv-gttor theent/dlt/rtrv-ttcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.424 E2469 Cmd Rej: NDGT parameter not permitted with ALIAS
The alias and ndgt parameters cannot be specified together in the command.
Recovery
Re-enter the ent-tt command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.425 E2470 Cmd Rej: Point Code network type does not match TT network type
The ANSI/ITU SCCP Conversion feature must be enabled before a translated point code and a translation type in different network types can be specified.
Recovery
2.2.426 E2471 Cmd Rej: Translation TYPE has an alias
The translation type cannot be deleted until the alias assigned to it has been deleted.
Recovery
2.2.427 E2472 Cmd Rej: Translation TYPE is referenced by GTT entry
A translation type cannot be deleted if the translation type is referenced by a GTT entry.
Recovery
2.2.428 E2473 Cmd Rej: TTN and TYPE do not correspond to each other
The value specified for the ttn parameter must correspond to a translation type entry (specified by the type/typea/typei/typen/typen24/typeis/typens parameter). The values specified for the ttn and type/typea/typei/typen/typen24/typeis/typens parameters must already exist in the translation table.
Recovery
2.2.429 E2474 Cmd Rej: Translation TYPE must be specified
If the alias parameter is specified, then the type/typea/typei/typen/typen24/typeis/typens parameter must be specified.
Recovery
Re-enter the dlt-tt command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.430 E2475 Cmd Rej: Either TYPE or TTN must be specified
The type/typea/typei/typen/typen24/typeis/typens or ttn parameter must be specified.
Recovery
Re-enter the ent/chg/dlt/rtrv-gtt or the dlt-tt command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.431 E2477 Cmd Rej: This function is not yet supported
You attempted to enter a command that has not yet been developed and enabled. You may have made a clerical error.
Recovery
Re-enter the command that generated this error message.
If this error message appears again, refer to the Commands User's Guide for valid syntax usage.
2.2.432 E2478 Cmd Rej: Wild card entries are not allowed in this command
A wild card (*) cannot be specified as a value for any parameter in the command
Note:
When a ‘wild card’ is used to specify a parameter value ‘*’ it indicates the full range of values. Do not confuse this usage with the parameter value '**', which SEAS uses for “all and every entry in the database including the value '*'”.Recovery
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.
2.2.433 E2479 Cmd Rej: E5-SM4G Throughput Cap feature must be enabled
For the enable-ctrl-feat command, the Dual ExAP Config feature can not be enabled before E5-SM4G Throughput Cap feature is enabled.
Recovery
2.2.434 E2480 Cmd Rej: RI=GT must be specified when XLAT=DPCNGT
If the xlat=dpcngt parameter is specified, then the ri=gt parameter must be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.435 E2481 Cmd Rej: SSN must be specified when XLAT=DPCSSN
If the xlat=dpcssn parameter is specified, then the ssn parameter must be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.436 E2482 Cmd Rej: TIF Sel Scr and TIF NS features are mutually exclusive
enable-ctrl-feat command, TIF Selective Screening feature is mutually exclusive with TIF Number Substitution feature. TIF Selective Screening feature uses Number Substitution digit field to store Call Types associated with DN.
Recovery
2.2.437 E2483 Cmd Rej: Unknown / Invalid GWSOA parameter combination
This error condition occurs when an unsupported combination of parameters is provided for a gateway screening command; it should not appear under normal conditions. GWSOA parameter combinations should be known and valid.
Recovery
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.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.438 E2484 Cmd Rej: SSN must be 1 if NSFI=AFTPC
The ssn=1 parameter must be specified before the nsfi=aftpc parameter can be specified.
Recovery
Re-enter the ent-scr-cdpa command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.439 E2485 Cmd Rej: All entered point code elements must be C if any are C
If one of the point code parameters has a value of c (for “Continue”) then all of the point code parameters must have a value of c.
Note:
If c is specified for the first parameter, then the other parameters will default to c in the database.Recovery
Re-enter the command, that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.440 E2486 Cmd Rej: NSFI must be STOP if COPY or REDIRECT are specified
If the copy=yes or redirect=yes parameter is specified, then the nsfi=stop parameter must be specified.
Recovery
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.
2.2.441 E2488 Cmd Rej: H0 and H1 must be specified for given SI
If the si parameter has a value of 00, 01, or 02, then the h0 and h1 parameters must be specified. If a value other than 00, 01, or 02 is specified for the si parameter, then the h0 parameter cannot be specified.
Recovery
Re-enter the ent/chg/dlt-scr-sio command, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.442 E2489 Cmd Rej: H0/H1 matches existing H0/H1 in given SR
The values specified for the h0 and h1 parameters cannot already exist in the range of any existing wild-carded h0/h1 pair in the sr, nic, and si parameter combination.
Note:
A ‘wild card’ is a term to describe the parameter value ‘*’ that indicates the full range of values. Do not confuse this usage with the parameter value '**', which SEAS uses for “all and every entry in the database including the value '*'”.Recovery
2.2.443 E2490 Cmd Rej: H0 and H1 cannot be specified for SI greater than 2
If the si parameter has a value greater than 2, then the h0 and h1 parameters cannot be specified.
Recovery
- If applicable, determine the existing values for the si parameter. Enter the
rtrv-scr-siocommand. - Re-enter the
ent/chg/dlt/rtrv-scr-siocommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.444 E2491 Cmd Rej: NH0 and NH1 cannot be specified for NSI greater than 2
If the value specified for the nsi parameter is greater than 2, then the nh0 and nh1 parameters cannot be specified.
Recovery
Re-enter the chg-scr-sio command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.445 E2492 Cmd Rej: The NSFI / RI combination is invalid
A supported combination of values for the ri and nsfi parameters must be entered.
- If the ri=gt parameter is specified, then the nsfi=tt parameter must be specified.
- If the ri=dpc parameter is specified, then the nsfi=cdpa parameter must be specified.
- If the ri=* parameter is specified, then the nsfi=tt or nsfi=cdpa parameter must be specified.
Recovery
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.
2.2.446 E2493 Cmd Rej: H1 must be wild card if H0 is wild card
If a wild-card (*) value is specified for the h0 parameter, then a wild-card value must be specified for the h1 parameter.
Note:
A ‘wild card’ is used to describe the asterisk parameter value ‘*’ that indicates the full range of values. Do not confuse this usage with the parameter value '**', which SEAS uses for “all and every entry in the database including the value '*'”.Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.447 E2494 Cmd Rej: The NSFI is invalid for this screen type
A valid value must be specified for the nsfi parameter.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.448 E2495 Cmd Rej: Point codes contain invalid wild card combinations
The “wild card” parameter value (*) can be specified only in certain parameter combinations in the gateway screening commands.
Note:
A ‘wild card’ is a term used to describe a parameter value ‘*’ that indicates the full range of values. Do not confuse this usage with the parameter value '**', which SEAS uses for all and every entry in the database including the value '*'.Recovery
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 and to the Database Administration - GWS User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.449 E2496 Cmd Rej: NI, ZONE, MSA, UN or NPC cannot be C - more than one exists
The point code c-c-c, or npc=c, cannot be deleted until all other entries in the screening reference have been deleted.
Recovery
2.2.450 E2497 Cmd Rej: NI, ZONE, MSA, UN or NPC cannot be C for existing blocked SR
The point code c-c-c, or the npc=c parameter can be specified only for a screening reference that does not alerady exist.
Recovery
2.2.451 E2498 Cmd Rej: Last entry in given SR is ref'ed by another screen
The specified screening reference contains only one entry. If this screening reference is referenced by another screen, it cannot be deleted.
Recovery
2.2.452 E2499 Cmd Rej: Maximum number of rules exceeded in screen set
If the screen set reaches 100% capacity (indicated by the “100% full” message), the EAGLE will allow subsequent entries. An error will occur, however, when downloading the screen set to the card.
Recovery
2.2.453 E2500 Cmd Rej: Maximum number of screen sets exceeded
The system can contain up to 63 user-definable screen sets.
Recovery
2.2.454 E2501 Cmd Rej: Mixed point code types are not allowed
The command was entered with a point code that contains different network types. Point codes are specified by the following parameters:
ANSI point code – ni, nc, ncm and for the enter and change commands — nni, nnc, nncm
ITU-I point code – zone, area, id and for the enter and change commands — nzone, narea, nid
ITU-N point code – npc and for the enter and change commands — nnpc
ITU-N24 point code - msa, ssa, sp and for the enter and change commands — nmsa, nssa, nsp
An example of a point code containing different network types (i.e., mixed types of point codes) is ni-area-npc. This is not allowed. If any of the enter and change commands are entered, an existing point code of one network type can be changed to another network type—as long as all the proper parameters are used.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide to the Database Administration - GWS User's Guide (Gateway Screening commands) and to the Database Administration - IP7 User's Guide (Route key commands) for assistance.
2.2.455 E2502 Cmd Rej: NSR cannot be specified if COPY or REDIRECT are specified
If the copy=yes or redirect=yes parameter is specified, then the nsr parameter cannot be specified.
Recovery
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.
2.2.456 E2503 Cmd Rej: NC cannot be zero when NI is less than 6
If the value specified for the ni parameter is less than 6, then a value of 0 cannot be specified for the nc parameter.
Recovery
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.
2.2.457 E2504 Cmd Rej: New/existing NSFI=AFTPC requires new/existing SSN=1
If the nsfi=aftpc parameter is specified, then the ssn parameter must have a value of 1.
Recovery
- Display the existing values for the ssn parameter. Enter the
rtrv-scr-cdpacommand. - Re-enter the
chg-scr-cdpacommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.458 E2505 Cmd Rej: NH0 and NH1 must be specified for given NSI
If the value specified for the nsi parameter is less than or equal to 2, and the value specified for the si parameter was greater than 2, then the nh0 and nh1 parameters must be specified.
Recovery
Re-enter the chg-scr-sio command that generated this error message specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.459 E2506 Cmd Rej: New H0/H1 matches existing wild carded H0/H1 in given SR
The values specified for the h0 or h1 parameters cannot have correspond to values that were set (by default) to be wild-carded.
Note:
A ‘wild card’ is a term to describe the parameter value ‘*’ that indicates the full range of values. Do not confuse this usage with the parameter value '**', which SEAS uses for “all and every entry in the database including the value '*'”.Recovery
Re-enter the chg-scr-sio command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.460 E2507 Cmd Rej: NH0 and NH1 cannot be specified for SI greater than 2
If the value specified for the nsi parameter is greater than 2, then the nh0 and nh1 parameters cannot be specified.
Recovery
Re-enter the chg-scr-sio command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.461 E2508 Cmd Rej: SCMGFID is invalid
If the ssn=1 parameter is specified, then the scmgfid parameter must be specified.
If the ssn parameter has a value other than 1, then the scmgfid parameter cannot be specified.
Recovery
Re-enter the ent/chg/dlt/rtrv-cdpa command, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.462 E2509 Cmd Rej: NH1 must be wild card if NH0 is wild card
If a wild-card value (*) is specified for the nh0 parameter, then a wild-card value must be specified for the nh1 parameter.
Note:
A ‘wild card’ is a term used to describe the parameter value ‘*’ that indicates the full range of values. Do not confuse this usage with the parameter value '**', which SEAS uses for “all and every entry in the database including the value '*'”.Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.463 E2510 Cmd Rej: NI is invalid
A valid combination of the ni, nc, and/or ncm parameters must be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.464 E2511 Cmd Rej: NC is invalid
A valid combination of the ni, nc, and/or ncm parameters must be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.465 E2512 Cmd Rej: NCM is invalid
A valid combination of the ni, nc, and/or ncm parameters must be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.466 E2514 Cmd Rej: PC/SSN/RI/SCCPMT already exists in given SR
For the chg-scr-cgpa command, the values specified for the new CGPA point code, nri, nsccpmt, and nssn parameters cannot already exist in the CGPA entity set.
For the ent-scr-cgpa command, the values specified for the CGPA point code, ri, sccpmt, and ssn parameters cannot already exist in the CGPA entity set.
Recovery
2.2.467 E2515 Cmd Rej: PC/SSN/RI/SCCPMT does not exist in given SR
The values specified for the pc, ssn, ri, and sccpmt parameters must already exist in the screening reference.
Recovery
2.2.468 E2516 Cmd Rej: PC/SSN/SCMGFID already exists in given SR
For the chg-scr-cdpa command, the values specified for the new CdPA point code, nscmgfid, and nssn parameters cannot already exist in the CDPA entity set.
For the ent-scr-cdpa command, the values specified for the CdPA point code, scmgfid, and ssn parameters cannot already exist in the CDPA entity set
Recovery
- Display the current entries in the CDPA entity set. Enter the
rtrv-scr-cdpacommand. - Re-enter the
ent/chg-scr-cdpacommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.469 E2517 Cmd Rej: PC/SSN/SCMGFID does not exist in given SR
The values specified for the pc, ssn, or scmgfid parameter must already exist in the screening reference.
Recovery
2.2.470 E2518 Cmd Rej: NNIC, NSI, and NH0/NH1 entry already exists in given SR
The values specified for the nnic, nsi, nh0, and nh1 parameters cannot already exist in the specified screening reference.
Recovery
- Display the existing values in the screening reference. Enter the
rtrv-scr-sio:sr=command. - Re-enter the
chg-scr-siocommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.471 E2519 Cmd Rej: ISUPMT/TUPMT already exists in given SR
The value specified for the (n)isupmt or (n)tupmt parameter cannot already exist in the screening reference specified by the sr parameter.
Recovery
2.2.472 E2520 Cmd Rej: ISUPMT/TUPMT does not exist in given SR
The value specified for the isupmt or tupmt parameter must already exist in the screening reference specified by the sr parameter.
Recovery
- Display the existing screening reference data. Enter the
rtrv-scr-isup:sr=command. - Re-enter the
chg/dlt-scr-isupcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.473 E2521 Cmd Rej: NIC must be specified for given SI
If the nic parameter is specified, then the si parameter must be specified.
Recovery
Re-enter the rtrv-scr-sio command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.474 E2522 Cmd Rej: NIC does not exist for given SR
The value specified for the nic parameter must already exist in the screening reference specified by the sr parameter.
Recovery
- Display the SIO information for the screening reference. Enter the
rtrv-scr-sio:scr=command. - Re-enter
chg/dlt/rtrv-scr-siocommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.475 E2523 Cmd Rej: A specific RI must be specified in the range (DPC, GT, *)
A valid value or range of values must be specified for the ri parameter. Refer to the command description in Commands User's Guide for the values.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.476 E2524 Cmd Rej: A specific TT must be specified in the range (1-255,*)
A valid value or range of values must be specified for the type parameter. Refer to the command description in Commands User's Guide for the values.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.477 E2525 Cmd Rej: NI,ZONE,MSA,UN or NPC must be C when creating new blocked SR
For the ent-scr-blkdpc command, when a blocked DPC screen is created, the first entry for the ni-nc-ncm, zone-area-id, or msa-ssa-sp must be c-c-c or the npc=c parameter must be specified.
For the ent-scr-blkopc command, when a blocked OPC screen is created, the first entry for the ni-nc-ncm, zone-area-id, or msa-ssa-sp must be c-c-c or the npc=c parameter must be specified.
For both commands, subsequent entries can be specific point codes.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
Contact My Oracle Support for assistance if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.478 E2526 Cmd Rej: All new PC parms must be null if NI,ZONE,MSA,UN or NPC = C
If the specified ni-nc-ncm, zone-area-id, or msa-ssa-sp is equal to c-c-c or if the npc=c parameter is specified, then the nsfi=fail parameter and the nni, nnc, nncm, nzone, narea, nid, nmsa, nssa, nsp, and nnpc parameters cannot be specified. Point code c-c-c and npc=c cannot be changed to a numbered point code.
Recovery
Re-enter the chg-scr-blkdpc or chg-scr-blkopc command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.479 E2527 Cmd Rej: C value not allowed
If the nsfi=fail parameter is specified, then a value of c cannot be specified for the nni-nnc-nncm, nzone-narea-nid, nmsa-nssa-nsp, or nnpc parameters.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.480 E2528 Cmd Rej: No match on AREA or SSA parameter during retrieve
No match was found for the area or ssa parameter.
Recovery
Re-enter the command, specifying the screening reference (sr parameter) to show all values for the screening reference.
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 and to the Database Administration - GWS User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.481 E2530 Cmd Rej: No match on H0 parameter during retrieve
The h0 heading code (h0 parameter) was not found.
Recovery
Re-enter the rtrv-scr-sio command, specifying the screening reference (sr parameter) to show all values for the screening reference.
Re-enter the rtrv-scr-sio command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.482 E2531 Cmd Rej: No match on H1 parameter during retrieve
The value specified for the h1 parameter must already exist.
Recovery
2.2.483 E2532 Cmd Rej: No match on ID or SP parameter during retrieve
The values specified for the id and sp parameters must already exist.
Recovery
2.2.484 E2533 Cmd Rej: No match on NC parameter during retrieve
The value specified for the nc parameter must already exist.
Recovery
2.2.485 E2534 Cmd Rej: No match on NCM parameter during retrieve
The value specified for the ncm parameter must already exist.
Recovery
2.2.486 E2535 Cmd Rej: No match on NI parameter during retrieve
For the gateway screening commands, the value specified for the ni parameter must already exist.
For the rept-meas command, if the ni parameter is specified for origin reports, then measurements data must be available at the time the command is entered.
Recovery - Gateway Screening commands
- Display the current values for the parameters. Enter the command that generated this error message, specifying only the all=yes parameter.
- Provision new values as necessary. Refer to the Database Administration - GWS User's Guide for assistance.
- Re-enter the command that generated this error message, specifying a valid combination of parameters.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - rept-meas
2.2.487 E2536 Cmd Rej: No match on NIC parameter during retrieve
The value specified for the nic parameter must already exist.
Recovery
2.2.488 E2537 Cmd Rej: No match on NPC parameter during retrieve
The value specified for the npc parameter must already exist.
Recovery
2.2.489 E2538 Cmd Rej: No match on NSFI parameter during retrieve
For the gateway screening commands, the value specified for the nsfi parameter must already exist.
Recovery
2.2.490 E2539 Cmd Rej: No match on NSR parameter during retrieve
The value specified for the nsr parameter must already exist.
Recovery
2.2.491 E2540 Cmd Rej: No match on PRI parameter during retrieve
The value specified for the pri parameter must already exist.
Recovery
2.2.492 E2541 Cmd Rej: No match on RI parameter during retrieve
The value specified for the ri parameter must already exist.
Recovery
2.2.493 E2542 Cmd Rej: No match on SI parameter during retrieve
The value specified for the si parameter must already exist.
Recovery
2.2.494 E2543 Cmd Rej: No match on SSN parameter during retrieve
The value specified for the ssn parameter must already exist.
Recovery
Re-enter the command specifying the screening reference to show all subsystem numbers, as well as other values for the screening reference.
2.2.495 E2544 Cmd Rej: No match on TYPE parameter during retrieve
The value specified for the type parameter must already exist.
Recovery
2.2.496 E2545 Cmd Rej: No match on ZONE or MSA parameter during retrieve
The value specified for the zone or msa parameter must already exist.
Recovery
2.2.497 E2546 Cmd Rej: NSFI must be specified
If the value specified for the point code parameter is c-c-c, then the nsfi parameter must be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.498 E2547 Cmd Rej: NSFI must not be FAIL
If a value of c-c-c is specified for the point code parameter, then the nsfi=fail parameter cannot be specified.
Recovery
Re-enter the ent/chg-scr-blkdpc or ent/chg-scr-blkopc command, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.499 E2548 Cmd Rej: NSFI must be STOP
A value of stop must be specified for the nsfi parameter.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.500 E2549 Cmd Rej: NSFI must be FAIL
If the specified ni-nc-ncm , zone-area-id , or msa-ssa-sp is not equal to c-c-c , or if the npc=c parameter is not specified, then the nsfi=fail parameter must be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.501 E2550 Cmd Rej: NSFI / NSR cannot be specified
If a value of stop or fail is specified for the nsfi parameter, then the nsr parameter cannot be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.502 E2551 Cmd Rej: NSI must be specified for given NNIC
If the nnic parameter is specified, then the nsi parameter must be specified.
Recovery
Re-enter the chg-scr-sio command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - GWS User's Guide for assistance.
2.2.503 E2552 Cmd Rej: NSFI and NSR do not reference an existing screen
The values specified for the nsfi and nsr parameters must reference an existing screen.
Recovery
- Display the screen set data. Enter the appropriate
rtrv-command (for example, if thechg-scr-blkdpccommand generated the error message, then enter thertrv-scr-blkdpccommand). - 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 and to the Database Administration - GWS User's Guide for assistance.
2.2.504 E2553 Cmd Rej: NSR must be specified for given NSFI
If the nsfi parameter has a value other than stop or fail, then the nsr parameter must be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.505 E2554 Cmd Rej: NSR cannot be specified when NSFI is STOP or FAIL
If a value of stop or fail is specified for the nsfi parameter is specified, then the nsr parameter cannot be specified
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.506 E2555 Cmd Rej: Point code does not exist in given SR
The point code defined by the ni, nc, and ncm parameters must already be defined in the specified screening reference (NPC, the ITU-N standard, or zone area ID, the ITU-I standard).
Recovery
- Display the point codes for the given screening reference. Enter the appropriate
rtrv-command (for example, if thechg-scr-blkdpccommand generated the error message, then enter thertrv-scr-blkdpccommand). - 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 and to the Database Administration - GWS User's Guide for assistance.
2.2.507 E2556 Cmd Rej: A complete point code must be entered
A complete point code must be entered using one and only one of the four point code forms represented as ni-nc-ncm (ANSI point codes), zone-area-id (ITU-I point codes), msa-ssa-sp (ITU-N24 point codes), or npc (ITU-N point codes). The only exception is the special case of entering c for “Continue” in the commands that allow it.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.508 E2557 Cmd Rej: GWS table is full
The table shared by the Gateway Screening and Global Title Translation (GTT) features is full and the database could not be updated.
Either a gateway screening screen set and all of its rules, or a GTT type (and all GTT data referencing that translation type) must be deleted from the database.
Recovery - For a Gateway Screening Screen Set
-
Display the gateway screening screen sets in the database. Enter the
rtrv-scrsetcommand. Select a screen set to delete from the database. -
Enter these commands to verify the gateway screening entities that reference the gateway screening screen set selected in Step 1.
-
rtrv-scr-aftpc -
rtrv-scr-blkdpc -
rtrv-scr-blkopc -
rtrv-scr-cdpa -
rtrv-scr-cgpa -
rtrv-scr-dpc -
rtrv-scr-destfld -
rtrv-scr-opc -
rtrv-scr-tt -
rtrv-scr-sio
-
-
Delete any entries in the gateway screening entities displayed in Step 2 that reference the screen set name selected in Step 1. This includes the screen set itself. Refer to the Database Administration - GWS User's Guide for assistance
-
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - For a Global Title Translation Type
2.2.509 E2558 Cmd Rej: Point code already exists in given SR
The specified point code cannot already exist in the screening reference. If asterisks or ranges are specified for the point code, nothing that matches the specified range or point codes can already exist in the screening table for the screening reference.
If the SR already exists, the blocked OPC cannot be defined as specified or exist within an existing range of OPCs. The blocked OPC that was intended to be added to the BLKOPC screening table for the blocked OPC SR was specified by one of these parameter sets: ni-nc-ncm, zone-area-id, msa-ssa-sp, or npc.
Recovery
- Display the screening reference data. Enter the appropriate
rtrv-command (for example, if theent-scr-blkdpccommand generated the error message, then enter thertrv-scr-blkdpccommand). - Re-enter the command that generated this error message, specifying a different point code for the screening reference. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.510 E2559 Cmd Rej: PC/SSN does not exist in given SR
The point code/subsystem number combination (ni, nc, ncm, ssn) must already exist in the specified screening reference.
OR
The AFTPC or AFTPC range defined by the one of the four point code types represented (ni-nc-ncm, zone-area-id, msa-ssa-sp, or npc) must already exist in the screening reference before the command can be entered.
Recovery
- Display the screen set data. Enter the appropriate
rtrv-command (for example, if thechg-scr-blkdpccommand generated the error message, then enter thertrv-scr-blkdpccommand). - 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 and to the Database Administration - GWS User's Guide for assistance.
2.2.511 E2561 Cmd Rej: PC/SSN already exists in given SR
The value specified for the point code or subsystem parameter cannot already exist in the specified screening reference.
Recovery
- Display the point code/subsystem number combinations. Enter the appropriate
rtrv-command (for example, if thechg-scr-cdpacommand generated the error message, then enter thertrv-scr-scdpacommand). - 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 and to the Database Administration - GWS User's Guide for assistance.
2.2.512 E2562 Cmd Rej: A specific PRI must be specified in the range (0-3,*)
For a SEAS command, the pri parameter specified must be in the range 0-3,*.
Recovery
Re-enter the command that generated this error message, specifying a valid value for the pri parameter. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.513 E2563 Cmd Rej: A specific H0 must be specified in the range (0-15,*)
For a SEAS command, the h0 parameter specified must be in the range 0-15,*.
Recovery
Re-enter the command that generated this error message, specifying a valid value for the h0 parameter. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.514 E2564 Cmd Rej: Point code out of range
A valid value must be specified for the point code. The following point codes are not allowed:
- ANSI point code value 000-000-000
- ITU-International point code value 0-000-0
Recovery
Re-enter the command that generated this error message, specifying the correct point code value. Refer to the command description in the Commands User's Guide for assistance.
2.2.515 E2565 Cmd Rej: Gateway screening rules table is full
If the Gateway Screening Rules table is full, then a gateway screening entry cannot be added. The Gateway Screening Rules table can contain a maximum of 360,600 rules. To add another gateway screening entry, an existing gateway screening entry must be deleted or changed.
Recovery
2.2.516 E2566 Cmd Rej: A specific H1 must be specified in the range (0-15,*)
For a SEAS command, the h1 parameter specified must be in the range 0-15,*.
Recovery
Re-enter the command that generated this error message, specifying a valid value for the h1 parameter. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.517 E2567 Cmd Rej: Screen set name already exists
The value specified for the scrn parameter cannot already exist in the database.
Recovery
- Display the existing screen set data. Enter the
rtrv-scrsetcommand. - Re-enter the
ent-scrsetcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - GWS User's Guide for assistance.
2.2.518 E2568 Cmd Rej: Screen set name is referenced by a link set
A screen set that is assigned to a linkset cannot be deleted.
Recovery
2.2.519 E2569 Cmd Rej: SIO does not exist in given SR
The entry specified by the nic, si, h0, and h1 parameters must already exist in the database.
Recovery
- Display the SIO information for the specified screening reference. Enter the
rtrv-scr-siocommand. - Re-enter
chg/dlt-scr-siocommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - GWS User's Guide for assistance.
2.2.520 E2570 Cmd Rej: NIC, SI, and H0/H1 entry already exists in given SR
The combination of the nic, si, h0, and h1 parameters cannot already exist in the screening reference.
Recovery
- Display the SIO information for the specified screening reference. Enter the
rtrv-scr-siocommand. - Re-enter the
ent-scr-siocommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.521 E2571 Cmd Rej: SI does not exist for given SR
The specified si and sr combination must already exist in the database.
Recovery
- Display the existing SIO screening references and associated service indicators in the database. Enter the
rtrv-scr-siocommand. - Re-enter the
chg/dlt/rtrv-scr-siocommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.522 E2572 Cmd Rej: NIC and SI must be specified for given H0 and H1
If the h0 and h1 parameters are specified, then the si and nic parameters must be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.523 E2573 Cmd Rej: SR or NSR does not reference an existing SR
The screening reference specified by the sr or nsr parameter does not exist.
Recovery
2.2.524 E2574 Cmd Rej: TYPE does not exist in given SR
The value specified for the type parameter must already exist in the screening reference.
Recovery
- Display the translation types in the screening reference. Enter the
rtrv-scr-ttcommand. - Re-enter the
chg/dlt-scr-ttcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.525 E2575 Cmd Rej: TYPE matches existing TYPE in given SR
The value specified for the ntype parameter cannot already exist in the screening reference.
Recovery
2.2.526 E2577 Cmd Rej: A specific SSN must be specified in the range (1-255,*)
The ssn parameter must be specified and must have a value within the correct range.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.527 E2579 Cmd Rej: GWS must be ON if LAN is ON
The Gateway Screening feature must be turned on before the STP LAN feature can be turned on.
Note:
Once a feature that is controlled using a feature bit is turned on, it cannot be turned off.Recovery
2.2.528 E2580 Cmd Rej: A specific NIC must be specified in the range (0-3)
The nic parameter must be specified and must have a value within the correct range.
Recovery
Re-enter the dlt-scr-sio command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.529 E2581 Cmd Rej: CRMD feature must be ON
For the ent/chg-dstn commands, the Cluster Routing and Management Diversity (CRMD) feature must be turned on before before a cluster destination point code can be entered or changed.
For the chg-feat command, the CRMD feature must be turned on before the Nested Cluster Routing (NCR) feature can be turned on.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.530 E2582 Cmd Rej: RHOST and RPORT must be specified with TCP
For the ent-ip-conn command, RHOST and RPORT are mandatory parameters when PROT = TCP.
Recovery
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 and Database Administration - Features User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.531 E2584 Cmd Rej: GTT feature must be ON
The GTT feature must be turned on before a specific feature can be enabled or card type entered. Refer to the command description in Commands User's Guide for a list of features that require the GTT feature to be ON.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.532 E2585 Cmd Rej: GWS feature must be ON
For the enable-ctrl-feat command, the Gateway Screening (GWS) feature must be turned on before the feature can be enabled. Refer to the command description in Commands User's Guide for a list of features that require the GWS feature to be turned on.
For the ent-card command, the GWS feature must be turned on before a GLS card can be added to the database.
The GWS and STP LAN features must be turned on before the ent-dlk command can be entered.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.533 E2586 Cmd Rej: Host Name Referenced by Connection
For the dlt-ip-host command, before a local entry can be deleted from the IP Host table, all connection references to the hostname must be deleted. This rule does not apply to remote host entries.
Recovery
2.2.534 E2587 Cmd Rej: Card GPL of link does not match domain of linkset APC
The domain of the linkset specified by the lsn parameter must match the domain of the link specified by the link parameter.
Recovery
2.2.535 E2588 Cmd Rej: Connection Name already exists
For the ent-dconn command, a unique DCNAME must be specified for a new connection.
For the ent-ip-conn command, the CNAME connection should be unique for every new connection.
Recovery - ent-dconn
- Enter the
rtrv-dconncommand to display the diameter connection name in the database. - Re-enter the
ent-dconncommand with a new diameter connection name. Refer to the command description in Commands User's Guide for assistance.Contact My Oracle Support if this message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - ent-ip-conn
2.2.536 E2589 Cmd Rej: Maximum number of Connections provisioned
For the ent-ip-conn command, the number of CNAMES has reached the maximum limit. New connection can not be made.
Recovery
2.2.537 E2590 Cmd Rej: SIP Feature must be enabled
Recovery
2.2.538 E2591 Cmd Rej: SA SELSCR SA(X)DGTS value must be none or between 1-FF
chg-npp-srs command, only one call type can be specified for the SELSCR Service Action in the TIF NPP service rule. If the AS specified by the asn parameter contains the SELSCR Service Action, the corresponding SA Digit String specified must be between 1-FF or none.
For the ent-npp-srs command, only one call type can be specified for the SELSCR SA. If the AS specified by the asn parameter contains the SELSCR SA, the corresponding SA Digit String specified must be between 1-FF or none.
Recovery
2.2.539 E2592 Cmd Rej: Warm Restart capable Feature must be enabled
An EPAP-based feature or an LNP feature that is capable of warm restart must be enabled, SIP or DEIR must be enabled, at least one ENUM card must be present, or at least one GTT-enabled IPSG card must be present before this command can be entered with the data=persist parameter.
Recovery
2.2.540 E2593 Cmd Rej: APC cannot be of a different domain than previous
The specified adjacent point code (APC) must be in the same domain as the previous APC assigned to the linkset.
Recovery
2.2.541 E2594 Cmd Rej: Failed reading SIP Phone Context table
For the chg-sip-npp command, the SIP Phone Context table SIPPHCXT should be accessible.
For the dlt-sip-npp command, the SIP Phone Context table SIPPHCXT should be accessible.
For the ent-sip-npp command, the SIP Phone Context table SIPPHCXT should be accessible.
For the rtrv-sip-npp command, the SIP Phone Context table SIPPHCXT should be accessible.
Recovery
Re-enter the command that generated this error message. Refer to the command description in Commands User's Guide and Database Administration - Features User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.542 E2595 Cmd Rej: SS7 Destination assigned to non-SS7 linkset
If the route is assigned a destination that is marked for the SS7 domain, then the linkset assigned to that route must have an adjacent point code assigned to the SS7 domain.
Recovery
2.2.543 E2597 Cmd Rej: Cccmmd table must be accessible
The CCCMMD table must be accessible.
Recovery
Re-enter the chg/rtrv-cmd command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.544 E2598 Cmd Rej: Cccnames table must be accessible
The CCCNAMES table must be accessible.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.2.2.545 E2599 Cmd Rej: Failed reading the extended link table
The Extended Link table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.546 E2600 Cmd Rej: Linkset SAPC referenced by route
A Secondary Adjacent Point Code (SAPC) linkset cannot be deleted if a route exists for the linkset in the SAPC’s domain or group code.
Recovery
2.2.547 E2601 Cmd Rej: Command aborted due to system error
A severe system fault has occurred and the command was rejected.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.548 E2603 Cmd Rej: Card must be inhibited before executing this command
The specified card (other than OAM locations) must be in the OOS-MT-DSBLD (out of service - maintenance disabled) state before this command can be entered.
If the location specified by the loc parameter is an OAM card location, then the command can be entered while the card is IN-SR status (as DB modifications are not allowed while the OAM is inhibited). However, the card needs to be re-initialized after the command for the changes to take effect.
For the ent-slk command, the E5-ATM or E5-ATM-B card must be in the OOS-MT-DSBLD state before the card can support an A1 link.
Note:
This error message does not apply to HMUX, HIPR, or HIPR2 MUX cards for theinit-flash command.
Recovery
2.2.549 E2604 Cmd Rej: Card location not assigned a TCP/IP link
The specified card must contain a TCP/IP data link.
Recovery
2.2.550 E2607 Cmd Rej: IPADDR assigned to a TCP/IP node
The value specified for the ipaddr parameter cannot already exist in the TCP/IP Link table and cannot be a TCP/IP node.
Recovery
2.2.551 E2608 Cmd Rej: IPADDR not assigned to a TCP/IP link
The IP address specified for the ipaddr parameter must be the IP address of a TCP/IP node instead of a TCP/IP data link.
Recovery
2.2.552 E2609 Cmd Rej: Only one optional parameter may be specified
Only one optional parameter at a time can be specified in the command.
Recovery
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.
2.2.553 E2610 Cmd Rej: IPADDR assigned to a TCP/IP link
The value specified for the ipaddr parameter cannot already exist in the TCP/IP link table and cannot be a TCP/IP node.
Recovery
2.2.554 E2611 Cmd Rej: Total Ethernet Capacity is greater than 100% for IP Node
The value assigned to the cap parameter, when added to the values that were assigned when IP addresses were defined, cannot total more than 100.
Recovery
2.2.555 E2612 Cmd Rej: IPPORT already assigned
The IP port specified by the ipport parameter cannot already be assigned.
Recovery
2.2.556 E2613 Cmd Rej: IPPORT can only be specified if IPADDR is specified
If the ipport parameter is specified, then the ipaddr parameter must be specified.
Recovery
Re-enter the rtrv-ip-node command that generated this error message, specifying a valid combination of parameters. Refer to the Database Administration - Features User's Guide for assistance.
2.2.557 E2614 Cmd Rej: IPADDR w/o IPRTE must match first octet of TCP/IP link
The class of the IP address specified by the ipaddr parameter must match the class of the assigned TCP/IP data link's IP address. The system supports three classes of IP addresses: Class A, Class B, and Class C. Class A IP addresses can contain only the values 1 - 126 in the first field of the IP address. Class B IP addresses can contain only the values 128 - 191 in the first field of the IP address. Class C IP addresses can contain only the values 192 - 223 in the first field of the IP address.
Recovery
2.2.558 E2615 Cmd Rej: IPADDR w/o IPRTE must match first 2 octets of TCP/IP link
If the network portion and class of the IP address of the TCP/IP node matches the class of the assigned TCP/IP data link's IP address, the iprte parameter cannot be specified. The values of the ipaddr parameter, the IP address of the TCP/IP node, and the iprte parameter cannot be the same.
Recovery
2.2.559 E2616 Cmd Rej: IPADDR w/o IPRTE must match first 3 octets of TCP/IP link
The value specified for the network portion of the ipaddr parameter must match the network portion of the IP address assigned to the TCP/IP data link.
The network portion of the IP address is based on the class of the IP address. If the IP address is a Class A IP address, the first field is the network portion of the IP address. If the IP address is a Class B IP address, the first two fields are the network portion of the IP address. If the IP address is a Class C IP address, the first three fields are the network portion of the IP address.
Recovery
2.2.560 E2617 Cmd Rej: IPAPPL already assigned to specified LOC
The specified IP application specified by the ipappl parameter cannot already be assigned to the TCP/IP data link specified by the loc parameter.
Recovery
2.2.561 E2619 Cmd Rej: Only one of IPAPPL or IPPORT may be specified
The ipappl and ipport parameters cannot be specified toether in the command.
Recovery
Re-enter the dlt-ip-node command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.562 E2620 Cmd Rej: No optional parameters may be specified if FORCE=YES
If the force=yes parameter is specified, then the ipappl, ipport, or loc parameters cannot be specified.
Recovery
Re-enter the dlt-ip-node command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.563 E2621 Cmd Rej: FORCE=YES must be specified to delete entire node
Entering the command with only the ipaddr parameter is interpreted as an attempt to delete all connections from the specified IP node. To delete all connections from an IP node, the force=yes parameter must be specified.
Recovery
Re-enter the dlt-ip-node command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.564 E2622 Cmd Rej: IPADDR not assigned to specified LOC
If the loc parameter is specified, the card location must be equipped with a IP data link.
Recovery
2.2.565 E2623 Cmd Rej: IPPORT on node not assigned to specified LOC
If the ipport and loc parameters are specified, then the ipaddr/ipport combination must be assigned to the TCP/IP data link specified by the loc parameter.
Recovery
2.2.566 E2624 Cmd Rej: IPAPPL on node not assigned to specified LOC
If the ipappl and loc parameters are specified, then the ipaddr/ipappl combination must be assigned to the TCP/IP data link specified by the loc parameter.
Recovery
2.2.567 E2625 Cmd Rej: IPADDR not assigned to any TCP/IP link
The node specified by the ipaddr parameter must be connected to a TCP/IP data link.
Recovery
2.2.568 E2626 Cmd Rej: IPPORT on Node not connected to any TCP/IP link
The value specified for the ipport parameter must be assigned to a TCP/IP node, and that node must be connected to a TCP/IP data link.
Recovery
2.2.569 E2627 Cmd Rej: IPAPPL on node not connected to any TCP/IP link
The value specified for the ipappl parameter must be assigned to a TCP/IP node, and that node must be connected to a TCP/IP data link.
Recovery
- Display the TCP/IP nodes in the database. Enter the
rtrv-ip-nodecommand. - Re-enter the
dlt-ip-nodecommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.570 E2628 Cmd Rej: Only one of IPADDR, IPAPPL, IPRTE, or LOC can be specified
Only one of the ipaddr, ipappl, iprte, or loc parameters can be specified in the command.
Recovery
Re-enter the rtrv-ip-node command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.571 E2629 Cmd Rej: Card has IP LNK with IP address assigned
The specified card location has an IP link assigned to it. The card cannot be deleted from the database until the IP link is deleted from the database.
Recovery
2.2.572 E2630 Cmd Rej: IPADDR and IPRTE cannot be the same address
The same address cannot be specified for the ipaddr and the iprte parameters.
Recovery
2.2.573 E2631 Cmd Rej: Link must be cancelled before executing this command
All signaling or data links must be OOS-MT-DSBLD (out of service - maintenance disabled) before the dlt-dlk or inh-card command can be entered.
Recovery
2.2.574 E2632 Cmd Rej: IPRTE address assigned to TCP/IP Link
The router IP address must not be assigned to a local TCP/IP data link.
Recovery
- Display the TCP/IP data links in the database. Enter the
rtrv-dlkcommand. - Display the TCP/IP router addresses in the database. Enter the
rtrv-ip-nodecommand. - Re-enter the
ent-ip-nodecommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.575 E2633 Cmd Rej: IPRTE must use 1st octet of Class A TCP/IP Link
The network portion of the router IP address must match the network portion of the IP address assigned to the TCP/IP data link. The IP address assigned to the TCP/IP router is a Class A IP address. For a Class A IP address, the first field is the network portion of the IP address. The first field value of a Class A IP address is from 1 - 126. The values 0 and 127 are not allowed for IP addresses.
Recovery
2.2.576 E2634 Cmd Rej: IPRTE must use 1st 2 octets of Class B TCP/IP Link
The network portion of the value specified for the iprte parameter must match the network portion of the IP address assigned to the TCP/IP data link. The IP address assigned to the TCP/IP router is a Class B IP address. For a Class B IP address, the first two fields are the network portion of the IP address. The first field value of a Class B IP address is from 128 - 191.
Recovery
2.2.577 E2635 Cmd Rej: IPRTE must use 1st 3 octets of Class C TCP/IP Link
The network portion of the value specified for the iprte parameter must match the network portion of the IP address assigned to the TCP/IP data link. The IP address assigned to the TCP/IP router is a Class C IP address. For a Class C IP address, the first three fields are the network portion of the IP address. The first field value of a Class B IP address is 192 - 223.
Recovery
2.2.578 E2636 Cmd Rej: IPADDR assigned to a TCP/IP router
The IP address (ipaddr) cannot be in the TCP/IP link table and cannot be a TCP/IP router.
Recovery
- Display the existing TCP/IP router addresses. Enter the
rtrv-ip-nodecommand. - Re-enter the
ent-dlkcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.579 E2637 Cmd Rej: Failed reading SIP Prefix table
For the chg-sip-npp command, the SIP Prefix table SIPNNPFX should be accessible.
For the dlt-sip-npp command, the SIP Prefix table SIPNNPFX should be accessible.
For the ent-sip-npp command, the SIP Prefix table SIPNNPFX should be accessible.
For the rtrv-sip-npp command, the SIP Prefix table SIPNNPFX should be accessible.
Recovery
Re-enter the command that generated this error message. Refer to the command description in Commands User's Guide and Database Administration - Features User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.580 E2638 Cmd Rej: IPADDR already assigned to another TCP/IP link
The value specified for the ipaddr parameter cannot already be assigned to a TCP/IP data link.
Recovery
2.2.581 E2639 Cmd Rej: Failed reading redirect table
The Gateway Screening Redirect Function table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.582 E2640 Cmd Rej: Redirect function data has already been entered
Once specific gateway screening redirect function data is entered, the same ent-gws-redirect command cannot be entered again.
Recovery
2.2.583 E2641 Cmd Rej: Redirect function data has not been entered
The chg/dlt-gws-redirect commands can be entered only if the gateway screening redirect function data has been previously entered with the ent-gws-redirect command.
Recovery
No action is necessary.
2.2.584 E2642 Cmd Rej: DPC must have at least one route defined
The value specified for the destination point code parameter must have at least one route assigned to it.
For the ent/dlt/rtrv-pct command, the values specified for the realpc/realpca/realpci/realpcn and filtpc/filtpca/filtpci/filtpcn parameters must have at least one route for each value defined in the Route table.
For the chg-stpopts command, if the gdpc/gdpca/gdpci/gdpcn/gdpcn24/gdpcn16 parameter is defined as a destination, it must have at least one route defined.
Recovery
2.2.585 E2643 Cmd Rej: Cannot delete last route to DPC ref. in MAP table
The last route for the specified destination point code being removed cannot be referenced by a mated application or a concerned signaling point code. If any destinations referencing the specified routset exist in the MAP table, then the last route of the routeset cannot be deleted.
Recovery
2.2.586 E2644 Cmd Rej: SIP Phone Context table is full
For the ent-sip-npp command, the SIP Phone Context table SIPPHCXT has reached its maximum limit.
Recovery
2.2.587 E2645 Cmd Rej: Cannot delete last route to DPC ref. by redirect func
The last route to a destination referenced by the redirect function destination parameter cannot be deleted.
Recovery
2.2.588 E2646 Cmd Rej: SIP Prefix table is full
For the ent-sip-npp command, the SIP Prefix table SIPNNPFX as it has reached its maximum limit.
Recovery
2.2.589 E2647 Cmd Rej: Only one of PCN or PCN24 may be specified
The pcn and pcn24 parameters cannot be specified together in the command.
Recovery
Re-enter the ent/chg-sid command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.590 E2648 Cmd Rej: Failed reading the route table
The Route table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.591 E2649 Cmd Rej: Failed reading DBMM 2 table
For the chg-sip-npp command, the SIP DBMM 2 table should be accessible.
For the dlt-sip-npp command, the SIP DBMM 2 table should be accessible.
For the ent-sip-npp command, the SIP DBMM 2 table should be accessible.
For the rtrv-sip-npp command, the SIP DBMM 2 table should be accessible.
Recovery
Re-enter the command that generated this error message. Refer to the command description in Commands User's Guide and Database Administration - Features User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.592 E2651 Cmd Rej: SIP Prefix entry already exists
For the ent-sip-npp command, the SIP prefix should be unique for a phone-context. Prefix value can not be duplicated for the same phone context.
Recovery
2.2.593 E2654 Cmd Rej: Assigned PFXs must be deleted before PHCTXT can be deleted
For the dlt-sip-npp command, the Phone Context can not be deleted if it still has some Prefix assigned to it.
Recovery
2.2.594 E2655 Cmd Rej: SIP Prefix entry does not exist
For the chg-sip-npp command, the SIP Prefix entry requested does not exist in the SIPNNPFX table.
For the dlt-sip-npp command, the SIP Prefix entry requested does not exist in the SIPNNPFX table.
For the rtrv-sip-npp command, the SIP Prefix entry requested does not exist in the SIPNNPFX table.
Recovery
Refer to the command description in Commands User's Guide and Database Administration - Features User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.595 E2656 Cmd Rej: SIP Phone Context entry does not exist
For the chg-sip-npp command, the SIP Phone Context entry requested does not exist in the SIPPHCXT table.
For the dlt-sip-npp command, the SIP Phone Context entry requested does not exist in the SIPPHCXT table.
For the rtrv-sip-npp command, the SIP Phone Context requested does not exist in the SIPPHCXT table.
Recovery
Refer to the command description in Commands User's Guide and Database Administration - Features User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.596 E2657 Cmd Rej: Point code not defined
The value specified for the Point Code parameter must already exist in the associated point code table.
For the
chg-stpopts command, the
gdpc/gdpca/gdpci/gdpcn/gdpcn24/gdpcn16 parameter must
be defined in the Destination table or defined as the STP site point code.
For the
dlt-mate-stp command, the
pc/pca/pci/pcn/pcn24/pcn16 parameter must be
defined in the Mate STP table.
Recovery
2.2.597 E2658 Cmd Rej: LHOST and LPORT combination already has connection
For the ent-ip-conn command, duplicate LHOST, RHOST, LPORT and RPORT entry combination is not allowed with PROT=TCP or PROT=UDP with RHOST, RPORT specified.
Recovery
2.2.598 E2659 Cmd Rej: SIP Phone Context must be specified
For the rtrv-sip-npp command, the SIP Phone Context (PHCTXT) must be specified if the SIP Prefix (PFX) is specified.
Recovery
Refer to the command description in Commands User's Guide and Database Administration - Features User's Guide for assistance. Re-enter the command that generated this error message, specifying a valid combination.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.599 E2661 Cmd Rej: 1M System TPS feature requires HIPR2 high rate feature ON
For chg-ctrl-feat command, the 1M System TPS feature requires HIPR2 high rate mode feature to be ON.
For chg-ctrl-feat command, the HIPR2 high rate mode feature can not be OFF if 1M System TPS feature is turned ON.
Recovery
2.2.600 E2662 Cmd Rej: Feat can not be turned off if system IP/ATM TPS exceeds 750K
For chg-ctrl-feat command, the 1M System TPS feature can not be deactivated, if the system TPS is more than 750K.
Recovery
2.2.601 E2663 Cmd Rej: Only Dual ExAP Config feature should be Enabled
For the rept-stat-mfc command, the service=SCPEPAP parameter can not be specified if both EPAP Data Split and Dual ExAP Config features are enabled.
For rept-stat-sccp command, the data=EPAP parameter can not be specified if EPAP Data Split and Dual ExAP Config features are enabled.
Recovery
2.2.602 E2665 Cmd Rej: SRVNAME must be specified with E5APPB Card/Telco Switch
For the ent-card command, the SRVNAME must be specified with E5APPB Card / Telco Switch.
Recovery
Re-enter the command that generated this error message, specifying a valid SRVNAME and other combination of parameters. Refer to the command description in the Commands User's Guide.
Contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.603 E2666 Cmd Rej: SRVNAME already exists
For the ent-card command, the SRVNAME already exists.
Recovery
2.2.604 E2667 Cmd Rej: Same Power source of E5APPB cards running same application
For the ent-card command, the E5APPB application cards can not have the same power source, if force parameter is not specified.
Recovery
Re-enter the command that generated this error message with force=yes parameter. Refer to the command description in the Commands User's Guide and to the Database Administration - System Management User's Guide for assistance. .
Contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.605 E2668 Cmd Rej: Failure accessing IPCONN table
For the
chg-ip-conn command, the IPCONN table
should be accessible.
For the
dlt-ip-conn command, the IPCONN table
should be accessible.
For the
dlt-ip-host command, before deleting an IP Host
table entry, all connection references to the hostname are checked in the
IPCONN table. The IPCONN table must be accessible.
For the
ent-ip-conn command, the IPCONN table
should be accessible.
For the
rtrv-ip-conn command, the IPCONN table
should be accessible.
Refer to the command description in Commands User's Guide and Database Administration - Features User's Guide for assistance. Re-enter the command that generated this error message, specifying a valid combination of parameters.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.606 E2669 Cmd Rej: Cannot set DefCC to NONE if SIPNP is ON
For the chg-stpopts command, the defcc=none parameter can not be specified if the SIPNP feature is turned ON.
Recovery
2.2.607 E2670 Cmd Rej: Invalid value of DATA parameter for given APPL
If the IPSG32 GPL is running on the location specified by the loc parameter, then gtt and nosccp are the only valid values for the DATA parameter. If the GPL is anything but the IPSG32 GPL, the data=nosccp parameter cannot be used for the card at that location.
For the
chg-card command, if the card is
type=slic with
data=gtt and is changed to
type=enet/enetb, then
data must be changed to
nosccp first.
For the
ent-card command, the
DATA parameter can only be equal to
DN or
ELAP when the
type=dsm and
appl=siphc parameters are specified.
For the
rept-stat-card command, the
data=nosccp parameter can be
specified only when the
appl=ipsg parameter is specified.
Recovery
2.2.608 E2672 Cmd Rej: SIP Phone Context already exists
For the ent-sip-npp command, the Phone Context should be unique.
Recovery
2.2.609 E2673 Cmd Rej: Default Phone Context cannot be deleted
For the dlt-sip-npp command, the Default Phone Context cannot be deleted from the SIPPHCXT table.
Recovery
2.2.610 E2674 Cmd Rej: Connection parameters must be unique
For the ent-ip-conn command, the LHOST, RHOST, LPORT and RPORT entry combination must be unique for each IP connection if PROT=TCP is specified or the RHOST, RPORT entry combination must be unique if PROT=UDP is specified.
Recovery
2.2.611 E2675 Cmd Rej: Shelf locations 6200 and 6300 are reserved for FPB shelf
For the ent-shlf command, shelf locations 6200 and 6300 are reserved for shelf type FPB only.
Recovery
2.2.612 E2676 Cmd Rej: Telco Switch can be provisioned only in FPB shelf
For the ent-card command, the Telco Switch can only be provisioned in FPB shelf.
Recovery
2.2.613 E2677 Cmd Rej: E5APPB card and Telco Switch are not allowed in same shelf
For the ent-card command, the E5APPB card and Telco Switch can not be provisioned in the same shelf.
Recovery
2.2.614 E2678 Cmd Rej: Maximum 6 TELCO Switches can be provisioned in a shelf
For the ent-card command, a maximum of 6 Telco switches are allowed in a shelf.
Recovery
2.2.615 E2679 Cmd Rej: RPORT and RHOST are required together
For the ent-ip-conn command, the PROT=UDP requires both RHOSTand RPORT entry combinations.
Recovery
2.2.616 E2680 Cmd Rej: OAM IP Security Feature must be activated.
For the chg-ftp-serv command, the OAM IP Security Feature must be activated.
For the chg-secu-dflt command, the OAM IP Security Feature must be activated.
For the ent-ftp-serv command, the OAM IP Security Feature must be activated.
Recovery
2.2.617 E2681 Cmd Rej: FPB shelf is reserved for E5APPB card/Telco Switch
For the ent-card command, the FPB Shelf is reserved for E5APPB cards and Telco Switches only.
Recovery
2.2.618 E2682 Cmd Rej: Cannot delete an open Connection
dlt-dconn command, any diameter connection that is still OPEN to receive traffic cannot be deleted (the open parameter set to yes with the chg-assoc command).For the dlt-ip-conn command, the connection that is still OPEN to receive traffic can not be deleted.
Recovery - dlt-dconn
- Enter the
rtrv-dconncommand to display the diameter connections and SCTP association. - Enter the
rtrv-assoc:aname=<association name associated with diameter connection>command to display the open status. - Enter the
chg-assoc:aname=<association name associated with diameter connection>:open=nocommand to close the open connection. - 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 and Database Administration - Features User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - dlt-ip-conn
2.2.619 E2683 Cmd Rej: LHOST has open connection
chg-ip-lnk command, the local IP address can not be changed if the current or new local host has open connections.
Recovery
2.2.620 E2684 Cmd Rej: Specified Lhost is not valid for Card and Appl Type
Connections can be made only with an LHOST that is configured on a SIP card.
Recovery
- Use the
rtrv-ip-hostcommand to locate a LHOST on a SIP card. - If no LHOST is present on a SIP card, then configure one with the
ent-ip-hostcommand. - Re-enter the command that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.621 E2685 Cmd Rej: Remote IP address exists in the IPLINK table
ent-ip-conn command, theThe remote IP address (RHOST) must not exist in the IPLINK table.
Recovery
2.2.622 E2686 Cmd Rej: Both NPDS and NPDD can not be set to default values
For the chg-sip-npp command, at least one NPDD or NPDS must be specified with non-default (other than 0, NONE) value.
For the ent-sip-npp command, at least one NPDD or NPDS must be specified with non-default (other than 0, NONE) value.
Recovery
2.2.623 E2687 Cmd Rej: Inhibit IPSM card(s) before changing the value of param SSH
For the chg-secu-dflt command, the value of parameter SSH can be changed to ON/OFF once the type IPSM cards are inhibited.
Recovery
2.2.624 E2688 Cmd Rej: SIP not Configured
For the rept-stat-ipconn the SIP card running the SIPHC application must be configured before this command can be entered.
For the rept-stat-sip the SIP card running the SIPHC application must be configured before this command can be entered.
Recovery
2.2.625 E2689 Cmd Rej: Card(s) provisioned in shelf require FAN
For the chg-shlf command, the Shelf FAN bit can not be turned OFF, if an EPM-B based card(s), a HC-MIM card(s) or an E5-APP-B card(s) is provisioned on the shelf.
Recovery
2.2.626 E2690 Cmd Rej: E5-SM4G Throughput Cap qty 6800 or above must be enabled
For the chg-stpopts command, to allow ANSI GFLEX and other EPAP based features to co-exist the E5-SM4G Throughput Cap quantity key for 6800 must be enabled.
For the enable-ctrl-feat command, to allow ANSI GFLEX and other EPAP based features to co-exist the E5-SM4G Throughput Cap quantity key for 6800 must be enabled.
Recovery
2.2.627 E2691 Cmd Rej: J7 Support Feature must be enabled
The J7 Support Feature must be enabled to enter any ITU-N 16-bit Point Code.
Recovery
2.2.628 E2693 Cmd Rej: FWORD is not supported at this time
Memory Type of FWORD is NOT supported at this time.
Recovery
Re-enter the set-mem command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.629 E2694 Cmd Rej: Invalid combination of ADDR and PADDR specified
The addr and paddr parameters cannot be specified together in the command.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.630 E2695 Cmd Rej: DPADDR cannot be entered with DR/DRARM/DA
If the da, dr, or drarm parameter is specified, then the dpaddr parameter cannot be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.631 E2696 Cmd Rej: REP cannot be specified when DUR=PERM
If the dur=perm parameter is specified, then the rep parameter cannot be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.632 E2697 Cmd Rej: IND cannot be greater than 3
The value specified for the ind parameter cannot be greater than 3.
Recovery
Re-enter the ent-bp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.633 E2698 Cmd Rej: DUR=PERM cannot be specified with P186 or P286
If the value of the processor type portion of the type parameter is p186 or p286, then the dur=perm parameter cannot be specified.
Recovery
Re-enter the ent-bp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.634 E2699 Cmd Rej: DATA cannot be specified with TYPE = P186, P286, or IXP
The value data can be specified for the breakpoint-type portion of the type parameter only if the value p486 is specified for the processor-type portion of the type parameter.
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.635 E2700 Cmd Rej: ACCESS can only be specified with TYPE=P486-DATA or ARM-DATA
A value of p486-data or arm-data must be specified for the type parameter before the access parameter can be specified.
Recovery
Re-enter the ent-bp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.636 E2701 Cmd Rej: Meas Platform feature must be ON
The Measurements Platform feature must be turned on before the ent-card command can be entered for a type MCPM card (E5-MCPM-B).
For the chg-measopts command, the Measurements Platform feature must be turned on before the platformenable=on parameter can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.637 E2702 Cmd Rej: At least one MCPM card must be configured in system
At least one type MCPM card (E5-MCPM-B) must be configured in the system if the Measurements Platform feature is turned on before the rept-stat-meas command can provide status for the feature.
Recovery
2.2.638 E2703 Cmd Rej: Missing parameter - DPADDR or DR
The dpaddr or dr parameter must be specified.
Recovery
Re-enter the ent-bp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.639 E2704 Cmd Rej: Invalid IPADDR
A command was entered for an IP address that does not exist in the database, or a value was specified that does not conform to the naming conventions.
Recovery
Re-enter the command that generated this error message, specifying a valid IP address that conforms to the naming conventions. Refer to the command description in Commands User's Guide and to Database Administration - Features User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.640 E2705 Cmd Rej: IP Node Address never entered or Card DB corrupt
The IP address specified by the ipaddr parameter must match the IP address of the remote IP node for the card specified by the loc parameter.
Recovery
2.2.641 E2706 Cmd Rej: APPL is invalid for report or entity
The value of the appl parameter must apply to the reports specified for the enttype and type parameters.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.642 E2707 Cmd Rej: LOC is invalid for specified report TYPE
The type=systot and loc parameters cannot be specified together in the command.
Recovery
Re-enter the rept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Measurements Reference for assistance.
2.2.643 E2708 Cmd Rej: APPL or LOC must be specified
The appl and loc parameters cannot be specified together in the command.
Recovery
Re-enter the rept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Measurements Reference for assistance.
2.2.644 E2709 Cmd Rej: APPL is invalid for specified PERIOD
The appl parameter can be specified only with the period=last or period=specific parameter.
Recovery
Re-enter the rept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Measurements Reference for assistance.
2.2.645 E2710 Cmd Rej: Cannot assign ITU and ANSI LHOST to the same AS
For the chg-assoc command, the current lhost and the specified new lhost must run the same type of application (ITU or ANSI).
For the ent-as command, the associations assigned to the specified M3UA/SUA association (adapter type) cannot be assigned to a different local host type than the local host type for the associations for the M3UA/SUA associations (adapter type) already assigned to the AS (ITU or ANSI).
Recovery - chg-assoc
-
Display the IP address for the current and new association local hosts. Enter the
rtrv-ip-hostcommand -
Display the card location for each local host IP address from Step 1. Enter the
rtrv-ip-lnkcommand. -
Display the application that is running on each local host card. Enter the
rtrv-cardcommand.The SS7IPGW and IPLIM applications are ANSI, and the IPGWI and IPLIMI applications are ITU.
-
Re-enter the
chg-assoccommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - ent-as
2.2.646 E2711 Cmd Rej: Invalid parameter
The specified parameter is not recognized by the software.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.647 E2712 Cmd Rej: RESETCHAR not valid with ACTION=CREATE
If the action=create parameter is specified, then the name, ext, and filelength parameters must be specified. All other parameters are ignored or defaulted.
Recovery
Re-enter the chg-tbl command that generated this error, specifying a valid combination of parameters.
Note:
Contact My Oracle Support before entering thechg-tbl command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.648 E2713 Cmd Rej: FILELENGTH not valid with ACTION=RESET
If the action=reset parameter is specified, then the id parameter must be specified. All other parameters are ignored or defaulted.
Recovery
Re-enter the chg-tbl command that generated this error message, specifying a valid combination of parameters.
Note:
Contact My Oracle Support before entering thechg-tbl command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.649 E2714 Cmd Rej: NAME not valid with ACTION=RESET
If the action=reset parameter is requested, then the id parameter must be entered. All other parameters are ignored or defaulted.
Recovery
Re-enter the chg-tbl command that generated this error message, specifying a valid combination of parameters.
Note:
Contact My Oracle Support before entering thechg-tbl command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.650 E2715 Cmd Rej: EXT not valid with ACTION=RESET
If the action=reset parameter is specified, then the id parameter must be specified. All other parameters are ignored or defaulted.
Recovery
Re-enter the chg-tbl command that generated this error message, specifying a valid combination of parameters.
Note:
Contact My Oracle Support before entering thechg-tbl command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.651 E2716 Cmd Rej: RESETCHAR not valid with ACTION=RENAME
If the action=rename parameter is specified, then the id, name, and ext parameters must be specified. All other parameters are ignored or defaulted.
Recovery
Re-enter the chg-tbl command that generated this error message, specifying a valid combination of parameters.
Note:
Contact My Oracle Support before entering thechg-tbl command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.652 E2717 Cmd Rej: filelength not valid with ACTION=RENAME
If the action=rename parameter is specified, then the id, name, and ext parameters must be specified. All other parameters are ignored or defaulted.
Recovery
Re-enter the chg-tbl command that generated this error message, specifying a valid combination of parameters.
Note:
Contact My Oracle Support before entering thechg-tbl command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.653 E2719 Cmd Rej: REDIRECT can only be specified with ANSI point codes
The value specified for the dpc parameter must be an ANSI point code with at least one assigned route.
Recovery
2.2.654 E2720 Cmd Rej: 386/486 register cannot be specified
For 80286 processors, 80386 or 80486 registers cannot be specified.
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.655 E2721 Cmd Rej: Integer value must be less than 65535
For 80286 processors, integer values for registers and conditions must be less than 65535.
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.656 E2723 Cmd Rej: Password operations not allowed on a non-secure terminal
The OA&M IP Security Enhancements feature must be turned on before passwords can be created or modified from a Telnet terminal (terminal IDs 17 - 40).
Recovery - login command
Login from a serial terminal (terminal IDs 1 - 16).
Recovery - chg-pid command
2.2.657 E2724 Cmd Rej: S13 Feature Must Be Enabled
For the chg-dconn command, the S13/S13' Int for EIR feature must be enabled before changing any parameter of a diameter connection.
For the chg-deiropts command, the S13/S13' Int for EIR feature must be enabled before changing any DEIR configuration.
For the dlt-dconn command, the S13/S13' Int for EIR feature must be enabled before deleting any existing diameter connection.
For the ent-card command, the S13/S13' Int for EIR feature must be enabled before the type=dsm and appl=deirhc parameters can be specified.
For the ent-dconn command, the S13/S13' Int for EIR feature must be enabled before entering any diameter connection.
For the rtrv-dconn command, the S13/S13' Int for EIR feature must be enabled before retrieving any diameter connection entry.
For the rtrv-deiropts command, the S13/S13' Int for EIR feature must be enabled before retrieving Diameter EIR configuration options.
Recovery
2.2.658 E2725 Cmd Rej: ANSI site id not defined
The ANSI self-ID destination point code for the STP must be defined before ANSI destinations can be changed.
Recovery
2.2.659 E2726 Cmd Rej: ITU-INTL site id not defined
The ITU-I self-ID destination point code (DPC) for the STP must be defined before ITU-I destinations can be changed.
Recovery
2.2.660 E2727 Cmd Rej: ITU-NATL site id not defined
The ITU-N self-ID destination point code (DPC) for the STP must be defined before ITU-I destinations can be changed.
2.2.661 E2728 Cmd Rej: S13 Feature Must Be Activated
For the alw-card command, the S13/S13' Int for EIR feature must be activated before allowing a card running DEIRHC/DEIR64 GPL.
For the chg-mtc-measopts command, the S13/S13' Int for EIR feature must be turned on before the mtchdeir=on parameter or the mtcddeir=on parameter can be specified.
For the rept-ftp-meas command, the S13/S13' Int for EIR feature must be activated before the enttype=deir and type=mtch/mtcd parameters can be specified.
For the rept-stat-deir command, the S13/S13' Int for EIR feature must be activated before retrieving the overall status of DEIR cards.
Recovery
2.2.662 E2730 Cmd Rej: Invalid Realm
A valid value must be specified for the realm parameter. The value must start with a letter and can contain up to 60 characters. Allowed characters are a-z, A-Z, 0-9, and - (dash). If the realm contains a dash, then the realm must be enclosed within quotation marks.
Recovery
2.2.663 E2731 Cmd Rej: RHOST required for DIAM association
RHOST is a mandatory parameter for DIAM association.
Recovery
2.2.664 E2732 Cmd Rej: RSVDTPS must be less than or equal to MAXTPS
RSVDTPS of a diameter connection must be less than or equal to MAXTPS.
Recovery
2.2.665 E2733 Cmd Rej: The T1PORT at the specified location is already equipped
The port specified by the t1port parameter cannot be already equipped with a T1 interface.
Recovery
2.2.667 E2736 Cmd Rej: All signaling links serviced by the T1 must be deactivated
For the chg-t1 command, all signaling links that are serviced by the specified T1 card (loc parameter) must be deactivated before the values for the encode, t1tsel, ll, and framing parameters can be changed.
For the inh-card command, if the card is type LIMT1, all signaling links providing timeslots serviced by the T1 interfaces assigned to the card must be deactivated, unless the force=yes parameter is specified.
Recovery
2.2.668 E2737 Cmd Rej: The T1PORT at the specified location is not equipped
For the chg/dlt/rtrv-t1 commands, the port specified by the t1port parameter must have already been configured with a T1 interface on the specified T1 card.
For the ent-slk command, the T1 interface on the card at the location specified by the loc parameter must be defined before a signaling link can be assigned to the port.
Recovery
2.2.669 E2738 Cmd Rej: Can not inhibit IMT bus - alternate bus is in abnormal state
Cards that prevent the IMT buses from being inhibited during the upgrade cannot exist in the system.
Recovery
Caution:
It is strongly recommended that theact-upgrade command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.
2.2.670 E2739 Cmd Rej: T1 card location is unequipped
For the ent/chg/dlt/rtrv-t1 command, the card location specified by the loc parameter must be equipped.
For the ent-slk command, the T1 interface of the T1 card specified by the t1loc parameter must already be defined before a signaling link can be assigned to the card.
Recovery
2.2.671 E2740 Cmd Rej: The specified LOC only supports SLTC loopbacks
The tst-slk:loopback=sltc command can only be run on the LIME1, LIIMT1, or LIMCH card types.
For IPSG M2PA signaling links or IPLHC signaling links where the ipliml2=m2pa parameter is specified, only the loopback=sltc test is allowed.
Recovery
2.2.672 E2742 Cmd Rej: T1 is assigned to card
Before a T1 card can be deleted, any T1 interfaces assigned to the card must be deleted.
Recovery
2.2.673 E2745 Cmd Rej: ALHOST is invalid without LHOST
The local host (lhost) must be configured before configuring the alternate local host (alhost).
Recovery
Re-enter the chg-assoc command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.674 E2746 Cmd Rej: TS value on the T1 already in use by a signaling link
The value specified for the ts parameter cannot already be assigned to a signaling link serviced by the T1 interface on the specified T1 card.
Recovery
2.2.675 E2747 Cmd Rej: FORCE=YES is required when card is allowed
The card in the location specified with the loc parameter must be inhibited for the dlt-ip-rte command to complete successfully. The force=yes parameter must be specified to enter the command when the card is allowed.
Recovery
2.2.676 E2748 Cmd Rej: T1 TS value must be specified in the range (1-24)
The ts parameter value for a T1 link must be in the range 1-24.
Recovery
Re-enter the ent-slk command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.677 E2749 Cmd Rej: Could not block link for testing
The command was unsuccessful. This error message may indicate a serious failure and require technical assistance.
Recovery
Wait for a brief period, and re-enter the command.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.678 E2750 Cmd Rej: UserID already logged on (or is logging on) another terminal
If a user is already logged on to a terminal, then the user cannot log on to another terminal. The user cannot change their password while being logged on to any terminal.
Recovery
2.2.679 E2751 Cmd Rej: UserID has been revoked
The user ID has been revoked by the systems administrator.
Recovery
Contact the systems administrator.
2.2.680 E2752 Cmd Rej: UserID has become obsolete and cannot be used
The number of days that have elapsed since the last successful login to the system exceeds the number established for the site.
Recovery
Contact the systems administrator.
2.2.681 E2753 Cmd Rej: Password does not contain enough alphabetic characters
The password must contain at least the number of alphabetic characters specified by the alpha parameter in the chg-secu-dflt command.
Recovery
2.2.682 E2754 Cmd Rej: Password does not contain enough numeric characters
chg-secu-dflt command.
Recovery
2.2.683 E2755 Cmd Rej: Password does not contain enough punctuation characters
The password must contain at least the number of punctuation characters specified by the punc parameter in the chg-secu-dflt command.
Recovery
2.2.684 E2756 Cmd Rej: Failed reading the password table
The Password table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.685 E2757 Cmd Rej: Invalid userID/password combination
The combination of user ID and password values must already exist in the database.
Recovery
- Contact the systems administrator to verify the correct user ID-password combination.
- Re-enter the
logincommand, specifying the assigned user ID and password combination.
2.2.686 E2758 Cmd Rej: ALPHA+NUM+PUNC must not be greater than 12
The password total of alphabetic, numeric, and punctuation characters cannot exceeds the system allowed maximum of 12.
Note:
Commandsent-user and chg-user are only available to the system administrator.
Recovery
Re-enter the ent/chg/act-user, chg-pid, or login command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.687 E2759 Cmd Rej: Revocation of security admin userID not allowed
The revoke=yes parameter cannot be specified for a user ID with system administration authorization.
Recovery
Re-enter the ent/chg-user command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
Note:
Theent/chg-user commands can be entered only by a use wirth system administration authority.
2.2.688 E2760 Cmd Rej: Failed reading the security defaults table
The Security Defaults table is corrupt or cannot be found by the system.
Recovery
- Re-enter the command that generated this error message.
- Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.689 E2761 Cmd Rej: Password cannot contain userID
The password cannot contain the associated User ID.
Recovery
2.2.690 E2762 Cmd Rej: Terminal temporarily disabled. Excessive LOGIN failures
The terminal is disabled because the login failure threshold level was exceeded.
Recovery
Contact the system administrator.
2.2.691 E2765 Cmd Rej: Invalid password. Keyboard is locked. Enter UNLOCK command
The password of the logged in user must be entered to unlock the keyboard.
Recovery
2.2.692 E2767 Cmd Rej: Keyboard is not locked
The keyboard is not locked, or the unlock command was entered at an OAP terminal. OAP terminals cannot be locked.
Recovery
The keyboard is not locked. No action required.
2.2.693 E2768 Cmd Rej: DURAL must be specified within 0..995959 or 999999
A valid value must be specified for the dural parameter.
Recovery
Re-enter the chg-trm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.694 E2769 Cmd Rej: Entry already exists for this application at this IP Address
An entry for the specified application ID at the specified IP address cannot already exist.
Recovery
2.2.695 E2770 Cmd Rej: Terminal temporarily disabled. Excessive UNLOCK failures
The terminal keyboard is locked and temporarily disabled because the number of failed unlock attemps exceeds the site-specified maximum.
Recovery
Contact the system administrator.
2.2.696 E2771 Cmd Rej: Both WRNLN and WRNTX must be specified
The wrnln and wrntx parameters must be specified together in the command.
Recovery
Re-enter the chg-secu-dflt command that generated this error message, specifying a valid combiation of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.697 E2772 Cmd Rej: Entry already exists for this application at this priority
An entry for the specified application ID at the specified priority cannot already exist.
Recovery
2.2.698 E2773 Cmd Rej: FTP Server table must be accessible
The FTP Server table must be accessible.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.699 E2774 Cmd Rej: FTP Server table entry not found for this APP/IPADDR
For the act-ftp-trns command, the FTP Server table must contain at least one FTP server entry that specifies the user application.
For the act-upgrade command, the ent-ftp-serv:app=dist command must be entered before a value of getrel or chkrel can be specified for the action parameter.
Caution:
It is strongly recommended that this command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.The DB application server must be provisioned (see the ent-ftp-serv command) before the chg-db:action=backup:dest=server or chg-db:action=restore:src=server command can be entered.
For the chg/dlt-ftp-serv command, the specified FTP server entry must already exist in the FTP Server table for the specified IP address and application.
Recovery
2.2.700 E2775 Cmd Rej: Cannot change terminal authority while user is logged on
Terminal access rights cannot be changed while a user is logged on to that terminal.
Recovery
- Display the users that are logged into the system Enter the
rept-stat-usercommand. - Re-enter the
chg-secu-trmcommand that generated this error message when the user ID for the terminal of interest is logged off.
2.2.701 E2776 Cmd Rej: At least two ports must have security admin authority
At least two terminals must be configured as security administration terminals in case one of the terminals has a hardware failure.
Recovery
2.2.702 E2777 Cmd Rej: Cannot change TYPE as system requires 2 SA enabled terminals
The system requires that at least two terminals be configured as security administration terminals. If only two security administration terminals are configured, then the value of the type parameter cannot be changed to a value that would make the terminal unusable (printer, or none) because only one security administration terminal would remain.
Recovery
2.2.703 E2778 Cmd Rej: Max number of entries exist in FTP Server table
A maximum of 10 FTP servers can be entered in the FTP Server table.
Recovery
2.2.704 E2779 Cmd Rej: Max number of FTPSERV table entries exist for this APP
The FTP Server table can contain entries for a maximum of 10 FTP servers: however, the number of FTP servers supported by an application may be less than 10. Entries that are made for an application cannot be made for more than the maximum number of FTP servers supported by the application.
- The Measurements Platform Application (app=meas) supports 3 FTP servers.
-
The FTP-based Table Retrieve Application (FTRA) (app=user) supports 2 FTP servers.
-
The Database (app=db) and Software Distribution (app=dist) applications each support 1 FTP server.
- The SS7 Firewall Logging application (app=sflog) supports 2 Secure FTP servers.
Note:
Refer to the command description in Commands User's Guide and to the Database Administration - System Management User's Guide for assistance with theent-ftp-serv command.
Recovery
- Display the FTP servers currently entered in the FTP Server table. Enter the
rtrv-ftp-servcommand. - Delete an existing FTP server for the application.
- Re-enter the
ent-ftp-servcommand that generated this error message.
2.2.705 E2780 Cmd Rej: DFLTACT must be specified as FORWARD, DUPLICATE, or DUPDISC
If the mapset, ri, or tt parameter is specified, then a value of forward, duplicate, or dupdisc must be specified for the dfltact parameter.
Recovery
Re-enter the ent-gsms-opcode command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.706 E2781 Cmd Rej: NDFLTACT parameter must be FORWARD, DUPLICATE, or DUPDISC
The ndfltact parameter must have a value of forward, duplicate, or dupdisc before the nmapset, nri, and ntt parameters or the pc or ssn parameter can be specified.
Recovery
2.2.707 E2782 Cmd Rej: Failed reading IPAPSOCK table
The IPAPSOCK table should be accessible.
Recovery
2.2.708 E2783 Cmd Rej: DCNAME not present in DCONN table
The diameter connection name specified for the DCNAME parameter must already exist in the DCONN table.
Recovery
2.2.709 E2784 Cmd Rej: Cannot switch between ITU-N and ITU-N24 site id assignments
If a 14-bit ITU-N site ID currently exists, it must be disabled before a 24-bit ITU-N site ID can be assigned.
If a 24-bit ITU-N site ID currently exists, it must be disabled before a 14-bit ITU-N site ID can be assigned.
Recovery
2.2.710 E2785 Cmd Rej: ITU-N 24bit site id not defined
A 24-bit ITU-N self-ID destination point code for the STP must be defined before 24-bit ITU-N destinations can be entered.
Recovery
2.2.711 E2786 Cmd Rej: One PC parameter required with ALL parameter
If the all=yes parameter is specified, then the pc parameter must be specified, and the pc1/pc2/pc3/pc4 parameters cannot be specified.
Recovery
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.
2.2.712 E2787 Cmd Rej: PC network type does not match existing PC network type
For the ent/chg-mrn commands, the apca and pcn24 parameters cannot be specified for the same MRN set.
For the chg-sccp-serv command, the specified point code network type must match an existing point code network type.
Recovery
2.2.713 E2788 Cmd Rej: Invalid Loopback selection for LIME1ATM
If an E1-ATM card is used, then a value of payload or line cannot be specified for the loopback parameter.
Recovery
2.2.714 E2789 Cmd Rej: AMGTT/AMGTT CdPA Only/AMGTT CgPA Upgrade must be ON
The AMGTT, AMGTT CdPA Only, or AMGTT CgPA Upgrade feature must be ON before any of the parameters in the chg/ent-gtmod commands, except for the ntt parameter, can be specified.
Recovery
2.2.715 E2791 Cmd Rej: DEIR not Configured
No Diameter EIR card running DEIRHC/DEIR64 gpl is configured.
Recovery
2.2.716 E2792 Cmd Rej: Association already assigned to Connection
For the dlt-assoc command, an association that is already assigned to a diameter connection in the DCONN table cannot be deleted from the IPAPSOCK table.
For the ent-dconn command, ANAME cannot be assigned to another diameter connection.
Recovery - dlt-assoc
- Enter the
rtrv-dconncommand to display the associations for diameter connections. - Enter the
dlt-dconn:dcname=<connection name for association to be deleted> command to delete the diameter connection entry. - Re-enter the command that generated this error message.
Refer to the command description in Commands User's Guide and Database Administration - Features User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - ent-dconn
2.2.717 E2799 Cmd Rej: Association adapter is not DIAM
The adapter for the association linked to a diameter connection on a DEIR card must be of type DIAM.
Recovery
2.2.718 E2801 Cmd Rej: J7 Support feature must not be Enabled
If the J7 support feature is already enabled, an ANSI or ITU-N24 SID cannot be provisioned.
Recovery
- If this error message appears, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.719 E2802 Cmd Rej: J7 Support feature can not be Enabled
If an ANSI or ITU-N24 SID is already provisioned, then the J7 support feature cannot be enabled.
Recovery
2.2.720 E2803 Cmd Rej: EIR or S13 feature must be ON
If the imei parameter is specified, the EIR feature or S13 feature must be turned on.
Recovery
2.2.721 E2804 Cmd Rej: GFLEX or EIR or S13 feature must be ON
If the imsi parameter is specified, then the G-Flex feature, EIR feature, or S13 feature must be turned on.
Recovery
2.2.722 E2805 Cmd Rej: Host and Realm required for diameter connection
For the chg-assoc command, the realm must be associated with the RHOST specified in the IPHOST table for a diameter association.
For the ent-assoc command, LHOST with REALM and RHOST with REALM are mandatory parameters for an association with adapter type DIAM.
For the ent-ip-host command, HOST and REALM must be specified together for the host associated with a diameter connection.
Recovery - chg/ent-assoc
- Enter the
rtrv-ip-host:display=detailcommand to display the host configured in EAGLE. - Re-enter the command that generated this error message, specifying the proper LHOST and RHOST parameter values with which realm is associated.
Refer to the command description in Commands User's Guide and Database Administration - Features User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - ent-ip-host
2.2.723 E2806 Cmd Rej: ITU-N 16bit site id not defined
An ITU-N16 destination point code cannot be provisioned if an ITU-N16 site identification is not provisioned.
Recovery
2.2.724 E2807 Cmd Rej: Dual ExAP Config feature must NOT be Enabled
The ISUP NP with EPAP feature cannot be enabled once the Dual ExAP Config feature has been enabled.
Recovery
Enter the rtrv-ctrl-feat command to verify whether the Dual ExAP Config feature is enabled. If the Dual ExAP Config feature is enabled, contact My Oracle Support for a manual feature turn off.
After the Dual ExAP Config feature is turned off, re-enter the command that generated this error message.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.725 E2808 Cmd Rej: TPS exceeded on DEIR card
The sum of RSVDTPS for all the diameter connections on a particular card must not exceed the maximum diameter card TPS (8000).
Recovery
2.2.726 E2809 Cmd Rej: ITUN16 SID is not allowed for MAP commands in J7 Support
An ITUN16 SID cannot be entered. Provisioning of a local subsystem for the ITUN16 SID is rejected so that ITUN16 MSUs are not forwarded to local subsystems.
Recovery
2.2.727 E2810 Cmd Rej: Command is not valid for ITU-N16 links
The specified command is not supported for J7 links.
Recovery
- Refer to the command descriptions in Commands User's Guide for assistance. If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.728 E2811 Cmd Rej: EE Filter table is full
The Eagle Eyes Filter (EE FLT) table is full.
Recovery
2.2.729 E2812 Cmd Rej: EE Filter does not match card appl type
The Filter appl and card appl should be the same.
Recovery
2.2.730 E2813 Cmd Rej: Unable to read EE Filter table
The Eagle Eyes Filter (EE FLT) table is corrupt or cannot be found.
Recovery
2.2.731 E2814 Cmd Rej: GPORT invalid if APORT or IGM is enabled
For the chg-sccp-serv and ent/chg-srvsel, commands, if the A-Port or IS41 GSM Migration (IGM) feature is enabled, then a value of gport cannot be specified for the serv or nserv parameter.
For the chg-sid command, if the A-Port or IGM feature is enabled, then the cpctype=gport parameter cannot be specified.
Recovery
2.2.732 E2815 Cmd Rej: PC and RC must be entered as a pair
The pc and rc parameters must be specified together in the command.
Recovery
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.
2.2.733 E2816 Cmd Rej: PC already exists in the MRN entity set
The value specified for the pc/pca/pci/pcn/pcn24 parameter cannot already exist in the MRN table.
Recovery
- Display the existing values in the MRN table. Enter the
rtrv-mrncommand. - Re-enter the
ent/chg-mrncommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.734 E2817 Cmd Rej: MRN table is full
One or more point codes in the command will exceed the maximum number of point codes that can be entered into the MRN table (3000 if the IGTTLS feature is turned on and 6000 if the IGTTLS and FGTTLS features are turned on).
Recovery
2.2.735 E2818 Cmd Rej: A maximum of 128 PCs are allowed in a group
Each point code group in the Mated Relay Node (MRN) table can contain a maximum of 128 point codes.
Recovery
2.2.736 E2819 Cmd Rej: Destination disk is unformatted
The destination disk must be formatted before the command can be entered.
Recovery
Refer to the Maintenance Guide and to the command description for the command that generated this error message in the Commands User's Guide for assistance with formatting the destination disk.
Contact My Oracle Support for additional assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.737 E2820 Cmd Rej: Source location must specify the active fixed disk
The value specified for the sloc parameter must indicate the active fixed disk.
Recovery
2.2.738 E2821 Cmd Rej: Could not access removable disk
A formatted removable drive containing the next release is required for the upgrade. A hardware problem with the removable drive may exist.
Recovery
Refer to Maintenance Guide and contact My Oracle Support for assistance with the removable drive. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.739 E2822 Cmd Rej: Destination location must specify the standby fixed disk
The value specified for the dloc parameter must indicate the standby fixed disk.
Recovery
2.2.740 E2823 Cmd Rej: Destination location must specify the standby removable disk
The value specified for the dloc parameter must indicate the standby removable disk.
Recovery
Re-enter the copy-fta 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.742 E2825 Cmd Rej: Could not access removable disk
The removable drive is not available. A hardware problem may exist.
Recovery
Re-enter the copy-fta command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.743 E2826 Cmd Rej: Could not access active fixed disk
A hardware problem may exist.
Recovery
Re-enter the copy-fta or copy-gpl command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.744 E2827 Cmd Rej: Filter not present
The specified Filter ID must exist in the EE FLT table.
Recovery
2.2.745 E2828 Cmd Rej: Source and destination disks not compatible
A hardware problem may exist.
Recovery
copy-fta or format-disk command that generated this error message.
Caution:
Contact My Oracle Support before entering theformat-disk command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.746 E2829 Cmd Rej: Destination disk capacity equals 0
The system cannot determine the capacity of the disk being formatted.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.747 E2830 Cmd Rej: Source drive not coherent
A hardware problem may exist.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.748 E2831 Cmd Rej: Current database not coherent
Resolving this issue is beyond the scope of this manual.
Recovery
Refer to the Database Administration - System Management User's Guide for assistance.
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.749 E2832 Cmd Rej: MTPRSI is only valid if MTPRS or ITUMTPRS feature is ON
The ANSI MTP Restart (MTPRS) or the ITU MTP Restart (ITUMTPRS) feature must be turned on before the mtprsi parameter can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.750 E2833 Cmd Rej: MTPRSIT parameter is only valid if MTPRS feature is ON
The ANSI MTP restart (MTPRS) feature must be turned on before the mtprsit parameter can be specified
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.751 E2834 Cmd Rej: MTPRSE parameter is only valid if MTPRS feature is ON
The ANSI MTP Restart (MTPRS) or the ITU MTP Restart (ITUMTPRS) feature must be turned on before the mtprse parameter can be specified.
Note:
Once a feature that is controlled using a feature bit is turned on, it cannot be turned off.Recovery
2.2.752 E2835 Cmd Rej: MTPRSE is only valid in the SS7 domain
MTP Restart Equipped (MTPRSE) indicator is only valid for adjacent ANSI nodes in the SS7 domain.
Recovery
Re-enter the command, specifying adjacent ANSI node parameters in the SS7 domain. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.753 E2836 Cmd Rej: Too many nested cluster dstn entered
If the ncai=yes parameter is specified, then the maximum number of provisioned nested clusters is 500.
Recovery
2.2.754 E2837 Cmd Rej: NCR must be enabled to enter NCAI param
The Nested Cluster Routing (NCR) feature must be turned on before the ncai parameter can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.755 E2838 Cmd Rej: Unable to change Network/Cluster dstn NCAI param
If the members of a cluster have different route sets, then the ncai=no parameter cannot be specified to change a provisioned nested cluster point code to a non-nested cluster point code.
Recovery
2.2.756 E2839 Cmd Rej: Invalid parameter for ITU-N 24bit point code
If a 24-bit ITU-N point code is specified, then a 14-bit ITU-N alias or ANSI alias point code cannot be specified.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.757 E2840 Cmd Rej: Failed reading tt map table
The TT MAP table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.758 E2841 Cmd Rej: tt map table full for LSN specified
The translation type MAP table is full for the linkset specified by the lsn parameter.
Recovery
2.2.760 E2843 Cmd Rej: TT Mapping is not provisioned for this link set
The linkset specified by the lsn parameter must already be provisioned.
Recovery
2.2.761 E2844 Cmd Rej: ETT not defined for LSN and IO specified
The ett parameter must be specified.
Recovery
Re-enter the ent/chg-ttmap command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.762 E2845 Cmd Rej: ETT already mapped for LSN and IO specified
The mapping specified by the ett, lsn, and io parameters cannot already exist.
Recovery
2.2.763 E2846 Cmd Rej: ETT cannot be mapped to MTT with same value
The value specified for the ett cannot have already been specified for the mtt parameter.
Recovery
2.2.764 E2847 Cmd Rej: IF IO or ETT specified, BOTH opt. parms must be specified
The io and ett parameters must be specified together in the command.
Recovery
Re-enter the dlt-ttmap command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.765 E2848 Cmd Rej: ASL8 is only valid for ANSI link sets
The asl8=yes parameter can only be assigned to an SS7 ANSI linkset (a linkset containing an adjacent point code in the SS7 domain).
Recovery
Re-enter the ent/chg-ls command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.766 E2849 Cmd Rej: PC must already exist in the MRN table
The value specified for the point code parameter must already exist in the MRN table.
Recovery
- Display the entries in the MRN table. Enter the
rtrv-mrncommand. - 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.
2.2.767 E2850 Cmd Rej: MTPXLxx parameters are only valid if crmd feature is ON
The Cluster Routing and Management Diversity (CRMD) feature must be turned on before the mtpxlq, mtpxlet, and mtpxlot parameters can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.768 E2851 Cmd Rej: MTPXLQ cannot exceed available space in the dstn table
The value specified for the mtpxlq parameter cannot exceed the allowable sum of destinations provisioned as determined by adding the values specified for the mtpdpcq and mtpxlq parameters (mtpdpcq + mtpxlq <= sum).
Recovery
2.2.769 E2852 Cmd Rej: Failed reading STP Options table
The STP Options table is corrupt or cannot be found.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.770 E2853 Cmd Rej: ELEI is only valid for cluster destinations
If the elei parameter is specified, then a cluster destination for the dpc/dpca/dpci/dpcn/dpcn24 parameter must be specified.
Recovery
2.2.771 E2854 Cmd Rej: Alias PCs are not valid for cluster destinations
If a cluster or network destination for the (dpc/dpca/dpci/dpcn/dpcn24) parameter is specified, then the alias point code parameter (aliasa/aliasi/aliasn/aliasn24) cannot be specified.
Recovery
2.2.772 E2855 Cmd Rej: Cluster DPCs are only valid if the CRMD feature is ON
The Cluster Routing and Management Diversity (CRMD) feature must be turned on before a cluster DPC (ni-nc-* ), can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.773 E2856 Cmd Rej: ELEI is only valid if the CRMD feature is ON
The Cluster Routing and Management Diversity (CRMD) feature must be turned on before the elei parameter can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.774 E2857 Cmd Rej: DPC is referenced by SCCP’s MAP table
A destination point code (DPC) that is being referenced in the Mated Application (MAP) table cannot be deleted.
Recovery
2.2.775 E2858 Cmd Rej: EE Filter associated to Network Card
The specified filter should not be associated with any network card.
Recovery
2.2.776 E2859 Cmd Rej: Destination address must be a full point code
The specified point code or adjacent point code must be a full point code. A full point code is specified using numerical values for all three segments of the point code.
Recovery
2.2.777 E2860 Cmd Rej: TFATCABMLQ value exceeds number of links in link set
For the chg-ls command, the value specified for the tfatcabmlq parameter cannot be more than the total number of links assigned to the linkset.
For the dlt-slk command, if the lsrestrict=on parameter is specified (see the chg-ss7opts command), and if deleting the link would send the number of links assigned to the linkset below the value specified for the tfatcabmlq parameter (see the chg-ls command), then the link cannot be deleted.
Recovery - chg-ls
- Display the linkset information. Enter the
rtrv-lscommand.The LNKS column lists the total number of links assigned to the linkset.
- Re-enter the
chg-lscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - dlt-slk
2.2.778 E2861 Cmd Rej: Site PC, CPCs and NCPCs must be full point codes
The STP destination and capability point codes must be specified as full point codes.
Recovery
Re-enter the ent/chg/rtrv-sid command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.779 E2862 Cmd Rej: EE Card table is full
The EE CARD table cannot contain more than 256 entries.
Recovery
2.2.780 E2863 Cmd Rej: Destination’s alias PCs must be full PCs
The value specified for an alias point code must be a full point code. An asterisk cannot be used to designate the network indicator (ni), network cluster (nc), or network cluster member (ncm).
Recovery
Re-enter the ent/chg/rtrv-dstn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.781 E2864 Cmd Rej: Address (PCx) of primary subsystem must be a full PC
Numerical values must be specified for all three segments of the destination point code.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.782 E2865 Cmd Rej: Address (MPCx) of mate subsystem must be a full PC
The value specified for the point code (pc, pc1, pc2, pc3, or pc4) or mate point code (mpc, mpca, mpci, mpcn, or mpcn24) must be a full point code, and must exist in the routing table.
Recovery
2.2.783 E2866 Cmd Rej: TFATCABMLQ is invalid for C-link sets
The tfatcabmlq parameter cannot be changed for C linksets, because C linksets are the primary route for mated STPs.
Recovery
2.2.784 E2867 Cmd Rej: Unable to read EE Card table
The EE CARD table is corrupt or cannot be found.
Recovery
2.2.785 E2868 Cmd Rej: Invalid NCAI parameter has been entered
The ncai parameter can only be specified for a destination address that is a cluster destination.
Recovery
2.2.786 E2869 Cmd Rej: NCAI param is only valid if both feat CRMD and NCR are ON
The Cluster Routing and Management Diversity (CRMD) and Nested Cluster Routing (NCR) features must be turned on before the ncai parameter can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.787 E2870 Cmd Rej: LFS feature must be ON
The Link Fault Sectionalization (LFS) feature must be turned on before the command can be entered.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.788 E2871 Cmd Rej: NCPCx and CPCx type must match
The capabiity point code type for the cpc/cpca/cpci/cpcn/cpcn24 and ncpc/ncpca/ncpci/ncpcn/ncpcn24 parameter must be the same.
Recovery
2.2.789 E2872 Cmd Rej: CPCx has not been provisioned
If an ncpc, ncpca, ncpci, ncpcn, or ncpcn24 parameter is specified, then the specified corresponding cpc, cpca, cpci, cpcn, or cpcn24 parameter value must already exist in the database.
Recovery
2.2.790 E2873 Cmd Rej: NCPCx cannot be specified without CPCx
If the ncpc/ncpca/ncpci/ncpcn/ncpcn24 parameter is specified, then the cpc/cpca/cpci/cpcn/cpcn24 parameter must be specified.
Recovery
Re-enter the chg-sid command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.791 E2874 Cmd Rej: Failed reading site identification table
The Site Identification table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.792 E2875 Cmd Rej: Network/Cluster cannot have alias DPC members
A cluster destination cannot be defined using the same network identifier (ni) and network cluster (nc) subfields of any previously defined alias ANSI point codes.
Recovery
2.2.793 E2876 Cmd Rej: Alias DPCs cannot be a member of a Network or Cluster
Alias ANSI point codes cannot have the same network identifier (ni) and network cluster (nc) subfields as a cluster point code that is already defined.
Recovery
2.2.794 E2877 Cmd Rej: NCAI required if cluster members have different route set
If a cluster point code is specified, then the collection of signaling points sharing the same network identifier (ni) and network cluster (nc) subfields must have the same route set. If the collection has different route sets, then ncai=yes parameter must be specified.
Recovery
2.2.795 E2878 Cmd Rej: Ordered routes cannot be assigned to cluster members
If the specified destination address is a full point code address (ni-nc-ncm) and a member of a provisioned cluster (ni-nc-*), then the ncai=yes parameter must be specified in the ent/chg-dstn command before an ordered route can be assigned.
Recovery
2.2.796 E2879 Cmd Rej: Ordered routes cannot be deleted from cluster members
If the specified destination address is a full point code address (ni-nc-ncm) and a member of a provisioned cluster (ni-nc-*), then the ncai=yes parameter must be specified in the ent/chg-dstn command before an ordered route can be deleted.
Recovery
2.2.797 E2880 Cmd Rej: MTPDPCQ cannot exceed available space in the dstn table
The value specified for the mtpdpcq parameter cannot exceed the allowable sum of destinations provisioned as determined by adding the values of the mtpdpcq and mtpxlq parameters.
Recovery
2.2.798 E2881 Cmd Rej: MTPDPCQ cannot be increased while x-list storage is full
The number of DPCs configured using the mtpdpcq parameter cannot be increased if space allocated for maintaining x-list entries (mtpxlq parameter) is full.
Recovery
2.2.799 E2882 Cmd Rej: MSAR=ONLY must be specified exclusively
If the msar=only parameter is specified, then no other parameters can be specified.
Recovery
Re-enter the rtrv-dstn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.800 E2883 Cmd Rej: Maximum number of CPCs defined (96)
A maximum of 96 capability point codes can be specified.
Recovery
2.2.801 E2884 Cmd Rej: PCx, NPCx, CPCx or NCPCx must not be equal
The same value cannot be specified for the pc/pca/pci/pcn/pcn24, cpc/cpca/cpci/cpcn/cpcn24, npci/npcn, or ncpc/ncpca/ncpci/ncpcn/ncpcn24 parameters.
Recovery
Re-enter the chg-sid command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.802 E2885 Cmd Rej: Ordered routes cannot be changed for cluster members
If the specified destination address is a full point code address (ni-nc-ncm) and a member of a provisioned cluster (ni-nc-*), then the ncai=yes parameter must be specified in the ent/chg-dstn command before an ordered route can be changed.
Recovery
2.2.803 E2886 Cmd Rej: DSTN address must be a full, network or cluster PC
The destination address must be a full point code, a network destination, or a cluster point code.
Recovery
2.2.804 E2887 Cmd Rej: Failed accessing maintenance data
The cluster exception-list (x-list) maintenance data is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.805 E2888 Cmd Rej: MTPDPCQ cannot be less than no. of destinations provisioned
The value specified for the mtpdpcq parameter must be greater than or equal to the number of DPCs provisioned.
Recovery
- Display the number of DPCs configured in the database. Enter the
rtrv-dstncommand. - Re-enter the
chg-stpoptscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.806 E2889 Cmd Rej: Duplicate Filter on a Network card is not allowed
The fltid specified should not be already associated with the card.
Recovery
2.2.807 E2890 Cmd Rej: DPC must be specified as wildcard when used with STAT
If the stat parameter is specified, then the dpc aparameter must be specified in wild card format (ni-nc-** or ni-nc-***).
A ‘wildcard value’ is an expression meaning the value is a variable indicated by an asterisk.
Refer to “Point Code Formats and Conversion” in Appendix A of the Commands User's Guide for a detailed description of point code formats, rules for specification, and examples.
Recovery
Re-enter the rept-stat-dstn 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.808 E2891 Cmd Rej: Failed reading Link Fault Sectionalization table
The Link Fault Sectionalization table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.809 E2892 Cmd Rej: LOC is not LFS capable
The card location specified by the loc parameter must identify a provisioned HC-MIM, E5-E1T1, or E5-E1T1-B card, provisioned with the LIMT1 card type, configured with either the SS7ANSI or CCS7ITU application.
Recovery
- Display information about the card. Enter the
rtrv-cardcommand. - Re-enter the
chg/dact/dlt/ent/rtrv-lbporrept-stat-lfscommand that generated this error message, specifying a valid card location. Refer to the command description in Commands User's Guide and to Database Administration - SS7 User's Guide for assistance.
2.2.810 E2893 Cmd Rej: REP must be greater than prev. and less than subsequent REP
The rep parameter value that is specified for this loopback point (LBP) must be greater than the rep parameter value of any previously defined LBP and less than the rep parameter value of any subsequently defined LBP.
Recovery
2.2.811 E2894 Cmd Rej: LBP has already been provisioned
The value specified for the lbp parameter cannot already exist in the database.
Recovery
2.2.812 E2895 Cmd Rej: REP must be zero if link element to be tested is NEI
If the rle=nei parameter is specified, then the rep=0 parameter must be specified.
Recovery
Re-enter the act/chg/ent-lbp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.813 E2896 Cmd Rej: DS0 and NEI link elements do not support non-latching tests
If the lfst=nlt parameter is specified, then a value of ds0 or nei cannot be specified for the rle parameter.
Recovery
Re-enter the act/ent/chg-lbp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.814 E2897 Cmd Rej: REP is only valid if LFST is defined as LLT
The lfst=llt parameter must be specified before the rep parameter can be specified.
Recovery
Re-enter the ent/chg/act-lbp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.815 E2898 Cmd Rej: LBP cannot exceed previously defined NEI LBP value
The value specified for the lbp parameter cannot exceed the lbp parameter value previously defined for a loopback point with rle=nei specified.
Recovery
2.2.816 E2899 Cmd Rej: NEI LBP has already been defined for the CCS7 link
For each SS7 signaling link, the rle=nei parameter can be specified for only one loopback point. That loopback point must be the terminating SS7 signaling link component.
Recovery
2.2.817 E2900 Cmd Rej: NEI LBP must be defined as the last link element
The loopback point (LBP) ID of the remote link element (RLE) must define the last element on the link. For example, for ent-lbp:loc=1101:port=a:lbp=2:rle=nei:lfst=llt, the NEI loopback point 2, at card location 1101 port a, must be the last element on that signaling link/
Recovery
2.2.818 E2901 Cmd Rej: LBP must have been previously defined in database
The value specified for the lbp parameter must already exist in the database.
Recovery
2.2.819 E2902 Cmd Rej: LBP or ALL parameter must be specified exclusively
The lbp and all parameters cannot be specified together in the command.
Recovery
Re-enter the dlt-lbp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.820 E2903 Cmd Rej: LOC and PORT parameter combination must be specified
For the inh/unhb-alm command, if the dev=slk parameter is specified, then the loc and link parameters must be specified.
The loc and port parameters must be specified together in the rept-stat-cdl, rept-stat-enet, rept-stat-lfs, or rept-stat-tstslk command.
For the rtrv-lbp command, If the lbp parameter is specified, then the loc and port parameters must be specified to display the attributes for a specific loopback point (lbp parameter) that lies along an SS7 signaling link.
The loc and e1port parameters must be specified together in the rtrv-e1 command
The loc and t1port parameters must be specified together in the rtrv-t1 command.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.821 E2904 Cmd Rej: TFATFRPR must be in increments of 100 msec
A value for the tfatfrpr parameter must be specified in increments of 100 milliseconds (0.10 seconds).
Recovery
Re-enter the chg-stpopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.822 E2905 Cmd Rej: LFS command in progress
The previously entered link test command must be accepted before another link test command can be entered.
Recovery
2.2.823 E2906 Cmd Rej: LFS test is completing, can not be canceled
A previously issued act-lbp command is about to complete. A new dact-lbp command can not be accepted until the currently running act-lbp command completes.
Recovery
2.2.824 E2907 Cmd Rej: No active LFS Test on the specified link
There is no active LFS Test on the specified link.
Recovery
2.2.825 E2908 Cmd Rej: LOOPBACK param needed for FELINE or FEPAYLOAD exclusively
If the action=stop parameter is specified, then a value of feline or fepayload must be specified for the loopback parameter.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Maintenance Guide for more information.
2.2.826 E2909 Cmd Rej: LFS data is only valid for OCTET and ALTERNATE patterns
A value of octet or alternate must be specified for the pattern parameter before the data parameter can be specified.
Recovery
Re-enter the act-lbp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Maintenance Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.827 E2910 Cmd Rej: RLE and LFST must be specified when database is not used
If the rep or clli parameter is specified, then the lfst and rle parameters must be specified.
Recovery
Re-enter the act/ent/chg-lbp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.828 E2911 Cmd Rej: OCTET and ALTERNATE are not valid for non-latching test
Values of octet or alternate can be specified for the pattern parameter only for latching tests.
Recovery
2.2.829 E2913 Cmd Rej: STOP Loopback type must match active loopback
If the action=stop parameter is specified, and a value of feline or fepayload is specified for the loopback parameter, then there cannot be an active loopback for the J1/T1 span, or the active loopback must be the one specified in the command.
Recovery
2.2.830 E2914 Cmd Rej: REP parameter must be specified
The rep parameter must be specified if the default value of the parameter is a duplicate of the rep parameter value of any previously defined loopback point.
Recovery
2.2.831 E2915 Cmd Rej: MTPT10ALT cannot be less than level-3 timer T10
The value specified for the mtp10alt parameter must be equal to or greater than the value specified for the Level3-T10 timer (see the chg-l3t command).
Recovery
2.2.832 E2916 Cmd Rej: Link must not be active to execute command
The specified signaling link cannot be active.
Recovery
2.2.833 E2917 Cmd Rej: Link must be SS7 to execute command
The specified signaling link must be an SS7 signaling link.
Recovery
2.2.834 E2918 Cmd Rej: Link must be SS7 to display Level 2 stats
The l2stats parameter can be specified for only SS7 signaling links.
Recovery
2.2.835 E2920 Cmd Rej: Loopback in progress
Only one loopback test can be performed at a time.
Recovery
Re-enter the act-lbp command after the active loopback test is complete.
2.2.836 E2921 Cmd Rej: LFS must not be running on requested link
The command cannot be entered if an LFS test is running on the specified link.
Recovery
2.2.837 E2922: Cmd Rej: Link must be SAAL to execute command
The loopback=payload parameter can be specified for only ATM high-speed signaling links.
Recovery
2.2.838 E2923 Cmd Rej: Maximum number of link tests already in progress
The command cannot be entered if the maximum number of LFS or link tests are already running in the system.
Recovery
2.2.839 E2924 Cmd Rej: LOC has maximum number of LFS Tests already in progress
The maximum number of allowed tests is already in progress on this LOC. At least one active LFS test on this LOC must be completed before another act-lbp command can be performed for this card location.
Recovery
2.2.840 E2925 Cmd Rej: The Gateway Linkset table is full
The Gateway Linkset table can contain a maximum of 255 entries.
Recovery
2.2.841 E2926 Cmd Rej: A problem occurred while trying to access the GWS database
An intermittent system problem may exist.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.842 E2927 Cmd Rej: The linkset is provisioned locally
Gateway screening (GWS) on a linkset cannot be provisoned through the OAP if GWS has already been provisioned on the linkset GWS through an EAGLE terminal.
Recovery
Determine whether GWS is present on the linkset. Enter the rept-stat-ls:lsn= command, specifying the linkset of interest.
Contact My Oracle Support if additional assistance is required. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.843 E2928 Cmd Rej: The linkset specified is not a Gateway Linkset
The gwsa, gwsm, and gwsd parameters and the gtwy-ls command can be specified only for Gateway Linksets.
Recovery
2.2.844 E2929 Cmd Rej: The linkset specified does not exist in the linkset table
The value specified for the lsn parameter must already exist in the database.
Recovery
- Display the linkset information. Enter the
rtrv-lscommand. - Re-enter the
chg/dlt/rtrv-lscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.845 E2930 Cmd Rej: The Gateway Linkset specified already exists
The value specified for the lsn parameter cannot already exist.
Recovery
- Display the linkset information. Enter the
rtrv-lscommand. - Re-enter the
ent-lscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide (SS7 links), and the Database Administration - IP7 User's Guide (IP links) for assistance.
2.2.846 E2931 Cmd Rej: SEAS Gateway Screen Set names can not be changed locally
Gateway linksets must be configured from a SEAS terminal.
Recovery
2.2.847 E2932 Cmd Rej: SEAS Gateway Linkset can not be deleted locally
Gateway linksets can be deleted only from a SEAS terminal.
Recovery
2.2.848 E2933 Cmd Rej: A specific SI must be specified in the range (0-15)
The si parameter must be specified, and the value must be within a valid range.
Recovery
Re-enter the ent/chg/dlt-scr-sio command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.849 E2935 Cmd Rej: If SDATE=EDATE, then ETIME after or same as STIME
If the same value is specified for the sdate and edate parameters, then the value specified for the etime parameter must be the same or later than the value specified for the stime parameter.
Recovery
Re-enter the rtrv-log command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance
2.2.850 E2936 Cmd Rej: SDATE+STIME must be before current date-time
The values specified for the sdate and stime parameters must be earlier than the current date-time combination.
Recovery
Re-enter the rtrv-log command that generated this error message, specifying a valid command combination of parameters. Refer to the command description in Commands User's Guide and to Maintenance Guide for assistance.
2.2.851 E2938 Cmd Rej: RTRV-LOG command already in progress
The rtrv-log command cannot be entered while another rtrv-log command is in progress.
Recovery
Re-enter the rtrv-log command after the active rtrv-log command finishes processing.
2.2.852 E2939 Cmd Rej: Unable to read the selected log
The system cannot access the selected log using the rtrv-log command.
Recovery
This error message indicates a potentially serious disk error.
Contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.853 E2940 Cmd Rej: Standby MASP is not available
The standby MASP is corrupt or cannot be found.
Recovery
Re-enter the rtrv-log command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.854 E2941 Cmd Rej: Invalid combination - EDATE with STIME
The stime parameter and the edate parameter cannot be specified together in the command.
Recovery
Re-enter the rtrv-log command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Maintenance Guide for assistance.
2.2.855 E2942 Cmd Rej: Failed reading/writing Extended Linkset Table
A hardware problem may exist.
Recovery
Re-enter the rtrv/set-gtwy-acthresh command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.856 E2943 Cmd Rej: Failed reading/writing Extended STP Options Table
A hardware problem may exist.
Recovery
Re-enter the rtrv-gtwy-prmtrs or set-scrrej-prmtrs command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.857 E2944 Cmd Rej: Invalid INTRVL value specified
A valid value must be specified for the intrvl parameter. Refer to the command description in Commands User's Guide for assistance.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.858 E2945 Cmd Rej: Source database version is not compatible
The specified source drive is not at the correct database version for the upgrade to proceed.
Recovery
Caution:
It is strongly recommended that this command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.2.2.859 E2946 Cmd Rej: No match on DESTFLD parameter during retrieve
A match was not found for the nsfi=destfld parameter.
Recovery
- Display the existing values for the nsfi parameter. Enter the
rtrv-scr-siocommand. - Re-enter the
rtrv-scr-siocommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.860 E2947 Cmd Rej: No match on SCCPMT parameter during retrieve
The value specified for the sccpmt parameter must match a screening reference in the allowed CGPA entity set.
Recovery
2.2.861 E2948 Cmd Rej: No match on SCMGFID parameter during retrieve
The value specified for the scmgfid parameter must match a screening reference in the allowed CDPA entity set.
Recovery
2.2.862 E2949 Cmd Rej: SNAME must be specified
If the dev=applsock parameter is specified, then the sname parameter must be specified.
Recovery
Re-enter the inh/unhb-alm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.863 E2950 Cmd Rej: PORT parameter invalid for DEV selected
The value specified for the port/link parameter must be compatible with the device configured with the dev parameter.
Recovery
Re-enter the inh/unhb-alm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.864 E2951 Cmd Rej: LSN must be specified
If the dev=ls parameter is specified, then the lsn parameter must be specified.
Recovery
Re-enter the inh/unhb-alm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.865 E2952 Cmd Rej: PORT must be specified
If the dev=lsmsconn parameter is specified, then the port parameter must be specified.
Recovery
Re-enter the inh/unhb-alm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.866 E2953 Cmd Rej: ID must be specified
If the dev=cdt parameter is specified, then the id parameter must be specified.
Recovery
Re-enter the inh/unhb-alm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.867 E2954 Cmd Rej: DEV state does not allow alarms to be inhibited
The command will not execute while the signaling link is running either a Link Fault Sectionalization test or a Loopback test.
Recovery
Wait for the device to finish its action, then re-enter the inh-alm command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.868 E2955 Cmd Rej: Network Routing is only valid if the NRT feature is ON
For the ent/chg/dlt/rtrv-dstn or ent/chg/dlt/rtrv-rte command, the Network Routing (NRT) feature must be turned on before a network destination can be entered.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.869 E2956 Cmd Rej: NCM must be * when using Network Routing
When using network routing, if the destination point code has a value of * in the nc field, then the ncm field must also be * (for example, dpc=21-*-*).
Recovery
Re-enter the ent/chg/dlt/rtrv-dstn or ent/chg/dlt/rtrv-rte command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.870 E2960 Cmd Rej: CHG-PID not allowed while in upgrade mode
The chg-pid command cannot be entered while the system is in upgrade mode.
Recovery
Re-enter the chg-pid command after the upgrade has completed.
2.2.871 E2961 Cmd Rej: <#> (domain) must be between <min> and <max>
The value specified for the timer must be within the range for that domain.
Recovery
Re-enter the command that generated this error message, specifying a valid value that is within the minimum-maximum range of permissible timer values. Refer to the command description in Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.872 E2962 Cmd Rej: <device> is <condition>
- must be inserted
- must be initialized
- cannot be a measurement removal disk
- must be a system removable disk
A valid upgrade release must reside on the plug-in flash drive or the inactive partition of the fixed disk.
Note:
For all recovery procedures, refer to the command description in Commands User's Guide for the command that generated this error message and to Database Administration - System Management User's Guide for assistance.Note:
After completing each procedure, re-enter the command that generated the error message. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.Recovery - Plug-in flash drive is not inserted
Insert a system disk for the current system release.
Recovery - Plug-in flash drive is not initialized
format-disk command for details on how to use the system to format drives.
Caution:
Contact My Oracle Support before entering theformat-disk command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - Plug-in flash drive is not a system disk
The removable drive must be accessible and ready and must be formatted as a system removable disk, NOT as a measurement removable disk.
Insert a system disk for the current system release.
Recovery - Plug-in flash drive is not a MEAS disk
-
Remove the system disk from the E5-MASP.
-
Insert a MEAS disk for the current system release.
Recovery - Plug-in flash drive is inaccessible (internal problem)
Remove and re-install the E5-MASP and drive or a spare E5-MASP.
Recovery - Fixed disk is not inserted
Insert a fixed disk for the current system release.
Recovery - Fixed disk is not initialized
Initialize the disk.
Recovery - Fixed disk is inaccessible (internal problem)
Remove and re-install the E5-MASP and drive or a spare E5-MASP.
2.2.873 E2963 Cmd Rej: Cannot read DB Stat Table (<database>, <disk>, <MASP status>) [or] Cmd Rej: Incorrect DB version (<database>, <disk>, <MASP status>) [or] Cmd Rej: DB status is UPG 1 (<database>, <disk>, <MASP status>) [or] Cmd Rej: DB is incoherent (<database>, <disk>, <MASP status>)
-
DB Stat Table cannot be read
-
DB version is incorrect
-
DB status is UPG 1
-
DB is incoherent
(‘Incoherent’ means that a previous database update was unsuccessful, leaving the coherency indicator unchanged)
For more information on database coherency, refer to the Database Administration - System Management User's Guide.
The designation of the problem database is identified as:
-
<database>Curr DB orBkup DB
-
<disk>Fxd Disk orRmv Disk
-
<MASP status>Active MASP orStby MASP
Recovery
2.2.874 E2964 Cmd Rej: PVN/FCNA/FCNB conflicts with IPRTE or IPLNK network
For the chg-eisopts command, the destination of a static IP route or the local interface network address of an IP card must be different from the EAGLE PVN, FCNA, or FCNB network address before the eiscopy=on parameter can be specified.
Recovery
2.2.875 E2965 Cmd Rej: Too many parameters entered
For the chg-ppsopts command, if the gta1, gta2, or gta3 parameter is specified, then the ngta parameter cannot be specified.
For the inh/unhb-alm command, a valid combination of parameters must be specified.
For the inh-alm command, if a value other than timed is specified for the dur parameter, then the edate and etime parameters cannot be specified.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.876 E2966 Cmd Rej: TRM must be specified
The trm parameter must be specified.
For the inh/unhb-alm commands, if the dev=trm parameter is specified, then the trm parameter must be specified.
Recovery
Re-enter the command that generated this error messages, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.877 E2967 Cmd Rej: Active OAM database is incoherent
The database was found to be incoherent, which means that a previous database update was unsuccessful, leaving the coherency indicator unchanged. During the subsequent attempted execution of an upgrade procedure, an error was detected when either of the following was issued: act-upgrade:action=convertoam or act-upgrade:action=convertstp
Recovery
2.2.878 E2968 Cmd Rej: Card disconnect from both IMT busses not allowed
The card specified in the disc-imt command cannot be isolated from both IMT busses.
Recovery
Wait for the IMT Fault Isolation Test to complete before re-entering the command that generated this error message. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.879 E2969 Cmd Rej: Unable to determine current connect status of card
The code cannot determine the state of the alternate IMT bus. When disconnecting one IMT bus, the other (alternate) IMT bus must be in a known, good state (IS-NR).
Recovery
Re-enter the command that generated this error message. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.880 E2970 Cmd Rej: Max limit of INC/EXC Filters reached on card
A maximum of 16 include filters and 16 exclude filters can be attached to a card.
Recovery
2.2.881 E2971 Cmd Rej: System busy - Repeat later
- Heavy disk activity (resulting from database maintenance or measurement collection) is preventing access to the system.
OR
- A conflict between two action commands has occurred. If you enter an action command while another action command is in progress, your command cannot execute.
An action command is a command that changes the state of entities within the EAGLE. Refer to the command description in Commands User's Guide for assistance.
Recovery
2.2.882 E2972 Cmd Rej: Specified Link is not valid for Card and Appl Type
The specified link is not valid for the card and application type. Refer to the command description and to Appendix A in the Commands User's Guide for details on the links supported for each card and application type.
Recovery
Re-enter the command that generated this error message, specifying a valid link for the card type and application.
2.2.883 E2974 Cmd Rej: BPS must be 56000 for all ports on Multi Port LIM
If a multi-port LIM card is used, then the bps=56000 parameter must be specified.
Recovery
- Display the card type. Enter the
rtrv-cardcommand. - Re-enter the
ent-slkcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.884 E2975 Cmd Rej: Specified port is not supported
The card in the location specified by the loc parameter must support the port specified by the port parameter. Refer to the command description in Commands User's Guide for ports supported by various cards.
Note:
IPv6 configuration is not allowed on port A for the cards provisioned with MPS-based GPLs.Recovery
2.2.885 E2976 Cmd Rej: Card does not support more than 2 Links
A signaling link was specified that is not supported on the card that is running. Refer to the command description and to Appendix A in the Commands User's Guide for details on the links supported on each card type.
Recovery
Re-enter the command that generated this error message, specifying a port that is valid for the card that is running.
2.2.886 E2977 Cmd Rej: Cannot leave a solitary PC in group
Point codes cannot be deleted from an MRN group if the deletion leaves only one point code in the group. If deleting one or more point codes from the MRN group leaves only one point code in the group, then the entire MRN group must be deleted.
Recovery
2.2.887 E2978 Cmd Rej: RC is required if no other optional parameters are provided
The rc parameter must be specified if no other optional parameters are specified in the command.
Recovery
Re-enter the chg-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.888 E2979 Cmd Rej: Cannot enter the same PC more than once
For the ent/chg-mrn command, the specified point code value cannot already exist in the MRN table.
For the chg-sccp-serv command, the specified point code value cannot already exist in the SCCP-SERV table.
For the dlt-mrn and dlt-sccp-serv commands, the point code cannot be specified more than once for deletion.
Recovery
2.2.889 E2980 Cmd Rej: Must be in upgrade phase 3 or full function mode
The EAGLE must be in Upgrade Phase 3 mode or Full Function mode before the init-network command can be entered.
Upgrade Phase 3 mode means that the MASPs are running GPLs that match the major revision defined for the approved GPLs, but the other network processors are only prepared to be upgraded. Full Function mode means that all MASPs are running GPLs that match the major revision defined for the approved GPLs. Full Function mode is the normal operating mode for the MASP.
Recovery
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.890 E2981 Cmd Rej: Already in nodal isolation
At least one SS7ANSI or CCS7ITU card must exist with an in-service active link before the init-network command can be entered.
Recovery
2.2.891 E2982 Cmd Rej: Database is incoherent
The database is incoherent, which means that a previous database update was unsuccessful, thereby leaving the coherency indicator unchanged.
For more information on database coherency, refer to Database Administartion - Systems Management User's Guide.
Recovery
2.2.892 E2984 Cmd Rej: Eagle Eyes not configured on the card
Eagle Eyes is not configured on the card.
Recovery
2.2.893 E2985 Cmd Rej: Application ID not supported
The value of the APPLID parameter is fixed and cannot be changed.
Recovery
2.2.894 E2986 Cmd Rej: LNP or AINPQ feature must be ON
chg/rtrv-lnpopts command can be entered.
Recovery
2.2.895 E2987 Cmd Rej:The TPC can be used only when creating a SOL or DOM group
Recovery
Re-enter the ent-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.896 E2988 Cmd Rej: Maximum number of Mated Applications (MAP) exceeded
A maximum of 128 mated applications is allowed per MAP set.
Recovery
2.2.897 E2989 Cmd Rej: RC must be specified for PC since MPC is specified
If the mpc parameter is specified, then the rc parameter must be specified.
Recovery
Re-enter the ent-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.898 E2990 Cmd Rej: Relative Cost (RC) of true PC must be less than RC of mate
The value specified for the rc parameter value of a true point code cannot be greater than the relative cost of its mate. If the pc parameter value is a true point code, the subsystem must have a lower relative cost than all other mated subsystems in the group.
Recovery
Re-enter the ent/chg-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.899 E2991 Cmd Rej: Relative Cost (RC) of true MPC must be less than RC of mate
The value specified for the materc parameter for a true mated point code cannot be greater than the relative cost of its mate. If the mpc parameter value is a true point code, then the subsystem must have a lower relative cost than all other mated subsytems in the group.
Recovery
Re-enter the ent/chg-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.900 E2992 Cmd Rej: MSSN and MateRC must be specified since MPC is specified
If the mpc parameter is specified, the mssn and materc parameters must be specified.
Recovery
Re-enter the ent/chg-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.901 E2993 Cmd Rej: True Point Code must remain primary entity
The true point code in the MAPGROUP must be and remain the primary PC/SSN for that MAPGROUP. The RC value of the pc parameter cannot be changed nor can a new point code be added to the MAPGROUP, which would result in the true point code no longer being the primary PC/SSN of the MAPGROUP.
Recovery
2.2.902 E2994 Cmd Rej: True Point Code may not be routed to self
The value specified for the pc and mpc parameters cannot route the true point code to itself.
Recovery
Re-enter the ent/chg-map command that generated this error, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.903 E2995 Cmd Rej: True Point Code can only have one mate
A true point code can have only one mate.
Recovery
2.2.904 E2996 Cmd Rej: Intermed GTT Load sharing feature must be ON
The Intermediate Global Title Translation Load Sharing (IGTTLS) feature must be turned on before the ent/chg/rtrv-mrn commands can be entered.
For the enable-ctrl-feat command, the IGTTLS feature must be turned on before the GTT LS ARI feature can be enabled.
Recovery
2.2.905 E2997 Cmd Rej: PC must match NPCFMTI set in CHG-STPOPTS
The format of any of the specified point code parameters must match the format that was assigned with the chg-stpopts:npcfmti parameter.
Refer to the chg-stpopts command description in Commands User's Guide for valid npcfmti parameter values.
Recovery
2.2.906 E2998 Cmd Rej: PC cannot match the SID
The value specified for the point code parameter cannot be the same as the EAGLE site identifier (SID).
Recovery
2.2.907 E2999 Cmd Rej: Failed reading the MRN table
The Mated Relay Node (MRN) table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.908 E3000 Cmd Rej: DPC is referenced by SCCP in MRN table or SCCP Serv table
A Destination Point Code (DPC) that is referenced by an SCCP as a point code in the Mated Relay Node (MRN) or SCCP SERV table cannot be deleted.
Recovery
2.2.909 E3001 Cmd Rej: SDATE must be earlier or equal to EDATE
The date that is specified for the sdate parameter must be earlier than or equal to the date specified for the edate parameter.
Recovery
Re-enter the rtrv-log or rtrv-seculog command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.910 E3002 Cmd Rej: STIME must be earlier or equal to ETIME
The time specified for the stime parameter must be earlier than or equal to the time specified for the etime parameter.
Recovery
Re-enter the rtrv-seculog 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. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.911 E3003 Cmd Rej: Modification of security log not allowed
The copy-fta and copy-tbl commands cannot be used to modify the security log.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.912 E3004 Cmd Rej: Un-uploaded security log entries exist on standby fixed disk
All security log entries must be uploaded before the standby fixed disk can be initialized or formatted.
Recovery
2.2.913 E3005 Cmd Rej: Security log command already in progress
A security log command cannot be entered while another security log command is already in progress.
Recovery
Re-enter the copy/rept-stat/rtrv-seculog command after the active security log command finishes processing.
2.2.914 E3006 Cmd Rej: Hex Digit Support for GTT feature must be ON
For the chg-gsmsmsopts command, the Hex Digit Support for GTT feature must be turned on before hexadecimal values can be specified for the mosmsgta parameter.
For the ent/chg/dlt/rtrv-gta commands, the Hex Digit Support for GTT feature must be turned on before hexadecimal values can be specified for the gta/saddr and egta/eaddr parameters.
For the ent/chg/rtrv-gtt commands, the Hex Digit Support for GTT feature must be turned on before hexadecimal values can be specified for the gta and egta parameters.
For the ent/chg/rtrv-gtmod commands, the Hex Digit Support for GTT feature must be turned on before hexadecimal digits can be specified for the npds and nsds parameters.
Recovery
2.2.915 E3007 Cmd Rej: Specified UID is reserved for system use
The user IDs seas and none are reserved for system use and cannot be specified in the command.
Recovery
Re-enter the ent-user command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.916 E3008 Cmd Rej: Failed reading the security log attributes table
The Security Log Attributes table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.917 E3009 Cmd Rej: LNP feature must be ON
The LNP feature (an LNP ported TNs quantity) must be enabled before the LNP 150,000 LRNs feature or the LNP 300,000 NPANXXs feature can be enabled.
The LNP feature must be turned on before the following actions can be performed:
- Change the LNP database
- Turn on the Wireless Number Portability (WNP) feature
- Retrieve or report on LNP information or measurements
- Enter the
chg/rtrv-lnpopts,ent/chg/dlt/rtrv-acg-mic,ent/chg/dlt/rtrv-acg-noc,ent/chg/dlt/rtrv-lnp-serv, orrept-stat-lnpcommand - Specify the appl=lnp parameter in the
ent-ss-applcommand - Specify the data parameter in the
rst-cardcommand -
Change a system cpctype=lnp and the LNP subsystem.
Recovery
2.2.918 E3012 Cmd Rej: LNP Subsystem is offline in database
The LNP subsystem must be online before the LNPQ subsystem number can be specified as a value for the ssn parameter.
Recovery
2.2.919 E3013 Cmd Rej: No other GWS stop actions can be specified with STRIP
The GWS STRIP stop action cannot be specified with another stop action in the same action set. The GWS STRIP stop action is mutually exclusive with other GWS stop actions.
Recovery
2.2.920 E3014 Cmd Rej: Card location specified must be an SCCP card
The value specified for the loc parameter must identify a configured Service Module card running the VSCCP application or a GTT-enabled IPSG card.
Recovery
2.2.921 E3015 Cmd Rej: Cannot delete last route to a DPC referencd by the MRN table
If any destinations referencing the routeset exist in the MRN table, then the last route of the routeset cannot be deleted.
Recovery
2.2.922 E3017 Cmd Rej: GWS DUP Point Code is required for GWS DUP stop action
For the chg-gws-actset command, the GWS DUP point code (GDPC) must be configured in the STPOPTS table before the GWS DUP stop action can be specified.
For the chg-stpopts command, the GWS DUP point code (GDPC) cannot be set to invalid if the GWS DUP stop action is configured.
Recovery - chg-gws-actset
- Display the GDPC by entering the
rtrv-stpoptscommand. If the following line is displayed in the output, that GDPC is not configured:GDPCA -------------- - Configure the GDPC using the
chg-stpoptscommand. - Re-enter the
chg-gws-actsetcommand.Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - chg-stpopts
2.2.923 E3018 Cmd Rej: SSNE should be greater than SSN
The value specified for the ssne parameter must be greater than the value specified for the ssn parameter.
Recovery
Re-enter the ent/dlt-rmt-appl command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.924 E3019 Cmd Rej: Conflicts with existing entry
The following conditions may cause this error:
-
A point code was entered of the same network type (ANSI/ITUI/ITUN) that does not match the point code already in the Remote Application table for that type.
-
The point codes match, but the si value is already present (except when si=3).
-
The point code matches, si=3, and one or more subsystem numbers already entered overlap the range specified by the ssn and ssne parameter values.
Recovery
2.2.925 E3020 Cmd Rej: Remote Application not found
The values specified for the ipc, si, and ssn...ssne parameters must already exist.
Recovery
2.2.926 E3022 Cmd Rej: LOC or DCNAME must be specified
The diameter card location or diameter connection name must be specified with the peakreset parameter.
Recovery
2.2.927 E3031 Cmd Rej: MULTCC entry cannot be NONE
The multcc=none parameter cannot be specified.
Recovery
Re-enter the chg-gsmopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the G-Port User's Guide for assistance.
2.2.928 E3040 Cmd Rej: <string> cannot be used in this command
The value specified for a parameter cannot be a reserved word for another parameter in the command. Reserved words (for example, “none”) cannot be used to name a group.
Recovery
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 information about reserved words for the command.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.929 E3041 Cmd Rej: Timeout
A timeout occurred while processing the command.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.930 E3042 Cmd Rej: Command Response Timeout, freeing up scroll area
While in keyboard send/receive (KSR) mode, a command was entered, but no response from the OAM was received.
Recovery
2.2.931 E3043 Cmd Rej: IMT test in progress
act/init-flash, clr-imt-stats, flash/init-card, init-imt-gpl, init-network, rept-imt-info, rept-imt-lvl1, and rept-imt-lvl2 commands cannot be entered during an Extended Bit Rate Error Test (BERT).
Note:
Theinit-card command can be entered during an Extended BERT; however, the appl parameter cannot be specified in the command.
The alw/conn/disc/inh/rmv-imt commands cannot be entered during an IMT Fault Isolation Test or an Extended BERT.
The chg-ctrl-feat cannot be used to turn the HIPR2 High Rate Mode feature on or off during an Extended BERT.
The init-mux command cannot be entered during an IMT Fault Isolation Test unless the force=yes parameter is specified. The command cannot be entered during an Extended BERT even if the force=yes parameter is specified.
Recovery
Perform one of the following actions:
- Re-enter the command after the test is complete.
- Re-enter the
init-muxcommand specifying the force=yes parameter (for the IMT Fault Isolation Test).Note:
If theinit-mux:force=yescommand is entered for the bus that is NOT under test, then the EAGLE will initialize.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.932 E3044 Cmd Rej: Invalid parameter specified for report type
If the report=util parameter is specified, then the ebucket and sbucket parameters cannot be specified.
The report=err parameter must be specified before the erronly and mode parameters can be specified.
A value of hiprerr, hipr2err, or hmuxerr must be specified for the report parameter before the sshelf and eshelf parameter can be specified.
The sshelf parameter must be specified and a value of hiprerr or hipr2err must be specified for the report parameter before the sslot and eslot parameters can be specified.
Recovery
Re-enter the rept-imt-info 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.933 E3045 Cmd Rej: Alternate bus must be IS-NR
The state of the alternate IMT bus must be IS-NR before the bus can be tested.
Recovery
2.2.934 E3046 Cmd Rej: Target bus must be inhibited
The state of the IMT bus being tested must be OOS-MT-DSBLD (out of service maintenance disabled) before the tst-imt command can be entered for a Fault Isolation test.
Recovery
2.2.935 E3047 Cmd Rej: Parameter combination invalid
For the
clr-imt-stats and
rept-imt-lvl2 commands, the
s/e or
sloc/eloc parameter combination must
be specified.
For the
ent/chg-e1 and
ent/chg-t1 commands, if the
linkclass=unchan parameter is
specified, then the
chanbrdg=on or
cas=on parameters cannot be
specified. The
linkclass=unchan parameter must be
specified before the
minsurate parameter can be
specified.
For the
ent/chg-ls commands, ITUTFR cannot be
specified for a link set to be configured for APCN16.
For the
ent-ip-conn command, the
rhost and
rport must be specified with
prot=tcp/udp.
For the
rept-gb-lvl2 command, if the
sloc or
eloc parameter is specified, then
the
loc parameter cannot be specified.
For the
rept-imt-lvl1 command, the
s/e, sloc/eloc, and
sshelf/eshelf parameter combinations
cannot be specified together.
For the
rtrv-dconn command, multiple
combinations of optional parameters are not allowed.
For the
rtrv-gttset command, if the
setidx parameter is specified, then
no other parameter can be specified; if the
npsn parameter is specified, then only
settype cane be specified; if the
gttsn parameter is specified, then
the
settype, netdom, actsn,
gtmodid, and
sxudt parameters cannot be specified.
For the
rtrv-ip-host command, the
Display=all and
realm parameters must not be
specified together.
For the tst-imt
command, if the
type=faulttest parameter is
specified, then the
time,
maxerr, and
action parameters cannot be
specified. If the
action=stop parameter is specified,
then the
time and
maxerr parameters cannot be
specified.
Recovery
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.
2.2.936 E3048 Cmd Rej: Starting address/location/shelf must be specified
For the clr-imt-stats and rept-imt-lvl1 commands, the s, sloc, or sshelf parameter must be specified.
Recovery
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.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.937 E3049 Cmd Rej: Ending bucket cannot be less than starting bucket
The value specified for the ebucket parameter must be greater than or equal to the value specified for the sbucket parameter.
Recovery
Re-enter the rept-imt-info command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.938 E3050 Cmd Rej: L parameter cannot be used in combination with LOC
The l and loc parameters cannot be specified together in the command.
Recovery
Re-enter the rept-imt-lvl2 command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.939 E3051 Cmd Rej: Source address/location must be specified
The l or loc parameter must be specified in the command.
Recovery
Re-enter the rept-imt-lvl2 command that generated this error messgage, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.940 E3052 Cmd Rej: IMT statistics collection in progress - Repeat later
The command was entered when the system was collecting the Interprocessor Message Transport (IMT) statistics for the hourly performance monitoring report.
Recovery
Wait for the system to finish collecting the IMT statistics, then re-enter the command.
-
If IMT errors are found during the collection process, the hourly performance monitoring report is generated and the collection process has finished. When the hourly performance monitoring report is generated, re-enter the command.
-
If no IMT errors are found during the collection process, the hourly performance monitoring report is not generated. In this case, wait five minutes, then re-enter the command.
2.2.941 E3053 Cmd Rej: Failed reading ACG NOC table
The Automatic Call Gapping (ACG) Node Overload Control (NOC) table is corrupt or cannot be found.
Recovery
Re-enter the ent/chg/dlt/rtrv-acg-noc command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.942 E3054 Cmd Rej: The specified overload level is not defined
The value specified for the lvl parameter must already exist.
Recovery
2.2.943 E3055 Cmd Rej: Failed reading ACG MIC table
The Automatic Call Gapping (ACG) Manually Initiated Control (MIC) table is corrupt or cannot be found.
Recovery
Re-enter the ent-acg-mic command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.944 E3056 Cmd Rej: Parameters ND, INTVL, and AINTVL are required
If the type=all parameter is specified, then the aintvl, intvl, and nd parameters must be specified.
Note:
If the type=all parameter is specified, an MIC with type=all must exist.Recovery
Re-enter the ent-acg-mic command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance
2.2.945 E3057 Cmd Rej: Parameters SERV and DGTS are not allowed for TYPE = ALL
If the type=all parameter is specified, then the serv and dgts parameters cannot be specified.
Note:
If the type=all parameter is specified, then an MIC with type=all must exist.Recovery
Re-enter the ent/chg/dlt/rtrv-acg-mic command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance
2.2.946 E3058 Cmd Rej: Parameters SERV and DGTS are required
If the type=sd parameter is specified, then the serv and dgts parameters must be specified.
Note:
If the type=sd parameter is specified, an MIC with the same serv and dgts must exist.Recovery
Re-enter the ent/chg/dlt/rtrv-acg-mic command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance
2.2.947 E3059 Cmd Rej: Parameter ND is not allowed
If the type=sd parameter is specified, then the nd parameter cannot be specified.
Note:
If the type=sd parameter is specified, an MIC with the same service and digits must exist.Recovery
Re-enter the ent/chg-acg-mic command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance
2.2.948 E3060 Cmd Rej: Parameter AINTVL is required
If the serv=ain parameter is specified, then the aintvl parameter must be specified.
Recovery
Re-enter the ent/chg-acg-mic command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.949 E3061 Cmd Rej: Parameter INTVL is not allowed
If the serv=ain parameter is specified, then the intvl parameter cannot be specified.
Recovery
Re-enter the ent/chg-acg-mic command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.950 E3062 Cmd Rej: Parameter INTVL is required
If the serv=in parameter is specified, then the intvl parameter must be specified.
Recovery
Re-enter the ent/chg-acg-mic command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.951 E3063 Cmd Rej: Parameter AINTVL is not allowed
If the serv=in parameter is specified, then the aintvl parameter cannot be specified.
Recovery
Re-enter the ent/chg-acg-mic command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.952 E3064 Cmd Rej: DGTS parameter must be 3 or 6–10 digits
The value specified for the dgts parameter must be 3 or 6–10 digits in length.
Recovery
Re-enter the ent/chg/dlt/rtrv-acg-mic command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Administration and LNP Feature Activation Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.953 E3065 Cmd Rej: ND parameter must be 3 or 6-10
The value specified for the nd parameter must be 3 or a number from 6–10.
Recovery
Re-enter the ent/chg-acg-mic command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.954 E3066 Cmd Rej: A MIC of TYPE=ALL already exists
If the type=all parameter is specified, then a manually initiated control (MIC) that applies to all query services cannot not already exist.
Recovery
2.2.955 E3067 Cmd Rej: A MIC with the same service and digits already exists
If the type=sd parameter is specified, then an ACG manually initiated control (MIC) containing the same query service and digits cannot already exist in the database.
Recovery
2.2.956 E3068 Cmd Rej: Table full - a maximum of 256 TYPE=SD MICs are allowed
The LNP database has a maximum capacity of 256 Manually Initiated Controls.
Recovery
2.2.957 E3069 Cmd Rej: Parameter ND, DRTN, INTVL, or AINTVL is required
If the type=all parameter is specified, then the nd, drtn, intvl, or aintvl parameter must be specified.
Recovery
Re-enter the ent/chg-acg-mic command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.958 E3070 Cmd Rej: Parameter DRTN or AINTVL is required
If the serv=ain parameter is specified, then the drtn or aintvl parameter must be specified.
Recovery
Re-enter the chg-acg-mic command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.959 E3071 Cmd Rej: Parameter DRTN or INTVL is required
If the serv=in parameter is specified, then the drtn or intvl parameter must be specified.
Recovery
Re-enter the chg-acg-mic command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.960 E3072 Cmd Rej: No MIC of TYPE=ALL exists
If the type=all parameter is specified, then an MIC with type=all must already exist.
Recovery
- Display the values of existing ACG controls. Enter the
rtrv-acg-miccommand. - Re-enter the
chg/dlt-acg-miccommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.961 E3073 Cmd Rej: No MIC with the same service and digits exists
The values specified for the serv and dgts parameters must already exist in the LNP database.
Recovery
2.2.962 E3074 Cmd Rej: AND parameter must be 6 or 10
A value of 6 or 10 must be specified for the and parameter.
Recovery
Re-enter the ent/chg-acg-noc command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.963 E3075 Cmd Rej: IND parameter must be 6 or 10
A value of 6 or 10 must be specified for the ind parameter.
Recovery
Re-enter the ent/chg-acg-noc command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.964 E3076 Cmd Rej: The specified overload level has already been defined
The value specified for the lvl parameter cannot already exist.
Recovery
2.2.965 E3078 Cmd Rej: DPC cannot be defined as a remote application IPC
A remote application Internal Point Code (IPC) cannot be specified as a value for the dpc parameter.
Recovery
2.2.966 E3079 Cmd Rej: Command cannot be executed on an MGMT terminal
If the keyboard of a terminal is defined as type mgmt then the lock command cannot be specified.
Recovery
2.2.967 E3080 Cmd Rej: ACTION must be specified as FORWARD, DUPLICATE, or DUPDISC
If the mapset, ri, or tt parameter is specified, then the value specified for the action parameter must be forward, duplicate, or dupdisc.
Recovery
Re-enter the ent-gsmmap-scrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - Features User's Guide for assistance.
2.2.968 E3081 Cmd Rej: NACTION parameter must be FORWARD, DUPLICATE, or DUPDISC
The naction parameter must have a value of forward, duplicate, or dupdisc before the npc/npca/npci/npcn/npcn24, nssn, nri, ntt, or naction parameters can be specified.
If the naction parameter has a value of forward, duplicate, or dupdisc, then the npc/npca/npci/npcn/npcn24 parameter and the nssn parameter must be specified.
Recovery
Re-enter the chg-gsmmap-scrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.969 E3082 Cmd Rej: NDFLTACT must be specified (FORWARD, DUPLICATE, or DUPDISC)
If the nmapset, nri, or ntt parameter is specified, and the ndfltact parameter is not specified, then the dfltact parameter must have a previously provisioned value of forward, duplicate, or dupdisc.
Recovery
2.2.970 E3083 Cmd Rej: NACTION must be specified (FORWARD, DUPLICATE, or DUPDISC)
If the nmapset, nri, or ntt parameter is specified, and the naction parameter is not specified, then the action parameter (see the ent-gsmmap-scrn command) must have a value of forward, duplicate, or dupdisc.
Recovery
2.2.971 E3084 Cmd Rej: Both OAM cards must be of the same type
The two cards that run the OAM must be the same type before the database can be updated.
Note:
Legacy TDM, GPSM-II, and MDAL cards cannot be installed in the same system as E5-TDM, E5-MCAP, and E5-MDAL cards.For the chg-db command, if the OAM is in mixed mode, and the 10,000 Routesets or Integrated GLS feature is enabled or the Integrated Measurements feature is turned on, then the action=repair parameter cannot be specified.
copy-disk command cannot be entered.
Caution:
Contact My Oracle Support before entering thecopy-disk command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery
2.2.972 E3085 Cmd Rej: Cannot change the RC parameter with the ENT command
The ent-mrn command cannot be used to change the relative cost (rc parameter) assigned to a point code.
Recovery
Enter the chg-mrn command to change the value of the rc parameter. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.973 E3086 Cmd Rej: New PC and RC must be entered as a pair
If a new point code is being added to the Mated Relay Node (MRN) table, or if the Flexible GTT Loadsharing feature is enabled, and the mrnset=new parameter is specified, then the pc and rc parameters must be specified together in the command.
Recovery
2.2.974 E3087 Cmd Rej: Must enter at least one PC/RC pair
For the ent/chg-mrn commands, when adding point codes, at least one additional point code must be specified.
For the chg-sccp-serv command, when addding new point codes or modifying relative cost values, at least one pc/rc pair must be specified.
Note:
If point codes are being added, then the wt parameter cannot be specified.Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.975 E3088 Cmd Rej: Platformenable or Oamhcmeas option must be on
Caution:
The platformenable and oamhcmeasopts parameters in the chg-measopts command are used to turn on the Measurements Platform collection function and the Integrated Measurements collection function, respectively. After the Measurements Platform or Integrated Measurements collection function is turned on, it cannot be turned off using the chg-measopts command.
For the chg-ctrl-feat command, the Measurements Platform or Integrated Meaurements collection function must be turned on before the 15 Minute Measurements feature can be turned on.
For the chg-measopts command, the platformenable=on or oamhcmeas=on parameter must be specified before the cllibasedname=on parameter can be specified.
For the enable-ctrl-feat command, the Measurements Platform feature and the Meaurements Platform collection function must be turned on before the MTP MAP Screening feature can be enabled.
The Measurements Platform or Integrated Meaurements collection function must be turned on before the rept-ftp-meas or rept-stat-meas command can be entered.
For the rept-meas command, retrievals for period=LAST, SPECIFIC, and ALL are rejected by the EAGLE if either measplat or integrated measurements is not enabled.
Recovery
2.2.976 E3089 Cmd Rej: FTP Server password must be 1 - 15 characters in length
A password that is between 1 - 15 characters in length must be entered.
Recovery
2.2.977 E3090 Cmd Rej: Full Point Code must be specified
The value specified for the pc/pca/pci/pcn/pcn24, np/npca/npci/npcn/npcn24, epc/epca/epci/epcn, and realpc/realpca/realpci/realpcn parameters must be a full point code. A full point code contains numerical values for all segments of the point code.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.2.2.978 E3091 Cmd Rej: PC/SSN must be given with Action FORWARD, DUPLICATE, DUPDISC
If the command contains the dfltact, ndfltact, or (n)action parameter that is set to a value of forward, duplicate, or dupdisc, then the point code and subsystem number parameters must be specified in the command.
Recovery
2.2.979 E3092 Cmd Rej: PC/SSN must be specified if FORCE is specified
If the force parameter is specified, then the point code and subsystem number parameters must be specified.
Recovery
Re-enter the ent/chg-gsmmap-scrn or ent/chg-gsms-opcode command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.980 E3093 Cmd Rej: EROUTE not Configured
At least one STC card must be configured before the rept-stat-mon command can be entered.
Recovery
2.2.981 E3094 Cmd Rej: Both OAM cards must be of same type to perform upgrade
Both OAM cards installed in the system must be of the same type before the upgrade can be performed.
Caution:
It is strongly recommended that theact-upgrade command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.
Recovery
2.2.982 E3095 Cmd Rej: LHOST/ALHOST location not found
The card location associated with the lhost and alhost parameters must already exist in the IP Link table and the associated signaling link must be activated.
Recovery
2.2.983 E3096 Cmd Rej: Invalid socket/association ratio for card type
An invalid socket/association ratio exists for this type of card.
Recovery
2.2.984 E3098 Cmd Rej: GTA must not be NONE
A value of none cannot be specified for the gta, gta1, gta2, and gta3 parameters.
Recovery
Re-enter the chg-ppsopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.985 E3099 Cmd Rej: GTA must be specified when NGTA is specified
For the chg-gsmopts command, if the nppsmsgta parameter is specified, then the ppsmsgta parameter must be specified.
For the chg-ppsopts command, if the ngta parameter is specified, then the gta parameter must be specified
Recovery
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.
2.2.986 E3100 Cmd Rej: GTA doesn't exist in PPSOPTS Table
If the ngta parameter is specified, then the value specified for the gta parameter must already exist in the PPSOPTS table.
Recovery
- Display the entries n the PPSOPTS table. Enter the
rtrv-ppsoptscommand. - Re-enter the
chg-ppsoptscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.987 E3101 Cmd Rej: Maximum number of GTAs already provisioned
A maximum of 32 GTA values (for 32 IN platforms) can be defined in the PPSOPTS table.
Recovery
2.2.988 E3102 Cmd Rej: NGTA already exists in PPSOPTS Table
The value specified for the ngta parameter cannot already exist in the PPSOPTS table.
Recovery
- Display the entries in the PPSOPTS table. Enter the
rtrv-ppsoptscommand. - Re-enter the
chg-ppsoptscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.989 E3103 Cmd Rej: GTT must be ON before XGTT can be enabled
The GTT feature must be turned on before the XGTT Table Expansion feature can be enabled.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.990 E3104 Cmd Rej: Either LOC or APPL or TYPE must be specified
Either the loc, appl, or type parameter must be specified in the command. The parameters cannot be specified together in the command except when appl=ipsg.
Note:
When appl=ipsg, permitted values of the type parameter are type=gtt (initialize all GTT-enabled IPSG cards) and type=nosccp (initialize all GTT-disabled IPSG cards).Recovery
2.2.991 E3107 Cmd Rej: At least one of SMSMR services must be configured
The Portability Check for Mobile Originated SMS feature or the PPSMS feature must be turned ON, or the MO SMS ASD/ MO SMS B-Party Routing/ MO SMS GRN/ MO SMS IS41-to-GSM Migration/ MO-based GSM SMS NP/ MO-based IS41 SMS NP feature must be ENABLED before the SMSMR Service is entered with the SRVCNAME parameter.
Recovery
2.2.992 E3109 Cmd Rej: Temporary feature key is not allowed for the feature
A temporary feature access key cannot be used to enable or turn on features that do not allow a temporary feature access key. Refer to the command description in Commands User's Guide for a list of features that allow a temporary feature access key.
Recovery
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.993 E3110 Cmd Rej: Loading Mode unstable due to maint. baseline not established
The command was entered while the MASP was re-initializing.
Note:
Loading mode support denies the execution of LNP database change commands when the system is in an unstable loading mode. An unstable loading mode will result in all STP or LNP database update commands being rejected.Recovery
Re-enter the command that generated this error message after the MASP has re-initialized.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.994 E3111 Cmd Rej: Loading mode unstable. System’s LIM service is unavailable
Less than 80% of the system’s LIM cards and the minimum number of VSCCP or SCCP cards required to support 80% of the LIM cards are not in service or are inhibited (OOS-MT-DSBLD).
Note:
Loading mode support denies the execution of LNP database change commands when the system is in an unstable loading mode. An unstable loading mode will result in all STP or LNP database update commands being rejected.Recovery
2.2.995 E3112 Cmd Rej: Loading Mode unstable due to SCCP service is deficient
The system detected that LIM cards are being denied SCCP service or the state of a type DSM card is not in-service normal (IS-NR) or out-of-service maintenance disabled (OOS-MT-DSBLD).
Note:
Loading mode support denies the execution of LNP database change commands when the system is in an unstable loading mode. An unstable loading mode results in all STP or LNP database update commands being rejected.Recovery
2.2.996 E3114 Cmd Rej: For GFLEX, the SNAI must be SUB, NATL OR INTL
If the value specified for the SRVCNAME parameter is GFLEX, then the SNAI parameter must be specified as SUB, NATL, or INTL.
Recovery
2.2.997 E3115 Cmd Rej: Dual ExAP Config/SIPNP/DEIR Feature must be enabled
If the TYPE specified is EPAP, ELAP, or GTT for VSCCP, then the Dual ExAP Config, SIPNP, or DEIR feature must be enabled. For appl=ipsg and type=gtt, no such features must be enabled.
Recovery
2.2.998 E3117 Cmd Rej: No available primary MCP
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.999 E3118 Cmd Rej: Failed Reading GTT TT table
The GTT Table is corrupt or cannot be found by the system.
Recovery
Re-enter the chg/dlt-loopset command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1000 E3119 Cmd Rej: Failed Reading GTT TRANS table
The GTT Trans table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1001 E3120 Cmd Rej: Failed reading GTT DBMM table
The GTT DataBase Memory Manager (DBMM) table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1002 E3121 Cmd Rej: Domain indicated by GTIx must match that of existing TT
If the value specified for the tt parameter is an existing translation type that has gtii/gtin/gtin24/gtiis/gtins=4, then the domain of the new entry must match the existing domain.
Recovery
2.2.1003 E3122 Cmd Rej: SERV has not been assigned a true TT
If the alias parameter is specified, then the serv parameter must already have an assigned translation type.
Recovery
2.2.1004 E3123 Cmd Rej: Failed Reading LNP TT SERV table
The LNP TT SERV table is corrupt or cannot be found by the system.
Recovery
Re-enter the ent/chg/dlt/rtrv-lnp-serv command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1005 E3124 Cmd Rej: Failed Reading LNP SS Appl table
The LNP TT SS-APPL table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1006 E3125 Cmd Rej: SNP, SNAI and SRVCNAME is mandatory for srvc action
The snp, snai, and srvcname parameters must be specified when the act parameter is set to srvc.
Recovery
2.2.1007 E3128 Cmd Rej: The J1PORT at the specified location is not equipped
The J1 port specified by the j1port parameter must have already been configured with a J1 interface on the specified J1 card with the application as CCS7ITU.
Recovery - tst-j1
- Enter a j1port on the J1 card.
- Re-enter the
tst-j1command on that particular j1port.Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - chg-j1
2.2.1008 E3130 Cmd Rej: The J1PORT at the specified location is already equipped
The port specified by the j1port parameter must not be already equipped with a J1 interface.
Recovery
2.2.1010 E3133 Cmd Rej: AMASLPID must be provisioned before INCSLP=yes
AMASLPID must be provisioned before INCSLP is set to yes.
Recovery
2.2.1011 E3136 Cmd Rej: J1 card location is unequipped
The card in the location specified by the loc parameter must be equipped.
Recovery
2.2.1012 E3138 Cmd Rej: LOC and J1PORT parameter combination must be specified
The loc and j1port parameters must be specified together, if any parameters are specified for the command.
Recovery
2.2.1013 E3139 Cmd Rej: Translation Type is already in LNP database
The value specified for the tt parameter cannot already exist in the LNP database.
Recovery
- Display the existing entries in the LNP database. Enter the
rtrv-lnp-servcommand. - Revise the translation type values as desired. Refer to the ELAP Administration and LNP Feature Activation Guide for assistance.
- Re-enter the
ent-lnp-servcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1014 E3140 Cmd Rej: Service Type is already in LNP database
For the chg-lnp-serv command, the value specified for the nserv parameter cannot already exist in the LNP database.
For the ent-lnp-serv command, if the tt parameter is specified, then the value of the serv parameter cannot already exist in the LNP database.
Recovery
2.2.1015 E3141 Cmd Rej: J1 Port test command not in progress
The action=stop parameter can be specified only when a port test is running.
Recovery
2.2.1016 E3143 Cmd Rej: New Translation Type already in LNP database
The value specified for the ntt parameter cannot already exist in the LNP database.
Note:
A maximum of eight unique LNP services can each be assigned one translation type apiece.Recovery
- Display the existing entries in the LNP database. Enter the
rtrv-lnp-servcommand. - Re-enter the
chg-lnp-servcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.1017 E3144 Cmd Rej: J1 Port test command in progress
For the act-slkcommand, a link cannot be activated if the tst-j1command is in progress on the same port on which the particular link to be activated is configured.
For the tst-j1command, only one port test can run at one time on the J1 port specified by the j1port parameter.
Recovery
2.2.1018 E3145 Cmd Rej: New Translation Type Name already in LNP database
The value specified for the nttn parameter cannot already exist in the LNP database.
Note:
Up to eight unique LNP services can each be assigned one translation type apiece.Recovery
- Display the existing entries in the LNP database. Enter the
rtrv-lnp-servcommand. - Re-enter the
chg-lnp-servcommand that generated this error message, specifying a valid combination of parameters. Refer to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.1019 E3146 Cmd Rej: Service type is not in LNP database
The value specified for the serv parameter must already exist in the LNP database.
Recovery
2.2.1020 E3147 Cmd Rej: Translation Type referenced in LNP database
If a translation type is assigned to the service, then the service cannot be deleted.
Recovery
- Display the entries in the LNP database. Enter the
rtrv-lnp servcommand. - Delete or change the translation types as necessary. Refer to the ELAP Administration and LNP Feature Activation Guide for assistance.
- Re-enter the
dlt-lnp-servcommand that generated this error message. - Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1021 E3148 Cmd Rej: Translation Type Name is not in the LNP database
The value specified for the ttn parameter must already exist in the LNP database.
Recovery
- Display the entries in the LNP database. Enter the
rtrv-lnp-servcommand. - Re-enter the
ent/chg-lnp-servcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.1022 E3149 Cmd Rej: Maximum number of applications already assigned
The maximum number of applications cannot already exist.
Recovery
2.2.1023 E3150 Cmd Rej: Application already assigned
The specified subsystem application cannot already exist.
Recovery
- Display the existing subsystem applications. Enter the
rtrv-ss-applcommand. - Delete applications as necessary. Refer to the appropriate feature manual for assistance.
- Re-enter the
ent-ss-applcommand that generated this error message.
2.2.1024 E3151 Cmd Rej: All signaling links serviced by the J1 must be deactivated
For the chg-j1 command, all signaling links that are serviced by the specified J1 card with application as CCS7ITU must be deactivated before the values for the encode, j1tsel, and ll parameters can be changed.
For the tst-j1 command, all signaling links that provide timeslots serviced by J1 interfaces on the specified card must be deactivated before this command can be entered. None of the signaling links can be running link diagnostic tests (tst-slk and act-cdl commands) when this command is entered.
Recovery
2.2.1025 E3152 Cmd Rej: Application type not in LNP database
The value specified for the appl parameter must already exist in the database.
Recovery
- Display the existing subsystem applications. Enter the
rtrv-ss-applcommand. - Re-enter the
chg/dlt-ss-applcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.1026 E3153 Cmd Rej: Subsystem must be inhibited before it can be OFFLINE
The subsystem must be inhibited before the nstat=offline parameter can be specified.
Recovery
2.2.1027 E3154 Cmd Rej: Subsystem must be in opposite state of change
The state of the subsystem is already online (or offline).
Recovery
No action required.
2.2.1028 E3155 Cmd Rej: Subsystem must be inhibited before it can be deleted
The subsystem must be inhibited before it can be deleted.
Recovery
2.2.1029 E3157 Cmd Rej: J1 is assigned to card
Before a J1 card can be deleted, any J1 interfaces assigned to the card must be deleted.
Recovery
2.2.1030 E3160 Cmd Rej: BPS must be 64000 for J1 links in ent-slk
The BPS parameter value must be 64000 for J1 links. By default, BPS is 64000 for J1 links.
Recovery
2.2.1031 E3161 Cmd Rej: Time Slot must not be greater than 24 for J1 links.
The time slot (ts parameter) value must not be greater than 24 for J1 links. The range for time slot is 1 - 24.
Recovery
2.2.1032 E3163 Cmd Rej: ECM must be basic for J1 links.
The error correction method (ECM parameter) value must be BASIC for J1 links. By default, ECM is BASIC for J1 links.
Recovery
2.2.1034 E3167 Cmd Rej: GSERV Entry already exists
The specified entry already exists in the GSERV table. Duplicate entries cannot exist in the GSERV table.
Note:
A maximum of 256 tt values, 50 gta values, and 50 opc values can be provisioned in the GSERV table.
Recovery
Perform one of the following actions:
-
Verify that the gserv data was entered correctly and re-enter the
ent-gserv-datacommand. -
Display the data in the GSERV table. Enter the
rtrv-gserv-datacommand. Verify that the gserv data already exists in the GSERV table.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1035 E3169 Cmd Rej: No change required for this timer and L2tset
Timers are not allowed to change for a level 2 timer set (l2tset parameter) value greater than 35.
Recovery
2.2.1036 E3170 Cmd Rej: All signaling links serviced by this J1 must be deleted
All signaling links providing time slots serviced by the specified J1 interface must be deleted before the J1 interface can be deleted. Use the dlt-slk command to delete the signaling links providing the time slots.
Recovery
2.2.1037 E3171 Cmd Rej: TS value on the J1 already in use by a signaling link
A specific time slot can be assigned in the ts parameter to only one J1 signaling link for the J1 interface that services that time slot.
Recovery
2.2.1038 E3172 Cmd Rej: Alias is not assigned to SERV
The specified alias must be associated with the LNP service to be deleted.
Recovery
2.2.1039 E3177 Cmd Rej: FORCE=YES must be specified if NUM is greater than 50
If the value specified for the num parameter is greater than 50, then the force=yes parameter must be specified.
Recovery
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.
2.2.1040 E3179 Cmd Rej: SIPNP Feat not enabled or no ENUM/SFLOG card provisioned
chg/dlt/ent/rtrv-ip-conn command, the
SIP NP feature must be enabled before configuring any SIP-related information,
or at least one ENUM/IPS with SFLOG card must be provisioned before entering
any ENUM/IPS with SFLOG connection information.
At least one IPS card with SFLOG=yes must be provisioned before entering any TCP connection information on IPS.
For the
rept-stat-ipconn command, the SIP NP
feature must be enabled before retrieving the dynamic status of the SIP
transport, and at least one ENUM card must be provisioned before retrieving the
dynamic status of ENUM connections, and at least one IPS card with SFLOG=yes
must be provisioned before entering any TCP connection information on IPS.
Recovery
- Enter the
rtrv-crtl-featcommand to display the status of the SIP NP feature, or enter thertrv-cardcommand to display the cards in the database. - If necessary, enter the
enable-ctrl-featcommand to enable and turn ON the SIP NP feature, or configure a card running the ENUMHC application. - Re-enter the command that generated this error message, specifying a valid combination of parameters.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1041 E3180 Cmd Rej: TCP protocol is not supported for ENUM card
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1042 E3181 Cmd Rej: Card location specified must be an SIP/ENUM/SFLOG card
Recovery
- Enter the
rtrv-cardcommand to verify the card location is provisioned as an SIP, ENUM or IPS with SFLOG card. - Re-enter the command that generated this error message, specifying a valid card location.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1043 E3182 Cmd Rej: Failure accessing ENUMACL table
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1044 E3183 Cmd Rej: Failure accessing ENUMPRID table
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1045 E3184 Cmd Rej: Failure accessing ENUMPROF table
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1046 E3185 Cmd Rej: Failure accessing ENUM DNBLK table
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1047 E3186 Cmd Rej: TT, TTN, & DV parameters are not allowed with ALIAS
If the alias parameter is specified, then the tt, ttn, and dv parameters cannot be specified.
Recovery
Re-enter the ent-lnp-serv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.1048 E3187 Cmd Rej: Card location specified must be an ENUM card
Recovery
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1049 E3188 Cmd Rej: ENUM not Configured
Recovery
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1050 E3189 Cmd Rej: At least one profile name must be specified
Recovery
Re-enter the command that generated this error message, specifying at least one profile.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1051 E3190 Cmd Rej: RRDOMAIN must be specified
Recovery
Re-enter the command that generated this error message, specifying RRDOMAIN.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1052 E3191 Cmd Rej: RPDOMAIN must be specified
Recovery
Re-enter the command that generated this error message, specifying RPDOMAIN.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1053 E3192 Cmd Rej: Profile Name not present in ENUM PROF table
Recovery
- Enter the
rtrv-enum-profcommand to display the entries in the ENUM Profile Table. - Re-enter the command that generated this error message, specifying a valid profile name.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1054 E3193 Cmd Rej: ENUM ACL table is full
Recovery
- Enter the
rtrv-enum-aclcommand to display the entries in the ENUM ACL Table. - Enter the
dlt-enum-aclcommand to delete an entry from the ENUM ACL Table. - Re-enter the command that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1055 E3194 Cmd Rej: ENTITYID or SDN and EDN must be specified
Recovery
Re-enter the command that generated this error message, specifying either the ENTITYID parameter or the SDN and EDN parameters.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1056 E3195 Cmd Rej: At least one ENUM card must be provisioned
For the chg-mtc-measopts command, at least one ENUM card must be provisioned before the mtchenum=on or mtcdenum=on parameter can be specified.
For the rept-ftp-meas command, at least one ENUM card must be present before the enttype=enum parameter can be specified.
Recovery
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1057 E3196 Cmd Rej: Overlapping entry must be removed
ent-enum-acl command, an overlapping IP Address cannot be provisioned in the ENUM ACL Table.
For the ent-enum-profsel command, an overlapping SDN - EDN cannot already be provisioned in the ENUM DN Block Table.
Recovery
- Enter the
rtrv-enum-aclcommand to display the entries in the ENUM ACL Table, or thertrv-enum-profselcommand to display the entries in the ENUM DN Block Table. - Enter the
dlt-enum-aclcommand to delete an entry from the ENUM ACL Table, or thedlt-enum-profselcommand to delete an entry from the ENUM DN Block Table. - Re-enter the command that generated this error message, specifying a valid combination of parameters.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1058 E3197 Cmd Rej: ENTITY ID or SDN or EDN must be specified
Recovery
Re-enter the command that generated this error message, specifying the ENTITYID, SDN, or EDN parameter.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1059 E3198 Cmd Rej: Failed reading LNP Options table
The LNP Options table is corrupt or cannot be found by the system.
Recovery
Re-enter chg/rtrv-lnpopts command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1060 E3199 Cmd Rej: To change or delete SERV, it must have no LNP aliases
For the chg-lnp-serv command, all LNP aliases for the existing service must be removed from the LNP database before the nserv or ntt parameter can be specified.
For the dlt-lnp-serv command, all aliases associated with the LNP service must be deleted before the service can be changed or deleted.
Recovery
2.2.1061 E3200 Cmd Rej: TST-DISK command prevented
The tst-disk command cannot be entered when other database commands are running.
Recovery
2.2.1062 E3201 Cmd Rej: TST-DISK command in progress
tst-disk command is in progress.
Recovery
Re-enter the command that generated this error message after the test is complete.
2.2.1063 E3202 Cmd Rej: TST-DISK not allowed on Active TDM
If an E5-TDM card is installed, then the disk=fixed parameter cannot be specified.
Recovery
2.2.1064 E3203 Cmd Rej: SDN and EDN digit length must be the same
Recovery
Re-enter the command that generated this error message, specifying valid values for the SDN and EDN parameters.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1065 E3204 Cmd Rej: EDN must be greater than or equal to SDN
Recovery
Re-enter the command that generated this error message, specifying valid values for the SDN and EDN parameters.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1066 E3205 Cmd Rej: SPARM must be specified alone or with RTYPE=NAPTR
RTYPE=NAPTR parameter.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1067 E3206 Cmd Rej: Profile name must be unique
Recovery
Re-enter the command that generated this error message, specifying a unique name for the new profile.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1068 E3207 Cmd Rej: Entity ID must be unique
Recovery
Re-enter the command that generated this error message, specifying a unique entity ID.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1069 E3208 Cmd Rej: Order of the profile is incorrect
Recovery
Re-enter the command that generated this error message, specifying the prn1, prn2, prn3, and prn4 parameters in the proper order.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1070 E3209 Cmd Rej: CPCTYPE cannot be specified without CPC
If the cpctype parameter is specified, then the cpc, cpca, cpci, cpcn, or cpcn24 parameter must be specified.
Recovery
Re-enter the chg-sid command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.1071 E3210 Cmd Rej: CPCTYPE cannot be specified with NCPC
If the cpctype parameter is specified, then the ncpc, ncpca, ncpci, ncpcn, or ncpcn24 parameter cannot be specified.
Recovery
Re-enter the chg-sid command that generated ths error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - SS7 User's Guide for assistance.
2.2.1072 E3211 Cmd Rej: At least one profile name should have valid value
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1073 E3214 Cmd Rej: conglvl1 must be less than conglvl2
Recovery
Re-enter the command that generated this error message, specifying valid congestion levels.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1074 E3215 Cmd Rej: Cannot access GSERV table
The system is busy or the GSERV table is corrupt.
Recovery
Re-enter the ent/dlt/rtrv-gserv-data command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1075 E3216 Cmd Rej: G-Port SRI Query for Prepaid feature is not enabled
The G-Port SRI Query for Prepaid feature must be enabled before the ent/dlt/rtrv-gserv-data commands can be entered.
For the chg-gsmopts command, the G-Port SRI Query for Prepaid feature must be enabled before the dfltrn parameter can be specified.
Recovery
2.2.1076 E3217 Cmd Rej: Profile name is referenced by PRID or DNBLK table
Recovery
- Enter the
rtrv-enum-profselcommand to display the entries in the ENUM Profile Selection Table or the ENUM DN Block Table. - Enter the
dlt-enum-profselcommand to delete the appropriate entry from the ENUM Profile Selection Table or the ENUM DN Block Table. - Re-enter the command that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1077 E3219 Cmd Rej: NAPTR profiles must be unique
Recovery
Re-enter the command that generated this error message, specifying unique NAPTR profiles.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1078 E3220 Cmd Rej: CPCx must be ANSI if CPCTYPE equals LNP
If the cpctype=lnp parameter is specified, then the cpc(x) parameter must be specified with an ANSI point code value.
Recovery
2.2.1079 E3221 Cmd Rej: ENUM PRID Table is full
Recovery
- Enter the
rtrv-enum-profselcommand to display the entries in the ENUM Profile Selection Table. - Enter the
dlt-enum-profselcommand to delete an entry from the ENUM Profile Selection Table. - Re-enter the command that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1080 E3222 Cmd Rej: ENUM PROF Table is full
Recovery
- Enter the
rtrv-enum-profcommand to display the entries in the ENUM Profile Table. - Enter the
dlt-enum-profcommand to delete an entry from the ENUM Profile Table. - Re-enter the command that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1081 E3223 Cmd Rej: ENUM DNBLK Table is full
Recovery
- Enter the
rtrv-enum-profselcommand to display the entries in the ENUM DN Block Table. - Enter the
dlt-enum-profselcommand to delete an entry from the ENUM DN Block Table. - Re-enter the command that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1082 E3225 Cmd Rej: NONE is a reserved name and cannot be used for a TTN
The ttn=none parameter cannot be specified.
Recovery
Re-enter the ent-lnp-serv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.1083 E3226 Cmd Rej: New DV indication must not match old DV indication
The same value cannot be specified for the dv and ndv parameters.
Recovery
Re-enter the chg-lnp-serv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the ELAP Administration and LNP Feature Activation Guide for assistance.
2.2.1084 E3227 Cmd Rej: SPARM=SIP/PSTNSIP is not supported for default profile
Recovery
Re-enter the command that generated this error message, specifying a PRN parameter value other than default.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1085 E3229 Cmd Rej: SDN and EDN must be specified
Recovery
Re-enter the command that generated this error message, specifying both the SDN and EDN parameters.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1086 E3230 Cmd Rej: RRDOMAIN must be specified with sparm=sip/pstnsip
Recovery
Re-enter the command that generated this error message, specifying either SPARM=SIP or SPARM=PSTNSIP.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1087 E3231 Cmd Rej: Default profile cannot be deleted
Recovery
Re-enter the command that generated this error message, specifying a PRN parameter value other than default.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1088 E3233 Cmd Rej: System serial number has not been locked
Note:
Contact My Oracle Support and refer to the command description in Commands User's Guide before using theent-serial-num command to lock the Serial Number table. If an incorrect serial number is locked in the database, a manual procedure and a system disk are required from Oracle.
Recovery
- Display the serial number information. Enter the
rtrv-serial-numcommand. - If the correct serial number has been entered but not locked, enter the
ent-serial-numcommand with the correct serial number and thelock=yesparameter. - If the serial number has not been entered, contact the system administrator and refer to the
ent-serial-numbercommand in Commands User's Guide for the procedure and information to enter and lock the correct serial number. - Re-enter the
enable-ctrl-featcommand that generated this error message.Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1089 E3234 Cmd Rej: Default profile cannot be associated with any profsel entry
Recovery
Re-enter the command that generated this error message, specifying a prX (X=1,2,3,4) parameter value other than default.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1090 E3235 Cmd Rej: Response type can only be changed for the default profile
Recovery
Re-enter the command that generated this error message, specifying prn=default.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1091 E3236 Cmd Rej: SDN and EDN must be unique
Recovery
- Enter the
rtrv-enum-profselcommand as needed to display the entries in the ENUM Profile Selection Table. - Re-enter the command that generated this error message, specifying unique values for the SDN and EDN parameters.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1092 E3237 Cmd Rej: Cannot change the last screenset
Recovery
- Use the
rtrv-scrsetcommand to display all screen sets. - Use the
dlt-scrsetcommand to remove a screen set definition from the database. - Re-enter the
chg-scrsetcommand that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1093 E3239 Cmd Rej: Card does not use MPS functionality
Recovery
- Enter the
rtrv-cardcommand to display the cards in the database. - Re-enter the command that generated this error message, specifying the location of the appropriate VSCCP card.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1094 E3240 Cmd Rej: SIP or ENUM or SFLOG not configured
Recovery
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1095 E3241 Cmd Rej: The Card Set List is not valid, verify or create
act-upgrade command with the threstype assigned to card sets, the list of card sets need to be created and valid.
Recovery
- Enter the
act-upgrade:action=createsetscommand to create a new current list of card sets. - Re-enter the command that generated this error message.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1096 E3242 Cmd Rej: EPAP based SM4G card present in system.
Recovery
- Display the cards in the system. Enter the
rtrv-cardandrtrv-stpcommands. - Replace SM4G cards as necessary. Refer to Maintenance Guide for assistance.
- Re-enter the command that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1097 E3243 Cmd Rej: Unknown hardware configuration
A card with unknown hardware was detected in system whle executing the enable-ctrl-feat command. The card may be in the process of loading, or a loading error has occurred.
Recovery
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1098 E3244 Cmd Rej: UIM number does not exist in UIM Threshold table
The specified UIM number must already exist in the UIM Threshold Table.
Recovery
- Display the valid UIM numbers. Enter the
rtrv-uim-acthreshcommand. - Re-enter the
dlt-uim-acthreshcommand that generated this error messagem specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - System Management User's Guide for assistance.
2.2.1099 E3245 Cmd Rej: PLNP feature must be ON
The PLNP (PCS 1900 LNP) feature must be turned on before a value of pcs can be specified for the (n)serv parameter.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1100 E3246 Cmd Rej: 'none' is an invalid profile name
Recovery
Re-enter the command that generated this error message, specifying a valid profile name.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1101 E3248 Cmd Rej: MFC Off, upgrade aborted
Recovery
- Use the
chg-stpoptscommand to turn ON the MFC feature. - Re-enter the command that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1102 E3250 Cmd Rej: DV must be SCCP when SERV is a user defined type or WSMSC
If a value of udf1, udf2, udf3, udf4, or wsmsc is specified for the serv parameter, then the (n)dv=sccp parameter must be specified.
Recovery
2.2.1103 E3251 Cmd Rej: If specified, (N)DV must be TCAP for specified service
If a value of lnpqs, ain, in, pcs, wnp, or lrnqt is specified for the serv parameter, then the dv=tcap parameter must be specified.
Recovery
Re-enter the ent/chg-lnp-serv command that generated this message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide, the ELAP Administration and LNP Feature Activation Guide, and the appropriate feature manual for assistance.
2.2.1104 E3252 Cmd Rej: A TTN-reserved service type name only if it matches SERV
A reserved service type name can be specified as a value for the(n)ttn parameter only if the name matches the existing service (value specified for the serv parameter).
Recovery
2.2.1105 E3258 Cmd Rej: LHOST and ALHOST must be of the same IP version
The IP address associated with the LHOST and ALHOST should be of the same IP version.
Recovery
- Using the
rtrv-ip-hostcommand, check the version (IPv4 or IPv6) of the IP address corresponding to lhost and alhost. - Change alhost or lhost according to the IP version on which communication channel needs to be opened.
- Check using the
rtrv-ip-hostcommand that lhost and alhost both now correspond to either IPv4 addresses or IPv6 addresses.
2.2.1106 E3260 Cmd Rej: GSERV Table is full
A maximum of 256 tt values, 50 gta values, and 50 opc values can be provisioned in the GSERV table.
Recovery
2.2.1107 E3264 Cmd Rej: LHOST and RHOST must be of the same IP version
The IP address associated with the LHOST and RHOST should be of the same IP version.
Recovery
2.2.1108 E3265 Cmd Rej: Either MCPM or integrated meas is reqrd to turn on COLLECT
Recovery
- Display the status of the Measurements Platform and Integrated Measurements features. Enter the
rtrv-featandrtrv-ctrl-featcommands, respectively.If the Meaurements Platform feature has a status of OFF in the
rtrv-featcommand output, then the feature is not turned on. If the Integrated Measurements feature does not appear in thertrv-ctrl-featoutput, then the feature is not enabled. - Display the status of the Measurements Platform or Integrated Measurements collection function. Enter the
rtrv-measoptscommand. - Enable/turn on the desired feature and collection function as necessary. Refer to the Database Administration - System Management User's Guide for assistance.
- Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1109 E3266 Cmd Rej: Only 6 message relay services can be assigned
A maximum of 6 Message Relay services are allowed.
Recovery
2.2.1110 E3267 Cmd Rej: Failed reading MEAS Control table
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1111 E3268 Cmd Rej: Failed reading MEAS Options table
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1112 E3269 Cmd Rej: Invalid H0/H1 or NH0/NH1 specified
A valid combination of h0 and h1 parameters and/or nh0 and nh1 parameters must be specified. Table 2-5 lists valid parameter combinations.
Table 2-5 Valid h0/h1 or nh0/nh1 Parameter Combinations
| h0 (nh0) parameter | h1 (nh1) parameter |
|---|---|
|
A single value |
A single value |
|
A single value |
A range |
|
A single value |
An asterisk (*) entry |
|
A range |
An asterisk (*) entry |
|
An asterisk (*) entry |
An asterisk (*) entry |
For the chg-scr-sio command, the values specified for the nh0 or nh1 parameters must be valid for the h0 or h1 values already in the database.
Recovery
Re-enter the ent/chg/dlt-scr-sio command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.1113 E3271 Cmd Rej: NSFI is invalid
The value specified for the nsfi parameter must be valid. Refer to the command description in Commands User's Guide for a list of valid values for the nsfi parameter.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters.
2.2.1114 E3272 Cmd Rej: PC does not match existing entry in given SR
The values specified for the area, id, msa, narea, nc, ncm, ni, nid, nnpc, npc, nsp, nssa, nzone, sp, ssa, or zone point code parameters must match the existing entry specified by the sr parameter. The blocked OPC or DPC defined must already exist in the screening reference.
Recovery
2.2.1115 E3273 Cmd Rej: NIC, SI, H0/H1, and PRI entry already exists in given SR
If the screening reference exists, the nic, si, h0/h1, and priorities to be added to the allowed SIO entity set for the SIO screening reference cannot exist in that allowed SIO entity set.
Recovery
2.2.1116 E3274 Cmd Rej: GTTSET and NPSN set domain mismatch
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1117 E3275 Cmd Rej: SFLOG action is being referred by GTTACT Table
Recovery
- Delete the SFLOG action from the GTT Action table.
- Re-enter the
dlt-cardcommand that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1118 E3276 Cmd Rej: Command not allowed while in upgrade mode
The command cannot be entered while the system is in upgrade mode.
For the chg-ctrl-feat command, the HIPR2 High Rate Mode feature cannot be turned on or off if the system is in upgrade mode.
Recovery
Re-enter the command after the system has completed the upgrade that is in progress.
2.2.1119 E3277 Cmd Rej: Maximum number of SFTHROT/SFAPP Action already provisioned
Recovery
- Enter the
rtrv-gttactcommand to display the GTT Action table. - Use the
dlt-gttactcommand to delete an existing SFTHROT GTT Action. - Re-enter the
ent-gttactcommand that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1120 E3278 Cmd Rej: RMIN must be less than or equal to RMAX
The value specified for the rmin parameter must be less than or equal to the value specified for the rmax parameter.
Recovery
Re-enter the chg-assoc command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1121 E3279 Cmd Rej: CWMIN must be less than or equal to assoc BUFSIZE
The value specified for the cwmin parameter must be less than or equal to the value specified for the bufsize parameter.
Recovery
Re-enter the chg-assoc command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1122 E3282 Cmd Rej: Failed reading the SAPC table
The SAPC table is corrupt or cannot be found.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1123 E3283 Cmd Rej: At least one SCCP/SFAPP and one SFLOG must be configured
Recovery
- Enter the
rtrv-cardcommand to display the cards in the system. - Configure an SCCP/SFAPP card running the SCCPHC/SFAPP
application and an SFLOG card running the IPSHC application, if necessary.
Refer to Maintenance Guide, Database Administration - System Management User's Guide, and
Hardware Referencefor assistance. - Re-enter the
rept-stat-sflogcommand that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1124 E3284 Cmd Rej: NPSN Param only supports MBR SETTYPES
Recovery
- Display the existing GTT sets; enter the
rtrv-gttsetcommand. - Re-enter the command that generated this error message, specifying a valid combination of parameters.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1125 E3285 Cmd Rej: Cannot change existing STP True PC if in MAP table
The True Point Code cannot be changed if it already exists in the MAP table.
Recovery
2.2.1126 E3286 Cmd Rej: STP True PC does not exist in MAP table
The true point code must already exist in the mated applications (MAP) table.
Recovery
2.2.1127 E3287 Cmd Rej: Map with STP True PC has a local subsystem SS-APPL assigned
An STP true point code that is assigned to an AIQ, ATINPQ, EIR, INP, LNP, or V-Flex subsystem cannot be deleted.
Recovery
2.2.1128 E3288 Cmd Rej: STP True PC and LNP SSN do not exist in MAP table
The STP true point code and the LNP subsystem number must already be defined in the Mated Applications (MAP) table before the LNP subsystem number and application can be specified.
Recovery
2.2.1129 E3289 Cmd Rej: Must specify NC when NI is specified for ORIGNINC
If the ni parameter is specified, then the nc parameter must be specified.
Recovery
Re-enter the rept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Measurements Reference for assistance.
2.2.1130 E3290 Cmd Rej: No more subsystem can be provisioned with specified True PC
The maximum number of possible entries in the MAP table has been reached for the specified True Point code.
Recovery
Re-enter the ent/chg-map 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1131 E3291 Cmd Rej: Card location specified must be an OAM card
For the clr/disp-disk-stats command, a value of 1113 or 1115 must be specified for the loc parameter.
For the init-flash command, if the initclk parameter is specified, then a value of 1113 or 1115 must be specified for the loc parameter.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1132 E3292 Cmd Rej: Must specify either: ENTRY or ROW with COLUMN
If the entry parameter is specified, then the row and column parameters cannot be specified.
The column and row parameters must be specified together in the command.
Recovery
Re-enter the disp/set-tbl command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1133 E3293 Cmd Rej: Invalid offset
A valid value must be specified for the offset parameter.
Recovery
Re-enter the set-lba or set-tbl 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1134 E3294 Cmd Rej: Security tables may not be altered
The Security Log, User ID, and Password tables cannot be revised.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1135 E3295 Cmd Rej: DEBUG must be ON
The specified command could not be executed because the debug function is turned off.
Recovery
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1136 E3296 Cmd Rej: A timeout occurred while processing SCSI Debug Command
A timeout occurred on the SCSI device before or during the processing of this command.
Recovery
Contact My Oracle Support for assistance. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1137 E3297 Cmd Rej: Failed reading trouble text table
The Trouble Text Table is corrupt or cannot be found by the system.
Recovery
Re-enter the set-uim-acthresh command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1138 E3298 Cmd Rej: If specified, BPS must be 2048000 for LIME1ATM Card
If a link is entered for an E5-ATM or E5-ATM-B card (card type LIME1ATM) then the bps=2048000 parameter must be specified.
Recovery
Re-enter the ent-slk command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1139 E3299 Cmd Rej: Network Security Enhancements feature must be ON
The Network Security Enhancements feature must be enabled and turned on before the secmtpmate, secmtpsid, secmtpsnm and secsccpscmg parameters can be specified.
Recovery
2.2.1140 E3328 Cmd Rej: GSERV entry does not exist
The value specified for the tt, opc/opca/opci/opcn/opcn24, or gta parameter must already exist in the GSERV table.
Recovery
- Display the entries in the GSERV table. Enter the
rtrv-gserv-datacommand. - Re-enter the
dlt-gserv-datacommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1141 E3330 Cmd Rej: APORT or IGM must be enabled
The A-Port or the IS41 GSM Migration (IGM) feature must be enabled before the chg-is41opts command can be entered.
For the chg/rtrv-sid commands, the A-Port or IGM feature must be enabled before the cpctype=mnp parameter can be specified.
Recovery
2.2.1142 E3331 Cmd Rej: ECGSSN/ECDSSN cannot be specified without CGSSN/CDSSN
The ecgssn/ecdssn and cgssn/cdssn parameters must be specified together in the command.
Recovery
Re-enter the rtrv-gta that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1143 E3332 Cmd Rej: GTA/CGPC/OPC/CG-CDSSN/OPCODE/DPC/ADDR are mutually xclusve
The cgpc, cgssn, gta, opc, cdssn, dpc, opcode, acn, pkgtype, family, and saddr parameters cannot be specified together in the command.
If the cgssn and cdssn parameters are both specified in the same command (in any order), then only the value for the last of the two parameters specified is used during processing.
Recovery
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.
2.2.1144 E3333 Cmd Rej: Alarm Inhibition Level cannot be changed
Recovery
- Use the
unhb-almcommand to restore the reporting of alarms for the given device. - Re-enter the
inh-almcommand that generated this error message, specifying a new alarm inhibit at the desired level.
Refer to the command descriptions in Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1145 E3334 Cmd Rej: LNP and specified feature are mutually exclusive
Certain features cannot be enabled, and the INP and AINPQ features cannot be turned on if any of the LNP (LNP ported TNs quantity), LNP 150,000 LRNs, or LNP 300,000 NPANXX features are enabled. Refer to the command description in Commands User's Guide for a list of features that are mutually exclusive with the LNP features.
Recovery
2.2.1146 E3336 Cmd Rej: IGM must be enabled
The IS41 GSM Migration (IGM) feature must be enabled before the is412gsm, gsm2is41, migrpfx, or serverpfx parameter can be specified.
Recovery
2.2.1147 E3337 Cmd Rej: MNP invalid if GPORT enabled and APORT/IGM not enabled
The Mobile Number Portability (MNP) service is not supported if the G-Port feature is enabled and either the A-Port feature or IS41 GSM Migration (IGM) feature is not enabled.
Recovery
2.2.1148 E3338 Cmd Rej: PC/SETID/SSN does not exist in MAP table
If the Flexible GTT Load Sharing (FGTTLS) feature is enabled, and if the ri=ssn parameter is specified, then the values specified for the pc/pca/pci/pcn and ssn parameters must exist in the MAP table in the MAP set specified by the setid parameter, or in the default MAP set if the setid parameter is not specified.
Recovery
2.2.1149 E3339 Cmd Rej: PC/SETID does not exist in MRN table
If the ri=gt parameter is specified, then the value specified for the pc/pca/pci/pcn parameter must already exist in the MRN table.
Recovery
2.2.1150 E3342 Cmd Rej: GFLEX/INP/AINPQ/GPORT/PPSMS/VFLEX OFF or ATINP/AIQ not enbld
The G-Flex, G-Port, INP, AINPQ, PPSMS, IDP Relay, or V-Flex feature must be turned on, or the ANSI41 AIQ or ATINP feature must be enabled before the dn parameter can be specified.
The G-Flex, G-Port, INP, or V-Flex feature must be turned on, or the ATINP, IDP Relay, or any TIF feature must be enabled before the entityid parameter can be specified.
Recovery
2.2.1151 E3343 Cmd Rej: Speed and Duplex must be specified together
The speed and duplex parameters must be specified together in the command.
Recovery
Re-enter the ent-dlk command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1152 E3345 Cmd Rej: SRM, MRC or WT specified with RC (use FORCE=YES)
The force=yes parameter must be specified before the rc parameter can be specified in the same command with the srm, mrc, or wt parameter.
Recovery
Re-enter the chg-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1153 E3346 Cmd Rej: WTx specified while modifying RCx (use FORCE=YES)
The force=yes parameter must be specified before the rc, rc1, rc2, rc3, or rc4 parameter can be specified in the same command with the wt, wt1, wt2, wt3, or wt4 parameter.
Recovery
Re-enter the chg-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1154 E3347 Cmd Rej: FORCE only with RC and SRM, MRC or WT specified
The force parameter can be used only to specify the rc parameter and the srm, mrc, or wt parameter in the same command.
Recovery
Re-enter the chg-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1155 E3348 Cmd Rej: FORCE only with RCx and WTx specified
The force parameter can be used only to specify the rc(X) and wt(X) parameter together in the command.
Recovery
Re-enter the chg-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1156 E3349 Cmd Rej: INP/AINPQ must be ON or APORT/GPORT/PPSMS/MOSMS feat enbld
The G-Port, A-Port, IS41 GSM Migration, MO-based GSM SMS NP, MO-based IS41 SMS NP, MO SMS IS41-to-GSM Migration, or Prepaid SMS Intercept Ph1 feature must be enabled, or the INP or AINPQ feature must be turned on before the mtchnp=on or mtcdnp=on parameter can be specified.
Recovery
2.2.1157 E3350 Cmd Rej: Value of SETID must not exceed 3000 if RI = GT
If the ri=gt parameter is specified, then the value of the setid parameter cannot exceed the value of the maximum MRN set ID.
Recovery
Re-enter the chg-ppsopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1158 E3351 Cmd Rej: Failed reading Prepaid SMS Options Table
The Prepaid SMS Options Table read failed.
Recovery
Re-enter the command that generated this error message.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1159 E3356 Cmd Rej: TIF feature is mutually exclusive with LNP
The LNP feature and any TIF feature (Number Portability/ Additional Subscriber Data / Generic Routing Number) cannot be enabled at the same time.
Recovery
2.2.1160 E3357 Cmd Rej: TIF feature must be enabled
The TIF Number Portability feature must be enabled before the rcause or nprst parameter can be specified.
Recovery
2.2.1161 E3359 Cmd Rej: SETID should be specified only if FGTTLS feature is enabled
Recovery
- Display the status of the FGTTLS feature. Enter the
rtrv-ctrl-featcommand.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.
- Enable the FGTTLS feature as necessary. Refer to Database Administration - GTT User's Guide for assistance.
- Re-enter the command that generated this error message. Refer to the command description in Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1162 E3360 Cmd Rej: GTA already exists in PPSOPTS Table
The value of the gta, gta1, gta2, or gta3 parameter cannot already exist in the database unless the ngta parameter is specified.
Recovery
Re-enter the chg-ppsopts command that generated this error message, specifying a valid combination of parameters. Refer to Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1163 E3361 Cmd Rej: Multiple GTA parameters cannot have the same GTA value
The gta, gta1, gta2, and gta3 parameters cannot have the same value.
Recovery
Re-enter the chg-ppsopts command that generated this error message, specifying a valid combination of parameters. Refer to Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1164 E3362 Cmd Rej: PC (not equal to none) and RI must be entered as a pair
The pc/pca/pci/pcn and ri parameters must be specified together in the command, or a value of none must be specified for the pc/pca/pci/pcn parameter.
Recovery
Re-enter the chg-ppsopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1165 E3363 Cmd Rej: Feature cannot be enabled with DSM less than 4G is present
The feature cannot be enabled because a DSM card with less than 4 gigabytes of memory is present in the system.
Recovery
2.2.1166 E3364 Cmd Rej: Transaction Based GTT Load Sharing Feature must be Enabled
The Transaction-Based GTT Load-Sharing feature must be enabled before the tgtt0, tgtt1, tgttudtkey, or tgttxudkey parameters can be specified.
Recovery
2.2.1167 E3365 Cmd Rej: SETID must not be NONE if RI = SSN
If the ri=ssn parameter is specified, then the setid=none parameter cannot be specified.
Recovery
Re-enter the chg-ppsopts command that generated this error message, specifying a valid combination of parameters. Refer to Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1168 E3367 Cmd Rej: DRA with NEC and NEC=NONE combination not allowed
If the nec=none parameter is specified, then values of asdrnnecdn, rnasdnecdn, rnnecdn, rngrnnecdn, and grnrnnecdn cannot be specified for the dra parameter.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the Commands User's Guide and the INP/AINPQ User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1169 E3368 Cmd Rej: PPT can be specified only with PC/PCA/PCI/PCN/RI/SETID/SSN
The pc/pca/pci/pcn, ri, setid, and ssn parameters must be specified before the ppt parameter can be specified.
Recovery,
Re-enter the chg-ppsopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1170 E3370 Cmd Rej: Weighted GTT Load-Sharing feature must be ON
The Weighted GTT Load-Sharing (WGTTLS) feature must be turned on before the dfltwt, eswt, grptwt, mwt, thr, or wt/wt1/wt2/wt3/wt4 parameter can be specified.
Recovery
2.2.1171 E3371 Cmd Rej: WTx must have a matching PCx specified
If the wt(X) parameter is specified, then the pc(X) parameter must be specified.
Recovery
Re-enter the ent/chg-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1172 E3372 Cmd Rej: All specified RC values must be equal
If the thr parameter is specified, then the values specified for the rc1, rc2, rc3, and rc4 parameters must be equal.
Recovery
Re-enter the ent-map or ent-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1173 E3373 Cmd Rej: WTx or DFLTWT must be specified with THR
The wt/wt1/wt2/wt3/wt4 or dfltwt parameter must be specified if the thr parameter is specified.
Recovery
Re-enter the ent-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1174 E3374 Cmd Rej: WT parameter can't be specified
The rc parameter must be specified before the wt parameter can be specified.
Recovery
Re-enter the ent/chg-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1175 E3375 Cmd Rej: ESWT and GRPWT can't be specified together
The eswt and grpwt parameters cannot be specified together in the command.
Recovery
Re-enter the chg-map or chg-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1176 E3376 Cmd Rej: THR can't be specified with ESWT=none
The eswt=none parameter and the thr parameter cannot be specified together in the command.
Note:
If the thr parameter is not specified, then a value of 1% is assigned to each weighted PC.Recovery
Re-enter the chg-map or chg-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1177 E3377 Cmd Rej: WTx and RCx can't be specified with ESWT, GRPWT and THR
If the eswt, grpwt, and thr parameters are specified, then the rc(X) and wt(X) parameters cannot be specified.
Recovery
Re-enter the chg-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1178 E3378 Cmd Rej: RCx or WTx must be specified
If the Weighted GTT Loadsharing (WGTTLS) feature is enabled and individual point codes are being modified, then the wt or rc parameter must be specified for each point code.
Recovery
2.2.1179 E3379 Cmd Rej: Only PC must be specified
Alternate point codes cannot be specified when modifying an entity set or RC group.
Recovery
Re-enter the chg-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1180 E3380 Cmd Rej: WTx required for all specified PCx values
Weighted and non-weighted PCs cannot co-exist in a single MRN group. When creating a new weighted MRN group or adding to an existing weighted MRN group, the dfltwt parameter must be specified, or an individual weight must be specified for each PC.
Recovery
Re-enter the ent-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1181 E3381 Cmd Rej: Must specify weight for new point codes for weighted groups
For the chg-map command, if the mpc parameter is specified for a weighted MAP group, then the mwt parameter must be specified.
For the chg-mrn command, if an alternate point code (pc1/pc2/pc3/pc4) is added to a weighted MRN group, then a corresponding weight (wt1/wt2/wt3/wt4) parameter must be specified for each new point code.
For the ent-mrn command, if an alternate point code pc1/pc2/pc3/pc4 is added to a weighted MRN group, then the wt1/wt2/wt3/wt4 or dfltwt parameter must also be specified.
Recovery
2.2.1182 E3382 Cmd Rej: Can’t specify weight for non-weighted groups
For the chg-map command, if the mpc parameter is specified for a non-weighted MAP group, then the mwt parameter cannot be specified.
Note:
When changing an existing point code in a non-weighted entity set only the rc parameter can be specified.For the ent/chg-mrn command, if the pc1/pc2/pc3/pc4 parameter is specified for a non-weighted MRN group, then the wt1/wt2/wt3/wt4 and dfltwt parameters cannot be specified.
Recovery
2.2.1183 E3383 Cmd Rej: Can’t specify ESWT=none for non-weighted groups
The eswt=none parameter cannot be specified for a non-weighted MAP group or MRN group.
Recovery
- Determine whether the MAP group or MRN group is weighted. Enter the
rtrv-maporrtrv-mrncommand, respectively. - Re-enter the
chg-maporchg-mrncommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1184 E3384 Cmd Rej: GRPWT/THR mustn't be specified for non-weighted groups
The grpwt and thr parameters cannot be specified for a non-weighted MAP group or MRN group.
Recovery
2.2.1185 E3385 Cmd Rej: Weight can't be specified to create SOL or DOM groups
For the ent-map command, if the values specified for the rc and materc parameters in the MAP group are equal, then the rc, materc, mpc, and mwt parameters must be specified for the new entry.
For the ent-mrn command, if all of the values specified for the rc parameter in the MRN group are unique, then the wt, wt1, wt2, wt3, wt4, and thr parameters cannot be specified.
Recovery
2.2.1186 E3386 Cmd Rej: WT and MWT must be specified with THR
If the thr parameter is specified, then the wt and mwt parameters must be specified.
Recovery
Re-enter the ent-map command that generated this error message, specifying a valid combination of paraemters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1187 E3387 Cmd Rej: WT and MWT must be specified together
The wt and mwt parameters must be specified together in the command.
Recovery
Re-enter the ent-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1188 E3388 Cmd Rej: ESWT, GRPWT and THR can't be specified with MPC
If the mpc or mssn parameter is specified, then the eswt, grpwt, and thr parameters cannot be specified.
Recovery
2.2.1189 E3389 Cmd Rej: Only PC/SSN can be specified with ESWT, GRPWT and THR params
The eswt, grpwt, and thr parameters cannot be used to modify an individual entity in an entity set or RC group. These parameters are used to modify all the entities in an entity set or RC group.
The rc, wt, mrc, srm, sso, or grp parameter must be specified to modify an individual entity in an entity set or RC group.
If the eswt, grpwt, and thr parameters are specified, then the rc, wt, mrc, srm, sso, or grp parameter cannot be specified.
Recovery
Re-enter the chg-map command that generated this error message, specifying a valid combination of parameters for the desired action. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1190 E3390 Cmd Rej: RCx must be specified
If the Weighted GTT Loadsharing (WGTTLS) feature is not enabled, and individual PCs are being modified, then the rc parameter must be specified for each PC.
Recovery
2.2.1191 E3391 Cmd Rej: DFLTWT can't be specified when WTx for each PCx is specified
If the wt, wt1, wt2, wt3, or wt4 parameter is specified, then the dfltwt parameter cannot be specified.
Recovery
Re-enter the ent-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1192 E3392 Cmd Rej: ESWT, GRPWT and THR can't be specified for SOL or DOM groups
The eswt, grpwt, and thr parameters cannot be specified if the MAP group or MRN group is in solitary or dominant mode.
Recovery
2.2.1193 E3393 Cmd Rej: MPC must be specified since MWT is specified.
If the mwt parameter is specified, then the mpc parameter must be specified.
Recovery
Re-enter the ent/chg-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1194 E3396 Cmd Rej: LNP and PPSMS Intercept Ph1 features are mutually exclusive
Recovery - Enable Only PPSMS
- Turn off the LNP ELAP Configuration feature. Refer to ELAP Administration and LNP Feature Activation Guide for assistance.
- Re-enter the
enable-ctrl-featcommand that generated this error message.
Recovery - Enable LNP and PPSMS
- Enter the
rtrv-ctrl-featcommand to verify the status of the Dual ExAP Config feature. If the Dual ExAP Config feature is not enabled, enter theenable-ctrl-featcommand to enable the feature. Enter thechg-ctrl-featcommand to turn on the Dual ExAP Config feature. - Re-enter the
enable-ctrl-featcommand that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1195 E3397 Cmd Rej: ANAME is invalid for type-enttype combo
The enttype=sctpasoc or enttype=ua parameter must be specified before the aname parameter can be specified.
Recovery
Re-enter the rept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1196 E3398 Cmd Rej: ASNAME is invalid for type-enttype combo
The enttype=ua parameter must be specified before the asname parameter can be specified.
Recovery
Re-enter the rept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1197 E3399 Cmd Rej: Association is not assigned to AS
The association specified by the aname parameter must be assigned to the application server specified by the asname parameter.
Recovery
2.2.1198 E3400 Cmd Rej: NPSN not configured under GTTSET
Recovery
- Display the existing GTT sets; enter the
rtrv-gttsetcommand. -
Re-enter the command that generated this error message, specifying a valid combination of parameters.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1199 E3401 Cmd Rej: NPSN SETTYPE should be different from GTT SETTYPE
Recovery
- Display the existing GTT sets; enter the
rtrv-gttsetcommand. -
Re-enter the command that generated this error message, specifying a valid combination of parameters.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1200 E3402 Cmd Rej: GTTSN and NPSN must not form Circular Entries
Recovery
- Display the existing GTT sets; enter the
rtrv-gttsetcommand. -
Re-enter the
chg-gttsetcommand that generated this error message, specifying a valid combination of parameters.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1201 E3403 Cmd Rej: Association name must be specified
If the enttype=sctpasoc or enttype=ua parameter is specified, then the aname parameter must be specified.
- Re-enter the
rept-meascommand that generated this message, specifying a valid combination of parameters. Refer to Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1202 E3404 Cmd Rej: VCI values 0..4 and 6..31 are reserved
The values 0 - 4 and 6 - 31 cannot be specified for the vci parameter. These values are reserved system values.
Recovery
Re-enter the ent-slk command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.1203 E3406 Cmd Rej: BPS must be 1544000 for LIMATM cards
If the specified card is a LIMATM card, then a value of 1544000 must be specified for the bps parameter.
Recovery
2.2.1204 E3407 Cmd Rej: LSL parameters not valid for card type
The parameter values specified for the signaling link are not supported for the links on the card specified by the loc parameter. Refer to the command description for the ent-slk command in the Commands User's Guide for valid parameters for each type of link.
Recovery
2.2.1205 E3408 Cmd Rej: ATM parameters not valid for card type
The parameter values specified for the signaling link are not supported for the links on the card specified by the loc parameter. Refer to the command description for the ent-slk command in the Commands User's Guide for valid parameters for each type of link.
Recovery
2.2.1206 E3409 Cmd Rej: Max number combined LSLs and HSLs already entered
A maximum of 1200, 1500, 2000, or 2800 links is allowed in the system. The maximum depends on the enabled Large System # Links quantity (see the rtrv-ctrl-feat command output). A FAK is required to enable support for more than 1200 links. A mixture of high-speed, E1 high-speed, SE-HSL, IP, and low-speed signaling links is supported.
Recovery
2.2.1207 E3410 Cmd Rej: Failed reading the ATM link parameter set table
The ATM Parameter Set table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1208 E3411 Cmd Rej: Specified LPSET contains default values and not configurable
LPSETs 20 and 30 contain system default parameters which can be copied but not changed.
Recovery
Re-enter the chg-atm-lps command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.1209 E3412 Cmd Rej: SRCLPSET and LPSET cannot be equal
The srclpset and lpset parameters must have different values.
Recovery
Re-enter the chg-atm-lps command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistasnce.
2.2.1210 E3413 Cmd Rej: ACTION and SRCLPSET must be specified together
The action and srclpset parameters must be specified together in the command.
Recovery
Re-enter the chg-atm-lps command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.1211 E3414 Cmd Rej: Invalid parameters for ACTION=COPY
If the action=copy parameter is specified, then only the lpset and scrlpset parameters can be specified.
Recovery
Re-enter the chg-atm-lps command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.1212 E3415 Cmd Rej: LOC and CLASS cannot be specified together
The loc and class parameters cannot be specified together in the same command.
Recovery
Re-enter the rtrv-slk command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1213 E3416 Cmd Rej: NI is invalid for type-enttype combo
The type=gtwy parameter must be specified, and a value of lsdestni, lsonismt, lsorigni, origni, or origninc must be specified for the enttype parameter before the ni parameter can be specified.
Recovery
Re-enter the rept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Measurements Reference for assistance.
2.2.1214 E3417 Cmd Rej: NC is invalid for type-enttype combo
The type=gtwy and enttype=origninc parameters must be specified before the nc parameter can be specified.
Recovery
Re-enter therept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Measurements Reference for assistance.
2.2.1215 E3418 Cmd Rej: Specified BPS is invalid
The card application must be ATMANSI before the bps=1544000 parameter can be specified. The card application must be ATMITU before the bps=2048000 parameter can be specified.
Recovery
2.2.1216 E3419 Cmd Rej: Day is invalid for type-enttype combination
For the rept-ftp-meas command, the day parameter can be specified with the type=mtcd and enttype=aiq, eir, lnp, np, mapscrn, gttapath , or vflex parameters.
For the rept-meas command, the day parameter can be specified with the type=mtcd and enttype=lnp or mapscrn parameters.
Recovery
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.
2.2.1217 E3420 Cmd Rej: 'Default' is an invalid ASNAME
The asname=default parameter cannot be specified.
Recovery
Re-enter the ent-as command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1218 E3421 Cmd Rej: DSTN5000 feature must be ON
For the enable-ctrl-feat command, the 5000 Routes feature must be turned on before the 6000, 7000 or 8000 Routesets feature can be turned on and before the 10,000 Routesets feature can be enabled.
Fro the chg-stpopts command, the 5000 Routes feature must be turned on before the mtpdpcq parameter value can be increased to more than 2000.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1219 E3422 Cmd Rej: Echo capability not applicable on originating terminal
The value specified for the trm parameter cannot indicate the terminal from which the command is issued.
Recovery
Re-enter the act/canc-echo command, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1220 E3423 Cmd Rej: DAY must be specified when PERIOD=SPECIFIC
If the period=specific parameter is specified, then the day parameter must be specified.
Recovery
Re-enter the rept-ftp-meas or rept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Measurements Reference for assistance.
2.2.1221 E3425 Cmd Rej: Invalid parameter for SS7ANSI, ATMANSI, IPLIM, or SS7IPGW
A valid parameter combination must be entered for the card type and GPL. Refer to the command description for the ent-trace command in the Commands User's Guide for a discussion of the valid parameters.
Recovery
2.2.1222 E3426 Cmd Rej: ANSI PC parameters are invalid for ITU cards
A valid parameter combination must be entered for the card type and GPL. Refer to the command description for the ent-trace command in the Commands User's Guide for a discussion of the valid parameters.
Recovery
2.2.1223 E3427 Cmd Rej: ITU PC parameters are invalid for ANSI cards
A valid parameter combination must be entered for the card type and GPL. Refer to the command description for the ent-trace command in the Commands User's Guide for a discussion of the valid parameters.
Recovery
2.2.1224 E3428 Cmd Rej: Invalid parameter for CCS7ITU or IPLIMI
A valid parameter combination must be entered for the card type and GPL. Refer to the command description for the ent-trace command in the Commands User's Guide for a discussion of the valid parameters.
Recovery
2.2.1225 E3429 Cmd Rej: Invalid parameter for VSCCP
A valid parameter combination must be entered for the card type and GPL. Refer to the command description for the ent-trace command in the Commands User's Guide for a discussion of the valid parameters.
Recovery
2.2.1226 E3430 Cmd Rej: At least one SFTHROT GTT action must be configured
chg-measopts command, at least one SFTHROT GTT action must be provisioned before the systotsfthrot=on parameter can be specified.
For the chg-mtc-measopts command, at least one SFTHROT GTT action must be provisioned before the mtcdsfthrot=on parameter can be specified.
For the rept-ftp-meas command, at least one SFTHROT GTT action must be provisioned before the enttype=sfthrot parameter can be specified.
Recovery
- Provision at least one SFTHROT GTT action entry.
- Re-enter the command that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1227 E3431 Cmd Rej: SCCPCNV must be ON before TCAPCNV can be ON
The SCCPCNV feature must be turned on before the TCAPCNV feature can be turned on.
Note:
Once a feature that is controlled by a feature bit is turned on, it cannot be turned off.Recovery
2.2.1228 E3432 Cmd Rej: Code parameter not supported for OAM locations
If an OAM card is installed in the location specified by the loc parameter, then only a value of inactiveprtn can be specified for the code parameter.
Recovery
2.2.1229 E3433 Cmd Rej: DPC parameter must be specified
If the dev=route parameter is specified, then the dpc/dpca/dpci/dpcn/dpcn24 parameter must be specified.
Recovery
Re-enter the inh/unhb-alm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1230 E3434 Cmd Rej: The alarms are already inhibited for this device
Alarms are already inhibited for the specified device.
Recovery
2.2.1231 E3435 Cmd Rej: To disable CRITALMINH, critical alarms cannot be inhibited
If critical alarms are inhibited in the system, then the critalminh=no parameter cannot be specified.
Recovery
2.2.1232 E3436 Cmd Rej: CRITALMINH not set when trying to inhibit critical alarms
The CRITALMINH STP option must be provisioned before critical alarms can be inhibited.
Recovery
2.2.1233 E3437 Cmd Rej: Device alarm inhibit table not accessible
The Device Alarm Inhibit table is not accessible and may be corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1234 E3438 Cmd Rej: Lvl 1 Removable detected during upgrade
The removable drive required for the upgrade has upgrade phase indicators. The upgrade command expects the disks to be in certain phases before executing a specific action. This message occurs if the removable drive is swapped out during the upgrade so that the disk is no longer in the expected phase.
Recovery
If the removable drive was swapped out, re-insert the removable drive being used for the upgrade.
OR
- Determine the status of the removable drive. Enter the
act-upgrade:action=dbstatuscommand. - Follow the recovery procedure in the upgrade procedure documentation, or contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1235 E3439 Cmd Rej: Standby TDM in unknown upgrade mode
The TDMs have upgrade phase indicators. The upgrade command expects the disks to be in certain phases before executing a specific action. This message appeared because the standby TDM is not in the correct phase.
Recovery
- Display the current database status. Enter the
act-upgrade:action=dbstatuscommand. - Follow the recovery procedure in the upgrade procedure documentation, or contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1236 E3440 Cmd Rej: Active TDM in unknown upgrade mode
The TDMs have upgrade phase indicators. The upgrade command expects the disks to be in certain phases before executing a specific action. This message appeared because the active TDM is not in the correct phase.
Recovery
- Display the current database status. Enter the
act-upgrade:action=dbstatuscommand. - Follow the recovery procedure in the upgrade procedure documentation, or contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1237 E3441 Cmd Rej: Target Release source disk in unknown upgrade mode
The disk that contains the upgrade target release is in an unknown upgrade mode.
The upgrade command expects the disk to be in certain phases before executing a specific action.
Recovery
- Display the current database status. Enter the
act-upgrade:action=dbstatuscommand. - Follow the recovery procedure in the upgrade procedure documentation, or contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1238 E3442 Cmd Rej: Removable is from previously aborted upgrade
The act-upgrade command specifying the convertstp action runs from upgrade phase 0 to upgrade phase 3 unless an anomaly occurs that causes the command to terminate.
Recovery
Follow the recovery procedure in the upgrade procedure documentation, or contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1239 E3443 Cmd Rej: THRES parm and action=CONVERTSTP must be specified together
The action=convertstp parameter and the thres parameter must be spcified together in the command.
Caution:
It is strongly recommended that this command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.Recovery
Re-enter the act-upgrade command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1240 E3444 Cmd Rej: Upgrade prevented due to auto-inhibited card
act-upgrade command can be entered.
Caution:
It is strongly recommended that this command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.Recovery
2.2.1241 E3446 Cmd Rej: SLK not provisioned for assigned Lhost
A signaling link must be assigned to the associated signaling link port on the local host before the open=yes parameter can be specified.
Recovery
2.2.1242 E3447 Cmd Rej: IPLIMx and IPSG connections cannot be resident in AS
The value specified for the aname parameter cannot refer to an IPLIMx or IPSG association.
Recovery
2.2.1243 E3448 Cmd Rej: LHOST has open socket or association
For the chg-ip-lnk command, a local IP address cannot be changed if the current or new local host has open sockets or associations (the open parameter set to yes with the ent/chg-assoc command).
For the dlt-slk command, an IPLIMx or IPGWx signaling link assigned to a local host cannot be deleted if the link has open sockets or associations.
Note:
Open sockets or associations are provisioned with the open=yes parameter in thechg-assoc command.
For the ent-dconn command, any OPEN association cannot be assigned to a new diameter connection (the open parameter set to yes/no with the chg-assoc command).
Recovery
- Display the host name for the local host. Enter the
rtrv-ip-hostcommand. - Display connection status for the associations. Enter the
rtrv-assoccommand for the local host name. - Change the connection status of each open association as desired. Refer to Database Administration - IP7 User's Guide for assistance.
- Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - ent-dconn
2.2.1244 E3449 Cmd Rej: SADDR must be specified for MBR GTT settypes
Recovery
- Display the existing GTT sets if needed; enter the
rtrv-gttsetcommand. - Re-enter the command that generated this error message, specifying a valid combination of parameters.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1245 E3450 Cmd Rej: Invalid Part Number
The value specified for the partnum parameter must be the correct part number for the purchased feature.
Recovery
Re-enter the enable/chg-ctrl-feat command that generated this error message, specifying the correct part number for the feature.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1246 E3451 Cmd Rej: Controlled Feature is not enabled
For the chg-ctrl-feat command, the controlled feature specified by the partnum parameter must be enabled before this command can be entered.
For the chg-sccpopts command, either the Dual ExAP Config or EPAP Data Split feature must be enabled before the GTTDIST=GTT parameter can be specified.
For the chg-trm command, the IP User Interface (Telnet) feature must be enabled and turned on before the type=telnet parameter (IDs 17-40) or the type=emsalm parameter (IDs 1-40) can be specified.
For the chg-mtc-measopts command, the GTT Action - DISCARD, GTT Action - FORWARD, or GTT Action - DUPLICATE feature must be enabled before the mtchgttapath=on or mtcdgttapath=on parameter can be specified.
For the ent-gttact command, the GTT Action - DISCARD, GTT Action - FORWARD, or GTT Action - DUPLICATE feature must be enabled before the act=srvc parameter can be specified.
For the rept-ftp-meas command, the GTT Action - DISCARD, GTT Action - FORWARD, or GTT Action - DUPLICATE feature must be enabled before the enttype=gttapath parameter can be specified.
The GTT Action - DISCARD, GTT Action - FORWARD, or GTT Action - DUPLICATE feature must be enabled before the ent/chg/dlt-gttapath command can be entered.
For the rtrv-gttact command, the GTT Action - DISCARD, GTT Action - FORWARD, or GTT Action - DUPLICATE feature must be enabled before the pc, ri, ssn, tt, cgpc, cgpcogmsg, or useicmsg parameters can be specified.
Recovery
2.2.1247 E3453 Cmd Rej: Database does not contain a serial number
A valid system serial number must be entered and locked in the database before this command can be entered for the feature.
Recovery
2.2.1248 E3454 Cmd Rej: Routesets Feature Quantity must be increased
The number of routes being set beyond 5000 is more than the Feature Quantity Key will allow. Before the value of the mtpdpcq or the mtpxlq parameters can be changed, the correct Routesets Feature must be turned on.
Note:
The values of the mtpdpcq and mtpxlq parameters are interdependent. To increase the number of DPCs that can be provisioned, the number of x-list entries that the STP is to maintain must be decreased. To increase the number of x-list entries that the STP maintains, the number of DPCs that can be provisioned must be decreased.Recovery
2.2.1249 E3455 Cmd Rej: SCTP Association or SLK provisioned: Card supports 16 links
All available links on the specified IPLIM card have already been provisioned.
Recovery
2.2.1250 E3456 Cmd Rej: LNP ELAP Configuration feature must be ON
The LNP ELAP Configuration feature must be turned on before the following features can be enabled:
-
24 Million LNP ported TNs or greater
- 300,000 LNP ported NPANXXs
- 150,000 LNP ported LRNs
Recovery
2.2.1251 E3457 Cmd Rej: Perm feature key cannot be turned off for the feature
After a Permanently On feature is turned on, it cannot be turned off with the chg-ctrl-feat command.
Refer to the Database Administration - System Management User's Guide and to the command description in Commands User's Guide for details about turning on and off controlled features with feature access keys. The command description also contains a list of Permanently On features.
Recovery
2.2.1252 E3458 Cmd Rej: DEFMAPVR/SXUDT can be specified with OPCODE SETTYPES only
ent/chg/rtrv-gta command only when the
specified GTT set has a set type of opcode (see the
ent-gttset command).
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1253 E3459 Cmd Rej: GTTSET MBR Settypes Support ITU BGN/CNT/END Pkgtype
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1254 E3460 Cmd Rej: DEFMAPVR is supported by MBR GTT settypes
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1255 E3461 Cmd Rej: EADDR cannot be specified without SADDR
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1256 E3462 Cmd Rej: LNP ported TNs 24million Qty Feat Require at least DSM2GB
All DSM cards must have at least 2 GB of memory before the LNP Ported TNs 24 Million feature can be enabled.
Recovery
- Upgrade the hardware with sufficient (at least 2 GB) memory. Refer to the Maintenance Guide and contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
- Re-enter the
enable-ctrl-featcommand that generated this error message.
2.2.1257 E3463 Cmd Rej: LNP ported TNs 36million Qty Feat Require at least DSM3GB
All DSM cards must have at least 3 GB of memory before the LNP Ported TNs 36 Million feature can be enabled.
Recovery
- Upgrade the hardware with sufficient (at least 3 GB) memory. Refer to Maintenance Guide and contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
- Re-enter the
enable-ctrl-featcommand that generated this error message.
2.2.1258 E3464 Cmd Rej: LNP ported TNs 48 to 192 M Qty Feat Req at least DSM4GB
All DSM cards must have at least 4 GB of memory before the LNP Ported TNs 48 - 192 Million feature can be enabled.
Recovery
- Upgrade the hardware as necessary. Refer to Maintenance Guide and contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
- Re-enter the
enable-ctrl-featcommand that generated this error message.
2.2.1259 E3465 Cmd Rej: USEICMSG only valid for FWD/DUP/SCPVAL
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1260 E3466 Cmd Rej: SSO parameter is not compatible with True PC
The value specified for the sso parameter cannot be the same as the system true point code.
Recovery
2.2.1261 E3468 Cmd Rej: FTP Transfer already in progress
An act-ftp-trns command cannot be entered if another file transfer is already in progress.
Recovery
The act-ftp-trns command is for Oracle use only. Contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1262 E3469 Cmd Rej: M2PATSET requires M2PA adapter type
If the m2patset parameter is specified, then the adapter=m2pa parameter must be specified.
Recovery
Re-enter the ent/chg-assoc command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1263 E3470 Cmd Rej: SRCTSET and TSET cannot be equal
The same value cannot be specified for the srctset and tset parameters.
Recovery
Re-enter the chg-m2pa-tset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1264 E3471 Cmd Rej: Application server name must be specified
If the enttype=ua parameter is specified, then the asname parameter must be specified.
Recovery
Re-enter the rept-meas command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Measurements Reference for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1265 E3472 Cmd Rej: Timer value and SRCTSET cannot be specified together
A timer value and the SRCTSET parameter should not be specified together.
Recovery
Re-enter the chg-m2pa-tset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1266 E3473 Cmd Rej: The last active serial port cannot be inhibited
One serial port must remain active and available for login and must be of the terminal type capable of entering commands.
Recovery
2.2.1267 E3474 Cmd Rej: Prepaid SMS Intercept Ph1 feature must be enabled
The Prepaid SMS Intercept Ph1 feature must be enabled before an Action Set containing the PPRELAY Service Action can be specified as a value for the asn parameter with the MOSMSGCDPN or MOSMSGCGPN service.
Recovery
2.2.1268 E3475 Cmd Rej: Failure reading HOME SMSC Address entries
The Home SMSC Address table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1269 E3476 Cmd Rej: HOME SMSC Address to be deleted does not exist in database
The value specified for the smsc parameter must already exist in the HOME SMSCADDR table.
Recovery
- Display the existing values for the smsc parameter. Enter the
rtrv-home-smsccommand. - Re-enter the
dlt-home-smsccommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1270 E3477 Cmd Rej: HOME SMSC Address already exists
The specified HOME SMSC address cannot already exist in the HOME SMSCADDR table.
Recovery
2.2.1271 E3478 Cmd Rej: Home SMSC Table is Full
The HOME SMSCADDR table can contain a maximum of 500 entries.
Recovery
2.2.1272 E3479 Cmd Rej: Port Check for MO SMS feature must be enabled
The Portability Check for MO SMS feature must be enabled before an Action Set containing the FRAUDCHK Service Action can be specified as a value for the asn parameter with the MOSMSGCGPN service.
Recovery
2.2.1273 E3480 Cmd Rej: PPT must be specified with PC/PCA/PCI/PCN/RI/SETID/SSN
If the pc, pca, pci, pcn, ri, setid, or ssn parameter is specified, then the ppt parameter must be specified.
Recovery
Re-enter the chg-ppsopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1274 E3481 Cmd Rej: S/ESLOT cannot be set to 9 or 10
The HIPR or HIPR2 MUX card slots (09 and 10) cannot be specified as values for the sslot and eslot parameters.
Recovery
Re-enter the rept-imt-info command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1275 E3482 Cmd Rej: Link capacity exceeds limit allowed by HSL feature key
The link capacity provisioned by the ent-slk command cannot exceed the maximum allowed by the SE-HSL or ST-HSL-A quantity.
Recovery
2.2.1276 E3490 Cmd Rej: HIPR must be equipped on the shelf for this card
For the ent/chg-e1 commands, HIPR2 cards must be equipped in card locations xy09 and xy10 on each shelf that contains one or more HC-MIM or E5-E1T1 cards that are used as E1 or SE-HSL cards.
For the ent-slk command, HIPR2 cards must be in card locations xy09 and xy10 on each shelf that contains one or more HC-MIM, E5-E1T1, E5-E1T1-B, E5-ENET, E5-ENET-B, or SLIC cards when link parameter values a4-a63 and b4-b63 are specified.
For the ent/chg-t1 commands, HIPR2 cards must be equipped in card locations xy09 and xy10 on each shelf that contains one or more HC-MIM or E5-E1T1 cards that are used as T1 cards or ST-HSL-A cards.
Recovery
2.2.1277 E3493 Cmd Rej: MULTCC entry already exists in the GSM Options MULTCC list
The value specified for the defcc parameter (chg-stpopts command) or multcc parameter (chg-gsmopts command) cannot already exist in the GSM Options MULTCC List.
Recovery
- Display the existing values for the defcc or multcc parameter. Enter the
rtrv-stpoptscommand or thertrv-gsmoptscommand, respectively. - 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1278 E3494 Cmd Rej: Link is invalid for card location
An invalid link was entered for the card. Refer to the command description and to Appendix A in the Commands User's Guide for valid links for each card type.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1279 E3496 Cmd Rej: Card location specified must be an SCCP/SFAPP or SFLOG card
Recovery
- Enter the
rtrv-cardcommand to display the cards in the system. - Re-enter the command that generated this error message, specifying a valid location.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1280 E3497 Cmd Rej: Either ALIASN or ALIASN24, not both, for destination
For ANSI or ITU-I destinations, the aliasn and aliasn24 parameters cannot be specified together in the command.
Recovery
Re-enter the ent/chg-dstn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1281 E3498 Cmd Rej: SPRM & TPRM combination must be unique in a GTTAct Set
Recovery
- Enter the
rtrv-gttasetcommand to display the entries from the GTT action set table. - Re-enter the command that generated this error message, specifying a valid combination of parameters.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1282 E3499 Cmd Rej: Security parameter must be ON
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1283 E3500 Cmd Rej: GFLEX feature must be ON
For the chg-gsmopts command, the G-Flex feature must be turned on before the defmnc, ccnc, or mccmnc parameter can be specified.
For the chg-sid command, the G-Flex feature must be turned on when the cpctype=gflex parameter is specified.
For the chg-stpopts command, the G-Flex feature must be turned on before the ansigflex parameter can be specified.
For the enable-ctrl-feat command, the G-Flex feature must be turned on before the G-Flex MAP Layer Routing feature can be enabled.
For the ent/chg/rtrv-srvsel command, the G-Flex feature must be turned on before the nserv/serv=gflex parameter can be specified.
For the ent/chg-gttact command, the G-Flex feature must be turned on before the GFLEX service is entered with the SRVCNAME parameter.
Recovery
2.2.1284 E3501 Cmd Rej: CCNC does not exist
The value specified for the ccnc parameter must already exist in the database if the mccmnc=none parameter is specified.
Recovery
Re-enter the chg-gsmopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to G-Port User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1285 E3502 Cmd Rej: The NONE value is not allowed in this case
For the ent-trace command, a value of none cannot be specified for the dn, entityid, gt, imei, or imsi parameter.
For the ent/dlt-homern command, the rn=none parameter cannot be specified.
For the ent-vflx-vmsid command, a value of none cannot be specified for the idx0-idx9 parameters.
Recovery
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. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1286 E3503 Cmd Rej: Card Configuration is inconsistent with Card Set List
Recovery
- Enter the
act-upgrade:action=createsetscommand to create a new current list of card sets. - Re-enter the command that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1287 E3504 Cmd Rej: GSM Selector does not exist
The requested SRV Selector entry must exist in the database.
Recovery
- Use the
ent-srvselcommand to configure a valid SRV Selector. - Re-enter the
chg/dlt-srvselcommand to modify the srvsel entry.
Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1288 E3505 Cmd Rej: Prepaid SMS, A-Party RTG or SK RTG feature must be ON
The Prepaid Short Message Service (PPSMS) Intercept Phase 1, IDP A-Party Routing, or IDP Service Key Routing feature must be enabled and turned on before the chg/rtrv-ppsopts command can be entered.
For the ent/chg/rtrv-srvsel command, the PPSMS feature must be turned on before the (n)serv=smsmr parameter can be specified.
For the rtrv-ppsopts command, the PPSMS feature must be turned on before the ppt parameter can be specified.
Recovery
2.2.1289 E3506 Cmd Rej: ISUP Message Type must be valid
The ISUP Message Type (ISUPMT parameter) must be specified for SEAS command.
Recovery
- Re-enter the
chg/dlt-scr-isupcommand with the ISUPMT parameter.
Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1290 E3507 Cmd Rej: EAGLEGEN,TT,NP(V),NAI(V) parameters mustn't be specified
If the gti(x)=0 parameter is specified, then the eaglegen, tt, np/npv, and nai/naiv parameters cannot be specified.
Recovery
Re-enter the ent/chg/dlt/rtrv-gttsel command that generated this error message specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1291 E3508 Cmd Rej: MBR settypes cannot be referenced by GTT selectors
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1292 E3509 Cmd Rej: LNPSUBDIGLEN should be less than LNPNATLDIGLEN
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1293 E3510 Cmd Rej: EPMA/SM4G card not supported for this feature
The EPMA/SM4G cards are not supported when the E5-SMxG Throughput Capacity feature at 13.6 TPS (893-0191-04) is enabled.
- Replace EPMA/SM4G cards with E5-SM8G-B cards.
- Re-enter the
enable-ctrl-featcommand that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1294 E3511 Cmd Rej: CCNC and MCCMNC parameters must be entered together
The ccnc and mccmnc parameters must be specified together in the command.
Recovery
Re-enter the chg-gsmopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the G-Port User's Guide for assistance.
2.2.1295 E3512 Cmd Rej: All provisioned shelves must have HIPR cards
HIPR cards must be installed on all provisioned shelves in the system before the system can contain more than 115 ATM cards.
Recovery
2.2.1296 E3513 Cmd Rej: Invalid parameter combination with PERDATA param
For the init-card command, the perdata parameter can be specified only when the loc or appl parameter is specified along with the data=persist parameter. In addition, the type parameter cannot be specified with the perdata parameter.
Note:
The card at the location specified by the loc parameter must run either the IPSG32 GPL or the VSCCP application, and the application specified by the appl parameter must be either IPSG or VSCCP.For the init-sys command, the perdata parameter can be specified only when the data parameter is specified.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1297 E3514 Cmd Rej: Maximum of 10 unique CCNCs allowed
A maxiumum of 10 sets of ccnc/mccmnc parameter combinations are allowed.
Recovery
2.2.1298 E3515 Cmd Rej: CCNC already exists
The value specified for the ccnc parameter cannot already exist unless the mccmnc=none parameter is also specified.
Recovery
Re-enter the chg-gsmopts command that generated this error message.
2.2.1299 E3516 Cmd Rej: APPL must be IPSG/VSCCP with DATA parameter
When the data parameter is specified, the application specified by the appl parameter must be IPSG or VSCCP.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1300 E3517 Cmd Rej: VSCCP cards have insufficient extended memory
Each provisioned DSM/VSCCP card must have at least 4 GB of memory before the AINPQ feature can be enabled.
Recovery
2.2.1301 E3520 Cmd Rej: Invalid TYPE and APPL combination
When the appl=ipsg parameter is specified, the value specified for the type parameter can be only nosccp or gtt. When the appl=vsccp parameter is specified, the value specified for the type parameter can be only dn, imsi, epap, elap, or gtt.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1302 E3521 Cmd Rej: HS can only be specified with BUS
The hs parameter can be specified only when the bus parameter is specified.
The hs parameter should be specified only as a tool to facilitate updating spare cards for releases that only support MUX bus speeds of 2.5 Gbps.
Recovery
Re-enter the init-mux 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1303 E3522 Cmd Rej: CHECKMULCOMP/PRIO can be specified with OPCODE SETTYPES only
For the chg/ent-gta command, the prio parameter can be specified with OPCODE GTT set types only.
For the chg/ent-gttset command, the checkmulcomp parameter can be specified with OPCODE GTT set types only.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1304 E3523 Cmd Rej: At least one parameter must be changed
For the chg-srvsel command, the nsnp, nsnai,ndfltact, ngttselid, on, off, or nserv parameter must be specified.
For the chg-npp-srs command, the asn or invkserv parameter must be specified.
Recovery
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.
2.2.1305 E3524 Cmd Rej: INP/AINPQ feature(s) must be ON
The INP or AINPQ feature must be turned on before the chg/rtrv-inpopts or ent/dlt/rtrv-homern commands can be specified.
For the ent/rtrv-sid commands, the INP feature must be turned on tefore the cpctype=inp parameter can be specified.
For the ent/cg/rtrv-srvsel commands, the INP or AINPQ feature must be turned on before a value of inpmr or inpq can be specified for the serv parameter.
For the ent/chg/dlt-ss-appl commands, the INP feature must be turned on before the appl=inp parameter can be specified.
Recovery
2.2.1306 E3525 Cmd Rej: Command will cause system clock outage – Use FORCE=YES
If E5-MASP reload would cause a system clock outage, the initclk parameter cannot be specified unless force=yes is also specified.
Note:
Creating a system clock outage will probably result in the loss of traffic on all links.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 and to Database Administration - System Management User's Guide for assistance.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1307 E3527 Cmd Rej: NMULTCC entry already exists in the GSM Options MULTCC list
The value specified for the nmultcc parameter cannot already exist in the GSM Options MULTCC List.
Recovery
- Display the multcc parameter values currently in the MULTCC list. Enter the
rtrv-gsmoptscommand. - Re-enter the
chg-gsmoptscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the G-Port User's Guide for assistance.
2.2.1308 E3528 Cmd Rej: Only one UDP can provision per lhost
Only one UDP connection can be provisioned per interface (lhost).
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1309 E3529 Cmd Rej: Application type not in SS-APPL table
The value specified for the appl parameter must already exist in the SS-APPL table.
Recovery
- Display the values for the SS-APPL table.Enter the
rtrv-ss-applcommand. - Re-enter the
dlt-ss-applcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the appropriate feature manual for assistance.
2.2.1310 E3530 Cmd Rej: Dual ExAP or EPAP Data Split must be ON or GTT-LIM present
The DATA=GTT parameter is allowed only when the Dual ExAP Config feature is ON, the EPAP Data Split feature is ON, or a GTT-capable LIM is present in the system.
Recovery
- Issue the command without the DATA=GTT parameter, install a GTT-capable LIM, or enter the
rtrv-ctrl-featcommand to determine the status of the Dual ExAP Config feature or the EPAP Data Split feature in the system.Enter the
enable-ctrl-featcommand to enable the appropriate feature as needed, and thechg-ctrl-featcommand to turn on the appropriate feature. - Re-enter the
rept-stat-sccpcommand that generated this 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1311 E3532 Cmd Rej: Exceeding max number of SS7 links for GTT-enabled IPSG card
The card has exceeded the maximum of 32 links configured on a GTT-enabled IPSG card.
Recovery
If trying to change an NOSCCP IPSG card with more than 32 equippped links to a GTT-enabled IPSG card:
- Remove SLKs until the number of SLKs on the NOSCCP IPSG card is less than or equal to 32.
- Retry changing the card from NOSCCP to GTT-enabled IPSG card.
2.2.1312 E3533 Cmd Rej: Serv Selector table is full
The Service Selector table contains the maximum number of entries.
Recovery
2.2.1313 E3534 Cmd Rej: E1 Port test command in progress
A port test is in progress on the specified E1 port. Only one port test can be performed at a time.
Recovery
Re-enter the tst-e1 command that generated this error message after all tests are complete.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1314 E3535 Cmd Rej: E1 Port test command not in progress
There is no active test in progress on the specified E1 port. The action=stop parameter cannot be performed if there is no active port test.
Recovery
No action.
2.2.1315 E3536 Cmd Rej: 32-BIT APPL NOT SUPPORTED
Recovery:
- Inhibit or delete any SMxG and SLIC cards running 32-bit GPLs.
- Convert any cards to 64-bit GPLs.
2.2.1316 E3537 Cmd Rej: Card's A/B and C/D interfaces must be unique
Each IP address entered into the IP Link table must be unique (a card cannot have two interfaces on the same network).
Recovery
2.2.1317 E3538 Cmd Rej: Linkset SLK requires ITUN APC/SAPC to be 14bit or 24bit only
For the chg-ls command:
- A linkset cannot have both a 14-bit ITU-N and a 24-bit ITU-N APC/SAPC unless it contains only IPGWI links or IPLIM M3UA links. These links support 14-bit ITU-N and 24-bit ITU-N traffic simultaneously.
- A linkset with the ipgwapc=no parameter cannot have both a 14-bit ITU-N and a 24-bit ITU-NAPC/SAPC if no links are provisioned. The SAPC cannot be a 24-bit ITU-N point code if the linkset contains IPLIM or E1 ATM links, which do not support 24-bit ITU-N traffic.
For the ent-slk command:
-
Linksets with 14-bit ITU-N and 24-bit ITU-N APCs or SAPCs can contain only IPGWI or IPLIMI M3UA links. These links support 14-bit ITU-N and 24-bit ITU-N traffic simultaneously.
-
Linksets containing 24-bit ITU-N APCs or SAPCs cannot contain E1 ATM links. These links do not support 24-bit ITU-N traffic.
Recovery
2.2.1318 E3539 Cmd Rej: SIP NP Feature Must Be Activated
The SIP NP Feature must be activated before provisioning a card with the data=elap parameter.
Recovery
- Enable the SIP Number Portability feature by entering the
enable-ctrl-feat:partnum=893040601command. - Turn on the SIP NP feature using the
chg-ctrl-feat:partnum=893040601:status=oncommand.
2.2.1319 E3540 Cmd Rej: DATA parm can be entered for IPSG appl running on SLIC card only
The data parameter can only be specified for the IPSG application running on the SLIC card.
Recovery
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1320 E3541 Cmd Rej: Failed reading GSM Options Table
The GSM Options table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1321 E3542 Cmd Rej: Failed reading GSM SSN Table
The GSM SSN table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1322 E3543 Cmd Rej: Failed reading GTT Selector Table
The GTT Selector table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1323 E3544 Cmd Rej: Failed reading GTT Set Table
The GTT Set table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1324 E3545 Cmd Rej: Failed reading SERV Selector Table
The Service Selector table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1325 E3546 Cmd Rej: Failed reading GSM DBMM Table
The GMS DBMM table is corrupt or cannot be found.
Recovery
Re-enter the command that generated this error message.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1326 E3547 Cmd Rej: SFAPP not Configured
This error occurs when no SFAPP cards are provisioned in
the EAGLE while running the
rept-stat-sfapp command.
Recovery
2.2.1327 E3548 Cmd Rej: Card location specified must be an SFAPP card
This error occurs when the
rept-stat-sfapp command is being executed for an
invalid card type in EAGLE.
Recovery
2.2.1328 E3549 Cmd Rej: Offline state is not allowed for sfapp
The status of the SFAPP subsystem cannot be offline.
Recovery
2.2.1329 E3550 Cmd Rej: GTT must be ON before EGTT can be ON
The Global Title Translation (GTT) feature must be turned on before the Enhanced Global Title Translation (EGTT) feature can be turned on.
Note:
Once a feature controlled using a feature bit is turned on, it cannot be turned off.Recovery
2.2.1330 E3551 Cmd Rej: NP and NPV must not be specified together
The np/npv parameters, cdnp/cdnpv, and cgnp/cgnpv parameters cannot be specified together in the command.
Recovery
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.
2.2.1331 E3552 Cmd Rej: NAI and NAIV must not be specified together
The nai/naiv parameters, cdnai/cdnaiv parameters, and cgnai/cgnaiv parameters cannot be specified together in the command.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command descriptionin the Commands User's Guide for assistance.
2.2.1332 E3553 Cmd Rej: GTI (A)=4, and GTI (X)=1 and 3 are not supported
For the ent/chg/dlt/rtrv-gttsel and ent/chg/dlt/rtrv-srvsel commands: The gtia=4, gti(x)=1, and gti(x)=3 parameters cannot be specified.
For the tst-msg command: For an ANSI message, the CDPA GTI must be 2 and the CGPA GTI must be 0 or 2 (see the chg-sccp-msg command). For an ITU message, the CDPA GTI must be 2 or 4 and the CGPA GTI must be 0, 2, or 4.
For the chg-sccp-msg command: The values 1 and 3 cannot be specified for the cdgti and cggti parameters.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1333 E3554 Cmd Rej: NP(V) and NAI(V) must not be specified for given GTI value
If the gti(x)=2 parameter is specified, then the nai/naiv or npv/naiv parameters cannot be specified.
Recovery
Re-enter the command that generated the error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.1334 E3555 Cmd Rej: NP(V) and NAI(V) must be specified for given GTI value
If the gti(x)=4 parameter is specified, then an np(v) and nai(v) parameter combination must be specified. These parameters can be specified in any combination.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for more information.
2.2.1335 E3556 Cmd Rej: MTT_ATLEAST_ONE_SFAPP_GTT_ACT_MUST_CONFIG
When no GTT Action is provisioned for the SFAPP card.
Recovery
- Provision SFAPP GTT action on EAGLE.
2.2.1336 E3557 Cmd Rej: EGTT must be ON
The Enhanced GTT (EGTT) feature must be turned on before
the
ent/chg/dlt/rtrv-gta,
ent/chg/dlt/rtrv-gttsel, or
ent/chg/dlt/rtrv-gttset
commands can be entered.
For the
enable-ctrl-feat command, the EGTT
feature must be turned on before the Flexible Linkset Optional Based Routing
(FLOBR),
GTT Action - DISCARD, GTT Action - DUPLICATE, GTT
Action - FORWARD, MO SMS B-Party Routing, or Origin-based SCCP Routing
(OBSR) features can be enabled:
For the
chg-gsmsmsopts command, the EGTT
feature must be turned on before the
is41smscgttsn parameter can be
specified.
For the
chg-mtc-measopts command, the EGTT feature must be
turned ON before the
mtchgttset=on or
mtcdgttset=on parameters can be specified.
For the
ent/chg-lnp-serv commands, the EGTT
feature must be turned on before the
(n)gttselid, (n)dfltact, or
on/off=gttrqd parameter can be
specified.
For the
ent/chg/rtrv-srvsel command, the EGTT
feature must be turned on before the
(n)gttselid or
(n)dfltact parameter can be
specified.
For the
ent-gttact command, the EGTT feature
must be turned on before the
srvc or
scpval GTT Action can be entered.
For the
rept-ftp-meas command, the EGTT feature must be
turned ON before the
enttype=gttset parameter can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1337 E3558 Cmd Rej: SFAPP SSN can not be used
The SSN value already assigned to SFAPP should not be
used in
alw-map-ss, chg-gta, chg-gtmod, chg-gtt, chg-gttsel, chg-map,
chg-mrn, ent-gta, ent-gtmod, ent-gtt, ent-gttsel, ent-map, ent-mrn,
and
inh-map-ss commands.
Recovery
2.2.1338 E3560 Cmd Rej: (n)GTT Set specified by GTTSN already exists
The value specified for the gttsn parameter cannot already exist in the database.
Recovery
2.2.1339 E3561 Cmd Rej: GTT Set specified by GTT Set Name/index does not exist
The value specified for the GTT set name parameter must match the name of an existing GTT Set.
Recovery
2.2.1340 E3562 Cmd Rej: Network domains of GTI and CdPA GTT Set must match
For the chg-gttsel command, the network domain (ANSI or ITU) must match the domain of the GTT Set entry specified by the cdgttsn, cdgtasn, or gttsn parameter.
For the ent-gttsel command, the network domain of the specified GTT selector must match the domain of the GTT set specified by the gttsn, cdgtasn, or cdgttsn parameter, unless the domain of the GTT set has a value of cross.
Recovery
2.2.1341 E3563 Cmd Rej: NAI entries per TT-NP combination has reached allowed max
If the gti(x)=4 parameter is specified, then the GTT Selector table cannot have more than 5 NAI entries per TT/NP combination.
Recovery
2.2.1342 E3564 Cmd Rej: GTT Set table is full
The specified GTT set could not be enetered into the GTT Set table because the GTT Set table is full. The GTT Set table contains a maximum of 2000 entries.
Recovery
2.2.1343 E3565 Cmd Rej: Set name must not be specified as NONE
For the ent/chg/dlt/rtrv-gta command, a value of none cannot be specified for the gttsn or refgttsn parameter.
For the ent/chg/dlt/rtrv-gttset command, the (n)gttsn=none parameter cannot be specified.
For the ent-gttsel command, a value of none cannot be specified for the gttsn, cdgtasn, cggtasn, cgpcsn, cdgttsn, or cggttsn parameter.
For the ent/rtrv-gttact-path command, a value of none cannot be specified for the opgttsn, cggttsn, or cdgttsn parameter.
For the ent/chg/dlt/rtrv-gtt and ent/dlt/rtrv-tt commands, the ttn=none parameter cannot be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1344 E3566 Cmd Rej: GTT Set is being referred by other entities
The GTT set cannot be deleted if it is referenced by npsn or in the GTTSEL or GTA tables, or if the GTT set is used by the BPARTYGTTSN or IS41SMSCGTTSN option.
Recovery
2.2.1345 E3567 Cmd Rej: GTT Set must not be used by or assigned to any Translation
For the chg-gttset command, if GTAs are assigned to the GTT set, then the ndgt parameter cannot be specified.
For the dlt-gttset command, if any translation is provisioned in the GTT set or if the GTT set is used by any translation, then the GTT set cannot be deleted.
Recovery
2.2.1346 E3568 Cmd Rej: Either NUM parm or OLD/NEW parm must be specified
Either the NUM parameter or the old VLR/NEW VLR parameter can be specified.
Recovery
- Specify the oldVLR/NewVLR or Num parameter.
2.2.1347 E3569 Cmd Rej: OLD and NEW VLR combination already exists
When the Old VLR and NEW VLR combination already exists.
Recovery
- Enter another combination of oldVLR and newVLR.
2.2.1348 E3570 Cmd Rej: Point Code type does not match GTT Set network domain
The ANSI/ITU SCCP Conversion feature must be enabled before a translated point code that is of a different domain than the GTT set specified by the gttsn parameter can be specified.
Recovery
2.2.1349 E3571 Cmd Rej: GTA/SADDR Length does not match GTT Set number of digits
The length of the specified gta/saddr parameter must match the number of digits provisioned for the specified GTT set when the VGTT feature is turned off. If the VGTT feature is turned on, then up to 10 GTA/SADDR lengths can exist per GTT set. If the Support for 16 GTT Lengths in VGTT feature is turned on, then up to 16 GTA/SADDR lengths can exist per GTT set.
Note:
Once a feature that is controlled with a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1350 E3572 Cmd Rej: RI must be SSN when CCGT is YES
If the ccgt=yes parameter is specified, then the ri=ssn parameter must be specified.
Recovery
Re-enter the ent/chg-gta command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1351 E3573 Cmd Rej: CCGT must be NO when PC is the STP’s PC or CPC
If the new or existing pc/pca/pci/pcn/pcn24 parameter is an STP point code or capability point code, then the ccgt=no parameter must be specified.
Recovery
2.2.1352 E3574 Cmd Rej: BLACKLIST VLR number is not allowed
- Enter a non-blacklisted VLR number.
2.2.1353 E3575 Cmd Rej: The sum of the values for NPCFMTI must be equal to 14
The sum of all the values specified by the npcfmti parameter (m1+m2+m3+m4) must equal 14.
Recovery
Re-enter the chg-stpopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1354 E3577 Cmd Rej: CCGT must be NO when RI is set to GT
If the ccgt=no parameter is specified, then the ri=gt parameter must be specified.
Recovery
Re-enter the ent-gta command that generated this error message, specifying ccgt=no and ri=gt. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1355 E3578 Cmd Rej: NP and NAI must be specified as DFLT together
A value of dflt must be specified for the np and nai parameters, or neither parameter can have a value of dflt.
Recovery
Re-enter the ent/chg/dlt/rtrv-gttsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - GTT User's Guide for assistance.
2.2.1356 E3579 Cmd Rej: NI parameter may not be specified for ITU linksets
If the type=gtwy parameter is specified, and the value of the enttype parameter is lsorigni, lsdestni, or lsonismt, then the ni parameter cannot be specified for ITU linksets.
Recovery
2.2.1357 E3581 Cmd Rej: SSN value must be LNP, INP, EIR, VFLEX, ATINPQ or AIQ SSN
The value specified for the ssn parameter must be the AIQ, ATINPQ, EIR, INP, LNP, or V-Flex subsystem number.
Recovery
2.2.1358 E3582 Cmd Rej: INP Subsystem is offline in database
The INP subsystem must be online before the INP subsystem number can be specified as a value for the ssn parameter.
Recovery
2.2.1359 E3583 Cmd Rej: Initial Command Response Timeout
A response from the entered command has not been received on the OAM/EOAM, within the two-second command response interval.
Recovery
2.2.1360 E3584 Cmd Rej: No SCCP application card provisioned to support feature.
An SCCP application card must be present in the system before the feature can be enabled.
Recovery
2.2.1361 E3585 Cmd Rej: Dest IP Address is invalid
A valid destination IPv4 or IPv6 address must be specified as the value for the dest or dest6 parameter. Refer to the command description in Commands User's Guide for the criteria for a valid destination IP address.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1362 E3586 Cmd Rej: Dest IP Address already exists for this card
The destination IP address specified by the dest parameter cannot already exist for the card in the location specified by the loc parameter.
Recovery
2.2.1363 E3587 Cmd Rej: Dest IPAddr can't be local to any of the n/w on the card
The destination IP address cannot be local to the A or B any network for the card in the location specified by the loc parameter.
Recovery
2.2.1364 E3588 Cmd Rej: Dest IP Address does not exist for this card
The destination IP address specified by the dest parameter must already exist in the IP Route table for the specified card.
Recovery
2.2.1365 E3589 Cmd Rej: Specified cards A, B interface IP Address must be assigned
The A or B interface IP address must already be assigned for the card specified by the loc parameter.
Recovery
2.2.1366 E3591 Cmd Rej: Invalid System serial number
Note:
Contact My Oracle Support before using theent-serial-number command. Entering a serial number into the Secure Gateway with lock=yes is permanent. Correcting an incorrect serial number requires a manual procedure and system disk (MO) from Oracle.
The specified serial number must meet the following naming conventions:
-
Up to 15 alphanumeric characters (A...Z,a...z, or 0...9). Mixed case is allowed.
-
The first two characters (the prefix) must be letters.
-
The remaining characters must be numeric.
-
No special characters or spaces.
Recovery
Contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1367 E3592 Cmd Rej: System serial number is already locked in database
The specified serial number has already been locked in the Serial Number table. Once the table is locked, the serial number cannot be specified again.
Recovery
Contact My Oracle Support for assistance with changing the serial number. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1368 E3593 Cmd Rej: Part Number does not belong to an On/OFF Feature
The Part Number specified in the command must be for an On/Off feature that is currently on. If a Permanently On feature is turned on with this command, then it cannot be turned off. Refer to the command description in Commands User's Guide for a list of On/Off features.
Recovery
Determine the status of the feature in the system. Enter the rtrv-ctrl-feat command.
Note:
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.Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1369 E3594 Cmd Rej: Def Router IP Addr cannot be an existing IP Link Address
The defrouter IP address cannot be an existing IP Link Address.
Recovery
- Display the TCP/IP data links in the database. Enter the
rtrv-dlkcommand. - Re-enter the
chg-ip-cardcommand that generated this error message, specifying a valid Default Router address.
Refer to the command description in Commands User's Guide and to Database Administration - Features User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1370 E3595 Cmd Rej: Def Router IP Addr must be local to this card's network
The IP address specified by the defrouter parameter must be local to the network for the card.
Recovery
2.2.1371 E3596 Cmd Rej: IP Address still referenced by the Def Router
The values for the ipaddr and subnet, ipaddr6 and prefixlen parameters cannot be changed to addresses that represent a different network if the address specified by the defrouter parameter is assigned to the network interface.
Recovery
2.2.1372 E3597 Cmd Rej: IP Address still referenced by static IP Routes
The addresses specified by the ipaddr and submask parameters cannot be changed to addresses that represent a different network if the address is referenced by any static IP routes using this network interface.
Recovery
2.2.1373 E3598 Cmd Rej: LNP ELAP Configuration and WNP features must be ON
The LNP ELAP Configuration and Wireless Number Portability (WNP) features must be turned on before the LNP SMS feature can be turned on.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1374 E3599 Cmd Rej: WSMSC feature must be Activated
For the chg-lnpopts command, the LNP Short Message Service (LNP SMS) feature must be turned on before the wsmsc10dig parameter can be specified.
For the ent/chg-lnp-serv commands, the LNP SMS feature must be turned on before the (n)serv=wsmsc parameter can be specified.
Recovery
2.2.1375 E3600 Cmd Rej: Old and New VLR should be different
- Enter different values in the oldVLR and newVLR parameters.
2.2.1376 E3601 Cmd Rej: OLD and NEW VLR combination not exists
The OLD and NEW VLR combination does not exist in the VLR Roaming table.
Recovery
2.2.1377 E3602 Cmd Rej: Failure reading VLR Roaming Table
Failure reading VLR Roaming Table in the
ent-vlr-roaming, chg-vlr-roaming, rtrv-vlr-roaming,
and
dlt-vlr-roaming commands.
Recovery
2.2.1378 E3603 Cmd Rej: VLR length is out of range. Range: 1....5
The VLR number in a VLR profile can not be longer than 5 digits.
Recovery
2.2.1379 E3604 Cmd Rej: Failure reading VLR Profile Table
Not able to access the VLR Profile Table in the
ent-vlr-prof, chg-vlr-prof, rtrv-vlr-prof, dlt-vlr-prof,
ent-vlr-roaming, chg-vlr-roaming, and
rtrv-vlr-roaming commands.
Recovery
2.2.1380 E3605 Cmd Rej: An entry with entered VLR already exists in VLR profile tbl
- Enter a different VLR number as this one already exists.
2.2.1381 E3606 Cmd Rej: VLR Profile Table is full
- Delete one ore more entries before entering a new one, as the table is full.
2.2.1382 E3607 Cmd Rej: No entry found for entered VLR in VLR profile tbl
There is no existing VLR profile for the entered VLR in the VLR Profile Table.
Recovery
2.2.1383 E3608 Cmd Rej: Max no of VLR entries provisioned with same leading digits
- Delete one or more entries with same leading digits as the number being entered.
2.2.1384 E3609 Cmd Rej: A reference of this entry exists in VLR roaming tbl
Reference(s) of the VLR entry with the same VLR number as the entered VLR exists in the VLR Roaming Table.
Recovery
2.2.1385 E3610 Cmd Rej: Failure reading VLR DBMM Table
Not able to access the VLR DBMM Table in the
ent-vlr-roaming, chg-vlr-roaming, dlt-vlr-roaming,
ent-vlr-prof, chg-vlr-prof, and
dlt-vlr-prof commands.
Recovery
2.2.1386 E3611 Cmd Rej: STP table is full
This MTT is displayed when user tries to add another point code in the STP table and table is full.
Recovery
2.2.1387 E3612 Cmd Rej: SSN must be in SS-APPL table when PC is true point code
If the pc/pca/pci/pcn/pcn24 parameter is specified, and the point code is the STP true point code, then the value specified for the ssn parameter must already exist in the SS-APPL table.
Recovery
2.2.1388 E3613 Cmd Rej: DPC must exist for the STP entry
2.2.1389 E3614 Cmd Rej: STP point code already in use
2.2.1390 E3615 Cmd Rej: T1 Port test command in progress
A T1 Port test is already in progress. Only one port test is performed at a time.
Recovery
Wait for all tests to complete, then re-enter the tst-t1 command.
2.2.1391 E3616 Cmd Rej: APC/SAPC type and group code must match DPC
The adjacent point code/secondary adjacent point code (APC/SAPC) type and group code in the linkset specified by the lsn parameter must match the value specified by the dpc/dpca/dpci/dpcn/dpcn24 parameter.
Recovery
2.2.1392 E3617 Cmd Rej: EPAP240M feature can't be turned ON once EPAPX feature is ON
Once EPAPX feature is ON then EPAP240M feature cannot be turned ON.
Recovery
- EPAPX is ON is a feature and a recovery procedure is not applicable.
2.2.1393 E3618 Cmd Rej: LHOST and ALHOST must refer to different IP addresses
The hostnames specified by the lhost and alhost parameters must be associated with different IP addresses.
Recovery
2.2.1394 E3619 Cmd Rej: LHOST and ALHOST must refer to IP address on the same card
The hostnames specified by the lhost and alhost names must refer to IP addresses on the same IP card.
Recovery
2.2.1395 E3620 Cmd Rej: Mate STP table read failed
2.2.1396 E3621 Cmd Rej: Invalid parameter values for specified ATI/PSI gtmodid
2.2.1397 E3626 Cmd Rej: Cannot change IPSG FCMODE to FCOPY due to ports C/D config
Recovery
Ensure that no IPSG card in Eagle has IP links provisioned on Fast copy ports.
2.2.1398 E3627 Cmd Rej: Invalid combination of LHOST and ALHOST interfaces
If LHOST is on interface A, then ALHOST must be on interface B.
Recovery
- Display the port information for the card. Enter the
rtrv-ip-lnkcommand. - Re-enter the command that generated this error message, specifying a valid combination of parameters.
2.2.1399 E3628 Cmd Rej: SFAPP(P) to OAM SYNC in progress
The OAM synchronization is in progress.
Recovery
2.2.1400 E3629 Cmd Rej: Turn off EISCOPY before changing PVN and PVNMask
The EAGLE 5 Integrated Monitoring Support feature copy (EISCOPY) function must be turned off before the PVN and PVN submask addresses in the system.
Recovery
2.2.1401 E3630 Cmd Rej: Entry is already defined as the STP Options DefCC
The value specified for the multcc or nmultcc parameter cannot already be defined as the STP Options Default Country Code (DEFCC) by the chg-stpopts command.
Recovery
- Display the value specified for the defcc parameter. Enter the
rtrv-stpoptscommand. - Re-enter the
chg-gsmoptscommand that generated this message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the G-Port User's Guide for assistance.
2.2.1402 E3631 Cmd Rej: Incompatible Feature/Option status
For the chg-gsmopts command, the G-Flex feature must be turned on or the G-Port or IGM feature must be enabled before the ccnc and mccmnc parameters can be specified.
For the chg-gsmsmsopts command, the Portability Check for MO SMS feature or the MO-based GSM SMS NP feature must be turned on before the mosmsdigmat or mosmstcapseg parameter can be specified.
For the chg-mtc-measopts command, the A-Port, G-Port, IGM, MO SMS IS41-to-GSM Migration, MO-based GSM SMS NP, MO-based IS41 SMS NP, Prepaid SMS Intercept Ph1, TIF ASD, TIF GRN, TIF Number Portability, or TIF Simple Number Substitution feature must be enabled, or the INP feature must be turned on before the mtchnp=on parameter or the mtcdnp=on parameter can be specified.
For the ent/chg/rtrv-srvsel commands, the PPSMS or Portability Check for MO SMS feature must be turned on, or the MO SMS ASD, MO SMS GRN, MO SMS IS41-to-GSM Migration, MO SMS B-party Routing, MO-based GSM SMS NP, or MO-based IS41 SMS NP feature must be enabled before the (n)serv=smsmr parameter can be specified.
For the chg-stpopts command, If the TN quantity key is above 228M, or if ELAP version 8.0 or above is provisioned, then the dsmaud=ccc parameter cannot be specified.
For the rept-ftp-meas and rept-meas commands, the A-Port, G-Port, IGM, Prepaid SMS Intercept Ph1, TIF ASD, TIF GRN, TIF Number Portability, or TIF Simple Number Substitution feature must be enabled, or the INP, MO SMS IS41-to-GSM Migration, MO-based GSM SMS NP, or MO-based IS41 SMS NP feature must be turned on before the mtchnp=on or mtcdnp=on parameter can be specified.
The A-Port or IGM feature must be enabled before the rtrv-is41opts command can be entered.
Recovery
2.2.1403 E3632 Cmd Rej: MULTCC list is full
The multiple country code (MULTCC) list can contain a maximum of 10 entries.
Recovery
2.2.1404 E3633 Cmd Rej: MULTCC entry does not exist
If the multcc and nmultcc parameters are specified to change the multcc value to the nmultcc value, then the multcc value must already exist in the multiple country code list.
Recovery
- Display the current entries in the MULTCC list. Enter the
rtrv-gsmoptscommand. - Re-enter the
chg-gsmoptscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the G-Port User's Guide for assistance.
2.2.1405 E3634 Cmd Rej: Cannot set DefCC to none if a GSM Options MULTCC is defined
If a GSM Options MULTCC entry has already been defined then the defcc=none parameter cannot be specified.
Recovery
2.2.1406 E3635 Cmd Rej: UIM number does not exist in STP Trouble Text Table
The UIM number must already exist in the Trouble Text table.
Recovery
- Verify that the UIM number has been entered correctly. Refer to Unsolicited Alarm and Information Messages Reference for a complete list of UIM numbers.
- Re-enter the
set-uim-acthreshcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - System Management User's Guide for assistance.
2.2.1407 E3636 Cmd Rej: No ACTIVE SFAPP Card available
There is no active SFAPP card available.
For the
chg-sfappopts command, when there is no active SFAPP
cards on the EAGLE, the user will not be able to switch the mode.
Recovery
Ensure that there is an active SFAPP card in the system.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1408 E3637 Cmd Rej: Turn OFF SFAPP(P)->OAM sync before this command
OAM DB goes into inconsistent state while executing the
format-disk command just before SFAPP->OAM sync.
The prisfsync parameter in SFAPPOPTS table must be turned off before running this command.
Recovery
- Set value of prisfsync parameter as off using chg-sfappopts:prisfsync=off command.
- Re-enter the command that generated this error message.
2.2.1409 E3638 Cmd Rej: Failed Reading SS Appl table
The SS Appl table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1410 E3639 Cmd Rej: SUBCDPN should be configured in TIFOPTS for TIFRDNBL SA
SUBCDPN will be the number replaced instead of CDPN in case SA is TIFRDNBL, therefore, it is mandatory for this SA.
Recovery
If SA is TIFRDNBL, configure TIFOPTS using the
chg-tifopts:subcdpn=<> command.
2.2.1411 E3642 Cmd Rej: Invalid Generic Name
Format of Generic name entered is invalid.
Recovery
Set Generic name containing up to a maximum of 15 characters and values including 0-9, A-Z, *, SPACE, and all special characters.
The supported formats are as follows:
- zzzzzz
- zzz*
- *zzz
- zz*zz
- *zz*
2.2.1412 E3643 Cmd Rej: Similar Generic name already exist
Subset or Super-set of the Generic name is already present in the gen-name table.
Recovery
Add an alternate Generic name.
2.2.1413 E3644 Cmd Rej: Generic name table full
Generic name table full.
Recovery
Delete an existing Generic name entry.
2.2.1414 E3645 Cmd Rej: Unable to read Generic name table
Unable to read Generic name table.
Recovery
Replace the table manually.
2.2.1415 E3646 Cmd Rej: GWS must be ON before CNCF can be ON
The Gateway Screening (GWS) feature must be turned on before he CNCF feature can be turned on.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1416 E3647 Cmd Rej: WNP feature must be ON
The Wireless Number Portability (WNP) feature must be turned on before the (n)serv=wnp parameter can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1417 E3648 Cmd Rej: XLAT must be DPCSSN and RI must be SSN if PC is the True PC
If the pc/pca/pci/pcn/pcn24 parameter is specified, and the point code is the STP true point code, then the value of the new or existing xlat parameter must be dpcssn, and the new or existing value of the ri parameter must be ssn.
Recovery
2.2.1418 E3649 Cmd Rej: Generic name does not exist
Generic name does not exist in the table.
Recovery
Set Generic name.
2.2.1419 E3650 Cmd Rej: Generic name table empty
Generic name table empty.
Recovery
Set Generic name.
2.2.1420 E3651 Cmd Rej: SUBCDPN referenced in NPP-SRS cannot be removed.
If SUBCDPN is referenced in npp-srs it cannot be set to none.
Recovery
Remove the reference of SUBCDPN from NPP-SRS.
2.2.1421 E3652 Cmd Rej: IPSM to OAM SYNC in progress
Block all UI commands as IPSM->OAM sync is in progress as the CAT2 table is getting updated.
Recovery
Stop the IPSM to OAM sync.
Re-enter the commands that generated this error message.
2.2.1422 E3654 Cmd Rej: TCP/UDP connection is not supported on this port interface
TCP connections on SCCP/SFAPP cards for Visualization must be on Port C.
Recovery
Map TCP connections on SCCP/SFAPP cards to Port C for Visualization connectivity.
2.2.1423 E3655 Cmd Rej: Failed Reading the GWS Stop Action Set table
The GWS Stop Action table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1424 E3656 Cmd Rej: ACTNAME specified must exist in GWS Stop Action Set table
The value specified for the actname parameter must already exist in the GWS Stop Action Set table.
Recovery
2.2.1425 E3657 Cmd Rej: NSR cannot be specified if ACTNAME is specified
The nsr and actname parameters cannot be specified together in the command.
Recovery
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.
2.2.1426 E3658 Cmd Rej: NSFI must be STOP if ACTNAME is specified
If the actname parameter is specified, then the nsfi=stop parameter must be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.1427 E3661 Cmd Rej: Target drive capacity must be sufficient to perform request
The target drive must have sufficient capacity to hold the required amount of data. Refer to the Commands User's Guide for the disk drive capacity requirements.
Recovery
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.2.2.1428 E3665 Cmd Rej: ENUMBER must be greater than or equal to SNUMBER
Recovery
To retrieve an entry, enter the same same.
2.2.1429 E3668 Cmd Rej: No other optional parameters may be specified with ALL
If the all=none parameter is specified, then no other optional parameters can be specified.
Recovery
Re-enter the chg-gws-actset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.1430 E3669 Cmd Rej: The CNCF feature must be on if CNCF is specified
The Calling Name Conversion Feature (CNCF) feature must be turned on before a value of cncf can be specified for the act1 - act10 parameters.
Note:
Once a feature that is controlled using a feature bit is turned on, it cannot be turned off.Recovery
2.2.1431 E3671 Cmd Rej: Duplicate ACTs in different slots are not allowed
A specific gateway screening stop action can be specified for only one gateway screening stop action parameter for each gateway screening stop action set. Refer to the chg-gws-actset command description in Commands User's Guide for a list of valid stop actions.
Recovery
Re-enter the chg-gws-actset command that generated this error message, specifying a valid combination of parameters.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1432 E3672 Cmd Rej: ACTNAME already exists in GWS Action Set Table
The value specified for the actname parameter must already exist in the database.
Recovery
- Display the existing values for the actname parameter. Enter the
rtrv-gws-actsetcommand. - Re-enter the
chg-gws-actsetcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance. s
2.2.1433 E3673 Cmd Rej: COPY must be in ACT1
The copy value can be used only with the act1 parameter.
Recovery
Re-enter the chg-gws-actset command that generated this error message, specifying a vaid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.1434 E3674 Cmd Rej: RDCT must be in lowest priority action slot
The rdct value must be specified with the last gateway screening stop action parameter specified for the command.
Recovery
Re-enter the chg-gws-actset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.1435 E3675 Cmd Rej: An ACTNAME must be specified
A value for the actname parameter is required when an action set is first entered in the database. Afterward, the actname parameter is optional.
Recovery
Re-enter the chg-gws-actset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.1436 E3678 Cmd Rej: ACTNAME and ACTID can not both be specified
The actname and actid parameters cannot be specified together in the command.
Recovery
Re-enter the rtrv-gws-actset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.1437 E3679 Cmd Rej: FORCE=YES must be specified to change existing stop action
The force=yes parameter must be specified to change an existing stop action.
Recovery
Re-enter the chg-gws-actset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - GWS User's Guide for assistance.
2.2.1438 E3680 Cmd Rej: No match on ACTNAME parameter during retrieve
A match must exist for the value specified for the actname parameter.
Recovery
- Display the existing values for the actname parameter. Enter the
rtrv-gws-actsetcommand without specifying any parameters. - Enter a new actname value as desired. Refer to the Database Administration - GWS User's Guide for assistance.
- Re-enter the
rtrv-gws-actnamecommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1439 E3681 Cmd Rej: Source and destination combination is not allowed
For the act-upgrade command, if the dest=remove parameter is specified, then the src=fixed and src=usb parameters cannot be specified.
Caution:
It is strongly recommended that theact-upgrade command be used only in conjunction with the system Upgrade Procedure for your target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.
For the copy-gpl command, GPLs can be copied only as follows:
- From the fixed disk on the active TDM to the removable drive
- From the removable drive to the fixed disk on the standby TDM
- From the active TDM to the standby TDM
- From the standby TDM to the removable drive
The active TDM cannot be the destination.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1440 E3682 Cmd Rej: GWS and LNP must be ON before TLNP can be ON
The LNP and Gateway Screening features must be turned on before the Triggerless LNP feature can be turned on.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1441 E3683 Cmd Rej: TLNP feature must be ON
For the chg-gws-actset command, the Triggerless LNP Feature (TLNP) must be turned on before a value of tlnp can be specified for the act1 - act10 parameters.
For the chg-lnpopts command, the TLNP feature must be turned on before the jipprv or jipdigits parameter can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1442 E3685 Cmd Rej: TLNP and CNCF cannot be in the same action set
The tlnp and cncf stop actions cannot be specified in the same action set.
Recovery
Re-enter the chg-gws-actset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.1443 E3686 Cmd Rej: GTT DBMM table is full
The GTTDBMM Table cannot contain more than 42,502 entries.
Recovery
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1444 E3687 Cmd Rej: Cannot enter MULTCC if STP Options DefCC is NONE
If the defcc=none parameter is specified (see the chg-stpopts command), then the multcc parameter cannot be specified.
Recovery
2.2.1445 E3688 Cmd Rej: 15-minute measurement collection in progress
For the chg-measopts command, if quarter-hour collection and report processing is in progress, then the collect15min=off parameter cannot be specified.
For the rept-ftp-meas or rept-meas command, if quarter-hourly collection and report processing is in progress, then the report type comp, systot, avl, or gtwy cannot be specified.
Recovery
To get a report before routine collection has started, perform one of the following actions:
- Enter the command, specifying the period=last parameter.
- Enter the command without specifying the period parameter.
- Re-enter the command after collection has completed.
Note:
The prior period is no longer accessible after collection has completed.
Refer to the command description in Commands User's Guide and to the Measurements Reference for assistance.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1446 E3689 Cmd Rej: Period must be 1/4 hour boundary
A quarter-hour boundary must be specified for the qh parameter.
Recovery
Re-enter the
rept-ftp-meas or
rept-meas command that generated this
error message, specifying a valid combination of parameters. Refer to the
command description in
Commands User's Guide and to
Measurements Reference for assistance.
2.2.1447 E3690 Cmd Rej: QH cannot be specified unless 15 min meas is turned ON
The 15 Minute Measurements feature must be turned on and the 15 Minute Measurements collection option must be on before the qh parameter can be specified.
Recovery
2.2.1448 E3691 Cmd Rej: No other parameters allowed with APPL specification
Unless appl=vsccp/ipsg is specified, no other parameter can be specified with the appl parameter.
Recovery
Re-enter the rept-stat-card 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1449 E3693 Cmd Rej: COLLECT can't be ON if COLLECT15MIN & PLATFORMENABLE are ON
Note:
The Measurements Platform collection option cannot be turned off after it has been provisioned.Recovery
2.2.1450 E3694 Cmd Rej: QH and HH cannot be specified together
The hh and qh parameters cannot be specified together in the command.
Recovery
Re-enter the rept-ftp-meas or rept-meas command that generated this error message, specifying a vald combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1451 E3695 Cmd Rej: Command supported only for IPGWx and IPSG linksets
This command can be entered for only IPGWx or IPSG M3UA linksets.
Recovery
- Display the linksets in the database. Enter the
rtrv-lscommand. - Configure a new linkset as necessary. Refer to the Database Administration - IP7 User's Guide for assistance.
- Re-enter the
rept-stat-iptpscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1452 E3697 Cmd Rej: 15-minute measurement feature must be ON
The 15 Minute Measurements feature must be turned on before the collect15min=on parameter can be specified.
Recovery
2.2.1453 E3698 Cmd Rej: At least one MCP card must be IS-NR
The Measurements Platform feature must be turned on and a type MCPM card (E5-MCPM-B) must be available in the IS-NR state before the 15 Minute Measurements feature can be turned on.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Note:
The Measurements Platform collection function must be turned on (see thechg-measopts command) before an MCPM card can be placed in the IS-NR state.
Recovery
2.2.1454 E3699 Cmd Rej: EIR feature must be ON
For the ent/chg/dlt-ss-appl commands, the Equipment Identity Register (EIR) feature must be turned on before the appl=eir parameter can be specified.
For the chg-gsmopts command, the EIR feature must be turned on before the eirgrsp, eirsptype, or eirimsichk parameter can be specified and before the eirimsichk option can be specified for the on or off parameter.
For the ent/chg-map commands, the EIR feature must be turned on before a true point code value for the pci or mpci parameter can be specified
For the chg-mtc-measopts command, the EIR feature must be turned on before the mtcdeir=on or mtcheir=on parameter can be specified
For the chg-sid command, the EIR feature must be turned on before the cpctype=eir parameter can be specified
For the ent/chg-srvsel commands, the EIR feature must be turned on before the (n)serv=eir parameter can be specified
For the ent-trace command, the EIR feautre must be turned on before the imei parameter can be specified.
For the rept-ftp-meas command, the EIR feature must be turned on before the enttype=eir parameter can be specified.
Recovery
2.2.1455 E3710 Cmd Rej: APPL not valid for command
For the chg-card command, a value of ipsg must be specified for the nappl parameter.
For the ent/init/rept-stat-card or rept-meas command, a valid value must be specified for the appl parameter. Refer to the command description in the Commands User's Guide for a list of valid values.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters.
2.2.1456 E3717 Cmd Rej: Both LIMIT and INTRVL must be specified
The limit and intrvl parameters must be specified together in the command.
Recovery
Re-enter the set-uim-acthresh command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.1457 E3725 Cmd Rej: Removable drive database level is not compatible
The removable plug-in flash drive cannot contain an EAGLE backup image.
Recovery
Caution:
It is strongly recommended that theact-upgrade command be used only in conjunction with the system Upgrade Procedure for your target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.
2.2.1458 E3726 Cmd Rej: Active device state does not permit database change
For the chg/ent-card commands, the E5-ENET or E5-ENET-B card must be inhibited and in an Out-of Service-state before the card can be changed/provisioned.
For the chg-gedti-card command, if the GEDTI Hub is in ACTIVE state then the port cannot be changed.
For the dlt-card command, the card must be inhibited before it can be deleted.
For the dlt-lg-card command, the card must be deactivated before it can be deleted.
For the dlt-lg-engine command, the engine must be deactivated before it can be deleted.
For the dlt-lg-grp command, the group must be deactivated before it can be deleted.
For the dlt-slk command, the signaling link must be in the unavailable (UAV) state before it can be removed.
For the ent-slk command, the command cannot be entered, if the link is In-Service.
Recovery
2.2.1459 E3727 Cmd Rej: Max number of cards of application type already exist
The maximum number of cards allowed for that application type cannot be exceeded in the database.
Refer to the command description for the ent-card command and Appendix A of the Commands User's Guide for additional card information.
Recovery
2.2.1460 E3728 Cmd Rej: Card(s) not in-service normal - FORCE parameter required
The force=yes parameter must be specified for cards that are not the In-service Normal state.
Recovery
2.2.1461 E3731 Cmd Rej: Invalid Hostname
The value specified for the host parameter must begin with an alphabetic character and can contain a–z, A–Z, 0–9, -, or .. The host name can be up to 60 characters in length.
Recovery
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 and to the Database Administration - IP7 User's Guide for more information.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1462 E3732 Cmd Rej: Invalid Subnet Mask
For the chg-ip-card command, a valid value must be specified for the bpsubmask parameter. .
For the chg-ip-lnk and ent-ip-rte commands, a valid value must be specified for the submask parameter.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.1463 E3733 Cmd Rej: Socket name not found
The specified socket name was not found in the associated table.
Recovery
- Determine if the entered socket name is present in the SNAME field of the output. Enter the
rtrv-appl-rtkeycommand. - Re-enter the
dlt-appl-rtkeycommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1464 E3735 Cmd Rej: Hostname must be unique
The value specified for the host parameter cannot already exist in the IP host table.
Recovery
2.2.1465 E3736 Cmd Rej: Socket name already exists
The specified socket name and filter parameters cannot already exist in the Routing Key table.
Recovery
- Display the socket names and filter parameters in the Routing Key table. Enter the
rtrv-appl-rtkeycommand. - Re-enter the
ent-appl-rtkeycommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1466 E3737 Cmd Rej: Socket connection parameters must be unique
The set of values used to specify a socket (lhost, rhost, lport, rport, port) cannot be identical to a set of values that are used to specify an existing socket.
Recovery
- Display the existing socket connection values. Enter the
rtrv-assoccommand. - Re-enter the
ent-assoccommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1467 E3738 Cmd Rej: Host table is full
The IP Host table can have a maximum of 2048 entries.
Recovery
2.2.1468 E3739 Cmd Rej: No Entry found
The value specified for the host parameter must already exist in the IP Host table.
For the
chg-assoc and
ent-assoc commands, RHOST is not
present in the IPHOST table.
For the
chg/dlt-ip-conn command, the value
specified for the CNAME parameter must already exist in the IPCONN table.
For the
chg/dlt/rtrv-enum-prof command, the
specified profile name must be present in the ENUM Profile Table.
For the
dlt/rtrv-enum-acl command, the IP
address specified by the
IPADDR/IPADDR6 parameter must be
provisioned in the ENUM ACL Table.
For the
dlt/rtrv-enum-profsel command, the
value specified for the
ENTITYID,
SDN or
EDN must already exist in the ENUM
Profile Selection Table or the ENUM DN Block Table respectively.
Recovery - Non-ENUM commands:
- Display the existing entries in the IP Host table.
Enter the
rtrv-ip-hostcommand.Host names are shown in the HOST field.
- 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 and to Database Administration - IP7 User's Guide for assistance.
Recovery - ENUM commands:
- Use the
rtrv-enum-prof,rtrv-enum-acl, orrtrv-enum-profselcommand to display the entries in the ENUM Profile Table, ENUM ACL Table, ENUM Profile Selection Table, or the ENUM DN Block Table. - 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1469 E3740 Cmd Rej: If AUTO=yes, Then Duplex and SPEED are not allowed
If the auto=yes parameter is specified, then the duplex and speed parameters cannot be specified.
Recovery
Re-enter the chg-ip-lnk command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1470 E3741 Cmd Rej: If TIMER is specified, TVALUE must be specified
If the timer parameter is specified, then the tvalue parameter must be specified.
Recovery
Re-enter the chg-uaps command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1471 E3742 Cmd Rej: If PARM is specified, PVALUE must be specified
If the parm parameter is specified, then the pvalue parameter must be specified.
Recovery
Re-enter the chg-uaps command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1472 E3743 Cmd Rej: SSN required if SI is 3
If the si=3 (or the string equivalent si=sscp) parameter is specified, then the ssn parameter must be specified.
Recovery
Re-enter the ent/chg/dlt-appl-rtkey or ent/dlt-rmt-appl command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1473 E3745 Cmd Rej: Invalid Domain name
The value specified for the domain parameter must be comprised of (a–z, A–Z, 0–9, -, .), and up to 120 characters in length. If the value contains a hyphen, then the host name must be enclosed within quotation marks.
Recovery
Re-enter the
chg-ip-card command that generated
this error message, specifying a valid combination of parameters. Refer to the
command description in
Commands User's Guide and to the
Database Administration - IP7 User's Guide
for assistance.
2.2.1474 E3746 Cmd Rej: No other optional parms can be entered with SRCSET
If the srcset parameter is specified, then no additional optional parameters can be specified.
Recovery
Re-enter the chg-uaps command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1475 E3747 Cmd Rej: Too many IP connections per card
The E5-ENET, E5-ENET-B, and SLIC cards have a maximum number of allowed associations and links.
Recovery
Re-enter the ent/chg-assoc command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1476 E3748 Cmd Rej: Socket Table full
IP Socket/Association (IPAPSOCK) Table cannot contain more than 4000 entries.
Recovery
- Use the
rtrv-assoccommand to see all the configured associations. - Use the
dlt-assoccommand to delete the unneeded association entries. - Re-enter the
ent-assoccommand to configure an association.
Refer to the command descriptions in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1477 E3749 Cmd Rej: If IPADDR is specified SUBMASK is required
The ipaddr and submask parameters must be specified together in the command.
Recovery
Re-enter the chg-ip-lnk command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1478 E3751 Cmd Rej: Max sockets per routing key exceeded
The routing key cannot already be associated with the maximum number of socket names allowed (16).
Recovery
2.2.1479 E3753 Cmd Rej: Command is not supported for IPLIM SS7IPGW
tst-slk command.
Recovery
2.2.1480 E3754 Cmd Rej: Command is not supported for IPGW(x) links
The command is not valid for cards running the IPGHC GPL.
Recovery
2.2.1481 E3757 Cmd Rej: SSN is not allowed unless SI is 3
The si=3 (or the string equivalent si=sccp) parameter must be specified before the ssn parameter can be specified.
Recovery
2.2.1482 E3758 Cmd Rej: If Domain name is specified RSTDOMAIN is not valid
The rstdomain and domain parameters cannot be specified together in the command.
Recovery
Re-enter the chg-ip-card command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1483 E3760 Cmd Rej: IP Address must be unique
For the chg-ip-card command, the IP address specified by the bpipaddr and bpsubmask parameters must be unique.
For the chg-ip-lnk command, each IP address entered into the IP Link table must be unique.
For the ent-enum-acl command, the IP address specified by the ipaddr parameter must be unique.
For the ent-ip-host command, the value specified for the ipaddr parameter cannot already exist in the IP Host table.
Recovery
2.2.1484 E3761 Cmd Rej: At least one of TIMER, PARM, SRCSET must be entered
The parm, srcset, or timer parameter must be specified.
Recovery
Re-enter the chg-uaps command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1485 E3762 Cmd Rej: Host table must contain IP Link addresses
For the
chg-ip-lnk command, the value
specified for the
ipaddr and
ipaddr6 parameter must already exist in the IP
Host table.
For the
dlt-ip-host command, if the value
specified for the
host parameter has an IP address in
the IP Link table, then the IP address must be deleted from the IP Link table
before the IP host name can be deleted.
Recovery -
chg-ip-lnk
- Display the IP Host table. Enter the
rtrv-ip-hostcommand.The address information is shown in the IPADDR field of the output.
-
Enter an IP address as necessary. Refer to Database Administration - IP7 User's Guide for assistance.
-
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery
- dlt-ip-host
2.2.1486 E3763 Cmd Rej: Routing Key table full
The Routing Key table can contain a maximum of1000 entries per system.
Recovery
2.2.1487 E3764 Cmd Rej: Routing Key not found
The specified entry was not found in the Routing Key table.
Recovery
2.2.1488 E3765 Cmd Rej: Fully specified connection required to change OPEN
Values for all parameters required to fully specify the connection must be specified before the open=yes parameter can be specified. Refer to the command description for the chg-assoc command in the Commands User's Guide for a list of these parameters.
The aname parameter and at least one other optional parameter must be specified before the open=no parameter can be specified.
Recovery
Re-enter the chg-assoc command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1489 E3767 Cmd Rej: Socket Name not defined
The value specified for the sname parameter must already exist in the IPAPSOCK table.
Recovery
2.2.1490 E3768 Cmd Rej: PORT B not supported for device
If the card application is SS7IPGW or IPGWI, then only the link=a parameter can be specified.
Recovery
2.2.1491 E3769 Cmd Rej: Too many sockets per SLK
The allowed maximum is 1 connection per signaling link on IPLIMx cards.
Recovery
- Use the
rtrv-assoccommand to see the SLK configured for the association under consideration. - Re-enter the
chg-assoccommand to configure an association with a unique SLK and socket combination.
Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1492 E3770 Cmd Rej: SS7 parameters cannot be specified for IP7 link
If an IP link is assigned to a card (application IPLIM, IPLIMI, IPGWI, or SS7IPGW), then the atmtsel, e1atmcrc4, e1atmsi, e1atmsn, ecm, lpset, l2tset, ll, pcrn1, pcrn2, vci, and vpi parameters cannot be specified.
Recovery
2.2.1493 E3772 Cmd Rej: Only one SS7IPGW or IPGWI link allowed in mated linkset
If the specified linkset has a mate linkset, only 1 SS7IPGW or IPGWI signaling link can be assigned to the linkset. The assigned link must be an SS7IPGW or IPGWI link.
Note:
When a link is added to a linkset, the link remains in the state OOS-MT-DSBLD (out of service maintenance disabled) until it is activated.Recovery
2.2.1494 E3774 Cmd Rej: Failed reading the UIM Threshold Table
The UIM Threshold table is corrupt or cannot be found by the system.
Recovery
Re-enter the set-uim-acthresh command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1495 E3775 Cmd Rej: SERIAL param valid only with APPL param
The appl parameter must be specified before the serial parameter can be specified.
Recovery
Re-enter the init-card command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1496 E3776 Cmd Rej: Invalid APPL selection for SERIAL init card command
A valid value must be specified for the appl parameter.
Recovery
Re-enter the init-card command, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1497 E3777 Cmd Rej: APPL=ALL can only be selected when SERIAL=YES is specified
The serial=yes parameter must be specified before the appl=all parameter can be specified.
Recovery
Re-enter the init-card command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1498 E3778 Cmd Rej: Active/Stby GPL versions are not compatible
The OAMHC GPL version that is running in the active OAM card location must be the same as the OAMHC GPL version that is running in the standby OAM card location.
Note:
This error may have occurred during an upgrade, when one OAM card can be booted from a removable drive and the other from the fixed disk.Recovery
2.2.1499 E3779 Cmd Rej: FORCE=YES must be specified
If the specified card is the only in-service MPS-Service Module card, then the force=yes parameter must be specified.
Recovery
2.2.1500 E3780 Cmd Rej: Syntax Error Found
The command must conform to the required syntax.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for the syntax rules for the command.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1501 E3781 Cmd Rej: MTP restart option invalid for IPGWx and IPSG-M3UA linksets
If the ipgwapc=yes or ipsg=yes parameter is specified, then the mtprse=yes parameter cannot be specified.
Recovery
2.2.1502 E3782 Cmd Rej: Command Not Found
The pass-through command was not found.
Recovery
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 information about the command.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1503 E3783 Cmd Rej: CICS must be less than or equal CICE
The value specified for the cics parameter must be less than or equal to the value specified for the cice parameter.
Recovery
Re-enter the ent/chg/dlt/rtrv-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - IP7 User's Guide for assistance.
2.2.1504 E3785 Cmd Rej: IPISUP Feature must be ON
The ISUP routing-over-IP feature must be turned on before a DPC/SI/CIC routing key to route ISUP messages can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1505 E3786 Cmd Rej: CIC Range overlaps an existing routing key
The values specified for the circuit identification code range cics - cice cannot overlap an existing routing key.
Recovery
2.2.1506 E3787 Cmd Rej: SSN not allowed with OPC, CICS and CICE
The ssn parameter and the opc, cics, and cice parameters cannot be specified together in the command.
Recovery
Re-enter the rtrv-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1507 E3788 Cmd Rej: OPC, CICS, CICE are required if SI is 4, 5 or 13
If a value of 4, 5, or 13 (or tup, isup, or qbicc, respectively) is specified for the si parameter, then the opc, cics, and cice parameters must be specified.
Recovery
- Display the current settings for the si parameter. Enter the
rtrv-appl-rtkeycommand. - Re-enter the
ent/chg/dlt-appl-rtkeycommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1508 E3789 Cmd Rej: OPC, CICS, CICE are not allowed unless SI is 4, 5 or 13
The opc, cics, and cice parameters can be specified with the si parameter only if the si parameter has a value of 4, 5, or 13 (or tup, isup, or qbicc).
Recovery
- Display the current values for the si parameter. Enter the
rtrv-appl-rtkeycommand. - Re-enter the
ent/chg/dlt/rtrv-appl-rtkeycommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - IP7 User's Guide for assistance.
2.2.1509 E3791 Cmd Rej: Gtwy IP Address is invalid
A valid gateway IPv4 or IPv6 address must be specified for the gtwy or gtwy6 parameter.
Recovery
Re-enter the
ent/dlt-ip-rte command that generated
this error message, specifying a valid combination of parameters. Refer to the
command description in the
Commands User's Guide and to the
Database Administration - IP7 User's Guide
for assistance.
2.2.1510 E3792 Cmd Rej: Gtwy IPAddr must be local to any one of the n/w on the card
For the card in the location specified in the loc parameter, the gateway IP address must correspond to an IP address that is local to this card’s A or B a network on the card.
Recovery
2.2.1511 E3793 Cmd Rej: Max IP Route entries already exist for this card
The maximum number of 64 static IP routes for card in the location specified by the loc parameter already exist in the Static IP Route table.
Recovery
2.2.1512 E3794 Cmd Rej: IP Route table full
A maximum of 2048 static IP routes can exist in the Static IP Route table.
Recovery
2.2.1513 E3795 Cmd Rej: LNP ported NPANXXs 300K Qty Feat Requires at least DSM2GB
At least a 2 GB DSM card must be installed before the LNP ported NPANXX 300K Quantity Key feature can be enabled.
Recovery
2.2.1514 E3796 Cmd Rej: LNP ported LRNs 150K Qty Feat Requires at least DSM2GB
At least a 2 GB DSM card must be installed before the LNP ported LRNs 150K Quantity Keys feature can be enabled.
Recovery
2.2.1515 E3799 Cmd Rej: FORCE=YES must be specified
For the act-lpb or tst-slk command, the force=yes parameter must be specified to activate a test if 256 or more tests are already running in the system.
For the chg-clkopts command, the force=yes parameter must be specified if the hsclksrc and clock=all parameters are specified, and the high speed clocks are reporting.
For the ent/chg-rtx command, the force=yes parameter must be specified if the ilsn and (n)lsn parameter have the same value, or if the value specified for the opc/opca/ppci/opcn/opcn24 parameter is the same as the APC of the linkset specified by the (n)lsn parameter.
For the ent/chg-e1 command, the force=yes parameter must be specified before the chanbrdg=on parameter can be specified for an odd-numbered E1 port on an HC-MIM or E5-E1T1 card if the adjacent next higher even-numbered port is already provisioned with an E1 interface.
For the ent/chg-t1 command, the force=yes parameter must be specified before the chanbrdg=on parameter can be specified for an odd-numbered T1 port on an HC-MIM or E5-E1T1 card if the adjacent next higher even-numbered port is already provisioned with a T1 interface.
For the inh-card command, the force=yes parameter must be specified if the specified card is the only in-service MPS-DSM.
For the rept-stat-rtd command, the force=yes parameter must be specified if the reset=yes parameter is specified
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.1516 E3807 Cmd Rej: Failed reading Secondary Point Code (SPC) table
The Secondary Point Code table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1517 E3809 Cmd Rej: SPC may not exist in the STP’s route table
The value specified for the secondary point code cannot already exist as a destination or an alias in the STP database’s Destination table.
Recovery
- Display the DPCs in the Destination table. Enter the
rtrv-dstncommand. - Re-enter the
ent-spccommand that generated the error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.1518 E3810 Cmd Rej: SPC may not exist as a TPC or CPC in the SID table
For the chg-sid command, the values specified for the true point code and capability point codes cannot be the same as existing secondary point codes.
For the ent-spc command, the value specified for the secondary point code cannot be the same as the existing true point code or capability point code.
Recovery
2.2.1519 E3811 Cmd Rej: SPC may not exist as a TPC, CPC, or DPC in the route table
The value specified for the spc parameter cannot already exist in the Destination table as a destination point code, true point code, or concerned point code.
Recovery
2.2.1520 E3812 Cmd Rej: The SPC already exists
The specified Secondary Point Code (SPC) entry cannot already exists in the Secondary Point Code table.
Recovery
- Display the existing SPCs. Enter the
rtrv-spccommand. - Re-enter the
ent-spccommand that generated the error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.1521 E3814 Cmd Rej: SPC does not exist
The value specified for the spc parameter must already be defined in the SPC table.
If the point code specified by the spc parameter is valid and the linkset type specified by the lst parameter is not prx, then the SPC point code must exist in the SPC table.
Recovery
2.2.1522 E3815 Cmd Rej: The maximum number of SPCs has already been defined
A maximum of 40 Secondary Point Codes (SPCs) can be entered into the database.
Recovery
2.2.1523 E3819 Cmd Rej: SPC may not be referenced in the STP’s route table
A secondary point code (SPC) that is referenced in the Destination table cannot be deleted.
Recovery
2.2.1524 E3820 Cmd Rej: Site SPC must be a full point code
The value specified for the spc parameter must be a a full point code or none. A full point code contains numerical values for all three segments of the point code.
Recovery
Re-enter the ent-spc command that generated this error message, specifying valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1525 E3821 Cmd Rej: SPC & DPC must be the same network type
The network type (ANSI, ITU-N, or ITU-I) of the value specified for the spc parameter, must match the network type for the destination point code (DPC).
If a value other than none is specified for the spc parameter, then the network type of the SPC must match the same network type of the APC.
Recovery
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.
2.2.1526 E3822 Cmd Rej: SPC must be a full point code
The value specified for the spc parameter must be a full point code or none. A full point code contains numerical values for all three segments of the point code.
Recovery
2.2.1527 E3823 Cmd Rej: Domain must be SS7 if SPC is specified
If the spc parameter is specified, then the domain=ss7 parameter must be specified.
Recovery
Re-enter the ent-dstn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.1528 E3825 Cmd Rej: New CIC range overlaps an existing routing key
The value specified for the new circuit identification code range (ncics-ncice) cannot overlap an existing routing key.
Recovery
2.2.1529 E3826 Cmd Rej: NCICS must be less than or equal to NCICE
The value specified for the ncics parameter must be less than or equal to the value specified for the ncice parameter.
Recovery
Re-enter the chg-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration Guide - IP7 User's Guide for assistance.
2.2.1530 E3827 Cmd Rej: No change requested
At least one parameter value must be different from the values provisioned for the table entry.
For the act/dact-gedti commands, activating/deactivating a GEDTI Hub that is already activated/deactivated has no affect.
For the chg-gttapath command, a GTT set-value combination(s) cannot be associated with a GTT path that is already associated to another combination.
Recovery
Re-enter the command that generated this error message, specifying at least one different parameter. Refer to the command description in the Commands User's Guide for assistance.
Recovery - chg-gttapath
2.2.1531 E3828 Cmd Rej: Card GPL type IPGWx requires a link set with IPGWAPC=YES
The lsn parameter must reference a linkset that specifies an IP gateway adjacent point code (ent-ls:ipgwapc=yes).
Recovery
2.2.1532 E3829 Cmd Rej: Link set with IPGWAPC=YES requires IPGWx GPL
If the ipgwapc=yes parameter was specified in the ent-ls command for the linkset specified by the lsn parameter, then the card application must be SS7IPGW or IPGWI.
Recovery
2.2.1533 E3830 Cmd Rej: DPC can't specify cluster rte for IPGWx or IPSG-M3UA linkset
If the ipgwapc=yes parameter has been specified for the linkset specified by the lsn parameter, then the associated dpc/dpca/dpci/dpcn/dpcn24 parameter cannot have a cluster route assigned.
Recovery
2.2.1534 E3831 Cmd Rej: Invalid parameter combination for SI
A valid combination of parameters must be entered for the specified service indicator (si) value. Refer to the command description in Commands User's Guide for valid parameter combinations.
Recovery
Re-enter the chg-appl-rtkey command that generated this error message, specifying a valid combination of parameters.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1535 E3832 Cmd Rej: SPLIT must be greater than CICS
The value specified for the split parameter must be greater than the value specified for the cics parameter.
Recovery
Re-enter the chg-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1536 E3833 Cmd Rej: SPLIT must be less than or equal to CICE
The value entered for the split parameter must be less than or equal to the value entered for the cice parameter.
Recovery
Re-enter the chg-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1537 E3834 Cmd Rej: NCICE unspecified, NCICS must be less than or equal CICE
If the ncice parameter is not specified, then the value specified for the ncics parameter must be less than or equal to the value specified for the cice parameter.
Recovery
Re-enter the chg-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1538 E3835 Cmd Rej: L2STATS not valid for SS7IPGW
Output for the l2stats parameter in the rept-stat-slk command is not available for IP point-to-multipoint links (E5-ENET or E5-ENET-B cards equipped as SS7IPGW or IPGWI links).
Recovery
Display the card and application type. Enter the rtrv-card command.
The information is shown in the TYPE and APPL fields of the output.
Contact My Oracle Support if additional assistance is required. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1539 E3836 Cmd Rej: Command not valid for IPLIM
The command is not valid on TCP/IP point-to-point links (type DCM cards equipped as IPLIM links).
Recovery
2.2.1540 E3837 Cmd Rej: Command not valid for IPGHC
The act-lpo command is not valid for cards running the IPGHC GPL.
The blk-slk command is not valid for cards running IPGHC links.
For the ent-rte command, all routes with ANSI DPCs must use ANSI linkset APCs. A route with an ITU-I DPC can go over an ITU-N APC and an ITU-N DPC can go over an ITU-I APC.
The rept-stat-tstslk command cannot be entered for E5-ENET or E5-ENET-B cards that are running the IPGHC or IPSG application, or that have IPGHC or IPSG-M3UA links.
The tst-slk command is not valid for cards running the IPGHC application.
The ublk-slk command is not valid for E5-ENET or E5-ENET-B cards with IPGHC links.
Recovery
2.2.1541 E3838 Cmd Rej: SPLIT, NCICS, NCICE are not allowed unless SI is 4, 5 or 13
A value of 4, 5, or 13 (tup, isup, or qbicc) must be specified before the split, ncics, or ncice parameter can be specified.
Recovery
Re-enter the chg-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1542 E3839 Cmd Rej: SPLIT, RC, NCICS, NCICE or attributes required
The split, rc, ncics, or ncice parameter must be specified in the command.
Recovery
Re-enter the chg-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1543 E3840 Cmd Rej: Attributes required
All required attrbutes must be specified in the command.
Recovery
Re-enter the chg-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1544 E3841 Cmd Rej: SRKQ exceed max allowed rtkey limit
The total srkq parameter value cannot exceed 2500 for E5-ENET or E5-ENET-B cards running the SS7IPGW or IPGWI application.
Recovery
2.2.1545 E3842 Cmd Rej: Entries in static route key table cannot exceed SRKQ
For the ent/chg-appl-rtkey commands, a limit of 2500 routing keys exists for SS7IPGW and IPGWI applications running on E5-ENET or E5-ENET-B cards.
For the chg-sg-opts command, the value specified for the srkq parameter must be greater than or equal to the current number of static routing key entries.
Recovery
2.2.1546 E3847 Cmd Rej: FORCE valid only with APPL, DATA or INITCLK parameters
The force parameter can be specified with only the appl, data, or initclk parameter.
Recovery
Re-enter the init-card command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1547 E3848 Cmd Rej: FORCE parameter valid only with DATA parameter
If the force parameter is specified, then the data parameter must be specified
Recovery
Re-enter the init-sys command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1548 E3849 Cmd Rej: Card(s) cannot warm restart - FORCE parameter required
If the data=persist parameter is specified, and if all of the specified cards do not meet the warm restart requirements, then the force parameter must be specified and a full data download may be required. Table 2-6 describes the possible reasons a card may require a full data download:
Table 2-6 Reason that Card Requires a Full Data Download
| xxxxxxxx value | Description |
|---|---|
| POWER ON | Power on reset |
| XILINX VERSION | M256 Xilinx version has changed |
| DB VERSION | LNP Database version has changed |
| DB LEVEL | Database level is not supported or difference exceeds incremental loading capability |
| DB STATUS | Database status is incoherent |
| HW ERR | Hardware error bit checks on the card fail |
| AUDIT FAILED | Checksum comparisons of the LNP database fail |
| AUDIT TIMEOUT | LNP initialization audit timed out |
| NO AUDIT | Unable to perform LNP DB audit. LNP audit not on or excessive number of unknown checksums |
| USER REQUEST | User initiated init-card or init-sys command reload type cold
|
| UNKNOWN | Unknown |
| OTHER | Other |
Recovery
Re-enter the init-card or init-sys command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1549 E3850 Cmd Rej: Parameters inconsistent on re-entering of command
The init-sys command causes a complete system reload and must be entered twice. The command parameters must match for the first and second entries of the command.
Recovery
Re-enter the init-sys command, specifying the same parameters both times.
2.2.1550 E3851 Cmd Rej: MTPRSE parameter is only valid if ITUMTPRS feature is ON
The ITU MTP Restart (ITUMTPRS) feature must be turned on before the mtprse parameter can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1551 E3852 Cmd Rej: Specified APPL/LOC/TYPE not supported with DATA parameter
The data parameter can be specified only for SCCP card locations or GPLs, MPS database (VSCCP) card locations or GPLs, SIP/ENUM/DEIR card locations or GPLs, or GTT-enabled IPSG card locations or GPLs.
For the init-card command, the data parameter is not allowed when the DUAL ExAP Config or EPAP Data Split feature is ON and type=GTT is specified for the VSCCP application. However, the data parameter with type=GTT is allowed if specified for the IPSG application..
Recovery
2.2.1552 E3854 Cmd Rej: NCICS unspecified, NCICE must be greater than or equal CICS
The value specified for the ncice parameter must be greater than or equal to the value entered for the cics parameter, if the ncics parameter is not specified.
Recovery
2.2.1553 E3856 Cmd Rej: Processor timeout error
There was a processor timeout error during the period when this command was entered.
Recovery
Re-enter the chg-sg-opts command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1554 E3857 Cmd Rej: Unexpected response message error
This command generated an unexpected response message.
Recovery
Re-enter the chg-sg-opts command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1555 E3858 Cmd Rej: Host Name Still Referenced in IP Link Table
The value specified for the host parameter must be deleted from the IP Link table before it can be deleted from the IP Host table.
Recovery
2.2.1556 E3860 Cmd Rej: Link not valid for card or application type
Link A can be specified for an E5-ENET or E5-ENET-B card running the SS7IPGW or IPGWI application.
Links A - A7 and B - B7 can be specified for an E5-ENET or E5-ENET-B card running the IPLIM or IPLIMI application.
Links A - A15 and B - B15 can be specified for an E5-ENET or E5-ENET-B card running the IPSG application.
If the value specified for the lhost parameter refers to an IPSG card or a DEIR card running the DEIRHC/DEIR64 GPL, then the link parameter cannot be specified.
Recovery
2.2.1557 E3862 Cmd Rej: SLSOCBIT parameter is only valid for ITU Link Sets
The slsocbit parameter cannot be specified for an ANSI linkset.
Recovery
2.2.1558 E3863 Cmd Rej: SLSOCBIT parameter not permitted if SLSOCB Feature is OFF
The SLSOCB feature must be turned on before the slsocbit parameter can be specified
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1559 E3864 Cmd Rej: SLSRSB parameter is only valid for ITU Link Sets
The slsrsb parameter can be specified only for ITU link sets.
Recovery
2.2.1560 E3865 Cmd Rej: Cannot enter MTPRSE with SLSOCBIT, SLSRSB parameters
The mtprse parameter and the slsocbit and slsrsb parameters cannot be specified in the same command.
Recovery
Re-enter the rtrv-ls command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.1561 E3866 Cmd Rej: Shelf FAN bit must be enabled
For the chg/ent-card command, the Shelf FAN bit must be turned on before E5-ENET-B, E5-APP-B, and SLIC cards can be provisioned.
For the ent/chg-e1 command, the Shelf FAN bit must be turned on before HC-MIM cards that are used as E1 or SE-HSL cards can be used in a system shelf.
For the ent/chg-t1 command, the Shelf FAN bit must be turned on before HC-MIM cards that are used as T1 or ST-HSL-A cards can be used in a system shelf.
For the ent-slk command, the Shelf FAN bit must be turned on before links a16-a63 and b16-b63 can be provisioned. Links a16-a63 and b16-b63 are only applicable for SLIC cards running the IPSG application.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1562 E3867 Cmd Rej: MPC feature must be enabled
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1563 E3870 Cmd Rej: GTT must be ON before VGTT can be ON
The Global Title Translation (GTT ) feature must be turned on before the Variable Length GTT (VGTT) feature can be turned on.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
- Display the status of the GTT feature. Enter the
rtrv-featcommand. - Turn on the GTT feature as necessary. Refer to the Database Administration - GTT User's Guide for assistance.
- Re-enter the
chg-featcommand that generated this error message. - Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1564 E3871 Cmd Rej: ITUTFR parameter is only valid for ITU link sets
The itutfr parameter can be specified only for ITU-N linksets.
Recovery
2.2.1565 E3872 Cmd Rej: FRAMING=ESFPERF not supported
The ST-HSL-A feature must be turned on before the framing=esfperf parameter can be specified.
Recovery
2.2.1566 E3873 Cmd Rej: Card GPL type IPGWI requires a link set with IPGWAPC=YES
If the type=ipgwi parameter is specified, then the value specified for the lsn parameter must indicate a linkset with an IP gateway adjacent point code (the ipgwapc=yes parameter is specified in the ent-ls command).
Recovery
2.2.1567 E3874 Cmd Rej: TUP must use DPC/SI route key if DPC is ANSI
A DPC/SI routing key must be specified when an ANSI DPC is used and the si=4 parameter is specified. TUP is used only in an ITU network.
Recovery
2.2.1568 E3876 Cmd Rej: L2STATS not valid for IPGWI
Output for the l2stats parameter in the rept-stat-slk command is not available for TCP/IP point-to-multipoint links (type DCM cards equipped as IPGWI links).
Recovery
Display the card and application type. Enter the rtrv-card command.
The information is shown in the TYPE and APPL fields of the output.
Contact My Oracle Support if additional assistance is required. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1569 E3877 Cmd Rej: ANSI/ITU point code type mismatch
For the ent/chg-rte command, all linksets in a routeset must have the same network type. The network type of the routeset must be the same as the network type of the destination point code.
For the ent/chg-rtx command, the network domain of the adjacent point code (APC) in the linkset or of the routes in the specified routeset must be the same network domain of the specified destination point code or its alias.
For the chg-dstn command, the network type of the routeset must be the same as the network type of the destination point code.
Recovery
2.2.1570 E3878 Cmd Rej: CIC outside of valid range for SI
For the ent/chg/dlt/rtrv-appl-rtkey commands, the values specified for the cics and cice parameters must be within the valid range.
For the ent-appl-rtkey command, the si=5 parameter must be specified before the cics and cice parameters can be specified.
For the ent/dlt/rtrv-pct commands, the values specified for the ecics/ecice and rcics/rcice parameters must be within the valid range.
Recovery
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. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1571 E3879 Cmd Rej: The MPC feature must be ON before ITUDUPPC can be ON
The Multiple Point Code (MPC) feature must be turned on before the ITUDUPPC feature can be turned on.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1572 E3880 Cmd Rej: Grp Code of dstn & True PC must match if no Secondary PC
If the destination does not use an SPC, then the group code of the destination must be the same as the group code of the ITU national true point code.
If the destination uses an SPC, then the group code of the destination must match the group code of the SPC.
Recovery
2.2.1573 E3881 Cmd Rej: Group Code and/or Spare Point Code of DPC and SPC must match
If an ITU national destination is provisioned, the ITUDUPPC feature is turned on, and the destination uses an SPC, then the group code of the destination must match the group code of the SPC.
For example, if the ITU national true point code has a group code of ee, then destinations with group codes of ee can be added without using an SPC. Destinations with a group code of ff, however, must use an SPC with a group code of ff.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1574 E3883 Cmd Rej: GSM Map Screening feature must be ON
The GSM Map Screening feature must be turned on before the ent/chg-gsmmap-scrn, ent/chg-gsms-opcode, and ent/chg-gsmssn-scrn commands can be entered.
For the chg-mtc-measopts command, the GSM Map Screening feature must be turned on before the mtcdmap=on or mtchmap=on parameter can be specified.
For the chg-sccpopts command, the GSM Map Screening feature must be turned on before the mstcapce parameter can be specified.
For the chg-stpopts command, the GSM Map Screening feature must be turned on before the gsmdflt or gsmsdecerr parameters can be specified.
For the enable-ctrl-feat command, the GSM Map Screening feature must be turned on before the EGMS feature can be enabled.
For the ent/chg-ls commands, the GSM Map Screening feature must be turned on before the gsmscrn parameter can be specified.
For the rept-ftp-meas command, the GSM Map Screening feature must be turned on before the enttype=mapscrn or mtcdmap=on parameter can be specified.
Recovery
2.2.1575 E3884 Cmd Rej: SSN/TYPE combination already exists
The ssn/type parameter combination cannot already exist in the GSM SSN Screening table.
Recovery
2.2.1576 E3885 Cmd Rej: Failure reading the GSM SSN Screening Table
The GSM SSN Screening table must be accessible for the command to execute. A failure occurred in reading the table.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1577 E3886 Cmd Rej: SSN/TYPE combination does not exist
The ssn/type parameter combination must already exist in the GSM SSN Screening table.
Recovery
- Display the entries in the GSM SSN Screening table. Enter the
rtrv-gsmssn-scrncommand. - Re-enter the
dlt-gsmssn-scrncommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1578 E3887 Cmd Rej: OPCODE already exists
The value specified for the opcode parameter cannot already exist in the GSM MAP Op-Code table.
Recovery
- Display the current entries in the GSM MAP Op-Code table. Enter the
rtrv-gsms-opcodecommand. - Re-enter the
ent-gsms-opcodecommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1579 E3888 Cmd Rej: OPNAME already used
The value specified for the opname parameter cannot already exist in the GSM MAP Op-Code table.
Recovery
- Display the current entries in the GSM MAP Op-Code table. Enter the
rtrv-gsms-opcodecommand. - Re-enter the
ent-gsms-opcodecommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1580 E3889 Cmd Rej: Failure reading the GSM OPCODE Table
The GSM MAP Op-Code table must be accessible for the command to execute. A failure occurred in reading the table.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1581 E3890 Cmd Rej: Failure reading the GSM MAP SCRN Table
The GSM MAP screening table must be accessible for the command to execute. A failure occurred in reading the table.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1582 E3892 Cmd Rej: OPNAME does not exist in the database
The value specified for the opname parameter must already exist in the GSM MAP Op-Code table.
Recovery
- Display the current entries in the GSM Map Op-Code table. Enter the
rtrv-gsms-opcodecommand. - Re-enter the command that generated this error message, specifying a valid combination of values. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1583 E3893 Cmd Rej: Entry being deleted is referenced by a GSM Map Screen entry
An entry that is referenced in the GSM MAP screening table cannot be deleted.
Recovery
2.2.1584 E3894 Cmd Rej: SADDR and EADDR must have the same number of digits
The saddr and eaddr parameters must contain the same number of digits.
Recovery
- Display the current values for the saddr parameter if applicable. Enter the
rtrv-gsmmap-scrncommand. - Re-enter the
ent/rtrv-gsmmap-scrncommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1585 E3895 Cmd Rej: EADDR must be greater than SADDR
The value specified for the eaddr parameter must be greater than the value specified for the saddr parameter.
Recovery
- Display the current values for the saddr parameter, if applicable. Enter the
rtrv-gsmmap-scrncommand. - Re-enter the
ent/rtrv-gsmmap-scrncommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1586 E3897 Cmd Rej: GSM MAP SCRN entry already exists or overlaps another entry
If a single entry is specified for the CgPA or CdPA (the eaddr parameter is not specified), then the combination of saddr, npv, and naiv values for the specified opname must not already exist in the GSM MAP Screening Table.
If a range entry is specified for the CgPA or CdPA (the eaddr parameter is specified), the combination of saddr, eaddr, npv, and naiv for the specified opname must not already exist or overlap with another range entry in the GSM MAP Screening Table.
Recovery
2.2.1587 E3898 Cmd Rej: EADDR cannot be specified without SADDR
If the eaddr parameter is specified, then the saddr parameter must be specified.
Recovery
Re-enter the ent/rtrv-gsmssn-scrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1588 E3900 Cmd Rej: GSM Map Screening feature must be enabled
The GSM MAP Screening feature must be enabled before the command can be entered.
Recovery
2.2.1589 E3901 Cmd Rej: CGPA entry is referred by CDPA entries
All CdPA entries that are assigned to the CdPA entry must be deleted before the CgPA entry can be deleted.
Recovery
2.2.1590 E3902 Cmd Rej: FORBID cannot be STATE or LOCATION for the given OPNAME
Recovery
2.2.1591 E3903 Cmd Rej: Screening action can not be ATIERR for the given OPNAME
The operation code referenced by the specified opname parameter must have a value of 71 before the (n)action=atierr parameter can be specified.
Recovery
2.2.1592 E3904 Cmd Rej: DFLTACT cannot be ATIERR unless OPCODE=71
The opcode=71 parameter must be specified before the (n)dfltact parameter can be specified.
Recovery
2.2.1593 E3905 Cmd Rej: CGSR doesn’t exist for specified OPNAME
The value specified for the cgsr parameter must already exist in the database.
Recovery
2.2.1594 E3906 Cmd Rej: The GSM Map Screening table is full
The GSM MAP Screening table can contain a maximum of 4000 entries.
Recovery
2.2.1595 E3908 Cmd Rej: Invalid OAM HW config or an HMUX card is out of service
Invalid hardware configuration alarms are set or an HMUX alarm must be addressed.
Recovery
- Verify that all HMUX cards are in service. Enter the
rept-stat-cardcommand. - Follow the recovery procedure in the upgrade procedure documentation, or contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1596 E3909 Cmd Rej: XLIST Point codes may not be permanently inhibited
The inh-alm command cannot be used to permanently inhibit XLIST point codes.
Recovery
2.2.1597 E3910 Cmd Rej: Translation TYPEN24 specified does not exist
The value specified for the typen24 parameter must already exist in the Translation Type table.
Recovery
2.2.1598 E3911 Cmd Rej: Either PLNP or WNP Features must be ON
The Personal Communication Service 1900 Local Number Portability (PLNP) feature or the Wireless LNP (WNP) feature must be turned on before the wqredrct parameter can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1599 E3921 Cmd Rej: ITU National Point Code must be full point code
ANSI point code value 000-000-000 and ITU-International point code value 0-000-0 are not allowed.
The ITU-National point code must be a full point code. A full point code is specified with a numerical value for the nnnnn segment of the point code.
If the ITUDUPPC (ITU national duplicate point code) feature is on, then the ITU national point code will also contain a group code. The group code is a two-character field from aa to zz that is entered as the last subfield of an ITU-N point code, nnnnn-gc (for example, 2112-aa).
Note:
Once a feature this is controlled using a feature bit has been turned on, it cannot be turned off.A flexible point code format can be assigned with the chg-stpopts:npcfmti parameter. Refer to the command description for the chg-stpopts command in Commands User's Guide for assistance.
An asterisk (*) cannot be used to enter or change ITU national point codes. The asterisk is allowed only for retrieving ITU national point codes.
Recovery
2.2.1600 E3922 Cmd Rej: GTT must be ON before INP/AINPQ can be ON
The GTT feature must be turned on before the INP or AINPQ feature can be turned on.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1601 E3925 Cmd Rej: HOMERN table is full
The HOMERN table can contain a maximum of 100 entries.
Recovery
2.2.1602 E3926 Cmd Rej: Failed reading HOMERN table
The HOMERN table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1603 E3928 Cmd Rej: STP True PC and INP Subsystem does not exist in MAP Table
The STP true point code and the INP subsystem number must already be defined in the mated applications (MAP) table before the INP application can be specified.
Recovery
2.2.1604 E3929 Cmd Rej: LNP/INP/EIR/VFLEX must be ON or ATINP/AIQ must be enabled
Note:
Before the LNP feature can be turned on, or before the quantity of LNP telephone numbers can be increased, DSM/VSCCP cards and a sufficient amount of memory must be configured in the EAGLE.Recovery
2.2.1605 E3930 Cmd Rej: RN already exists in HOMERN table
The value specified for the rn parameter cannot already exist in the HOMERN table. .
Recovery
2.2.1606 E3931 Cmd Rej: RN does not exist in HOMERN table
The specified routing number must already exist in the HOMERN table.
Recovery
2.2.1607 E3934 Cmd Rej: CPCx must not be ANSI if CPCTYPE is INP
If an ANSI point code is used, then a value of inp cannot be specified for the cpctype parameter.
Recovery
2.2.1608 E3935 Cmd Rej: DRANP and DRANPV must not be specified together
The dranp and dranpv parameters cannot be specified together in the command.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.1609 E3936 Cmd Rej: DRANAI and DRANAIV must not be specified together
The dranai and dranaiv parameters cannot be specified together in the command.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.1610 E3937 Cmd Rej: Entry already exists with specified GTI-TT-NP(V)-NAI(V)-SSN
The specified entry cannot match an existing gti, tt, nai(v), np(v), and ssn parameter combination.
Recovery
2.2.1611 E3938 Cmd Rej: Entry does not exist with specified GTI-TT-NP(V)-NAI(V)-SSN
An entry must already exist that matches the gti/gtii/gtin/stin24, tt, ssn, np(v), and nai(v) combination of parameters.
Recovery
2.2.1612 E3939 Cmd Rej: (N)SNP must be E164 when (N)SERV=INPMR
If a value of inpmr, smsmr, or gport is specified for the nserv parameter, then the nsnp=E164 parameter must be specified.
Recovery
Re-enter the ent/chg/rtrv-srvsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the appropriate feature manual for assistance.
2.2.1613 E3940 Cmd Rej: (N)SERV value is invalid for the specified (N)SNAI
If a value of rnidn, rnndn, or rnsdn is specified for the nsnai/snai parameter, then a value of inpmr, gport, or smsmr must be specified for the nserv/serv parameter.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the appropriate feature manual for assistance.
2.2.1614 E3941 Cmd Rej: GTII must not be specified when (N)SERV = INPQ
If the nserv/serv=inpq parameter is specified then the gtii parameter cannot be specified.
Recovery
Re-enter the ent/chg/rtrv-srvsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the appropriate feature manual for assistance.
2.2.1615 E3942 Cmd Rej: GTI/GTIA is invalid for specified (N)SERV
If a value of inpmr, inpq, gport, or eir is specified for the (n)serv parameter, then the gtia and gti parameters cannot be specified.
If the MO-based IS41 SMS NP, MO-based GSM SMS NP, or MO SMS IS41-to-GSM Migration feature is enabled, and the (n)serv=smsmr parameter is specified, then the gtia and gti parameters can be specified.
Recovery
2.2.1616 E3943 Cmd Rej: SNP/SNAI mustn't be specified for requested service
If a value of aiq, atinp, eir, idpr, inpq, ttr, or vflex is specified for the (n)serv parameter, then the (n)snai and (n)snp parameters cannot be specified.
Recovery
Re-enter the ent/chg/rtrv-srvsel command that generated this error message, specifying a valid combination of parameters. Refer to the Commands User's Guide and to the appropriate feature manual for assistance.
2.2.1617 E3944 Cmd Rej: SNAI & SNP must be specified for requested service
If a value of gflex, gport, inpmr, or smsmr is specified for the nserv/serv parameter, then the nsnai/snai and nsnp/snp parameters must be specified.
Recovery
Re-enter the ent/chg-srvsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the appropriate feature manual for assistance.
2.2.1618 E3945 Cmd Rej: SERV must not be GFLEX when SNAI = RNIDN/RNNDN/RNSDN
If a value of rnidn, rnndn, or rnsdn is specified for the snai paramether, then the serv=gflex parameter cannot be specified.
Recovery
Re-enter the rtrv-srvsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.1619 E3946 Cmd Rej: Entry already exists with specified GTII-TT-NP(V)-NAI(V)-SSN
An entry cannot match an existing gti/gtii/gtin/gtin24, tt, np(v), nai(v) and ssn parameter combination.
Recovery
- Display the existing entries. Enter the
rtrv-srvselcommand. - Re-enter the
ent-srvselcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1620 E3947 Cmd Rej: Entry already exists with specified GTIN-TT-NP(V)-NAI(V)-SSN
The entry cannot match an existing gti/gtii/gtin/gtin24, tt, np(v), nai(v), and ssn parameter combination.
Recovery
- Display the existing entries Enter the
rtrv-srvselcommand. - Re-enter the
ent-srvselcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1621 E3948 Cmd Rej: Entry does not exist with specified GTII-TT-NP(V)-NAI(V)-SSN
The entry specified by the gtii, tt, np(v), nai(v), and ssn parameter combination must already exist.
Recovery
- Display the existing entries. Enter the
rtrv-srvselcommand. - Re-enter the
chg/dlt-srvselcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the appropriate feature manual for assistance.
2.2.1622 E3949 Cmd Rej: Specified card cannot be the Active MASP
The card address specified by the loc/sloc/eloc parameter cannot be for the Active MASP
Recovery
Re-enter the command specifying a card address that is not the Active MASP.
2.2.1623 E3950 Cmd Rej: Standby MASP is inhibited
The database cannot be updated because the standby MASP is inhibited.
The standby MASP must be in the Active state before thechg-db command can be entered.
Recovery
2.2.1624 E3951 Cmd Rej: Entry does not exist with specified GTIN-TT-NP(V)-NAI(V)-SSN
The specified entry must match an existing gtin, tt, np(v), nai(v), and ssn parameter combination.
Recovery
- Display the existing entries. Enter the
rtrv-srvselcommand. - Re-enter the
chg/dlt-srvselcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the appropriate feature manual for assistance.
2.2.1625 E3953 Cmd Rej: NSNAI and NSNP must be specified when NSERV = GFLEX
If the nserv=gflex parameter is specified, then the nsnai and nsnp parameters must be specified.
Recovery
Re-enter the chg-srvsel command tht generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the G-Flex C7 Relay User's Guide for assistance.
2.2.1626 E3954 Cmd Rej: NSNAI must be specified when NSERV = INPMR
If the nserv=inpmr parameter is specified, then the nsnai parameter must be specified.
Recovery
Re-enter the chg-srvsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the INP/AINPQ User's Guide for assistance.
2.2.1627 E3955 Cmd Rej: Invalid combination of parameters for a partial routing key
The specified parameters must define a full or partial routing key.
Recovery
Re-enter the ent/chg/dlt/rtrv-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1628 E3957 Cmd Rej: When type=partial or default, specify attributes
If a value of partial or default is specified for the type parameter, then the rcontext parameter must be specified.
Recovery
Re-enter the chg-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1629 E3958 Cmd Rej: When type=partial or default, SPLIT/RESIZE are not supported
If a value of partial or default is specified for the type parameter, then the split parameter cannot be specified.
Recovery
Re-enter the chg-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1630 E3959 Cmd Rej: Invalid combination of parameters for a default routing key
If the type=default parameter is specified, then the dpc, si, ssn, opc, cics, and cice parameters cannot be specified.
Recovery
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.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1631 E3961 Cmd Rej: PVN and PVNMASK must be specified together
The pvn and pvnmask parameters must be specified together in the command.
Recovery
Re-enter the chg-netopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - Features User's Guide for assistance.
2.2.1632 E3962 Cmd Rej: PVN and PVNMASK must not be the same
The same value cannot be specified for the pvn and pvnmask parameters.
Recovery
- Display the current PVN and PVNMASK IP addresses in the system. Enter the
rtrv-netoptscommand. - Re-enter the
chg-netoptscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1633 E3964 Cmd Rej: TSCSYNC must be ON before E5IS can be ON
The Time Slot Counter Synchronization (TSCSYNC) feature must be turned on before the EAGLE 5 Integrated Monitoring Support feature (E5IS) feature can be turned on.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1634 E3965 Cmd Rej: Invalid PVN
chg-netopts command:
- The pvn=0 parameter cannot be specified.
- The value specified for the pvn parameter must be a valid Class B network IP address.
- The host portion of the value specified for the pvn parameter must be 0.0.0.0 based on the value specified for the pvnmask parameter.
For the chg-eisopts command, the host portion of the PVN network address must be 0 based on the PVN subnet mask (see the chg-netopts command) before the eiscopy=on parameter can be specified.
Recovery - chg-netopts
Re-enter the chg-netopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - chg-eisopts
2.2.1635 E3966 Cmd Rej: Max number of STC cards per shelf is entered
If the shelf contains HMUX cards in slots 9 and 10, then a maximum of 3 STC cards can be provisioned on the shelf. If HIPR or HIPR2 cards are installed in slots 9 and 10, then the additional STCs can be provisioned.
Recovery
2.2.1636 E3967 Cmd Rej: E5IS must be ON
The EAGLE 5 Integrated Monitoring Support (E5IS) feature must be turned on before this command can be entered.
Note:
Once a feature that is controlled using a feature bit is turned on, it cannot be turned off.Recovery
2.2.1637 E3968 Cmd Rej: Invalid hardware for EISCOPY to be ON
At least 2 STC cards in the IS-NR state must be installed on at least one shelf of the system before the copy function for the EAGLE 5 Integrated Monitoring Support feature can be enabled.
Recovery
2.2.1638 E3979 Cmd Rej: Read NETOPTS table failed
The NETOPTS table is corrupt or cannot be found.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1639 E3989 Cmd Rej: GPORT feature must be ON when (N)SERV=GPORT
The G-Port feature must be turned on before the nserv/serv=gport parameter can be specified.
Recovery
2.2.1640 E3990 Cmd Rej: (N)SNP must be E164 when (N)SERV=GPORT/SMSMR
If a value of gport or smsmr is specified for the (n)serv parameter, then the (n)snp=e164 parameter must be specified.
Recovery
Re-enter the ent/chg-srvsel or ent/chg-gttact command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1641 E3991 Cmd Rej: GPORT feature must be ON
For the chg-ctrl-feat command, the G-Port feature must be turned on before the MO-based GSM SMS NP or MT-Based GSM SMS NP feature can be turned on.
For the chg-gsmopts command, the G-Port feature must be turned on before the migrpfx=multiple parameter can be specified.
For the enable-ctrl-feat command, the G-Port feature must be turned on before the GSM MAP SRI Redirect for Serving HLR, ISUP NP with EPAP, MNP CRP, or PPSMS features can be enabled
For the ent/chg-gttact command, the G-Port feature must be turned on before the GPORT service is entered with the SRVCNAME parameter.
For the rtrv-gserv-data command, the G-Port feature must be turned on before this command can be entered.
Recovery
2.2.1642 E3992 Cmd Rej: SRFADDR, SRFNAI & SRFNP parameters must be entered together
The srfaddr, srfnai, and srfnp parameters must be specified together in the command.
Recovery
Re-enter the chg-gsmopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the G-Port User's Guide for assistance.
2.2.1643 E3994 Cmd Rej: (N)SERV must be GPORT/SMSMR when (N)SNAI=CCRNDN
If the nsnai=ccmdn parameter is specified, then a value of gport or smsmr must be specified for the nserv parameter.
Recovery
Re-enter the ent/chg/rtrv-srvsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the G-Port User's Guide for assistance.
2.2.1644 E3995 Cmd Rej: MSRNNAI and MSRNNP parameters must be entered together
The msrnnai and msrnnp parameters must be specified together in the command.
Recovery
Re-enter the chg-gsmopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the G-Port User's Guide for assistance.
2.2.1645 E3997 Cmd Rej: GFLEX must be ON or GPORT/EIR/IGM/VFLEX/MO SMS feat enabled
The G-Flex feature must be turned on or the EIR, G-Port, IGM, MO SMS ASD, MO SMS B-Party Routing, MO SMS GRN, MO SMS IS41-to-GSM Migration, MO-based GSM SMS NP, Prepaid SMS Intercept Ph1, or V-Flex feature must be enabled before the rtrv-gsmopts command can be entered.
Recovery
2.2.1646 E3998 Cmd Rej: NSNAI must not be NONE for requested service
A value of atinp, eir, idpr, idps, inpq,ttr, or vflex must be specified for the nserv parameter before the nsnai=none parameter can be specified.
Recovery
Re-enter the chg-srvsel command that generated this error message, specifying a valid combination of parameters. Refer to the Commands User's Guide and to the G-Port User's Guide for assistance.
2.2.1647 E3999 Cmd Rej: When type=full, DPC and SI must be specified
If the type=full parameter is specified, then the dpc or si parameter must be specified.
Recovery
Re-enter the ent/chg/dlt-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1648 E4000 Cmd Rej: No data is available to display.
Audit data is available only if the execution of a periodic or manual DDB audit is complete.
Recovery
Use the aud-data command to start a manual DDB audit or wait for periodic DDB audit start. Refer to the command description in Commands User's Guide for more information.
Re-enter the rept-stat-ddb command that generated this error message.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1649 E4001 Cmd Rej: Group Code of DPCN and OPCN must match
The group codes for the dpcn and opcn parameter values must match.
Recovery
Re-enter the ent-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1650 E4003 Cmd Rej: MULTGC=YES requires IPSG-M2PA, IPGWI, or IPLIMI links
For the chg-ls and ent-slk commands, if the multgc=yes parameter is specified (see the ent/chg-ls command), then all links assigned to the linkset must be of the same type.
For the chg-ls command, if the multgc=yes parameter is specified, then an IPGWI or IPLIMI link must be specified.
Recovery
2.2.1651 E4005 Cmd Rej: Either INP/AINPQ/GPORT must be ON or TINP must be enabled
For the chg-measopts command, the INP or G-Port feature must be turned on before the enttype=np:type=mtch parameter can be specified. The INP, AINPQ, G-Port, A-Port, or IGM feature must be turned on before the mtchnp=on or mtcdnp=on parameter can be specified.
The INP or G-Port feature must be turned on before the ent/dlt/rtrv-homern commands can be specified.
For the rept-ftp-meas command, the INP, AINPQ, G-Port, A-Port or IGM feature must be turned on before the mtchnp=on, mtcdnp=on, or enttype=np parameter can be specified.
For the rept-meas command, the INP, AINPQ, G-Port, A-Port, or IGM feature must be turned on before the entity=np parameter can be specified.
Recovery
2.2.1652 E4007 Cmd Rej: Exceeding max GTA Lengths supported per TT
If the VGTT feature is turned on, then up to 10 GTA lengths can exist per translation type. If the Support for 16 GTT Lengths in VGTT feature is turned on, then up to 16 GTA lengths can exist per translation type.
Note:
Once a feature that is controlled using a feature bit has been turned on it cannot be turned off.Recovery
2.2.1653 E4008 Cmd Rej: Exceeding max GTA/SADDR Lengths supported per GTTSET
If the VGTT feature is turned on, then up to 10 GTA/SADDR lengths can exist per GTT set. If the Support for 16 GTT Lengths in VGTT feature is turned on, then up to 16 GTA/SADDR lengths can exist per GTT set.
Note:
Once a feature that is controlled using a feature bit has been turned on it cannot be turned off.Recovery
2.2.1654 E4009 Cmd Rej: GTA Length is not defined for TT
The specified GTA length must already be defined for the specified translation type.
Recovery
2.2.1655 E4011 Cmd Rej: NDGT Parameter is invalid for VGTT
If the Variable Length GTT (VGTT) feature is turned on, then the ndgt parameter cannot be specified.
Note:
Once a feature that is controlled with a feature bit has been turned on, it cannot be turned off.Recovery
- Display the status of the VGTT feature. Enter the
rtrv-featcommand. - 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 and to the Database Administration - GTT User's Guide for assistance.
2.2.1656 E4012 Cmd Rej: Invalid PVNMASK
The value specified for the pvnmask parameter must be a valid subnet IP address. Refer to the command description in Commands User's Guide for a list of values.
Recovery
Re-enter the chg-netopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1657 E4013 Cmd Rej: T1 Port test command not in progress
There is no active test in progress on the specified T1 port.
Recovery
No action required.
2.2.1658 E4014 Cmd Rej: CGSR must be specified when CDSR is specified
If the cdsr parameter is specified, then the cgsr parameter must be specified.
Recovery
Re-enter the rtrv-gsmmap-scrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1659 E4015 Cmd Rej: CGSR or CDSR shouldn't be specified when SADDR is specified
If the saddr parameter is specified, then the cgsr and cdsr parameters cannot be specified.
Recovery
Re-enter the rtrv-gsmmap-scrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1660 E4016 Cmd Rej: SADDR, NPV and NAIV must be specified together
The saddr, npv, and naiv parameters must be specified together in the command.
Recovery
Re-enter the rtrv-gsmmap-scrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1661 E4017 Cmd Rej: ACTION or FORBID parameter shouldn't be specified
If the saddr, eaddr, npv, naiv, or cdsr parameter is specified, then the forbid and action parameters cannot be specified.
Recovery
Re-enter the rtrv-gsmmap-scrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1662 E4019 Cmd Rej: OPCODE and OPNAME shouldn't be specified together
The opcode and opname parameters cannot be specified together in the command.
Recovery
Re-enter the rtrv-gsms-opcode command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1663 E4024 Cmd Rej: SRCSET and SET cannot be equal
The same value cannot be specified for the set and srcset parameters.
Recovery
Re-enter the chg-uaps command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1664 E4027 Cmd Rej: S/ESHELF parameters are invalid with specified report type
A value of hmuxerr, hiprerr, or hipr2err must be specified for the report parameter before the sshelf and eshelf parameters can be specified.
Recovery
Re-enter the rept-imt-info command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.1665 E4029 Cmd Rej: BOOT parameter is not valid with the specified card
The boot parameter can be specified only if the target is an E5-class card.
Recovery
Re-enter the
init-flash command that generated this
error message without specifying the
boot parameter.
For MUX
(HIPR, HIPR2) cards, the
init-flash command cannot boot the
card. To boot the card, enter the
init-mux command after the
init-flash command.
Refer to the command descriptions in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1666 E4032 Cmd Rej: Either BUS or Location (not both) must be specified
The bus or loc parameter must be specified in the command. The parameters cannot be specified together in the command.
Recovery
Re-enter the init-mux command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1667 E4033 Cmd Rej: If GTIXLAT is 22, NAI and NP cannot be specified
If the gtixlat=22 parameter is specified, then the nai and np parameters cannot be specified.
Recovery
Re-enter the ent-gtcnv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1668 E4034 Cmd Rej: If GTIXLAT is 24, NAI and NP must be specified
If the gtixlat=24 parameter is specified, then the nai and np parameters must be specified.
Recovery
Re-enter the ent-gtcnv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1669 E4035 Cmd Rej: TTA must be specified for a direction of ATOI
If the dir=atoi parameter is specified, then the tta parameter must be specified.
Recovery
Re-enter the chg-gtcnv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1670 E4036 Cmd Rej: At least TTA, TTI must be specified for a direction of BOTH
If the dir=both parameter is specified, then the tta and tti parameters must be specified.
Recovery
Re-enter the chg/dlt-gtcnv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1671 E4037 Cmd Rej: Error in FEATCTRL.TBL database, maintenance required
The Feature Control database (FEATCTRL.TBL) is corrupt. Database maintenance is required.
Recovery
Contact My Oracle Support if this error message appears again for the enable-ctrl-feat command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1672 E4039 Cmd Rej: MULTGC=YES not allowed if ITUDUPPC feature is OFF
The International National Duplicate Point Code (ITUDUPPC) feature must be turned on before the multgc=yes parameter can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1673 E4044 Cmd Rej: Only two E1/T1 ports allowed for Linkclass=Unchan
For the ent-e1 command, only 2 ports can be used for E1 interfaces on an HC-MIM card that is used as an SE-HSL card.
For the ent-t1 command, only 2 of the 8 ports can be used for T1 interfaces on an HC-MIM card that is used as an ST-HSL-A card.
Recovery
2.2.1674 E4045 Cmd Rej: Linkset with MULTGC=YES requires IPGWI/IPLIMI/IPSG GPL
If the value specified for the lsn parameter references a linkset that specifies multgc=yes, then the card application must be IPGWI, IPSG, or IPLIMI.
Recovery
2.2.1675 E4046 Cmd Rej: E1 is assigned to card
Before an E1 card can be deleted, any E1 interfaces assigned to the card must be deleted.
Recovery
2.2.1676 E4047 Cmd Rej: Signaling link is not provisioned for the card
At least one signaling link must be associated with a 2-port E1 card or Channel card or an E1/T1 MIM card used as an E1 card, T1 card, or Channel card (card type LIME1, LIMT1, or LIMCH) before the card can be allowed.
Recovery
2.2.1677 E4048 Cmd Rej: All signaling links serviced by the E1 must be deactivated
For the chg-e1 command, if the value specified for the loc parameter indicates an E1 card, then all signaling links that are serviced by the card must be deactivated before the values for the crc4, cas, encode, and e1tsel parameters can be changed.
All signaling links that provide timeslots serviced by E1 interfaces on the card specified by the loc parameter must be deactivated before the tst-e1 command can be entered. None of the signaling links can be running link diagnostic tests (tst-slk and act-cdl) when this command is entered.
For the inh-card command, if the card is type LIME1, all signaling links providing timeslots serviced by the E1 interfaces assigned to the card must be deactivated before this command can be entered unless the force=yes parameter is specified.
Recovery
2.2.1678 E4051 Cmd Rej: TS value on the E1 already in use by a signaling link
The value specified for the ts parameter cannot already be in use by the E1 card.
Recovery
2.2.1679 E4054 Cmd Rej: The E1PORT at the specified location is already equipped
An E1 interface cannot be added to the database if the E1 port on the E1 card already has an E1 interface defined in the specified location.
Recovery
2.2.1680 E4055 Cmd Rej: The E1PORT at the specified location is not equipped
An E1 interface must already be defined on the port specified by the e1port parameter before the chg/dlt/rtrv-e1 command can be entered.
For the ent-slk command, an E1 interface must be defined for the card at the location specified by the loc parameter before a signaling link can be assigned to the port.
Recovery
2.2.1681 E4057 Cmd Rej: All signaling links serviced by this E1/T1 must be deleted
All signaling links that are serviced by the E1 or T1 interface must be deleted before the interface can be deleted.
Recovery
2.2.1682 E4059 Cmd Rej: Failed reading the E1/T1 table
The E1/T1 table is corrupt or cannot be found.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1683 E4060 Cmd Rej: MULTGC=YES requires ITU-N or ITU-I point code
If the multgc=yes parameter is specified, then an ITU-N or ITU-I point code must be specified.
Recovery
Re-enter the ent/chg-ls command that generated this error emssage, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1684 E4061 Cmd Rej: Group Code of DPC(s) and APC/SAPC must match when MULTGC=NO
The group codes for the DPC(s) and APC/SAPC must match if the multgc=no parameter is specified.
The multgc=no parameter can be specified only if there are no routes with group codes different than the ADJPC's group code.
If the ADJPC's group code is changed, then the multgc=yes parameter must be specified or there must be no routes using the linkset.
Recovery
2.2.1685 E4062 Cmd Rej: Inhibit IPSM card(s) before changing feature status
All type IPSM cards in the system must be inhibited before the EAGLE OA&M IP Security Enhancements feature can be turned on or off.
Recovery
Inihibit all IPSM cards as necessary and then re-enter the chg-ctrl-feat command to turn the EAGLE OA&M IP Security Enhancements feature on or off. Refer to the Database Administration - System Management User's Guide for assistance.
2.2.1686 E4063 Cmd Rej: GTI/GTIA/GTII/GTIN not within specified range of 1 to 4
The value specified for the gti/gtia/gtii/gtin parameter must be within a valid range. Refer to the command description in Commands User's Guide for valid ranges.
Recovery
Re-enter the command that generated this error message, specifying a valid combination of parameters.
2.2.1687 E4064 Cmd Rej: Host Name Referenced by Application Socket or Association
Before a local entry can be deleted from the IP Host table, all association references to the host name must be deleted. This rule does not apply to remote host entries.
Recovery
2.2.1688 E4065 Cmd Rej: Application Sockets on Port B Not Allowed
A link cannot be assigned to Port B if an association is assigned to the port.
Recovery
2.2.1689 E4066 Cmd Rej: Matching routing key already entered for AS
The specified AS name parameter and routing key cannot already exist in the Routing Key table.
Recovery
2.2.1690 E4067 Cmd Rej: Invalid combination of parameters for a default routing key
If the type=default parameter is specified, then the asname and rcontext parameters are the only optional parameters that can be specified.
Recovery
Re-enter the ent-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1691 E4068 Cmd Rej: Must specify ASNAME
If the dev=as parameter is specified, then the asname parameter must be specified.
Recovery
Re-enter the inh/unhb-alm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.1692 E4069 Cmd Rej: Entry exists with specified GTIN24-TT-NP(V)-NAI(V)-SSN
The specified entry cannot match an existing gti/gtii/gtin/gtin24, tt, ssn, np(v) and nai(v) parameter combination.
Recovery
- Display the existing values for the parameters. Enter the
rtrv-srvselcommand. - Re-enter the
ent-srvselcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to G-Port User's Guide for assistance.
2.2.1693 E4070 Cmd Rej: LNP is mutually exclusive with an existing feature
For the chg-ctrl-feat command, the INP and AINPQ features cannot be turned on if the LNP (an LNP ported TNs quantity), LNP 150,000 LRNs, or LNP 300,000 NPANXX feature is enabled and on.
For the enable-ctrl-feat command, the LNP (an LNP ported TNs quantity), LNP 150,000 LRNs, or LNP 300,000 NPANXX feature cannot be enabled if the INP or AINPQ feature is turned on or if certain features are enabled. See the command description for the enable-ctrl-feat command in the Commands User's Guide for a list of features that are mutually exclusive with LNP.
Recovery
Display the status of controlled features in the system. Enter the rtrv-ctrl-feat command.
If the feature does not appear in the output, then the feature is not enabled. If the feaure has a status of OFF, then the feature is enabled but is not turned on.
If any of the mutually exclusive features are enabled or enabled and turned on, then the LNP (an LNP ported TN quantity), LNP 150,000 LRN, or LNP 300,000 NPANXX feature cannot be used. Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1694 E4071 Cmd Rej: VFLEX cannot be turned ON if STPOPTS DefCC/DefNDC is NONE
The defcc and defndc system options must be provisioned before the V-Flex feature can be turned on.
Recovery
2.2.1695 E4073 Cmd Rej: AS/socket cannot be deleted while assigned to a routing key
Any association between the application server (AS) and the routing key must be deleted before the AS association can be deleted.
Recovery
2.2.1696 E4074 Cmd Rej: Could not locate adapter type
The adapter type specified was not recognized.
Recovery
Re-enter the command that generated this error message, specifying a valid adapter type. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1697 E4075 Cmd Rej: Invalid name for adapter type
A value of m2pa, m3ua, or sua must be specified for the adapter parameter.
Recovery
2.2.1698 E4076 Cmd Rej: E1 card location is unequipped
For the ent/chg/dlt/rtrv-e1 command, the card in the location specified by the loc parameter must be equipped (defined in the database).
For the ent-slk command, the card location specified by the e1loc parameter must contain an HC-MIM, E5-E1T1, or E5-E1T1-B card that is used as an E1 card.
Recovery
2.2.1699 E4077 Cmd Rej: Parameters incompatible with adapter type
If an IPSG-M3UA signaling link is used, then the alw/inh/tst/unhb-slk commands cannot be entered.
For the tst-slk command, if an IPSG-M2PA signaling link is used, then the loopback=sltc parameter must be specified.
For the ent-assoc command, if the card is running the IPLIM or IPLIMI application, then the lhost parameter can only have an association with an adapter value of m2pa.
Recovery
2.2.1700 E4078 Cmd Rej: Conflicting parameters specified
If the rcontext parameter is specified, then the split, ncics, and ncice parameters cannot be specified.
Recovery
Re-enter the chg-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1701 E4079 Cmd Rej: Specified AS name not found
The value specified for the asname parameter must already exist in the AS table.
Recovery
- Display the entries in the AS table. Enter the
rtrv-ascommand. - 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.
2.2.1702 E4080 Cmd Rej: INP/AINPQ, GPORT, APORT or VFLEX feature must be ON
The A-Port, AINPQ, G-Port, INP, or V-Flex feature must be turned on before this command can be entered.
Recovery
2.2.1703 E4081 Cmd Rej: Maximum number of connections already provisioned for AS
A maximum of 16 associations (M3UA/SUA/M2PA IP connections) can be provisioned for an application server (AS).
Recovery
2.2.1704 E4083 Cmd Rej: Connection adapter type does not match AS adapter type
All M3UA/SUA associations added to the Application Server (AS) must have the same adapter type.
Recovery
2.2.1705 E4084 Cmd Rej: Cannot set DefCC/DefNDC to NONE, if VFLEX feature is ON
The defcc or defndc parameters cannot be set to NONE if the VFLEX feature is ON.
Recovery
Re-enter the chg-stpopts 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1706 E4087 Cmd Rej: Both NPV and NAIV must be either * or numbers
The values specified for the npv and naiv parameters must both be either * (wildcards) or numbers.
Recovery
Re-enter the ent-gsmmap-scrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1707 E4089 Cmd Rej: Unable to change adapter when assigned to an AS
The adapter value for an association cannot be changed if the association is assigned to an application server (AS).
Recovery
2.2.1708 E4090 Cmd Rej: Open associations cannot have same lhost/lport
No two open associations can have the same value for the LHOST/LPORT parameters.
Recovery
- Use the
rtrv-assoccommand to see all the configured associations. - Re-enter the
chg-assoccommand to update an association with unique LHOST/LPORT values.
Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1709 E4091 Cmd Rej: Association connection parameters must be unique
The values specified for the lhost, rhost, lport, and rport parameters cannot already exist.
Recovery
2.2.1710 E4092 Cmd Rej: Too many associations per SLK
A maxiumum of 1 association per signalling link can be assigned for an IPLIMx card.
Recovery
2.2.1711 E4093 Cmd Rej: Too many associations per card
A maximum of 32 associations can be provisioned on an E5-ENET/E5-ENET-B card running the IPSG application or a DEIR card running the DEIRHC application.
A maximum of 128 associations can be provisioned on a SLIC card running the IPSG application.
Recovery
2.2.1712 E4094 Cmd Rej: IPSM card has Critical Thermal Alarm
For the alw-trm command, if a critical thermal alarm is raised against the type IPSM card hosting the terminal, then the specified Telnet terminal cannot be returned to the IS-NR state.
For the chg-ctrl-feat command, at least one terminal without a thermal alarm must exist before the SEAS Over IP feature can be turned on.
Recovery
Re-enter the command that generated this error message after the card's thermal temperature subsides below the thermal level, and the IPSM thermal alarm clears.
Contact My Oracle Support for assistance, if necessary. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1713 E4095 Cmd Rej: Failed reading Call Decision table
The Call Decision table is corrupt or cannot be found.
Recovery
Re-enter the command that generated this error message.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1714 E4096 Cmd Rej: Association name already exists
The association name cannot already exist in the IPAPSOCK table.
Recovery
- Display the existing association names in the IPAPSOCK table. Enter the
rtrv-assoccommand. - Re-enter the
ent-assoccommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1715 E4097 Cmd Rej: Cannot assign LHOST/ALHOST to the interface
In order to support all 4 IP ports on SLIC IPSG card for signaling, the provisioning rules allows the following configurations:
- Port A and C can be used as primary hosts: lhost.
- Port B and D can be used on alhost.
Recovery
2.2.1716 E4098 Cmd Rej: OPEN must be NO to change an Association or its AS/Rtkey
For the chg/dlt-assoc command, the connection state of an association must be open=no before the characteristics of an association can be changed or the association can be deleted.
For the ent/chg/dlt-as command, the connection state of the associations bound to the M3UA/SUA associations for an application server (AS) must be open=no before the AS can be entered, changed, or deleted.
Recovery - chg/dlt-assoc
- Display the associations and their connection states. Enter the
rtrv-assoccommand. - Change the connection state for the specified association to open=no as necessary. Refer to the Database Administration - IP7 User's Guide for assistance.
- Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - ent/chg/dlt-as
2.2.1717 E4099 Cmd Rej: Association name not found
The association name specified by the aname parameter must already exist in the IPAPSOCK table.
For the rept-meas command, the association specified by the aname parameter must be provisioned in the system.
For the rtrv-dconn command, the ANAME specified must be present in the IPAPSOCK table and referred by diameter connection.
Recovery
- Display the existing association names in the IPAPSOCK table. Enter the
rtrv-assoccommand. - 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.
2.2.1718 E4100 Cmd Rej: LNP feature must be ON before LNP ELAP Config can be ON
The LNP feature must be turned on before the LNP ELAP Configuration feature can be turned on.
Recovery
2.2.1719 E4102 Cmd Rej: At least one MPS based feature must be enabled/ON
The G-Flex, INP, AINPQ, G-Port, EIR, LNP ELAP Configuration, Prepaid SMS Intercept Ph1, A-Port, or V-Flex feature must be turned on before the following actions can be performed:
- The dsmaud parameter can be specified in the
chg-stpoptscommand - The db=mps parameter can be specified in the
rept-stat-dbcommand - The
rept-stat-mpscommand can be entered
Recovery
- Enter the
rtrv-ctrl-featcommand display the status of the controlled features in the system.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.
- Enable and turn on the desired feature. Refer to the associated feature manual for assistance.
- Re-enter the command that generated this error message.
2.2.1720 E4107 Cmd Rej: AS table is full
A maximum of 250 application servers (AS) can exist in the AS table.
Recovery
2.2.1721 E4109 Cmd Rej: Association is still assigned to AS
An association that is assigned to an application server (AS) cannot be deleted from the IPAPSOCK table
Recovery
2.2.1722 E4111 Cmd Rej: Network/Cluster OPC cannot be criteria for DPCI/DPCN
Recovery
Re-enter the ent-rtx command that generated this error message, specifying a valid combination of parameters.
Refer to the command description in Commands User's Guide for assistance. If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1723 E4112 Cmd Rej: ITU OPC cannot be the criteria for Network/Cluster ANSI DPC
Recovery
Re-enter the ent-rtx command that generated this error message, specifying a valid combination of parameters.
Refer to the command description in Commands User's Guide for assistance. If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1724 E4113 Cmd Rej: Measurement collection in progress, Retry later
The copy/format-disk commands cannot be entered while OAM measurements collection is in progress.
Note:
Entering thechg-meas command while the copy-disk command is in progress results in read and write errors, because the standby fixed disk is not accessible and the active fixed disk only allows read-only access.
Recovery
Contact My Oracle Support before entering these commands. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1725 E4114 Cmd Rej: TTA cannot be specified for a direction of ITOA
If the dir=itoa parameter is specified, then the tta parameter cannot be specified.
Recovery
Re-enter the dlt-gtcnv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1726 E4115 Cmd Rej: TTI must be specified for a direction of ITOA
If the dir=itoa parameter is specified, then the tti parameter must be specified.
Recovery
Re-enter the dlt-gtcnv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1727 E4116 Cmd Rej: Wildcard/Asterisk invalid for direction of BOTH
If the dir=both parameter is specified, then a wildcard value (*) cannot be specified for any of the other parameters.
Note:
A wildcard is an entry specified with the use of asterisks. (*).Recovery
Re-enter the ent/chg/dlt-gtcnv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1728 E4117 Cmd Rej: Wildcard/Asterisk combination invalid for direction
If the dir=atoi parameter is specified, then a wildcard value ( * ) can be specified only for the tta parameter.
Note:
A wildcard is an entry specified with the use of asterisks (*).Recovery
Re-enter the ent/chg-gtcnv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1729 E4118 Cmd Rej: Wildcard/Asterisk required for TTI, NP, NAI if DIR is ITOA
If the dir=itoa parameter is specified, then a wildcard value (*) must be specified for the tti, np, and nai parameters.
Note:
A wildcard is an entry specified with the use of asterisks (*).Recovery
Re-enter the ent/chg/dlt-gtcnv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1730 E4119 Cmd Rej: Key values: DIR, TTA, TTI, NP, NAI already exist
The entry specified by the dir, tta, tti, np, or nai value(s) cannot already exist in the GTCNV table.
Recovery
- Display the current entries in the GTCNV table. Enter the
rtrv-gtcnvcommand. - Re-enter the
ent-gtcnvcommand that generated this error message, specifying a valid combiation of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1731 E4120 Cmd Rej: Key values: DIR, TTA, TTI, NP, NAI does not exist
The combination of dir, tta, tti, np, and nai parameters to be changed or deleted must already exist in the database.
Recovery
- Determine the existing values. Enter the
rtrv-gtcnvcommand. - Re-enter the
chg/dlt-gtcnvcommand that generated this error message, specifying a valid combiation of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1732 E4121 Cmd Rej: ENCODE = AMI not currently supported
The encode=ami parameter is supported only for an HC-MIM, E5-E1T1, or E5-E1T1-B card used as an E1 card.
Recovery
2.2.1733 E4122 Cmd Rej: Both NP and NAI must be specified if either is present
The np and nai parameters must be specified together in the command.
Recovery
Re-enter the dlt-gtcnv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1734 E4123 Cmd Rej: SAPC entry not found for the linkset
Recovery
2.2.1735 E4124 Cmd Rej: APC/SAPC in specified group code already exists for linkset
If the multgc=no parameter is specified, then only one secondary adjacent point code (SAPC) or adjacent point code (APC) per domain per linkset can be specified.
If the multgc=yes parameter is specified, then only one SAPCN per group code per link set can be specified.
Recovery
2.2.1736 E4125 Cmd Rej: Maximum SAPC entries exceeded
The maximum number of sapc/sapca/sapci/sapcn/sapcn24 entries cannot already exist.
Recovery
2.2.1737 E4126 Cmd Rej: Only one ITU-N APC/SAPC allowed with MULTGC=NO
If the multgc=no parameter is specified for the linkset, then only one secondary adjacent point code or adjacent point code can be specified per ITU-N domain per linkset is allowed.
Recovery
2.2.1738 E4127 Cmd Rej: Only one ITU-I or 24-bit ITU-N APC/SAPC allowed per linkset
Only one secondary adjacent point code or adjacent point code is allowed per linkset in an ITU-I or 24-bit ITU-N domain.
Recovery
2.2.1739 E4128 Cmd Rej: SAPC entry present for the linkset
A secondary adjacent point code cannot already be provisioned for the linkset.
Recovery
2.2.1740 E4129 Cmd Rej: SAPC allowed for ITU-I or ITU-N linkset only
The sapc parameter cannot be specified for an ANSI linkset.
Recovery
2.2.1741 E4132 Cmd Rej: Group code not allowed with specified network type
The gc parameter cannot be specified for ANSI, ITUI, or ITUN24 network appearances.
Recovery
2.2.1742 E4133 Cmd Rej: Group code required for ITUN when ITUDUPPC feat is ON
If the ITUDUPPC feature is turned on, then the gc parameter must be specified for ITUN network appearances.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1743 E4134 Cmd Rej: Group code not allowed when ITUDUPPC feat is OFF
If the ITU Duplicate Point Code (ITUDUPPC) feature is turned off, then the gc parameter cannot be specified.
Recovery
2.2.1744 E4135 Cmd Rej: Group code must be in SID or SPC table
The value specified for the gc parameter must already exist in the SID or SPC table.
Recovery
2.2.1745 E4136 Cmd Rej: NA already equipped
The network appearance cannot already exist in the Network Appearance table.
Recovery
- Display the entries in the Network Appearance table. Enter the
rtrv-nacommand. - Re-enter the
ent-nacommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1746 E4137 Cmd Rej: Group code or network type already equipped
Recovery
- Display the existing network appearances. Enter the
rtrv-nacommand. - Re-enter the
ent-nacommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1747 E4138 Cmd Rej: NA entry not found
The specified network appearance must already exist in the Network Appearance table.
Recovery
- Display the entries in the Network Appearance table. Enter the
rtrv-nacommand. - Re-enter the
dlt-nacommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1748 E4139 Cmd Rej: Routing Context already equipped
A duplicate routing key cannot exist.
If a routing key contains a routing context, then the routing key cannot be split.
Recovery
2.2.1749 E4141 Cmd Rej: Inhibit IPSM card(s) before changing Telnet feature status.
All type IPSM cards must be inhibited before the Telnet feature can be turned on or off.
Recovery
2.2.1750 E4142 Cmd Rej: VFLEX feature must be ON
For the chg-mtc-measopts command, the V-Flex feature must be turned on before the mtchvflex=on or mtcdvflex=on parameter can be specified.
For the ent/chg/rtrv-srvsel commands, the V-Flex feature must be turned on before the nserv/serv=vflex parameter can be specified.
For the ent/chg/dlt-ss-appl commands, the V-Flex feature must be turned on before the appl=vflex parameter can be specified.
For the rept-ftp-meas command, the V-Flex feature must be turned on before the enttype=vflex parameter can be specified.
For the chg/rtrv-sid command, the V-Flex feature must be turned on before the cpctype=vflex parameter can be specified.
Recovery
2.2.1751 E4143 Cmd Rej: GPORT/IGM must be enabled or VFLEX must be ON
The G-Port or IGM feature must be enabled or the V-Flex feature must be turned on before the multcc and nmultcc parameters can be specified.
Recovery
2.2.1752 E4145 Cmd Rej: TYPE parameter value is invalid for this processor
The data and codesw values for the breakpoint type portion of the type parameter cannot be specified when the value ixp is specified for the processor type portion of the type parameter.
Recovery
Re-enter the ent-bp command that generated this error message, specifying valid values. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1753 E4146 Cmd Rej: CTX parameter is invalid for this card
The ctx parameter is valid only on IXP-based cards where the value ixp is specified for the processor type portion of the type parameter.
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1754 E4147 Cmd Rej: Invalid combination of TYPE, UENG, and CTX parameters
For an IXP-based card, the ueng and the ctx parameters must be specified.
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1755 E4148 Cmd Rej: DATA parameter is invalid for this card
The data parameter is only valid on an IXP-based card.
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1756 E4149 Cmd Rej: ARM register must be specified
The ca, cb, and drarm parameters must be specified for an IXP-based card when the value arm is specified for the processor type portion of the type parameter.
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1757 E4150 Cmd Rej: CA/CB parameters are invalid for this processor
The ca and cb parameters cannot be specified for a card when the value ixp is specified for the processor type portion of the type parameter.
Recovery
Re-enter the ent-bp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1758 E4151 Cmd Rej: UENG parameter is invalid for this card
The ueng parameter can be specified only for IXP-based cards.
Recovery
Re-enter the ent/disp/dlt-bp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1759 E4152 Cmd Rej: Invalid combination of TYPE and DATA parameters
The data parameter can be specified only if the type=data parameter is specified.
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1760 E4153 Cmd Rej: CA or CB register value is invalid for this card
The values specified for the ca and cb parameters must be valid for an IXP-based card when the value arm is specified for the processor type portion of the type parameter.
Recovery
Re-enter the ent-bp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1761 E4154 Cmd Rej: DRARM parameter is invalid for this processor
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1762 E4155 Cmd Rej: DR parameter is invalid for this card
The dr parameter cannot be specified for an IXP-based card.
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1763 E4156 Cmd Rej: DRARM parameter is invalid for this card
The drarm parameter is only valid on an IXP-based card.
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1764 E4157 Cmd Rej: DA parameter is invalid for this card
The da parameter is not valid for an IXP-based card.
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1765 E4158 Cmd Rej: ADDR parameter is invalid for this card
The addr parameter is valid only for DS0 cards with PROM-based COM processors (the proc=com parameter is specified).
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1766 E4159 Cmd Rej: TYPE parameter value is invalid for this card
Processor types ARM and IXP are only valid on an IXP-based card.
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1767 E4160 Cmd Rej: ACCESS parameter value is invalid for this card
The value any for the format portion of the access parameter can be specified only on IXP-based cards. The format value must be set to any on IXP-based cards.
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1768 E4161 Cmd Rej: Routing Context is required for SUA
If a routing key is associated with an SUA application server (AS), then the rc parameter must be specified.
Recovery
2.2.1769 E4164 Cmd Rej: G-Flex MAP Layer Routing feature must be ON
The G-Flex MAP Routing (G-Flex MLR) feature must be enabled and turned on before the gflexmaplayerrtg, maplyrrtgon, or maplyrrtgoff parameter can be specified.
Recovery2.2.1770 E4165 Cmd Rej: Point Code Subtype Prefix not supported
If a value of ansi or itun24 is specified for the pctype parameter, then a value of s or ps cannot be specified for the pcst parameter.
Recovery
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.
2.2.1771 E4166 Cmd Rej: EGMS must be ON before MTP MAP Screening can be enabled
The Enhanced GSM MAP (EGMS) feature must be turned on before the MTP MAP Screening feature can be enabled.
Recovery
2.2.1772 E4167 Cmd Rej: Cannot add NP and NAI to an entry where GTIXLAT is 22
If the gtixlatt=22 parameter is specified, then the nnp and nnai parameters cannot be specified.
Recovery
- Display the current values for the gtixlatt parameter. Enter the
rtrv-gtcnvcommand. - Re-enter the
chg-gtcnvcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1773 E4168 Cmd Rej: At least one Non-Key parm that is to be changed is required
One of the npdd, npds, nsdd, nsds, or rdmod parameters must be specified in the command.
Recovery
Re-enter the chg-gtcnv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1774 E4169 Cmd Rej: GT Conversion table is full
The Default Global Title Conversion (GTCNV) table can contain a maximum of 1000 entries.
Recovery
2.2.1775 E4170 Cmd Rej: Prefix & Suffix digit modification parameters can't be mixed
The nsdd/nsds and the npdd/npds parametes cannot be specified in the same command.
Recovery
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 and to the Database Administration - GTT User's Guide for assistance.
2.2.1776 E4171 Cmd Rej: SCCP Conversion feature must be enabled
The ANSI/ITU SCCP Conversion feature must be enabled before the ent/chg/dlt/rtrv-gtcnv commands can be entered.
For the chg-sccpopts command, the ANSI/ITU SCCP Conversion feature must be enabled before the cnvainat parameter can be specified.
For the chg-stpopts command, the ANSI/ITU SCCP Conversion feature must be enabled before the cnvcgda, cnvcgdi, cvncgdn, cvncgdn24, or gtcnvdflt parameters can be specified.
For the ent/chg-gtmod command, the ANSI/ITU SCCP Conversion feature must be enabled before the ngti parameter can be specified.
For the chg-gttset command, the ANSI/ITU SCCP Conversion feature must be enabled before the netdom parameter can be specified.
For the ent/rtrv-gttset command, the ANSI/ITU SCCP Conversion feature must be enabled before the netdom=cross parameter can be specified.
For the rtrv-gtt command, the ANSI/ITU SCCP Converstion feature must be enabled before the pctype parameter can be specified.
Recovery
2.2.1777 E4172 Cmd Rej: Can't switch existing Pfx/Sfx, use RDMOD to reset
The rdmod=yes parameter must be specified to reset the current digit modifier values before the values specified for the npdd/npds and nsdd/nsds parameters can be reversed.
Recovery
2.2.1778 E4173 Cmd Rej: Not compatible with SCCP Conversion feature
Recovery
Display the status of the ANSI/ITU SCCP Conversion 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.
If the ANSI/ITU SCCP Conversion feature is enabled, no further action can be taken. Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1779 E4174 Cmd Rej: GT0FILL can be specified as ON only if NGTI is specified
The ngti parameter must be specified with a value other than none before the on=gt0fill parameter can be specified.
Recovery
Re-enter the ent/chg-gtmod command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1780 E4175 Cmd Rej: If NGTI is 4, NNP and NNAI must be specified
If the ngti=4 parameter is specified, then the nnp and nnai parameters must be specified.
Recovery
Re-enter the ent/chg-gtmod command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1781 E4176 Cmd Rej: If NGTI is 2, NNP and NNAI cannot be specified
If the ngti=2 parameter is specified, then the nnp and nnai parameters cannot be specified.
Recovery
Re-enter the ent/chg-gtmod command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1782 E4177 Cmd Rej: Invalid TPCs are present in the MAP table for specified SSN
- For the INP subsystem, the True Point code cannot be an ITU-I or ANSI point code.
- For the EIR subsystem, the True Point code cannot be an ANSI point code.
- For the AIQ, ATINPQ or VFLEX subsystem, the True Point code cannot be an ITU-N24 point code.
Recovery
2.2.1783 E4180 Cmd Rej: Wildcard SSN already exists
A duplicate entry for the gti/gtia/gtii/gtin, tt, np(v), nai(v), and a wildcard ssn is invalid. (A wildcard ssn entry is specified with the use of asterisks).
Recovery
- Display the existing values for the above parameters. Enter the
rtrv-srvselcommand. - Re-enter the
ent-srvselcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the relevant feature manual for assistance.
2.2.1784 E4181 Cmd Rej: Specific SSN already exists
For the ent-srvsel command, a combination of the gti/gtia/gtii/gtin, tt, np(v), nai(v), and ssn parameters that matches an existing combination cannot be specified.
For the ent-ss-appl command, the value specified for the ssn parameter cannot already exist in the SS-APPL table.
Recovery
- Display the existing values for the service selector parameters or the existing entries in the SS-APPL table. Enter the
rtrv-srvselorrtrv-ss-applcommand, respectively. - 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, the G-Port User's Guide (
ent-srvselcommand) and the ELAP Administration and LNP Feature Activation Guide (ent-ss-applcommand) for assistance.
2.2.1785 E4182 Cmd Rej: STP True PC and EIR Subsystem do not exist in MAP table
To reserve an EIR subsystem number for an application, the STP true point code and the EIR subsystem number combination must already be defined in the Mated Applications (MAP) table.
Recovery
2.2.1786 E4183 Cmd Rej: INP/AINPQ/EIR/VFLEX feature must be ON or ATINP/AIQ must be enabled
The INP, AINPQ, V-Flex, or EIR feature must be turned on or the ANSI41 AIQ or ATINP feature must be enabled before the value specified for the mpcn parameter can be a true point code.
Recovery
2.2.1787 E4184 Cmd Rej: EIR Subsystem is offline in database
The EIR subsystem must be online before the EIR subsystem number can be specified as a value for the ssn parameter.
Recovery
2.2.1788 E4185 Cmd Rej: EIR feature must be enabled
For the dlt-ss-appl command, the EIR feature must be enabled before the appl=eir parameter can be specified.
For the rtrv-sid command, the EIR feature must be enabled before the cpctype=eir parameter can be specified.
Recovery
2.2.1789 E4188 Cmd Rej: Must have LNP/EIR/VFLEX/AIQ/ATINP enabled or INP/AINPQ ON
The ANSI41 AIQ, ATINP, EIR, LNP, or V-Flex feature must be enabled, or the AINPQ or INP feature must be turned on before the rtrv-ss-appl command can be entered.
Recovery
2.2.1790 E4189 Cmd Rej: Invalid PC type for the subsystem associated with SSN value
If a subsystem is configured for a subsystem number (SSN) value in the SS-APPL table, then the specified MAP table entry for that subsystem must be a valid point code type for that subsystem. The following point code types are not valid for the indicated subsystems:
- For the INP subsystem, the True Point code cannot be an ITU-I point code.
- For the AIQ, ATINPQ, VFLEX, or EIR subsystem, the True Point code can not be an ITU-N24 point code.
Recovery
2.2.1791 E4191 Cmd Rej: GFLEX/EIR/VFLEX must be ON or GPORT/IGM/MO SMS feat enabled
The G-Port, IGM, MO SMS ASD, MO SMS B-Party Routing, MO SMS GRN, MO SMS IS41-to-GSM Migration, MO-based GSM SMS NP, or Prepaid SMS Intercept Ph1 feature must be enabled, or the G-Flex, EIR, or V-Flex feature must be turned on before this command can be entered.
Recovery
2.2.1792 E4192 Cmd Rej: GFLEX or EIR feature must be on
The G-Flex or Equipment Identity Register (EIR) feature must be turned on before the imsi parameter can be specified.
Recovery
2.2.1793 E4193 Cmd Rej: Spare Point Code Feature must be enabled
The Spare Point Code Support feature must be enabled before a spare point code (prefix s-) can be specified in the command.
Recovery
2.2.1794 E4194 Cmd Rej: Cannot delete last route to DPC referenced in PPSOPTS table
The last route to a destination point code that still exists in the Prepaid SMS Options (PPSOPTS) table cannot be deleted until the existing point code is deleted from the PPSOPTS table.
Recovery
2.2.1795 E4198 Cmd Rej: If PRECD specified, NPDS/NSDS/NPDD/NSDD must be specified
If the precd parameter is specified, then the npdd, npds, nsdd, or nsds parameter must be specified.
Recovery
Re-enter the ent-gtmod command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1796 E4200 Cmd Rej: Cannot use NEXT if preceding RTRV-LOG command used TYPE=ALL
The rtrv-log:next= command cannot be entered following a rtrv-log command that contained the type=all parameter.
Recovery
Re-enter the rtrv-log command without specifying the next parameter or enter the rtrv-log command without the type=all parameter and then enter the rtrv-log:next= command.
Refer to the command description in Commands User's Guide and to the Maintenance Guide for assistance.
2.2.1797 E4201 Cmd Rej: SCCPCNV, TCAPCNV must be disabled
If the SCCPCNV (SCCP Conversion) feature and TCAPCNV (TCAP Conversion) feature are turned on, then the ANSI/ITU SCCP Conversion feature cannot be enabled.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
Display the status for the SCCP Conversion and TCAP Conversion features. Enter the rtrv-feat command.
Contact My Oracle Support for additional assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1798 E4202 Cmd Rej: SCCP Conversion feature requires at least TSM Hardware
The ANSI/ITU SCCP Conversion feature requires Service Module cards in the system.
Recovery
2.2.1799 E4203 Cmd Rej: ENUM requires an SNUM as its mate parameter.
The snum and enum parameters must be specified together in the command.
Recovery
Re-enter the rtrv-log or rtrv-trbltx command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
2.2.1800 E4204 Cmd Rej: ENUM must be greater or equal to mate parameter SNUM.
The value specified for the enum parameter must be equal to or greater than the value specified for the snum parameter.
Recovery
Re-enter the rtrv-log or rtrv-trbltx command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1801 E4205 Cmd Rej: ENUM range does not match SNUM: 1-999 or 1000-1999.
The value specified for the enum parameter must be in the same range as the value specified for the snum parameter. Refer to the command description in Commands User's Guide for the valid ranges.
Recovery
Re-enter the rtrv-log or rtrv-trbltx command that generated this error message, specifying a valid combination of parameters.
2.2.1802 E4206 Cmd Rej: NEXT requires this term issued last valid RTRV-LOG command.
The rtrv-log:next= command must be entered on the same terminal where the previous successful rtrv-log command was entered in the system. If the next parameter is specified, then no other parameters can be specified in the command.
Recovery
Re-enter the rtrv-log command without specifying the next parameter, or enter the rtrv-log:next= command from the same terminal while making certain that no other terminal enters an intervening rtrv-log command. Refer to the command description in the Commands User's Guide and to the Maintenance Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1803 E4208 Cmd Rej: No other parameters are permitted with the NEXT parameter.
If the next parameter is specified, then no other parameters can be specified.
Recovery
Re-enter the rtrv-log command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1804 E4209 Cmd Rej: OUTGRP and SNUM/ENUM combination invalid.
If the outgrp parameter is specified, then the snum and enum parameters cannot be specified.
Recovery
Re-enter the rtrv-trbltx command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1805 E4210 Cmd Rej: TYPE and SNUM/ENUM combination invalid.
For the rtrv-log command, if the type parameter is specified, then the snum and enum parameters cannot be specified.
For the rtrv-trbltx command, the values specified for the snum and enum parameters must be in the range for the type parameter (1-999 for Alarms and 1000-1999 for UIMs).
Recovery
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 and to the Maintenance Guide for assistance.
2.2.1806 E4211 Cmd Rej: If DIR=BKWD, SDATE/STIME must be > EDATE/ETIME.
If the dir=bkwd parameter is specified, then the values specified for the sdate and stime parameters must be greater than the values specified for the edate and etime parameters.
Recovery
Re-enter the rtrv-log command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1807 E4212 Cmd Rej: Cannot execute command until table initialization complete
The table initialization of the ELOG and UIM logs must complete (the maintenance baseline must be established) before the rtrv-log command can be entered.
Recovery
Re-enter the rtrv-log command when the table initialization of the ELOG and UIM logs has completed.
2.2.1808 E4213 Cmd Rej: Current set of next elog entries have been overwritten
Since the previous entry of a rtrv-log command, a number of UAMs and/or UIMs have been logged. Consequently, the pointer to the next log to display has been overwritten by those alarms occurring since the original rtrv-log command was entered. Because the pointer was overwritten by system activity, the next parameter cannot be specified until after a new rtrv-log command without a next parameter is entered and executed.
Recovery
2.2.1809 E4214 Cmd Rej: LOC and E1PORT parameter combination must be specified
For the ent-slk command, if the loc parameter indicates an SE-HSL card, then the e1port parameter must be specified.
For the inh/unhb-alm commands, if the dev=e1port parameter is specified, then the loc and e1port parameters must be specified.
For the rtrv-e1 command, the loc and e1port parameters must be specified together in the command.
Recovery
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.
2.2.1810 E4215 Cmd Rej: LOC and T1PORT parameter combination must be specified
For the ent-slk command, if the loc parameter indicates an ST-HSL-A card, then the t1port parameter must be specified.
For the inh/unhb-alm commands, if the dev=t1port parameter is specified, then the loc and t1port parameters must be specified.
For the rtrv-t1 command, the loc and t1 parameters must be specified together in the command.
Recovery
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.
2.2.1811 E4223 Cmd Rej: Action requires SAPC or RCONTEXT but not together
If the action=delete parameter is specified, then the sapc, or rcontext parameter must be specified. The sapc and rcontext parameters cannot be specified together in the command.
Recovery
Re-enter the chg-ls command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide, and to Database Administration - SS7 User's Guide (SS7 linksets) or to Database Administration - IP7 User's Guide (IP linksets) for assistance.
2.2.1812 E4230 Cmd Rej: First 2 characters of Serial Number must be alphabetical
The system serial number must start with two alphabetic characters.
Recovery
Re-enter the command that generated this error message, specifying alphabetic characters for the first two characters of the serial number. Refer to the command description in Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1813 E4231 Cmd Rej: Last 8 characters of Serial Number must be numerical
The format of the serial number should be AANNNNNNNN, where NNNNNNNN must be numeric digits (0 - 9). Letters, special characters, and spaces are not allowed.
Recovery
Re-enter the command that generated this error message, specifying numbers for the last 8 characters of the serial number. Refer to the command description in Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1814 E4232 Cmd Rej: NT Serial Number must be 10 characters long
The format of the serial number needs to be two alphabetic characters followed by 8 numbers. For example, NT01234567.
Recovery
Re-enter the command that generated this error message, specifying a valid serial number. Refer to the command description in Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1815 E4233 Cmd Rej: Lock cannot be specified on first NT Serial Number entry
The serial number must be entered at least once without specifying the lock parameter.
Recovery
Re-enter the ent-serial-num command that generated this error message without specifying the lock parameter. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1816 E4238 Cmd Rej: Point code matches a STP secondary point code
For the ent-dstn command, the value specified for the point code parameter cannot already exist as a secondary point code (SPC).
For the ent/dlt/rtrv-pct commands, the value specified for the epc/epci/epcn parameter cannot be the same as an SPC.
Recovery
2.2.1817 E4239 Cmd Rej: At least one other optional parameter is required
For the chg-gsmmap-scrn command, if the cdsr parameter is specified, then at least one additional optional parameter must be specified.
For the rtrv-data-rtdb command, if the G-Flex, G-Port, INP, AINPQ, EIR, Prepaid IDP Relay Query, V-Flex, or Prepaid SMS Intercept Ph1 (PPSMS) feature is turned on, or the ATINP feature is enabled, then the imsi, dn, entity, imei, or entitytype parameter must be specified.
Recovery - chg-gsmmap-scrn
chg-gsmmap-scrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
Recovery - rtrv-data-rtdb
2.2.1818 E4240 Cmd Rej: GFLEX, GPORT or VFLEX feat must be ON or ATINP enabled
The G-Flex , G-Port, or V-Flex feature must be turned on or the ATINP feature must be enabled before the entity parameter can be specified.
Recovery
2.2.1819 E4241 Cmd Rej: Link test must not be running on requested link
The act/dact-lbp and act-cdl commands cannot be entered while a signaling link test generated by the tst-slk command is running.
Recovery
2.2.1820 E4242 Cmd Rej: Requested link must not be in command driven loopback
The act/dact-lbp and tst-slk commands cannot be entered while a Command Driven Loopback is in progress.
Recovery
Perform one of the following actions:
-
Stop the command-driven loopback for the appropriate card and link. Refer to the Maintenance Guide for assistance.
-
Re-enter the command that generated this error message, specifying a different card and link.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1821 E4243 Cmd Rej: Link test command in progress
If the specified signaling link is already running a link test, then the tst-slk command cannot be entered.
Recovery
2.2.1822 E4244 Cmd Rej: Link test command not in progress
The tst-slk:action=stop command is not valid if a link test is not in progress on the specified card and link.
Recovery
2.2.1823 E4245 Cmd Rej: Card does not support command driven loopback
The card in the location specified by the loc parameter must support command driven loopback. Refer to the Maintenance Guide for a list of cards that support command driven loopback.
Recovery
2.2.1824 E4246 Cmd Rej: Command driven loopback in progress
The act-cdl command cannot be specified for a link that is already performing a command driven loopback test.
Recovery
2.2.1825 E4247 Cmd Rej: Command driven loopback not in progress
The dact-cdl command is not valid if the signaling link is not currently in command driven loopback but is running a link test.
Recovery
2.2.1826 E4248 Cmd Rej: Dependent GPL must be activated
EPM-based cards cannot support a valid trial version of the BLBEPM GPL and BLCPLD GPL at the same time. One of these GPLs must be downloaded and activated before the other one can be downloaded.
HC-MIM cards cannot support a valid trial version of the BLBIOS GPL and BLCPLD GPL at the same time. One of these GPLs must be downloaded and activated before the other one can be downloaded.
Recovery
2.2.1827 E4251 Cmd Rej: IPTPS required for IPGWx linksets
The iptps parameter must be specified for IPGWx linksets.
Recovery
2.2.1828 E4252 Cmd Rej: IPTPS not allowed for non-IPGWx linksets
The iptps parameter cannot be specified for linksets that are not IPGWx. The ipgwapc=yes parameter must be specified (see the ent-ls command) before the iptps parameter can be specified.
Recovery
2.2.1829 E4253 Cmd Rej: LSUSEALM allowed only for IPGWx and IPSG linksets
The lsusealm parameter cannot be specified for non-IPGWx linksets. The ipgwapc=yes or ipsg=yes parameter must be specified before the lsusealm parameter can be specified.
Recovery
2.2.1830 E4254 Cmd Rej: SLKUSEALM allowed only for IPGWx and IPSG linksets
The ipgwapc=yes or the ipsg=yes parameter must be specified before the slkusealm parameter can be specified.
Recovery
2.2.1831 E4255 Cmd Rej: Total provisioned system TPS limit exceeded
If the HIPR2 High Rate Mode feature is turned off, then the total TPS of all signaling links configured in the EAGLE must be less than or equal to 500,000 TPS. If the HIPR2 High Rate Mode feature is turned on, then the total TPS of all signaling links configured in the EAGLE must be less than or equal to 750,000 TPS.
Note:
The total system TPS is equal to the SIGTRAN TPS + the ATM TPS.Recovery
2.2.1832 E4256 Cmd Rej: TPS must be divisible by 10
The value specified for the iptps parameter must be divisible by 10.
Recovery
Re-enter the ent/chg-ls command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1833 E4257 Cmd Rej: Entity must be specified when Entity type is specified
If the entitytype parameter is specified, then the enttity parameter must be specified.
Recovery
Re-enter the rtrv-data-rtdb command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the appropriate feature manual for assistance.
2.2.1834 E4258 Cmd Rej: Target card is not a SCCP application card.
The card in the location specified by the loc parameter must be an SCCP application card.
Recovery
- Display the cards in the system. Enter the
rtrv-cardcommand. - Install an SCCP application card as necessary. Refer to Maintenance Guide for assistance.
- 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.
2.2.1835 E4259 Cmd Rej: Target card is not in Active state
The card at the location specified by the loc or rloc parameter must be in an Active state.
Recovery
2.2.1836 E4260 Cmd Rej: Cluster DPCs can't inherit A or E linkset types
Cluster destination point codes (DPCs) cannot inherit cluster members that have routes with A or E linkset types.
Recovery
2.2.1837 E4261 Cmd Rej: Point code is not configured for the specified Prepaid type
The pc/pca/pci/pcn parameter must be provisioned for the prepaid type specified by the ppt parameter before the setid parameter can be specified.
Recovery
2.2.1838 E4262 Cmd Rej: SI value must be 3 for SUA
For the ent/chg-appl-rtkey commands, the si=3 parameter must be specified for routing keys associated with SUA Application Servers.
For the ent-as command, for SCCP MSU traffic, the routing key service indicator associated with an Application Server containing SUA ASPs must be 3 (SCCP) for the following key types:
-
DPC-SI-SSN key
-
DPC-SI key
-
SI-only key
Recovery
2.2.1839 E4264 Cmd Rej: Parameter PCST / NPCST is not allowed with C for blocked SR
For the ent/chg/dlt/rtrv-scr-aftpc, ent/chg/dlt/rtrv-scr-cdpa, ent/chg/dlt/rtrv-scr-cgpa, and ent/chg/dlt/rtrv-scr-destfld commands, the pcst parameter cannot be used with an ANSI point code parameter (ni, nc, ncm) or an ITU-N24 point code parameter (sa, ssa, sp)
For the ent-/chg/dlt/rtrv-scr-blkopc or ent/chg/dlt/rtrv-scr-blkdpc commands, the (n)pcst and subparameter c cannot be specified for a blocked screening reference (SR).
Recovery
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 and to the Database Administration - GWS User's Guide for assistance.
2.2.1840 E4265 Cmd Rej: Network Appearance table full
The Network Appearance table can contain a maximum of 45 entries.
Recovery
2.2.1841 E4268 Cmd Rej: Cannot delete last route to DPC ref. in CSPC table
The last route to a destination point code that still exists in the Concerned Secondary Point Code (CSPC) table cannot be deleted until the point code is deleted from the CSPC table. If any of the destinations referencing the routset exist in the CSPC table, then the last route of the routeset cannot be deleted.
Recovery
2.2.1842 E4269 Cmd Rej: No match on PCST parameter during retrieve
The value specified for the pcst parameter must already exist in the database.
Recovery
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.
2.2.1843 E4272 Cmd Rej: Max number of rcontexts per AS exceeded
An AS can be associated to only one routing key that contains a routing context value.
Recovery
2.2.1844 E4273 Cmd Rej: Private PC is only allowed for IPGWx linksets
Private (p-) and private and spare (ps-) point codes can only be assigned to IPGW linksets (the ipgwapc=yes parameter is specified).
Recovery
2.2.1845 E4274 Cmd Rej: Cannot mix Unchannelized and Channelized modes on E1/T1 card
For the ent-e1 command, channelized and unchannelized E1 ports (mixed mode) cannot be specified on a single HC-MIM or E5-E1T1 card.
For the ent-t1 command, channelized and unchannelized T1 ports (mixed mode) cannot be specified on a single HC-MIM or E5-E1T1 card.
Recovery
2.2.1846 E4275 Cmd Rej: Cannot specify TS when Linkclass=Unchan
The ts parameter cannot be specified for HC-MIM or E5-E1T1 cards that are used for SE-HSL or ST-HSL-A links (the linkclass=unchan parameter is specified in the ent-e1 or ent-t1 command).
Recovery
2.2.1847 E4276 Cmd Rej: BPS value not valid for Linkclass=Unchan
A value of 1984000 or 1536000 must be specified for the bps parameter if an HC-MIM or E5-E1T1 card is used for SE-HSL or ST-HSL-A links (the linkclass=unchan parameter is specified in the ent-e1 or ent-t1 command) respectively.
Recovery
2.2.1848 E4278 Cmd Rej: APCNTYPE parameter is only valid for ITUN/ITUN24 link sets
The apcn or apcn24 parameter must be specified before the apcntype parameter can be specified.
Recovery
2.2.1849 E4279 Cmd Rej: Only IPGWx routes are allowed for private PCs
A private point code can be specified as the destination point code (dpca/dpci/dpcn) only for a route that contains an IPGWx linkset.
Recovery
2.2.1850 E4280 Cmd Rej: Alias PCs exceed Max allowed for Feature Quantity
If more than 8000 alias point codes are already assigned in the system, then the 7000 Routesets and 8000 Routesets features cannot be enabled.
If more than 10000 alias point codes are already assigned in the system, then the 10,000 Routesets feature cannot be enabled.
Recovery
2.2.1851 E4281 Cmd Rej: Specified link not supported for Linkclass=Unchan
If an HC-MIM card is used for SE-HSL or ST-HSL-A links, then a value of a or b must be specified for the link parameter.
If an E5-E1T1 card is used for SE-HSL or ST-HSL-A links, then a value of a must be specified for the link parameter.
Recovery
2.2.1852 E4282 Cmd Rej: An HSL feature key must be enabled for Linkclass=Unchan
An SE-HSL feature quantity must be enabled before the linkclass=unchan parameter can be specified for an SE-HSL card.
An ST-HSL-A feature quantity must be enabled before the linkclass=unchan parameter can be specified for an ST-HSL-A card.
Recovery
2.2.1853 E4283 Cmd Rej: Command cannot be executed on a Telnet terminal
The specified command cannot be issued from a Telnet terminal (terminal IDs 17 to 40).
Recovery
2.2.1854 E4284 Cmd Rej: CGPA entry can’t be provisioned
Recovery
2.2.1855 E4285 Cmd Rej: Enhanced GSM Map Screening feature must be ON
For the ent/chg-gsmmap-scrn commands, the Enhanced GSM MAP Screening (EGMS) feature must be turned on before the (n)cdsr, ncdsr, pc, and pca parameters can be specified. The ent-gsmmap-scrn command also requires the EGMS feature to be on before the saddr=* parameter can be specified and before the saddr and eaddr parameters can contain hexadecimal digits.
For the ent/chg-gsms-opcode commands, the EGMS feature must be turned on before opcode=* or (n)pc/(n)pca parameter can be specified.
For the ent/chg-ls command, the EGMS feature must be turned on before the gsmscrn=on parameter can be specified for ANSI linkset.
Recovery
2.2.1856 E4286 Cmd Rej: EADDR shouldn't be specified when SADDR = *
If the saddr=* parameter is specified, then the eaddr parameter cannot be specified.
Recovery
Re-enter the ent/rtrv-gsmmap-scrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1857 E4287 Cmd Rej: CDSR doesn't exist for specified OPNAME and CGSR
The value specified for the cdsr parameter must already exist.
Recovery
2.2.1858 E4288 Cmd Rej: NCGSR shouldn't be specified when CDSR is specified
If the cdsr parameter is specified, then the ncgsr parameter cannot be specified.
Recovery
Re-enter the chg-gsmmap-scrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1859 E4289 Cmd Rej: (N)CGSR already exists for specified OPNAME
The value specified for the (n)cgsr parameter cannot already exist in the database.
Recovery
2.2.1860 E4290 Cmd Rej: CDSR must be specified when NCDSR is specified
If the ncdsr parameter is specified, then the cdsr parameter must be specified.
Recovery
Re-enter the chg-gsmmap-scrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1861 E4291 Cmd Rej: Enhanced GSM Map Screening feature must be enabled
For the dlt-gsmmap-scrn command, the EGMS feature must be enabled before the cdsr parameter can be specified.
Fro the rtrv-gsmmap-scrn command, the EGMS feature must be enabled, before the cgsr, cdsr, or saddr=* parameter can be specified and before the saddr and eaddr parameters can contain hexadecimal digits.
For the rtrv-gsms-opcode command, the EGMS feature must be enabled before the opcode=* parameter can be specified or before an opname parameter that refers to an opcode=* parameter can be specified.
Recovery
2.2.1862 E4292 Cmd Rej: SADDR must be specified when EGMS feature is OFF
If the Enhanced GSM MAP Screening (EGMS) feature is turned off, then the saddr parameter must be specified.
Recovery
2.2.1863 E4293 Cmd Rej: (N)CDSR already exists for specified CGSR
The value specified for the (n)cdsr parameter cannot already exist for the CgPA Screening Reference (cgsr parameter).
Recovery
- Display the existing GSM MAP Screening CdPA entries. Enter the
rtrv-gsmmap-scrncommand. - Re-enter the
ent/chg-gsmmap-scrncommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.1864 E4294 Cmd Rej: Meas for Enh GSM MAP Screening not supported on EOAM
If the Enhanced GSM MAP Screening (EGMS) feature is turned on, then the rept-meas command cannot be used to generate EGMS measurements reports.
Recovery
2.2.1865 E4296 Cmd Rej: SRVSEL of ITU found, but not allowed with ANSIGFLEX
If the Service Selector table contains an ITU entry, then the ANSIGFLEX option cannot be turned on.
Recovery
2.2.1866 E4297 Cmd Rej: ITU entries not allowed when ANSIGFLEX is on
If the ANSIGFLEX option is turned on, then ITU Service Selector entries cannot be specified.
Recovery
2.2.1867 E4298 Cmd Rej: Alias PC table is full
If the 7000 Routesets or 8000 Routesets feature is enabled, then a maximum of 8000 aliases can be provisioned in the system. If the 10,000 Routesets feature is enabled, then a maximum of 10,000 aliases can be provisioned in the system.
Recovery
2.2.1868 E4299 Cmd Rej: Cannot enter a wildcard with XLAT=2, Use XLAT=4 for wildcard
If the dir=itoa and gtixlat=22 parameters are specified, then wildcard values (*) cannot be specified. The dir=itoa and gtixlat=24 parameters must be specified before wildcard values can be specified
Note:
A wildcard is an entry specified with the use of asterisks (*).Recovery
Re-enter the chg/dlt-gtcnv command that generated this error message, specifying a valid combiation of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1869 E4300 Cmd Rej: Conns cannot exist in rtkeys with and without rcontext
An AS cannot be simultaneously assigned to routing keys with routing contexts and to routing keys without routing contexts. All routing key(s) associated with an AS must either have routing contexts or not have routing contexts.
Recovery
- Display the routing keys and routing context values. Enter the
rtrv-appl-rtkey:display=allcommand. - If the routing key is already assigned to an AS, re-enter the command that generated this error message, specifying an appropriate routing context value for the routing key. Refer to the Database Administration - IP7 User's Guide for assistance.
- To assign the routing key to an AS, re-enter the command ensuring that all the routing key(s) associated with an AS have routing contexts, or all the routing key(s) associated with an AS have no routing contexts.
- To delete the routing context of a routing key that is already assigned to an AS, delete all routing keys associated with the AS and then re-enter routing keys without routing context values for the AS. The last RTKEY assigned to an AS cannot be deleted unless all associations in the AS provisioned for the RTKEY are OPEN=NO.
2.2.1870 E4301 Cmd Rej: PCx specified does not exist as a True Point Code
The value specified for the pci or pcn parameter must already exist as an STP destination point code.
Recovery
- Display the STP self-identity destination point code, CLLI, and capability point codes associated with the STP in its active database. Enter the
rtrv-sidcommand. - Verify the PCx value exists. Refer to the specific command and “Point Code Formats and Conversion,” in the Commands User's Guide for information on the correct values.
- Re-enter the
chg-sidcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1871 E4302 Cmd Rej: NPCx cannot be specified without PCx
The pci/npci or pcn/npcn parameters must be specified together in the command.
Recovery
Re-enter the chg-sid command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.1872 E4316 Cmd Rej: VENDID table is full
Recovery
- Display the entries in the Vendor ID table. Enter the
rtrv-vendidcommand. - Delete an entry from the Vendor ID table as necessary. Enter the
dlt-vendidcommand. - Re-enter the
ent-vendidcommand that generated this error message.
Refer to the command descriptions in Commands User's Guide and to G-Port User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1873 E4317 Cmd Rej: Failed reading VENDID table
The Vendor ID table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1874 E4318 Cmd Rej: VENDID already exists in VENDID table
The specified ID entry cannot already exist in the Vendor ID table.
Recovery
2.2.1875 E4319 Cmd Rej: VENDID does not exist in VENDID table
The specified vendor ID entry must already exist in the Vendor ID table.
Recovery
- Display the entries in the Vendor ID table. Enter the
rtrv-vendidcommand. - Re-enter the
dlt-vendidcommand specifying the appropriate vendor ID. Refer to the command description in Commands User's Guide for assistance.
2.2.1876 E4320 Cmd Rej: SRI Redirect Feature must be enabled
For the chg-gsmopts command, the GSM MAP SRI Redirect feature must be enabled before the SRIRDCTENT parameter can be set to either SP or GRN.
For the chg-prefix command, the GSM MAP SRI Redirect feature must be enabled before a GSM MAP SRI Redirect prefix can be defined.
For the ent/rtrv-vendid commands, the GSM MAP SRI Redirect feature must be enabled before the command can be entered.
Recovery
2.2.1877 E4321 Cmd Rej: All VENDID table entries must be of length VENDIDLEN
All VENDID table entries must have the number of digits specified by the vendidlen parameter value.
Recovery
Re-enter the ent-vendid command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the G-Port User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1878 E4322 Cmd Rej: VENDIDLEN may only be changed if VENDID table is empty
All Vendor IDs must be deleted from the table before a different Vendor ID length can be specified.
Recovery
2.2.1879 E4323 Cmd Rej: Invalid condition value comparison for CA or CB register.
A valid value must be specified for the ca and cb parameters.
Recovery
Re-enter the ent-bp 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1880 E4325 Cmd Rej: ELAP architecture does not support LNP quantity requested
The ELAP version that is installed must support the required LNP quantity before the associated LNP quantity feature can be be enabled. Refer to the command description for the enable-ctrl-feat command in the Commands User's Guide for the required version of ELAP for each LNP quantity. Refer to the ELAP Administration and LNP Feature Activation Guide for additional assistance.
Recovery
2.2.1881 E4326 Cmd Rej: ELAP must be available to verify LNP quantity support
ELAP must be installed and available before an LNP feature greater than 96 Million cannot be enabled.
Recovery
2.2.1882 E4327 Cmd Rej: For VENDNUM specified the prefix is not provisioned
A prefix with the same prefix number as the Vendor Number specified by the vendnum parameter must already be provisioned for the GSM MAP SRI Redirect feature.
Recovery
2.2.1883 E4328 Cmd Rej: IS412GSM must be provisioned before SERVERPFX
The is412gsm parameter must be specified before the serverpfx parameter can be specified.
Recovery
Re-enter the chg-gsmopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the IS41 GSM Migration User's Guide for assistance.
2.2.1884 E4329 Cmd Rej: Set SERVERPFX to NONE before disabling IS412GSM
The serverpfx=none parameter must be specified before the is412gsm=none parameter can be specified.
Recovery
Re-enter the chg-gsmopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the IS41 GSM Migration User's Guide for assistance.
2.2.1885 E4330 Cmd Rej: Network Address conflicts with IP Route Table
The IP Network address specified by the pvn/pvnmask parameters or the fcna/fcnb parameters cannot have an existing route in the IP Route table.
Recovery
2.2.1886 E4331 Cmd Rej: Specified network addr assigned to a IP card Ethernet Port
The IP network address specified by the pvn/pvnmask or fcna/fcnb parameters cannot be the same as, overlap, or include any IP network or host addresses assigned to any Ethernet interface for any IP card.
Recovery
2.2.1887 E4332 Cmd Rej: The specified network address is assigned to PVN/FCNA/FCNB
The IP network address specified by the ipaddr and submask parameters must be different from the PVN and fast copy network addresses specified by the pvn/pvnmask, fcna/fcnamask, and fcnb/fcnbmask parameters.
Recovery
2.2.1888 E4333 Cmd Rej: The specified IP route is assigned to PVN/FCNA/FCNB
The network address specified by the dest and submask parameters must be different from the network address specified by the pvn/pvnmask, fcna/fcnamask, and fcnb/fcnbmask parameters of the NETOPTS table.
Recovery
- Display the IP network information. Enter the
rtrv-netoptscommand. - Re-enter the
ent-ip-rtecommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.1889 E4334 Cmd Rej: Requires C-linksets parameter tfatcabmlq to be set to 0
The tfatcabmlq=0 parameter must be specified for all C-linksets before the lsrestrict=off parameter can be specified.
Recovery
2.2.1890 E4336 Cmd Rej: TINP and CNCF cannot be in the same GWS action set
The tinp and cncf gateway screening stop actions cannot be specified in the same action set.
Recovery
Re-enter the chg-gws-actset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GWS User's Guide for assistance.
2.2.1891 E4338 Cmd Rej: CDN does not exist in the database
The value specified for the cdn parameter must already exist in the Call Decision table.
Recovery
- Enter the
rtrv-vflx-cdcommand to display the current values. - If the specified value does not exist, enter it.
- Re-enter the command that caused this error message, specifying the correct value.
Refer to the command descriptions in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1892 E4339 Cmd Rej: Common screening list feature invalid
The specified feature name must be valid for a feature that uses a Common Screening List. The feature name must be specified as it appears in the rtrv-ctrl-feat command output. Enough of the name must be specified to make the name unique when two features begin with the same word or acronym.
Refer to the command description in Commands User's Guide for a list of features that use a Common Screening List.
Recovery
Re-enter the command that generated this error message, specifying a valid feature name.
2.2.1893 E4340 Cmd Rej: Common screening list key invalid
The parameter specified for the common screening list key must be valid. Refer to the command descriptions in the Commands User's Guide for a list of valid screening list parameters.
Recovery
- Display the provisioned screening list values. Enter the
rtrv-cslcommand. - Re-enter the
ent/chg-cslcommand that generated this error message, specifying a valid combination of parameters.
2.2.1894 E4341 Cmd Rej: (N)CDN already exists in the database
The value specified for the ncdn parameter or the cdn parameter cannot already exist in the Call Decision table.
Recovery
- Enter the
rtrv-vflx-cdcommand to display the current values. - Re-enter the command that caused this error message, specifying a valid value for the ncdn or cdn parameter.
Refer to the command descriptions in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1895 E4343 Cmd Rej: Feature Prefix too long
The specified prefix value must contain a number of digits that is equal to or less than the maximum number of digits required by the specified feature.
Recovery
Re-enter the chg-prefix 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1896 E4345 Cmd Rej: Feature Prefix already exists
The specified feature prefix cannot already exist.
Recovery
- Display the provisioned prefix information for all features. Enter the
rtrv-prefixcommand. - Re-enter the
chg-prefixcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1897 E4346 Cmd Rej: FEATPFX table full
A maximum of 256 entries is allowed in the FEATPFX table.
Recovery
2.2.1898 E4347 Cmd Rej: Feature Name is not valid
The value specified for the feature parameter must be supported by the command and must be entered in the format specified by the rtrv-ctrl-feat command. Refer to the command description in Commands User's Guide for a list of features supported by the chg-prefix command.
Recovery
Re-enter the chg-prefix command that generated this error message, specifying a valid combination of parameters.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1899 E4348 Cmd Rej: Feature Prefix Number invalid
The value specified for the prefixnum parameter must be valid for the specified feature. Refer to the command description for the chg-prefix command in Commands User's Guide for a list of valid values.
Recovery
Re-enter the chg-prefix command that generated this error message, specifying a valid combination of parameters.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1900 E4349 Cmd Rej: Feature Prefix still in use
The specified feature prefix value must not be used by the specified feature.
Recovery
2.2.1901 E4350 Cmd Rej: Feature Prefix not found
The specified feature prefix must already exist in the FEATPFX table.
Recovery
2.2.1902 E4351 Cmd Rej: Telnet Feature must be enabled
The Telnet feature must be enabled before the SEAS Over IP feature can be enabled.
Recovery
2.2.1903 E4352 Cmd Rej: SUBNETID table is full
The Subnet ID table has a maximum of 50 entries.
Recovery
2.2.1904 E4353 Cmd Rej: Failed reading SUBNETID table
The Subnet ID table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1905 E4354 Cmd Rej: SUBNETID already exists in SUBNETID table
The specified Subnet ID entry cannot already exist in the Subnet ID table.
Recovery
2.2.1906 E4355 Cmd Rej: SUBNETID does not exist in SUBNETID table
The specified Subnet ID entry must already exist in the Subnet ID table.
Recovery
2.2.1907 E4356 Cmd Rej: ISUP NP with EPAP feature must be enabled
The ISUP NP with EPAP feature must be enabled before the ent/rtrv-subnetid command can be entered.
For the chg-prefix command, the ISUP NP with EPAP feature must be enabled before an ISUP NP with EPAP prefix can be specified
Recovery
2.2.1908 E4357 Cmd Rej: All SUBNETID table entries must be of length SUBNETIDLEN
All subnet ID entries must have the number of digits specified by the subnetidlen parameter.
Recovery
2.2.1909 E4358 Cmd Rej: SUBNETIDLEN may only be changed if SUBNETID table is empty
The value for the subnetidlen parameter can only be changed if the Subnet ID table is empty.
Recovery
2.2.1910 E4359 Cmd Rej: For SUBNETNUM specified the prefix is not provisioned
A prefix with the same prefix number as the value specified for the subnetnum parameter must already be provisioned for the ISUP NP with EPAP feature.
Recovery
2.2.1911 E4360 Cmd Rej: VENDIDLEN must be set before Vendor ID may be entered
The vendidlen parameter must be specified before any Vendor ID can be specified.
Recovery
Re-enter the ent-vendid command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the G-Port User's Guide for assistance.
2.2.1912 E4361 Cmd Rej: Enter VENIDLEN, or VENDID, VENDNUM and VENDTYPE
The vendidlen parameter cannot be specified in the same command with the vendid, vendnum, and vendtype parameters.
Recovery
Re-enter the ent-vendid command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the G-Port User's Guide for assistance.
2.2.1913 E4362 Cmd Rej: SUBNETIDLEN must be set before Subnet ID may be entered
The subnetidlen parameter must be specified before any subnet ID can be specified
Recovery
Re-enter the ent-subnetid command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1914 E4363 Cmd Rej: Enter param SUBNETIDLEN , or params SUBNETID and SUBNETNUM
The subnetidlen and subnetid parameters cannot be specified together in the command.
Recovery
Re-enter the ent-subnetid command that generated this error message, specifiying 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1915 E4364 Cmd Rej: Failed reading FEATPFX table
The FEATPFX table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1916 E4365 Cmd Rej: Either TLNP or ISUP NP with EPAP must be enabled
The Triggerless LNP (TLNP) feature must be turned on before the tlnp stop action can be specified.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1917 E4366 Cmd Rej: DEV parameter is not supported by the specified location
The specified device type must be supported by the card in the specified card location.
Recovery
Re-enter the inh/unhb-alm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide for valid parameter combinations.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1918 E4367 Cmd Rej: TT parameter must be specified
If a value of 2 or 4 is specified for the gti(x) parameter, then the tt parameter must be specified.
Recovery
Re-enter the ent/chg/dlt-gttsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1919 E4368 Cmd Rej: The specified CMD cannot be assigned a configurable class
The login command is available to all users and cannot be assigned to a configurable class.
Recovery
Re-enter the chg-cmd command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1920 E4369 Cmd Rej: Cannot assign APC with exception routes to linkset
A point code cannot be assigned to a linkset as an Adjacent Point Code (APC) if the point code has been provisioned with exception routes.
Recovery
2.2.1921 E4370 Cmd Rej: Level 1 Alarm Threshold level must be less than Level 2
Each Level 1 parameter value must be less than its corresponding Level 2 parameter value.
Recovery
2.2.1922 E4371 Cmd Rej: GPORT must be enabled
For the enable-ctrl-feat command, the G-Port feature must be enabled before the MT-Based GSM SMS NP or G-Port SRI Query for Prepaid features can be enabled.
For the chg-gsmopts command, the G-Port feature must be enabled before the sridnnotfound parameter can be specified.
Recovery
2.2.1923 E4374 Cmd Rej: Association in maximum allowed application servers
An association can be assigned to a maxiumum of 50 application servers.
Recovery
2.2.1924 E4375 Cmd Rej: Route Exception already exists for input parameters
An exception route entry cannot already exist with the same input parameter values, other than the relative cost.
Recovery
2.2.1925 E4376 Cmd Rej: Maximum matching Route Exceptions already exist for DPC
The 6-Way Loadsharing on Routesets feature must be turned on before more than 2 routes can be provisioned with the same relative cost for a given exception route criteria.
Recovery
2.2.1926 E4377 Cmd Rej: Maximum Route Exceptions already exist per DPC and Criteria
A maximum of six exception routes can be associated with the specified DPC and criteria.
Recovery
2.2.1927 E4378 Cmd Rej: Maximum Route Exceptions already exist for this STP
The overall number of exception routes and normal routes that can be defined for the EAGLE cannot be greater than the number of Destination Point Codes assigned.
Recovery
2.2.1928 E4379 Cmd Rej: Failed to access Route Exception Table
The Route Exception table must be accessible.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1929 E4380 Cmd Rej: Route Exception does not exist
The combination of exception route parameter conditions specified must already exist.
Recovery
2.2.1930 E4381 Cmd Rej: CIC Range overlaps an existing range
The range specified by the cic and ecic parameters cannot overlap an existing CIC range.
Recovery
2.2.1931 E4382 Cmd Rej: LSN and NLSN cannot be identical
The same values cannot be specified for the lsn and nlsn parameters.
Recovery
Re-enter the chg-rtx command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - SS7 User's Guide for assistance.
2.2.1932 E4383 Cmd Rej: Either NLSN or RC must be specified
The nlsn or rc parameter must be specified in the command.
Recovery
Re-enter the chg-rtx command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.1933 E4384 Cmd Rej: Use type=remote or enter ipaddr in IPLNK table
If the type=local parameter is specified, then the value specified for the ipaddr parameter must already exist in the IP Link table.
Note:
A remote host resides in a different network or subnetwork. A local host resides within the EAGLE.Recovery
2.2.1934 E4385 Cmd Rej: Use type=local or remove ipaddr from IPLNK table
If the type=remote parameter is specified, then the value specified for the ipaddr parameter cannot already exist in the IP Link table.
Note:
A remote host resides in a different network or subnetwork. A local host resides within the EAGLE.Recovery
2.2.1935 E4386 Cmd Rej: IP Address referenced in IPHOST table
The IP address of an existing IP link entry in the IP Link table cannot be changed if the IP address exists in the IP Host table.
Recovery
2.2.1936 E4387 Cmd Rej: OPC must not be identical to DPC
The same value cannot be specified for the Originating Point Code (opc/opca/opci/opcn/opcn24 parameter) and Destination Point Code (dpc/dpca/dpci/dpcn/dpcn24 parameter).
Recovery
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 and to the Database Administration - SS7 User's Guide for assistance.
2.2.1937 E4388 Cmd Rej: Exception route cannot be assigned to adjacent point code
The value specified for the dpc parameter cannot already be used as an adjacent point code (APC).
Recovery
2.2.1938 E4389 Cmd Rej: BOOT=NO not supported for specified gpl
If the BLCPLD or BLIXP GPL is being downloaded, then the boot=no parameter cannot be specified.
Recovery
Re-enter the init-flash command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide, the Database Administration - System Management User's Guide, and the Maintenance Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1939 E4391 Cmd Rej: Exception route cannot be assigned to cluster members
The Nested Cluster Routing (NCR) feature must be turned on before an exception route can be assigned to cluster members.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.1940 E4392 Cmd Rej: Assigned SLKs must be deleted before apcntype can be changed
All links assigned to the linkset must be removed before the apcntype parameter value can be changed.
Recovery
2.2.1941 E4393 Cmd Rej: Origin Based SCCP Routing feature must be enabled
For the ent/chg-gta commands, the Origin Based SCCP Routing (OBSR) feature must be enabled before the opcsn, cgpc/cgpca/cgpci/cgpcn/cgpcn24, opc/opca/opci/opcn/opcn24, or (e)cgssn parameters can be specified.
For the dlt/rtrv-gta command, the OBSR feature must be enabled if the cgpc/cgpca/cgpci/cgpcn/cgpcn24, opc/opca/opci/opcn/opcn24, or (e)cgssn parameters can be specified.
For the chg/ent/rtrv-gttsel commands, the OBSR feature must be enabled before the cdgtasn, cggtasn, cgpcsn, or cgssn parameters can be specified.
For the dlt-gttsel command, the OBSR feature must be enabled before the cgssn parameter can be specified.
For the ent/rtrv-gttset commands, the OBSR feature must be enabled before the settype parameter can have a value of cggta, cgssn, opc, or cgpc.
For the chg/ent-ls commands, the OBSR feature must be enabled before the gttmode parameter can have a value of acdcd, cgacdcd, acdcgcd, acdcdcg, cgcd, cdcg, or cg.
For the chg-sccpopts command, the OBSR feature must be enabled before the dfltgttmode parameter can have a value of acdcd, cgacdcd, acdcgcd, acdcdcg, cgcd, cdcg, or cg.
Recovery
2.2.1942 E4397 Cmd Rej: At least one GTT Set Name must be specified
At least one GTT set name parameter must be specified. Refer to the command description in Commands User's Guide for valid GTT set name parameters.
Recovery
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 and to the Database Administration - GTT User's Guide for assistance.
2.2.1943 E4398 Cmd Rej: OPTSN and CGSELID/CDSELID are mutually exclusive
For the chg-gta command, the cdselid, cgselid, and optsn parameters cannot be specified together in the command. If the GTTSN has a set type of cdgta, cdssn, or opcode (see the ent-gttset command) then the optsn parameter can be specified if one of the other exclusive parameters is specified.
For the ent-gta command, the cdselid, cgselid, and optsn parameters cannot be specified together in the command. If the GTT set has a set type of cdgta, cdssn, or opcode, then the opcsn parameter can be specified with one of the above parameters.
Recovery
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 and to the Database Administration - GTT User's Guide for more information.
2.2.1944 E4399 Cmd Rej: Set type of GTT Set Name doesn't match
For the ent/chg-gta commands, the value specified for the gttsn parameter must match the corresponding set type entry in the GTTSET table.
For the ent/chg-gttapath commands, the GTT set name specified by the opgttsn, cggttsn, or cdgttsn parameter must have a set type of OPCODE, CGGTA, or CDGTA , respectively.
Recovery
2.2.1945 E4400 Cmd Rej: GTA/CGPC/OPC/CGSSN/CDSSN/OPCODE/DPC/SADDR must be specified
The cgpc/cgpca/cgpci/cgpcn/cgpcn24/cgpcn16, opc/opca/opci/opcn/opcn24/opcn16, cgssn, gta, cdssn, dpc/dpca/dpci/dpcn/dpcn24/dpcn16, opcode/acn/pkgtype, opcode/family/pkgtype, or saddr parameter must be specified.
Recovery
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.
2.2.1946 E4401 Cmd Rej: CGSSNSN cannot be specified with CGGTASN/OPCSN/CGPCSN/SELID
If the cgssnsn parameter is specified, then the cggtasn, opcsn, cgpcsn, and selid parameters cannot be specified.
Recovery
Re-enter the ent-gta command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1947 E4402 Cmd Rej: SETTYPE must be CDGTA/MBR Type when NETDOM=CROSS
For the
ent/rtrv-gttset command, if the
netdom=cross parameter is specified,
then the value specified for the GTT set type (settype) parameter must be
cdgta.
For the
chg/ent/rtrv-gttset
command, the
netdom=cross parameter can be
specified if the existing GTT set type (settype) parameter is
cdgta/imei/imsi/msisdn/vlrnb/smrpoa/smrpda.
Recovery
- For the
chg-gttsetcommand, display the existing values for the settype parameter. Enter thertrv-gttsetcommand. - 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 and to the Database Administration - GTT User's Guide for assistance.
2.2.1948 E4403 Cmd Rej: CGSSN cannot be specified with OPTSN/OPCSN/CGSELID
For the chg-gta command, the FLOBR feature must be turned on before the cgssn, opcsn, optsn, and cgselid parameters can be specified in the same command.
For the ent-gta command, if the cgssn parameter is specified, then the optsn and cgselid parameters cannot be specified.
Recovery - ent-gta
Re-enter the ent-gta command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
Recovery - chg-gta
2.2.1949 E4404 Cmd Rej: End value must be greater than or equal to a starting value
For the ent/chg/dlt/rtrv-gta commands, the value specified for the ecgssn/ecdssn parameter must be greater than the value specified for the cgssn /cdssn parameter, respectively.
For the ent/dlt/rtrv-pct commands, the value specified for the ecice/rcice parameter must be greater than or equal to the value specified for the ecics/rcics parameter, respectively.
For the ent/chg/dlt/rtrv-rtx commands, the value specified for the ecic parameter must be greater than or equal to the value specified for the cic parameter.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1950 E4405 Cmd Rej: OPTSN GTT set type is not compatible with GTTSN set type
If the GTT set specified by the
gttsn parameter (GTTSN set) has a
set type of cdgta (see the
ent-gttset command), then the
optsn parameter cannot specify a GTT
set (OPTSN set) with a set type of cgssn.
The OPTSN set must have a set type of cggta or
cgpc.
The FLOBR feature must be turned on before a GTTSN set with a set type of cgpc, cggta, or opc can be specified with an OPTSN with a set type other than cgssn.
If the FLOBR feature is turned on, and the GTTSN set has a set type of cdgta or cdssn, then the OPTSN set cannot have a set type of opc.
If the TOBR feature is turned on, and the GTTSN set has a set type of opcode, then the OPTSN set cannot have a set type of opc.
If the GTTSN set has a MAP Based Routing (MBR) set type (imei/imsi/vlrnb/msisdn/smrpda/smrpoa), then the OPTSN set type cannot have the same set type as GTTSN.
If the OPTSN set has a MAP Based Routing (MBR) set type (imei/imsi/vlrnb/msisdn/smrpda/smrpoa), then the GTTSET must have a MBR or opcode set type.
Recovery
2.2.1951 E4406 Cmd Rej: GTA parm must be specified if GTTSN is type of CDGTA/CGGTA
The gta parameter must be specified if the value specified for the GTTSN set type is cdgta or cggta. The gta parameter cannot be specified for other set types.
Recovery
Re-enter the ent/chg/dlt-gta command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1952 E4407 Cmd Rej: CGPCx parm must be specified if GTTSN is type of CGPC
The cgpc/cgpca/cgpci/cgpcn/cgpcn24 parameter must be specified if the value specified for the GTTSN set type is cgpc.
Recovery
2.2.1953 E4408 Cmd Rej: OPCx parm must be specified if GTTSN is type of OPC
The opc/opca/opci/opcn/opcn24 parameter must be specified if the value specified for the GTTSN set type is opc. These parameters can only be specified if the GTTSN set type is opc.
Recovery
2.2.1954 E4409 Cmd Rej: CGSSN parm must be specified if GTTSN is type of CGSSN
The cgssn parameter must be specified if the value specified for the GTTSN set type is cgssn. The cgssn parameter can only be specified if the GTTSN set type is cgssn.
Recovery
2.2.1955 E4412 Cmd Rej: CGSSN/CDSSN range cannot overlap an existing range
The range specified by the cgssn/ecgssn and cdssn/ecdssn parameters cannot overlap a currently existing range for the specified GTT set.
Recovery
2.2.1956 E4414 Cmd Rej: SSNSELID Table is full
The SSNSELID Table can contain a maximum of 100,000 entries.
Recovery
2.2.1957 E4415 Cmd Rej: CGSSN/CDSSN range does not exist
The range specified by the cgssn/ecgssn and cdssn/ecdssn parameters must exist for the specified GTT set. An exact match is not required.
Recovery
2.2.1958 E4416 Cmd Rej: Cant dlt last/all route to DSTN/member that has xception rte
The last route to a destination that contains exception routes cannot be deleted. If any of the destinations referencing the specified routset contains exception routes, then the last route of the routeset cannot be deleted.
If a cluster point code is provisioned with ncai=no (see the ent/chg-dstn command), and any cluster member has an associated exception route, then the routeset can not be deleted using the all=yes parameter.
Recovery
2.2.1959 E4433 Cmd Rej: APORT must be enabled
The A-Port feature must be enabled before the MO-based IS41 SMS NP or MT-based IS41 SMS NP feature can be enabled.
Recovery
2.2.1960 E4435 Cmd Rej: OPC/ILSN/CIC/SI is mandatory and mutually exclusive
The cic, ilns, opc, or si parameter must be specified. Only one of these parameters can be specified.
Recovery
Re-enter the ent/chg/dlt-rtx command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1961 E4439 Cmd Rej: Cmd or Shell parameter must be specified
The pass command must include either the cmd= parameter or the shellcmd= parameter.
Recovery
Re-enter the pass command that generated this error message, specifying either the cmd= parameter or the shellcmd= parameter.
Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1962 E4440 Cmd Rej: Card running the specified code load.
If all flash GPLs are already running the approved code load, then the flash-card command does not have any effect. If any flash GPL is not approved, then the flash-card command re-flashes only the non-approved GPL(s).
Recovery
2.2.1963 E4446 Cmd Rej: MO-based GSM SMS NP or MO SMS ASD/GRN must be enabled
The MO-based GSM SMS NP, MO SMS ASD, or MO SMS GRN feature must be enabled before the mosmsfwd or mosmsgta parameter can be specified.
Recovery
2.2.1964 E4447 Cmd Rej: At least one entity is required to turn on measurements
For the chg-meas command, at least one SLK or SIP/DEIR connection must be configured before the collect=on parameter can be specified.
For the chg-measopts command, at least one SLK or SIP/DEIR connection must be configured before the platformenable=on or oamhcmeas=on parameter can be specified.
Recovery
2.2.1965 E4448 Cmd Rej: Maximum adapter states per card exceeded
There are per card and per system limits on the maximum number of sockets supported: the maximum number of sockets per Local Host on SS7IPGW/IPGWI cards is 50, the maximum number of sockets per signaling link on IPLIM/IPLIMI cards is 1, and the maximum number of IP connections per system is 4000.
Each time an M3UA/SUA association is assigned to an AS, the SS7IPGW or IPGWI card that hosts the association must maintain a state (ASP-Down, ASP-Inactive, ASP-Active) for the association/AS combination.
Recovery
2.2.1966 E4452 Cmd Rej: SOIP Feature cant be turned ON if IPUI feature is not ON
The IP User Interface (IPUI) feature must be turned on before the SEAS Over IP feature can be turned on.
Recovery
2.2.1967 E4453 Cmd Rej: SOIP Feature must be ON
The SEAS Over IP (SOIP) feature must be turned on before a SEAS terminal can be specified.
Recovery
2.2.1968 E4457 Cmd Rej: CGSELID is valid only if specified GTTSN set type is CDGTA
The FLOBR feature must be turned on before the gttsn parameter can specify a GTT set with a set type other than cdgta (see the ent-gttset command) in the same command with the cgselid parameter.
Recovery
2.2.1969 E4458 Cmd Rej: Common screening list feature is required
An enabled feature that uses a common screening list must be specified using either the pn or feature parameter.
Recovery
Re-enter the ent/chg/dlt/-csl command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.1970 E4459 Cmd Rej: Common screening list type is required
A valid value must be specified for the list parameter.
Recovery
Re-enter the ent/chg/dlt/-csl command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance
2.2.1971 E4460 Cmd Rej: Common screening list type is invalid
The value specified for the list parameter must be valid for the specified screening feature.
Recovery
Re-enter the ent/chg/dlt/rtrv-csl command that generated this error message, specifying a valid combination of parameters. Refer to the command descriptions in the Commands User's Guide for the appropriate values for each screening feature.
2.2.1972 E4461 Cmd Rej: Common screening list entry already exists
The value specified for the ds parameter cannot already exist for the specified feature and screening list.
Recovery
2.2.1973 E4462 Cmd Rej: Common screening list entry not present
The specified entry must exist for the specified feature part number or feature name and list type.
Recovery
- Display the existing entries. Enter the
rtrv-cslcommand. - Re-enter the
chg/dlt-cslcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the appropriate feature manual for assistance.
2.2.1974 E4464 Cmd Rej: Common screening list invalid parameter combination
A valid parameter combination must be specified.
Recovery
Re-enter the ent/chg/dlt/rtrv-csl command that generated this error message, specifying an appropriate parameter combination. Refer to the command description in Commands User's Guide for assistance.
2.2.1975 E4466 Cmd Rej: Common screening list full
The common screening list for the specified feature is full. Each list table is allowed to contain a maximum number of entries. Refer to the command description in Commands User's Guide for the maximum number of entries for each list.
Recovery
2.2.1976 E4467 Cmd Rej: Common screening list read fail
The specified screening list cannot be read.
Recovery
Re-enter the ent/chg/dlt/rtrv-csl command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1977 E4468 Cmd Rej: Common screening list requested feature must be enabled
The feature that is specified in the feature parameter must be enabled. Refer to the command description in Commands User's Guide for a list of features and part numbers.
Recovery
2.2.1978 E4469 Cmd Rej: Failed reading SSNSELID table
The SSNSELID table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1979 E4472 Cmd Rej: The IP Addr of E5-IPSM corresponding to SEAS Trm must be set
For the chg-ctrl-feat command, an IPSM card must be provisioned before the SEAS Over IP feature can be turned on.
An IPSM card must be provisioned before the alw-trm or rst-trm command can be entered for a SEAS terminal.
Recovery
2.2.1980 E4473 Cmd Rej: CONN parameter required with IPADDR, PORT, LOGIN and HNAME
The conn parameter must be specified before the port, ipaddr, login, or hname parameter can be specified.
Recovery
Re-enter the chg-seas-config command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.1981 E4474 Cmd Rej: SEASCLLI must be set
The SEASCLLI value must be configured before the SEAS Over IP feature can be turned on.
Note:
The SEAS over IP feature must be enabled before the SEASCLLI value can be configured.Recovery
2.2.1982 E4475 Cmd Rej: MRNSET must be specified (only) if RI parameter is GT
If the Flexible GTT Loadsharing (FGTTLS) feature is enabled, and the ri=gt parameter is specified, then the mrnset parameter must be specified. If the ri=ssn parameter is specified, then the mrnset parameter cannot be specified
Recovery
2.2.1983 E4476 Cmd Rej: Specified PC must exist in MRNSET
The value specified for the point code parameter must already exist in the MRN Set.
Recovery
2.2.1984 E4477 Cmd Rej: Terminal cannot be changed to type SEAS
- The value specified for the trm parameter is 1 - 16.
- Specifying the parameter results in more than one SEAS terminal on a type IPSM card.
- Specifying the parameter results in more than two SEAS terminals in the system.
- An IPSM card is not physically present in the corresponding location.
- The SEAS terminal specified by the parameter values does not exist in the SEASCFG table.
Recovery
2.2.1985 E4478 Cmd Rej: Force must be specified to inhibit the last SEAS terminal
For the inh-card command, if the card specified by the loc parameter has the last in-service SEAS Terminal configured, then the force=yes parameter must be specified to inhibit the card.
For the inh-trm command, if the terminal specified by the trm parameter is the last SEAS terminak, then the force=yes parameter must be specified to inhibit the last terminal.
Recovery
- Display the terminals in the system. Enter the
rtrv-trmcommand. - Configure an additional SEAS terminal if desired. Refer to the Database Administration - System Management User's Guide for assistance.
- 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.
2.2.1986 E4479 Cmd Rej: MRNSET must be specified (only) if FGTTLS feature is enabled
The Flexible GTT Load Sharing (FGTTLS) feature must be enabled before the mrnset parameter can be specified.
Recovery
2.2.1987 E4480 Cmd Rej: Specified MRNSET does not exist
For the ent/chg/rtrv-gta, ent/chg/rtrv-gtt, ent/chg/rtrv-gttact, chg-map, and chg/dlt/rtrv-mrn commands, the value specified for the mrnset parameter must already exist in the MRN table.
For the chg/dlt-sccp-serv commands, the specified MRN set must already exist in the SCCP-SERV portion of the MRN table.
Recovery
2.2.1988 E4481 Cmd Rej: SOIP Feature is ON
If the SEAS Over IP (SOIP) feature is turned on, then the IPUI feature cannot be turned off.
Recovery
2.2.1989 E4482 Cmd Rej: NEW or DFLT MRNSET must be specified
When creating a weighted entity set, the mrnset parameter must be specified.
Recovery
Re-enter the ent-mrn command that generated this error message, specifing a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1990 E4483 Cmd Rej: PC does not exist in specified MRNSET
For the chg-sccp-serv and dlt-sccp-serv commands, the specified point code must already exist in the specified MRNSET portion of the SCCP-SERV table.
For the ent/chg-gta, ent/chg-gtt, and ent/chg-gttact commands, if the Flexible GTT Load Sharing (FGTTLS) feature is enabled, then the specified point code must already exist in the specified MRN set.
For the ent/chg-map commands, the value specified for the mrnpc parameter must already exist in the specified MRN Set.
For the ent/chg/dlt/rtrv-mrn commands, the specified point code must already exist in the MRN set.
Recovery
2.2.1991 E4484 Cmd Rej: MRN entry is being referred by other entities
If the Flexible GTT Load Sharing (FGTTLS) feature is enabled, then an MRN entry cannot be deleted if the entry is referenced in the MAP, GTT, GTT Action, or PPSOPTS table, using the MRNSET/PC combination.
If the FGTTLS feature is not enabled, then the MRN entry cannot be deleted if the entry is referenced in the GTT, GTT Action, or PPSOPTS table, using the point code.
Recovery
2.2.1992 E4485 Cmd Rej: PC & MRNSET must be specified together
If the Flexible GTT Loadsharing (FGTTLS) feature is enabled, then the pc/pca/pci/pcn/pcn24 and mrnset parameters must be specified.
Recovery
2.2.1993 E4486 Cmd Rej: CgPA GTT Set does not exist
The GTT set specified by the cgttsn, cggtasn, or cgpcsn parameter must already exist in the GTT Set table.
Recovery
2.2.1994 E4487 Cmd Rej: Network domains of GTI and CgPA GTT Set must match
The network domain of the CgPA GTT Set specified by the cggttsn, cggtasn, or cgpcsn parameter must match the domain indicated by the gti(x) parameter.
Recovery
- Display the information for the GTT sets. Enter the
rtrv-gttsetcommand. - Re-enter the
ent/chg-gttselcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.1995 E4488 Cmd Rej: CGGTASN/CGPCSN set type doesn't match
The set type of the GTT set specified by the cggtasn or cgpcsn parameter must match the set type of the corresponding entry in the GTT Set table.
Recovery
2.2.1996 E4489 Cmd Rej: Common screening list key must be unique
The leading digit pattern in the ds parameter must be unique in the specified screening list for the specified feature.
Recovery
2.2.1997 E4490 Cmd Rej: Card type must be DCM/SLIC for a 100Mbit link
If the speed=100 parameter is specified, then
the card in the specified location must be an E5-ENET or
E5-ENET-B card. For both cards, the card type in the ent-card command is DCM.
Recovery
2.2.1998 E4491 Cmd Rej: Invalid IP database configuration
Unresolved IP references were found in the IP database while executing the act-upgrade command. This means that the database contains references to IP signaling entities (Application Server, IP Connection, IP Host, etc) that do not exist or configuration parameters that are no longer supported.
Recovery
Follow the recovery procedure in the Upgrade Procedure documentation, or Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.1999 E4492 Cmd Rej: Common screening list invalid DS parameter value
The value specified for the ds parameter must contains valid value(s) for the specified feature screening list.
Recovery
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.
2.2.2000 E4493 Cmd Rej: Common screening list DS length invalid
The length of the digit string that is specified for the ds parameter must be valid for the screening feature and list type.
Recovery
Re-enter the ent/chg-csl command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the appropriate feature manual for assistance.
2.2.2001 E4498 Cmd Rej: The Prepaid IDP Query Relay feature must be enabled
The Prepaid IDP Query Relay (IDPR) feature must be enabled before the chg-tatr-opts or chg/rtrv-ttr-msg commands can be entered.
For the tst-msg command, the IDPR feature must be enabled before the feat=ttr parameter can be specified.
Recovery
2.2.2002 E4499 Cmd Rej: Common screening list invalid parameter value
The specified common screening list parameter value must be valid for the specified screening list feature.
Recovery
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 and to the appropriate feature manual for assistance.
2.2.2003 E4500 Cmd Rej: IDPR must be ON or IAR Base must be enabled when SERV=TTR
The Prepaid IDP Query Relay (IDPR) feature must be turned on or the IAR Base feature must be enabled before a value of ttr can be specified for the nserv or serv parameter.
Recovery
2.2.2004 E4502 Cmd Rej: GTT must be ON before IDPR can be enabled
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.2005 E4505 Cmd Rej: Service parameters not supported when SERV=IDPR or TTR
Recovery
Re-enter the ent/chg/rtrv-srvsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Analyzed Information Features User's Guide and IDP-Related Features User's Guide for assistance.
2.2.2006 E4507 Cmd Rej: DEFCC must be provisioned
The defcc parameter must be provisioned before the Prepaid IDP Query Relay feature can be turned on.
2.2.2007 E4508 Cmd Rej: SEAS can only update translations with Default MRNSET/MAPSET
If a SEAS command is used, then the mrnset=dflt or mapset=dflt parameter must be specified.
Recovery
Re-enter the chg-gta or chg-gtt command that issued this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide, the Database Administration - GTT User's Guide, and Database Administration - SEAS User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2008 E4509 Cmd Rej: Translation entry already exists
The specified translation entry cannot already exist.
Recovery
- Display the existing translation entries. Enter the
rtrv-gtacommand. - Re-enter the
ent-gtacommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2009 E4510 Cmd Rej: Translation entry does not exist
For the chg/dlt-gta commands, the specified point code must already exist.
For the ent/chg-gttact-path command, a translation entry corresponding to the specified (opgttsn + opcode + pkgtype + acn/family)/(cgttsn + cggta(ecgtta))/cdgttsn +cdgta(ecdgta)) parameters must exist.
Recovery
- Display the existing point codes. Enter the
rtrv-gtacommand. - 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 and to the Database Administration - GTT User's Guide for assistance.
2.2.2010 E4511 Cmd Rej: CdPA GTT Set does not exist
The GTT set specified by the cdgtasn, cdgttsn, or gttsn parameter must already exist in the GTT Set table.
Recovery
- Display the existing GTT sets. Enter the
rtrv-gttsetcommand. - Re-enter the
ent/chg/rtrv-gttselcommand that generated this error message, specifiying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2011 E4513 Cmd Rej: CDGTASN/GTTSN cannot be specified as NONE
A value of none cannot be specified for the cdgtasn or gttsn parameters.
Recovery
Re-enter the chg-gttsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2012 E4514 Cmd Rej: CdPA and/or CgPA GTT Set can't be specified as NONE
A value of none cannot be specified for the gttsn, cdgtasn, cdgttsn, cggttsn, cggtasn, or cgpcsn parameter.
Recovery
Re-enter the chg/rtrv-gttsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2013 E4516 Cmd Rej: CgPA GTT set must not be specified
If a full GTT selector key is specified by the gti(x), tt, np/npv, nai/naiv, cgssn, selid, and lsn parameters, then the cgpcsn, cggtasn, and cggttsn parameters cannot be specified.
Recovery
Re-enter the rtrv-gttsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2014 E4517 Cmd Rej: CdPA GTT set must not be specified
If a full GTT selector key is specified by the gti(x), tt, np/npv, nai/naiv, selid, and lsn parameters, then the gttsn, cdgtasn, or cdgttsn parameters cannot be specified.
Recovery
Re-enter the rtrv-gttsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2015 E4518 Cmd Rej: SEAS output group cannot be turned OFF for SEAS terminal
If the specified terminal is a SEAS terminal then the SEAS output group cannot be turned off.
Recovery
2.2.2016 E4519 Cmd Rej: CdPA GTT Set type must be cdgta
The GTT Set specified by the cdgtasn or gttsn parameter must have a set type of cdgta.
Recovery
- Display the set types. Enter the
rtrv-gttsetcommand. - Change the set type if necessary. Refer to the Database Administration - GTT User's Guide for assistance.
- Re-enter the
ent/chg/rtrv-gttselcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.2017 E4522 Cmd Rej: OPCSN set domain must be the same as GTTSN set domain
The OPCSN set domain must be the same as the GTTSN set domain; i.e., if the GTTSN set domain is ANSI, then the OPCSN set domain must also be ANSI; and if the GTTSN set domain is ITU, then the OPCSN set domain must also be ITU.
Recovery
2.2.2018 E4523 Cmd Rej: MAPSET must be specified (only) if FGTTLS feature is enabled
If the Flexible GTT Load-Sharing (FGTTLS) feature is enabled, then the (n)mapset parameter must be specified. If the FGTTLS feature is not enabled, then the (n)mapset parameter cannot be specified.
Recovery
2.2.2019 E4524 Cmd Rej: Failed Reading MAP table
The MAP table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2020 E4525 Cmd Rej: Failed Reading RPC3 table
The RPC3 table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2021 E4526 Cmd Rej: MAP table is full
For the chg-map command, the mate point code in the command will exceed the maximum number of entries in the MAP table.
For the ent-map command, one or more point codes in the command will exceed the maximum number of entries in the MAP table.
Recovery
2.2.2022 E4527 Cmd Rej: Specified MAPSET does not exist
The value specified for the mapset parameter must already exist in the MAP table.
Recovery
2.2.2023 E4528 Cmd Rej: PC/SSN doesn't exist in MAPSET
For the ent/chg-gsmmap-scrn and ent/chg-gsms-opcode commands, if the value of the (n)mapset parameter is not dflt or if the (n)mapset=dflt and the force=no parameters are specified, then the values for the npc and nssn parameters must already be provisioned for the new MAP set.
For the ent/chg-gta, ent/chg-gtt, and ent/chg-gttact commands, the specified or previously provisioned PC/SSN must exist in the specified or previously provisioned MAP set.
For the chg/dlt/rtrv-map commands, the PC/SSN/MAPSET combination must already be provisioned in the MAP table.
Recovery
- Display the PC/SSN entries in the MAP table. Enter the
rtrv-mapcommand. - Add Point Code and SSN entries to the MAP set as desired. Refer to the Database Administration - GTT User's Guide for assistance
- 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 and to the Database Administration - GTT User's Guide for assistance.
2.2.2024 E4529 Cmd Rej: MAP entry is being referred by other entities
If the Flexible GTT Load Sharing (FGTTLS) feature is enabled, then a MAP entry cannot be deleted if the entry is referenced in the MRN, GTT, GTT Action, GSM MAP Opcode or GSM MAP Screening table using the MAPSET/PC/SSN combination, or if the entry is referenced in the MRN, GTT, GSM MAP Opcode, GSM MAP Screening, or PPSOPTS table using the MAPSET/PC combination, and the entry is the last entry in that MAP set with the specified point code.
If the FGTTLS feature is not enabled, then a MAP entry cannot be deleted if the entry is referenced in the GTT, GTT Action, GSM MAP Opcode or GSM MAP Screening table using the PC/SSN combination or if the entry is referenced in GTT, GSM MAP Opcode, GSM MAP Screening, or PPSOPTS table using the point code, and the entry is the last entry in the MAP table with the specified point code.
Recovery
2.2.2025 E4530 Cmd Rej: MAPSET must be specified if action is FORWARD/DUP/DUPDISC
If a value of forward, duplicate, or dupdisc is specified for the (n)dfltact parameter, then the (n)mapset parameter must be specified.
Recovery
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.
2.2.2026 E4531 Cmd Rej: NMAPSET must be specified if FORCE is specified
The nmapset parameter must be specified before the force parameter can be specified.
Recovery
Re-enter the chg-gsms-opcode or chg-gsmmap-scrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.2027 E4532 Cmd Rej: MAPSET must be specified (only) if RI parameter is SSN
The Flexible GTT Load-Sharing (FGTTLS) feature must be enabled and the ri=ssn parameter must be specified before the mapset parameter can be specified. If the FGTTLS feature is enabled and the ri=ssn parameter is specified, then the mapset parameter must be specified.
Recovery
2.2.2028 E4534 Cmd Rej: CSPC entry is being referred by other entities
The specified CSPC group cannot be deleted because it is being referenced by other RPC3/MAP table entries.
Note:
Error message E4534 is only generated if the Flexible GTT Load-Sharing (FGTTLS) feature is enabled. If the FGTTLS feature is not enabled, the following caution note is displayed:CSPC GROUP MAY BE IN USE BY A MATE APPLICATIONRecovery
2.2.2029 E4535 Cmd Rej: NDGT parameter mustn't be specified
If the settype parameter has a value of cdssn, cgpc, cgssn, opc, dpc, or opcode, then the ndgt parameter cannot be specified.
Recovery
Re-enter the ent/chg-gttset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2030 E4536 Cmd Rej: settype parameter must be specified
If the OBSR feature is enabled or the FLOBR feature is turned on, then the settype parameter must be specified.
Recovery
2.2.2031 E4537 Cmd Rej: Power Threshold entry already exists in FPT table
The value specified for the thrshld parameter cannot already exist in the Frame Power Threshold table.
Recovery
- Display the entries in the Frame Power Threshold table. Enter the
rtrv-frm-pwrcommand. - Re-enter the
ent-frm-pwrcommand that generated this error message, specifying a valid combination of parameters. Refer to the command definition in the Commands User's Guide for assistance.
2.2.2032 E4538 Cmd Rej: Power Threshold entry does not exist in FPT table
The value specified for the thrshld parameter must already exist in the Frame Power Threshold table.
Recovery
2.2.2033 E4539 Cmd Rej: Failed reading FPT table
The Frame Power Threshold table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2034 E4540 Cmd Rej: Failed reading Assembly Power table
The Assembly Power table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2035 E4541 Cmd Rej: Entered Frame must be a provisioned frame
The frame specified by the frm parameter must already be provisioned. The command description in Commands User's Guide lists the supported values for the frm parameter.
Recovery
2.2.2036 E4542 Cmd Rej: Failed deleting shelf as FPT entry is provisioned
If the equipment shelf is the only provisioned shelf in the frame, and a frame power threshold entry is configured in the Frame Power Threshold table for the frame, then the shelf cannot be deleted until the frame power threshold entry is deleted from the Frame Power Threshold table.
Recovery
2.2.2037 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
2.2.2038 E4544 Cmd Rej: The IDPS Feature must be enabled
The IDP Screening for Prepaid feature must be enabled before provisioning is allowed.
Recovery
2.2.2039 E4545 Cmd Rej: IDP Screening for Prepaid feature must be ON when SERV=IDPS
The IDP Screening for Prepaid feature must be turned on before the (n)serv=idps parameter can be specified.
Recovery
2.2.2040 E4546 Cmd Rej: GTT must be ON before IDPS can be enabled
The GTT feature must be turned on before the IDP Screening for Prepaid feature can be enabled.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.2041 E4548 Cmd Rej: Requested service parameters not supported when SERV=IDPS
If the (n)serv=idps parameter is specified, then the only valid mandatory service parameters are tt, serv, ssn, gtin, and gtii. The optional service selector parameters supported are np and nai.
Recovery
Re-enter the ent/chg-srvsel 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2042 E4549 Cmd Rej: EDATE/ETIME must be greater than system date/time
The values specified for the edate and etime parameters must be greater than the current system date and time.
Recovery
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.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2043 E4550 Cmd Rej: Both EDATE and ETIME parameters are required
If the dur=timed parameter is specified, then the edate and etime parameters must be specified.
Recovery
Re-enter the inh-alm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.2044 E4551 Cmd Rej: DISPLAY parameter is mandatory with DUR parameter
If the dur parameter is specified, then the display parameter must be specified.
Recovery
Re-enter the rept-stat-alm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.2045 E4554 Cmd Rej: DEV must be either SLK, LS or ROUTE if CLLI is specified
If the clli parameter is specified, then a value of slk, ls, or route must be specified for the dev parameter.
Recovery
Re-enter the rept-stat-alm command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.2046 E4555 Cmd Rej: Version parameter not supported for SUA or M3UA
The ver parameter only supports M2PA adapters.
Recovery
2.2.2047 E4556 Cmd Rej: Timer not supported for M2PA Draft 6
The specified timer must be supported by M2PA Draft 6 (ver=d6).
Recovery
2.2.2048 E4557 Cmd Rej: Timer value or SRCTSET required
A timer value parameter or the srctset parameter must be specified.
If the srctset parameter is specified, then no other timer values can be specified. The value specified for the timer set parameter cannot be the same as the value specified for the tset parameter.
Recovery
2.2.2049 E4560 Cmd Rej: CGSSNSN set domain must be the same as GTTSN set domain
The values specified for the gttsn and cgssnsn parameters must have the same domain (ANSI or ITU).
Recovery
2.2.2050 E4562 Cmd Rej: MOSMSGTTDIG option must be SCCPCdPA
The mosmsgttdig=sccpcdpa parameter must be specified before the bpartygttsn=none parameter can be specified.
Recovery
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.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2051 E4563 Cmd Rej: IPGW linksets not supported for proxy destinations
If an IPGW linkset is used, then the value specified for the apc parameter cannot be associated with a proxy point code.
Recovery
2.2.2052 E4565 Cmd Rej: SCCP Loop Detection Feature is not enabled
For the ent/chg-gta, ent/chg-gtt, and ent/chg/rtrv-gttact commands, the SCCP Loop Detection feature must be enabled before the loopset parameter can be specified.
The SCCP Loop Detection feature must be enabled before the ent/chg/dlt/rtrv-loopset commands can be entered.
Recovery
2.2.2053 E4566 Cmd Rej: LoopSet Table is full
The Loopset table can hold a maximum of 1000 loopsets. Each loopset can have a maximum of 12 point code entries for a total maximum of 12000 point codes.
Recovery
2.2.2054 E4567 Cmd Rej: Cannot access LoopSet table
The Loopset table is corrupt or cannot be found by the system. The Loopset table must be accessible.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2055 E4568 Cmd Rej: Loop Set entry does not exist
The specified loopset entry must already exist in the Loopset table.
Recovery
- Display all the loopsets in the Loopset table. Enter the
rtrv-loopset:num=1000:force=yescommand. - Re-enter the command that generated this error message, specifying an entry that exists in the Loopset table.
2.2.2056 E4569 Cmd Rej: Cannot delete loopset when in use by GTT
A loopset entry that is being referenced by the GTT feature cannot be deleted.
Recovery
2.2.2057 E4570 Cmd Rej: Point Code in use by GTT Force parameter required
The force=yes parameter must be specified to delete a point code entry that is in use by GTT.
Recovery
Re-enter the dlt-loopset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2058 E4571 Cmd Rej: Addition of these pointcodes will exceed the pc limit
A maximum of 6 point codes can be added using the chg-loopset command with the apcl parameter. The loopset entry can contain a maximum of 12 point codes.
Recovery
2.2.2059 E4572 Cmd Rej: Requires force since Loopset is in use by GTT
The force parameter must be specified to modify a loopset that is being referenced by the GTT feature.
Recovery
2.2.2060 E4573 Cmd Rej: PC2 parameter requires PC1 parameter
If the pc2 parameter is specified, then the pc1 parameter must be specified.
Recovery
Re-enter the chg-loopset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - GTT User's Guide for assistance.
2.2.2061 E4574 Cmd Rej: NPC1/NPC2 requires use of PC1/PC2
If the npc1/npc2 parameters are specified, then the pc1/pc2 parameters must be specified.
Recovery
Re-enter the chg-loopset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - GTT User's Guide for assistance.
2.2.2062 E4575 Cmd Rej: Replace and Append Point Code lists are mutually exclusive
The rpcl parameter and apcl parameters cannot be specified together in the command.
Recovery
Re-enter the chg-loopset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2063 E4576 Cmd Rej: PC1/PC2 cannot be used with either Point Code list
The pc1/pc2 parameters cannot be specified in the same command with the rpcl or apcl parameter.
Recovery
Re-enter the chg-loopset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2064 E4577 Cmd Rej: Loop Set entry already exists
The value specified for the loopset parameter cannot already exist in the database.
Recovery
2.2.2065 E4579 Cmd Rej:MTPLPRST option must be on
For the chg-stpopts command, if the Origin-based MTP Routing feature is enabled, then the mtplprst=no parameter cannot be specified.
For the enable-ctrl-feat command, the mtplprst=yes parameter must be specified (see the chg-stpopts command) before the Origin-based MTP Routing feature can be enabled.
Recovery
2.2.2066 E4580 Cmd Rej: CIC must be specified if ECIC is specified
If the ecic parameter is specified, then the cic parameter must be specified.
For the ent/dlt/rtrv-pct commands, if the or rcice parameter is specified, then the ecics or rcics parameter must be specified, respectively.
Recovery
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.
2.2.2067 E4581 Cmd Rej: Unsupported Hardware is equipped in the system
The feature is mutually exclusive with hardware in the system. Refer to the command description in Commands User's Guide for a list of mutually exclusive features and hardware.
Recovery
2.2.2068 E4582 Cmd Rej: Single rte to APC or SAPC for IPGW LS allowed
For the ent/chg-rte commands, more than one route cannot be assigned to an APC or SAPC for an IPGWx linkset.
For the chg-ls command, an APC or SAPC cannot be assigned to an IPGWx linkset that is already assigned to a route involving another linkset.
For the ent-ls command, an APC cannot be assigned to an IPGWx linkset that is already assigned to a route involving another linkset.
Recovery
- Display the routes and associated linksets. Enter the
rtrv-rtecommand. - 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 and to the Database Administration - SS7 User's Guide for assistance.
2.2.2069 E4583 Cmd Rej: DISPLAY parameter is mandatory with FRM parameter
If the frm parameter is specified, then the display parameter must be specified.
Recovery
Re-enter the rtrv-stp command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - System Management User's Guide for assistance.
2.2.2070 E4584 Cmd Rej: MTP Origin Based Routing Feature must be ON
The MTP Origin Based Routing feature must be enabled and turned on before the ent/chg/dlt/rtrv-rtx command can be entered or the rept-stat-rte:mode=rtx parameter can be specified.
Recovery
2.2.2071 E4585 Cmd Rej: Failed reading SCCP service table
The SCCP Service table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2072 E4586 Cmd Rej: Invalid combination of new and existing point codes
Either all of the specified point codes, (pc1/pc2/pc3/pc4 parameter) must already exist or none of the specified point codes can exist.
Note:
When adding new point codes, none of the point codes that are specified in one command can already exist in the SCCP-SERV group in the SCCP-SERV table, and all of the point codes must be added to the same SCCP-SERV group.Recovery
- Display the point codes associated with the services. Enter the
rtrv-sccp-servcommand. - Re-enter the
chg-sccp-servcommand that generated this error message, specifying a valid combination of point codes. Refer to the command description in Commands User's Guide and to the G-Port User's Guide for assistance.
2.2.2073 E4587 Cmd Rej: At least one point code must be specified
At least one point code must be specified in the command.
Recovery
Re-enter the dlt-sccp-serv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the appropriate feature manual for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2074 E4589 Cmd Rej: SCCP-SERV allocation within MRN table is full
For each supported service (G-Port and G-Flex), up to 7 point codes can be specified for each network type (ANSI, ITU-I, S-ITU-I, ITU-N, S-ITU-N, and ITU-N24).
Recovery
2.2.2075 E4590 Cmd Rej: Maximum point codes have been allocated to SCCP-SERV set
An SCCP service group can contain up to 7 point codes.
Recovery
2.2.2076 E4591 Cmd Rej: PC must already exist in the SCCP-SERV set
The specified point code must already exist in the specified SCCP service group.
Recovery
2.2.2077 E4594 Cmd Rej: Feature associated with SERV must be ON or enabled
The G-Flex feature must be enabled before the serv=gflex parameter can be specified.
The G-Port feature must be enabled before the serv=gport parameter can be specified.
The A-Port or IGM feature must be enabled and turned on before the serv=mnp parameter can be specified.
Recovery
2.2.2078 E4595 Cmd Rej: Only one E1/T1 port allowed for Linkclass=Unchan
For the ent-e1 command, only 1 port can be used for E1 interfaces on an E5-E1T1 card that is used as an SE-HSL card. Any 1 of the 8 ports can be used on the SE-HSL card.
For the ent-t1 command, only 1 of the 8 ports can be used for T1 interfaces on an E5-E1T1 card that is used as an ST-HSL-A card.
Recovery
2.2.2079 E4596 Cmd Rej: Point Code does not exist in the Loopset Table entry
The value specified for the pc1 or pc2 parameter must exist in the Loopset table.
Recovery
2.2.2080 E4597 Cmd Rej: RTKEY DPC cannot be IPGWx APC or SAPC
For the ent-appl-rtkey command, a destination point code (DPC) cannot be specified for a routing key if the DPC is the adjacent node (APC) or Secondary Adjacent Point Code (SAPC) for an IPGW linkset.
For the ent/chg-ls command, an IPGW linkset cannot be provisioned if the linkset contains an APC or SAPC that is already configured in a routing key.
Recovery
2.2.2081 E4598 Cmd Rej: Routing Context not configured
The value of the nrcontext parameter cannot be changed for a routing key if the rcontext parameter has not been configured for that routing key.
Recovery
2.2.2082 E4600 Cmd Rej: Must specify ASNAME or RC
Either the asname or rc parameter must be specified in the command.
Recovery
Re-enter the ent-appl-rtkey command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.2083 E4602 Cmd Rej: Requested Assoc Buffer Space Exceeds Available Buffer Space.
The requested buffer size cannot exceed available buffer space for the card type.
Table 2-7 Default Buffer Configuration Sizes
| Card | Default Buffer Size (KB) | Minimum Buffer Size (KB) | Maximum Buffer Size (KB) |
|---|---|---|---|
|
E5-ENET/E5-ENET-B/ IPLIM |
200 |
8 |
400 |
|
E5-ENET/E5-ENET-B/ IPGW |
16 |
8 |
400 |
Recovery
2.2.2084 E4605 Cmd Rej: Loopset Name and display type list are mutually exclusive
If the name parameter is specified, then the disp=list parameter cannot be specified.
Recovery
Re-enter the rtrv-loopset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2085 E4606 Cmd Rej: Point code type mismatch
For the chg-loopset command, when adding point codes using the apcl parameter, or changing individual point codes using the pc1/npc1 or pc1/npc2 parameters, the new point code type must match the point code type of the loopset entry to which these point codes are being added or changed.
For the ent/dlt/rtrv-pct commands, the values specified for the epc/epca/epci/epcn, filtpc/filtpca/filtpci/filtpcn, and realpc/realpca/realpci/realpcn parameters must have the same domain.
Recovery - chg-loopset
- Display the existing point code types. Enter the
rtrv-loopsetcommand. - Re-enter the
chg-loopsetcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - GTT User's Guide for assistance.Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - ent/chg/dlt-pct
2.2.2086 E4607 Cmd Rej: Linkset referenced by exception historic route
A linkset that is being used by an exception route cannot be deleted.
Recovery
2.2.2087 E4608 Cmd Rej: True Point Code can exist only in Default MAPSET
A true PC/SSN can only exist in the default MAP Set.
Recovery
2.2.2088 E4613 Cmd Rej: Failed Reading SEASCFG Table
The SEASCFG table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2089 E4614 Cmd Rej: SOIP Feature must be Enabled
The SEAS Over IP (SOIP) feature must be enabled before the chg/rtrv-seas-config commands can be entered.
For the chg-trm command, the SOIP feature must be enabled before the type=seas parameter can be specified.
Recovery
2.2.2090 E4615 Cmd Rej: SEAS Terminal Not Inhibited
For the chg-seas-config command, the SEAS terminal must be inhibited before the seasclli, ipaddr, port, login, hname, or authmode parameter can be specified.
For the chg-trm command, the SEAS terminal must be inhibited before the type=seas parameter can be specified.
Recovery
2.2.2091 E4616 Cmd Rej: SEAS Terminal Not Configured
At least one SEAS terminal must be configured before the SEAS Over IP feature can be turned on.
Recovery
2.2.2092 E4617 Cmd Rej: SEAS Terminal is Auto-Inhibited
The specified terminal cannot be an auto-inhibited SEAS terminal.
Recovery
2.2.2093 E4618 Cmd Rej: STPOPTS DefCC must not be NONE
For the chg-ctrl-feat command, the DEFCC system option (see the chg-stpopts command) must be provisioned with a value other than none before the ATINP, MT-Based GSM SMS NP, or MT-Based IS41 SMS NP feature can be turned on.
For the enable-ctrl-feat command, the DEFCC system option must be provisioned with a value other than none before the IAR Base feature can be enabled.
Recovery
2.2.2094 E4619 Cmd Rej: Failed Reading IPTERM Table
The IPTERM table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2095 E4620 Cmd Rej: E5-IPSM Card is not Present
For the chg-ctrl-feat command, all card locations that correspond to SEAS terminals must be provisioned with IPSM cards before the SEAS Over IP feature can be turned on.
For the chg-trm command, If the SEAS Over IP (SOIP) feature is turned on, then an IPSM card must be provisioned at the location corresponding to the specified SEAS terminal.
Recovery
2.2.2096 E4621 Cmd Rej: PCX and NPCX must be unique
If the npc1/pc1 or npc2/pc2 parameters are specified together, then the value of the npc parameter cannot equal the value of the pc parameter.
Recovery
Re-enter the chg-loopset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2097 E4622 Cmd Rej: PC1 and PC2 must be unique
Equal values cannot be specified for the pc1 and pc2 parameters.
Recovery
Re-enter the chg-loopset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2098 E4623 Cmd Rej: NPC1 and NPC2 must be unique
Equal values cannot be specified for the npc1 and npc2 parameters.
Recovery
Re-enter the chg-loopset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2099 E4624 Cmd Rej: PCs in point code list must be unique
For the chg-loopset command, the values specified for the apcl and rpcl parameters must be unique.
For the dlt/ent-loopset command, the values for the pcl parameter must be unique.
Recovery
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.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2100 E4625 Cmd Rej: PC already exists in the loopset entry
The value of the apcl parameter cannot already exist in the loopset.
Recovery
- Use the
rtrv-loopsetcommand to retrieve loopset data from the database. - Re-enter the
chg-loopsetcommand that generated this error message, specifying a valid value for the apcl parameter.
Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2101 E4626 Cmd Rej: Must have at least 1 valid PC in a point code list
For the chg-loopset command, at least one valid point code must be specified as a value for the apcl and rpcl parameters.
For the dlt/ent-loopset command, at least one valid point code must be specified as a value for the pcl parameter.
Recovery
Re-enter the command that generated this error message, specifying at least one valid point code. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2102 E4627 Cmd Rej: Valid point codes must be continuous in point code list
For the chg-loopset command, the values for the apcl and rpcl parameters cannot include any invalid point codes.
For the dlt/ent-loopset command, the values for the pcl parameter cannot include any invalid point codes.
Recovery
Re-enter the command that generated this error message, specifying valid point codes consecutively and separated by commas. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2103 E4628 Cmd Rej: NONE is an invalid name for a loopset entry
The name=none parameter cannot be specified.
Recovery
Re-enter the command that generated this error message, specifying a valid name. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2104 E4629 Cmd Rej: RI/SETID must not be specified when PC/PCA/PCI/PCN=none
If a value of none is specified for the pc, pca, pci, or pcn parameter, then the ri or setid parameter cannot be specified.
Recovery
2.2.2105 E4631 Cmd Rej: Multiple Linksets to Single Adjacent PC feature must be ON
The Multiple Linksets to Single Adjacent PC (MLS) feature must be enabled and turned on before the spc parameter can be specified.
Recovery
2.2.2106 E4632 Cmd Rej: Max linksets to same APC exceeded
A maximum of 1 IPGW linkset or maximum of 6 of any other linksets are allowed between any APC and the EAGLE.
Recovery
2.2.2107 E4633 Cmd Rej: SPC may not be referenced in the STP's linkset table
A secondary point code that is referenced in the Linkset table cannot be deleted.
Recovery
2.2.2108 E4634 Cmd Rej: No change in APC actually requested
The adjacent point code specified by the apc parameter must differ from the APC value for the linkset specified by the lsn parameter.
Recovery
2.2.2109 E4635 Cmd Rej: No change in SPC actually requested
For the chg-ls command, the point code specified by the spc parameter must differ from the SPC value for the linkset specified by the lsn parameter.
For the chg-dstn command, the value specified for the spc parameter must differ from the SPC of the destination/route entry specified by the dpc parameter.
Recovery
2.2.2110 E4636 Cmd Rej: SPC may not exist as an SPC in the route table for the APC
The value specified for the spc parameter cannot already be specified as a secondary point code for an adjacent destination point code.
Recovery
2.2.2111 E4637 Cmd Rej: APC has no assigned linksets
At least one linkset must be associated with the point code specified by the apc parameter.
Recovery
2.2.2112 E4638 Cmd Rej: SPC may not exist as an SPC in the linkset table for the DPC
Recovery
- Enter the
rtrv-dstncommand to display the destination point codes in the database. - Re-enter the
chg-dstncommand that generated this error message, specifying a valid value for the spc parameter.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2113 E4639 Cmd Rej: Only 1 IPGW linkset supported by a single APC
An IPGW linkset cannot be assigned to a node that already contains a linkset.
Recovery
2.2.2114 E4641 Cmd Rej: VFLEX feature must be enabled
The V-Flex feature must be enabled before the command can be entered.
Recovery
2.2.2115 E4642 Cmd Rej: Unable to read Routing Number table
The Routing Number table is corrupt or cannot be found by the system.
Recovery
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2116 E4643 Cmd Rej: Routing Number table is full
The maximum number of entries was reached in the Routing Number table. The Routing Number table cannot contain more than 10,000 entries.
Recovery
2.2.2117 E4644 Cmd Rej: (N)RNNAME already exists in the database
The value specified for the nrnname or rnname parameter cannot already exist in the Routing Number table.
Recovery
- Display the current values in the Routing Number table. Enter the
rtrv-vflx-rncommand. - Re-enter the
ent/chg-vflx-rncommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the V-Flex User's Guide for assistance.
2.2.2118 E4645 Cmd Rej: (N)RN already exists in the database
The value specified for the nrn/rn parameter cannot already exist in the Routing Number table.
Recovery
- Display the current values in the Routing Table. Enter the
rtrv-vflx-rncommand. - Re-enter the
ent/chg-vfx-rncommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the V-Flex User's Guide for assistance.
2.2.2119 E4646 Cmd Rej: RNNAME doesn't exist in the database
The value specified for the rnname parameter must already exist in the Routing Number table.
Recovery
- Display the current values in the Routing Number table. Enter the
rtrv-vflx-rncommand. - Re-enter the command that generated this error message, specifying a valid combination of values. Refer to the command description in Commands User's Guide and to the V-Flex User's Guide for assistance.
2.2.2120 E4647 Cmd Rej: RN doesn't exist in the database
The value specified for the rn parameter must already exist in the Routing Number table.
Recovery
- Display the entries in the Routing Number table. Enter the
rtrv-vflx-rncommand. - Re-enter the
rtrv-vflx-rncommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the V-Flex User's Guide for assistance.
2.2.2121 E4648 Cmd Rej: RN entry is being referred by other entities
The value specified for the rnname parameter cannot be referenced by an entry in the VMSID table.
Recovery
2.2.2122 E4649 Cmd Rej: Entry with RDI, DNSTAT, BCAP, (N)VMDIG already exists
The value specified for the (n)vmdig parameter cannot already exist in the Call Decision table with the same dnstat, rdi, and bcap values.
Recovery
- Display the current values in the Call Decision table. Enter the
rtrv-vflx-cdcommand. - Re-enter the
ent/chg-vflx-cdcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the V-Flex User's Guide for assistance.
2.2.2123 E4650 Cmd Rej: MT-Based IS41 SMS NP must be enabled
The MT-based IS41 SMS NP feature must be enabled before the mtsmsdnfmt, mtsmstype, mtsmsparm, mtsmsdltr, mtsmsdltrv, mtsmsackn, mtsmsesn, mtsmsssn, mtsmsnakerr, mtsmsdigtype, or mtsmschksrc parameter can be specified.
Recovery
2.2.2124 E4651 Cmd Rej: Invalid adapter for specified association
An association with adapter=sua or adapter=m3ua cannot be specified as a value for the lhost parameter on a card running the IPLIM or IPLIMI or application.
An association with adapter=m2pa cannot be specified as a value for the lhost parameter on a card running the SS7IPGW or IPGWI application.
An association with adapter=sua cannot be specified as a value for the lhost parameter on a card running the IPSG application.
Recovery
2.2.2125 E4652 Cmd Rej: Error while reserving disk
The command could not reserve the disk-under-test; the disk is unresponsive.
Recovery
-
Make sure no other disk operation is in progress (audit, database backup, or database restore). If so, wait for the operation to complete.
- Re-enter the command that generated this error message. If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4
2.2.2126 E4653 Cmd Rej: Could not reserve disk
The disk-under-test could not be reserved to perform the requested operation; the disk is unavailable or busy.
Recovery
-
Make sure no other disk operation is in progress (audit, database backup, or database restore). If so, wait for the operation to complete.
- Re-enter the command that generated this error message. If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4
2.2.2127 E4654 Cmd Rej: Error issuing TST-DISK request
Error occurred while accessing disk during tst-disk.
Recovery
-
Make sure no other disk operation is in progress (audit, database backup, or database restore). If so, wait for the operation to complete.
- Re-enter the command that generated this error message. If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4
2.2.2128 E4655 Cmd Rej: MT-Based GSM MMS NP must be enabled
The MT-Based GSM MMS NP feature must be enabled before the mtmmsgta, mtmmstype, mtmmsentylen, mtmmslen, or mtmmsackn parameter can be specified.
Recovery
2.2.2129 E4656 Cmd Rej: Similar entry exists with different DNSTAT value
The value specified for the nvmdig/vmdig parameter cannot differ from a value that already exists in the Call Decision table by only the value of the dnstat parameter. The values specified for the rdi and bcap parameters must differ as well.
- Display the values that exist using the
rtrv-vflx-cdcommand. - 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 and to V-Flex User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2130 E4657 Cmd Rej: IPGWAPC and IPSG cannot both be YES
The ipgwapc=yes and ipsg=yes parameters cannot be specified together in the command.
Recovery
2.2.2131 E4658 Cmd Rej: ADAPTER can only be specified when IPSG=YES
The ispg=yes parameter must be specified before the adapter parameter can be specified.
Recovery
2.2.2132 E4659 Cmd Rej: RCONTEXT prohibited unless IPSG=YES and ADAPTER=M3UA
The rcontext parameter can be specified only for IPSG-M3UA linksets.
Recovery
2.2.2133 E4660 Cmd Rej: No change in RC actually requested
The route cost specified by the rc parameter must differ from the existing route cost for the linkset specified by the lsn parameter.
Recovery
2.2.2134 E4661 Cmd Rej: VMS ID does not exist in the database
The value specified for the id parameter must already exist in the VMSID table.
Recovery
2.2.2135 E4662 Cmd Rej: GSMOPTS DefMCC must not be NONE
The defmcc parameter (see the chg-gsmopts command) must be provisioned before the MT-Based GSM SMS NP feature can be turned on.
Recovery
2.2.2136 E4663 Cmd Rej: Failed reading VMSID table
The VMSID table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2137 E4664 Cmd Rej: VMS ID already exists in the database
The value specified for the id parameter cannot already exist in the VMSID table.
Recovery
- Display the current values by using the
rtrv-vflx-vmsidcommand. - Re-enter the command that generated this error message, specifying a valid id parameter.
Refer to the command descriptions in Commands User's Guide for assistance. If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2138 E4665 Cmd Rej: <RN Name> does not exist in the Routing Number table
For the chg-vflx-vmsid command, the routing number name of the entry specified by the id parameter must already exist in the routing number table.
For the ent-vflx-vmsid command, the values specified by the idx* parameters must already exist in the routing number table.
For the rtrv-vflx-vmsid command, the value specified by the rnname parameter must already exist in the routing number table.
Recovery
- Search for the missing value by using the
rtrv-vflx-rn:rnname=<name>command. - If the RN entry is not present, create it and then re-enter the original command. If the RN entry is present, re-enter the original command.
Refer to the command descriptions in Commands User's Guide and to V-Flex User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2139 E4666 Cmd Rej: ASNOTIF prohibited unless IPSG=YES and ADAPTER=M3UA
The asnotif parameter can be specified only for IPSG M3UA linksets (the ipsg=yes and adapter=m3ua parameters are specified).
Recovery
2.2.2140 E4667 Cmd Rej: IPSG=YES and ADAPTER=M3UA requires LST=A
The lst=a parameter must be specified for IPSG M3UA linksets (the ipsg=yes and adapter=m3ua parameters are specified).
Recovery
2.2.2141 E4669 Cmd Rej: SPC parameter is not supported by IPGW linksets
If the ipgwapc parameter is specified, then the spc parameter cannot be specified.
Recovery
2.2.2142 E4671 Cmd Rej: VMSID table is full
The VMSID table contains a maximum of 1000 entries.
Recovery
- Display the number of provisioned entries in the table. Enter the
rtrv-tbl-capacitycommand. - Delete entries if necessary. Refer to the V-Flex User's Guide for assistance.
- Re-enter the
ent-vflx-vmsidcommand that generated this error message.
2.2.2143 E4672 Cmd Rej: Login, Password, and Host must be set in SEASCFG
The login and hname parameters must be provisioned (see the chg-seas-config command) before the SEAS Over IP feature can be turned on
Recovery
2.2.2144 E4673 Cmd Rej: CCSMR Server password must be 1-15 characters in length
The value of the password requested by the login parameter must be from 1 - 15 alphanumeric charecters in length.
Recovery
Re-enter the chg-seas-config command that generated this error message, specifying a password that is from 1 - 15 alphanumeric characters in length.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2145 E4674 Cmd Rej: STP True PC and VFLEX Subsystem does not exist in MAP Table
If the V-Flex feature is turned on, then the STP true point code and V-Flex subsystem must exist in the MAP table.
Recovery
- Display the values that exist in the MAP table using the
rtrv-mapcommand to verify the presence of the true point code and VFLEX subsystem. If these do not exist they must be created. - Re-enter the command that generated this error message.
Refer to the command descriptions in Commands User's Guide and to V-Flex User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2146 E4677 Cmd Rej: PRX allowed only if PPC feature is enabled
The Proxy Point Code feature must be enabled before the prx parameter can be specified.
Recovery
2.2.2147 E4678 Cmd Rej: PPC allowed only if PPC feature is enabled
The Proxy Point Code feature must be enabled before the ppc parameter can be specified.
Recovery
2.2.2148 E4681 Cmd Rej: SPC and PPC are mutually exclusive
The spc and ppc parameters cannot be specified together in the command.
Recovery
Re-enter the ent-dstn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.2149 E4682 Cmd Rej: PPC and DPC must be of the same network type
The dpc and ppc parameters must be of same network type.
Recovery
Re-enter the ent-dstn command that caused this error to occur, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.2150 E4683 Cmd Rej: Group code of PPC and DPC must match
The dpc and ppc parameters must have the same group code.
Recovery
Re-enter the ent-dstn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.2151 E4684 Cmd Rej: Allowed Proxy PC capacity exceeded
The total number of proxy destinations cannot exceed the value given by the enabled Proxy Point Code quantity feature.
Recovery
- Determine the Proxy Point Code quantity that is enabled. Enter the
rtrv-ctrl-featcommand. - To enable a higher value than allowed by the feature quantity, you must be entitled to use a higher quantity feature must be purchased. Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2152 E4685 Cmd Rej: PPC referred by other entities
The prx=no parameter cannot be specified if linksets or other entries of the Route (DSTN) table refer to the destination point code as a proxy point code.
Recovery
- Display the entries in the DSTN table for the destination point code of interest. Enter the
rtrv-dstn:dpc=command. - Change the reference for the destination point code as necessary. Refer to the Database Administration - SS7 User's Guide for assistance.
- Re-enter the
ent/chg-dstncommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance
2.2.2153 E4686 Cmd Rej: PPC not supported for IPGWx DPC
The ipgwapc=yes and ppc=yes parameters cannot be specified together in the command.
Recovery
Re-enter the ent-dstn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.2154 E4687 Cmd Rej: PRX=YES not supported for IPGWx DPC
The ipgwapc=yes and prx=yes parameters cannot be specified together in the command.
Recovery
Re-enter the ent-dstn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.2155 E4688 Cmd Rej: LST=PRX if & only if APC uses PPC in route(dstn) table
The value specified for the proxy point code must be defined in the Destination table before the lst=prx parameter can be specified.
Recovery
2.2.2156 E4689 Cmd Rej: PPC must be specified if and only if linktype is PRX
The lst=prx parameter must be specified before the ppc parameter can be specified. If the lst=prx parameter is specified, then the ppc parameter must be specified.
Recovery
Re-enter the ent-ls command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.2157 E4690 Cmd Rej: Cannot use one PPC for more than 10 linksets
A maximum of 10 linksets can reference a proxy point code.
Recovery
2.2.2158 E4691 Cmd Rej: Two point codes must not refer each other as PPC
Two adjacent point codes cannot reference each other as proxy point codes.
Recovery
2.2.2159 E4692 Cmd Rej: One LS must use PPC assigned to APC in route (dstn) table
For the dlt-ls command, if multiple linksets and a proxy point code are defined for an APC, then the proxy linkset must be the final linkset that is deleted.
For the ent-ls command, if multiple linksets and a proxy point code are defined for an APC, then the first linkset defined in the command must use the proxy point code.
Recovery
- Display the linksets defined for the APC. Enter the
rtrv-lscommand. - Re-enter the command that generated the error message. Refer to the command description in Commands User's Guide and to the to the Database Administration - SS7 User's Guide for assistance.
2.2.2160 E4693 Cmd Rej: Command not allowed for proxy links
The act/canc-lpo, blk-slk, and dlt-dstn commands cannot be specified for links belonging to proxy linksets
Recovery
2.2.2161 E4694 Cmd Rej: APC must not use SPC and PPC together
The spc and ppc parameters cannot be specified together in the command.
Recovery
Re-enter the ent-ls command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.2162 E4695 Cmd Rej: LST=PRX is valid only if PPC feature is enabled
The Proxy Point Code feature must be enabled before the lst=prx parameter can be specified.
Recovery
2.2.2163 E4696 Cmd Rej: PPC must be a full point code
The value specified for the ppc parameter must be a full point code.
Recovery
2.2.2164 E4697 Cmd Rej: PPC and APC must be of the same network type
The values specified for the apc and ppc parameters must have the same network type.
Recovery
2.2.2165 E4698 Cmd Rej: Group code of PPC and APC must match
The group codes assigned to the values specified for the apc and ppc parameters must be of the same network type.
Recovery
2.2.2166 E4699 Cmd Rej: Parameter cannot be specified for proxy linksets
If a proxy linkset is used, then the apc, sapc, action, and lst parameters cannot be specified.
Recovery
2.2.2167 E4700 Cmd Rej: APORT must be ON
The A-Port feature must be turned on before the MO- or MT-based IS41 SMS NP feature can be turned on.
Recovery
2.2.2168 E4701 Cmd Rej: MT-Based GSM SMS NP must be enabled
For the chg-gsmsmsopts command, the MT-Based GSM SMS NP feature must be enabled before the mtsmsimsi, mtsmsnni, mtsmstype, mtsmsackn, mtsmsdltr, mtsmsdltrv, mtsmsnakerr, mtsmschksrc or srismdn parameter can be specified.
For the enable-ctrl-feat command, the MT-Based GSM SMS NP feature must be enabled before the MT-Based GSM MMS NP feature can be enabled.
Recovery
2.2.2169 E4702 Cmd Rej: MNP SMS must be ON or MO/MT SMS feature must be enabled
ent-home-smsc command can be entered:
- MO SMS IS41-to-GSM Migration
- MO-based GSM SMS NP
- MO-based IS41 SMS NP
- MT-Based GSM SMS NP
- MT-Based IS41 SMS NP
Recovery
2.2.2170 E4703 Cmd Rej: MNP SMS, MO/MT SMS NP or MO SMS IS412GSM Migr must be enbld
One of the following features must be enabled before the dlt/rtrv-home-smsc command can be entered:
- MO SMS IS41-to-GSM Migration
- MO-based GSM SMS NP
- MO-based IS41 SMS NP
- MT-Based GSM SMS NP
- MT-Based IS41 SMS NP
- Portability Check for Mobile Originated SMS
Recovery
2.2.2171 E4706 Cmd Rej: Maximum number of entries already exist for RDI,DNSTAT,BCAP
The maximum number of 25 entries cannot already be provisioned for a given rdi, dnstat and bcap.
Recovery
- Use the
rtrv-vflx-cdand thedlt-vflx-cdcommands to retrieve and delete some of the entries. - Re-enter the command that generated this error message.
Refer to the command descriptions in Commands User's Guide and to V-Flex User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2172 E4707 Cmd Rej: PRX using DPC not allowed in GTT, MAP, MRN tables
The value specified for the pc/pca/pci/pcn parameter cannot be associated with a proxy point code.
Recovery
2.2.2173 E4708 Cmd Rej: One route must use PPC assigned in route (dstn) table
For the chg-rte command, if a proxy linkset is used, then the nlsn parameter cannot be specified.
For the dlt-rte command, if multiple routes are assigned to a point code, then the route that uses the proxy linkset must be the final route that is deleted.
For the ent-rte command, if multiple routes are defined for the destination point code, and if a proxy point code is assigned to the destination point code, then the first route defined in the ent-rte command must use the proxy linkset.
Recovery
2.2.2174 E4709 Cmd Rej: Cannot set DefCC to NONE if MT-Based GSM SMS NP is ON
If the MT-Based GSM SMS NP feature is turned on, then the defcc=none parameter cannot be specified.
Recovery
2.2.2175 E4710 Cmd Rej: Unable to read VFLEX Options Table
The V-Flex options table is corrupt or cannot be read by the system.
Recovery
Re-enter the command that generated this error message.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2176 E4711 Cmd Rej: NEQUERYONLY option must be ON
The nequeryonly=on parameter must be specified before the netype parameter can be specified.
Recovery
- Display the current parameters using the
rtrv-vflx-optscommand. - If nequeryonly=off is specified, set nequeryonly to on.
- Re-enter the command that generated this error message.
Refer to the command descriptions in Commands User's Guide and to V-Flex User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2177 E4713 Cmd Rej: PRX using DPC not allowed in GSM tables
If the (n)action or (n)dfltact parameter has a value of forward, duplicate, or dupdisc, then the value specified for the point code parameter cannot be associated with a proxy point code in the Route table
- Display the parameter values for the relevant command. Enter the
rtrv-gsmmap-scrnor thertrv-gsms-opcodecommand. - Display the entries in the Route table. Enter the
rtrv-rtecommand. - Re-enter the
ent/chg-gsmmap-scrnorent/chg-gsms-opcodecommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.2178 E4714 Cmd Rej: PPC not supported for IPGW Linksets
If the ipgwapc=yes parameter is specified, then the ppc parameter cannot be specified.
Recovery
Re-enter the ent-ls command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.2179 E4716 Cmd Rej: LNP/VFLEX/EIR/INP must be ON or ATINP/AIQ must be enabled
The LNP, V-Flex, EIR, or INP feature must be turned on or the ANSI41 AIQ or ATINP feature must be enabled before the value specified for the pca/mpca parameter can be a true point code.
Recovery
2.2.2180 E4717 Cmd Rej: EIR/VFLEX feature must be ON or ATINP/AIQ must be enabled
The EIR or V-Flex feature must be turned on or the ATINP or AIQ feature must be enabled before the value specified for the pci/mpci parameter can be a true point code.
Recovery
2.2.2181 E4718 Cmd Rej: DefMCC can't be NONE if MT-Based GSM SMS NP feature is ON
If the MT-Based GSM SMS NP feature is turned on, then the defmcc=none parameter cannot be specified.
Recovery
2.2.2182 E4720 Cmd Rej: MTSMSDLTRV must not be NONE in database
A value for the mtsmsdltrv parameter must be specified before a value of either prern or postrn can be specified for the mtsmsdltr parameter.
Recovery
Re-enter the chg-gsmsmsopts or chg-is41smsopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide, and to G-Port User's Guide (chg-gsmsmsopts command) or A-Port User's Guide (chg-is41smsopts command) for assistance.
2.2.2183 E4721 Cmd Rej: VFLEX Subsystem is offline in database
The V-Flex subsystem must be online before the V-Flex subsystem number can be specified as a value for the ssn parameter.
Recovery
2.2.2184 E4722 Cmd Rej: PPC not supported for Private PC
For the chg/ent/rtrv-ls command, the PPC specified must not be a private point code.
For the ent-dstn command, if the value of the dpc parameter is a private point code, then the ppc parameter cannot be specified.
For the rtrv-dstn command, the proxy point code specified by the ppc parameter cannot be a private point code.
Recovery
Re-enter the command that generated this message, specifying a non-private point code for the proxy point code parameter. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2185 E4723 Cmd Rej: PRX=YES not supported for Private PC
If the specified destination point code is a private point code, then the prx=yes parameter cannot be specified
Recovery
2.2.2186 E4724 Cmd Rej: Proxy PC not defined in route (dstn) table
The specified PPC must exist in the DSTN table and the parameter prx=yes parameter must be specified.
Recovery
2.2.2187 E4725 Cmd Rej: LSN for proxy route cannot be changed
For the chg-dstn command, if the routeset specified in the command is associated with a proxy point code in the Destination table, then the linkset cannot be changed.
For the chg-rte command, if the value specified for the dpc parameter refers to a Proxy Point Code in the Destination table, then the nlsn parameter cannot be specified.
Recovery - chg-dstn
The linkset cannot be changed. Contact My Oracle Support if this error message appears. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - chg-rte
2.2.2188 E4726 Cmd Rej: Linkset Type for Network/Cluster Route can't be PRX
For the chg-dstn command, if the specified destination point code is a cluster or network destination point code, then the specified routeset cannot contain a route over proxy linksets.
For the ent/chg-rte commands, if a proxy linkset is used, then the value specified for the dpc parameter cannot be a network cluster address (ni-nc-*) or network address (ni-*-*).
Recovery - chg-dstn
- Determine whether the DPC is a cluster point code. Enter the rtrv-dstn command.
- Display the proxy linksets. Enter the
rtrv-ls:lst=prxcommand. - Revise the data as necessary. Refer to the Database Administration - SS7 User's Guide for assistance.
- 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 and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - ent/chg-rte
- Display the proxy linksets. Enter the
rtrv-ls:lst=prxcommand. - Revise the data as necessary. Refer to the Database Administration - SS7 User's Guide for assistance.
- Re-enter the command that generated this error message, specifing a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2189 E4727 Cmd Rej: SPC cannot be assigned to entry that uses PPC
If the prx=yes parameter is specified, then the spc/spca/spci/spcn/spcn24 parameter cannot be specified.
Recovery
2.2.2190 E4728 Cmd Rej: PPC destination in route(dstn) table is not proxy
The value specified for the ppc/ppca/ppci/ppcn/ppcn24 parameter must already exist in the DSTN table, and the prx=yes parameter must be assigned.
Recovery
2.2.2191 E4729 Cmd Rej: Linkset APC/PPC pair is already being used
The values of the apc and ppc parameters can be assigned to only one linkset.
Recovery
- Display the current values for the apc and ppc parameters. Enter the
rtrv-lscommand. - Re-enter the
ent-lscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.2192 E4730 Cmd Rej: Maximum Proxy PC capacity exceeded
A maximum of 100 Proxy destinations can be provisioned.
Recovery
2.2.2193 E4731 Cmd Rej: Cluster DPCs can't inherit PRX linkset type
Cluster destination point codes cannot inherit cluster members that have routes using proxy linksets.
Recovery
2.2.2194 E4732 Cmd Rej: Same option in ON & OFF params cannot be specified
The same option cannot be specified by both the on and off parameters within the same command.
Recovery
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.
2.2.2195 E4733 Cmd Rej: Exception route does not support proxy destinations
If a proxy destination is used, then the ent-rtx command cannot be entered.
Recovery
2.2.2196 E4734 Cmd Rej: IDP A-Party Routing feature must be enabled
The IDP A-Party Routing feature must be enabled before the Action Set specified by the asn parameter can contain the CGPNRTG Service Action.
Recovery
2.2.2197 E4735 Cmd Rej: Both IDP A-Party & SK Routing features must be enabled
The IDP A-Party Routing feature and the IDP SK Routing feature must be enabled before the Action Set specified by the asn parameter can contain the CGPNSKRTG Service Action.
Recovery
2.2.2198 E4736 Cmd Rej: ACCgPN(X) and CCCgPN CAs are mutually exclusive
If the srvn=idprcdpn(X) parameter is specified, then the Action Set specified by the asn parameter cannot contain both the ACCGPN* and CCCGPN Conditioning Actions.
Recovery
2.2.2199 E4737 Cmd Rej: IDP A-Party Blacklist feature must be enabled
The IDP A-Party Blacklist feature must be enabled before the Action Set specified by the asn parameter can contain the BLKLSTQRY or BLKLSTRLY Service Action.
Recovery
2.2.2200 E4738 Cmd Rej: BLKLSTQRY and BLKLSTRLY SAs are mutually exclusive
If the AS specified by the asn parameter contains the BLKLSTQRY Service Action, then the Action Set cannot contain any other Service Actions.
Recovery
2.2.2201 E4739 Cmd Rej: DRAFRMT contains CC so DRANAI must be 4 (INTL)
If the new or existing value specified for the drafrmt parameter contains a country code, then only a value of 4 can be specified for the dranai parameter. If the dranai parameter has a new or existing value that is not equal to 4, then the value that is specified for the drafrmt parameter cannot contain a country code.
2.2.2202 E4740 Cmd Rej: MT-Based GSM SMS NP must be ON
The MT-Based GSM SMS NP feature must be turned on before the MT-Based GSM MMS NP feature can be turned on.
Recovery
2.2.2203 E4741 Cmd Rej: UDP connection not supported on card
Recovery
2.2.2204 E4750 Cmd Rej: A cost must be specified with a linkset
If the lsn parameter is specified, then the rc parameter must be specified.
Recovery
Re-enter the ent-rte or ent-rtx command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.2205 E4753 Cmd Rej: DSTN table entry was not found
No destination entry found for DSTN table index.
Recovery
Re-enter the command that generated this message, specifying a valid link/linkset/route parameter. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2206 E4754 Cmd Rej: S-Port Subscriber Differentiation feature must be ON
The S-Port Subscriber Differentiation feature must be turned on before the subdfrn parameter can be specified.
Recovery
2.2.2207 E4756 Cmd Rej: GPORT/IGM/MO SMS feature must be enabled
The G-Port, IGM, MO SMS ASD, MO SMS B-Party Routing, MO SMS GRN, MO-based GSM SMS NP, or Prepaid SMS Intercept Ph1 feature must be enabled before the defmapvr parameter can be specified.
Recovery
2.2.2208 E4758 Cmd Rej: Linkset types must match for all linksets to the same APC
All linksets assigned to the same adjacent destination point code must be of the same type.
Recovery
2.2.2209 E4760 Cmd Rej: Linkset APC/SPC pair is already being used
The values specified for the apc and spc parameters cannot be assigned to another linkset.
Recovery
- Display the linkset information. Enter the
rtrv-lscommand. - Re-enter the
ent/chg-lscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - SS7 User's Guide for assistance.
2.2.2210 E4761 Cmd Rej: MOSMSGTA must be set
The mosmsgta parameter must be specified before the mosmsfwd=yes parameter can be specified.
Recovery
Re-enter the chg-gsmsmsopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the MO-SMS User's Guide for assistance.
2.2.2211 E4762 Cmd Rej: MTP routed SCCP or GWS Stop Action feature must be enabled
The MTP Routed SCCP or GWS Stop Action feature must be enabled before the mtprgtt or mtprgttfallbk parameter can be specified.
Recovery
2.2.2212 E4765 Cmd Rej: Obsolete MUX cards detected in the system
For the chg-ctrl-feat command, HIPR2 cards must be installed in all MUX locations before the HIPR2 High Rate Mode feature can be turned on.
The tst-imt command cannot be entered for an Extended Bit Rate Error Test (BERT) if the target bus contains obsolete MUX cards.
Recovery
2.2.2213 E4766 Cmd Rej: FCMODE must not be FCOPY
If the fcmode=fcopy parameter is specified (see the chg-eisopts command), then the fcna and fcnb parameters cannot be specified.
Recovery
- Display the value of the fcmode parameter. Enter the
rtrv-eisoptscommand. - Change the value of the fcmode parameter as desired. Refer to the Database Administration - Features User's Guide for assistance.
- Re-enter the
chg-netoptscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.2214 E4768 Cmd Rej: Invalid Link for hardware type E5ATM
If an E5-ATM or E5-ATM-B card is used, then a value of a, b, or a1 must be specified for the link parameter. A 3 Links per E5-ATM Card feature quantity must be enabled before the link=a1 parameter can be specified.
Recovery
2.2.2215 E4769 Cmd Rej: GPORT or IGM must be enabled
The G-Port or IGM feature must be enabled before the srfaddr, mrsndig, mrsnnai, sridn, msisdntrunc, migrpfx, gsm2is41, or serverpfx parameter can be specified and before a value of encodecug, encodenps, encdnpsptnone, encdnpsdnnotfound, or srismgttrtg can be specified for the on or off parameter.
Recovery
2.2.2216 E4771 Cmd Rej: GFLEX/GPORT must be ON or IGM/MT-Based GSM SMS NP enabled
The G-Flex or G-Port feature must be turned on or the MT-Based GSM SMS NP or IGM feature must be enabled before the defmcc parameter can be specified.
Recovery
2.2.2217 E4772 Cmd Rej: IPADDR and PORT combination cant be same for both the CCSMRs
The port and ipaddr parameters must have unique values for each CCS MR
Recovery
- Display the existing port and ipaddr parameter values. Enter the
rtrv-seas-configcommand. - Re-enter the
chg-seas-configcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.2218 E4774 Cmd Rej: No change in NCAI value requested
The value specified for the ncai parameter cannot be same as the NCAI provisioned for the destination point code.
Recovery
- Display the current values for the ncai parameter. Enter the
rtrv-dstncommand. - Change the ncai value if necessary. Refer to the Database Administration - SS7 User's Guide for assistance.
- Re-enter the
chg-dstncommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.2219 E4775 Cmd Rej: MNP CRP Feature must be ON
The MNP Circular Route Prevention (CRP) feature must be turned on before the crptt parameter can be specified.
Recovery
2.2.2220 E4776 Cmd Rej: CRP TT must be NONE
The crptt=none parameter must be specified (see the chg-gsmopts command) before the MNP Circular Route Prevention (MNP CRP) feature can be turned off.
Recovery
2.2.2221 E4777 Cmd Rej: Specified route does not exist in the RTX entry
The route associated with the linkset specified by the lsn parameter must already exist in the specified exception route.
Recovery
2.2.2222 E4779 Cmd Rej: MODE allowed only with DPC and RTX Class
The dpc parameter and the class criteria parameters must be specified before the mode parameter can be specified.
Recovery
Re-enter the rept-stat-rtx command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guideand to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2223 E4781 Cmd Rej: Cannot delete a route if an empty RTX results
For the dlt-rtx command, if the specified destination point code is assigned a proxy point code (PPC) in the Route table, then the specified routeset must contain a linkset for the destination point code, and the PPC of the linkset should be equal to the PPC assigned to the destination point code in the Route table.
Recovery
- Enter
rtrv-rtxto retrieve the exception route entries. Verify the route to be deleted is not the last route or RSET in the RTX table. Refer to the Database Administration - SS7 User's Guide for assistance. - Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2224 E4784 Cmd Rej: System wide SCTP checksum algorithm already configured
The chg-sg-opts:sctpsum=percard command must be entered before the chg-ip-card:sctpsum=command can be entered.
Recovery
2.2.2225 E4785 Cmd Rej: RLOC and LINK parameter combination must be specified
If the action=disp and tbl=lnk parameters are specified, then the rloc and link parameters must be specified.
Recovery
Re-enter the dbg-ddb command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.2226 E4786 Cmd Rej: Max 25 FPFX single digit wildcard chars '?' per NPP service
For the chg-ctrl-feat command, if a single digit wildcard (?) is specified as a value for the fpfx parameter more than 25 times across all of the rules for an NPP service, then the NPP Unlimited SDWC Characters feature cannot be turned off.
For the ent-npp-srs command, the NPP Unlimited SDWC Characters feature must be turned on before a single digit wildcard (?) can be specified as a value for the fpfx parameter more than 25 times across all of the rules for an NPP service.
Recovery
2.2.2227 E4787 Cmd Rej: SPARE ITU-INTL site id not defined
The spare ITU-I self-ID destination point code for the STP must be defined before spare ITU-I destinations can be entered.
Recovery
2.2.2228 E4788 Cmd Rej: SPARE ITU-NATL site id not defined
The spare ITU-N self-ID destination point code for the STP must be defined before spare ITU-N destinations can be entered.
Recovery
2.2.2229 E4789 Cmd Rej: Either AMGTT or AMGTT CgPA Upgrade feature must be ON
The AMGTT feature or the AMGTT CgPA Upgrade feature must be turned on before the cggtmod or cggtmodid parameter can be specified.
Recovery
2.2.2230 E4790 Cmd Rej: AMGTT CdPA Only feature cannot be enabled
The AMGTT CdPA Only feature cannot be enabled using the enable-ctrl-feat command. This feature is automatically enabled and turned on if the MGTT feature was on before upgrade to EAGLE Release 38.0 occurred.
Recovery
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2231 E4791 Cmd Rej: AMGTT CdPA Only must be ON
The AMGTT CdPA Only feature must be turned on before the AMGTT CgPA Upgrade feature can be enabled
Recovery
2.2.2232 E4792 Cmd Rej: AMGTT CdPA Only or AMGTT CgPA Upgrade must not be ON
If the AMGTT CdPA Only or AMGTT CgPA Upgrade feature is turned on, then the AMGTT feature cannot be enabled.
Recovery
2.2.2233 E4793 Cmd Rej: The parameter value can't be changed back to NONE
If a digit string value has already been specified for the mosmsgta or mtsmsdltrv parameter, then a value of none cannot be specified subsequently for that parameter.
Recovery
2.2.2234 E4799 Cmd Rej: DPC does not have any routes provisioned
Recovery
- Use the
ent-rtecommand to add routes to the system as needed. - Re-enter the
ent-rtxcommand that generated this error message, specifying a valid destination point code.
Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2235 E4800 Cmd Rej: EISCOPY must be ON
The eiscopy=on parameter must be specified before a value of stc or fcopy can be specified for the fcmode parameter.
Recovery
2.2.2236 E4801 Cmd Rej: Association is still assigned to a link
For the chg-assoc command, if the association on an IPSG card is referenced by a signaling link, then the values for the lhost and adapter parameters cannot be changed.
For the dlt-assoc command, if the association on an IPSG card is referenced by a signaling link, then the association cannot be deleted.
Recovery
2.2.2237 E4802 Cmd Rej: Association ADAPTER type doesn't match linkset ADAPTER type
The specified association (aname parameter) is configured in the database but has an adapter that differs from that of the specified linkset (lsn parameter).
Recovery
2.2.2238 E4803 Cmd Rej: Association and LOC must reference same card
The association specified by the aname parameter must be configured for the card that is specified by the loc parameter.
Recovery
2.2.2239 E4804 Cmd Rej: ANAME is prohibited for a non-IPSG link
The aname parameter can be specified only for IPSG links.
Recovery
- Display the linkset. Enter the
rtrv-ls:lsn=command. - Re-enter the
ent-slkcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide, to the Database Administration - SS7 User's Guide (SS7 links) and to the Database Administration - IP7 User's Guide (IP links) for assistance.
2.2.2240 E4805 Cmd Rej: ANAME is required for an IPSG link
If an IPSG linkset and card are used, then the aname parameter must be specified.
Recovery
- Display the signaling link information for the card. Enter the
rtrv-slk:loc=command. - Provision the aname parameter for the links as necessary.
- Re-enter the command that generated this error message.
Refer to the command description in Commands User's Guide and to Database Administration - IP7 User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2241 E4806 Cmd Rej: TPS exceeded allowed range
- E5-ENET - 5000 TPS
- E5-ENET-B or SLIC when the E5-ENET-B IPSG High Throughput Capacity feature is turned off - 6500 TPS
- E5-ENET-B or SLIC when the E5-ENET-B IPSG High Throughput Capacity feature is turned on - 9500 TPS
Recovery
2.2.2242 E4807 Cmd Rej: TPS exceeded for card
- E5-ENET - 5000 TPS
- E5-ENET-B when the E5-ENET-B IPSG High Throughput feature is turned off - 6500 TPS
- E5-ENET-B when the E5-ENET-B IPSG High Throughput feature is turned on - 9500 TPS
- SLIC - 12000 TPS
For the
chg-card and
ent-slk commands, the resulting total
TPS of all signaling links configured for the card cannot exceed the maximum
capacity for the card.
For the
chg-ctrl-feat command, if any
IPSG card in the system has a configured card
capacity above 6500 TPS, then the E5-ENET-B IPSG High Throughput feature cannot
be turned off.
For the
chg-ls command, the value specified
for the
slktps/rsvdslktps
parameter cannot cause the card to exceed the total maximum
capacity of the card.
Recovery
2.2.2243 E4808 Cmd Rej: Service Action(s) require an MPS dependent feature to be ON
All of the features that are associated with the Service Actions in the Action Set that is specified by the asn parameter must be turned on before the Action Set can be used. Refer to the Numbering Plan Processor (NPP) User's Guide for the features associated with each Service Action.
Recovery
2.2.2244 E4809 Cmd Rej: GPL type IPSG requires linkset with IPSG=YES
For an IPSG card, the ipsg=yes parameter must be specified (see the ent-ls command).
Recovery
2.2.2245 E4810 Cmd Rej: All links must be OOS-MT-DISABLED to modify RCONTEXT
All links must be in the OOS state before the rcontext parameter can be specified.
Recovery
2.2.2246 E4811 Cmd Rej: SLKTPS is prohibited for non-IPSG linksets
The slktps/rsvdslktps and maxslktps parameters can be specified only for IPSG linksets.
Recovery
2.2.2247 E4812 Cmd Rej: SLKTPS is required for IPSG linksets
If the ipsg=yes parameter is specified, then the slktps/rsvdslktps or maxslktps parameter must be specified.
The ipsg=yes and adapter=m3ua parameters must be specified before the slktps/rsvdslktps or maxslktps parameter can be specified.
Recovery
2.2.2248 E4813 Cmd Rej: Command not valid for IPSG-M3UA
Linkset adaptor IPSG-M3UA cannot be specified for an IPSG card.
Recovery
Re-enter the command that generated this message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2249 E4814 Cmd Rej: Linkset referenced by exception route ILSN
If the linkset that is specified by the lsn parameter is used as an incoming linkset for an exception route entry (see the rtrv-rtx command), then this command cannot be entered.
Recovery
Re-enter the command that generated this message, specifying a valid linkset. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2250 E4815 Cmd Rej: At least one EPAP related feature must be ON
For the chg-stpopts command, at least one EPAP-related feature must be turned on before the EPAP240M feature can be turned on.
For the enable-ctrl-feat command, at least one EPAP related feature must be turned on before the EPAP Data Split feature can be enabled.
For the rtrv-data-rtdb command, at least one EPAP related feature must be turned on before the entity, entitytype, or dn parameter can be specified.
Recovery
2.2.2251 E4816 Cmd Rej: ATINP feature must be enabled
The ATINP feature must be enabled before the chg/rtrv-atinpopts commands can be entered.
For the chg-mtc-measopts command, the ATINP feature must be enabled before the mtchatinpq=on or mtcdatinpq=on parameter can be specified.
For the chg/rtrv-sid command, the ATINP feature must be enabled before the mtchatinpq=on or cpctype=atinpq parameter can be specified.
For the ent/chg/rtrv-srvsel command, the ATINP feature must be enabled before the (n)serv=atinp parameter can be specified.
For the ent/chg/dlt-ss-appl command, the ATINP feature must be enabled before the appl=atinpq parameter can be specified.
Recovery
2.2.2252 E4817 Cmd Rej: ITU TCAP LRN Query (LRNQT) feature must be ON
The LRNQT feature must be turned on before the (n)serv=lrnqt parameter can be specified.
2.2.2253 E4819 Cmd Rej: Failure reading TSTMSG Table
The TSTMSG table is corrupt or cannot be found.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this mes
2.2.2254 E4820 Cmd Rej: Failure accessing EGLEOPTS table
The EGLEOPTS table is corrupt or cannot be found by the system.
For the
chg/rtrv-deiropts command, the
DEIROPTS table should be accessible.
For the
chg/rtrv-enumopts command, the
ENUMOPTS table should be accessible.
For the
chg/rtrv-sipopts command, the SIPOPTS
table should be accessible.
For the
chg-rtrv-sfappopts command, the SFAPPOPTS table
should be accessible.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2255 E4821 Cmd Rej: CDPNNAI and CGPNNAI must be specified with TCAPTYPE
If the tcaptype parameter is specified, then the cdpnnai and cgpnnai parameters must be specified.
Recovery
Re-enter the chg-ttr-msg 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4
2.2.2256 E4823 Cmd Rej: SAs specified are mutually exclusive
The Service Actions in the Action Set specified by the asn parameter cannot violate mutual exclusivity rules defined by the service specified by the srvn parameter.
Recovery
Re-enter the ent/chg-npp-srs command that generated this error message, specifying a valid combination of parameters. Refer to the Numbering Plan Processor (NPP) User's Guide to determine which Service Actions are mutually exclusive. Refer to the feature manual for the feature of interest for additional information.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2257 E4824 Cmd Rej: No BPIPADDR is provisioned for this card
The bpipaddr parameter must be specified before the bpsubmask parameter can be specified.
Recovery
Re-enter the chg-ip-card command that generated this error message, specifying a valid combination of values. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.2258 E4825 Cmd Rej: If BPIPADDR is specified BPSUBMASK is required
If the bpipaddr parameter is specified, then the bpsubmask parameter must be specified.
Recovery
Re-enter the chg-ip-card command that generated this error message, specifying a valid combination of values. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.2259 E4826 Cmd Rej: MULTGC is prohibited on IPSG-M3UA linksets
If the ipsg=yes and adapter=m3ua parameters are specified, then the multgc=yes parameter cannot be specified.
Recovery
2.2.2260 E4827 Cmd Rej: Correct RCONTEXT value is required to delete
If the action=delete parameter is specified to delete the routing context, then the value specified for the rcontext parameter must be the value used by the specified linkset in the database.
Recovery
- Display the values for the linkset. Enter the
rtrv-ls:lsn=command. - Re-enter the
chg-lscommand that generated this error message, specifying a valid combination of values. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.2261 E4828 Cmd Rej: Unique RCONTEXT required if associations in multiple lsets
All linksets that share an association must have the same routing context.
Recovery
2.2.2262 E4829 Cmd Rej: Multiple links w/in same linkset cannot share an association
For the chg-ls command, multiple signaling links in a single linkset cannot share the same association.
For the ent-slk command, the same value cannot be specified for the aname parameter for mulitple links in the same linkset.
Recovery
2.2.2263 E4830 Cmd Rej: LNP ported TNs (24Million or more) Qty Feature must be ON
The LNP ported TNs 24 Million Quantity feature or greater must be turned on before the LRNQT feature can be enabled.
Recovery
2.2.2264 E4831 Cmd Rej: Cannot set DefCC to NONE if MT-Based IS41 SMS NP is ON
If the MT-based IS41 SMS NP feature is turned on, then the defcc=none parameter cannot be specified.
Recovery
2.2.2265 E4832 Cmd Rej: CLRWRNTX=YES only valid with WRNLN parameter
If the clrwrntx=yes parameter is specified, then the wrnln parameter must be specified.
Recovery
2.2.2266 E4835 Cmd Rej: Limit 1 SLK per IPSG-M2PA association
If the value specified for the aname parameter indicates an IPSG-M2PA association, then only one signaling link can be assigned.
Recovery
2.2.2267 E4836 Cmd Rej: Limit 16 SLKs per IPSG-M3UA association
If the value specified for the aname parameter indicates an IPSG-M3uA association, then only 16 signaling links can be assigned.
Recovery
2.2.2268 E4837 Cmd Rej: MAPSET and MRNSET cannot be specified together
The xlat=none parameter must be specified before the mapset and mrnset parameters can be specified together in the command.
Recovery
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 and to the Database Administration - GTT User's Guide for assistance.
2.2.2269 E4838 Cmd Rej: GTIN24 must not be specified when (N)SERV = ATINP/AIQ/EIR
If a value of aiq, atinp, or eir is specified for the (n)serv parameter, then the gtin24 parameter cannot be specified.
Recovery
- Display the existing values for the (n)serv parameter. Enter the
rtrv-srvselcommand. - Re-enter the
ent/chg/rtrv-srvselcommand that generated this error message, specifying a valid combination of values. Refer to the command description in Commands User's Guide for assistance.
2.2.2270 E4840 Cmd Rej: Fast Copy capable card is required
At least one FC-capable card must be provisioned in the system before the type=fcs parameter can be specified.
Note:
Refer to the Database Administration - Features User's Guide for a description of an FC-capable card.Recovery
2.2.2271 E4842 Cmd Rej: Cannot set DefCC to NONE, if IDPR ON or IAR Base ENABLED
If the IDPR feature is turned on or the IAR Base feature is enabled, then the defcc=none parameter cannot be specified.
Recovery
2.2.2272 E4845 Cmd Rej: IGM or MO SMS IS41-to-GSM Migr must be enabled
The IGM or MO SMS IS41-to-GSM Migration feature must be enabled before the is412gsm parameter can be specified.
2.2.2273 E4846 Cmd Rej: MOSMSTCAPSEG and/or MOSMSDIGMAT not set to default value
If the mosmstcapseg=on parameter is specified, and the MO-based GSM SMS NP feature is not turned on, or if the mosmsdigmat=bestfit parameter is specified, then the Portability Check for MO SMS feature cannot be turned off.
Recovery
2.2.2274 E4847 Cmd Rej: SAPC is prohibited on IPSG-M3UA linksets
If the ipsg=yes and adapter=m3ua parameters are specified, a linkset cannot have an SAPC.
Recovery
2.2.2275 E4849 Cmd Rej: Linkset must not contain any IPSG type links
If the linkset contains any IPSG links, then the ipsg=no parameter cannot be specified.
Recovery
2.2.2276 E4851 Cmd Rej: Removable media can not be inserted
act-upgrade command, when the action=convertstp parameter is specified, no removable media can be inserted in any of the USB ports.
Caution:
It is strongly recommended that this command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.For the init-card command, if a removable drive is inserted in the system, then the prtngrp=inactive parameter cannot be specified.
Note:
When theinit-card command is issued to the OAM software, there is a 10-second wait before the card is reset. This wait period is intended to ensure that all database updates are complete before the card is reset.
Recovery - act-upgrade
Remove the removable media and re-enter the command, specifying a valid combination of parameters.
Contact My Oracle Support for additional assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - init-card
Remove the MO from the card, re-enter the command that generated this error message, and load the drive. Refer to the command description in Commands User's Guide and to Database Administration - System Management User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2277 E4855 Cmd Rej: MO SMS IS41 NP or MO SMS IS41-to-GSM Migr must be enabled
The MO-based IS41 SMS NP or MO SMS IS41-to-GSM Migration feature must be enabled before the mosmsdigmat parameter can be specified.
Recovery
2.2.2278 E4856 Cmd Rej: FPFX contains more than three ?
For the chg-ctrl-feat command, if any NPP service rules have more than three single digit wildcard characters (?) specified for the fpfx parameter, then the NPP Unlimited SDWC Characters feature cannot be turned on.
For the ent-npp-srs command, if the NPP Unlimited SDWC Characters feature is turned on, then the value specified for the fpfx parameter cannot contain more than three single digit wildcard characters (?).
Recovery
2.2.2279 E4857 Cmd Rej: WRNLN must be specified with WRNTX or CLRWRNTX=yes
If the wrnln parameter is specified, then the wrntx or clrwrntx=yes parameter must be specified.
Recovery
Re-enter the chg-secu-dflt command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - System Management User's Guide for assistance.
2.2.2280 E4861 Cmd Rej: At least 1 IDPRCDPN(X) srvc must be ON to turn ON IDPR FEAT
An IDPRCDPN(X) NPP service must be turned on before the Prepaid IDP Query Relay feature can be turned on.
Recovery
2.2.2281 E4867 Cmd Rej: IP address has been assigned to BPIPADDR
Each IP address in the IP link table must be unique.
Recovery
- Display the existing Bonded port IP addresses in the database. Enter the
rtrv-ip-cardcommand. - Re-enter the
chg-ip-lnkcommand that generated this error message, specifying a valid IP address.
Refer to the command description in Commands User's Guide and to Database Administration - Features User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2282 E4868 Cmd Rej: action set contains OFNAI value not defined by service
The Action Set specified by the asn parameter cannot contain an OFNAI class that has a value of none.
Recovery
2.2.2283 E4870 Cmd Rej: NUMSLKPROH must be less than or equal to NUMSLKRSTR
The value specified for the numslkproh parameter must be less than the value specified for the numslkrstr parameter.
Recovery
- Display the value of the numslkproh parameter. Enter the
rtrv-ls:lsn=command. - Re-enter the
chg-lsoptscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.2284 E4871 Cmd Rej: NUMSLKRSTR must be less than or equal to NUMSLKALW
The value specified for the numslkrstr parameter must be less than or equal to the value specified for the numslkalw parameter.
Recovery
- Display the value of the numslkalw parameter. Enter the
rtrv-ls:lsn=<xxxx>command. - Re-enter the
chg-lsoptscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.2285 E4873 Cmd Rej: NUMSLK thresholds allowed only for IPSG M3UA linksets
The value specified for the lsn parameter must indicate an IPSG-M3UA linkset before the numslkalw, numslkproh, and numslkrstr parameters can be specified.
Recovery
2.2.2286 E4874 Cmd Rej: NUMSLK value exceeds number of links in the linkset
The value of the numslkalw, numslkproh, and numslkrstr cannot be greater than the number of links configured in the IPSG-M3UA linkset.
Recovery
2.2.2287 E4875 Cmd Rej: TFATCABMLQ not allowed for IPSG M3UA linksets
The tfatcabmlq parameter cannot be specified for IPSG-M3UA linksets.
Recovery
2.2.2288 E4876 Cmd Rej: STP True PC and ATINPQ Subsystem does not exist in MAP Table
The STP true point code and an ATINPQ subsystem number must already be defined in the MAP table before the appl=atinpq parameter can be specified.
Recovery
2.2.2289 E4877 Cmd Rej: ATINPQ Subsystem is offline in database
The ATINPQ subsystem must be online before the ATINPQ subsystem number can be specified as a value for the ssn parameter
Recovery
2.2.2290 E4878 Cmd Rej: Invalid FCNA
The value specified for the fcna parameter must be a classless Inter Domain Routing (Supernet) address with a 23-bit network prefix.
Recovery
Re-enter the chg-netopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.2291 E4880 Cmd Rej: SSN must not be NONE if RI is SSN
If the (n)ri=ssn parameter is specified, then the (n)ssn=none parameter cannot be specified.
Recovery
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 and to the Database Administration - Features User's Guide for assistance.
2.2.2292 E4881 Cmd Rej: Action Set does not exist
The Action Set specified by the asn parameter must already exist in the NPP AS table.
Recovery
2.2.2293 E4882 Cmd Rej: Rule contains unsupported Conditioning Actions
The Action Set specified by the asn parameter cannot contain Conditioning Actions that are not supported by the service specified by the srvn parameter.
Recovery
- Display the Conditioning Actions in the Action Set. Enter the
rtrv-npp-ascommand. - Determine the Conditioning Actions supported by the NPP Service. Refer to the Numbering Plan Processor (NPP) User's Guide and to the appropriate feature manual for assistance.
- Re-enter the command that generated this error message.
2.2.2294 E4883 Cmd Rej: Rule contains unsupported Service Actions
The NPP Rule contains a Service Action that is not supported by the NPP Service.
Recovery
Determine the Service Actions supported by the NPP Service. Refer to Numbering Plan Processor (NPP) User's Guide and to the appropriate feature manual for assistance.
Re-enter the ent/chg-npp-srs 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2295 E4884 Cmd Rej: Rule contains unsupported Formatting Actions
The Action Set specified by the asn parameter cannot contain Formatting Actions that are not supported by the service specified by the srvn parameter.
Recovery
2.2.2296 E4885 Cmd Rej: Rule violates Service Action precedence
The Service Actions specified by the Action Set do not conform to the NPP Service's Service Action precedence order.
Recovery
Re-enter the ent/chg-npp-srs command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Numbering Plan Processor (NPP) User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2297 E4886 Cmd Rej: Rule conditions too many digits
The Conditioning Actions in the Action Set specified by the asn parameter cannot condition more digits than allowed by the value specified for the fdl parameter.
Recovery
Re-enter the ent/chg-npp-srs command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Numbering Plan Processor (NPP) User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2298 E4887 Cmd Rej: Rule does not condition a variable length digit string
If the fdl=* parameter is specified, then the Action Set specified by the asn parameter must contain Conditioning Actions that support variable digit string conditioning.
Recovery
Re-enter the ent/chg-npp-srs command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Numbering Plan Processor (NPP) User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2299 E4888 Cmd Rej: System Rule maximum (8192) reached
A maximum of 8192 NPP system-wide rules can be entered.
Recovery
2.2.2300 E4889 Cmd Rej: Service Rule maximum (4096) reached
A maximum of 4096 (4K) NPP service rules can be provisioned.
Recovery
2.2.2301 E4890 Cmd Rej: Rule already exists
The NPP rule already exists within the NPP Rule table.
Recovery
There is no need to enter a rule that already exists in the table. No further action needed for the ent-npp-srs command.
2.2.2302 E4891 Cmd Rej: Rule does not exist
The NPP Rule that is specified by the fdl, fnai, fpfx, and srvn parameters must already exist in the NPP Rule table.
Recovery
- Display the existing rules in the NPP Rule table. Enter the
rtrv-npp-srscommand. - Re-enter the
chg/dlt-npp-srscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Numbering Plan Processor (NPP) User's Guide for assistance.
2.2.2303 E4892 Cmd Rej: Action Set already exists
The Action Set cannot already exist in the NPP AS table.
Recovery
2.2.2304 E4893 Cmd Rej: Action Set referenced
An Action Set that is referenced by a rule cannot be changed or deleted.
Recovery
2.2.2305 E4895 Cmd Rej: CPCx must not be ITUN24 if CPCTYPE is ATINPQ/AIQ/EIR
If a value of atinpq, aiq, or eir is specified for the cpctype parameter, then the cpcn24 parameter cannot be specified.
Recovery
Re-enter the chg-sid command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if the error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2306 E4898 Cmd Rej: Minimum Number Conditioning Not Met
A set of numbering conditions must be met by the specified Conditioning Action, and the new or existing Formatting Actions within the Action Set must be able to be loaded by the corresponding Conditioning Actions.
Recovery
Re-enter the ent/chg-npp-as command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Numbering Plan Processor (NPP) User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2307 E4900 Cmd Rej: Entry does not exist with specified GTIN24-TT-NP(V)-NAI(V)
An entry must already exist that matches the gti/gtia/gtii/gtin/gtin24, tt, ssn, and np(v) and nai(v) combination of parameters.
Recovery
2.2.2308 E4901 Cmd Rej: TTI, NP, NAI cannot be specified for a direction of ATOI
If the dir=atoi parameter is specified, then the tti, np, and nai parameters cannot be specified.
Recovery
Re-enter the dlt-gtcnv command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2309 E4902 Cmd Rej: CSPC group cannot contain both PCN and PCN24 point codes
A concerned signaling point code group cannot include both PCN and PCN24 point codes (ITUN and ITUN24).
Recovery
2.2.2310 E4903 Cmd Rej: If NGTI of referred GTMOD is 4, PC cannot be ANSI
If the specified or previously provisioned translated point code is of type ANSI, then the ngti value of the referred GT Modification Identifier (see the ent-gtmod command) must be 2.
Recovery
- Display the point code types. Enter the
rtrv-sidcommand. - Display the ngti values of the GT Modification Identifiers. Enter the
rtrv-gtmodcommand. - 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 and to the Database Administration - GTT User's Guide for assistance.
2.2.2311 E4904 Cmd Rej: ADDTBLCNV and DELTBLCNV cannot be specified together
The addtblcnv and deltblcnv parameters cannot be specified together in the command.
Recovery
Re-enter the chg-upgrade-config 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2312 E4905 Cmd Rej: Group Code of APCN of ILSN must be equal to that of DPCN
Recovery
Re-enter the
ent-rtx command that generated this
error message, specifying a valid group code.
Refer to the command description in Commands User's Guide for assistance. If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2313 E4911 Cmd Rej: Disk invalid for hardware configuration
For the disp-disk-dir command, an E5-MCAP card must be provisioned in the system before the src=usb parameter can be specified.
For the chg-tbl and tst-disk commands, an E5-MCAP card must be installed before the disk=usb parameter can be specified.
For the copy-gpl and copy-tbl commands, an E5-MCAP card must be installed before a value of usb can be specified for the ddriv or sdrv parameter.
Recovery
Contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2314 E4912 Cmd Rej: Disk invalid for specified Location
For the copy-gpl command, the specified disk type must match the specified location.
For the copy-tbl command, if a value of fixed is specified for the sdrv or ddrv parameter, then a value of 1114 or 1116 must be specified for the sloc or dloc parameter.
format-disk command, a value of of 1114 or 1116 must be specified for the loc parameter before the type=fixed parameter can be specified.
Caution:
Contact My Oracle Support before entering theformat-disk command.
Recovery
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 occurs again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2315 E4913 Cmd Rej: Disk parameter required for specified location
The src parameter must be specified in the command.
Recovery
Re-enter the
disp-disk-dir 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 occurs again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2316 E4914 Cmd Rej: Src invalid for hardware configuration
An E5-MCAP card must be provisioned in the system before the src=usb parameter can be specified.
Recovery
For the act-upgrade command, use the rtrv-card command to display the cards in the system. Provision an E5-MCAP card, if necessary, and re-enter the command. Refer to Maintenance Guide and to Database Administration - Systems Management User's Guide for assistance.
Caution:
It is strongly recommended that theact-upgrade command be used only in conjunction with the system Upgrade Procedusre for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2317 E4915 Cmd Rej: Dest invalid for hardware configuration
An E5-MCAP card must be installed before the dest=usb parameter can be specified.
Recovery
Contact My Oracle Support if this error message appears. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2318 E4916 Cmd Rej: Command invalid for hardware configuration
act/dact-ip-lnk commands, the referenced card must be equipped and the value specified for the loc parameter must refer to one of the following cards:
- E5-ENET or E5-ENET-B card running the EROUTE, IPGWx, IPLIMx, or IPSG application
- IPSM card running the IPS application
- E5-SM4G or E5-SM8G-B card running the VSCCP application
- E5-OAM card running the OAMHC application
- E5-MCPM-B card
- SLIC card
For the chg-ee-card command, the card loc specified to detach a filter must have EE configured.
For the enable-ctrl-feat command, the EPAP Data Split or Dual ExAP Config feature can not be enabled if DSM, MPL, E1T1MIM, LIMATM, LIME1ATM cards are running in the system.
For the enable-ctrl-feat command, if the system is NOT in mixed mode (does not contain both OAM and E5-OAM cards) and is equipped with GPSM-II / TDM card(s), then the Integrated GLS and Integrated Measurements features cannot be enabled.
Recovery
2.2.2319 E4917 Cmd Rej: OAM card has Thermal Alarm
Recovery
- Verify that the fan assembly located in the shelf is working properly and that the fan filters are clean.
- If the fan unit is working properly, employ additional cooling methods to the card as needed. Use the
rtrv-th-almcommand to display the current temperature alarm thresholds, and if appropriate, thechg-th-almcommand to change the thresholds. - Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2320 E4918 Cmd Rej: Could not access USB disk
For the act-upgrade command, if the src=usb parameter is selected, then the plug-in flash drive upgrade media must be inserted in the Active OAM's flush-mounted USB port.
For the chg-db command, if the src=usb or dest=usb parameter is specified, then a plug-in flash drive must be inserted into the Active OAM's flush-mounted USB port.
For the chg-gpl command, a plug-in flash drive must be inserted in the Active OAM.
For the copy-gpl command, the plug-in flash drive must be accessible in the Active OAM's flush-mounted USB port.
Recovery
act-upgrade command, enter the rept-stat-db command to verify that a plug-in flash drive is installed. Install the drive if necessary. Refer to the Upgrade Procedures for the target release or Database Administration - System Management User's Guide for instructions.
Caution:
It is strongly recommended that theact-upgrade command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.
Contact My Oracle Support if this error message appears. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2321 E4919 Cmd Rej: Could not access RAM disk
The internal RAM disk must be available for the plug-in flash drive's upgrade image to be unpackaged.
Recovery
Re-enter the act-upgrade command, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
Caution:
It is strongly recommended that theact-upgrade command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.
Contact My Oracle Support if this error message occurs again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2322 E4920 Cmd Rej: Cannot copy table onto itself
The same value cannot be specified for the sloc and dloc or the stbl and dtbl parameters.
Recovery
Re-enter the copy-tbl 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 occurs again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2323 E4921 Cmd Rej: Type invalid for hardware configuration
An E5-MCAP card must be installed before the type=usb parameter can be specified.
Recovery
The format-disk:type=usb command must be specified by Oracle personnel only.
Contact My Oracle Support if this error message appears. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2324 E4922 Cmd Rej: PCR N1/N2 threshold is out of range for the link type
The values specified for the pcrn1 and pcrn2 parameters must be within the range specified for the link type.
Recovery
Re-enter the ent-slk command that gneerated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.2325 E4925 Cmd Rej: OPC must not be identical to APC of linkset
The value specified for the opc/opca/opci/opcn/opcn24 parameter cannot be the same as the adjacent point code of the linkset specified by the (n)lsn parameter.
Recovery
- Display the adjacent point codes for linksets in the database. Enter the
rtrv-lscommand. - 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.
2.2.2326 E4926 Cmd Rej: Service Portability feature must be enabled
The S-Port feature must be enabled before the sporttype parameter can be specified.
For the chg-tifopts command, the S-Port feature must be enabled before the sportrelay or sportrls parameter can be specified.
For the enable-ctrl-feat command, the S-Port feature must be enabled before the S-Port Subscriber Differentiation feature can be enabled.
Recovery
2.2.2327 E4927 Cmd Rej: S-Port feature exclusive of A-Party Blacklist feature
The S-Port feature and the IDP A-Party Blacklist feature cannot both be enabled in the system.
Recovery
2.2.2328 E4928 Cmd Rej: S-Port and SRI Query for Prepaid features must be enabled
The Service Portability and G-Port SRI Query for Prepaid features must be enabled before the sporttype parameter can be specified.
Recovery
2.2.2329 E4929 Cmd Rej: IS41 GSM Migration feature must be turned ON
The IS41 GSM Migration feature must be turned on before the igmsmsrelay, is41smscgttsn, or defis41smsc parameter can be specified.
Recovery
2.2.2330 E4930 Cmd Rej: IGMSMSRELAY cannot be yes, if DEFIS41SMSC is none
If the defis41smsc=none parameter is specified, then the igmsmsrelay=yes parameter cannot be specified.
Recovery
Re-enter the chg-gsmsmsopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the G-Port User's Guide for assistance.
2.2.2331 E4934 Cmd Rej: Formatting Action Not Loaded
The Action Set must contain a Conditioning Action that can load or populate all of the Formatting Action lists configured in the Action Set.
Recovery
2.2.2332 E4935 Cmd Rej: Service Must Have Rules to Turn On
The NPP Service must have associated rules associated before the status of the service can be set to ON.
Recovery
2.2.2333 E4936 Cmd Rej: Cannot Modify Service with Rules Provisioned
If the service specified by the srvn parameter references any NPP rules, then the intl, natl, nai1, nai2, and nai3 parameters cannot have a value of none.
Recovery
2.2.2334 E4940 Cmd Rej: Rule with Longer FPFX than FDL Invalid
If the NPP Rule's Filter Prefix (FPFX) and the Filter Digit Length (FDL) values are not set as variables (wildcard *), then the FPFX must not have digits greater than the FDL value.
Recovery
Re-enter the ent-npp-srs command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Numbering Plan Processor (NPP) User's Guide for assistance.
2.2.2335 E4941 Cmd Rej: Rule with FPFX=* value cannot have AS with CA(x)=FPFX
If a rule contains a filter prefix with a wildcard value, then the rule cannot contain an Action Set where the FPFX Conditioning Action is specified.
Recovery
2.2.2336 E4943 Cmd Rej: Number of links in the linkset falls below NUMSLK value
If deleting the link causes the provisioned link count to fall below the NUMSLK thresholds configured for the corresponding IPSG-M3UA linkset (see the chg-lsopts command), then the link cannot be deleted. If values of 0 or 1 are specified for all of the NUMSLK threshold parameters, then the last link can be deleted.
Recovery
2.2.2337 E4945 Cmd Rej: FPFX value cannot end with a '?'
The value specified for the fpfx parameter cannot contain a ? as the final character.
Recovery
Re-enter the ent-npp-srs command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Numbering Plan Processor (NPP) User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2338 E4946 Cmd Rej: Invalid FCNB
The value specified for the fcnb parameter must be a classless Inter Domain Routing (Supernet) address with a 23-bit network prefix.
Recovery
Re-enter the chg-netopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - Features User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2339 E4948 Cmd Rej: Adjacent PC of the Linkset must be ITUN or ITUI
Values for the icnimap and ognimap parameters other than none can be specified only for ITU-I and ITU-N adjacent point codes (APCs) of the linkset.
Recovery
2.2.2340 E4949 Cmd Rej: TESTMSG protocol does not match with the FEAT specified
The values specified for the prot and feat parameters must be compatible. Refer to the command description in Commands User's Guide for valid combinations.
Recovery
Re-enter the tst-msg command that generated this error message, specifying a valid combination of parameters.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2341 E4950 Cmd Rej: At least one ITU NP feature must be ON
At least one of the EPAP-based features must be enabled before the 1100 TPS/DSM for ITU NP feature can be enabled.
Recovery
2.2.2342 E4952 Cmd Rej: Only msg with ACTIVE=YES shall be sent to the Feature
The test message must be defined with active=yes (see the chg-isup-msg command), before the message is sent to the specified network card for test processing. Test messages are never sent out to the live network.
Recovery
2.2.2343 E4953 Cmd Rej: RESET is mutually exclusive with any other parameter
If the reset parameter is specified, then no other parameters can be specified in the command.
Recovery
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.
2.2.2344 E4956 Cmd Rej: System Action Set maximum (1024) reached
A maximum of 1024 (1k) Action Set entries can be specified in the NPP system.
Recovery
2.2.2345 E4957 Cmd Rej: MO SMS IS41-to-GSM Migration feature must be enabled
For the chg-is41smsopts command, the MO SMS IS41-to-GSM Migration feature must be enabled before the moigmpfx parameter can be specified.
For the ent/chg-npp-srs commands, the MO SMS IS41-to-GSM Migration feature must be enabled before an Action Set containing the MIGRATE Service Action can be specified as a value for the asn parameter with the MOSMSICDPN service.
Recovery
2.2.2346 E4958 Cmd Rej: ? must be in the first six FPFX digits
For the chg-ctrl-feat command, if any NPP service rules have a single digit wildcard character (?) specified after the sixth digit in the fpfx parameter, then the NPP Unlimited SDWC Characters feature cannot be turned on.
For the ent-npp-srs command, if the NPP Unlimited SDWC Characters feature is turned on, then the value specified for the fpfx parameter can contain single digit wildcard characters (?) within only the first six digits.
Recovery
2.2.2347 E4960 Cmd Rej: Conditioning Actions condition too many digits
The total number of digits to condition in the Conditioning Actiion list (ca=<list>) or the ca1...ca12 parameters cannot be larger than 32.
The total number of digits conditioned is calculated by adding the number of digits conditioned for each Conditioning Action value.
Recovery
Re-enter the ent/chg-npp-as command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide, the Numbering Plan Processor (NPP) User's Guide, the TIF User's Guide, and the feature manual for the feature of interest for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2348 E4961 Cmd Rej: ICNIMAP and OGNIMAP parameters must be specified together
The icnimap and ognimap parameters must be specified together in the command.
Recovery
Re-enter the chg-lsopts command, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.2349 E4962 Cmd Rej: ICNIMAP and OGNIMAP values are not compatible
The NI mapping for incoming messages in a linkset must be compatible with the NI mapping for the outgoing messages.
Recovery
Re-enter the chg-lsopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.2350 E4964 Cmd Rej: Duplicate CAs loading same FA invalid
An Action Set cannot have contain Conditioning Actions that load or populate the same Formatting Action.
Recovery
2.2.2351 E4965 Cmd Rej: CAs violate number conditioning
Conditioning Actions must be specified for inclusion in an individual Action Set using valid number conditioning rules:
- If the ZNX Conditioning Action is specified, then the CC*, AC*, SN*, DN*, and DNX Conditioning Actions cannot be specified.
- If the CC* AND DN* or DNX Conditioning Actions are specified, then the AC*, SN*, SNX, and ZNX Conditioning Actions cannot be specified.
- If the CC*, AC*, AND SN* or SNX Conditioning Actions are specified, then the DN*, DNX, and ZNX Conditioning Actions cannot be specified.
Recovery
2.2.2352 E4966 Cmd Rej: Parameter only valid for TELNET terminals
The type=telnet parameter must be specified before the logintmr and logouttmr parameters can be specified.
Recovery
- If changing a terminal that has already been configured, determine the current terminal type. Enter the
rtrv-trmcommand. - Re-enter the
chg-trmcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.2353 E4968 Cmd Rej: FAs violate number formatting
The Action Set cannot contain the following combinations of Formatting Actions:
- If the DN Formatting Action is specified, then the AC, SN, and ZN Formatting Actions cannot be specified.
- If the ZN Formatting Action is specified, then the AC, CC, SN, and DN Formatting Actions cannot be specified.
- If the SN Formatting Action is specified, then the ZN and DN Formatting Actions cannot be specified.
- If the RNOSPODN, RNOSPOSN, or RNOSPOZN Formatting Action is specified, then the RN, SP, SN, DN or ZN Formatting Actions cannot be specified.
- The RNOSPODN, RNOSPOSN, and RNOSPOZN Formatting Actions cannot be specified together.
Recovery
Re-enter the ent/chg-npp-as command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide, the Numbering Plan Processor (NPP) User's Guide, and the feature manual for the feature of interest for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2354 E4969 Cmd Rej: At least one SMS related feature must be Enabled
At least one of the MO-based or MT-based SMS features must be enabled before the command can be entered.
Recovery
2.2.2355 E4970 Cmd Rej: FPFX must be first in CA set
If specified, the FPFX Conditioning Action must be the first value (fpfx) in the ca value list or ca(X) parameter sequence.
Recovery
Re-enter the ent/chg-npp-as command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Numbering Plan Processor (NPP) User's Guide for more information.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2356 E4971 Cmd Rej: ZNX/DNX/SNX must be last in CA set
The ZNX, SNX, and DNX Conditioning Actions must be the final value (zns, snx, or dnx) in the ca value list or the ca(X) parameter sequence.
Recovery
Re-enter the ent/chg-npp-as command that generated this error, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Numbering Plan Processor (NPP) User's Guide for assistance.
If the error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2357 E4972 Cmd Rej: If specified, NSNP/NSNAI must be none for requested service
If the value specified for the nserv parameter is aiq, atinp, eir, idps, inpq, idpr, ttr, or vflex, then only a value of none can be specified for the nsnai or nsnp parameter.
Recovery
Re-enter the chg-srvsel 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2358 E4973 Cmd Rej: Parameter only valid for TELNET and EMSALM terminals
The pngtimeint and pngfailcnt parameters can be specified only for terminals with terminal type emsalm or telnet.
Recovery
2.2.2359 E4974 Cmd Rej: FCNA and FCNAMASK must not be identical
The fcna and fcnamask parameters must have different values.
Recovery
Re-enter the chg-netopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - System Management User's Guide for assistance.
2.2.2360 E4976 Cmd Rej: Terminal must be inhibited before changing the parameter
The logintmr, logouttmr, pngtimeint, and pngfailcnt parameters can be specified only when the terminal is in the Inhibited state.
Recovery
2.2.2361 E4977 Cmd Rej: At least one TIF feature must be ON
At least one TIF feature must be turned on before an Action Set containing the cdial Service Action can be specified as a value for the asn parameter.
Recovery
2.2.2362 E4978 Cmd Rej: BPIPADDR only valid for E5-SMxG being equipped but inhibited
For the chg-ip-card command, if the card in the location specified by the loc parameter is not an E5-SMxG-B or card is not inhibited then the bpipaddr and bpsubmask parameters cannot be specified.
Recovery
2.2.2363 E4979 Cmd Rej: Cannot set DefCC to NONE, if ATINP feature is ON
If the ATINP feature is turned on, then the defcc=none parameter cannot be specified.
Recovery
2.2.2364 E4980 Cmd Rej: Maximum number of traces already entered
Recovery
- Use the
disp-tracecommand to display trace entries. - Use the
dlt-tracecommand to delete a trace entry as needed. - Re-enter the
ent-tracecommand that generated this error message.
Refer to the command descriptions in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2365 E4981 Cmd Rej: TINP feature must be enabled before upgrade to 39.2 or later
For the chg-gws-actset command, the TINP feature must be enabled before upgrade to 39.2 or later before the tinp stop action can be specified.
The chg-tinpopts command cannot be entered unless the TINP feature was enabled before upgrading to Release 39.2 or later.
Recovery
2.2.2366 E4982 Cmd Rej: At least one TIF feature must be enabled
For the chg-gws-actset command, at least one TIF feature must be enabled before the tif, tif2, or tif3 stop action can be specified.
For the ent/chg-dstn commands, at least one TIF feature must be enabled before the splitiam parameter can be specified.
At least one TIF feature must be enabled before the chg-isup-msg or chg-tifopts commands can be entered.
For the tst-msg command, at least one TIF feature must be enabled before a value of tif, tif2, or tif3 can be specified for the feat parameter.
Recovery
2.2.2367 E4983 Cmd Rej: TIF, TIF2, TIF3, TLNP, TINP,RDCT and SCCP are mutually exclusive
Only one of the tif, tif2, tif3, tlnp, tinp, rdct, and sccp stop actions can be specified in the command.
Recovery
2.2.2368 E4984 Cmd Rej: TIF/TIF2/TIF3/TLNP/TINP/RDCT/SCCP must be last stop action
The tif, tif2, tif2, tlnp, tinp, rdct, or sccp stop action must be the last stop action in the command.
Recovery
2.2.2369 E4985 Cmd Rej: Destination does not support same ITU ntwk alias combination
Two ITUI or two ITUN aliases can be specified for the same destination point code only if the aliases have different prefixes. One alias must be spare and one non-spare.
Recovery
2.2.2370 E4987 Cmd Rej: Service actions CgpnSvcRqd and NPRLS are mutually exclusive
The CGPNSVCRQD and NPNRLS service actions cannot exist within the same action set.
Recovery
- Use the
rtrv-npp-ascommand to see the action set under consideration, to determine whether the CGPNSVCRQD or NPNRLS service action is configured. - Re-enter the
chg/ent-npp-srscommand to associate a service rule set entry to an action set that does not have both the CGPNSVCRQD and NPNRLS service actions configured.
Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2371 E4988 Cmd Rej: TIF SCS Forwarding feature must be ON
The TIF SCS Forwarding feature must be turned on before an Action Set containing the FWDSCS Service Action can be specified as a value for the asn parameter.
Recovery
2.2.2372 E4989 Cmd Rej: TIF Simple Number Substitution feature must be ON
The TIF Simple Number Substitution feature must be turned on before an Action Set containing the SNSCGPN Service Action can be specified as a value for the asn parameter.
Recovery
2.2.2373 E4990 Cmd Rej: Command exceeds 150 character limit
Recovery
Re-enter the command that generated this error message, specifying a maximum of 150 characters. Refer to the command description in Commands User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2374 E4992 Cmd Rej: ITU aliases with matching Spares are not allowed
Spares for aliasn 1 and aliasn 2 must be different, and Spares for aliasi 1 and aliasi 2 must be different.
Recovery
Re-enter the command that generated this message, specifying ITU aliases with non-matching spare point codes. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2375 E4993 Cmd Rej: If specified, (n)action must be PASS when (n)forbid=NONE
If the (n)forbid=none parameter is specified, then the (n)action=pass parameter must be specified.
Recovery
Re-enter the ent/chg-gsmmap-scrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.2376 E4994 Cmd Rej: TIF Number Portability feature must be ON
The TIF NP feature must be turned on before an Action Set containing the CRP, NPNRLS, CGPNNPRQD, NPRELAY, or NPRLS Service Action can be specified as a value for the asn parameter.
Recovery
2.2.2377 E4996 Cmd Rej: MO-SMS B-Party Routing feature must be Enabled
The MO SMS B-Party Routing feature must be enabled before the bpartygttsn or mosmsgttdig parameter can be specified.
Recovery
- Display the status of the MO SMS B-Party Routing feature. Enter the
rtrv-ctrl-featcommand.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.
- Enable the MO SMS B-Party Routing feature as necessary. Refer to the Database Administration - GTT User's Guide for assistance.
- Re-enter the
chg-gsmsmsoptsorchg-is41smsoptscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the G-Port User's Guide (chg-gsmsmsoptscommand) or the A-Port User's Guide (chg-is41smsoptscommand). - Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2378 E4997 Cmd Rej: SETTYPE of specified GTTSET must be CdGTA
Note:
The set type is provisioned using theent-gttset command.
For the chg-gsmsmsopts command, the GTT set specified by the bpartygttsn or is41smscgttsn parameter must have a GTT set type of cdgta.
For the chg-is41smsopts command the GTT set specified by the bpartygttsn parameter must have a GTT set type of cdgta.
For the ent/chg/dlt/rtrv-gtt command, the GTT set associated with the translation type specified by the ttn parameter must have a GTT set type of cdgta.
For the dlt/rtrv-tt command the GTT set associated with the translation type specified by the ttn parameter must have a GTT set type of cdgta.
Recovery
Note:
The Origin-based SCCP Routing (OBSR) feature must be turned on before GTT set type information is shown in the output for thertrv-gttset command.
2.2.2379 E4998 Cmd Rej: BPARTYGTTSN must not be NONE
If the bpartygttsn=none parameter is specified, then the mosmsgttdig=mapbparty parameter cannot be specified.
Recovery
- Enter the
rtrv-gttsetcommand to display a list of GTT sets. - Re-enter the command that generated this message, specifying a valid GTT set as the value for the bpartygttsn parameter.
Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2380 E5001 Cmd Rej: Up to two alias PCs are supported per DPC
A maximum of two alias point codes can be specified per destination point code.
Recovery
2.2.2381 E5002 Cmd Rej: MOSMS IS41 features must be enabled
For the tst-msg command, the MO SMS ASD, MO SMS GRN, MO SMS IS41-to-GSM Migration, or MO-based IS1 SMS NP feature must be enabled before the feat=mosmsnpp and prot=is41 parameters can be specified.
For the chg-is41smsopts command, the MO-based IS41 SMS NP, MO SMS IS41-to-GSM Migration, MO SMS ASD, or MO SMS GRN feature must be enabled before the modaparam, mosmsnai, or mosmsaclen parameter can be specified. The modaparam parameter can also be specified if the MO SMS B-Party Routing feature is enabled.
Recovery
2.2.2382 E5003 Cmd Rej: MOSMS GSM features must be enabled
The MO SMS ASD, MO SMS GRN, Prepaid SMS Intercept Ph1, MO-based GSM SMS NP, or Portability Check for MO SMS feature must be enabled before the feat=mosmsnpp and prot=gsm parameters can be specified.
Recovery
2.2.2383 E5012 Cmd Rej: FCNB and FCNBMASK must not be identical
The same value cannot be specified for the fcnb and fcnbmask parameters.
Recovery
Re-enter the chg-netopts command that generated this error message, specifying a valid cominbation of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.2384 E5013 Cmd Rej: PVN, FCNA and FCNB must not be identical
For the act-upgrade command, the EAGLE PVN address in the source database cannot be identical to the EAGLE FCNA or FCNB network address in the target database.
Caution:
It is strongly recommended that theact-upgrade command be used only in conjunction with the system Upgrade Procedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.
For the chg-eisopts command, the PVN, FCNA, and FCNB network addresses (see the chg-netopts command) must have different values before the eiscopy=on parameter can be specified.
For the chg-netopts command, the same value cannot be specified for the pvn, fcna, and fcnb parameters.
Recovery
2.2.2385 E5015 Cmd Rej: FCMODE must be turned OFF
The fcmode=off parameter must be specified before the eiscopy=off parameter can be specified.
The fcmode=off parameter must be specified to change the value of the fcmode parameter between stc and fcopy.
Recovery
Re-enter the chg-eispopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.2386 E5016 Cmd Rej: TYPE parameter is required
If the loc or mode parameter is specified, then the type parameter must be specified.
Recovery
Re-enter the rept-stat-mon command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.2387 E5018 Cmd Rej: MODE can be specified only when TYPE is eroute
The type=eroute parameter must be specified before the mode parameter can be specified.
Recovery
Re-enter the rept-stat-mon command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.2388 E5019 Cmd Rej: Either LOC or MODE can be specified
The loc and mode parameters cannot be specified together in the command.
Recovery
Re-enter the rept-stat-mon command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.2389 E5020 Cmd Rej: TIF ASD feature must be enabled
The TIF ASD feature must be enabled before an Action Set containing the ASDLKUP or CGPNASDRQD Service Actions can be specified as a value for the asn parameter with the TIF services.
Recovery
2.2.2390 E5021 Cmd Rej: TIF GRN feature must be enabled
The TIF GRN feature must be enabled before an Action Set containing the GRNLKUP or CGPNGRNRQD Service Action can be specified as a value for the asn parameter with the TIF services.
Recovery
2.2.2391 E5022 Cmd Rej: IDPR ASD feature must be enabled
The IDPR ASD feature must be enabled before an Action Set containing the ASDLKUP or CGPNASDRQD Servce Action can be specified as a value for the asn parameter with the IDPRCDPN(X) or IDPRCGPN service.
Recovery
2.2.2392 E5023 Cmd Rej: IDPR GRN feature must be enabled
The IDPR GRN feature must be enabled before an Action Set containing the GRNLKUP or CGPNGRNRQD Service Action can be specified as a value for the asn parameter with the IDPRCDPN(X) or IDPRCGPN service.
Recovery
2.2.2393 E5024 Cmd Rej: Prepaid IDP Query Relay feature must be activated
For the enable/chg-ctrl-feat commands, the Prepaid IDP Query Relay feature must be turned on before the IDP A-Party Blacklist, IDP A-Party Routing, or IDP Service Key Routing feature can be enabled and before the IDPR ASD or IDPR GRN feature can be turned on.
For the ent/chg/rtrv-srvsel commands, the Prepaid IDP Query Relay feature must be turned on before the (n)serv=idpr can be specified.
Recovery
2.2.2394 E5025 Cmd Rej: islsrsb is valid only if ISLSBR Feature is enabled
The SLS Bit Rotation by Incoming Linkset (ISLSBR) feature must be enabled before the islsrsb parameter can be specified.
Recovery
2.2.2395 E5026 Cmd Rej: ASDLKUP, CGPNASDRQD, and TIFRDNBL SAs are mutually exclusive
An Action Set containing the ASDLKUP, CGPNASDRQD, and TIFRDNBL Service Actions cannot be specified as a value for the asn parameter.
Recovery
2.2.2396 E5027 Cmd Rej: GRNLKUP and CGPNGRNRQD SAs are mutually exclusive
An Action Set containing the GRNLKUP and CGPNGRNRQD Service Actions cannot be specified as a value for the asn parameter.
Recovery
2.2.2397 E5028 Cmd Rej: Eroute or Fast Copy card is required
An STC card or an FC-capable card must be provisioned in the system.
Recovery
2.2.2398 E5030 Cmd Rej: MO SMS ASD Feature must be enabled
The MO SMS ASD feature must be enabled before an Action Set containing the ASDLKUP or CGPNASDRQD Service Action can be specified as a value for the asn parameter for the MOSMSGCDPN, MOSMSGCGPN, MOSMSICDPN, or MOSMSICGPN service.
Recovery
2.2.2399 E5031 Cmd Rej: MO SMS GRN Feature must be enabled
The MO SMS GRN feature must be enabled before the an Action Set containing the CGPNGRNRQD or GRNLKUP Service Action can be specified as a value for the asn parameter with the MOSMSGCDPN, MOSMSGCGPN, MOSMSICDPN, or MOSMSICGPN service.
Recovery
2.2.2400 E5032 Cmd Rej: INP CRP feature must be enabled
The INP CRP feature must be enabled before the relcause parameter can be specified.
Recovery
2.2.2401 E5033 Cmd Rej: INP feature must be ON
For the enable-ctrl-feat command the INP feature must be turned on before the INP CRP feature can be enabled.
The INP feature must be turned on before the chg-inpopts command can be entered.
Recovery
2.2.2402 E5035 Cmd Rej: TIF GRN feature cannot be turned ON unless MATCHSEQ is DN
The matchseq=dn parameter must be specified (see the chg-tifopts command) before the TIF GRN feature can be turned on.
Recovery
2.2.2403 E5036 Cmd Rej: TIF ASD feature cannot be turned ON unless MATCHSEQ is DN
The matchseq=dn parameter must be specified (see the chg-tifopts command) before the TIF ASD feature can be turned on.
Recovery
2.2.2404 E5037 Cmd Rej: MATCHSEQ cannot be set to NPTYPE, if TIF ASD Feature is ON
If the TIF ASD feature is turned on, then the matchseq=nptype parameter cannot be specified.
Recovery
2.2.2405 E5038 Cmd Rej: MATCHSEQ cannot be set to NPTYPE, if TIF GRN Feature is ON
If the TIF GRN feature is turned on, then the matchseq=nptype parameter cannot be specified.
Recovery
2.2.2406 E5039 Cmd Rej: MATCHSEQ cannot be NPTYPE unless TIF NP Feature is Enabled
The TIF Number Portability (TIF NP) feature must be enabled before the matchseq=nptype parameter can be specified.
Recovery
2.2.2407 E5040 Cmd Rej: Alternate RI Mate PC must be a full PC
The value specified for the mappc/mappca/mappci/mappcn/mappcn24 and mrnpc/mrnpca/ mrnpci/mrnpcn/mrnpcn24 parameters must be a full point code.
A full point code contains numerical values for all segments of the point code.
Recovery
Re-enter the ent/chg-map or ent/chg-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for more information.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2408 E5041 Cmd Rej: GTT LS ARI Feature must be enabled
For the chg/dlt-map commands, the GTT Load Sharing with Alternate Routing Indicator (GTT LS ARI) feature must be enabled before the mrnset and mrnpc parameters can be specified.
For the chg/dlt-mrn commands, the GTT LS ARI feature must be enabled before the mapset, mappc, or mapssn parameter can be specified.
Recovery
2.2.2409 E5042 Cmd Rej: PC and Alternate RI Mate PC network types don't match
The point codes and alternate RI Mate point codes must have the same network type as shown:
- ITUI, ITU-N, ITU-I spare, ITU-N-spare-ITUI, ITU-N, ITU-I spare, ITU-N-spare
- ANSI-ANSI
- ITUN-24-ITUN-24
Recovery
2.2.2410 E5043 Cmd Rej: MRNPC must be specified when MRNSET is specified
If the mrnset parameter is specified, then the mrnpc parameter must be specified.
Recovery
Re-enter the ent-map command that generated this message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2411 E5044 Cmd Rej: For ITU link sets, ISLSRSB must be in the range (1-4)
If an ITU linkset is used, then a value of 1–4 must be specified for the islsrsb parameter.
Recovery
2.2.2412 E5045 Cmd Rej: At least one card with IPSG GPL must be IS-NR
At least one card must be running the IPSG GPL and must be in the IS-NR state before a value of ipsg or all can be specified for the gpl parameter.
Recovery
2.2.2413 E5047 Cmd Rej: Incorrect Alternate RI Mate is specified
The value specified for the mrnset parameter must already be associated with a MAP Set.
Recovery
2.2.2414 E5048 Cmd Rej: MAPPC/MAPSSN must be specified when MAPSET is specified
If the mapset parameter is specified, then the mappc and mapssn parameters must be specified.
Recovery
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.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2415 E5049 Cmd Rej: MAPPC and MAPSSN must be specified together
The mappc and mapssn parameters must be specified together in the command.
Recovery
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.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2416 E5051 Cmd Rej: MAPPC/MAPSSN does not exist in MAPSET
The values specified for the mappc and mapssn parameters must already exist in the specified MAP Set.
Recovery
2.2.2417 E5052 Cmd Rej: MAPPC/MAPSET does not exist in MAP table
The values specified for the mapset and mappc parameters must already exist in the MAP table.
Recovery
2.2.2418 E5053 Cmd Rej: RSLS8 is only valid for ANSI link sets
The value specified for the lsn parameter must indicate an ANSI linkset before the rsls8=yes parameter can be specified.
Recovery
2.2.2419 E5054 Cmd Rej: PKG and PKGV must not be specified together
The tcappkg and tcappkgv parameters cannot be specified together in the command.
Recovery
Re-enter the chg-sccp-msg command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2420 E5055 Cmd Rej: Flexible GTT Load Sharing Feature must be enabled
The Flexible GTT Load Sharing (FGTTLS) feature must be enabled before the GTT LS ARI feature can be enabled.
Recovery
2.2.2421 E5056 Cmd Rej: FLOBR must be ON before TOBR can be enabled
The Flexible Linkset Optional Based Routing (FLOBR) feature must be turned on before the TCAP Opcode Based Routing (TOBR) feature can be enabled.
Recovery
2.2.2422 E5058 Cmd Rej: VGTT must be ON before enabling VGTT with 16 GTT lengths
The Variable Length GTT (VGTT) feature must be turned on before the Support for 16 GTT Lengths in VGTT feature can be enabled.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.2423 E5059 Cmd Rej: Configuration requires E5-SM4G card or better
For the ent/chg/rtrv-srvsel commands, if a DSM4G card is present in the system, then the on=gttrqd parameter cannot be specified.
For the enable-ctrl-feat command, if a DSM4G card is present in the system, then the FLOBR, GTT Action - DUPLICATE, and VGTT-16 features cannot be enabled.
Recovery
2.2.2424 E5060 Cmd Rej: Flexible Linkset Optional Based Routing must be ON
For the enable-ctrl-feat command, the FLOBR feature must be turned on before the TOBR feature can be enabled.
For the ent/dlt/chg/rtrv-gta command, the FLOBR feature must be turned on before the fallback, cdselid, (e)cdssn,dpc, or testmode parameter can be specified.
For the ent/chg/dlt/rtrv-gttsel command, the FLOBR feature must be turned on before the lsn, eaglegen, cdgttsn, and cggttsn parameters can be specified.
For the ent/rtrv-gttset command, the FLOBR feature must be turned on before a value of cdssn or dpc can be specified for the settype parameter.
Recovery
2.2.2425 E5061 Cmd Rej: Cannot use msgtype/lsn/selid/gttsn/cg* field if eaglegen=yes
If the eaglegen=yes parameter is specified, then the msgtype, lsn, selid, gttsn, cdgtasn, cgssn, cggttsn, cggtasn, and cgpcsn parameters cannot be specified.
Recovery
Re-enter the
ent/chg/dlt/rtrv-gttsel command that
generated this error message, specifying a valid combination of parameters.
Refer to the command description in
Commands User's Guide and to the
Database Administration - GTT User's Guide
for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2426 E5062 Cmd Rej: CDGTTSN and/or CGGTTSN must be specified with LSN
If the lsn parameter is specified, then the cdgttsn or cggttsn parameter must be specified.
Recovery
Re-enter the ent/chg/rtrv-gttsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - GTT User's Guide for assistance.
2.2.2427 E5063 Cmd Rej: OBSR must be enabled or FLOBR must be ON
For the ent/chg-gta commands, the OBSR feature must be enabled or the FLOBR feature must be turned on before the optsn parameter can be specified.
For the ent-gttset command, the OBSR feature must be enabled or the FLOBR feature must be turned on before the settype parameter can be specified and before more than 950 GTT sets can be provisioned.
Recovery
2.2.2428 E5064 Cmd Rej: CDGTASN/CGGTASN/CGPCSN are not valid when FLOBR ON
If the FLOBR feature is turned on, then the cdgtasn, cggtasn, and cgpcsn parameters cannot be specified.
Recovery
2.2.2429 E5066 Cmd Rej: GTT Action table is full
The GTT Action table cannot contain more than 2,000 entries.
Recovery
2.2.2430 E5067 Cmd Rej: Unable to access GTT Action table
The GTT Action table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2431 E5068 Cmd Rej: Uimreqd only valid for DISC/UDTS/TCAPERR/SCPVAL/SFAPP
A value of disc, udts, tcaperr, scpval or sfapp must be specified for the act parameter before a value of uimreqd can be specified for the on or off parameter.
Recovery
Re-enter the
ent/chg/rtrv-gttact command that
generated this error message, specifying a valid combination of parameters.
Refer to the command description in
Commands User's Guide and to
Database Administration - GTT User's Guide
for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2432 E5069 Cmd Rej: (New) GTT Action Id must not be NONE/FALLBACK
For the ent/chg/dlt/rtrv-gttact or ent/chg-gttaset command, a value of none or fallback cannot be specified for the (n)actid parameter.
For the rtrv-gttaset command, a value of fallback cannot be specified for the actid1/actid2/actid3/actid4/actid5/actid6 parameters.
Recovery
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 and to the Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2433 E5071 Cmd Rej: GTT Action Id does not exist
For the ent/chg/dlt/rtrv-gttact command, the GTT Action entry specified by the actid or defactid parameter must already exist in the database.
For the ent/chg-gttaset command, the Action ID specified by the actid1(X) parameter(s) must already exist in the GTT Action Table.
For the ent/chg-lnp-serv command, if a GTT Action ID is specified as the value for the (n)dfltact parameter, then the Action ID must already exist in the GTT Action table.
For the ent/chg/rtrv-srvsel command, if a GTT Action ID is specified as the value for the (n)dfltact parameter, then the Action ID must already exist in the GTT Action table.
Recovery
- Display the existing GTT Action IDs. Enter the
rtrv-gttactcommand. - 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 and to the Database Administration - GTT User's Guide for assistance.
2.2.2434 E5072 Cmd Rej: PC has no allowed route
A routeset and link that provides a path to the new CSPC must be configured before the ent-cspc command can be entered.
For the ent/chg-gttact command, the point code specified by the pc/pca/pci/pcn/pcn24 parameter must be associated with a valid route.
Recovery - ent-cspc
- Verify that the routeset and link path for the new Concerned Signaling Point Code have been configured. Enter the
rtrv-cspccommand. - Configure the routeset and link as needed. Refer to Database Administration - SS7 User's Guide for assistance.
- Re-enter the ent-cspc command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - ent/chg-gttact
2.2.2435 E5073 Cmd Rej: Linkset referenced by GTT selector table
A linkset that is referenced by the GTT selector table cannot be deleted.
Recovery
2.2.2436 E5074 Cmd Rej: ITU destination does not support ANSI/ITU alias combination
If the dpci parameter is specified, then a combination of ITUI and ANSI aliases cannot be specified. If the dpcn parameter is specified, then a combination of ITUN and ANSI aliases cannot be specified.
Recovery
2.2.2437 E5075 Cmd Rej: SLKTPS/RSVDSLKTPS must be less than or equal to MAXSLKTPS
The value specified for the slktps/rsvdslktps parameter must be less than or equal to the value specified for the maxslktps parameter.
Recovery
Re-enter the ent/chg-ls command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.2438 E5080 Cmd Rej: OPTSN or CGSELID/CDSELID is not valid
A value of none must be specified for the optsn, cgselid, or cdselid parameter before the parameter can be changed to another value.
Recovery
Re-enter the chg-gta command that generated this error message, specifying a value of none before changing the parameter. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support If this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2439 E5081 Cmd Rej: IS41SMSCGTTSN can not be none, if DEFIS41SMSC is not none.
If the defis41smsc parameter has a value other than none, then the is41smscgttsn=none parameter cannot be specified.
Recovery
- Display the entries in the GSMSMOPTS table. Enter the
rtrv-gsmsmsoptscommand. - Revise the entries as necessary. Refer to the G-Port User's Guide for assistance.
- Re-enter the
chg-gsmsmsoptscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide for assistance.
2.2.2440 E5082 Cmd Rej: GTT LS ARI feature must be turned OFF
The GTT LS ARI feature must be turned off before the IGTTLS feature can be turned off.
Recovery
2.2.2441 E5083 Cmd Rej: MAPPC can't be TPC or Mate of TPC
The value specified for the mappc parameter cannot match an existing STP point code.
Recovery
2.2.2442 E5084 Cmd Rej: To provision Alternate RI Mate, specify MRNPC
If the mrnset parameter is specified, then the mrnpc, mrnpca, mrnpci, mrnpcn, or mrnpc24 parameter must be specified.
Recovery
Re-enter the chg-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2443 E5085 Cmd Rej: To provision Alternate RI Mate, specify MAPPC/MAPSSN
The mappc and mapssn parameters must be specified together in the command.
Recovery
Re-enter the chg-mrn command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2444 E5086 Cmd Rej: Alternate RI Mate already provisioned
The ent-mrn command cannot be used to change an Alternate RI Mate that has already been specified for an MRN Set.
Recovery
Use the chg-mrn command to modify the Alternate RI Mate. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2445 E5087 Cmd Rej: ESWT, GRPWT and THR can not be specified with ARI Mate PC
If the eswt, grpwt, or thr parameter is specified, then the mrnpc parameter cannot be specified.
Recovery
Re-enter the chg-map command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2446 E5088 Cmd Rej: ARI Mate can't be provisioned for a MAPSET having TPC
If the MAP Set specified by the mapset parameter contains a True Point Code, then the mrnset parameter cannot be specified.
Recovery
2.2.2447 E5089 Cmd Rej: ISLSRSB value must be < 6 when RSLS8 is no
The rsls8=yes parameter (see the chg-lsopts command) must be specified for an ANSI linkset before a value greater than 5 can be specified for the islsrsb parameter.
Recovery
2.2.2448 E5090 Cmd Rej: RSLS8 is valid only if ISLSBR Feature is enabled
The SLS Bit Rotation (ISLSBR) feature must be enabled before the rsls8 parameter can be specified.
Recovery
2.2.2449 E5091 Cmd Rej: TIF Number Substitution feature must be Enabled
For the ent/chg-npp-srs command, the TIF Number Substitution feature must be enabled before an Action Set containing the NSCGPN or NSCDPN Service Action can be specified.
For the chg-tifopts command, the TIF Number Substitution feature must be enabled before the nsaddldata or nspublic parameters can be specified.
Recovery
2.2.2450 E5092 Cmd Rej: NSCgPN and SNSCgPN SAs are mutually exclusive
The Action Set specified by the asn parameter cannot contain both the NSCGPN and SNSCGPN Service Actions.
Recovery
2.2.2451 E5093 Cmd Rej: TIF NS feature cannot be Enabled unless MATCHSEQ is DN
The matchseq=dn parameter must be specified (see the chg-tifopts command) before the TIF Number Substitution feature can be enabled.
Recovery
2.2.2452 E5094 Cmd Rej: MATCHSEQ cannot be NPTYPE, if TIF NS Feature is Enabled
If the TIF Number Substitution feature is enabled, then the matchseq=nptype parameter cannot be specified.
Recovery
2.2.2453 E5095 Cmd Rej: SCCP and CNCF cannot be in the same action set
The SCCP and CNCF stop actions cannot exist in the same Action Set.
Recovery
2.2.2454 E5096 Cmd Rej: Origin Based SCCP Routing feature must be ON.
For the chg-sccpopts command, the Origin-based SCCP Routing (OBSR) feature must be turned on before the dfltgttmode parameter can have a value of acdcd, cgacdcd, acdcgcd, acdcdcg, cgcd, cdcg, or cg.
For the ent/chg-ls command, the OBSR feature must be turned on before the gttmode parameter can have a value of acdcd, cgacdcd, acdcgcd, acdcdcg, cgcd, cdcg, or cg.
Recovery
2.2.2455 E5097 Cmd Rej: RNP and RNPV must not be specified together
The rnp and rnpv parameters cannot be specified together in the command.
Recovery
Re-enter the chg-ainpopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the INP/AINPQ User's Guide for assistance.
2.2.2456 E5098 Cmd Rej: RNAI and RNAIV must not be specified together
The rnai and rnaiv parameters cannot be specified together in the command.
Recovery
Re-enter the chg-ainpopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the INP/AINPQ User's Guide for assistance.
2.2.2457 E5099 Cmd Rej: TCAP Opcode Based Routing feature must be turned ON
For the
chg-sccp-msg, command, a TOBR quantity
feature must be turned on before the
tcapacn, tcappkg, tcappkgv, tcapopcode,
tcapfamily, mapparam, imsidgts, imeidgts,
msisdndgts, vlrdgts, smrpoadgts, smrpdadgts, msisdnnp, smrpoanp, or
smrpdanp parameter can be specified.
For the
enable-ctrl-feat command, the TOBR
feature must be turned on before any of the TOBR quantity features can be
enabled.
For the
ent/rtrv-gttset command, the TOBR
feature must be turned on before the
settype=opcode/imei/imsi/msisdn/vlrnb/smrpoa/smrpda
parameter can be specified.
Recovery
2.2.2458 E5100 Cmd Rej: Larger Opcode Quantity FAK should be provided
A TOBR quantity feature cannot be enabled if a higher quantity level TOBR quantity feature is enabled.
Recovery
Display the quantity level that exists in the system. Enter the rtrv-ctrl-feat command.
Contact My Oracle Support for additional assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2459 E5101 Cmd Rej: Maximum Opcode Quantity FAK already enabled
If the TOBR quantity feature of maximum quantity level is enabled, then no other TOBR Quantity feature can be enabled.
Recovery
Display the TOBR quantity present in the system. Enter the rtrv-ctrl-feat command.
If the maxiumum quantity is enabled, then no recovery is required.
Contact My Oracle Support for additional assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2460 E5102 Cmd Rej: PC/PCA/PCI/PCN must be specified if SSN is specified
If the ssn parameter is specified, then the pc/pca/pci/pcn parameter must be specified.
Recovery
Re-enter the chg-ppsopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2461 E5103 Cmd Rej: OPTSN set domain must be the same as GTTSN set domain
The ANSI/ITU SCCP Conversion feature must be enabled before the GTT set specified by the optsn parameter can have a different domain than the GTT set specified by the gttsn parameter.
Recovery
2.2.2462 E5104 Cmd Rej: DIALPFX must be specified
If the ndialpfx or dltpfx parameter is specified, then the dialpfx parameter must be specified.
Recovery
Re-enter the chg-ainpopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the INP/AINPQ User's Guide for assistance.
2.2.2463 E5105 Cmd Rej: One of the TOBR quantity feature must be ON
A TOBR quantity feature must be turned on before the opcode, pkgtype, acn, family, saddr, eaddr, or defmapvr parameter can be specified.
Recovery
2.2.2464 E5106 Cmd Rej: OPCODE,PKGTYPE,ACN/FAMILY must be specified together
The opcode, pkgtype, and family parameters must be specified together for ANSI TCAP translations. The opcode, pkgtype, and acn parameters must be specified together for ITU TCAP translations.
Recovery
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.
2.2.2465 E5107 Cmd Rej: OPCODE param must be specified if GTTSN settype is OPCODE
If the GTT set specified by the gttsn parameter has a set type of opcode, then the opcode/acn/pkgtype or opcode/family/pkgtype parameters must be specified. These parameters cannot be specified for GTT sets of any other set types.
Recovery
2.2.2466 E5108 Cmd Rej: CDSSN param must be specified if GTTSN settype is CDSSN
If the GTT set specified by the gttsn parameter has a set type of cdssn, then the cdssn parameter must be specified. This parameter cannot be specified for GTT sets with other set types.
Recovery
2.2.2467 E5109 Cmd Rej: Exceeding TOBR Quantity feature OPCODE translations limit
The maximum number of OPCODE translation entries cannot exceed the value that is set by the associated TOBR quantity feature.
Recovery
2.2.2468 E5110 Cmd Rej: OPCSN is valid with cdgta/cdssn/opcode GTTSN type
The GTT set specified by the gttsn parameter must have a set type of cdgta, opcode, or cdssn before the opcsn parameter can be specified.
Recovery
2.2.2469 E5111 Cmd Rej: The GTTSN set name must not be same as OPTSN set name
The same value cannot be specified for the gttsn and optsn parameters.
Recovery
Re-enter the ent/chg-gta command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2470 E5112 Cmd Rej: GTT Action Set is referenced by translations
If the Action Set is referenced by a translation entry, then the Action Set cannot be deleted.
Recovery
2.2.2471 E5113 Cmd Rej: (New) GTT Action Set name must not be none
For the ent-gta command, the actsn=none parameter cannot be specified.
For the ent/chg/dlt/rtrv-gttaset command, the (n)actsn=none parameter cannot be specified.
Recovery
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 and to the Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2472 E5115 Cmd Rej: MO-based IS41 SMS NP must be enabled
For the ent/chg-npp-srs commands, the MO-based IS41 SMS NP feature must be enabled before an Action Set containing the CDPNNP Service Action can be specified as a value for the asn parameter with the MOSMSICDPN service.
For the chg-is41smsopts command, the MO-based IS41 SMS NP feature must be enabled before the mosmstype,defrn, or spfill parameter can be specified.
Recovery
2.2.2473 E5116 Cmd Rej: MO-based GSM SMS NP must be enabled
For the ent/chg-npp-srs commands, the MO-based GSM SMS NP feature must be enabled before an Action Set containing the CDPNNP Service Action can be specified as a value for the asn parameter with the MOSMSGCDPN service.
For the chg-gsmsmsopts command, the MO-based GSM SMS NP feature must be enabled before the mosmstype, defrn, or spfill parameter can be specified.
Recovery
2.2.2474 E5117 Cmd Rej: ALW option invalid for IPSG-M3UA associations
If the value specified for the aname parameter refers to an M3UA association on an IPSG card, then the alw parameter cannot be specified.
Recovery
2.2.2475 E5118 Cmd Rej: MO SMS GSM NP, PPSMS or MO SMS ASD/GRN must be enabled
The MO SMS ASD, MO SMS GRN, MO-based GSM SMS NP, or Prepaid SMS Intercept Ph feature must be enabled before the mosmsaclen, mosmsnai, or mosmssa parameter can be specified.
Recovery
- Display the status of controlled features in the system. Enter the
rtrv-ctrl-featcommand.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.
- Enable the desired feature. Refer to the MO-SMS User's Guide for assistance.
- Re-enter the command that generated this error message.
- Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2476 E5119 Cmd Rej: GTT Action-DISCARD Feature must be enabled
For the ent/chg/rtrv-gttact commands, the GTT Action - DISCARD feature must be enabled before a value of disc, udts, or tcaperr can be specified for the act parameter.
For the rtrv-gttact command, the GTT Action - DISCARD feature must be enabled before the uimreqd, atcaperr, itcaperr, or udtserr parameter can be specified.
Recovery
2.2.2477 E5120 Cmd Rej: GTT Action-DUPLICATE Feature must be enabled
The GTT Action - DUPLICATE feature must be enabled before the act=dup parameter can be specified.
Recovery
2.2.2478 E5121 Cmd Rej: CdPA/CgPA GTT Selector already exists
An entry cannot already exist that matches the eaglegen, gti, tt, and np(v) and nai(v) parameter combination for the specified CdPA and/or CgPA selector.
Recovery
- Display the GTT Selector table. Enter the
rtrv-gttselcommand. - Re-enter the
ent-gttselcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2479 E5122 Cmd Rej: CdPA/CgPA GTT Selector does not exist
The GTT selector specified by the msgtype, gti(x), tt, and np(v) and nai(v) parameters must already exist in the GTT Selector table.
Recovery
- Display the entries GTT Selector table. Enter the
rtrv-gttselcommand. - Re-enter the
chg/dlt-gttselcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2480 E5124 Cmd Rej: SCCP Conversion and FLOBR features must be ON
The ANSI/ITU SCCP Conversion feature must be enabled and the FLOBR feature must be turned on before the cgcnvsn parameter can be specified.
Recovery
2.2.2481 E5127 Cmd Rej: CGCNVSN is invalid when GTTSET type is not cggta/cdgta
The GTT set specified by the gttsn parameter must have a set type of cdgta or cggta (see the ent-gttset command) before the cgcnvsn parameter can be specified.
Recovery
2.2.2482 E5128 Cmd Rej: CGGTASN, CGPCSN and CGGTTSN are mutually exclusive
The cggtasn, cgpcsn, and cggttsn parameters cannot be specified together in the command.
Recovery
Re-enter the ent/chg/rtrv-gttsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2483 E5129 Cmd Rej: GTTSN, CDGTASN and CDGTTSN are mutually exclusive
The gttsn, cdgtasn, and cdgttsn parameters cannot be specified together in the command.
Recovery
Re-enter the ent/chg/rtrv-gttsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2484 E5130 Cmd Rej: CGSSN must not be specified with GTTSN, CDGTTSN or CDGTASN
For the ent/chg/rtrv-gttsel command, if the gttsn, cdgttsn, or cdgtasn parameter is specified, then the cgssn parameter cannot be specified.
For the chg/ent-gttsel commands, if the cggtasn, cgpcsn, or cggttsn parameter is specified, then the cgssn parameter must be specified.
Recovery
2.2.2485 E5131 Cmd Rej: SELID must not be specified with GTTSN or CDGTASN
If the gttsn or cdgtasn parameter is specified, then the selid parameter cannot be specified.
Recovery
Re-enter the ent/chg-gttsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2486 E5132 Cmd Rej: Invalid parameter(s) specified with NP=DFLT and NAI=DFLT
If the np=dflt or nai=dflt parameter is specified, then the cggtasn, cggttsn, cgpcsn, cgssn, eaglegen, lsn, and selid parameters cannot be specified.
Recovery
Re-enter the ent/chg/rtrv-gttsel command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2487 E5133 Cmd Rej: Interchanging IPLIMx/IPGWx Assoc to IPSG Assoc not supported
The value specified for the lhost parameter cannot change the local host for the association from an IPLIMx or IPGWx card to an IPSG card or from an IPSG card to an IPLIMx or IPGWx card.
Recovery
2.2.2488 E5135 Cmd Rej: Primary remote hostname required before alternate
The rhosttype=primary parameter must be specified before the rhosttype=alternate parameter can be specified.
Recovery
Re-enter the chg-assoc command that generated this error message, specifying a valid combination of parameters. Refer to the command description in the Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2489 E5136 Cmd Rej: Remote hostname required with rhosttype
If the rhosttype parameter is specified, then the rhost parameter must be specified.
Recovery
Re-enter the chg-assoc command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - IP7 User's Guide for assistance.
2.2.2490 E5137 Cmd Rej: Arhost value must not match lhost/alhost/rhost
The value specified for the alternate remote host cannot be the same as the value specified for the lhost, alhost, or rhost parameter in the same association.
Recovery
2.2.2491 E5138 Cmd Rej: Rhost value must not match lhost/alhost/arhost
The value specified for the rhost parameter cannot be the same as the value specified for the alternate remote host or for the lhost or alhost parameter in the same association.
Recovery
2.2.2492 E5139 Cmd Rej: CGCNVSN Gttset name cannot be same as GTTSN Gttset name
The value specified for the gttsn parameter cannot be the same as the value specified for the cgcnvsn parameter.
Recovery
2.2.2493 E5140 Cmd Rej: FAMILY parameter is allowed with ANSI TCAP PKGTYPE
If the family parameter is specified, then a value of ansiuni, qwp, qwop, resp, cwp, cwop, ansiabort, or any must be specified for the pkgtype parameter.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2494 E5141 Cmd Rej: ACN parameter is allowed with ITU TCAP PKGTYPE
If the acn parameter is specified, then a value of bgn, ituabort, ituuni, any, end, or cnt must be specified for the pkgtype parameter.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2495 E5143 Cmd Rej: GTT Set specified by OPTSN/OPCSN/CGCNVSN does not exist
The GTT set name specified by the optsn, opcsn, or cgcnvsn parameter must match an existing GTT set name.
Recovery
2.2.2496 E5144 Cmd Rej: PKGTYPE abort requires ACN/FAMILY/OPCODE value none
If the pkgtype=ituabort parameter is specified, then a value of none must be specified for the acn and opcode parameters.
If the pkgtype=ansiabort parameter is specified then a value of none must be specified for the family and opcode parameters.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2497 E5147 Cmd Rej: OPC/CGPC/CDPC/DPC Network Domain must match
The network domain of the values specified for the DPC, OPC, CGPA PC and CDPA PC must match.
Recovery
2.2.2498 E5148 Cmd Rej: Both FAMILY and OPCODE must be NONE if either is NONE
The family and opcode parameters must both have a value of none or neither parameter can have a value of none.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2499 E5149 Cmd Rej: Invalid table entry, can not be repaired by conversion code
The icdpnunknx and icdpnunknX and the gcdpnunknx and gcdpnunknX NPP Action Sets cannot co-exist in the source release.
Recovery
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2500 E5150 Cmd Rej: Info Analyzed Relay Base feature must be enabled
The IAR Base feature must be enabled before the chg-tatr-msg or chg-tatropts command can be entered.
For the enable-ctrl-feat command, the feature must be enabled before the IAR ASD, IAR GRN, or IAR NP feature can be enabled.
For the tst-msg command, the feature must be enabled before the feat=iar parameter can be specified.
Recovery
2.2.2501 E5151 Cmd Rej: Feat cannot be turned OFF if system IP/ATM TPS exceeds 500K
If the provisioned System TPS (SIGTRAN TPS + ATM TPS) is greater than 500,000, then the HIPR2 High Rate Mode feature cannot be turned off.
Recovery
2.2.2502 E5152 Cmd Rej: Info Analyzed Relay NP feature must be enabled
The IAR NP feature must be enabled before an Action Set containing the CDPNNP or CGPNNP Service Action can be specified as a value for the asn parameter with the IARCDPN or IARCGPN service.
Recovery
2.2.2503 E5153 Cmd Rej: Info Analyzed Relay ASD feature must be enabled
The IAR ASD feature must be enabled before an Action Set containing the ASDLKUP or CGPNASDRQD Service Action can be specified as a value for the asn parameter with the IARCDPN or IARCGPN service.
Recovery
2.2.2504 E5154 Cmd Rej: Info Analyzed Relay GRN feature must be enabled
The IAR GRN feature must be enabled before an Action Set containing the GRNLKUP or CGPNGRNRQD Service Action can be specified as a value for the asn parameter with the IARCDPN or IARCGPN service.
Recovery
2.2.2505 E5156 Cmd Rej: IAR NP and Service Portability features must be enabled
The IAR NP and Service Portability features must be enabled before the sporttype parameter can be specified.
Recovery
2.2.2506 E5157 Cmd Rej: DIALPFX must not be NONE
The dialpfx=none parameter cannot be specified.
Recovery
Re-enter the chg-ainpopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the INP/AINPQ User's Guide for assistance.
2.2.2507 E5158 Cmd Rej: ANSI41 AIQ feature must be enabled
The ANSI41 AIQ feature must be enabled before the chg-aiqopts command can be entered.
For the chg-mtc-measopts command, the feature must be enabled before the mtchaiq=on or mtcdaiq=on parameter can be specified.
For the chg/rtrv-sid command, the feature must be enabled before the cpctype=aiq parameter can be specified.
For the ent/chg/rtrv-srvsel command, the feature must be enabled before the (n)serv=aiq parameter can be specified
For the ent/chg/dlt-ss-appl command, the feature must be enabled before the appl=aiq parameter can be specified.
For the rept-ftp-meas command the feature must be enabled before the enttype=aiq parameter can be specified
Recovery
2.2.2508 E5160 Cmd Rej: DIALNAI and SNAI must be specified together
The dialnai and snai parameters must be specified together in the command.
Recovery
Re-enter the chg-ainpopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the INP/AINPQ User's Guide for assistance.
2.2.2509 E5161 Cmd Rej: STP True PC and AIQ Subsystem does not exist in MAP Table
The STP true point code and a MAP entry for the AIQ subsystem must be provisioned in the MAP table before the appl=aiq parameter can be specified.
Recovery
2.2.2510 E5163 Cmd Rej: RFMT with NEC and NEC=NONE combination not allowed
If the nec=none parameter is specified, then values of asdrnnecdn, rnasdnecdn, rnnecdn, rngrnnecdn, and grnrnnecdn cannot be specified for the rfmt parameter.
Recovery
Re-enter the chg-ainpopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the INP/AINPQ User's Guide for assistance.
2.2.2511 E5164 Cmd Rej: NDIALPFX already exists in AINPOPTS Table
The value specified for the ndialpfx parameter cannot already exist in the AINPOPTS table.
Recovery
- Display the existing values in the AINPOPTS table. Enter the
rtrv-ainpoptscommand. - Re-enter the
chg-ainpoptscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the INP/AINPQ User's Guide for assistance.
2.2.2512 E5165 Cmd Rej: DIALPFX doesn't exist in AINPOPTS Table
If the ndialpfx and dialpfx parameters are specified, then the value specified for the dialpfx parameter must already exist in the AINPOPTS table.
Recovery
2.2.2513 E5166 Cmd Rej: Maximum number of DIALPFXs already provisioned
A maximum of 40 Dialed Party Number Prefix values is allowed.
Recovery
2.2.2514 E5167 Cmd Rej: DIALNAI doesn't exist in AINPOPTS Table
If the snai=none parameter is specified, then the value specified for the dialnai parameter must already exist in the AINPOPTS table.
Recovery
2.2.2515 E5168 Cmd Rej: Maximum number of DIALNAIs already provisioned
A maximum of 2 Dialed Party Number Nature of Address values is allowed.
Recovery
2.2.2516 E5169 Cmd Rej: DLTPFX must not be specified, when NDIALPFX is NONE
If the ndialpfx=none parameter is specified, then the dltpfx parameter cannot be specified.
Recovery
Re-enter the chg-ainpopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description inCommands User's Guide and to the INP/AINPQ User's Guide for assistance.
2.2.2517 E5171 Cmd Rej: NONE in SPORTRELAY/RLS is compatible w/ NPTYPE in MATCHSEQ
If the matchseq=nptype parameter is specified, then the only value that can be specified for the sportrelay or sportrls parameter is none. If the sportrelay or sportrls parameter has a value other than none, then the matchseq=nptype parameter cannot be specified.
Recovery
2.2.2518 E5172 Cmd Rej: Invalid action type
For the ent/chg-gttact or ent/chg-gttaset command, a value of disc, udts, or tcaperr must be specified for the (n)defactid parameter.
For the ent/chg-gttaset command, only one Action ID in an Action Set can be associated with an action of type disc, udts, tcaperr, sflog, sfthrot, or srvc. If an action ID associated with the act=fwd parameter is specified, then a value of disc, utds, tcaperr, srvc, or fwd cannot be specified for the act parameter for any other action ID in the Action Set. If an Action ID with an action of srvc is specified, then no other Action ID in the same Action Set can be associated with an act of fwd, disc, udts, tcaperr, or srvc. If the act=dup parameter is specified for 5 action IDs in the Action Set, then the act=dup parameter cannot be specified for the remaining action ID in the Action Set. Action IDs associated with an act of disc, udts, tcaperr, srvc, or fwd must be the last actions in an Action Set. Action IDs associated with an action of sfthrot must be the first action in an Action Set. If the Action Set contains two Action IDs associated with an action of scpval, then the remaining Action ID cannot be associated with an action of scpval.
For the ent/chg-lnp-serv command, if a GTT Action ID is specified as a value for the (n)dfltact parameter, then the GTT Action ID must have a value of disc, udts, or tcaperr.
For the ent/chg-srvsel command, the value specified for the (n)dfltact parameter must be fallback, falltogtt, or a valid GTT Action of type disc/udts/tcaperr.
Recovery
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 and to the Database Administration - GTT User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2519 E5174 Cmd Rej: MTP routed GWS Stop Action feature must be enabled
The MTP Routed GWS Stop Action feature must be enabled before the SCCP stop action can be specified.
Recovery
2.2.2520 E5181 Cmd Rej: Unable to read the AIQ Options Table
The AIQ Options table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2521 E5182 Cmd Rej: AIQ Subsystem is offline in database
The AIQ subsystem must be online before the AIQ subsystem number can be specified as a value for the ssn parameter.
Recovery
2.2.2522 E5184 Cmd Rej: IMT Rate Change sequence is in progress
alw/disc-imt, flash/init-card, init-flash, init-mux, and init-sys commands cannot be entered if the IMT Rate Change sequence is in progress.
For the chg-ctrl-feat command, if the IMT Rate Change sequence is in progress, then the HIPR2 High Rate Mode feature cannot be turned on or off.
Recovery
Re-enter the command that generated this error message after the IMT Rate Change sequence is complete.
2.2.2523 E5185 Cmd Rej: GTT Action Path table is full
The GTT Action Path table cannot contain more than 10000 entries.
Recovery
2.2.2524 E5186 Cmd Rej: Unable to access GTT Action Path table
The GTT Action Path table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2525 E5187 Cmd Rej: Specified Path entry already exists
The GTT Action Path created by the specified combination of parameter values cannot already exist.
Recovery
2.2.2526 E5188 Cmd Rej: Target bus must be IS-NR or IS-ANR
The target bus must be in an in-service normal (IS-NR) or in-service abnormal (IS-ANR) state before the tst-imt command can be entered for an Extended Bit Rate Error Test (BERT).
Recovery
2.2.2527 E5189 Cmd Rej: TIME parameter is required
If the type=extbert parameter is specified, then the time parameter must be specified.
Recovery
Re-enter the tst-imt command that generated this eror message, specifying a valid combination of parameters. Refer to the Commands User's Guide for assistance.
2.2.2528 E5190 Cmd Rej: Password change denied, too soon since last change
The number of days specified by the minintrvl parameter in the chg-secu-dflt command must pass between password changes.
Recovery - login command
Contact the System Administrator to change the number of days.
Recovery - chg-pid command
2.2.2529 E5191 Cmd Rej: Password has too many character matches with old password
chg-secu-dflt command.
Recovery - login command
Re-enter the password, specifying a value with fewer duplicate characters from the existing password.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4 for assistance.
Recovery - chg-pid command
2.2.2530 E5192 Cmd Rej: Password matches a previous password
chg-secu-dflt command, has been reached.
Recovery - login command
Re-enter the password without specifying a previous password as the value.
Recovery - chg-pid command
2.2.2531 E5194 Cmd Rej: INP feature must be enabled
The INP feature must be enabled before the chg-inpopts command can be entered.
Recovery
2.2.2532 E5195 Cmd Rej: AINPQ feature must be enabled
The AINPQ feature must be enabled before the chg-ainpqopts command can be entered.
Recovery
2.2.2533 E5196 Cmd Rej: GTT Action Set does not exist
The GTT Action Set specified by the actsn parameter must already exist in the GTT Action Set table.
Recovery
- Display the existing GTT Action Sets. Enter the
rtrv-gttasetcommand. - 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 and to the Database Administration - GTT User's Guide for assistance.
2.2.2534 E5197 Cmd Rej: Unable to access GTT Action Set table
The GTT Action Set table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2535 E5198 Cmd Rej: GTT Action entry is referenced
For the chg-gttact command, the value specified for the act parameter cannot be changed until the associated Action ID is referenced by an Action Set (see the ent/chg-gttaset commands) or by a forward/scpval/sfthrot/sflog action. The value specified for the act parameter can only be changed from disc/udts/tcaperr to disc/udts/tcaperr.
For the dlt-gttact command, the Action ID specified by the actid parameter cannot be referenced by an Action Set or an action entry that is associated with an action of forward/scpval/sfthrot.
Recovery
2.2.2536 E5199 Cmd Rej: (New) GTT Action Id already exist
The GTT Action entry specified by the (n)actid parameter cannot already exist in the database.
Recovery
- Display the existing GTT Action IDs. Enter the
rtrv-gttactcommand. - Re-enter the
ent/chg-gttactcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2537 E5200 Cmd Rej: GTT Action Set table is full
The GTT Action Set table cannot contain more than 20000 entries.
Recovery
2.2.2538 E5201 Cmd Rej: GTT Action- FORWARD Feature must be enabled
The GTT Action - FORWARD feature must be enabled before the act=fwd parameter can be specified.
Recovery
2.2.2539 E5202 Cmd Rej: DIGMINLEN must be less than or equal to DIGMAXLEN
The value specified for the digminlen parameter must be less than or equal to the value specified for the digmaxlen parameter.
Recovery
- Display the values in the AIQOPTS table. Enter the
rtrv-aiqoptscommand. - Re-enter the
chg-aiqoptscommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Analyzed Information Features User's Guide for assistance.
2.2.2540 E5203 Cmd Rej: PFX and TRIGTYPE must be specified together
The pfx and trigtype parameters must be specified together in the command.
Recovery
Re-enter the chg-aiqopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Analyzed Information Features User's Guide for assistance.
2.2.2541 E5204 Cmd Rej: Max allowed AIQ Trigger Type - Prefix entries Provisioned
A maximum of 20 trigtype - pfx entries can be specified in the AIQOPTS table.
Recovery
2.2.2542 E5205 Cmd Rej: Cannot delete an AIQ Trigger Type that is not Provisioned
The value specified for the trigtype parameter must already exist in the AIQOPTS table.
Recovery
2.2.2543 E5234 Cmd Rej: GTT Action Id already provisioned in GTT Action Set
The GTT Action entry specified by the actid parameter cannot already exist in a GTT Action Set.
Recovery
- Display the existing GTT Action IDs. Enter the
rtrv-gttactcommand. - Re-enter the
ent-gttasetcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2544 E5235 Cmd Rej: (New) GTT Action Set name already exist
The GTT Action entry specified by the nactsn parameter cannot already exist in the database.
Recovery
- Display the existing GTT Action Sets. Enter the
rtrv-gttasetcommand. - Re-enter the
chg-gttasetcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to to the Database Administration - GTT User's Guide for assistance.
2.2.2545 E5236 Cmd Rej: GTT Action Ids should be unique in a GTT Action Set
The same value cannot be specified for the actid1/actid2/actid3/actid4/actid5/actid6 parameter(s).
Recovery
Re-enter the ent/chg-gttaset command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2546 E5245 Cmd Rej: RI must be SSN if PC is the True PC
If the pc/pca/pci/pcn/pcn24 parameter is specified, and the point code is the STP true point code, then the ri=ssn parameter must be specified.
Recovery
- Determine whether the point code is the STP TPC. Enter the
rtrv-sidcommand. - 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.
2.2.2547 E5246 Cmd Rej: New password matches old password
Recovery
Re-enter the password, specifying a value other than the current password.
2.2.2548 E5248 Cmd Rej: Both MASPs must be E5-OAM
For the chg-db command, if the OAM is in mixed mode (contains both OAM and E5-OAM MASPs), and the 10,000 Routesets or Integrated GLS feature is enabled or the Integrated Measurements feature is turned on, then the action=repair parameter cannot be specified.
copy-disk command cannot be entered.
Note:
Contact My Oracle Support before entering thecopy-disk command. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery
2.2.2549 E5252 Cmd Rej: Waiting for Extended BERT to start - retry later
The action=stop parameter cannot be specified because the Extended Bit Rate Error Test (BERT) has not started.
Recovery
Re-enter the tst-imt command after the Extended BERT has started.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2550 E5253 Cmd Rej: Extended BERT is completing, can not be stopped
The action=stop parameter cannot be specified because the Extended Bit Rate Error Test (BERT) is about to complete.
Recovery
Allow the Extended BERT to complete normally.
2.2.2551 E5254 Cmd Rej: Extended BERT is not in progress
The action=stop parameter cannot be specified because an Extended Bit Rate Error Test (BERT) is not running.
Recovery
No action is required.
2.2.2552 E5265 Cmd Rej: Service Portability and LOCREQ response feat must be enabled
The Service Portability and LOCREQ Query Response features must be enabled before the sporttype parameter can be specified.
Recovery
2.2.2553 E5266 Cmd Rej: LOCREQ response feature must be enabled
The LOCREQ Query Response feature must be enabled before the dftlrn parameter can be specified.
Recovery
2.2.2554 E5267 Cmd Rej: DPCx parameter must be specified if GTTSN set type is DPC
If the GTT set specified by the gttsn parameter has a set type of DPC, then the dpc/dpca/dpci/dpcn/dpcn24 parameter must be specified. If the GTT set has a set type other than DPC, then the dpc/dpca/dpci/dpcn/dpcn24 parameter cannot be specified.
Recovery
2.2.2555 E5268 Cmd Rej: XLAT=NONE entry not supported for GTT commands
The xlat=none parameter cannot be specified.
Recovery
Re-enter the chg/dlt-gtt command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2556 E5274 Cmd Rej: Link count exceeds max allowed for scheduled UI reports
If the Integrated Measurements feature is turned on and the link count exceeds 700 links, then the systotstp=on, systottt=on, complnkset=on, complink=on, gtwystp=on, and gtwylnkset=on parameters cannot be specified.
Recovery
2.2.2557 E5275 Cmd Rej: ent-card command for type DSM or SLIC already in progress
Recovery
Re-enter the original ent-card command for which the warning was issued.
2.2.2558 E5277 Cmd Rej: Transition in progress, Retry later
If an OAM/OAMHC to MCP/MCPHC or an MCP/MCPHC to OAMHC transition is in progress, then the oamhcmeas and platformenable parameters cannot be specified.
Recovery
Re-enter the chg-measopts command that generated this error message after the transition is complete. The subsystem alarms are cleared upon completion of the transition. On completion of the transition to the Integrated Measurements, UIM 1170: OAMHC Meas transition complete is displayed.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2559 E5278 Cmd Rej: Integrated Measurements feature must be ON
The Integrated Measurements feature must be turned on before the oamhcmeas=on parameter can be specified.
Recovery
2.2.2560 E5279 Cmd Rej: MEASPLAT or Integrated Measurements feature must be ON
The Measurements Platform or Integrated Measurements feature must be turned on before the chg-measopts, chg-mtc-measopts, rept-ftp-meas, or rept-stat-meas command can be entered.
Note:
Once a feature that is controlled using a feature bit has been turned on, it cannot be turned off.Recovery
2.2.2561 E5283 Cmd Rej: GTMOD table is full
For the act-upgrade command, if the AMGTT data in the GTT Translation table causes the GTMOD table to exceed 100,000 entries, then upgrade cannot occur.
Caution:
It is strongly recommended that this command be used only in conjunction with the system UpgradeProcedure for the target release. The Upgrade Procedure provides step-by-step information on performing an upgrade.For the ent-gtmod command, if the GTMOD table already contains 100,000 entries, then an entry must be deleted before another entry can be added.
Recovery
2.2.2562 E5284 Cmd Rej: Failed reading GTMOD table
The GTMOD table is corrupt or cannot be found.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2563 E5285 Cmd Rej: GTMODID does not exist
The value specified for the gtmodid, atirescgmodid, or psirescgmodid parameters must already exist in the GTMOD table.
Recovery
2.2.2564 E5286 Cmd Rej: GTMODID already exist
The value specified for the (n)gtmodid parameter cannot already exist in the GTMOD table.
Recovery
2.2.2565 E5287 Cmd Rej: GTMODID referenced in Translation/GTT Action tables
If the GTMOD identifier is referenced in the GTT or GTT Action tables, then the identifier cannot be deleted.
Recovery
2.2.2566 E5288 Cmd Rej: INIT-FLASH for MUX card(s) in progress
The HIPR2 High Rate Mode feature cannot be turned on or off until the flashing process executed by the init-flash command is completed on all of the MUX cards.
Recovery
As the flashing process completes for each MUX card, a message appears, stating that the process is complete. Wait until the message has appeared for each card, then re-enter the chg-ctrl-feat command to turn the HIPR2 High Rate Mode feature on or off.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2567 E5289 Cmd Rej: PRECD must be specified when NPD(x) and NSD(x) are specified
If the npdd/npds and nsdd/nsds parameters are specified or were previously specified, then the precd parameter must be specified.
Recovery
2.2.2568 E5290 Cmd Rej: Combined digit length of NPDS & NSDS must not exceed 21
The combined digit length of the values for the specified or previously specified npds and nsds parameters cannot be greater than 21.
Recovery
2.2.2569 E5291 Cmd Rej: CGGTMODID/CDGTMODID does not exist
The values specified for the cggtmodid and cdgtmodid parameters must already exist in the GTMODID table.
Recovery
2.2.2570 E5292 Cmd Rej: GTMODID must not be specified as NONE
The (n)gtmodid=none parameter cannot be specified.
Recovery
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 and to the Database Administration - GTT User's Guide for assistance.
2.2.2571 E5293 Cmd Rej: If NGTI is 4, referred GTT Translation PC cannot be ANSI
If the translation point code for the GTT translation associated with the GTMODID is ANSI, then the ngti=4 parameter cannot be specified.
Recovery
2.2.2572 E5294 Cmd Rej: NNP and NNAI can not be NONE if NGTI is 4
If the ngti=4 parameter is specified or was previously specified, then a value of none cannot be specified for the nnp or nnai parameters.
Recovery
- Display the existing values for the ngti parameter. Enter the
rtrv-gtmodcommand. - Re-enter the
ent/chg-gtmodcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2573 E5295 Cmd Rej: GT0FILL can't be ON if NGTI is NONE
If the ngti=none parameter is specified or was previously specified, then the on=gt0fill parameter cannot be specified.
Recovery
2.2.2574 E5296 Cmd Rej: CDGTMODID/CGGTMODID must not be specified as NONE
A value of none cannot be specified for the cdgtmodid or cggtmodid parameter.
Recovery
Re-enter the command that generated this message, specifying a valid value for the cdgtmodid or cggtmodid parameter. Refer to the command description in Commands User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2575 E5298 Cmd Rej: Default/Fail ACTID must not be specified as NONE
For the
ent/chg/rtrv-srvsel
and
ent/chg-lnp-serv commands, the
(n)dfltact=none parameter cannot be
specified.
For the
ent/chg/rtrv-gttact commands, the
defactid=none or
failactid=none parameter cannot be specified.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2576 E5299 Cmd Rej: PC and CGPC must be of same domain
The pc/pca/pci/pcn/pcn24 and cgpc/cgpca/cgpci/cgpcn/cgpcn24 parameters must have the same domain.
Recovery
2.2.2577 E5310 Cmd Rej: Loop Set must not be specified as NONE
The loopset=none parameter cannot be specified.
Recovery
Re-enter the ent-gttact command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2578 E5314 Cmd Rej: No association exists for a link on the card
All links on the E5-ENET, E5-ENET-B, or SLIC card specified by the loc parameter must have a corresponding association configured.
Note:
For IPLIM-hosted associations and links, a link and association are matched using the link parameter for theent-slk and ent-assoc commands. For IPSG-hosted associations, a link and association are matched using the aname parameter for the ent-slk command.
Recovery
2.2.2579 E5315 Cmd Rej: All associations must use M2PA adapter type
Only M2PA associations can be configured for the IP link at the address specified by the loc parameter.
Recovery
2.2.2580 E5316 Cmd Rej: FCMODE parameter is mandatory with FCGPL parameter
If the fcgpl parameter is specified, then the fcmode parameter must be specified.
Recovery
Re-enter the chg-eisopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - Features User's Guide for assistance.
2.2.2581 E5317 Cmd Rej: At least one card with IPGHC GPL must be IS-NR
At least one card must be running the IPGHC GPL and must be in the IS-NR state before a value of ipghc or all can be specified for the gpl parameter.
Recovery
2.2.2582 E5318 Cmd Rej: GTT Actions Path(s) associated with Translation entry
For the chg-gta and chg-gtt commands, the values specified for the gta and egta parameters must be an exact match to the GTA values referred in GTT Action Path table.
For the dlt-gta and dlt-gtt commands, if a translation entry is referenced in the GTT Action Path table (see the ent-gttact-path command), then the entry cannot be deleted.
Recovery
2.2.2583 E5319 Cmd Rej: At least one set-value combination must be specified
At least one combination of GTT values must be specified in the command.
Recovery
Re-enter the ent/chg/dlt-gttapath command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2584 E5320 Cmd Rej: INVKSERV value must be NONE for specified SRVN value
If the NPP Service specified by the srvn parameter does not support invoking another NPP Service, then only a value of none can be specified for the invkserv parameter.
Recovery
Refer to the Numbering Plan Processor (NPP) User's Guide and to the appropriate feature manual to determine the NPP Services that can be invoked by the NPP Service of interest.
Re-enter the ent/chg-npp-srs 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2585 E5321 Cmd Rej: INVKSERV value must be NONE or TIFCGPN
If the NPP Service specified by the srvn parameter can invoke the TIFCGPN NPP Service, then only a value of tifcgpn or none can be specified for the invkserv parameter.
Recovery
Refer to the Numbering Plan Processor (NPP) User's Guide and to the appropriate feature manual to determine the NPP Services that can be invoked by the NPP Service of interest.
Re-enter the ent/chg-npp-srs 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2586 E5322 Cmd Rej: INVKSERV value must be NONE or TIFCGPN2
If the NPP Service specified by the srvn parameter can invoke the TIFCGPN2 NPP Service, then only a value of tifcgpn2 or none can be specified for the invkserv parameter.
Recovery
Refer to the Numbering Plan Processor (NPP) User's Guide and to the appropriate feature manual to determine the NPP Services that can be invoked by the NPP Service of interest.
Re-enter the ent/chg-npp-srs 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2587 E5323 Cmd Rej: INVKSERV value must be NONE or TIFCGPN3
If the NPP Service specified by the srvn parameter can invoke the TIFCGPN3 NPP Service, then only a value of tifcgpn3 or none can be specified for the invkserv parameter.
Recovery
Refer to the Numbering Plan Processor (NPP) User's Guide and to the appropriate feature manual to determine the NPP Services that can be invoked by the NPP Service of interest.
Re-enter the ent/chg-npp-srs 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2588 E5324 Cmd Rej: FAs ASDOTHER and GRNOTHER require INVKSERV not equal to NONE
If the Action Set specified by the asn parameter contains the ASDOTHER or GRNOTHER Formatting Action, then the invkserv=none parameter cannot be specified.
Recovery
2.2.2589 E5325 Cmd Rej: Action Set with CgPN SAs require Rule INVKSERV equal to NONE
If the Action Set specified by the asn parameter contains the CGPNASDRQD, CGPNGNRQD, CGPNSVCRQD, NSCGPN, or SNSCGPN Service Action, then only a value of none can be specified for the invkserv parameter.
Recovery
2.2.2590 E5326 Cmd Rej: TIF Range CgPN Blacklist feature must be enabled
- an Action Set containing the NOCGPNRLS Service Action can be specified as a value for the asn parameter and a value of tif, tif2, or tif3 can specified for the srvn parameter
- an Action Set containing the FPFXRLS Service Action can be specified as a value for the asn parameter and a value of tifcgpn, tifcgnp2, or tifcgpn3 can specified for the srvn parameter
Recovery
2.2.2591 E5327 Cmd Rej: SA FPFXRLS is mutually exclusive with all other SAs
If the Action Set specified by the asn parameter contains the FPFXRLS Service Action, then no other Service Action can be specified in the Action Set.
Recovery
2.2.2592 E5328 Cmd Rej: SA FPFXRLS requires 2 SA(X)VAL values
If the Action Set specified by the asn parameter contains the FPFXRLS Service Action, then the Action Set must also contain a numerical values list with 2 numerical values.
Recovery
2.2.2593 E5329 Cmd Rej: SA FPFXRLS SA(X)VAL values must be between 0-127
If the AS specified by the asn parameter contains the FPFXRLS Service Action, then the 2 numerical values specified by the numerical values list must each be between 0-127.
Recovery
2.2.2594 E5330 Cmd Rej: SA NOCGPNRLS requires 2 SA(X)VAL values
If the AS specified by the asn parameter contains the NOCGPNRLS Service Action, then the AS must also contain a numerical values list with 2 numerical values.
Recovery
2.2.2595 E5331 Cmd Rej: SA NOCGPNRLS SA(X)VAL values must be between 0-127
If the Action Set specified by the asn parameter contains the NOCGPNRLS Service Action, then the 2 numerical values specified by the numerical values list must each be between 0-127.
Recovery
2.2.2596 E5332 Cmd Rej: TIF Subscr CgPN Blacklist feature must be enabled
The TIF Subscriber CgPN Blacklist feature must be enabled before an Action Set containing the BLRLS or BLNFNDRLS Service Action can be specified as a value for the asn parameter, and a value of tifcgpn, tifcgpn2, or tifcgpn3 can be specified as a value for the srvn parameter.
Recovery
2.2.2597 E5333 Cmd Rej: BLRLS requires 2 SA(X)VAL values
If the Action Set specified by the asn parameter contains the BLRLS Service Action, then the Action Set must also contain a numerical values list with 2 numerical values.
Recovery
2.2.2598 E5334 Cmd Rej: SA BLRLS SA(X)VAL values must be between 0-127
If the Action Set specified by the asn parameter contains the BLRLS Service Action, then the 2 numerical values specified by the numerical values list must each be between 0-127.
Recovery
2.2.2599 E5335 Cmd Rej: SA BLNFNDRLS requires 2 SA(X)VAL values
If the Action Set specified by the asn parameter contains the BLNFNDRLS Service Action, then the Action Set must also contain a numerical values list with 2 numerical values.
Recovery
2.2.2600 E5336 Cmd Rej: SA BLNFNDRLS SA(X)VAL values must be between 0-127
If the Action Set specified by the asn parameter contains the BLNFNDRLS Service Action, then the 2 numerical values specified by the numerical values list must each be between 0-127.
Recovery
2.2.2601 E5337 Cmd Rej: SA1 does not support SA1VAL for specified SRVN value
If the Service specified by the srvn parameter does not support a numerical value list for the first Service Action in the Action Set specified by the asn parameter, then the sa1val parameter in the Action Set can only have a value of none.
Recovery
2.2.2602 E5338 Cmd Rej: SA2 does not support SA2VAL for specified SRVN value
If the Service specified by the srvn parameter does not support a numerical value list for the second Service Action in the Action Set specified by the asn parameter, then the sa2val parameter in the Action Set can only have a value of none.
Recovery
2.2.2603 E5339 Cmd Rej: SA3 does not support SA3VAL for specified SRVN value
If the Service specified by the srvn parameter does not support a numerical value list for the third Service Action in the Action Set specified by the asn parameter, then the sa3val parameter in the Action Set can only have a value of none.
Recovery
2.2.2604 E5340 Cmd Rej: SA4 does not support SA4VAL for specified SRVN value
If the Service specified by the srvn parameter does not support a numerical value list for the fourth Service Action in the Action Set specified by the asn parameter, then the sa4val parameter in the Action Set can only have a value of none.
Recovery
2.2.2605 E5341 Cmd Rej: SA5 does not support SA5VAL for specified SRVN value
If the Service specified by the srvn parameter does not support a numerical value list for the fifth Service Action in the Action Set specified by the asn parameter, then the sa5val parameter in the Action Set can only have a value of none.
Recovery
2.2.2606 E5342 Cmd Rej: SA6 does not support SA6VAL for specified SRVN value
If the Service specified by the srvn parameter does not support a numerical value list for the sixth Service Action in the Action Set specified by the asn parameter, then the sa6val parameter in the Action Set can only have a value of none.
Recovery
2.2.2607 E5343 Cmd Rej: SA7 does not support SA7VAL for specified SRVN value
If the Service specified by the srvn parameter does not support a numerical value list for the seventh Service Action in the Action Set specified by the asn parameter, then the sa7val parameter in the Action Set can only have a value of none.
Recovery
2.2.2608 E5344 Cmd Rej: SA8 does not support SA8VAL for specified SRVN value
If the Service specified by the srvn parameter does not support a numerical value list for the eighth Service Action in the Action Set specified by the asn parameter, then the sa8val parameter in the Action Set can only have a value of none.
Recovery
2.2.2609 E5345 Cmd Rej: SA1 does not support SA1DGTS for specified SRVN value
If the Service specified by the srvn parameter does not support a digit string for the first Service Action in the Action Set specified by the asn parameter, then the sa1dgts parameter in the Action Set can only have a value of none.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2610 E5346 Cmd Rej: SA2 does not support SA2DGTS for specified SRVN value
If the Service specified by the srvn parameter does not support a digit string for the second Service Action in the Action Set specified by the asn parameter, then the sa2dgts parameter in the Action Set can only have a value of none.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2611 E5347 Cmd Rej: SA3 does not support SA3DGTS for specified SRVN value
If the Service specified by the srvn parameter does not support a digit string for the third Service Action in the Action Set specified by the asn parameter, then the sa3dgts parameter in the Action Set can only have a value of none.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2612 E5348 Cmd Rej: SA4 does not support SA4DGTS for specified SRVN value
If the Service specified by the srvn parameter does not support a digit string for the fourth Service Action in the Action Set specified by the asn parameter, then the sa4dgts parameter in the Action Set can only have a value of none.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2613 E5349 Cmd Rej: SA5 does not support SA5DGTS for specified SRVN value
If the Service specified by the srvn parameter does not support a digit string for the fifth Service Action in the Action Set specified by the asn parameter, then the sa5dgts parameter in the Action Set can only have a value of none.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2614 E5350 Cmd Rej: SA6 does not support SA6DGTS for specified SRVN value
If the Service specified by the srvn parameter does not support a digit string for the sixth Service Action in the Action Set specified by the asn parameter, then the sa6dgts parameter in the Action Set can only have a value of none.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2615 E5351 Cmd Rej: SA7 does not support SA7DGTS for specified SRVN value
If the Service specified by the srvn parameter does not support a digit string for the seventh Service Action in the Action Set specified by the asn parameter, then the sa7dgts parameter in the Action Set can only have a value of none.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2616 E5352 Cmd Rej: SA8 does not support SA8DGTS for specified SRVN value
If the Service specified by the srvn parameter does not support a digit string for the eighth Service Action in the Action Set specified by the asn parameter, then the sa8dgts parameter in the Action Set can only have a value of none.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2617 E5353 Cmd Rej: SA1VAL requires SA1 to be provisioned
For the chg-npp-as command, if no Service Actions are provisioned, then only a value of none can be specified for the sa1val parameter.
For the ent-npp-as command, if no Service Actions are provisioned, then the sa1val parameter cannot be specified.
Recovery
2.2.2618 E5354 Cmd Rej: SA2VAL requires SA2 to be provisioned
For the chg-npp-as command, if less than 2 Service Actions are provisioned, then only a value of none can be specified for the sa2val parameter.
For the ent-npp-as command, if less than 2 Service Actions are provisioned, then the sa2val parameter cannot be specified.
Recovery
2.2.2619 E5355 Cmd Rej: SA3VAL requires SA3 to be provisioned
For the chg-npp-as command, if less than 3 Service Actions are provisioned, then only a value of none can be specified for the sa3val parameter.
For the ent-npp-as command, if less than 3 Service Actions are provisioned, then the sa3val parameter cannot be specified.
Recovery
2.2.2620 E5356 Cmd Rej: SA4VAL requires SA4 to be provisioned
For the chg-npp-as command, if less than 4 Service Actions are provisioned, then only a value of none can be specified for the sa4val parameter.
For the ent-npp-as command, if less than 4 Service Actions are provisioned, then the sa4val parameter cannot be specified.
Recovery
2.2.2621 E5357 Cmd Rej: SA5VAL requires SA5 to be provisioned
For the chg-npp-as command, if less than 5 Service Actions are provisioned, then only a value of none can be specified for the sa5val parameter.
For the ent-npp-as command, if less than 5 Service Actions are provisioned, then the sa5val parameter cannot be specified.
Recovery
2.2.2622 E5358 Cmd Rej: SA6VAL requires SA6 to be provisioned
For the chg-npp-as command, if less than 6 Service Actions are provisioned, then only a value of none can be specified for the sa6val parameter.
For the ent-npp-as command, if less than 6 Service Actions are provisioned, then the sa6val parameter cannot be specified.
Recovery
2.2.2623 E5359 Cmd Rej: SA7VAL requires SA7 to be provisioned
For the chg-npp-as command, if less than 7 Service Actions are provisioned, then only a value of none can be specified for the sa7val parameter.
For the ent-npp-as command, if less than 7 Service Actions are provisioned, then the sa7val parameter cannot be specified.
Recovery
2.2.2624 E5360 Cmd Rej: SA8VAL requires SA8 to be provisioned
For the chg-npp-as command, if less than 8 Service Actions are provisioned, then only a value of none can be specified for the sa8val parameter.
For the ent-npp-as command, if less than 8 Service Actions are provisioned, then the sa8val parameter cannot be specified.
Recovery
2.2.2625 E5361 Cmd Rej: SA1DGTS requires SA1 to be provisioned
For the chg-npp-as command, if no Service Actions are provisioned, then only a value of none can be specified for the sa1dgts parameter.
For the ent-npp-as command, if no Service Actions are provisioned, then the sa1dgts parameter cannot be specified.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2626 E5362 Cmd Rej: SA2DGTS requires SA2 to be provisioned
For the chg-npp-as command, if less than 2 Service Actions are provisioned, then only a value of none can be specified for the sa2dgts parameter.
For the ent-npp-as command, if less than 2 Service Actions are provisioned, then the sa2dgts parameter cannot be specified.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2627 E5363 Cmd Rej: SA3DGTS requires SA3 to be provisioned
For the chg-npp-as command, if less than 3 Service Actions are provisioned, then only a value of none can be specified for the sa3dgts parameter.
For the ent-npp-as command, if less than 3 Service Actions are provisioned, then the sa3dgts parameter cannot be specified.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2628 E5364 Cmd Rej: SA4DGTS requires SA4 to be provisioned
For the chg-npp-as command, if less than 4 Service Actions are provisioned, then only a value of none can be specified for the sa4dgts parameter.
For the ent-npp-as command, if less than 4 Service Actions are provisioned, then the sa4dgts parameter cannot be specified.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2629 E5365 Cmd Rej: SA5DGTS requires SA5 to be provisioned
For the chg-npp-as command, if less than 5 Service Actions are provisioned, then only a value of none can be specified for the sa5dgts parameter.
For the ent-npp-as command, if less than 5 Service Actions are provisioned, then the sa5dgts parameter cannot be specified.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2630 E5366 Cmd Rej: SA6DGTS requires SA6 to be provisioned
For the chg-npp-as command, if less than 6 Service Actions are provisioned, then only a value of none can be specified for the sa6dgts parameter.
For the ent-npp-as command, if less than 6 Service Actions are provisioned, then the sa6dgts parameter cannot be specified.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2631 E5367 Cmd Rej: SA7DGTS requires SA7 to be provisioned
For the chg-npp-as command, if less than 7 Service Actions are provisioned, then only a value of none can be specified for the sa7dgts parameter.
For the ent-npp-as command, if less than 7 Service Actions are provisioned, then the sa7dgts parameter cannot be specified.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2632 E5368 Cmd Rej: SA8DGTS requires SA8 to be provisioned
For the chg-npp-as command, if less than 8 Service Actions are provisioned, then only a value of none can be specified for the sa8dgts parameter.
For the ent-npp-as command, if less than 8 Service Actions are provisioned, then the sa8dgts parameter cannot be specified.
Note:
Currently, the sa(X)dgts parameters are not supported by any command.Recovery
2.2.2633 E5369 Cmd Rej: Specified Path entry doesn't exist
The GTT Action Path must already exist in the GTT Action Path table.
Recovery
Re-enter the dlt/rtrv-gttact-path command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2634 E5371 Cmd Rej: Network domain of corresponding ttn must not be CROSS
The network domain of the translation type specified by the ttn parameter cannot be CROSS.
Recovery
- Display the network types. Enter the
rtrv-gttsetcommand. - Change the network domain if desired. Refer to the Database Administration - GTT User's Guide for assistance.
- 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.
2.2.2635 E5372 Cmd Rej: Loc contains invalid hardware
An E5-ENET or E5-ENET-B card must be installed in the location indicated by the loc parameter. The card must have a card type of DCM and must be running an IPLIMx application.
Recovery
2.2.2636 E5373 Cmd Rej: LOCREQ response feature must be activated
The LOCREQ Query Response feature must be turned on before a value of locreqrspnd can be specified for the on or off parameter.
Recovery
2.2.2637 E5374 Cmd Rej: Overlapped translation type does not exist
An overlapped translation type must exist before the ovrlapd parameter can be specified.
Recovery
Re-enter the rtrv-tt command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance
2.2.2638 E5375 Cmd Rej: Specified CgGTA/CdGTA not a start GTA in a Translation entry
The GTA value specified by the cggta or cdgta parameter must be the start GTA in the translation entry.
Recovery
- Display the global title addresses in the Global Title Translation table. Enter the
rtrv-gtacommand. - Re-enter the
ent/chg-gtta-pathcommand that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - GTT User's Guide for assistance.
2.2.2639 E5376 Cmd Rej: Specified path name already exists
The value specified for the (n)gttpn parameter cannot already exist in the database.
Recovery
2.2.2640 E5377 Cmd Rej: Path name and GTT set-value can't be specified together
Both path name and set-value combination(s) cannot be specified together.
Recovery
Re-enter the rtrv-gttapath command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - GTT User's Guide for assistance.
If this error message appears again, contact My Oracle Support. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2641 E5378 Cmd Rej: Specified path name doesn't exist
The value specified for the gttpn parameter must already exist in the database.
Recovery
2.2.2642 E5379 Cmd Rej: IMT Rate Change sequence is in progress on the specified bus
If an IMT Rate Change sequence is in progress on the specified bus, then the force=yes parameter must be specified.
Recovery
Re-enter the inh-imt command that generated this error message, specifying the force=yes parameter, or re-enter the command after the IMT Rate Change sequence is complete.
2.2.2643 E5380 Cmd Rej: IMT Rate Change sequence is in progress on the alternate bus
If an IMT Rate Change sequence is in progress on the alternate bus, then this command cannot be entered.
Recovery
Re-enter the inh-imt command that generated this error message after the IMT Rate Change sequence on the alternate bus is complete.
OR
Enter the inh-imt command that generated this error message, specifying the force=yes parameter and using the alternate bus as the value for the bus parameter.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2644 E5381 Cmd Rej: If FGTTLS feat enabled, specify MAPSET and/or MRNSET
If the Flexible GTT Loadsharing (FGTTLS) feature is enabled, and the xlat=none parameter is specified, then the mapset and/or mrnset parameter must be specified.
Recovery
2.2.2645 E5382 Cmd Rej: MRNSET is being referred by GTT Table entities
An MRN set cannot be deleted if the MRN set is referenced in the GTT table without an associated point code.
Recovery
2.2.2646 E5383 Cmd Rej: Not enough memory on card
The card must have sufficient DRAM memory to perform the GTMOD table Health Check during upgrade.
Recovery
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2647 E5384 Cmd Rej: XUDT UDT Conversion feature must be activated
The XUDT UDT Conversion feature must be turned on before the sccpmsgcnv parameter can be specified.
Recovery
2.2.2648 E5385 Cmd Rej: EPM-B based card(s) present in IS_NR/IS_ANR state
The EPM-B based card(s) must be in the OOS-MT-DSBLD before Message Flow Control can be turned OFF.
Recovery
2.2.2649 E5389 Cmd Rej: LOC must be specified with HISTORY
If the history parameter is specified, then the loc parameter must be specified.
Recovery
Re-enter the rept-stat-iptps command that generated this error message, specifiying a valid combination of parameters. Refer to the command description in Commands User's Guide and the Database Administration - IP7 User's Guide for assistance.
2.2.2650 E5390 Cmd Rej: PCT table is full
The PCT table contains the maximum entries allowed by the FAK associated with the enabled PCT feature.
Recovery
2.2.2651 E5391 Cmd Rej: PCT feature must be enabled
A PCT quantity feature must be enabled before the ent/chg/dlt/rtrv-pct command can be entered.
For the chg-lsopts, chg-stpopts, and rtrv-ls commands, a PCT quantity feature must be enabled before the pct parameter can be specified.
Recovery
2.2.2652 E5392 Cmd Rej: The PCT table is corrupt or cannot be found
The PCT table is corrupt or cannot be found by the system.
Recovery
Re-enter the command that generated this error message.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2653 E5393 Cmd Rej: Duplicate keys are not allowed
- EPC/EPCA/EPCI/EPCN + FILTPC/FILTPCA/FILTPCI/FILTPCN + SI + SSN/(ECICS/ECICE)
- REALPC/REALPCA/REALPCI/REALPCN + FILTPC/FILTPCA/FILTPCI/FILTPCN + SI + SSN/(RCICS/RCICE)
Recovery
2.2.2654 E5394 Cmd Rej: Group Code of EPC, RealPC and FiltPC must match
If the ITUDUPPC feature is on and ITU-N Point codes are specified, then the values specified for the epcn, realpcn, and filtpcn parameters must have the same group code.
Recovery
2.2.2655 E5395 Cmd Rej: Maximum PCT Quantity FAK already enabled
If the maximum quantity PCT feature is already enabled, then a PCT feature of lower quantity cannot be enabled.
Recovery
Display the status of of the PCT feature. Enter the rtrv-ctrl-feat command.
If the feature does not appear in the output then the feature is not enabled.
If the maximum quantity PCT feature is enabled, no further action can be taken.
Contact My Oracle Support if additional assistance is required. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2656 E5396 Cmd Rej: Larger PCT Quantity FAK is required
A PCT quantity feature cannot be enabled if a PCT feature with a higher quantity is already enabled.
Recovery
Display the status of the PCT feature. Enter the rtrv-ctrl-feat command.
If the feature does not appear in the output then the feature is not enabled.
If a PCT with a higher quantity than the desired quantity is already enabled, then no further action can be taken.
Contact My Oracle Support if additional assistance is required. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2657 E5397 Cmd Rej: Cannot delete last route to DPC referenced in PCT table
The last route to a destination point code that exists in the PCT table cannot be deleted until the Filter Point Code or the Real Point Code is deleted from the table.
Recovery
2.2.2658 E5398 Cmd Rej: Max no of unique EPCs/RealPCs cannot exceed 250
A total of 250 unique emulated point code and real point code values are supported in the PCT table.
Recovery
2.2.2659 E5399 Cmd Rej: Max no of PCT Translations per EPC/RealPC cannot exceed 100
A total of 100 PCT Translations with a single emulated point code and real point code is supported in the PCT table.
Recovery
2.2.2660 E5400 Cmd Rej: Spare point code is not allowed
A spare point code cannot be specified as a value for the epci/epcn, filtpci/filtpcn, and realpci/realpcn parameters.
Recovery
Re-enter the ent/dlt/rtrv-pct command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.2661 E5401 Cmd Rej: Single translation entry not found
The PCT translation entry with the specified parameters must already exist in the PCT table.
Recovery
2.2.2662 E5404 Cmd Rej: LSN or LOC must be specified with TPSCOST
If the tpscost parameter is specified, then the loc or lsn parameter must be specified.
Recovery
Re-enter the rept-stat-iptps command that generated this error message, specifiying a valid combination of parameters. Refer to the command description in Commands User's Guide and the Database Administration - IP7 User's Guide for assistance.
2.2.2663 E5410 Cmd Rej: Command supported only for IPSG linksets
The linkset specified by the lsn parameter must indicate an IPSG linkset.
Recovery
2.2.2664 E5411 Cmd Rej: LOC is valid with HISTORY, TPSCOST, or PEAKRESET set to YES
For the rept-stat-iptps command, if the loc parameter is specified, then the history, tpscost, or peakreset parameter must be specified.
Recovery
Re-enter the rept-stat-iptps command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and the Database Administration - IP7 User's Guide for assistance.
2.2.2665 E5412 Cmd Rej: Linkset type must be A for SLTSET=0
The sltset=0 parameter can be specified only for a type A linkset.
Recovery
2.2.2666 E5413 Cmd Rej: EPAP Data Split feature must be turned on
The EPAP Data Split feature must be turned on before DN or IMSI can be specified for the type parameter for VSCCP.
Recovery
2.2.2667 E5414 Cmd Rej: DATA parm must be specified with VSCCP/SIPHC/IPSG Appl
For the
chg/ent-card command,
if the EPAP Data Split feature is ON or the Dual ExAP
Config feature is enabled, and the value specified for the
loc parameter indicates an
E5-SM8G-B or SLIC card, then the
data parameter must be specified.
The
data parameter can be specified
only for an E5-SM8G-B or SLIC card running the VSCCP or SIPHC application or
for an IPSCP or SLIC running the GTT-enabled IPSG application card.
Note:
The data parameter is valid only for GTT-enabled IPSG cards, and not ENET/ENETB IPSG cards.For the
init-card command, the DATA parameter
can be specified only for VSCCP/SIPHC/IPSG application cards.
Recovery
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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2668 E5415 Cmd Rej: Feature can not be enabled with non-SMXG VSCCP in system
For the chg-stpopts command, the ANSIGFLEX option can not be turned ON if DSM is equipped in the system and one or more following feature are Enabled.
- 1100 TPS/DSM for ITU NP
- Port
- AINPQ
- ATINP
- EIR
- G-Flex MAP Layer Routing
- G-Port
- Info Analyzed Relay Base
- INP
- IS41 GSM Migration
- Prepaid Short Message Intercept Phase 1 (PPSMS)
- MO SMS ASD
- MO SMS GRN
- MO SMS IS41-to-GSM Migration
- MO-based GSM SMS NP
- MO-based IS41 SMS NP
- Portability Check for MO SMS
- TIF Number Portability
- TIF Number Substitution
- TIF Subscriber CgPN Blacklist
- V-Flex
- TIF Selective Screening
For the enable-ctrl-feat command, the following features can not be enabled if the ANSIGFLEX system option is ON (see the rtrv-stpopts command) and a DSM is equipped in the system.
- 1100 TPS/DSM for ITU NP
- ANSI-41 INP Query (AINPQ)
- A-Port
- ATINP
- Equipment Identity Register (EIR)
- G-Flex MAP Layer Routing
- G-Port
- Info Analyzed Relay Base
- INP
- IS41 GSM Migration (IGM)
- MO SMS ASD
- MO SMS GRN
- MO SMS IS41-to-GSM Migration
- MO-based GSM SMS NP
- MO-based IS41SMS NP
- Portability Check for MO SMS
- TIF Number Portability
- TIF Number Substitution
- TIF Subscriber CgPN Blacklist
- V-Flex
Recovery
2.2.2669 E5424 Cmd Rej: Invalid SI value specified
The si=3 parameter must be specified before the ssn parameter can be specified.
A value of 4, 5, or 13 must be specified for the si parameter before the ecice/ecics and rcice/rcics parameters can be specified.
A value of 5 or 13 must be specified for the si parameter before the relcause parameter can be specified.
Recovery
Re-enter the ent/dlt/rtrv-pct command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.2670 E5425 Cmd Rej: DN, IMSI are valid for DATA param
If the EPAP Data Split feature is ON, a value of dn or imsi must be specified for the data parameter for VSCCP.
Caution:
The data=epap parameter can only be specified by Oracle personnel. Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.Recovery
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.
2.2.2671 E5426 Cmd Rej: ECICS/ECICE and RCICS/RCICE should be in same range
The difference between the values specified for the ecice and ecics parameters must be equal to the difference between the values specified for the rcice and rcics parameters.
Recovery
Re-enter the ent/dlt/rtrv-pct command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2672 E5428 Cmd Rej: NAI, TON, and MAP must be specified together
The nai, ton, and map parameters must be specified together in the command.
Recovery
Re-enter the chg-ttrops command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the IDP-Related Features User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2673 E5429 Cmd Rej: Same option can't be spec in MAPLYRRTGON and MAPLYRRTGOFF
The same MAP operation cannot be specified by the maplyrrtgon and maplyrrtgoff parameters in the same command.
Recovery
Re-enter the chg-gsmopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to G-Flex C7 Relay User's Guide for assistance.
2.2.2674 E5430 Cmd Rej: If MAPLYRRTGON/MAPLYRRTGOFF is ALL no option can be spec
If a value of all is specified for the maplyrrtgon or maplyrrtgoff parameter, then no other value can be specified for either of these parameters in the same command.
Recovery
Re-enter the chg-gsmopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to G-Flex C7 Relay User's Guide for assistance.
2.2.2675 E5431 Cmd Rej: If MAPLYRRTGON is ALL, MAPLYRRTGOFF cannot be specified
If the maplyrrtgon=all parameter is specified, then the maplyrrtgoff parameter cannot be specified in the same command.
Recovery
Re-enter the chg-gsmopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to G-Flex C7 Relay User's Guide for assistance.
2.2.2676 E5432 Cmd Rej: If MAPLYRRTGOFF is ALL, MAPLYRRTGON cannot be specified
If the maplyrrtgoff=all parameter is specified, then the maplyrrtgon parameter cannot be specified in the same command.
Recovery
Re-enter the chg-gsmopts command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to G-Flex C7 Relay User's Guide for assistance.
2.2.2677 E5433 Cmd Rej: ECIC/Real CIC range can't be same if EPC is same as Real PC
If the same value is specified for the epc and realpc parameters, then the values specified for the ecics/ecice and rcics/rcice parameters cannot indicate the same range.
Recovery
Re-enter the ent/dlt/rtrv-pct command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to Database Administration - SS7 User's Guide for assistance.
Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2678 E5434 Cmd Rej: Can't delete DSTN that has exception route
If an exception route is associated with a cluster member, then the cluster member cannot be deleted.
Recovery
2.2.2679 E5437 Cmd Rej: VCI value greater than 16383 not allowed
If a 3 Links per E5-ATM Card feature quantity is enabled, and an E5-ATM or E5-ATM-B card is used, then a value less than or equal to 16383 must be specified for the vci parameter.
Recovery
2.2.2680 E5438 Cmd Rej: 3 Links per E5-ATM card feature must be enabled
For the ent-ee-flt command, if the appl = atm and port = a1 or port=all parameters are specified, then the 3 Links per E5-ATM feature must be on.
For the ent-slk command, a 3 Links per E5-ATM Card feature quantity must be enabled before the link=a1 parameter can be specified for an E5-ATM or E5-ATM-B card.
Recovery
2.2.2681 E5439 Cmd Rej: ATM link with VCI greater than 16383 exists
The VCI value for any ATM link (see the ent-slk command) must be less than or equal to 16383 before a 3 Links per E5-ATM Card feature quantity can be enabled.
Recovery
2.2.2682 E5440 Cmd Rej: Only one of FILTPC/A, FILTPCI, or FILTPCN may be specified
Only one of the filtpc/filpca, filtpci, or filtpcn parameters can be specified in the command.
Recovery
Re-enter the ent/dlt/rtrv-pct command that generated this error message, specifying a valid combination of parameters. Refer to the command description in Commands User's Guide and to the Database Administration - SS7 User's Guide for assistance.
2.2.2683 E5462 Cmd Rej: Number of ATM cards with 3 links exceeds allowable quantity
The maximum number of E5-ATM or E5-ATM-B cards with 3 links cannot exceed the value that is set by the 3 Links per E5-ATM Card quantity feature.
Recovery
2.2.2684 E5466 Cmd Rej: Point Code matches an Emulated Point Code in PCT table
For the chg-sid command, the values specified for the cpc/cpca/cpci/cpcn, ncpc/ncpca/ncpci/npcn, npc/npca/npci/npcn, and pc/pca/pci/pcn parameters cannot be the same as any Emulated Point Code (EPC) value in the PCT table.
For the ent-spc command, the value specified for the spc/spca/spci/spcn/spcn24 parameter cannot be the same as any EPC value in the PCT table.
Recovery
2.2.2685 E5467 Cmd Rej: Invalid value specified for the parameter
For the chg-assoc command, RHOSTTYPE = alternate cannot be specified with diameter association.
For the chg-stpopts command, the off=mfc parameter cannot be specified. My Oracle Support must assist with turning off the Message Flow Control option and returning control to TVG.
chg-assoc- Re-enter the
chg-assoccommand, specifying a valid value for the RHOSTTYPE parameter.Refer to the command description in Commands User's Guide for assistance. Contact My Oracle Support if this error message appears again. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
Recovery - chg-stpopts
Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2686 E5469 Cmd Rej: MAPSET is being referred by GTT Table entities
If the MAP set is referenced in the GTT table without an associated point code and subsystem number, then the MAP set cannot be deleted.
Recovery
2.2.2687 E5474 Cmd Rej: Card does not support specified data type
The value specified by the loc parameter must indicate a DN or IMSI card before the dn or imsi parameter can be specified, respectively.
Recovery
2.2.2688 E5475 Cmd Rej: MFC option can be changed once within 10 secs
The status of the mfc option cannot be changed more than once within 10 seconds.
Note:
After the mfc option has been configured to ON, it can only be configured to OFF by My Oracle Support.Recovery
Wait for 10 seconds, after the initial status change, then re-enter the chg-stpopts command that generated this error emssage. Contact My Oracle Support for assistance. See unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2689 E5476 Cmd Rej: Invalid RQDTBLNOP value for service
If a value of inpq, vflex, aiq, ati, or eir is specified for the (n)serv parameter, then the (n)rqdtblnop=gtt parameter cannot be specified.
Recovery
2.2.2690 E5477 Cmd Rej: RQDTBLNOP must NOT be specified
For the ent/chg-srvsel command, if a value of aiq or idps is specified for the (n)serv parameter, then the (n)rqdtblnop parameter cannot be specified.
For the ent/chg-ss-appl command, if the appl=aiq parameter is specified, then the (n)rqdtblnop parameter cannot be specified.
Recovery
2.2.2691 E5478 Cmd Rej: EPAP Data Split feature must be Enabled
For the chg-sccpopts command, the EPAP Data Split feature must be enabled before the gttdist={dn, imsi} parameter can be specified.
For the rept-stat-mfc command, the EPAP Data Split feature must be enabled before a value of scpdn or scpimsi can be specified for the service parameter.
For the rept-stat-sccp command, the EPAP Data Split feature must be turned on before the data={dn, imsi} parameter can be specified.
Recovery
2.2.2692 E5480 Cmd Rej: This upgrade action is unavailable in this release
Recovery
Re-enter the act-upgrade command, 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2693 E5481 Cmd Rej: THRES parameter not valid when using threstype = SET
Recovery
Re-enter the act-upgrade command, 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2694 E5482 Cmd Rej: SRVSETS or LIMSETS not valid unless threstype = SET
Recovery
Re-enter the chg-upgrade-config command, 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2695 E5483 Cmd Rej: LOC must be specified with ASSIGNSET
Recovery
Re-enter the chg-upgrade-config command, 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.
2.2.2696 E5484 Cmd Rej: ASSIGNSET value out of range for card group
Recovery
Re-enter the chg-upgrade-config command, 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 unresolvable-reference.html#GUID-CE2CF44E-63C8-4F31-9F3C-82D4F47787B4.