NNL-01060: Cache next checkpointed in: string
Cause: Control program statistic description
Action: None.
Cause: Control program statistic description
Action: None.
NNL-01059: Region data reload check failures: number
NNL-01059: Region data reload check failures: number
Cause: Control program statistic description
Action: None.
Cause: Control program statistic description
Action: None.
NNL-01058: Region data next checked for reload in: string
NNL-01058: Region data next checked for reload in: string
Cause: Control program statistic description
Action: None.
Cause: Control program statistic description
Action: None.
NNL-01057: Foreign data items cached: number
NNL-01057: Foreign data items cached: number
Cause: Control program statistic description
Action: None.
Cause: Control program statistic description
Action: None.
NNL-01056: Requests forwarded: number
NNL-01056: Requests forwarded: number
Cause: Control program statistic description
Action: None.
Cause: Control program statistic description
Action: None.
NNL-01055: Requests received: number
NNL-01055: Requests received: number
Cause: Control program statistic description
Action: None.
Cause: Control program statistic description
Action: None.
NNL-01054: Request forwarding enabled: string
NNL-01054: Request forwarding enabled: string
Cause: Control program statistic description
Action: None.
Cause: Control program statistic description
Action: None.
NNL-01053: Request processing enabled: string
NNL-01053: Request processing enabled: string
Cause: Control program statistic description
Action: None.
Cause: Control program statistic description
Action: None.
PCB-00554: Must include SQLCA when mode=ANSI and WHENEVER SQLWARNING used
PCB-00554: Must include SQLCA when mode=ANSI and WHENEVER SQLWARNING used
Cause: When MODE={ANSI | ANSI14}, an attempt was made to use the WHENEVER SQLWARNING statement without declaring the SQLCA. When MODE={ANSI | ANSI14}, declaring the SQLCA is optional, but to use the WHENEVER SQLWARNING statement, the SQLCA must be declared.
Action: Remove all WHENEVER SQLWARNING statements from the program or declare the SQLCA by hardcoding it or copying it into the program with the INCLUDE statement.
Cause: When MODE={ANSI | ANSI14}, an attempt was made to use the WHENEVER SQLWARNING statement without declaring the SQLCA. When MODE={ANSI | ANSI14}, declaring the SQLCA is optional, but to use the WHENEVER SQLWARNING statement, the SQLCA must be declared.
Action: Remove all WHENEVER SQLWARNING statements from the program or declare the SQLCA by hardcoding it or copying it into the program with the INCLUDE statement.
PCB-00553: FOR clause not allowed on this statement
PCB-00553: FOR clause not allowed on this statement
Cause: A FOR clause was used with a SELECT, LOB, or DEALLOCATE DESCRIPTOR statement. A FOR clause cannot be used with these statements. In the case of a SELECT statement, data returned from the last loop in the execution of the SELECT would overwrite data returned in a previous loop.
Action: Remove the FOR clause from the statement. Use a host language construct to iteratively execute the statement.
Cause: A FOR clause was used with a SELECT, LOB, or DEALLOCATE DESCRIPTOR statement. A FOR clause cannot be used with these statements. In the case of a SELECT statement, data returned from the last loop in the execution of the SELECT would overwrite data returned in a previous loop.
Action: Remove the FOR clause from the statement. Use a host language construct to iteratively execute the statement.
PCB-00552: The SQLCA and a SQLCODE variable cannot both be used
PCB-00552: The SQLCA and a SQLCODE variable cannot both be used
Cause: The SQLCA has been included and a SQLCODE variable has been declared. This is not allowed as references to the SQLCODE variable are ambiguous and will result in COBOL compiler errors.
Action: Use either the SQLCA or the SQLCODE variable. Remove either the include of the SQLCA or the SQLCODE variable declaration.
Cause: The SQLCA has been included and a SQLCODE variable has been declared. This is not allowed as references to the SQLCODE variable are ambiguous and will result in COBOL compiler errors.
Action: Use either the SQLCA or the SQLCODE variable. Remove either the include of the SQLCA or the SQLCODE variable declaration.
PCB-00551: The SQLCA has already been included
PCB-00551: The SQLCA has already been included
Cause: The precompiler has encountered an include SQLCA statement after SQLCA has already been included. The SQLCA can only be included once.
Action: Remove the duplicate include SQLCA statement.
Cause: The precompiler has encountered an include SQLCA statement after SQLCA has already been included. The SQLCA can only be included once.
Action: Remove the duplicate include SQLCA statement.
PCB-00550: Unable to log on to ORACLE with string . ORACLE error number: number
PCB-00550: Unable to log on to ORACLE with string . ORACLE error number: number
Cause: The precompiler was unable to log on to ORACLE with the specified username and password. An ORACLE error with given number occurred when the logon was attempted.
Action: .
Cause: The precompiler was unable to log on to ORACLE with the specified username and password. An ORACLE error with given number occurred when the logon was attempted.
Action: .
PCB-00525: Use of the AT clause is not permitted here
PCB-00525: Use of the AT clause is not permitted here
Cause: An explicit AT clause was used with an ALLOCATE statement or a FETCH or CLOSE statement also using a sql-cursor declaration.
Action: Remove the AT clause. 550 - 574, Miscellaneous
Cause: An explicit AT clause was used with an ALLOCATE statement or a FETCH or CLOSE statement also using a sql-cursor declaration.
Action: Remove the AT clause. 550 - 574, Miscellaneous
PCB-00502: This statement can only be used with THREADS=YES
PCB-00502: This statement can only be used with THREADS=YES
Cause: EXEC SQL ENABLE THREADS has been used, even though option THREADS is set to NO.
Action: Specify option THREADS=YES or remove the EXEC ENABLE THREADS statement from the source code. 525 - 549, Result Set Cursors
Cause: EXEC SQL ENABLE THREADS has been used, even though option THREADS is set to NO.
Action: Specify option THREADS=YES or remove the EXEC ENABLE THREADS statement from the source code. 525 - 549, Result Set Cursors
PCB-00501: Runtime context variable string not of correct type
PCB-00501: Runtime context variable string not of correct type
Cause: The runtime context variable referenced in an EXEC SQL CONTEXT USE statement is not of type sql_context.
Action: Declare your runtime context variable of type sql_context.
Cause: The runtime context variable referenced in an EXEC SQL CONTEXT USE statement is not of type sql_context.
Action: Declare your runtime context variable of type sql_context.
PCB-00500: No EXEC SQL CONTEXT USE statement encountered
PCB-00500: No EXEC SQL CONTEXT USE statement encountered
Cause: No EXEC SQL CONTEXT USE statement was encountered and the option threads=yes was requested.
Action: Ensure that the necessary context variable (of type sql-context) has been declared, ALLOCATEd, and USEd prior to any executable SQL statements.
Cause: No EXEC SQL CONTEXT USE statement was encountered and the option threads=yes was requested.
Action: Ensure that the necessary context variable (of type sql-context) has been declared, ALLOCATEd, and USEd prior to any executable SQL statements.
PCB-00404: %s
PCB-00404: %s
Cause: A syntax error was found.
Action: Do the appropriate action to fix the indicated error. 500 - 524, Threads
Cause: A syntax error was found.
Action: Do the appropriate action to fix the indicated error. 500 - 524, Threads
PCB-00403: EXEC statement cannot begin in Area A
PCB-00403: EXEC statement cannot begin in Area A
Cause: An EXEC statement began in Area A (before column 12).
Action: Shift the EXEC statement to the right to start it in Area B (in or after column 12).
Cause: An EXEC statement began in Area A (before column 12).
Action: Shift the EXEC statement to the right to start it in Area B (in or after column 12).
PCB-00402: Pseudo-text not properly terminated
PCB-00402: Pseudo-text not properly terminated
Cause: A block of pseudo-text has not been properly terminated with == .
Action: Terminate the pseudo-text at the appropriate place with == . 500 - 649, Other semantic errors grouped by these features: threads, result set cursors, miscellaneous, pl or sql (includes arraylen), exec tools and lobs.
Cause: A block of pseudo-text has not been properly terminated with == .
Action: Terminate the pseudo-text at the appropriate place with == . 500 - 649, Other semantic errors grouped by these features: threads, result set cursors, miscellaneous, pl or sql (includes arraylen), exec tools and lobs.
PCB-00401: Character string not properly terminated
PCB-00401: Character string not properly terminated
Cause: The character string was not terminated with a quote or apostrophe as appropriate or line continuation was not correct.
Action: Check that the character string is terminated properly and that line continuation syntax is correct.
Cause: The character string was not terminated with a quote or apostrophe as appropriate or line continuation was not correct.
Action: Check that the character string is terminated properly and that line continuation syntax is correct.
PCB-00400: %s
PCB-00400: %s
Cause: A syntax error was found.
Action: Do the appropriate action to fix the indicated error.
Cause: A syntax error was found.
Action: Do the appropriate action to fix the indicated error.
PCB-00322: EXEC SQL LOB statements an Oracle extension
PCB-00322: EXEC SQL LOB statements an Oracle extension
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, an EXEC SQL LOB 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 this statement. 400 - 499, Tokenizer or parsing errors.
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, an EXEC SQL LOB 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 this statement. 400 - 499, Tokenizer or parsing errors.
PCB-00321: Implicit varchar host variables are an Oracle extension
PCB-00321: Implicit varchar host variables are an Oracle extension
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, an iimplicit varchar variable was used in a SQL statement. 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 statement.
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, an iimplicit varchar variable was used in a SQL statement. 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 statement.
PCB-00320: VARYING host variable string is an Oracle extension
PCB-00320: VARYING host variable string is an Oracle extension
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, a variable declared of VARYING type was used in a SQL statement. 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 statement.
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, a variable declared of VARYING type was used in a SQL statement. 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 statement.
PCB-00319: EXEC ORACLE statements are an Oracle extension
PCB-00319: EXEC ORACLE statements are an Oracle extension
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, an EXEC ORACLE 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 this statement.
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, an EXEC ORACLE 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 this statement.
PCB-00318: ARRAYLEN is an Oracle extension
PCB-00318: ARRAYLEN is an Oracle extension
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the ARRAYLEN 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 this statement.
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the ARRAYLEN 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 this statement.
PCB-00317: Group item host variables are Oracle extensions
PCB-00317: Group item host variables are Oracle extensions
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, a group item variable was used as a host variable. 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 group items as host variables.
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, a group item variable was used as a host variable. 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 group items as host variables.
PCB-00316: SQL FORMS statements are Oracle extensions
PCB-00316: SQL FORMS statements are Oracle extensions
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the one of the following statements was used: o EXEC IAF GET o EXEC IAF PUT o EXEC TOOLS GET o EXEC TOOLS SET 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.
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the one of the following statements was used: o EXEC IAF GET o EXEC IAF PUT o EXEC TOOLS GET o EXEC TOOLS SET 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-00315: DECLARE TABLE is an Oracle extension
PCB-00315: DECLARE TABLE is an Oracle extension
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the DECLARE TABLE statement was used.
Action: No action required. However, for ANSI or ISO compliance, do not use this statement.
Cause: An Oracle extension to the ANSI or ISO SQL standard was used. Specifically, the DECLARE TABLE statement was used.
Action: No action required. However, for ANSI or ISO compliance, do not use this statement.
O2F-00322: Unable to close the OUTTYPE file
O2F-00322: Unable to close the OUTTYPE file
Cause: An operating system error occurred while attempting to close the OUTTYPE file.
Action: Try opening the OUTTYPE file with an editor to make sure you are able to access the file.
Cause: An operating system error occurred while attempting to close the OUTTYPE file.
Action: Try opening the OUTTYPE file with an editor to make sure you are able to access the file.
O2F-00321: Error opening the OUTTYPE file for writing
O2F-00321: Error opening the OUTTYPE file for writing
Cause: An operating system error occurred while attempting to open the OUTTYPE file.
Action: Make sure you spelled the filename of the OUTTYPE file correctly. Make sure you have operating system permission to open the the file.
Cause: An operating system error occurred while attempting to open the OUTTYPE file.
Action: Make sure you spelled the filename of the OUTTYPE file correctly. Make sure you have operating system permission to open the the file.
O2F-00320: Invalid filename for the OUTTYPE file
O2F-00320: Invalid filename for the OUTTYPE file
Cause: The filename specified for the OUTTYPE file is not syntactically correct.
Action: Make sure you spelled the filename of the OUTTYPE file correctly.
Cause: The filename specified for the OUTTYPE file is not syntactically correct.
Action: Make sure you spelled the filename of the OUTTYPE file correctly.
O2F-00319: No OUTTYPE file specified
O2F-00319: No OUTTYPE file specified
Cause: The required option OUTTYPE was not specified.
Action: Set the OUTTYPE option to the name of the file to which the TYPE file produced by OTT should be written. The OUTTYPE option may be specified on the command line or in a CONFIG file.
Cause: The required option OUTTYPE was not specified.
Action: Set the OUTTYPE option to the name of the file to which the TYPE file produced by OTT should be written. The OUTTYPE option may be specified on the command line or in a CONFIG file.
O2F-00318: Error writing to the OUTTYPE file
O2F-00318: Error writing to the OUTTYPE file
Cause: An operating system error occurred when attempting to write to the OUTTYPE file.
Action: Make sure you have operating system permission to write to the file. Also, make sure disk space is available.
Cause: An operating system error occurred when attempting to write to the OUTTYPE file.
Action: Make sure you have operating system permission to write to the file. Also, make sure disk space is available.
O2F-00317: Error opening the ERRTYPE file for writing
O2F-00317: Error opening the ERRTYPE file for writing
Cause: An operating system error occurred while attempting to open the ERRTYPE file for writing.
Action: Make sure you spelled the ERRTYPE filename correctly. Try creating or modifying the ERRTYPE file to make sure you have write access to the file.
Cause: An operating system error occurred while attempting to open the ERRTYPE file for writing.
Action: Make sure you spelled the ERRTYPE filename correctly. Try creating or modifying the ERRTYPE file to make sure you have write access to the file.
O2F-00316: An unexpected token was seen at the end of a type specification
O2F-00316: An unexpected token was seen at the end of a type specification
Cause: There is a syntax error in the INTYPE file.
Action: Check your documentation to make sure the type specifications
Cause: There is a syntax error in the INTYPE file.
Action: Check your documentation to make sure the type specifications
O2F-00315: An attribute of a type is listed twice in a type specification
O2F-00315: An attribute of a type is listed twice in a type specification
Cause: An attribute of a user-defined type is listed twice in a type specification in the INTYPE file. The second occurrence is ignored.
Action: Remove one of the two occurrences of the attribute.
Cause: An attribute of a user-defined type is listed twice in a type specification in the INTYPE file. The second occurrence is ignored.
Action: Remove one of the two occurrences of the attribute.
O2F-00314: AS expected but not seen in the INTYPE file
O2F-00314: AS expected but not seen in the INTYPE file
Cause: Incorrect syntax in the INTYPE file.
Action: Make sure your TYPE file syntax is correct.
Cause: Incorrect syntax in the INTYPE file.
Action: Make sure your TYPE file syntax is correct.
O2F-00313: Illegal or missing attribute name
O2F-00313: Illegal or missing attribute name
Cause: An attribute name was expected in the INTYPE file, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct attribute name.
Cause: An attribute name was expected in the INTYPE file, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct attribute name.
O2F-00312: Illegal or missing type version string
O2F-00312: Illegal or missing type version string
Cause: A type version name was expected, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct version name.
Cause: A type version name was expected, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct version name.
O2F-00311: Illegal or missing file name
O2F-00311: Illegal or missing file name
Cause: A legal file name was expected, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct file name.
Cause: A legal file name was expected, but was not seen.
Action: Make sure your TYPE file syntax is correct. Use a correct file name.
O2F-00310: Illegal or missing identifier name
O2F-00310: Illegal or missing identifier name
Cause: A legal C or C++ identifier was expected following AS, but was not seen.
Action: Use a legal C or C++ identifier, consisting of letters, digits, and underscores not beginning with a digit.
Cause: A legal C or C++ identifier was expected following AS, but was not seen.
Action: Use a legal C or C++ identifier, consisting of letters, digits, and underscores not beginning with a digit.
O2F-00309: Name of user-defined type is illegal or missing
O2F-00309: Name of user-defined type is illegal or missing
Cause: The name of a user-defined type is expected following the keyword TYPE at the beginning of a type specification. No legal type name was seen.
Action: Make sure that the type specification is syntactically correct, and that the type name is spelled correctly.
Cause: The name of a user-defined type is expected following the keyword TYPE at the beginning of a type specification. No legal type name was seen.
Action: Make sure that the type specification is syntactically correct, and that the type name is spelled correctly.
O2F-00308: No type specifications were seen in the INTYPE file
O2F-00308: No type specifications were seen in the INTYPE file
Cause: Either there are no type specifications in the INTYPE file, or the first type specification could not be read due to a previously reported error.
Action: Fix any previously reported errors. Make sure there are one or more type specifications in the INTYPE file.
Cause: Either there are no type specifications in the INTYPE file, or the first type specification could not be read due to a previously reported error.
Action: Fix any previously reported errors. Make sure there are one or more type specifications in the INTYPE file.
O2F-00307: Unable to read the INTYPE file
O2F-00307: Unable to read the INTYPE file
Cause: The first token of the INTYPE file was not read. Either an operating system error occurred while attempting to read from the INTYPE file, or all lines of the INTYPE file are blank lines or comment lines.
Action: Try opening the INTYPE file with an editor to make sure you are able to access the file. Make sure the INTYPE file contains one or more type specifications.
Cause: The first token of the INTYPE file was not read. Either an operating system error occurred while attempting to read from the INTYPE file, or all lines of the INTYPE file are blank lines or comment lines.
Action: Try opening the INTYPE file with an editor to make sure you are able to access the file. Make sure the INTYPE file contains one or more type specifications.
O2F-00306: Unable to close the INTYPE file
O2F-00306: Unable to close the INTYPE file
Cause: An operating system error occurred while attempting to close the INTYPE file.
Action: Try opening the INTYPE file with an editor to make sure you are able to access the file.
Cause: An operating system error occurred while attempting to close the INTYPE file.
Action: Try opening the INTYPE file with an editor to make sure you are able to access the file.
O2F-00305: Error opening the INTYPE file for reading
O2F-00305: Error opening the INTYPE file for reading
Cause: An operating system error occurred while attempting to open the INTYPE file.
Action: Make sure you spelled the filename of the INTYPE file correctly. Try opening the INTYPE file with an editor to make sure you have access to the file.
Cause: An operating system error occurred while attempting to open the INTYPE file.
Action: Make sure you spelled the filename of the INTYPE file correctly. Try opening the INTYPE file with an editor to make sure you have access to the file.
O2F-00304: Invalid filename for the INTYPE file
O2F-00304: Invalid filename for the INTYPE file
Cause: The filename specified for the INTYPE file is not syntactically correct.
Action: Make sure you spelled the filename of the INTYPE file correctly.
Cause: The filename specified for the INTYPE file is not syntactically correct.
Action: Make sure you spelled the filename of the INTYPE file correctly.
O2F-00303: No INTYPE file was specified
O2F-00303: No INTYPE file was specified
Cause: The required option INTYPE was not specified.
Action: Set the INTYPE option to the name of the file containing names of types for OTT to translate. The INTYPE option may be specified on the command line or in a CONFIG file.
Cause: The required option INTYPE was not specified.
Action: Set the INTYPE option to the name of the file containing names of types for OTT to translate. The INTYPE option may be specified on the command line or in a CONFIG file.
O2F-00302: Unable to allocate memory
O2F-00302: Unable to allocate memory
Cause: OTT was unable to allocate memory.
Action: Contact ORACLE customer support.
Cause: OTT was unable to allocate memory.
Action: Contact ORACLE customer support.
O2F-00301: Error attempting to read from the INTYPE file
O2F-00301: Error attempting to read from the INTYPE file
Cause: An operating system error occurred while attempting to read from the INTYPE file.
Action: Try opening the INTYPE file with an editor to make sure you are able to access the file.
Cause: An operating system error occurred while attempting to read from the INTYPE file.
Action: Try opening the INTYPE file with an editor to make sure you are able to access the file.
NZE-29249: an unrecognized state was passed to a cryptographic function
NZE-29249: an unrecognized state was passed to a cryptographic function
Cause: The application is probably passing the wrong parameters.
Action: Check the parameters being used with the toolkit functions.
Cause: The application is probably passing the wrong parameters.
Action: Check the parameters being used with the toolkit functions.
NZE-29248: an unrecognized WRL was used to open a wallet
NZE-29248: an unrecognized WRL was used to open a wallet
Cause: WRL s have a specific set of types and must be formatted correctly.
Action: Check the parameters being used with the toolkit functions.
Cause: WRL s have a specific set of types and must be formatted correctly.
Action: Check the parameters being used with the toolkit functions.
NZE-29247: an unopen toolkit object was used before it was opened
NZE-29247: an unopen toolkit object was used before it was opened
Cause: Some toolkit objects must be opened before they can be used.
Action: Check the parameters being used with the toolkit functions.
Cause: Some toolkit objects must be opened before they can be used.
Action: Check the parameters being used with the toolkit functions.
NZE-29246: the toolkit could not parse the tdu
NZE-29246: the toolkit could not parse the tdu
Cause: The TDU could be corrupted.
Action: Check the parameters being used with the toolkit functions.
Cause: The TDU could be corrupted.
Action: Check the parameters being used with the toolkit functions.
NZE-29245: the toolkit does not recognize the function being used
NZE-29245: the toolkit does not recognize the function being used
Cause: The application is probably passing the wrong parameters.
Action: Check the parameters being used with the toolkit functions.
Cause: The application is probably passing the wrong parameters.
Action: Check the parameters being used with the toolkit functions.
NZE-29243: the toolkit does not recognize the type of key being used
NZE-29243: the toolkit does not recognize the type of key being used
Cause: The application is probably passing the wrong parameters.
Action: Check the parameters being used with the toolkit functions.
Cause: The application is probably passing the wrong parameters.
Action: Check the parameters being used with the toolkit functions.
NZE-29242: the asymmetric key is too short to be used with the data.
NZE-29242: the asymmetric key is too short to be used with the data.
Cause: An asymmetric key must be at least 11 bytes longer than the data it is being used to encrypt.
Action: Use an asymmetric key with more bits or break the data into smaller pieces.
Cause: An asymmetric key must be at least 11 bytes longer than the data it is being used to encrypt.
Action: Use an asymmetric key with more bits or break the data into smaller pieces.
NZE-28807: Cannot update the data source.
NZE-28807: Cannot update the data source.
Cause: The system or application failed to update the data source (file or database).
Action: Enable Oracle Net tracing to determine the exact error.
Cause: The system or application failed to update the data source (file or database).
Action: Enable Oracle Net tracing to determine the exact error.
Subscribe to:
Posts (Atom)