on 08-20-2014 6:22 PM
Hi Gurus,
We have a problem when we try to connect to a SyBase DB (Adaptive Server Enterprise/15.7.0/EBF 20953 SMP ESD#4.2), the database is in suspect mode.
We ran the following commands after rebooting but the same error appears:
server>isql -X -Usapsso -S<SID> -w2000 -P<pass>
1> sp_configure "allow updates", 1
2> go
Parameter Name Default Memory Used Config Value Run Value Unit Type
------------------------------ ----------- ----------- ------------ ------------ -------------------- --------------------
allow updates to system tables 0 0 1 1 switch dynamic
(1 row affected)
Resulting configuration value and memory use have not changed from previous values: new configuration value 1, previous value 1.
(return status = 0)
1> quit
server> isql -X -Usapsa -S<SID> -w2000 -P<pass>
1> use master
2> go
1> begin transaction
2> go
1> update sysdatabases
2> set status = status & ~256
3> where name="<SID>"
4> go
(1 row affected)
1> quit
server> isql -X -Usapsso -S<SID> -w2000 -P<pass>
1> commit transaction
2> go
1> sp_configure "allow updates", 0
2> go
Parameter Name Default Memory Used Config Value Run Value Unit Type
------------------------------ ----------- ----------- ------------ ------------ -------------------- --------------------
allow updates to system tables 0 0 0 0 switch dynamic
(1 row affected)
Configuration option changed. ASE need not be rebooted since the option is dynamic.
Changing the value of 'allow updates to system tables' does not increase the amount of memory Adaptive Server uses.
(return status = 0)
1>quit
server> isql -X -Usapsa -S<SID> -w2000 -P<pass>
1> checkpoint
2> go
1> shutdown
2> go
This is the result of executing the following query.
1> select dbid, name, status, status2, status3, status4 from sysdatabases
2> go
dbid name status status2 status3 status4
------ ------------------------------ ------ ------- ----------- -----------
1 master 0 -32768 131072 16384
3 model 0 -32768 131072 16384
2 tempdb 8716 -32767 131072 540672
31513 sybsystemdb 0 -32768 131072 16384
31514 sybsystemprocs 8 -32768 131072 16384
31515 sybmgmtdb 12 -32768 131072 16384
4 <SID> 9024 49 131200 21544960
5 saptools 8712 1 131072 540672
6 saptempdb 8716 -32767 131328 540672
Could you help me to change this status, please?
Best Regards,
Dani
Hello,
1.load database SID with listonly = 'CREATE_SQL'
2.you drop database
then create database in 1 . script
then try to load database
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello,
first of all you are using ASE 15.7 SP42, I would suggest to use the latest ASE version.
The Error 3474 is reported cause the recovery cannot proceed, since the timestamp is out of sync.
The reason for this, is probably an old issue. Could you check your errorlogs and see if other errors are reported for page 1447848 in dbid 4.
Could be that you hit CR 740613, see SAP Note 1868675 for details, check the prerequisites if they fit for your problem.
Another candidate could be CR 747648, see SAP Note 2040685 for details.
To be sure what happened, you need to check what was done before you hit the first time this error.
If you need further help, just let us know.
Regards
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank for your help, Stefan.
Finally we have chosen to restore the database to a previous backup, but when executing the following command:
1> use master
2> go
1> load database <SID> from '/backup_directory/backup'
2> go
We get the following result:
Msg 926, Level 14, State 2:
Server '<SID>', Line 1:
Database '<SID>' cannot be opened. An earlier attempt at recovery marked it 'suspect'. Check the ASE errorlog for information as to the cause.
Any idea?
Hello,
the errorlog starts at 00:0000:00000:00000:2014/08/20 18:30:28.17 shortly before the recovery, where the database recovery failed.
The suspect error just means there was an earlier error, that marked the database suspect. Check the logs before the first Error 926 to see what happened.
With kind regards
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
After several attempts we have removed the suspect status but when restart the following appears:
Database '<SID>', checkpoint=(1645024, 14), first=(155850, 0), last=(1648828, 149).
Completed estimating recovery log boundaries for database '<SID>'.
Started ANALYSIS pass for database '<SID>'.
Completed ANALYSIS pass for database '<SID>'.
Log contains all committed transactions until 2014/08/19 12:14:39.13 for database <SID>.
Started REDO pass for database '<SID>'. The total number of log records to process is 2584914.
Redo pass for database '<SID>': 129245 records done (4%); 2455669 records left.
Redo pass for database '<SID>': 258490 records done (9%); 2326424 records left.
Redo pass for database '<SID>': 387735 records done (14%); 2197179 records left.
Redo pass for database '<SID>': 516980 records done (19%); 2067934 records left.
Redo pass for database '<SID>': 646225 records done (24%); 1938689 records left.
Redo pass for database '<SID>': 775470 records done (29%); 1809444 records left.
Redo pass for database '<SID>': 904715 records done (34%); 1680199 records left.
Redo pass for database '<SID>': 1033960 records done (39%); 1550954 records left.
Redo pass for database '<SID>': 1163205 records done (44%); 1421709 records left.
Redo pass for database '<SID>': 1292450 records done (49%); 1292464 records left.
Redo pass for database '<SID>': 1421695 records done (54%); 1163219 records left.
Redo pass for database '<SID>': 1550940 records done (59%); 1033974 records left.
Error: 3474, Severity: 21, State: 1
During redo the page timestamp value is less than old timestamp from log. Page #=1447848, object id = 1208908893, page timestamp=0000 09dcde72. Log old timestamp=0000 0a24137c. Log record marker = (1645024, 0).
Database '<SID>' (dbid 4): Recovery failed. Check the ASE errorlog for further information as to the cause.
Recovery has restored the value of 'local async prefetch limit' for '128K' pool in 'default data cache' from '80' to 'DEFAULT'.
Recovery has restored the value of 'local async prefetch limit' for '16K' pool in 'default data cache' from '80' to 'DEFAULT'.
Recovery has restored the original size for '128K' pool and '16K' pool in 'default data cache'.
Recovery complete.
(Attached the complete log file)
Best Regards and thank you for your help.
It does look like you did the correct steps to clear the suspect flag.
When you rebooted the server and recovery got to the <sid> database,
did it just say <sid> was already suspect, or did recovery report a serious
error and re-mark <sid> suspect?. If the later, please post the details
of the error.
-bret
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Bret,
In the file <SID>.log it says this:
Error: 926, Severity: 14, State: 1
Database '<SID>' cannot be opened. An earlier attempt at recovery marked it 'suspect'. Check the ASE errorlog for information as to the cause.
Unable to proceed with the recovery of dbid <4> because of previous errors.
(Attached the log file.)
After that... the process continues recovering the other databases with no problem.
Thank you for your help.
HI Bret Halford,
I discussed with in facebook for the same error,
please provide the solution steps urgent
Adaptive Server Enterprise/15.7.0/
: 12314, Severity: 21, State: 2
00:0013:00000:00071:2014/12/18 16:39:23.92 server Bad child page pointer found on page 518688 of index with id 2 of table 'SNAP' in database 'PP1'.
Expected child page pointer to be 0 but found 1902263. Check if the index is consistant using DBCC.
00:0013:00000:00136:2014/12/18 16:40:23.13 server Error: 12308, Severity: 21, State: 7
00:0013:00000:00136:2014/12/18 16:40:23.13 server Internal error : Invalid row id (Row 3, Page 150433) encountered in the table 'BTCCTL' in database 'PP1'.
le 'SNAP' in database 'PP1'. Expected child page pointer to be 0 but found 1902263. Check if the index is consistant using DBCC.
Your question does not appear to have anything to do with this discussion. Please start your own new discussion for this issue.
For SAP applications, I'd expect you to be using an account named "sapsa" rather than "sa". If your ASE isn't for running SAP applications, please post your discussion in http://scn.sap.com/community/ase-custom-applications
Please also be specific on what you mean by "it is not working". Does ASE not seem to be generating a new password? Are you unable to login with that password? What ASE version are you using?
User | Count |
---|---|
88 | |
23 | |
11 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.