Difference between revisions of "Fixing system tables in the master database after a change of Characterset / SortOrder"
m (→Fixing system tables in the master database after a change of Characterset/SortOrder) |
m (→Fixing system tables in the master database after a change of Characterset/SortOrder) |
||
Line 4: | Line 4: | ||
====Fixing system tables in the master database after a change of Characterset/SortOrder==== | ====Fixing system tables in the master database after a change of Characterset/SortOrder==== | ||
− | When you have changed the characterset and/or sort order for a server it might be necesarry to fix a few system tables in the master database. When you have not done this, a stacktrace similiar to this one will be shown in the errorlog. | + | When you have changed the characterset and/or sort order for a server it might be necesarry to fix a few system tables in the master database. When you have not done this, a stacktrace similiar to this one will be shown in the errorlog. Running "update index statistics" on tables in the master database seem to raise this stacktrace. |
{| border="1" | {| border="1" | ||
Line 125: | Line 125: | ||
Msg 7952, Level 16, State 1: | Msg 7952, Level 16, State 1: | ||
|- | |- | ||
− | |Server ' | + | |Server 'xxx', Line 1: |
|- | |- | ||
|A TEXT value with an invalid MAGIC NUMBER has been found on page 2370. TEXT values will no longer be checked for this table. Note because of this, the TEXT page count will be inaccurate. Use DBCC FIX_TEXT to fix the TEXT values. | |A TEXT value with an invalid MAGIC NUMBER has been found on page 2370. TEXT values will no longer be checked for this table. Note because of this, the TEXT page count will be inaccurate. Use DBCC FIX_TEXT to fix the TEXT values. | ||
Line 133: | Line 133: | ||
you need to run this: dbcc fix_text(spt_jtext) | you need to run this: dbcc fix_text(spt_jtext) | ||
+ | All these dbcc commands can be run while users are active in the server. | ||
Currently it is not known what ASE versions, character set or sort orders causes these problems. | Currently it is not known what ASE versions, character set or sort orders causes these problems. |
Revision as of 21:00, 11 March 2006
Things about Adaptive Server Enterprise
Administration
Fixing system tables in the master database after a change of Characterset/SortOrder
When you have changed the characterset and/or sort order for a server it might be necesarry to fix a few system tables in the master database. When you have not done this, a stacktrace similiar to this one will be shown in the errorlog. Running "update index statistics" on tables in the master database seem to raise this stacktrace.
|
To resolve this issue you to run the following commands in the master database:
dbcc reindex(spt_ijdbc_mda)
dbcc reindex(spt_mda)
dbcc reindex(spt_jtext)
When you reindex spt_jext and the following error is raised:
|
you need to run this: dbcc fix_text(spt_jtext)
All these dbcc commands can be run while users are active in the server. Currently it is not known what ASE versions, character set or sort orders causes these problems.