Answer / guest

Cause: In a CREATE CONTROLFILE command either this file or
all previous files were backups from before the last
RESETLOGS. This may also occur if this is a file that is
offline and has been offline since before the last RESETLOGS.

Action: If the file was taken offline normal before the last
RESETLOGS, and is still offline, omit it from the CREATE
CONTROLFILE command. Rename and online the file after the
database is open. Otherwise find the version of the
mentioned file consistent with the rest of the datafiles and
resubmit the command.

Please add more information about this Error

TNS-01306: nt secondary err code: number

1 Answers  

---

RMAN-08122: keep attributes for the backup are changed

1 Answers  

---

ORA-21522: attempted to use an invalid connection in OCI (object mode only)

1 Answers  

---

ORA-32145: Environment not specified

1 Answers  

---

ORA-30383: specified dimension level does not exist in the attribute

1 Answers  

---

---

ORA-24772: Cannot mix tightly-coupled and loosely-coupled branches

1 Answers  

---

RMAN-06458: AS COPY option cannot be used with RECOVERY FILES, RECOVERY AREA or DB_RECOVERY_FILE_DEST

1 Answers  

---

ORA-24351: invalid date passed into OCI call

1 Answers  

---

TNS-01417: "string" established:string refused:string state:string

1 Answers  

---

ORA-29345: can not plug a tablespace into a database using a different character set

1 Answers  

---

LPX-00107: element "~S" has multiple declarations

1 Answers  

---

ORA-14324: values being added already exist in DEFAULT partition

1 Answers  

---