Answer / guest

Cause: the server was unable to write the named checkpoint
file. This problem is typically due to the file system's
protection settings. The error is not fatal; it simply means
the server will not create any checkpoint data. Note,
however, that if the configuration database is ever
unavailable during a future server startup, the lack of
checkpoint data means you will be unable to force a startup
from checkpoint data with the names.no_region_database
parameter.

Action: Check to see that the server has permission to write
the file named in the error message.

Please add more information about this Error

RMAN-06742: platform name 'string' longer than number

1 Answers  

---

ORA-08315: sllfrb: Error reading file

1 Answers  

---

TNS-00256: Status of Navigator:

1 Answers  

---

ORA-12582: TNS:invalid operation

1 Answers  

---

ORA-00405: compatibility type "string"

1 Answers  

---

DRG-10831: can not insert into feedback table string

1 Answers  

---

NNO-00050: serious errors in configuration data, server cannot run

1 Answers  

---

DRG-10822: duplicate query name

1 Answers  

---

TNS-00541: underlying transport does not exist.

1 Answers  

---

QSM-01013: nested aggregates or CONNECT BY/START WITH clause present

1 Answers  

---

ORA-02073: sequence numbers not supported in remote updates

1 Answers  

---

NNL-00915: Authority required on server queries: string

1 Answers  

---