Client sync failure: "sequence does not exist"

Question

Hello everyone,
I could use some help on this.Using 10.3 mobile server and a mobile6 client (using the official mobile6 patch). After some syncs, a mobile client gets the error "sequence does not exist", and the replication fails.
When looking at the server log, after the client has successfully uploaded its data, a sequence "M$8232031$M" is created on the server just before the client can download its new data. Then, the server tries to get the nextval from that sequence - and the sequence is not there !!
What happened, what can cause this behaviour ?
Here is an excerpt from the server log with the "faulty" client sync :
clog: Subscription.prepStatement: ALL: SQL: INSERT INTO MOBILEADMIN.C$ALL_MANGLED_NAMES(CLIENTID,ORIGINAL_NAME,MANGLED_NAME) VALUES(?,?,?):
Object: @1da9a66
clog: Subscription.execDirectLogged: FINEST: GENERAL: Created M$8232031$M
clog: Subscription.mangleOS: ALL: FUNCTION: Exiting
clog: Subscription.pstmClose: ALL: FUNCTION: Entering
clog: Subscription.pstmClose: FINEST: GENERAL: pstmt::close
clog: Subscription.pstmClose: ALL: FUNCTION: Exiting
clog: Subscription.mangle: FINEST: GENERAL: conn user =MOBILEADMIN, e[0]=MOBILEADMIN
clog: Subscription.mangle: ALL: FUNCTION: Exiting: user.equals(e[0])
clog: Consolidator.DQ: ALL: FUNCTION: Invoking
clog: O8Server.advanceSequence: ALL: FUNCTION: Invoking
clog: Subscription.execSelectDirect: ALL: FUNCTION: Entering
clog: Subscription.execSelectDirect: ALL: SQL: exec:::
Object: SELECT "M$8232031$M".NEXTVAL FROM DUAL
clog: HeliosSession.startSession: FINEST: GENERAL: Decrement client download 0
clog: HeliosSession.clientDownload: ALL: FUNCTION: Invoking
clog: HeliosSession.startSession: MANDATORY: ALL:
Exception: java.sql.SQLException: ORA-02289: Sequence ist nicht vorhanden.
ORA-02289: Sequence ist nicht vorhanden.
clog: HeliosSession.sendE, s=ORA-02289: Sequence ist nicht vorhanden.
: ALL: FUNCTION: Entering
clog: HeliosSession.sendCompress: ALL: FUNCTION: Entering
clog: HeliosSession.sendCompress: FINEST: GENERAL: deflated total in,out is 52,2 bytes
clog: HeliosSession.sendCompress: FINEST: GENERAL: Sending byte array of 2 bytes
clog: HeliosSession.sendConv: ALL: FUNCTION: Invoking
clog: HeliosSession.initConvOS: ALL: FUNCTION: Invoking
clog: Client.send: ALL: FUNCTION: Entering
clog: Client.send: ALL: FUNCTION: Exiting
clog: ConvAtOutputStream.write: ALL: FUNCTION: Entering
clog: ConvAtOutputStream.write: FINEST: GENERAL: exlen:16
clog: ConvAtOutputStream.write: ALL: FUNCTION: Exiting
clog: ConvAtOutputStream.write: ALL: FUNCTION: Entering
clog: ConvAtOutputStream.write: FINEST: GENERAL: exlen:8
clog: ConvAtOutputStream.write: ALL: FUNCTION: Exiting
clog: HeliosSession.sendCompress: ALL: FUNCTION: Exiting
clog: HeliosSession.sendE: ALL: FUNCTION: Exiting
clog: HeliosSession.sendCompress: ALL: FUNCTION: Entering
clog: HeliosSession.sendCompress: FINEST: GENERAL: Sending byte array of 60 bytes
clog: HeliosSession.sendConv: ALL: FUNCTION: Invoking
clog: ConvAtOutputStream.write: ALL: FUNCTION: Entering
clog: ConvAtOutputStream.write: FINEST: GENERAL: exlen:6
clog: ConvAtOutputStream.xop: ALL: FUNCTION: Invoking
clog: Client.send: ALL: FUNCTION: Entering
clog: Client.send: ALL: FUNCTION: Exiting
clog: ConvAtOutputStream.xop: ALL: FUNCTION: Invoking
clog: Client.send: ALL: FUNCTION: Entering
clog: Client.send: ALL: FUNCTION: Exiting
clog: ConvAtOutputStream.xop: ALL: FUNCTION: Invoking
clog: Client.send: ALL: FUNCTION: Entering
clog: Client.send: ALL: FUNCTION: Exiting
clog: ConvAtOutputStream.xop: ALL: FUNCTION: Invoking
clog: Client.send: ALL: FUNCTION: Entering
clog: Client.send: ALL: FUNCTION: Exiting
clog: ConvAtOutputStream.write: ALL: FUNCTION: Exiting
clog: HeliosSession.sendConv: ALL: FUNCTION: Invoking
clog: ConvAtOutputStream.flush: ALL: FUNCTION: Entering
clog: ConvAtOutputStream.flush: FINEST: GENERAL: tail = 6
clog: ConvAtOutputStream.xop: ALL: FUNCTION: Invoking
clog: Client.send: ALL: FUNCTION: Entering
clog: Client.send: ALL: FUNCTION: Exiting
clog: ConvAtOutputStream.flush: FINEST: GENERAL: Sent to pipe 16 bytes
clog: HeliosSession.sendCompress: ALL: FUNCTION: Exiting
clog: Client.flush: ALL: FUNCTION: Entering
clog: Client.flush: ALL: RESUME: Data length: 86
clog: Client.flush: ALL: FUNCTION: Exiting
clog: HeliosSession.startSession: FINEST: GENERAL: disconnecting jdbc
clog: JupConnection.destroy: ALL: FUNCTION: Entering
clog: JupConnection.destroy: ALL: FUNCTION: Exiting
clog: HeliosSession.startSession: ALL: FUNCTION: Exiting
clog: Client.startSync: MANDATORY: ALL:
Exception: java.sql.SQLException: ORA-02289: Sequence ist nicht vorhanden.
ORA-02289: Sequence ist nicht vorhanden.
clog: HeliosSession.getSessionType: ALL: FUNCTION: Invoking
clog: Server.newConnection (): ALL: FUNCTION: Invoking

Answer 1

Check your err.log after you create the users to see if there is any issues.
I have had various issues with users Data Subsetting not being set. I find this happens when there are many blocking locks and users are being drop, created, password change, etc. Blocking locks are part of the nature of the application, the only way to really combat that is to do some performance tuning on the MGP and the SYNC.
Here is how I create my user:
        try {   
            rm.createUser(USERNAME, PASSWORD, DISPLAY_NAME, "U");
            rm.setUserAccess("/app", USERNAME, true);
            rm.setTemplateVariable("/app", USERNAME, "USER_ID", PARAMETER);
            rm.commitTransaction();
        } catch (ResException res) {
            rm.rollbackTransaction();
            res.printStackTrace();
        }