Discussion:
ifxclone issue
(too old to reply)
Link, David A
2013-09-24 14:54:40 UTC
Permalink
We are running 11.70.FC7W2 on AIX 6.1. It failed on the convert to ER.

Running a check we get the following error. It does not point us to a UDT and to our knowledge we do not have any UDTs.

FATAL: Instance has UDTs which do not support ER.
Secondary conversion to ER is not possible.

Errors:0001 Warnings:0036
command failed -- Error while processing cdr sec2er command - see output (225)
--
-- WARNING:
--
-- DDL statements will not be automatically propagated to the ER server
-- after converting the secondary server into an ER server. If you
-- create or alter any objects, such as databases, tables, indexes,
-- and so on., you must manually propagate those changes to the ER node and
-- change any replication rules affecting those objects.
--


How do we determine what the UDT may be? We ran the following query against the database which had what looked higher record count in the sysxtdtypes table. Here is the result.

print "select * from sysxtdtypes"|sqlcmd -d XXX
1||B|informix|lvarchar|40|0|32739|0|F|F|1|0
2||B|informix|sendrecv|40|0|2048|0|F|T|1|0
3||B|informix|impexp|40|0|2048|0|F|T|1|0
4||B|informix|impexpbin|40|0|2048|0|F|T|1|0
5||B|informix|boolean|41|0|1|1|T|F|1|0
6||B|informix|pointer|41|0|8|8|T|F|8|0
7||B|informix|indexkeyarray|40|0|1024|0|F|T|4|0
8||B|informix|rtnparamtypes|40|0|4096|0|F|T|1|0
9||B|informix|selfuncargs|41|0|24|24|F|T|1|0
10||B|informix|blob|41|0|72|72|F|T|4|0
11||B|informix|clob|41|0|72|72|F|T|4|0
12||B|informix|lolist|40|0|2048|0|F|T|4|0
13||B|informix|ifx_lo_spec|41|0|596|596|F|F|8|0
14||B|informix|ifx_lo_stat|41|0|644|644|F|F|8|0
15||B|informix|stat|40|0|272|0|F|T|8|0
16||B|informix|clientbinval|40|0|2048|0|F|T|1|0
17||B|informix|stream|41|0|4|4|T|F|1|0
18||D|informix|idssecuritylabel|2061|0||128|F|F|1|0
19||D|informix|idselementenc|2048|0||8|F|F|1|0
20||D|informix|idscoveringinfo|2061|0||128|F|F|1|0
2048||B|informix|sysbldsqltext|40|0|24000|0|F|F|1|0
2049||B|informix|node|40|0|256|0|F|F|4|0
2050||C|informix||21|0|0|136|||0|-1741983788
2074||C|informix||22|0|0|280|F|F|4|-39577010
2052||C|informix||22|0|260|0|F|F|4|-1569684745
2053||C|informix||22|0|260|0|F|F|4|-1748410400
2054||C|informix||19|0|0|152|||0|1304000557
2055||C|informix||22|0|0|275|F|F|4|-220858390
2111||C|informix||22|0|0|162|F|F|4|-74088656
2124||C|informix||22|0|0|22|F|F|4|-1506790425
2168||C|informix||22|0|0|182|F|F|4|532917742
2235||C|informix||22|0|28|0|F|F|4|1817905009
2281||C|informix||22|0|2124|0|F|T|4|1736553051
2282||C|informix||21|0|0|136|||0|2081655777


Not sure what the 2050+ extended_id's are.
Art Kagel
2013-09-24 15:01:13 UTC
Permalink
Mode "C" extended types are Collections or unnamed row types. Since the
name column is NULL for these entries, I will assume they are unnamed ROW
types. ROW type columns are supposed to be supported by ER, so I don't
know.

Art


Art S. Kagel, Principal Consultant

Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/

Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on my employer, Advanced DataTools, the IIUG, nor any
other organization with which I am associated either explicitly,
implicitly, or by inference. Neither do those opinions reflect those of
other individuals affiliated with any entity with which I am affiliated nor
those of the entities themselves.
We are running 11.70.FC7W2 on AIX 6.1. It failed on the convert to ER. ***
*
** **
Running a check we get the following error. It does not point us to a UDT
and to our knowledge we do not have any UDTs.****
** **
FATAL: Instance has UDTs which do not support ER.****
Secondary conversion to ER is not possible.****
** **
Errors:0001 Warnings:0036****
command failed -- Error while processing cdr sec2er command - see output
(225)****
--****
-- WARNING:****
--****
-- DDL statements will not be automatically propagated to the ER server**
**
-- after converting the secondary server into an ER server. If you****
-- create or alter any objects, such as databases, tables, indexes,****
-- and so on., you must manually propagate those changes to the ER node
and****
-- change any replication rules affecting those objects.****
--****
** **
** **
How do we determine what the UDT may be? We ran the following query
against the database which had what looked higher record count in the
sysxtdtypes table. Here is the result.****
** **
print "select * from sysxtdtypes"|sqlcmd -d XXX****
1||B|informix|lvarchar|40|0|32739|0|F|F|1|0****
2||B|informix|sendrecv|40|0|2048|0|F|T|1|0****
3||B|informix|impexp|40|0|2048|0|F|T|1|0****
4||B|informix|impexpbin|40|0|2048|0|F|T|1|0****
5||B|informix|boolean|41|0|1|1|T|F|1|0****
6||B|informix|pointer|41|0|8|8|T|F|8|0****
7||B|informix|indexkeyarray|40|0|1024|0|F|T|4|0****
8||B|informix|rtnparamtypes|40|0|4096|0|F|T|1|0****
9||B|informix|selfuncargs|41|0|24|24|F|T|1|0****
10||B|informix|blob|41|0|72|72|F|T|4|0****
11||B|informix|clob|41|0|72|72|F|T|4|0****
12||B|informix|lolist|40|0|2048|0|F|T|4|0****
13||B|informix|ifx_lo_spec|41|0|596|596|F|F|8|0****
14||B|informix|ifx_lo_stat|41|0|644|644|F|F|8|0****
15||B|informix|stat|40|0|272|0|F|T|8|0****
16||B|informix|clientbinval|40|0|2048|0|F|T|1|0****
17||B|informix|stream|41|0|4|4|T|F|1|0****
18||D|informix|idssecuritylabel|2061|0||128|F|F|1|0****
19||D|informix|idselementenc|2048|0||8|F|F|1|0****
20||D|informix|idscoveringinfo|2061|0||128|F|F|1|0****
2048||B|informix|sysbldsqltext|40|0|24000|0|F|F|1|0****
2049||B|informix|node|40|0|256|0|F|F|4|0****
2050||C|informix||21|0|0|136|||0|-1741983788****
2074||C|informix||22|0|0|280|F|F|4|-39577010****
2052||C|informix||22|0|260|0|F|F|4|-1569684745****
2053||C|informix||22|0|260|0|F|F|4|-1748410400****
2054||C|informix||19|0|0|152|||0|1304000557****
2055||C|informix||22|0|0|275|F|F|4|-220858390****
2111||C|informix||22|0|0|162|F|F|4|-74088656****
2124||C|informix||22|0|0|22|F|F|4|-1506790425****
2168||C|informix||22|0|0|182|F|F|4|532917742****
2235||C|informix||22|0|28|0|F|F|4|1817905009****
2281||C|informix||22|0|2124|0|F|T|4|1736553051****
2282||C|informix||21|0|0|136|||0|2081655777****
** **
** **
Not sure what the 2050+ extended_id’s are.****
** **
** **
_______________________________________________
Informix-list mailing list
http://www.iiug.org/mailman/listinfo/informix-list
Link, David A
2013-09-24 15:14:00 UTC
Permalink
I think we found it. The stupid ERROR is higher in the output of the check.

ERROR: create_sql is a UDT(sysbldsqltext) but has no ER support.
Found in table informix.sysbldobjects in database class

We think this is part of the node datablade. Are nodes supported by ER?

From: Art Kagel [mailto:***@gmail.com]
Sent: Tuesday, September 24, 2013 10:01 AM
To: Link, David A
Cc: informix-***@iiug.org
Subject: Re: ifxclone issue

Mode "C" extended types are Collections or unnamed row types. Since the name column is NULL for these entries, I will assume they are unnamed ROW types. ROW type columns are supposed to be supported by ER, so I don't know.

Art


Art S. Kagel, Principal Consultant

Advanced DataTools (www.advancedatatools.com<http://www.advancedatatools.com>)
Blog: http://informix-myview.blogspot.com/

Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference. Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves.

On Tue, Sep 24, 2013 at 10:54 AM, Link, David A <***@west.com<mailto:***@west.com>> wrote:
We are running 11.70.FC7W2 on AIX 6.1. It failed on the convert to ER.

Running a check we get the following error. It does not point us to a UDT and to our knowledge we do not have any UDTs.

FATAL: Instance has UDTs which do not support ER.
Secondary conversion to ER is not possible.

Errors:0001 Warnings:0036
command failed -- Error while processing cdr sec2er command - see output (225)
--
-- WARNING:
--
-- DDL statements will not be automatically propagated to the ER server
-- after converting the secondary server into an ER server. If you
-- create or alter any objects, such as databases, tables, indexes,
-- and so on., you must manually propagate those changes to the ER node and
-- change any replication rules affecting those objects.
--


How do we determine what the UDT may be? We ran the following query against the database which had what looked higher record count in the sysxtdtypes table. Here is the result.

print "select * from sysxtdtypes"|sqlcmd -d XXX
1||B|informix|lvarchar|40|0|32739|0|F|F|1|0
2||B|informix|sendrecv|40|0|2048|0|F|T|1|0
3||B|informix|impexp|40|0|2048|0|F|T|1|0
4||B|informix|impexpbin|40|0|2048|0|F|T|1|0
5||B|informix|boolean|41|0|1|1|T|F|1|0
6||B|informix|pointer|41|0|8|8|T|F|8|0
7||B|informix|indexkeyarray|40|0|1024|0|F|T|4|0
8||B|informix|rtnparamtypes|40|0|4096|0|F|T|1|0
9||B|informix|selfuncargs|41|0|24|24|F|T|1|0
10||B|informix|blob|41|0|72|72|F|T|4|0
11||B|informix|clob|41|0|72|72|F|T|4|0
12||B|informix|lolist|40|0|2048|0|F|T|4|0
13||B|informix|ifx_lo_spec|41|0|596|596|F|F|8|0
14||B|informix|ifx_lo_stat|41|0|644|644|F|F|8|0
15||B|informix|stat|40|0|272|0|F|T|8|0
16||B|informix|clientbinval|40|0|2048|0|F|T|1|0
17||B|informix|stream|41|0|4|4|T|F|1|0
18||D|informix|idssecuritylabel|2061|0||128|F|F|1|0
19||D|informix|idselementenc|2048|0||8|F|F|1|0
20||D|informix|idscoveringinfo|2061|0||128|F|F|1|0
2048||B|informix|sysbldsqltext|40|0|24000|0|F|F|1|0
2049||B|informix|node|40|0|256|0|F|F|4|0
2050||C|informix||21|0|0|136|||0|-1741983788
2074||C|informix||22|0|0|280|F|F|4|-39577010
2052||C|informix||22|0|260|0|F|F|4|-1569684745
2053||C|informix||22|0|260|0|F|F|4|-1748410400
2054||C|informix||19|0|0|152|||0|1304000557
2055||C|informix||22|0|0|275|F|F|4|-220858390
2111||C|informix||22|0|0|162|F|F|4|-74088656
2124||C|informix||22|0|0|22|F|F|4|-1506790425
2168||C|informix||22|0|0|182|F|F|4|532917742
2235||C|informix||22|0|28|0|F|F|4|1817905009
2281||C|informix||22|0|2124|0|F|T|4|1736553051
2282||C|informix||21|0|0|136|||0|2081655777


Not sure what the 2050+ extended_id's are.
jrenaut
2013-09-24 16:18:02 UTC
Permalink
Post by Link, David A
I think we found it. The stupid ERROR is higher in the output of the check.
 
ERROR:  create_sql is a UDT(sysbldsqltext) but has no ER support.
        Found in table informix.sysbldobjects in database class
 
We think this is part of the node datablade. Are nodes supported by ER?
 
Sent: Tuesday, September 24, 2013 10:01 AM
To: Link, David A
Subject: Re: ifxclone issue
 
Mode "C" extended types are Collections or unnamed row types.  Since the name column is NULL for these entries, I will assume they are unnamed ROW types.  ROW type columns are supposed to be supported by ER, so I don't know.
 
Art
 
Art S. Kagel, Principal Consultant
Advanced DataTools (www.advancedatatools.com)
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions and do not reflect on my employer, Advanced DataTools, the IIUG, nor any other organization with which I am associated either explicitly, implicitly, or by inference.  Neither do those opinions reflect those of other individuals affiliated with any entity with which I am affiliated nor those of the entities themselves.
 
We are running 11.70.FC7W2 on AIX 6.1. It failed on the convert to ER.
 
Running a check we get the following error. It does not point us to a UDT and to our knowledge we do not have any UDTs.
 
FATAL:  Instance has UDTs which do not support ER.
Secondary conversion to ER is not possible.
 
Errors:0001   Warnings:0036
command failed -- Error while processing cdr sec2er command - see output (225)
--
--
--  DDL statements will not be automatically propagated to the ER server
--  after converting the secondary server into an ER server.  If you
--  create or alter any objects, such as databases, tables, indexes,
--  and so on., you must manually propagate those changes to the ER node and
--  change any replication rules affecting those objects.
--
 
 
How do we determine what the UDT may be? We ran the following query against the database which had what looked higher record count in the sysxtdtypes table. Here is the result.
 
print "select * from sysxtdtypes"|sqlcmd -d XXX
1||B|informix|lvarchar|40|0|32739|0|F|F|1|0
2||B|informix|sendrecv|40|0|2048|0|F|T|1|0
3||B|informix|impexp|40|0|2048|0|F|T|1|0
4||B|informix|impexpbin|40|0|2048|0|F|T|1|0
5||B|informix|boolean|41|0|1|1|T|F|1|0
6||B|informix|pointer|41|0|8|8|T|F|8|0
7||B|informix|indexkeyarray|40|0|1024|0|F|T|4|0
8||B|informix|rtnparamtypes|40|0|4096|0|F|T|1|0
9||B|informix|selfuncargs|41|0|24|24|F|T|1|0
10||B|informix|blob|41|0|72|72|F|T|4|0
11||B|informix|clob|41|0|72|72|F|T|4|0
12||B|informix|lolist|40|0|2048|0|F|T|4|0
13||B|informix|ifx_lo_spec|41|0|596|596|F|F|8|0
14||B|informix|ifx_lo_stat|41|0|644|644|F|F|8|0
15||B|informix|stat|40|0|272|0|F|T|8|0
16||B|informix|clientbinval|40|0|2048|0|F|T|1|0
17||B|informix|stream|41|0|4|4|T|F|1|0
18||D|informix|idssecuritylabel|2061|0||128|F|F|1|0
19||D|informix|idselementenc|2048|0||8|F|F|1|0
20||D|informix|idscoveringinfo|2061|0||128|F|F|1|0
2048||B|informix|sysbldsqltext|40|0|24000|0|F|F|1|0
2049||B|informix|node|40|0|256|0|F|F|4|0
2050||C|informix||21|0|0|136|||0|-1741983788
2074||C|informix||22|0|0|280|F|F|4|-39577010
2052||C|informix||22|0|260|0|F|F|4|-1569684745
2053||C|informix||22|0|260|0|F|F|4|-1748410400
2054||C|informix||19|0|0|152|||0|1304000557
2055||C|informix||22|0|0|275|F|F|4|-220858390
2111||C|informix||22|0|0|162|F|F|4|-74088656
2124||C|informix||22|0|0|22|F|F|4|-1506790425
2168||C|informix||22|0|0|182|F|F|4|532917742
2235||C|informix||22|0|28|0|F|F|4|1817905009
2281||C|informix||22|0|2124|0|F|T|4|1736553051
2282||C|informix||21|0|0|136|||0|2081655777
 
 
Not sure what the 2050+ extended_id’s are.
 
 
_______________________________________________
Informix-list mailing list
http://www.iiug.org/mailman/listinfo/informix-list
I don't think what you found is related to the Node.2.0 blade. But from the doc it looks like for an opaque type to be ok for ER there needs to be both a streamread/streamwrite function for the type. The type you are getting the error on appears to be sysbldsqltext and when I looked for that I found it in $INFORMIXDIR/extend/ifxmngr in the sysbldinit.sql file. However, I didn't see a streamwrite/streamread function in there though. I think the ifxmngr blade is registered every time you register some other blade (I'm possibly incorrect about that) so it could be that because you registered the Node blade, the ifxmngr blade also gets registered and it appears that blade isn't set up to work with ER...which seems like that could be a problem. I'd guess you'd probably want to open a PMR on that, and see if the problem can be reproduced (the problem being that just registering the Node blade makes a server unable to use ifxclone to switch to ER or whatever it is you are doing exactly, and then the ifxmngr blade would need to be updated to include streamread/streamwrite functions) and likely submitted as a defect.

Jacques Renaut
IBM Informix Advanced Support
APD Team

Loading...