Exceptions After Syncing: cursor not closed. (Doc ID 1413715.1)

Last updated on SEPTEMBER 21, 2016

Applies to:

Oracle Database Mobile Server - Version: 11.1.0.0.0 and later   [Release: 11.1 and later ]
Information in this document applies to any platform.

Symptoms


On : 11.1.0.0.0 version, with Sync Client For Android.

When attempting to Synchronize
the following error occurs.

ERROR
-----------------------
12-20 09:04:37.428: E/Cursor(3121): Finalizing a Cursor that has not been deactivated or closed. database = /data/data/tests.sync.t/app_oracle.sync/sqlite_db/5361/MIPSS_FELT_PUB.db, table = null, query = SELECT TEXT FROM C$SCRIPTS WHERE SCRIPT_TYPE = 'NETCONFIG'
12-20 09:04:37.428: E/Cursor(3121): android.database.sqlite.DatabaseObjectNotClosedException: Application did not close the cursor or database object that was opened here


STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Install Mobile Server 11.1.0.0.0 and start it.
2. Compile the simple sync sample application in 11g and launch it from another Activity.
3. when It exits the MainAct.java activty, this Error occurs:
12-20 09:08:21.944: E/MapActivity(3331): Couldn't get connection factory client
12-20 09:08:21.967: E/ActivityThread(3331): Activity no.mesta.mipss.felt.activity.common.SynchronizeActivity has leaked IntentReceiver oracle.opensync.syncagent.android.AndroidPowerManager$1@45e197c0 that was originally registered here. Are you missing a call to unregisterReceiver()?

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms