Issues updating Multi Media Interaction Server

[phil]

hello,

i was updating Interaction Server 7.6.000.23 >>>7.6.101.24. Now a custom DB is not loaded correctly and MM- Tasks are not distributed through Interaction Server. The log says:

[...]

2010-03-26T11:37:52.625 Std 25004 Database:'testawd:oracle', DBServer:'DBServer_InteractionServer', DAP:'DAP_InteractionServer' is opened
2010-03-26T11:37:52.625 Std 25009 DAP:'DAP_InteractionServer', DBServer version:'7.6.000.14' ('7.5.000.02' or greater required)
2010-03-26T11:37:52.625 Dbg 25030 Database request sent: DAP:'DAP_InteractionServer'(0), request id:'5', dbchannel stack id:'1', interaction id:'', sql statement: [SELECT COLUMN_NAME, DATA_TYPE, DATA_LENGTH, DATA_PRECISION, CHAR_LENGTH FROM USER_TAB_COLUMNS WHERE TABLE_NAME = 'INTERACTIONS']
2010-03-26T11:37:52.625 Std 05060 Application started
2010-03-26T11:37:52.625 Dbg 25032 Database request executed: DAP:'DAP_InteractionServer'(0), request id:'5', dbchannel stack id:'1', interaction id:'', sql statement: [collect data]
2010-03-26T11:37:52.625 Dbg 25032 Database request executed: DAP:'DAP_InteractionServer'(0), request id:'5', dbchannel stack id:'1', interaction id:'', sql statement: [ ]
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'contact_id' with type 'VARCHAR2' and size 16 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'customer_segment' with type 'VARCHAR2' and size 64 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'service_type' with type 'VARCHAR2' and size 64 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'category' with type 'VARCHAR2' and size 64 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'case_id' with type 'VARCHAR2' and size 64 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'reason_code' with type 'VARCHAR2' and size 32 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'disposition_code' with type 'VARCHAR2' and size 32 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'from_personal' with type 'VARCHAR2' and size 256 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'from_address' with type 'VARCHAR2' and size 256 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'mailbox' with type 'VARCHAR2' and size 256 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'subject' with type 'VARCHAR2' and size 512 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25042 Size of interaction property is adjusted to match database: property 'ServiceObjective' with field name 'service_objective' had size 28, now 38
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'custom_1s' with type 'VARCHAR2' and size 256 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'custom_2s' with type 'VARCHAR2' and size 256 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'custom_3s' with type 'VARCHAR2' and size 256 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'custom_4s' with type 'VARCHAR2' and size 64 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'custom_5s' with type 'VARCHAR2' and size 64 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'custom_6s' with type 'VARCHAR2' and size 64 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'custom_7s' with type 'VARCHAR2' and size 64 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'custom_1n' with type 'NUMBER' and size 38 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'custom_2n' with type 'NUMBER' and size 38 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Trc 25046 Custom database field 'custom_3n' with type 'NUMBER' and size 38 is ignored because it is not defined in configuration
2010-03-26T11:37:52.625 Std 25048 Wrong database schema: property 'cache' with field name 'cache' is not found in database table definition
2010-03-26T11:37:52.625 Std 25048 Wrong database schema: property 'SubmitSeq' with field name 'submit_seq' is not found in database table definition
2010-03-26T11:37:52.625 Std 25048 Wrong database schema: property 'PlaceInQueueSeq' with field name 'place_in_queue_seq' is not found in database table definition

[...]

And this is how it should look like and does look like in the previous version:

[...]


2010-03-26T15:10:12.341 Dbg 25032 Database request executed: DAP:'DAP_InteractionServer'(0), request id:'24', sql statement:[Begin Transaction], dbchannel stack id:'1', interaction id:'' 
2010-03-26T15:10:12.341 Dbg 25030 Database request sent: DAP:'DAP_InteractionServer'(0), request id:'25', sql statement:[select id,server_id,parent_id,tenant_id,is_online,is_locked,snapshot_place_id,state,queue,media_type,type,subtype,agent_id,agent_group_id,place_id,place_group_id,submitted_by,TO_CHAR(received_at, 'YYYY-MM-DD HH24:MI:SS') AS received_at_,TO_CHAR(submitted_at, 'YYYY-MM-DD HH24:MI:SS') AS submitted_at_,TO_CHAR(delivered_at, 'YYYY-MM-DD HH24:MI:SS') AS delivered_at_,TO_CHAR(placed_in_queue_at, 'YYYY-MM-DD HH24:MI:SS') AS placed_in_queue_at_,TO_CHAR(moved_to_queue_at, 'YYYY-MM-DD HH24:MI:SS') AS moved_to_queue_at_,workbin,destinations,TO_CHAR(abandoned_at, 'YYYY-MM-DD HH24:MI:SS') AS abandoned_at_,external_id,priority,contact_id,customer_segment,service_type,category,case_id,reason_code,disposition_code,subject,from_personal,from_address,mailbox,service_objective,custom_1s,custom_2s,custom_3s,custom_4s,custom_5s,custom_6s,custom_7s,custom_1n,custom_2n,custom_3n from interactions where id in (select id from (select id from interactions where state = 0 and is_locked = 0 and queue = 'GTL_Q2' and tenant_id = 101 order by received_at, id) where rownum <= 200) order by received_at, id for update], dbchannel stack id:'2', interaction id:''

[...]

Do you know what the problem is, considering that i changed nothing but the binaries. There was no script provided with the Installation package, which could have adapted the DB. After a Rollback everything is fine again.

Have a nice weekend!
So long!

Phil

[catanirex]

Hi,

You have to run the upgrade script. It can be found in the installation directory after installing Interaction Server.

The warnings about custom database fields will still be in the logs, it is just telling you that there are no custom fields defined :-)

But the two last lines will be gone, and it will work!

[phil]

Great, thank you!

[René]

Hi Phil,

Structure of Interaction Server database was changed significantly in the release 7.6.1. Business attributes are not longer stored as independent fields/columns in the interaction table but these are stored within the field "flexible_properties". You can find more details in the Multimedia 7.6 User's Guide and in the Genesys Migration Guide.

R.