<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Sybase数据库技术，数据库恢复专家 &#187; 时间戳</title>
	<atom:link href="http://www.dbainfo.net/tag/%e6%97%b6%e9%97%b4%e6%88%b3/feed" rel="self" type="application/rss+xml" />
	<link>https://www.dbainfo.net</link>
	<description>提供Sybase ASE及Sybase SQL Anywhere数据库修复服务，电话：13811580958(微信)，QQ：289965371！We have many years of experience in recovering data from damanged Sybase devices. Contact us by Phone: +86 13811580958 Wechat: 13811580958 Email: 289965371@qq.com</description>
	<lastBuildDate>Sat, 14 Jun 2025 16:28:02 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>sybase启动报master时间戳不一致的问题</title>
		<link>https://www.dbainfo.net/maser-db-timestamp-inconsistent.htm</link>
		<comments>https://www.dbainfo.net/maser-db-timestamp-inconsistent.htm#comments</comments>
		<pubDate>Mon, 14 Dec 2009 09:33:24 +0000</pubDate>
		<dc:creator>dbainfo</dc:creator>
				<category><![CDATA[Sybase ASE]]></category>
		<category><![CDATA[时间戳]]></category>

		<guid isPermaLink="false">http://www.dbainfo.net/?p=103</guid>
		<description><![CDATA[当master设备文件正在被二进制编辑器修改时，数据库服务器不能正确读取文件报错： 00:00000:00000:2009/12/14 17:21:11.79 kernel  dopen: open 'D:\sybase\data\master.dat', No error 错误日志中仅仅有这么一条（ase15.0.3esd2#）. 每次启动的时候老是报00:00000:00011:2009/12/14 17:26:02.50 server  Error: 12315, Severity: 21, State: 1 00:00000:00011:2009/12/14 17:26:02.50 server  Corrupt page, Internal error: Mismatch between tail timestamp '0b7b' and the low two bytes of timestamp in the page header 'c9d3' while accessing page '2291' of object '3' in database '1'. Please contact [...]]]></description>
			<content:encoded><![CDATA[<p>当master设备文件正在被二进制编辑器修改时，数据库服务器不能正确读取文件报错：</p>
<p>00:00000:00000:2009/12/14 17:21:11.79 kernel  dopen: open 'D:\sybase\data\master.dat', No error</p>
<p>错误日志中仅仅有这么一条（ase15.0.3esd2#）.</p>
<p>每次启动的时候老是报00:00000:00011:2009/12/14 17:26:02.50 server  Error: 12315, Severity: 21, State: 1<br />
00:00000:00011:2009/12/14 17:26:02.50 server  Corrupt page, Internal error: Mismatch between tail timestamp '0b7b' and the low two bytes of timestamp in the page header 'c9d3' while accessing page '2291' of object '3' in database '1'. Please contact Sybase Technical Support.类似的错误，一个一个的修改很麻烦。</p>
<p>启动时打开flag=3607，所有数据库均处于bypass mode。这是截断master的日志报错</p>
<p>1&gt; dump tran master with no_log<br />
2&gt; go<br />
Msg 4237, Level 16, State 1:<br />
Line 1:<br />
Cannot dump master database's log as distributed transaction resolution is not complete ye<br />
t. Please retry later.<br />
1&gt; dump tran master with truncate_only<br />
2&gt; go<br />
Msg 4237, Level 16, State 1:<br />
Line 1:<br />
Cannot dump master database's log as distributed transaction resolution is not complete ye<br />
t. Please retry later.</p>
<p>即使对master数据库进行全备也不能截断日志。</p>
<p>dbcc checkdb(master),dbcc checktable(sysobjects),dbcc checktable(syslogs)等等之后。重启sybase就能够正常启动了。</p>
<p>————————————————————————————————————<br />
——— 本文为andkylee个人原创，请在尊重作者劳动成果的前提下进行转载；<br />
——— 转载务必注明原始出处 : <a href="http://www.dbainfo.net">http://www.dbainfo.net</a><br />
——— 关键字： ASE 15.0.3 时间戳 二进制  修复 master 设备文件<br />
————————————————————————————————————
<div style="clear: both; margin: 10px 0pt; border: 1px dashed rgb(153, 153, 153); font-size: 12px; padding: 5px 10px;">
<li>本文链接地址：<a href="https://www.dbainfo.net/maser-db-timestamp-inconsistent.htm">https://www.dbainfo.net/maser-db-timestamp-inconsistent.htm</a>；</li>
<li>本文为dbainfo个人原创，请在尊重作者劳动成果的前提下进行转载；</li>
<li>转载务必注明原始出处 : <a href="https://www.dbainfo.net/">Sybase数据库技术，数据库恢复专家</a>；</li>
<li>对《<a href="https://www.dbainfo.net/maser-db-timestamp-inconsistent.htm">sybase启动报master时间戳不一致的问题</a>》有何疑问或见解，请在本文下方发表；</li>
<li>对网站还有其他问题或建议，请提交在<a href="https://www.dbainfo.net/messages" target="_blank">留言板</a>，谢谢！</li>
</div>
<h2  class="related_post_title">随机日志</h2><ul class="related_post"><li>2015-03-08 -- <a href="https://www.dbainfo.net/sap-asa-cr-number-8.htm" title="SAP SQL Anywhere的所有已知BUG列表（8）">SAP SQL Anywhere的所有已知BUG列表（8）</a> (0)</li><li>2010-02-24 -- <a href="https://www.dbainfo.net/sql-server-2005-table_partitions.htm" title="SQL server 2005基于已存在的表创建分区[转]">SQL server 2005基于已存在的表创建分区[转]</a> (0)</li><li>2015-03-08 -- <a href="https://www.dbainfo.net/sap-ase-cr-number-7.htm" title="SAP Adaptive Server Enterprise的所有已知BUG列表（7）">SAP Adaptive Server Enterprise的所有已知BUG列表（7）</a> (0)</li><li>2009-11-18 -- <a href="https://www.dbainfo.net/sybase-ase-recovery-tool.htm" title="Sybase Adaptive Server Enterprise(ASE)数据库恢复工具">Sybase Adaptive Server Enterprise(ASE)数据库恢复工具</a> (2)</li><li>2014-12-20 -- <a href="https://www.dbainfo.net/asa_certifications.htm" title="Sybase SQL Anywhere各版本认证情况">Sybase SQL Anywhere各版本认证情况</a> (0)</li><li>2015-01-16 -- <a href="https://www.dbainfo.net/one-way-to-recover-master-configuration-area.htm" title="master数据库配置区域(configuration area)损坏的一种修复方法">master数据库配置区域(configuration area)损坏的一种修复方法</a> (1)</li><li>2011-09-21 -- <a href="https://www.dbainfo.net/pad.htm" title="便笺">便笺</a> (10)</li><li>2010-04-09 -- <a href="https://www.dbainfo.net/sybase1503-cross-platform-recovery.htm" title="Sybase15.0.3跨平台恢复过程">Sybase15.0.3跨平台恢复过程</a> (0)</li><li>2010-05-13 -- <a href="https://www.dbainfo.net/sybase-auquired-by-sap.htm" title="sybase 公司将被SAP收购，看重的是ASA这项移动数据库技术">sybase 公司将被SAP收购，看重的是ASA这项移动数据库技术</a> (0)</li><li>2010-05-12 -- <a href="https://www.dbainfo.net/tar-package-reached-end-of-file-before-expected.htm" title="tar打包时报错：Reached end-of-file before expected的解决方法">tar打包时报错：Reached end-of-file before expected的解决方法</a> (0)</li></ul>]]></content:encoded>
			<wfw:commentRss>https://www.dbainfo.net/maser-db-timestamp-inconsistent.htm/feed</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
