Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

dbcc question

204 views
Skip to first unread message

hiro

unread,
Dec 31, 2009, 11:51:39 PM12/31/09
to
Dear ASE guru.

I'm trying to test dbcc and I don't understand what is this probelm.

* probelm

The following problem occurred. could you tell me how to solve it??

When I execute sp_configure 'number of worker processes',50
It work fine. but I don't understand. this value is proper or not.

SQL> dbcc checkstorage(dbcc_test)

Checking dbcc_test: Logical pagesize is 4096 bytes
Msg 9961, Level 17, State 6:
Server 'ELEPHANT', Line 1:
DBCC failed to connect to the requested number of worker processes.
The number
of workers configured is insufficient, or the number of workers
exceeds 128. Use
sp_dbcc_updateconfig to reduce 'max worker processes' for this
database.
Msg 9960, Level 20, State 1:
Server 'ELEPHANT', Line 1:
A non-recoverable error has occurred in the CHECKSTORAGE operation.
The
operation has been aborted.
Msg 9970, Level 20, State 1:
Server 'ELEPHANT', Line 1:
DBCC cannot update the finish time in dbcc_operation_log table for
this
operation(opid = '28') of database 'dbcc_test'. This can be patched
by executing
sp_dbcc_patch_finishtime.
DBCC CHECKSTORAGE for database 'dbcc_test' encountered an error. Some
results
may not be available. Correct the problems reported and reexecute the
CHECKSTORAGE command.


* Environment

Adaptive Server Enterprise/15.0.3/EBF 16743 ESD#2/P/Linux Intel/Linux
2.6.9-42.
ELsmp i686/ase1503/2707/32-bit/FBO/Sun Jul 26 23:03:48
2009

1> sp_configure 'max memory'
2> go
Parameter Name Default Memory Used
Config Value Run Value
Unit
Type
------------------------------ -------------------- -----------
-------------------- --------------------
--------------------
----------
max memory 49152 2831152
1415576 1415576 memory pages
(2k)
dynamic
(return status = 0)

1> sp_configure 'worker'
2> go
Msg 17411, Level 16, State 1:
Server 'ELEPHANT', Procedure 'sp_configure', Line 322:
Configuration option is not unique.

Parameter Name Default Memory Used
Config Value Run Value
Unit
Type
------------------------------ -------------------- -----------
-------------------- --------------------
--------------------
----------
memory per worker process 1024 4
1024 1024
bytes
dynamic
number of worker processes 0 0
0 0
number
dynamic
(return status = 1)


1> sp_poolconfig dbcc_cache
2> go
Cache Name Status
Type Config
Value
Run Value
------------------------------------ ------------------------
------------------------
------------------------------------------
------------------------------------
dbcc_cache Active
Mixed 5.00
Mb
5.00 Mb
------------ ------------
Total 5.00 Mb 5.00 Mb
==========================================================================
Cache: dbcc_cache, Status: Active, Type: Mixed
Config Size: 5.00 Mb, Run Size: 5.00 Mb
Config Replacement: strict LRU, Run Replacement: strict LRU
Config Partition: 1, Run Partition: 1
IO Size Wash Size Config Size Run Size APF Percent
-------- ------------- ------------ ------------ -----------
4 Kb 204 Kb 0.00 Mb 1.00 Mb 10
32 Kb 800 Kb 4.00 Mb 4.00 Mb 10
(return status = 0)

1> sp_dbcc_evaluatedb
2> go
Recommended values for workspace size, cache size and process count
are:

Database name : dbcc_test
current suggested
scan workspace size : 0K 288K
text workspace size : 0K 96K
cache size : 5120K 1280K
process count : 2 2

1> sp_dbcc_configreport
2> go


Reporting default DBCC configuration information.

Parameter Name Value Size

database name DEFAULT_VALUES
scan workspace def$scan$ws (id = 1088003876) 512K
text workspace def$text$ws (id = 1120003990) 256K
max worker processes 1


Reporting configuration information of database dbcc_test.

Parameter Name Value Size

database name dbcc_test 20480K
dbcc named cache dbcc_cache 5120K
operation sequence number 28
max worker processes 2
scan workspace def$scan$ws (id = 1088003876) 512K **
Default
text workspace def$text$ws (id = 1120003990) 256K **
Default
(return status = 0)

mpeppler@peppler.org [Team Sybase]

unread,
Jan 1, 2010, 1:25:21 PM1/1/10
to
According to your message ASE wants to use 2 worker processes - so
setting the "number of worker processes" to 2 should be the correct
fix.

Note that for DBCC checkstorage ASE will normally use one worker
process per disk device used by a database, so you can quite easily
figure out how high to set the max number of worker processes
configuration parameter.

Michael

hiro

unread,
Jan 1, 2010, 7:32:09 PM1/1/10
to
Thanks Michael. (I'm using sybperl. also thanks)

I want to ask additional question.

1. What is mean default value ``0''
The default value of "number of worker processes" is 0
What is this mean??, It is mean that no limit??

2. What are process refer this value
What are process refer "number of process"??
only dbcc checkstorage??

3, maximum value of "number of process"
If a my ASE has some databases.
The maximum "number of process value" is
total of "max number of worker processes" each database?

Is this right??

Sincerely

On 1月2日, 午前3:25, "mpepp...@peppler.org [Team Sybase]"

mpeppler@peppler.org [Team Sybase]

unread,
Jan 2, 2010, 11:08:51 AM1/2/10
to
On Jan 2, 1:32 am, hiro <hiroys...@gmail.com> wrote:
> Thanks Michael. (I'm using sybperl. also thanks)
>
> I want to ask additional question.
>
> 1. What is mean default value ``0''
>  The default value of "number of worker processes" is 0
>  What is this mean??, It is mean that no limit??

No - 0 means 0 (i.e. none)

>
> 2. What are process refer this value
> What are process refer "number of process"??
> only dbcc checkstorage??
>

dbcc checkstorage uses this parameter, as well as queries that are
performed in parallel (e.g. over a partitioned table). You have to
turn on parallelism (also via sp_configure) to use that feature, and
in general it is not needed or beneficial to use it on "normal"
systems.

> 3, maximum value of "number of process"
>  If a my ASE has some databases.
>  The maximum "number of process value" is
>  total of "max number of worker processes" each database?
>
>  Is this right??

Not necessarily, unless you run the checkstorage process for each
database at the same time.
Otherwise, you only need to set the "max number of worker processes"
to the maximum needed by any single checkstorage check.

Michael

hiro

unread,
Jan 3, 2010, 3:14:42 AM1/3/10
to
Thanks Michael.

On Jan 3, 1:08 am, "mpepp...@peppler.org [Team Sybase]"

0 new messages