IBM Support

"An SMX connection attempt failed" returned in online.log while running ifxclone

Troubleshooting


Problem

You are running ifxclone to either clone an instance or set up a Secondary instance for replication, but you receive an SMX error followed by increased memory utilization and ultimately a failed ifxclone.

Symptom

In the online.log, you may see messages similar to the following

 

11:34:23 Physical Restore of datadbs Completed.
11:34:23 Checkpoint Completed: duration was 0 seconds.
11:34:23 Tue Jun 19 - loguniq 4737393, logpos 0x514564c, timestamp: 0xbd0c949b Interval: 141153

11:34:23 Maximum server connections 0
11:34:33 An SMX connection attempt failed.
11:34:33 Physical restore failed for dbspace number 5.
11:34:33
11:34:36 Physical Restore of datadbs2 ABORTED.
11:34:36 Aborted by client.
11:34:36 Physical restore failed for dbspace number 4.
11:34:36 stack trace for pid 57148614 written to /opt/informix/dump/af.49e34ab
11:34:37 Checkpoint Completed: duration was 0 seconds.
11:34:37 Tue Jun 19 - loguniq 4737393, logpos 0x514564c, timestamp: 0xbd0c94ff Interval: 141154

11:34:37 Maximum server connections 0
11:34:37 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 0, Llog used 0

11:34:38 Assert Failed: No Exception Handler
11:34:38 IBM Informix Dynamic Server Version 11.70.FC8
11:34:38 Assert Failed: No Exception Handler
11:34:38 IBM Informix Dynamic Server Version 11.70.FC8
11:34:38 Who: Session(8660, informix@, 0, 70000157937ed20)
Thread(182, SC_ontape_restore, 70000157935d058, 1)
File: mtex.c Line: 490
11:34:38 Results: Exception Caught. Type: MT_EX_OS, Context: mem
11:34:38 Action: Please notify IBM Informix Technical Support.
11:34:38 See Also: /opt/informix/dump/af.49e34ab, shmem.49e34ab.o
11:34:39 Physical Restore of datasdbs4 Completed.
11:34:39 Checkpoint Completed: duration was 0 seconds.
11:34:39 Tue Jun 19 - loguniq 4737393, logpos 0x514564c, timestamp: 0xbd0c950b Interval: 141154

11:34:39 Maximum server connections 0
11:35:07 Checkpoint Completed: duration was 0 seconds.
11:35:07 Tue Jun 19 - loguniq 4737393, logpos 0x514564c, timestamp: 0xbd0c956c Interval: 141155

11:35:07 Maximum server connections 0
11:35:07 Checkpoint Statistics - Avg. Txn Block Time 0.000, # Txns blocked 0, Plog used 0, Llog used 0

11:35:09 Physical Restore of datadbs6 Completed.
11:35:09 Checkpoint Completed: duration was 0 seconds.
11:35:09 Tue Jun 19 - loguniq 4737393, logpos 0x514564c, timestamp: 0xbd0c9578 Interval: 141155

11:35:09 Maximum server connections 0
11:45:27 mtex.c, line 490, thread 182, proc id 57148614, No Exception Handler.
11:45:28 The Master Daemon Died
11:45:28 The Master Daemon Died
11:45:28 The Master Daemon Died
11:45:28 Fatal error in ADM VP at mt.c:14055
11:45:28 Unexpected virtual processor termination, pid = 329368, exit = 0x100

11:45:28 PANIC: Attempting to bring system down

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSGU8G","label":"Informix Servers"},"Component":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
19 November 2018

UID

ibm10741247