>>Are you trying to do a segmented backup?
How big is your database?<<
Any answers to these questions? As you know, segmented processing has been discontinued for SB12.
That is truly bizarre.
>>we try to launch a Query the results is that the db crash and the table involved in our query Table is corrupted.<<
1. If there are no queries done, does the backup snapshot work?
2. What error do you get from the query that indicates that the table is corrupted?
3. Do you get that error and then the SQLBase server *engine* crashes, i.e. the whole SQLBase engine stops, not just the one database?
Can you try turning logbackup on for the database and doing a 'backup database', the 'release log' and 'backup logs'? Does that produce the same crash? If you are only doing backup snapshots, you are at great risk of losing data. See a whitepaper on setting up correct backup/recovery procedures so you have maximum recovery options.
http://support.guptatechnologies.com/su ... ite_Papers
Grab the second paper under the Previouos Versions' heading.
What we *really* need is a reproducible testcase. If we can reproduce it, we can fix it!
no, we are trying to create a normal snapshot backup, we also tried to create a segmented backup but without success.
1. Without Queries the snapshot work
2. If we launch a query during the backup DataBase we receive an error that say that the index in the table involved is corrupted. (Error 850, row LRP check Failure, DataPage corrupted).
We launch a Backup with logbackup on. Same problem.
We have a Dump of the crash (*****972.dmp is with segmentation, the other one is without segmentation) , is here attached.
Here are my findings.
1. I created a 5.0 GB database with two tables, each having 5 million rows, connecting with TCP/IP.
2. Tried various settings in the sql.ini file
a. cache=64000 to cache=512000
b. readonly=0 with RL or RR isolation levels in SQLTalk
c. readonly=1 with RC3 isolation level in SQLTalk
3. Tried different forms of backups
a. Backup snapshot (on server and on client) with the ‘from dbname’ option
b. Connect to database and backup snapshot without the ‘from dbname’ option
c. Backup database, release logs, backup logs
Regardless of all these variations, I could produce a hang of a SQLTalk session (but not a crash). Here are the statements:
SQLTalk session 1:
set server sb1232;
backup snapshot from sb12test to c:\backups on server;
SQLTalk session 2:
select * from systables;
select count(*) from caps_detail;
The select * from systables works fine, but the select count(*) hangs. The first session reports ‘Snapshot Backed Up’ and I can drop that session, but the second session runs forever with 100% CPU.
BTW, I had to be quick to get to the second session. The backup snapshot of a 5GB database only takes around 40 seconds.
I have given all this information to Development and they will be able to reproduce it, I am sure. If they can reproduce it, they can fix it!!
I will keep you all posted on our findings and when we get a fix I will make it available to you.
I think I have a similar problem. The last 2 days database crashed at the same time as the backup should started. Fail.sql is enclosed. Today in the morning Command Center shows the status of the backup (snapshot) job as "executing", but no action. Only the BKP-file was copied, no log-file. So I have no current backup to check if the database is corrupted because I can't force the users to logout. I will try to get a copy from database today at lunchtime but as I read the forum threads I assume that the problem is not a corrupted database.
Thanks in advance
[SQLB-2461] - Executing a BACKUP SNAPSHOT causes crash/hang/corruption.
Who is online
Users browsing this forum: [Ccbot] and 0 guests