Answer / guest

Cause: ALTER DATABASE NO FORCE LOGGING command failed
because the database is not in force logging mode.

Action: none

Please add more information about this Error

LSX-00293: missing one or more fields from element "~S"

1 Answers  

---

ORA-00227: corrupt block detected in controlfile: (block string, # blocks string)

1 Answers  

---

ORA-01862: the numeric value does not match the length of the format item

1 Answers  

---

ORA-04935: unable to get/convert SCN recovery lock

1 Answers  

---

TNS-12163: TNS:connect descriptor is too long

1 Answers  

---

ORA-38431: could not evaluate subexpression "string" for rowid "string"

1 Answers  

---

TNS-03603: Encountered a node with a version eariler than SQL*Net 2.3

1 Answers  

---

ORA-13263: column string in table string is not of type SDO_GEOMETRY

1 Answers  

---

ORA-33048: (XSAGDNGL23) In AGGMAP workspace object, the relation workspace object and the relation workspace object are both over the same base dimension.

1 Answers  

---

ORA-10659: Segment being shrunk is not a lob

1 Answers  

---

ORA-01100: database already mounted

3 Answers   Oracle, Wipro,

---

ORA-12561: TNS:unknown error

1 Answers  

---