Home › Forums › Persistence › Dump Files › Export to dump fails if selecting * as Data source
Tagged: Dump export
- This topic has 4 replies, 2 voices, and was last updated 5 years ago by shahzad.qureshi.
-
AuthorPosts
-
-
December 17, 2019 at 1:36 am #12483Zaccak SolutionsParticipant
Everytime I try to export a SQL DB to a dump file I get this error if I select * in Data source:
; 01:31:38,664 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment DefaultRelationalDatabase.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:38,836 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment dm:import:StagingImportDatabase.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:38,867 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment BI_1_BI_Database.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:38,883 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment portal:Portal.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:38,977 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment rules:Rules.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:39,039 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment StagingDatabase.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:39,367 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment bp:CPM.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:39,388 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment flow:Flow.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:39,463 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment ObjectQueueDatabase.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:39,775 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment LockDatabase.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:39,932 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment ecr:ECR.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:43,135 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment Conversation.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:43,309 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment call:Call.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:43,730 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment sso:SSO.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:43,902 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment AuditLogDatabase.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:44,012 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment msg:Messaging.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)
; 01:31:44,262 INFO [RelationalDatabaseConnectionPool] RelationalDatabaseFragment StatDatabase.[default]: Microsoft SQL Server 11.00.7001 (jTDS Type 4 JDBC Driver for MS SQL Server and Sybase 1.2.2)Error: Invalid query. Must do file lookup by equating name field to string, or a class to an OID. (err.persistence.file.query)
; 01:31:44,606 ERROR [GenericTool] Error executing the tool command
nexj.core.persistence.InvalidQueryException: Invalid query. Must do file lookup by equating name field to string, or a class to an OID. (err.persistence.file.query)
at nexj.core.persistence.file.FileAdapter.read(FileAdapter.java:310)
at nexj.core.persistence.Query.read(Query.java:6228)
at nexj.core.admin.etl.DataLoader.read(DataLoader.java:571)
at nexj.core.admin.etl.DataLoader.exportData(DataLoader.java:761)
at nexj.core.admin.etl.DataLoader.exportData(DataLoader.java:893)
at nexj.core.admin.etl.DataLoadManager$1.export(DataLoadManager.java:553)
at nexj.core.admin.etl.DataLoadManager.exportData(DataLoadManager.java:574)
at nexj.core.admin.etl.DataLoadManager.exportData(DataLoadManager.java:549)
at nexj.core.tools.DataLoadTool.exportData(DataLoadTool.java:460)
at nexj.core.tools.DataLoadTool.execute(DataLoadTool.java:109)
at nexj.core.tools.GenericTool.run(GenericTool.java:127)
at nexj.core.tools.DataLoadTool.main(DataLoadTool.java:623)
; 01:31:44,843 INFO [GenericTool] Exit code = 20 -
December 17, 2019 at 1:38 am #12492Zaccak SolutionsParticipant
A side note, Select * for recreate does work.
0 -
December 17, 2019 at 1:14 pm #12511shahzad.qureshiKeymaster
As the other thread I responded to, why are you exporting to a dump file? Dump files were deprecated in Finance 8.2 I believe (or around that time which is nearly 3-4 years ago) and eventually completely removed.
0 -
December 17, 2019 at 1:55 pm #12529Zaccak SolutionsParticipant
They seem to still be part of our 9.2 release.
0-
December 17, 2019 at 4:38 pm #12559shahzad.qureshiKeymaster
Please see my reply to your other question at https://community.nexj.com/discussion/Question/dump-file-upgrades-always-fail-in-9-2/#post-12549
The ability to use dump is expected to be removed from Studio so it is better to not use them at all. Our training documentation will also be updated to reflect the deprecation of dumps.
0
-
-
-
AuthorPosts
- You must be logged in to reply to this topic.