Informix - Problem description
Problem IT27609 | Status: Closed |
ERROR 768 WHEN RUNNING A QUERY | |
product: | |
INFORMIX SERVER / 5725A3900 / C10 - IDS 12.10 | |
Problem description: | |
One can get error: 768 when they run the below query SELECT distinct 'ORIGINAL', codigo_tipo_produto, codigo_marca, codigo_familia, codigo_subfamilia, codigo_produto, codigo_cor, tamanho from bi_carteira_detl a, bi_produto_tamanho b where a.produto_tamanho_id = b.produto_tamanho_id and a.produto_tamanho_id = 3915068 union SELECT distinct 'TROCAR', codigo_tipo_produto, codigo_marca, codigo_familia, codigo_subfamilia, codigo_produto, codigo_cor, tamanho from bi_produto_tamanho b where b.produto_tamanho_id = 3932494 ; 768: Internal error in routine compute_op_mem: operator not in phase. Error in line 10 Near character position 35 Below is the stack from the onmode -I 768 16:39:14 Stack for thread: 54 sqlexec base: 0x000000004e5eb000 len: 102400 pc: 0x000000000141d579 tos: 0x000000004e601270 state: running vp: 1 (oninit) afstack (oninit) afhandler (oninit) affail_interface (oninit) check_traperror (oninit) sqerr (oninit) sqerr1 (oninit) compute_op_mem (oninit) bldmgmseg (oninit) itbldroot (oninit) sqoptim (oninit) bldstructs (oninit) sqcmd (oninit) sq_cmnd (oninit) sq_prepare (oninit) sqmain (oninit) spawn_thread (oninit) th_init_initgls (oninit) startup | |
Problem Summary: | |
**************************************************************** * USERS AFFECTED: * * Users of IDS prior to 12.10.xC13. * **************************************************************** * PROBLEM DESCRIPTION: * * Error -768 when running a query. * **************************************************************** * RECOMMENDATION: * **************************************************************** | |
Local Fix: | |
Solution | |
Workaround | |
not known / see Local fix | |
Timestamps | |
Date - problem reported : Date - problem closed : Date - last modified : | 27.12.2018 03.10.2019 03.10.2019 |
Problem solved at the following versions (IBM BugInfos) | |
12.10.xC13 | |
Problem solved according to the fixlist(s) of the following version(s) |