I would just like to know how DB is updated in a Global project from HUB to SAT?
Is it updating only the Changes made in HUB and update it in the DB file in SAT?
or
Does it COPY the whole DBfile from HUB then replace the one in the SAT side.
this is because our setting for global connection is just 1 hour for 3 times a day, and I have a 2.5gb DB that is not getting updated in the SAT. Although the date modified of the DBfile in SAT side updates, the size doesn't.
it was only resolved when I Issued a manual UPDATE ALL WITH SAT and made global connection run longer.
It updates changes (sessions) only.
If it doesn't update (for any reason), sessions stay in a queue waiting for the next time.
Try increasing the connection time or the band width.
[QUOTE=corrado;105979]It updates changes (sessions) only.
If it doesn't update (for any reason), sessions stay in a queue waiting for the next time.
Try increasing the connection time or the band width.
Thanks for the information Corrado, that's very useful.
I will do your 1st suggestion as it is easier and doesn't have additional cost.
To enable you to monitor the progress of Global commands, Global stores details of issued commands in a transaction database. Transaction messages are generated in the database each time the progress of the command changes. Global provides a facility that enables you to view these transaction messages, and, if necessary, cancel commands that have not been carried out yet.
because if the change is minute like changing Description of a SDTE then it would not probably affect the DB file size, I assume.
The system stores in the database also the difference between two consecutive sessions.
[QUOTE=corrado;105979]It updates changes (sessions) only.
If it doesn't update (for any reason), sessions stay in a queue waiting for the next time.
Try increasing the connection time or the band width.
Hi Corrado,
I have a follow-up question of some sort.
Is there a sure way which I can check if a DB was successfully updated to the SAT? like from a log file or attribute?
because if the change is minute like changing Description of a SDTE then it would not probably affect the DB file size, I assume.
Yes I know of the transactions, I check those as well.
But for my case above, transaction says complete but in reality the DBfile size was incosistent between HUB and SAT. So that's why I was hoping for somekind of special checking that can be done in Admin side or via PML in order to check if everything is updated.
[QUOTE=corrado;105998]
The system stores in the database also the difference between two consecutive sessions.
can you elaborate on this part how I can check this difference? do you mean to say I have to check the last session in the SAT side and compare it with the last session in the HUB for that particular DB?
Let's say you have an empty design DB. You create a pump. Then savework. You delete the pump. Then savework. And again and again for one year. at the end of the year you delete the pump. You think the database is empty, don't you? But this is not true. The systems remembers what you have done during the last year.
Anyway....at the end of the syncronisation, session number should be identical both at SAT and HUB
[QUOTE=corrado;106006]Let's say you have an empty design DB. You create a pump. Then savework. You delete the pump. Then savework. And again and again for one year. at the end of the year you delete the pump. You think the database is empty, don't you? But this is not true. The systems remembers what you have done during the last year.
Anyway....at the end of the syncronisation, session number should be identical both at SAT and HUB
Yes, thank you for the explanation. I know of the individual sessions as that is the one used if we do backtrack changes to either retrieve deleted models or do some checking of some sort.
so basically, what I can do from my end here is I can make a macro the will produce a Log file of all the last session details of each DB and have it run in both HUB and SAT then compare?
Again, thanks for the info. I will move forward with this course of action.
