The following sections list the Oracle Database Mobile Server thrown exceptions and returned error messages:
Section 1.5, "CNS 9200–9299 Secure Socket Layer (SSL) Errors"
Section 1.6, "CNS 9300-9399 Automatic Synchronization Errors"
Section 1.10, "OMS 3100–3599 Errors from the oracle.lite.web.resource Package"
Section 1.13, "OMS 21000–21999 Errors reported by the Tools classes in oracle.lite.web.tools."
Each message code follows the format Product ID-nnnnn, where nnnnn is an integer. Messages specific to an operating system or another Oracle product are not listed here, although the message code may be listed with a reference to another Oracle document.
Each description contains the message number and text as well as the following:
Items in the error message text which appears in curly braces, for example, {publication name}, are replaced with values for objects which are then returned by the error message.
Sometimes you may encounter an error that is known as an abnormal condition. These are errors for which the exact cause is not clear. The following sections describe the probable causes of abnormal conditions and the actions you can take to solve them.
Abnormal conditions may arise from one of the following causes:
An invalid user action.
A bug in the component prevented the requested task from completing.
You should first contact your DBA and/or system administrator to determine if the message was caused by something other than Oracle Database Mobile Server. If you determine that the message was not the result of user error or a system problem, you should take the following steps:
Write down the message number and its text.
Write down the circumstances that led up to the message. Try to recall the actions you took, the objects involved (if any), and the exact sequence of keys that you pressed prior to the message.
Call Oracle Customer Support for assistance.
The Java Access Class errors are processed through the Java exception handling mechanism. Errors appear with names such as the following:
oracle.pol.jac.POLGroupNotFoundException
There are no error codes associated with these Java exceptions. If an internal error code causes a Java exception, the general oracle.pol.jac.POLException
appears and the internal error code that caused the exception is reported.
Some errors (such as internal errors) require you to call Oracle Customer Support to report the error. When you call Customer Support, you should have the following information available:
Your name, company, and Oracle Support ID number.
The hardware, operating system, and release number of the operating system on which Oracle Database Mobile Server is running.
The complete version number of Oracle Database Mobile Server that you were using when you encountered the error, including revision number and port release number, if any.
All other products and version numbers in use when the error occurred.
If you encountered one or more error codes or messages, the exact code numbers and message texts, in the order they appeared.
A description of the problem, including any unusual conditions.
The problem severity, according to the following codes:
1 = Program not usable. Critical impact on operations of a production system.
2 = Program not usable. Operations severely restricted.
3 = Program usable with limited functions. Not critical to overall operations.
4 = Problem circumvented by customer. Minimal effect, if any, on operations.
When using the Oracle Database Mobile Server APIs, you may receive an error message from an exception. This section describes all errors that can be thrown within the Oracle Database Mobile Server APIs.
Table 1-1 lists the error codes and messages that can be returned in the OSEException
class.
Table 1-1 OSEException Error Messages
Error number | Error Code | Error Message |
---|---|---|
-12000 |
|
Sync was canceled. |
-12001 |
|
Expecting opcode |
-12002 |
|
Could not find database |
-12003 |
|
User is not specified and the last user was not saved. |
-12004 |
|
Password is not specified and was not saved for user |
-12005 |
|
Received invalid record DML type |
-12006 |
|
Received invalid opcode |
-12008 |
|
|
-12011 |
|
Plugin has thrown an exception, see the cause. |
-12012 |
|
Invalid sync direction specified: |
-12016 |
|
Invalid transport type specified: |
-12017 |
|
Could not find plugin with id |
-12018 |
|
Got a record with BLOBs for a plugin that does not support BLOBs. |
-12019 |
|
Could not find publication |
-12021 |
|
Could not find snapshot with id |
-12023 |
|
Snapshot with id |
-12024 |
|
Opcode |
-12030 |
|
Sent encryption id |
-12031 |
|
Received erroneous unencrypted data. |
-12032 |
|
Received erroneous uncompressed data. |
-12034 |
|
Invalid encryption type specified: |
-12035 |
|
Unsuccessful HTTP response |
-12038 |
|
Server error, id = |
-12039 |
|
Internal error has occured (see the cause). |
-12040 |
|
Plugin is missing default database needed to create snapshot. |
-12043 |
|
Could not find publication with id |
-12044 |
|
Could not find plugin class |
-12047 |
|
Invalid priority specified: |
-12100 |
|
Failed to initialize plugin class |
-12101 |
|
Blank password is not allowed. |
-12102 |
|
Publication id |
-12103 |
|
Invalid string length |
-12104 |
|
Failed to get credentials from the server (the current credentials are invalid or missing). |
-12105 |
|
User name cannot be blank. |
Table 1-2 lists the error codes and messages that can be returned in the BGException
class.
Table 1-2 BGException Error Messages
Message Number | Message Constant | Message |
---|---|---|
12000 |
|
Info: Sync agent has been started |
12001 |
|
Info: Sync agent has been stopped |
12002 |
|
Info: Sync agent has been paused |
12003 |
|
Info: Sync agent has been resumed |
12004 |
|
Info: Compose of priority |
12005 |
|
Info: Compose of priority |
12006 |
|
Info: Sync of priority |
12007 |
|
Info: Sync of priority |
12008 |
|
Info: Apply has started for database |
12009 |
|
Info: Apply has finished for database |
12010 |
|
Info: Server notification of priority |
12011 |
|
Info: Network has changed from |
12012 |
|
Info: No network available. |
12013 |
|
Info: Evaluated network, name: |
12014 |
|
Info: Trace message: |
12015 |
|
Info: Unknown |
12200 |
|
Warning: Battery power is low ( |
12201 |
|
Warning: Memory is low ( |
-12500 |
|
Error: Compose of priority |
-12501 |
|
Error: Sync of priority |
-12502 |
|
Error: Apply has failed for database |
-12503 |
|
Error: Could not load automatic synchronization rule |
-12504 |
|
Error: Failed to evaluate automatic synchronization rule |
-12505 |
|
Error: Network manager error has occured. |
-12506 |
|
Error: Power manager error has occured. |
-12507 |
|
Error: Internal error has occured. |
-12508 |
|
Error: Found platform rule |
-12509 |
|
Error: Failed to establish dialup connection. |
-12510 |
|
Error: Failed to process server notification of priority |
-12511 |
|
Eror: Control connection to the agent is closed due to an error. |
-12512 |
|
Error: Invalid control command received: |
-12513 |
|
Error: Invalid server notification received: |
-12514 |
|
Error: Cannot stop the agent because |
-12516 |
|
Error: The agent cannot accept control command |
-12517 |
|
Could not find platform database. |
-12518 |
|
Invalid rule type: |
-12519 |
|
Invalid rule subtype: |
-12520 |
|
Invalid rule class: |
-12521 |
|
Invalid rule subtype |
-12522 |
|
Invalid date format: |
-12523 |
|
Invalid subtype |
-12524 |
|
Invalid subtype |
-12525 |
|
Invalid type |
-12526 |
|
Invalid type |
-12527 |
|
Query is missing for a SQL rule. |
-12528 |
|
Found duplicate platform databases: |
-12529 |
|
Cannot start the sync agent because another instance is already running. |
-12530 |
|
|
-12531 |
|
Invalid number parameter specified: |
-12532 |
|
Invalid string parameter specified: |
-12533 |
|
Invalid status to wait for: |
-12534 |
|
Invalid session handle provided. |
-12535 |
|
Control operation has timed out. |
-12536 |
|
Operation \"%s\" cannot be performed because sync agent is not running. |
-12537 |
|
Cannot create message reader because the allowed maximum of |
-12538 |
|
Message reader was canceled from another thread. |
-12539 |
|
Cannot start sync agent because it has been disabled. |
-12540 |
|
No background sync enabled publications were found on the client. |
-12541 |
|
Failed to evaluate rules for database |
-12542 |
|
Invalid parameter specified: |
-12543 |
|
Failed to start the Sync Agent. See the cause for more information. |
-12544 |
|
Failed to stop the Sync Agent. See the cause for more information. |
-12545 |
|
Failed to pause the Sync Agent. See the cause for more information. |
-12546 |
|
Failed to resume the Sync Agent. See the cause for more information. |
-12547 |
|
Sync Agent encountered fatal error or cannot be stopped. |
These errors are received if a problem occured within an automatic synchronization event.
bglog
directory for a more detailed error message. Then, check the given rule on the server for validity, modify the rule, and re-sync with a regular synchronization (msync).conscli.odb
for your user and check the C$BG_SYNC_LOG
table for the internal error message pertaining to this error. If the cause is not obvious, call Customer Support for assistance.conscli.odb
for your user and check for the network script of type "NETCONFIG
" that is stored in the C$SCRIPTS
table. Check the script for the names of all dialup connections. If they are not correct, fix the script on the server and re-synchronize with a regular synchronize (msync). Otherwise, check your dialup network settings.conscli.odb
for your user and check the C$BG_SYNC_LOG
table for the contents of the internal error message pertaning to this error. Check your network settings. Otherwise, call Customer Support for assistance.conscli.odb
for your user and check the C$BG_SYNC_LOG
table for the contents of internal error message pertaning to this error. Check your system power settings. Otherwise, call customer support for assistance.conscli.odb
for your user and check the C$BG_SYNC_LOG
table for the details of this message. Call Customer Support for assistance.CreateVirtualPKColumn ()
to create virtual primary key(s).ParentHint ()
, but it has not; or the parent table name was misspelled.ParentHint()
to set the parent table of the publication item.Ignore this error if it is for adding the same object.
Use the corresponding API to remove the named object first and try again.
Use another name.
CONNECTSTRING
or SERVICENAME
parameters. If these are correct, verify MOBILESCHEMA
and MOBILEPASSWORD
parameters. If these are correct, verify that database is available.GATHERSTATS
parameter.GATHERSTATS
enabled.