×
Discuss on any other topics
rdbmsConversion - Distributed Files
- RG
- Topic Author
- Offline
- New Member
-
Less
More
- Posts: 1
- Thank you received: 0
9 months 3 weeks ago - 9 months 3 weeks ago #24371
by RG
rdbmsConversion - Distributed Files was created by RG
We are migrating our jBase database from AIX to MSSQL Windows. Release R15 TAFC. We are encountering an issue with Distributed Files.
The parameters we set when launching the rdbmsConversion are as follows:
Enter database <XMLMSSQL/XMLDB2/XMLMSSQL> <default=J4> :XMLMSSQL
Enter number of agents to use for process <default=2> :3
Convert file data in ../bnk.data <Y/N> <default=Y> :Y
Convert dict data in ../bnk.dict <Y/N> <default=Y> :Y
Convert jnl/help/arc files <Y/N> <default=Y> :N
Generate Batches for Distributed Files <Y/N> <default=N> :N
Convert stub files to voc table entries <Y/N> <default=N> :Y
Options selected, Continue to scan phase Y/N <default=Y> :Y
Regardless of the setting for the "Generate Batches for Distributed Files" parameter, whether we set it to Y or N, distributed files are still created, but they end up in different tables: F_TABLE_NAME_n.
The question is how should we merge these tables F_TABLE_NAME_n into one main table F_TABLE_NAME? And how does the "Generate Batches for Distributed Files" parameter work?
The parameters we set when launching the rdbmsConversion are as follows:
Enter database <XMLMSSQL/XMLDB2/XMLMSSQL> <default=J4> :XMLMSSQL
Enter number of agents to use for process <default=2> :3
Convert file data in ../bnk.data <Y/N> <default=Y> :Y
Convert dict data in ../bnk.dict <Y/N> <default=Y> :Y
Convert jnl/help/arc files <Y/N> <default=Y> :N
Generate Batches for Distributed Files <Y/N> <default=N> :N
Convert stub files to voc table entries <Y/N> <default=N> :Y
Options selected, Continue to scan phase Y/N <default=Y> :Y
Regardless of the setting for the "Generate Batches for Distributed Files" parameter, whether we set it to Y or N, distributed files are still created, but they end up in different tables: F_TABLE_NAME_n.
The question is how should we merge these tables F_TABLE_NAME_n into one main table F_TABLE_NAME? And how does the "Generate Batches for Distributed Files" parameter work?
Last edit: 9 months 3 weeks ago by RG.
Please Log in or Create an account to join the conversation.
- VK
-
- Offline
- Platinum Member
-
- Globus:G9-G13|TAFC:R05-R23|TAFJ:R19,R23,R24:test
Less
More
- Posts: 1182
- Thank you received: 157
9 months 3 weeks ago #24372
by VK
Cheers
VK
Replied by VK on topic rdbmsConversion - Distributed Files
Hi
quoting Temenos info:
About "distributed files are still created, but they end up in different tables: F_TABLE_NAME_n": in my case it didn't happen. For example, I had F.DE.O.HANDOFF distributed and it ended up in dbo.F_DE_O_HANDOFF table. I used "Y" for "Generate Batches for Distributed Files".
quoting Temenos info:
Due to the potential for Distributed files to contain millions of items, this option provides the ability to process items from part files in batches of 1,000 ( by default ) items
Basically the RDBMSConversion will create files, containing lists of items, from the Distributed file, if 'Generate Batches for Distributed Files' is selected
The items containing the list of item ids are created in the 'rdbmsConversion/BATCH_' file
'rdbmsBatch' isn't actually doing any 'converting' at this pointAbout "distributed files are still created, but they end up in different tables: F_TABLE_NAME_n": in my case it didn't happen. For example, I had F.DE.O.HANDOFF distributed and it ended up in dbo.F_DE_O_HANDOFF table. I used "Y" for "Generate Batches for Distributed Files".
Cheers
VK
Please Log in or Create an account to join the conversation.
Time to create page: 0.079 seconds