V
Valeriy Bashkatov
Guest
Hi Bryan, Thank you for your reply! >>Theoretically, you could edit copies of the bulk copy code and use different date ranges if you have one on an index or use other options with other data. Yes, we do this for some tables, but unfortunately not for all tables this is possible. In addition, the tables are so big that even dividing the download by years, it's still too slow, since the DataServer makes a commit after loading each record into Oracle. I also tried to use ASCII Load but did not succeed for Oracle (See more at: ) >>If you want to use split threading for normal replication and need to start multiple replbatch processes, you need to add more replcontrol records, one for each split e.g. 1-2, 1-3. Basically, we add an input from the batch file with the split number to match the new replcontrol record and a mod number. We then add code to replproc to check the sequence number against the mod to see which records to process. Could you describe this, please, in more detail how to implement it? I created a record in replcontrol as follows: CREATE ReplControl. ASSIGN ReplControl.GroupID = "PROCESS" ReplControl.CodeID = "REPLICATION" ReplControl.CodeVal1 = "1-2" ReplControl.CodeVal2 = "0" ReplControl.CodeVal3 = "0". CREATE ReplControl. ASSIGN ReplControl.GroupID = "CONTROL" ReplControl.CodeID = "REPLICATION" ReplControl.CodeVal1 = "1-2" ReplControl.CodeVal2 = "0" ReplControl.CodeVal3 = "1". CREATE ReplControl. ASSIGN ReplControl.GroupID = "LOGGING" ReplControl.CodeID = "LEVEL" ReplControl.CodeVal1 = "REPLICATION" ReplControl.CodeVal2 = "1-2" ReplControl.CodeVal3 = "2". CREATE ReplControl. ASSIGN ReplControl.GroupID = "QUEUE" ReplControl.CodeID = "DISPOSITION" ReplControl.CodeVal1 = "REPLICATION" ReplControl.CodeVal2 = "1-2" ReplControl.CodeVal3 = "D". But it does not work ( When I start "replBatch.sh 1-2" where run this command: $DLC/bin/mbpro -pf $PRO2PATH/bprepl/scripts/replProc.pf -p bprepl/RunReplProc.p -param "Thread="$1 >> $LOG I get error int the $LOG file: ** Invalid character in numeric input 2. (76) The same error appears in Pro2SQL Administration Utility also What did I do wrong? Regards, Valeriy
Continue reading...
Continue reading...