RE: Errors when running dbms_stats.gather_fixed_object_stats

From: Bobak, Mark <>
Date: Tue, 25 Mar 2008 15:10:38 -0400
Message-ID: <>


Looks like the base bug is 5938326, which is public.

It's a bit vague, and I'm not entirely sure of the background, but this bug says, down towards the end: "Rediscovery:

When CSS/HAS is not installed and executed and v$asm_diskgroup

or similar ASM queries are issued with excessive logs in trace

files complaining about OCR not ready and/or CSS not running,

customers then have the issue.



Run CSS"

So, are you running CSS?

ps -ef|grep css

Do you see css running? If not, why not? CSS is required, even for single-instance ASM. Did you run all the scripts at the appropriate times (and as root) during the installation?

Again, just speculation based on what I read,

Hope it helps,



Mark J. Bobak
Senior Database Administrator, System & Product Technologies ProQuest
789 E. Eisenhower, Parkway, P.O. Box 1346 Ann Arbor MI 48106-1346
+1.734.997.4059 or +1.800.521.0600 x 4059

ProQuest...Start here.

-----Original Message-----

From: [] On Behalf Of Maureen English Sent: Tuesday, March 25, 2008 2:56 PM
To: Oracle-L Freelists
Subject: Errors when running dbms_stats.gather_fixed_object_stats

We're running on HP Tru64 Unix. After upgrading our databases, I ran dbms_stats.gather_fixed_object_stats and got ocr related messages in a trace file. This is apparently related to bug 5376261, but I can't access anything about this bug on Metalink.

  • 2008-03-10 16:17:33.226
  • SERVICE NAME:(SYS$USERS) 2008-03-10 16:17:33.217
  • SESSION ID:(1585.2771) 2008-03-10 16:17:33.217 2008-03-10 16:17:33.217: [ OCROSD]utgdv:2:ocr loc file cannot be opened 2008-03-10 16:17:33.226: [ OCROSD]utopen:1: Couldnt find ocr,[ocrmirror] location in config file 2008-03-10 16:17:33.226: [ OCRRAW]proprinit: Could not open raw device 2008-03-10 16:17:33.226: [ default]a_init:7!: Backend init unsuccessful : [33] 2008-03-10 16:17:33.227: [ CSSCLNT]clsssinit: error(33 ) in OCR initialization kgxgncin: CLSS init failed with status 21

Any suggestions?

-- Received on Tue Mar 25 2008 - 14:10:38 CDT

Original text of this message