Skip to Content
It is currently September 25th, 2022, 9:06 pm

All times are UTC - 6 hours [ DST ]




Post new topic Reply to topic  [ 3 posts ] 
Author Message
PostPosted: August 13th, 2022, 1:39 pm 
Offline
New User
New User

Joined: February 22nd, 2019, 1:20 pm
Posts: 24
Hi Folks,
I have issues with SAM PRO 2018.1 and 2019.1 versions - both with Firebird 2.5.2 databases. Both SAM versions are placed on two different PCs (with different Operating systems) as one is the major streaming equipment, the other one is backup. The first issue was noticed as the total tracks duration in SAM exceeded 50 days in total - resulting in displaying from 49 days + few hours + minutes TO 0 days + few hours + few minutes. I have contacted Spacial support and they told me to repair the database. I have not repaired it, as I did not notice any abnormal operational behaviour. At that time I have set up my new backup PC and after complete new and first installation of SAM PRO with its integrated Firebird database I noticed the same effect as on my regular streaming PC - displaying the same wrong total track duration. Now I have reached in total 100 days track duration and both PCs showed again a track duration fallback to 0 days + few hours & minutes.
So my questions are: Did someone notice this effect as well and if yes
- Does it have any influence on operational service ?
- Are there any side effects ?
- Future risks ?
- Is this a database error or a bug from SAM PRO ?

Folks, your feedback is appreciated ! Thanks !


Attachments:
tracks duration.jpg
tracks duration.jpg [ 77.82 KiB | Viewed 367 times ]
Top
 Profile  
Reply with quote  
PostPosted: August 24th, 2022, 4:33 pm 
Offline
Junior User
Junior User

Joined: April 27th, 2020, 6:15 pm
Posts: 40
Any particular reason you are using firebird? try switching to mariaDB.


Top
 Profile  
Reply with quote  
PostPosted: August 25th, 2022, 11:43 am 
Offline
New User
New User

Joined: February 22nd, 2019, 1:20 pm
Posts: 24
I am using Firebird DBs on different devices without any problems since 2013. I follow the "Never change a running system" procedure. Up to now I did not notice any negative impact for current operation - despite wrong displayed total track duration. I do not see any reason to make a DB change to due a "Cosmetic" failure.


Top
 Profile  
Reply with quote  
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 

All times are UTC - 6 hours [ DST ]


Who is online

Users browsing this forum: Bing [Bot], Majestic-12 [Bot] and 8 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group