TNS-00002: INTCTL: error while starting the Interchange

TNS-00002: INTCTL: error while starting the Interchange

Cause: of the problem. Be sure to turn tracing off when the problem has been rectified.

Action: Check the Interchange configuration files (INTCHG.ORA, TNSNET.ORA and TNSNAV.ORA) for errors and confirm that no other programs are using the ADDRESS(es) specified. If error continues, turn on tracing in the Interchange components and examine the trace files to determine the

TNS-00001: INTCTL: error while getting command line from the terminal

TNS-00001: INTCTL: error while getting command line from the terminal

Cause: Improper standard input connection from the terminal.

Action: Normally not visible to the user. Start the INTCTL program again. If error persists, contact Oracle Customer Support.

TNS-00000: Not An Error

TNS-00000: Not An Error

Cause: Everything is working as it should.

Action: Don t worry: Be happy.

PROT-00807: Please ensure you have file creation privileges in the above directory before running this tool.

PROT-00807: Please ensure you have file creation privileges in the above directory before running this tool.

Cause: ocrcheck called with incorrect or missing options

Action: Use ocrcheck with correct options

PROT-00715: Device or File integrity check failed n

PROT-00715: Device or File integrity check failed n

Cause: ocrcheck called

Action: None

PROT-00602: Failed to retrieve data from the cluster registry

PROT-00602: Failed to retrieve data from the cluster registry

Cause: Unable to retrieve necessary information from the cluster registry

Action: Check the availability of the cluster registry and the details of the failure from the log file

PROT-00601: Failed to initialize ocrcheck

PROT-00601: Failed to initialize ocrcheck

Cause: Unable to initialize and start ocrcheck

Action: Check log file for details about the failure

PROT-00415: Make sure you have file creation privileges in the above directory before running this tool.

PROT-00415: Make sure you have file creation privileges in the above directory before running this tool.

Cause: ocrdump called with incorrect or missing options

Action: Use ocrdump with correct options

PROT-00307: The specified key does not exist in cluster registry

PROT-00307: The specified key does not exist in cluster registry

Cause: Unable to retrieve the specified key from cluster registry

Action: Check log file for the key name

PROT-00306: Failed to retrieve cluster registry data

PROT-00306: Failed to retrieve cluster registry data

Cause: Unable to read cluster registry data

Action: Check log file for details about the failure

PROT-00305: Failed to write to dump file (string(

PROT-00305: Failed to write to dump file (string(

Cause: Unable to write to dump file while dumping cluster registry data

Action: Check access privilege or disk space of the requested path

PLW-06002: Unreachable code

PLW-06002: Unreachable code

Cause: Static program analysis determined that some code on the specified line would never be reached during execution. This may come as a result of expression evaluation at compile time.

Action: Inspect program logic for possible defects. Disable the warning if much code is made unreachable intentionally and the warning message is more annoying than helpful.

PLW-05006: shadow type generation resulted in warning: string

PLW-05006: shadow type generation resulted in warning: string

Cause: Compilation of a table function causes the creation of internally- generated types. A problem occurred during creation of these types which was not severe enough to prevent the creation of the types, but which may impact the usage of the table function. See the accompanying error message for more information.

Action: Fix the issue reported in the accompanying error message.

PLW-05005: function string returns without value at line string

PLW-05005: function string returns without value at line string

Cause: The function exited without a return value. Return statements are required for all PL or SQL functions.

Action: Inspect the function source code for exit points, and place a return at each point so that no runtime error will be generated when the function exits. NLS_ DO_NOT_TRANSLATE (5400,5401(

PLW-05004: identifier string is also declared in STANDARD or is a SQL builtin

PLW-05004: identifier string is also declared in STANDARD or is a SQL builtin

Cause: The indicated identifier was also either: o) declared in package STANDARD, or o) a SQL builtin function, or o) a pseudo-column. This situation can result in name resolution issues since the STANDARD or builtin declaration will be chosen over the local declaration in SQL statements; however the local declaration will be chosen over the STANDARD or builtin declaration outside SQL scope. (See the documentation on PL or SQL name resolution.)

Action: Either: o) rename the given identifier, o) qualify any references to the identifier with the containing scope s name, or o) make sure the intended resolution occurs if using the identifier in SQL scope.

PLW-05003: same actual parameter(string and string) at IN and NOCOPY may have side effects

PLW-05003: same actual parameter(string and string) at IN and NOCOPY may have side effects

Cause: The indicated parameter was declared with the NOCOPY hint in the subprogram specification but not in the body, or it was declared with the NOCOPY hint in the body but not in the specification.

Action: Ensure that the specification and the body agree in their use of NOCOPY. If this mismatch is not corrected, the program will obey the declaration given in the specification, ignoring that in the body.

PLW-05001: previous use of string (at line string) conflicts with this use

PLW-05001: previous use of string (at line string) conflicts with this use

Cause: While looking for prior declarations of a variable, constant, or label, the compiler found another declaration with the same name in the same scope. Or, the headers of subprogram in a package specification and body were not identical.

Action: Check the spelling of the variable, constant, or label name. Also check the names of all parameters and exceptions declared in the same scope. Then, remove or rename the object with the duplicate name. Or, change the headers of the packaged subprogram in the package specification or body so that they are identical.

PLW-05000: mismatch in NOCOPY qualification between specification and body

PLW-05000: mismatch in NOCOPY qualification between specification and body

Cause: The indicated parameter was declared with the NOCOPY hint in the subprogram specification but not in the body, or it was declared with the NOCOPY hint in the body but not in the specification.

Action: Ensure that the specification and the body agree in their use of NOCOPY. If this mismatch is not corrected, the program will obey the declaration given in the specification, ignoring that in the body.

PLS-01913: : instance must of be of type string or one of its subtypes

PLS-01913: : instance must of be of type string or one of its subtypes

Cause: The run-time type of the instance is the not declared type or one of its subtypes. e.g. TREAT(supertype AS subtype) fails.

Action: Catch the exception.

PLS-01912: : instance must of be of type string

PLS-01912: : instance must of be of type string

Cause: The run-time type of the instance is not the declared type. e.g. If the return value of a user defined constructor is wrong.

Action: Return the correct type.