Answer / guest

Cause: There is an overlap of file numbers in the files
specified on the command line or the same file is specified
twice. If they are not the exact same file then one is
likely to be a backup of the other. If they are two members
of the same log they must be specified together in a group
file spec. This message will also appear if the same
controlfile appears more than once in the control_files p
parameter in the init.ora file. If this happens, check for
additional error messages.

Action: Confirm that the file mentioned is not a repeat of a
file already mentioned in the command. If they are different
files then omit the earlier backup. If they are members of
the same log, insure they are in the same group file
specification. If this message appears because of a
duplicate controlfile, check the control_files parameter in
the init.ora file and see if a file is specified more than
once. If all files names appear to be unique, check to make
sure that the actual controlfiles themselves are unique. For
example, in UNIX check for a symbolic or a hard link to
another controlfile in the list.

Please add more information about this Error

LSX-00244: invalid NCName "~S"

1 Answers  

---

PROT-00017: Fatal Error

1 Answers  

---

LPX-00007: unexpected end-of-file encountered

1 Answers  

---

LSX-00164: no content specified in "~S"

1 Answers  

---

NZE-29164: External PKCS #12 wallet is not supported in FIPS mode.

1 Answers  

---

PLS-00371: at most one declaration for 'string' is permitted in the declaration section

4 Answers  

---

ORA-24306: bad buffer for piece

1 Answers  

---

ORA-27471: window "string.string" is already closed

1 Answers  

---

NID-00373: Revert changes for database string (Y/[N]) =>

1 Answers  

---

TNS-01004: reload [<listener_name>] : reload the parameter files and SIDs

1 Answers  

---

ORA-13837: invalid HASH_VALUE

1 Answers  

---

ORA-25190: an index-organized table maintenance operation may not be combined with other operations

1 Answers  

---