Icon and Infomart installation trouble

[smile]

I've installed ICON and Infomart v.7.6 as described in deployment guides in single tenant environment. I use only one db for roles ICON_CFG,ICON_CORE and ICON_OCS. When I'm running gim configuration checker or gimserver, they says:

[code]
09:56:01.699 Dbg 35000 GimConfig.getTenants - Tenant count=1

2009-09-30 09:56:02,074 INFO  Thread-434  55-30100 "Configuration file has been updated."

09:56:02.230 Trc 30100 Configuration file has been updated.

2009-09-30 09:56:03,152 WARN  Thread-434  55-24010 "Extract jobs are not runnable.  DAP 'icon_mart_DAP' configured with role ICON_CFG has no tenants in table 'genesys.GC_TENANT'."

09:56:03.168 Std 24010 Extract jobs are not runnable.  DAP 'icon_mart_DAP' configured with role ICON_CFG has no tenants in table 'genesys.GC_TENANT'.

09:56:03.215 Dbg 35204 GIM Listener - sending response for 'Request3rdServer' message with referenceID '3'.  Response='KVList:        '-rc' [int] = 4        '-errmsg' [str] =
"Extract jobs are not runnable.  DAP 'icon_mart_DAP' configured with role ICON_CFG has no tenants in table 'genesys.GC_TENANT'."'
[/code]

GIM Admin Console says the same as the last message when i'm trying to run job Job_ExtractICON'. In fact,  GC_TENANT table has no records. Who should to fill this table?

[ecki]

Hi,

That sounds like you did not correctly installed ICON database. Haven't you seen database errors when you run those scripts? If you are not yet using ICON in production, then the recommendation for fast resolution would be to drop Icon database and create it from the scratch. Make sure you have correct database access rights for user you are using for installation. Then delete *.pq Icon file and after this start ICON again.

Cheers,

e.

[René]

Smile,

Have you run ICON before running GIM Configuration Checker?

R.

[smile]

Thank you, All!
The proposed solution by [b]ecki[/b] was extremely useful. This may seems to very simple, but i've tried to reinstall icon  db several times, before without success. I think the key was in the strangest .pq file