|
1 <?xml version="1.0" encoding="utf-8"?> |
|
2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. --> |
|
3 <!-- This component and the accompanying materials are made available under the terms of the License |
|
4 "Eclipse Public License v1.0" which accompanies this distribution, |
|
5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". --> |
|
6 <!-- Initial Contributors: |
|
7 Nokia Corporation - initial contribution. |
|
8 Contributors: |
|
9 --> |
|
10 <!DOCTYPE concept |
|
11 PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd"> |
|
12 <concept id="GUID-24A149FA-B82A-53A2-83E6-4F625D7041D7" xml:lang="en"><title>Error |
|
13 codes</title><shortdesc>The errors returned by DBMS functions are mostly documented with |
|
14 those functions, but this document summarises some of the more common/general |
|
15 errors.</shortdesc><prolog><metadata><keywords/></metadata></prolog><conbody> |
|
16 <p>The Store database makes full use of file store functionality, and any |
|
17 errors produced by <codeph>CPermanentFileStore</codeph>, its stream objects |
|
18 and particularly the underlying file system may be returned by a DBMS function |
|
19 where indicated. Also many of the functions require memory to be dynamically |
|
20 allocated, and so can fail with <codeph>KErrNoMemory</codeph>.</p> |
|
21 <p>The errors returned by DBMS functions are mostly documented with those |
|
22 functions. There are a few general errors which can be returned by most of |
|
23 the API to indicate certain states that the database or rowsets have encountered.</p> |
|
24 <ul> |
|
25 <li id="GUID-27B4049F-3F3D-5B86-89B7-33BE8FEDA6C0"><p><codeph>KErrAccessDenied</codeph> - |
|
26 The database cannot mix data definition and data manipulation, or combine |
|
27 them in a single transaction. i.e.</p> <ul> |
|
28 <li id="GUID-838469A1-5415-53C4-A4ED-03D538AEFC54"><p>A rowset or data manipulation |
|
29 transaction is open on the database when attempting data definition or recovery.</p> </li> |
|
30 <li id="GUID-B29C8C26-298D-50F4-BAA5-425B46B85A89"><p> A data definition transaction |
|
31 is still open when attempting to create a rowset. </p> </li> |
|
32 <li id="GUID-91184D4A-1BCD-531F-914C-5756C4F08A2D"><p>Any incremental operation |
|
33 is open on the database.</p> </li> |
|
34 </ul> <p><codeph>KErrDied</codeph> - A transaction has been aborted, because |
|
35 an update or commit failed. In this state, the database and all associated |
|
36 rowsets become unusable. In this situation, all rowsets which are currently |
|
37 updating or inserting a row must be cancelled, and, if the transaction was |
|
38 begun explicitly, it must be rolled back. The database is now ready for use |
|
39 again.</p> </li> |
|
40 <li id="GUID-DFD729AD-B8EC-5A4A-962D-DBCC87C4C261"><p><codeph>KErrNotReady</codeph> - |
|
41 This is returned by all rowsets following a rollback on the database. The |
|
42 rowset is invalid and must at least be reset and re-evaluated if necessary, |
|
43 but can be closed and re-opened if preferred.</p> </li> |
|
44 <li id="GUID-EE40A750-1B31-5F2B-A33E-341F1DD9F2A8"><p><codeph>KErrCorrupt</codeph> - |
|
45 This is returned when an attempt is made to use an index which has been damaged |
|
46 due to a rollback. Rowsets which were using such an index fail on the first |
|
47 attempt to navigate their cursor. The database continues to be operational, |
|
48 but must be recovered to regain use of damaged indexes.</p> <p>This can also |
|
49 be returned in the unlikely event that corruption is detected in any of the |
|
50 streams which make up the database. Such damage cannot have been caused by |
|
51 DBMS itself, and cannot be repaired.</p> </li> |
|
52 </ul> |
|
53 </conbody></concept> |