BMcDowell1 Absent Member.
Absent Member.
888 views

ZCM Data Import with NSD 7.1 Not Working

Similar to another thread, but I'm using a newer configuration:

[INDENT]ZCM 11.3.0 with embedded Sybase database
NSD 7.1 appliance, external MySQL database[/INDENT]

I have followed all the various appropriate sections of documentation - some of which match the reality of the software, some not so much - and get a consistent error in the log file:

[INDENT][2015-05-13 11:02:53,665] INFO775355[LiveTimeScheduler_Worker-4] (SettingsFactory.java:118) - JDBC driver: jConnect (TM) for JDBC (TM), version: jConnect (TM) for JDBC(TM)/7.00(Build 26502)/P/EBF17993/JDK16/Thu Jun 3 3:09:09 2010
[2015-05-13 11:02:53,665] INFO775355[LiveTimeScheduler_Worker-4] (SettingsFactory.java:169) - Automatic flush during beforeCompletion(): disabled
[2015-05-13 11:02:53,665] INFO775355[LiveTimeScheduler_Worker-4] (SettingsFactory.java:173) - Automatic session close at end of transaction: disabled
[2015-05-13 11:02:53,666] INFO775356[LiveTimeScheduler_Worker-4] (SettingsFactory.java:188) - Scrollable result sets: enabled
[2015-05-13 11:02:53,666] INFO775356[LiveTimeScheduler_Worker-4] (SettingsFactory.java:196) - JDBC3 getGeneratedKeys(): enabled
[2015-05-13 11:02:53,666] INFO775356[LiveTimeScheduler_Worker-4] (SettingsFactory.java:204) - Connection release mode: auto
[2015-05-13 11:02:53,666] INFO775356[LiveTimeScheduler_Worker-4] (SettingsFactory.java:231) - Default batch fetch size: 1
[2015-05-13 11:02:53,667] INFO775357[LiveTimeScheduler_Worker-4] (SettingsFactory.java:235) - Generate SQL with comments: disabled
[2015-05-13 11:02:53,667] INFO775357[LiveTimeScheduler_Worker-4] (SettingsFactory.java:239) - Order SQL updates by primary key: disabled
[2015-05-13 11:02:53,667] INFO775357[LiveTimeScheduler_Worker-4] (SettingsFactory.java:243) - Order SQL inserts for batching: disabled
[2015-05-13 11:02:53,667] INFO775357[LiveTimeScheduler_Worker-4] (SettingsFactory.java:410) - Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
[2015-05-13 11:02:53,668] INFO775358[LiveTimeScheduler_Worker-4] (SettingsFactory.java:251) - Query language substitutions: {}
[2015-05-13 11:02:53,668] INFO775358[LiveTimeScheduler_Worker-4] (SettingsFactory.java:256) - JPA-QL strict compliance: disabled
[2015-05-13 11:02:53,668] INFO775358[LiveTimeScheduler_Worker-4] (SettingsFactory.java:261) - Second-level cache: disabled
[2015-05-13 11:02:53,668] INFO775358[LiveTimeScheduler_Worker-4] (SettingsFactory.java:265) - Query cache: disabled
[2015-05-13 11:02:53,669] INFO775359[LiveTimeScheduler_Worker-4] (SettingsFactory.java:395) - Cache region factory : org.hibernate.cache.impl.NoCachingRegionFactory
[2015-05-13 11:02:53,669] INFO775359[LiveTimeScheduler_Worker-4] (SettingsFactory.java:275) - Optimize cache for minimal puts: disabled
[2015-05-13 11:02:53,669] INFO775359[LiveTimeScheduler_Worker-4] (SettingsFactory.java:284) - Structured second-level cache entries: disabled
[2015-05-13 11:02:53,669] INFO775359[LiveTimeScheduler_Worker-4] (SettingsFactory.java:313) - Statistics: disabled
[2015-05-13 11:02:53,670] INFO775360[LiveTimeScheduler_Worker-4] (SettingsFactory.java:317) - Deleted entity synthetic identifier rollback: disabled
[2015-05-13 11:02:53,670] INFO775360[LiveTimeScheduler_Worker-4] (SettingsFactory.java:332) - Default entity-mode: pojo
[2015-05-13 11:02:53,670] INFO775360[LiveTimeScheduler_Worker-4] (SettingsFactory.java:336) - Named query checking : enabled
[2015-05-13 11:02:53,670] INFO775360[LiveTimeScheduler_Worker-4] (SettingsFactory.java:340) - Check Nullability in Core (should be disabled when Bean Validation is on): enabled
[2015-05-13 11:02:53,707] INFO775397[LiveTimeScheduler_Worker-4] (SettingsFactory.java:117) - RDBMS: SQL Anywhere, version: 12.0.1.3924
[2015-05-13 11:02:53,708] INFO775398[LiveTimeScheduler_Worker-4] (SettingsFactory.java:118) - JDBC driver: jConnect (TM) for JDBC (TM), version: jConnect (TM) for JDBC(TM)/7.00(Build 26502)/P/EBF17993/JDK16/Thu Jun 3 3:09:09 2010
[2015-05-13 11:02:53,708] INFO775398[LiveTimeScheduler_Worker-4] (SettingsFactory.java:169) - Automatic flush during beforeCompletion(): disabled
[2015-05-13 11:02:53,708] INFO775398[LiveTimeScheduler_Worker-4] (SettingsFactory.java:173) - Automatic session close at end of transaction: disabled
[2015-05-13 11:02:53,709] INFO775399[LiveTimeScheduler_Worker-4] (SettingsFactory.java:188) - Scrollable result sets: enabled
[2015-05-13 11:02:53,709] INFO775399[LiveTimeScheduler_Worker-4] (SettingsFactory.java:196) - JDBC3 getGeneratedKeys(): enabled
[2015-05-13 11:02:53,709] INFO775399[LiveTimeScheduler_Worker-4] (SettingsFactory.java:204) - Connection release mode: auto
[2015-05-13 11:02:53,709] INFO775399[LiveTimeScheduler_Worker-4] (SettingsFactory.java:231) - Default batch fetch size: 1
[2015-05-13 11:02:53,710] INFO775400[LiveTimeScheduler_Worker-4] (SettingsFactory.java:235) - Generate SQL with comments: disabled
[2015-05-13 11:02:53,710] INFO775400[LiveTimeScheduler_Worker-4] (SettingsFactory.java:239) - Order SQL updates by primary key: disabled
[2015-05-13 11:02:53,710] INFO775400[LiveTimeScheduler_Worker-4] (SettingsFactory.java:243) - Order SQL inserts for batching: disabled
[2015-05-13 11:02:53,711] INFO775401[LiveTimeScheduler_Worker-4] (SettingsFactory.java:410) - Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
[2015-05-13 11:02:53,711] INFO775401[LiveTimeScheduler_Worker-4] (SettingsFactory.java:251) - Query language substitutions: {}
[2015-05-13 11:02:53,711] INFO775401[LiveTimeScheduler_Worker-4] (SettingsFactory.java:256) - JPA-QL strict compliance: disabled
[2015-05-13 11:02:53,711] INFO775401[LiveTimeScheduler_Worker-4] (SettingsFactory.java:261) - Second-level cache: disabled
[2015-05-13 11:02:53,712] INFO775402[LiveTimeScheduler_Worker-4] (SettingsFactory.java:265) - Query cache: disabled
[2015-05-13 11:02:53,712] INFO775402[LiveTimeScheduler_Worker-4] (SettingsFactory.java:395) - Cache region factory : org.hibernate.cache.impl.NoCachingRegionFactory
[2015-05-13 11:02:53,712] INFO775402[LiveTimeScheduler_Worker-4] (SettingsFactory.java:275) - Optimize cache for minimal puts: disabled
[2015-05-13 11:02:53,712] INFO775402[LiveTimeScheduler_Worker-4] (SettingsFactory.java:284) - Structured second-level cache entries: disabled
[2015-05-13 11:02:53,713] INFO775403[LiveTimeScheduler_Worker-4] (SettingsFactory.java:313) - Statistics: disabled
[2015-05-13 11:02:53,713] INFO775403[LiveTimeScheduler_Worker-4] (SettingsFactory.java:317) - Deleted entity synthetic identifier rollback: disabled
[2015-05-13 11:02:53,713] INFO775403[LiveTimeScheduler_Worker-4] (SettingsFactory.java:332) - Default entity-mode: pojo
[2015-05-13 11:02:53,713] INFO775403[LiveTimeScheduler_Worker-4] (SettingsFactory.java:336) - Named query checking : enabled
[2015-05-13 11:02:53,714] INFO775404[LiveTimeScheduler_Worker-4] (SettingsFactory.java:340) - Check Nullability in Core (should be disabled when Bean Validation is on): enabled
[2015-05-13 11:02:53,743] INFO775433[LiveTimeScheduler_Worker-4] (SettingsFactory.java:117) - RDBMS: SQL Anywhere, version: 12.0.1.3924
[2015-05-13 11:02:53,744] INFO775434[LiveTimeScheduler_Worker-4] (SettingsFactory.java:118) - JDBC driver: jConnect (TM) for JDBC (TM), version: jConnect (TM) for JDBC(TM)/7.00(Build 26502)/P/EBF17993/JDK16/Thu Jun 3 3:09:09 2010
[2015-05-13 11:02:53,744] INFO775434[LiveTimeScheduler_Worker-4] (SettingsFactory.java:169) - Automatic flush during beforeCompletion(): disabled
[2015-05-13 11:02:53,744] INFO775434[LiveTimeScheduler_Worker-4] (SettingsFactory.java:173) - Automatic session close at end of transaction: disabled
[2015-05-13 11:02:53,745] INFO775435[LiveTimeScheduler_Worker-4] (SettingsFactory.java:188) - Scrollable result sets: enabled
[2015-05-13 11:02:53,745] INFO775435[LiveTimeScheduler_Worker-4] (SettingsFactory.java:196) - JDBC3 getGeneratedKeys(): enabled
[2015-05-13 11:02:53,745] INFO775435[LiveTimeScheduler_Worker-4] (SettingsFactory.java:204) - Connection release mode: auto
[2015-05-13 11:02:53,745] INFO775435[LiveTimeScheduler_Worker-4] (SettingsFactory.java:231) - Default batch fetch size: 1
[2015-05-13 11:02:53,745] INFO775435[LiveTimeScheduler_Worker-4] (SettingsFactory.java:235) - Generate SQL with comments: disabled
[2015-05-13 11:02:53,746] INFO775436[LiveTimeScheduler_Worker-4] (SettingsFactory.java:239) - Order SQL updates by primary key: disabled
[2015-05-13 11:02:53,746] INFO775436[LiveTimeScheduler_Worker-4] (SettingsFactory.java:243) - Order SQL inserts for batching: disabled
[2015-05-13 11:02:53,746] INFO775436[LiveTimeScheduler_Worker-4] (SettingsFactory.java:410) - Query translator: org.hibernate.hql.ast.ASTQueryTranslatorFactory
[2015-05-13 11:02:53,746] INFO775436[LiveTimeScheduler_Worker-4] (SettingsFactory.java:251) - Query language substitutions: {}
[2015-05-13 11:02:53,747] INFO775437[LiveTimeScheduler_Worker-4] (SettingsFactory.java:256) - JPA-QL strict compliance: disabled
[2015-05-13 11:02:53,747] INFO775437[LiveTimeScheduler_Worker-4] (SettingsFactory.java:261) - Second-level cache: disabled
[2015-05-13 11:02:53,747] INFO775437[LiveTimeScheduler_Worker-4] (SettingsFactory.java:265) - Query cache: disabled
[2015-05-13 11:02:53,747] INFO775437[LiveTimeScheduler_Worker-4] (SettingsFactory.java:395) - Cache region factory : org.hibernate.cache.impl.NoCachingRegionFactory
[2015-05-13 11:02:53,748] INFO775438[LiveTimeScheduler_Worker-4] (SettingsFactory.java:275) - Optimize cache for minimal puts: disabled
[2015-05-13 11:02:53,748] INFO775438[LiveTimeScheduler_Worker-4] (SettingsFactory.java:284) - Structured second-level cache entries: disabled
[2015-05-13 11:02:53,748] INFO775438[LiveTimeScheduler_Worker-4] (SettingsFactory.java:313) - Statistics: disabled
[2015-05-13 11:02:53,748] INFO775438[LiveTimeScheduler_Worker-4] (SettingsFactory.java:317) - Deleted entity synthetic identifier rollback: disabled
[2015-05-13 11:02:53,748] INFO775438[LiveTimeScheduler_Worker-4] (SettingsFactory.java:332) - Default entity-mode: pojo
[2015-05-13 11:02:53,749] INFO775439[LiveTimeScheduler_Worker-4] (SettingsFactory.java:336) - Named query checking : enabled
[2015-05-13 11:02:53,749] INFO775439[LiveTimeScheduler_Worker-4] (SettingsFactory.java:340) - Check Nullability in Core (should be disabled when Bean Validation is on): enabled
[2015-05-13 11:02:53,787]ERROR775477[LiveTimeScheduler_Worker-4] (SchemaStrategy.java:156) - Table check : syscolumns
[2015-05-13 11:02:53,788]ERROR775478[LiveTimeScheduler_Worker-4] (SchemaStrategy.java:156) - Table check : syscomments
[2015-05-13 11:02:53,788]ERROR775478[LiveTimeScheduler_Worker-4] (SchemaStrategy.java:156) - Table check : sysindexes
[2015-05-13 11:02:53,788]ERROR775478[LiveTimeScheduler_Worker-4] (SchemaStrategy.java:156) - Table check : syslogins
[2015-05-13 11:02:53,789]ERROR775479[LiveTimeScheduler_Worker-4] (SchemaStrategy.java:156) - Table check : sysobjects
[2015-05-13 11:02:53,790]ERROR775480[LiveTimeScheduler_Worker-4] (SchemaStrategy.java:156) - Table check : systypes
[2015-05-13 11:02:53,790]ERROR775480[LiveTimeScheduler_Worker-4] (SchemaStrategy.java:156) - Table check : sysusers
[2015-05-13 11:02:53,792]ERROR775482[LiveTimeScheduler_Worker-4] (ZenworksAmieDbComms.java:311) - An error occurred whilst initializing Comms: An unknown error occurred during the schema extraction - no tables were found
java.lang.Exception: An unknown error occurred during the schema extraction - no tables were found
at com.livetime.assetmgmt.dynamicdb.HbmParser.parseXML(HbmParser.java:267)
at com.livetime.assetmgmt.ZenworksAmieDbComms.generateSchema(ZenworksAmieDbComms.java:538)
at com.livetime.assetmgmt.ZenworksAmieDbComms.initCollection(ZenworksAmieDbComms.java:302)
at com.livetime.assetmgmt.ZenworksAmieMgr.analyzeAssets(ZenworksAmieMgr.java:232)
at com.livetime.assetmgmt.ZenworksAmieAnalysisJob.run(ZenworksAmieAnalysisJob.java:127)
at com.livetime.service.ZenworksAmieAnalysisService.execute(ZenworksAmieAnalysisService.java:66)
at org.quartz.core.JobRunShell.run(JobRunShell.java:213)
at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:557)
[/INDENT]

It seems as though there are valid schemas for each of the databases as each of the products are, independently, working just fine and accessing their respective databases without issue.

Customer really needs to have the HW/SW import work so that there are items to manage through the product.

Best regards -

Bruce McDowell Technical Services Consultant, McDowell Consulting LLC bruce@consultbruce.com
0 Likes
2 Replies
Anonymous_User Absent Member.
Absent Member.

Re: ZCM Data Import with NSD 7.1 Not Working

BMcDowell,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://www.novell.com/support and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Forums Team
http://forums.novell.com


0 Likes
padharsh1 Absent Member.
Absent Member.

Re: ZCM Data Import with NSD 7.1 Not Working

The below doc has details on importing(AMIE) from ZENworks and NSD 7.1. On which step are you seeing the problem
https://www.novell.com/documentation/servicedesk71/help71/Administrator/importing_items_using_zenamie.htm
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.