Oracle Error Messages: 11/16/11

NNL-00993: Auto-refresh failure retry expiration: string

NNL-00993: Auto-refresh failure retry expiration: string

Cause: Control program statistic description

Action: None.

NNL-00992: Auto-refresh failure retry interval: string

NNL-00992: Auto-refresh failure retry interval: string

Cause: Control program statistic description

Action: None.

NNL-00991: Maximum number of reforwards per request: number

NNL-00991: Maximum number of reforwards per request: number

Cause: Control program statistic description

Action: None.

NNL-00990: DEFAULT-FORWARDERS-ONLY mode: string

NNL-00990: DEFAULT-FORWARDERS-ONLY mode: string

Cause: Control program statistic description

Action: None.

NNL-00989: Objects received with no TTL: number

NNL-00989: Objects received with no TTL: number

Cause: Control program statistic description

Action: None.

NNL-00988: Non-authoritative NACKs received: number

NNL-00988: Non-authoritative NACKs received: number

Cause: Control program statistic description

Action: None.

NNL-00987: Authoritative answers when authority: number

NNL-00987: Authoritative answers when authority: number

Cause: Control program statistic description

Action: None.

NNL-00986: Reforwarded requests expired: number

NNL-00986: Reforwarded requests expired: number

Cause: Control program statistic description

Action: None.

NNL-00985: Requests reforwarded using referrals: number

NNL-00985: Requests reforwarded using referrals: number

Cause: Control program statistic description

Action: None.

NNL-00984: Name-to-hint translations failed: number

NNL-00984: Name-to-hint translations failed: number

Cause: Control program statistic description

Action: None.

NNL-00983: Name-to-hint translations: number

NNL-00983: Name-to-hint translations: number

Cause: Control program statistic description

Action: None.

NNL-00982: Not forwarded, no servers found: number

NNL-00982: Not forwarded, no servers found: number

Cause: Control program statistic description

Action: None.

NNL-00981: Timeouts, server not responding: number

NNL-00981: Timeouts, server not responding: number

Cause: Control program statistic description

Action: None.

NNL-00980: Forwarding failures: number

NNL-00980: Forwarding failures: number

Cause: Control program statistic description

Action: None.

NNL-00975: Desired data type: string

NNL-00975: Desired data type: string

Cause: Control program statistic description

Action: None.

NNL-00974: Name: string

NNL-00974: Name: string

Cause: Control program statistic description

Action: None.

NNL-00973: Query state: number

NNL-00973: Query state: number

Cause: Control program statistic description

Action: None.

NNL-00972: Query next issued in: string

NNL-00972: Query next issued in: string

Cause: Control program statistic description

Action: None.

NNL-00971: Query ID: number

NNL-00971: Query ID: number

Cause: Control program statistic description

Action: None.

NNL-00970: System query index number: number

NNL-00970: System query index number: number

Cause: Control program statistic description

Action: None.

NNL-00963: Timeouts, name TTL expired: number

NNL-00963: Timeouts, name TTL expired: number

Cause: Control program statistic description

Action: None.

NNL-00962: Cache checkpoint failures: number

NNL-00962: Cache checkpoint failures: number

Cause: Control program statistic description

Action: None.

NNL-00961: Cache checkpoints: number

NNL-00961: Cache checkpoints: number

Cause: Control program statistic description

Action: None.

NNL-00960: Time until cache flush: string

NNL-00960: Time until cache flush: string

Cause: Control program statistic description

Action: None.

NNL-00959: Time until cache dump to trace file: string

NNL-00959: Time until cache dump to trace file: string

Cause: Control program statistic description

Action: None.

NNL-00958: Name nodes freed: number

NNL-00958: Name nodes freed: number

Cause: Control program statistic description

Action: None.

NNL-00957: Name nodes created: number

NNL-00957: Name nodes created: number

Cause: Control program statistic description

Action: None.

NNL-00956: Hash tables freed: number

NNL-00956: Hash tables freed: number

Cause: Control program statistic description

Action: None.

NNL-00955: Hash tables enlarged: number

NNL-00955: Hash tables enlarged: number

Cause: Control program statistic description

Action: None.

NNL-00954: Hash tables created: number

NNL-00954: Hash tables created: number

Cause: Control program statistic description

Action: None.

NNL-00953: Cache lookup exact matches: number

NNL-00953: Cache lookup exact matches: number

Cause: Control program statistic description

Action: None.

PCB-00314: DECLARE DATABASE is an Oracle extension

PCB-00314: DECLARE DATABASE is an Oracle extension

Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the DECLARE DATABASE statement was used.

Action: No action required. However, for ANSI or ISO compliance, do not use this statement.

PCB-00313: TO SAVEPOINT clause is an Oracle extension

PCB-00313: TO SAVEPOINT clause is an Oracle extension

Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the TO SAVEPOINT lamp;lt;lamp;nbsp;save_idlamp;gt; clause was used in a ROLLBACK statement.

Action: No action required. However, for ANSI or ISO compliance, do not use the TO SAVEPOINT clause.

PCB-00312: Keyword WORK required here by ANSI

PCB-00312: Keyword WORK required here by ANSI

Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the keyword WORK was used in a COMMIT or ROLLBACK statement. For example, the offending code might look like: EXEC SQL COMMIT WORK RELEASE END-EXEC. This informational message is issued by the FIPS Flagger when FIPS=YES.

Action: No action required. However, for ANSI or ISO compliance, do not use the keyword WORK.

PCB-00311: Datatype equivalencing is an Oracle extension

PCB-00311: Datatype equivalencing is an Oracle extension

Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the EXEC SQL VAR statement was used.

Action: No action required. However, for ANSI or ISO compliance, do not use the EXEC SQL VAR statement.

PCB-00309: The CONNECT statement is Oracle implementation dependent

PCB-00309: The CONNECT statement is Oracle implementation dependent

Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the CONNECT statement was used to log on to ORACLE. For example, the offending code might look like: EXEC SQL CONNECT :USERNAME IDENTIFIED BY :PSSWORD END-EXEC. This informational message is issued by the FIPS Flagger when FIPS=YES.

Action: No action required. However, for ANSI or ISO compliance, specify the AUTO_CONNECT command-line option instead of using a CONNECT statement.

PCB-00307: DROP TABLE statement is an Oracle extension

PCB-00307: DROP TABLE statement is an Oracle extension

Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the DROP TABLE statement was used. This informational message is issued by the FIPS Flagger when FIPS=YES.

Action: No action is required. However, for ANSI or ISO compliance, do not use the DROP statement.

PCB-00306: CREATE FUNCTION or PROCEDURE or PACKAGE or TRIGGER are Oracle extensions

PCB-00306: CREATE FUNCTION or PROCEDURE or PACKAGE or TRIGGER are Oracle extensions

Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, one of the following statements was used: o CREATE FUNCTION o CREATE PROCEDURE o CREATE PACKAGE o CREATE TRIGGER This informational message is issued by the FIPS Flagger when FIPS=YES.

Action: No action is required. However, for ANSI or ISO compliance, do not use any of these statements.

PCB-00305: Oracle extension to the COMMIT and ROLLBACK statements

PCB-00305: Oracle extension to the COMMIT and ROLLBACK statements

Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the parameter RELEASE, COMMENT, or FORCE were used in a COMMIT or ROLLBACK statement. For example, the offending code might look like: EXEC SQL ROLLBACK RELEASE END-EXEC. This informational message is issued by the FIPS Flagger when FIPS=YES.

Action: No action required. However, for ANSI or ISO compliance, do not use the nonconforming parameter.

PCB-00302: This statement is not supported by ANSI

PCB-00302: This statement is not supported by ANSI

Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, a nonconforming SQL statement such as PREPARE was used. For example, the offending code might look like: EXEC SQL PREPARE SQL-STMT FROM :HV END-EXEC. This informational message is issued by the FIPS Flagger when FIPS=YES.

Action: No action required. However, for ANSI or ISO compliance, do not use the nonconforming statement.

PCB-00301: Use of non-ANSI function is an Oracle extension

PCB-00301: Use of non-ANSI function is an Oracle extension

Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, a non-ANSI function was used. This informational message is issued by the FIPS Flagger when FIPS=YES.

Action: No action is required. However, for ANSI or ISO compliance, do not use this function.

PCB-00242: A host variable or exact numeric constant is required here

PCB-00242: A host variable or exact numeric constant is required here

Cause: The particular item in the dynamic SQL statement is required to be a host variable or exact numeric (integer) constant, but is not.

Action: Change the item in the dynamic SQL statement to use a host variable or exact numeric constant. 300 - 399: FIPS flagging error messages.

PCB-00241: A host variable is required here

PCB-00241: A host variable is required here

Cause: The COUNT item in the dynamic SQL statement must be a host variable but is not.

Action: Use a host variable in the COUNT item of the dynamic SQL statement.

NZE-29241: a buffer block needs to more space but its length is fixed

NZE-29241: a buffer block needs to more space but its length is fixed

Cause: The application has preallocated an output buffer that is too short for the operation and has specified that the buffer should not grow as needed.

Action: Either preallocate a larger buffer or allow the toolkit to grow the output buffer as needed.

NZE-29240: the cryptographic engine does not recognize the algorithm

NZE-29240: the cryptographic engine does not recognize the algorithm

Cause: The application is probably passing the wrong parameters.

Action: Check the parameters being used with the cryptographic functions.

NZE-29239: the cryptographic engine could not initialize the algorithm

NZE-29239: the cryptographic engine could not initialize the algorithm

Cause: The cryptographic engine does not have enough information to correctly initialize the algorithm.

Action: Check the parameters being used with the cryptographic functions.

NZE-29238: the cryptographic engine could not apply the algorithm

NZE-29238: the cryptographic engine could not apply the algorithm

Cause: The cryptographic engine does not have enough information to correctly apply the algorithm.

Action: Check the parameters being used with the cryptographic functions.

NZE-29237: the cryptographic engine could not finish the algorithm

NZE-29237: the cryptographic engine could not finish the algorithm

Cause: The cryptographic engine does not have enough information to correctly finish applying the algorithm.

Action: Check the parameters being used with the cryptographic functions.

NZE-29236: the random number generator will not accept seed

NZE-29236: the random number generator will not accept seed

Cause: The cryptographic engine may have run out of memory.

Action: Make sure the executable has been linked with compatible library versions.

NZE-29235: the key information could not be retrieved

NZE-29235: the key information could not be retrieved

Cause: The key may be corrupted or may be an unsupported type.

Action: Check the parameters being used with the cryptographic functions.

NZE-29234: a key object was not extracted from encoding

NZE-29234: a key object was not extracted from encoding

Cause: The encoding may be corrupted or may not be a key object at all.

Action: Check the encoding and parameters passed to decoding routine.

NZE-29233: the key object could not be encoded

NZE-29233: the key object could not be encoded

Cause: The key object may be corrupted or may be an unsupported type.

Action: Check the key object being passed to the encoding routine.

NZE-29232: the cryptographic engine key initialization failed

NZE-29232: the cryptographic engine key initialization failed

Cause: During initialization of a key for cryptography, some failure occured. This includes running out of memory and passing illegal arguments.

Action: Make sure the executable has been linked with compatible library versions, and that the correct parameters are being used for the cryptographic functions.

NZE-29231: the cryptographic engine failed to initialize

NZE-29231: the cryptographic engine failed to initialize

Cause: During initialization of the cryptographic engine, some failure occured. This includes running out of memory and trying to seed the random number generator.

Action: Make sure the executable has been linked with compatible library versions, and that you are not running out of swap space.

NZE-29230: the header length is not sufficient for message header

NZE-29230: the header length is not sufficient for message header

Cause: The input TDU has either been corrupted or it is not being used correctly.

Action: Check that the TDU is being used from the beginning. If possible, compare the size of the TDU upon generation to the size trying to be used.

NZE-29229: the magic number found in the header does not match expected

NZE-29229: the magic number found in the header does not match expected

Cause: The input TDU has either been corrupted or it is not being used correctly.

Action: Check that the TDU is being used from the beginning. If possible, compare the size of the TDU upon generation to the size trying to be used.