Re: clob support frustration at support

[patrick zandi]

Original problem back ... Frustrating..

Summary: Host:HOSTNAME Problem:Oracle SIDNAME Alert Log Msg=( ORA-2:
index "ARADMIN"."IT145"  or par

Notes: Host:DHOSTNAME Problem:Oracle SIDNAME Alert Log Msg=( ORA-2:
index "ARADMIN"."IT145"  or partition of such index is in unusable state )
- full details in work info




On Mon, Apr 9, 2012 at 3:16 PM, patrick zandi  wrote:

> I am getting a little frustrated..
> Following the Clob in a row doc to put in a row.. after I ran the job, I
> get alerts in the oracle alert log about the
> Index is corrupt,  SO I figure .. fine I will dump all the indexes and I
> cannot.. I get the
> ORA-00054: resource busy and acquire with NOWAIT specified or timeout
> expired,  552,  BMC.CORE:BMC_BaseElement
> So fine, BMC comes back with
>
> From the above error it looks like the table/view -
> 'BMC.CORE:BMC_BaseElement ' is already locked by some query. Like you have
> executed "select for update" and has yet not committed/rollback and again
> fired select query. Kindly have your DBA to unlock the query or rollback
> before executing your query.
>
>
> They don't tell you how.. just that it needs to be done..  So we figure
> out that it is locked and then unlocked at about a every 15 seconds, and
> then not for 10 and then for 15 .. on and off.. constantly..
>
> no ryme nor reason.. Fine.. so we shutdown the db.. and start it back up
> again..
>
> Everything seems fine.. dropped all indexes.. Yeah... !!!
>
> added 4 indexes.. Wham .. Puke puke puke puke..
>
> Failure during SQL operation to the database : ORA-00054: resource busy
> and acquire with NOWAIT specified or timeout expired (ARERR 552).
>
> Failure during SQL operation to the database : 400131300 (ARWARN 552).
>
> Failure during SQL operation to the database : 400079600 (ARWARN 552).
>
> Failure during SQL operation to the database :
> 179,1,400079600,400127400,400129200 (ARWARN 552).
>
> Index length longer than 255 bytes --
>
> may not work on all databases (ARWARN 8037).
>
>
> This clob in a row, is turning into a FIASCO !!! BMC .. come on... my
> "less than bronze" support is not working..
>
>
>
>
>
>
> --
> Patrick Zandi
>



-- 
Patrick Zandi

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Re: clob support frustration at support

[patrick zandi]

ok, I figured out that the creating multiple indexs on a form, Fails.. but
if you add one at a time. it seems ok so far..


On Mon, Apr 9, 2012 at 4:41 PM, patrick zandi  wrote:

> yeah, already did that..  found it. .but it was intermittent.. very odd,
> like 5 times a min for 4 seconds..  but the ars would not allow the drop..
> so I decided to shutdown.. and restart.. the oracle. it cleared up.. and
> it allowed the drop of indexes.. but now I cannot create indexes..
> It is what BMC had me do with the clob..
>
> On Mon, Apr 9, 2012 at 3:59 PM, Axton  wrote:
>
>> ** You might look into the ar.conf parameter "Read-Only-Tran-Off"
>>
>> From the docs:
>> "Causes AR System not to create database transactions when only
>> reading data."
>>
>> Whether this will help or not depends on where the lock is coming from.
>>  You can see what has a lock using this:
>> select do.object_name,
>> dbms_rowid.rowid_create(1,
>> ROW_WAIT_OBJ#,
>> ROW_WAIT_FILE#,
>> ROW_WAIT_BLOCK#,
>> ROW_WAIT_ROW#) row_id,
>> 'select * from ' do.object_name ' where rowid = '''
>> dbms_rowid.rowid_create(1,
>> ROW_WAIT_OBJ#,
>> ROW_WAIT_FILE#,
>> ROW_WAIT_BLOCK#,
>> ROW_WAIT_ROW#)  query
>> from v$session s,
>>dba_objects do
>> where s.sid = 54 and
>>  s.ROW_WAIT_OBJ# = do.object_id;
>>
>> (attributed to 
>> http://knol.google.com/k/oracle-locks
>> )
>>
>> This page also has some good queries to get a list of the locks:
>> http://www.dba-oracle.com/t_ora_00054_locks.htm
>>
>> Axton Grams
>>
>> On Mon, Apr 9, 2012 at 2:16 PM, patrick zandi wrote:
>>
>>> ** I am getting a little frustrated..
>>> Following the Clob in a row doc to put in a row.. after I ran the job, I
>>> get alerts in the oracle alert log about the
>>> Index is corrupt,  SO I figure .. fine I will dump all the indexes and I
>>> cannot.. I get the
>>> ORA-00054: resource busy and acquire with NOWAIT specified or timeout
>>> expired,  552,  BMC.CORE:BMC_BaseElement
>>> So fine, BMC comes back with
>>>
>>> From the above error it looks like the table/view -
>>> 'BMC.CORE:BMC_BaseElement ' is already locked by some query. Like you have
>>> executed "select for update" and has yet not committed/rollback and again
>>> fired select query. Kindly have your DBA to unlock the query or rollback
>>> before executing your query.
>>>
>>>
>>> They don't tell you how.. just that it needs to be done..  So we figure
>>> out that it is locked and then unlocked at about a every 15 seconds, and
>>> then not for 10 and then for 15 .. on and off.. constantly..
>>>
>>> no ryme nor reason.. Fine.. so we shutdown the db.. and start it back up
>>> again..
>>>
>>> Everything seems fine.. dropped all indexes.. Yeah... !!!
>>>
>>> added 4 indexes.. Wham .. Puke puke puke puke..
>>>
>>> Failure during SQL operation to the database : ORA-00054: resource busy
>>> and acquire with NOWAIT specified or timeout expired (ARERR 552).
>>>
>>> Failure during SQL operation to the database : 400131300 (ARWARN 552).
>>>
>>> Failure during SQL operation to the database : 400079600 (ARWARN 552).
>>>
>>> Failure during SQL operation to the database :
>>> 179,1,400079600,400127400,400129200 (ARWARN 552).
>>>
>>> Index length longer than 255 bytes --
>>>
>>> may not work on all databases (ARWARN 8037).
>>>
>>>
>>> This clob in a row, is turning into a FIASCO !!! BMC .. come on... my
>>> "less than bronze" support is not working..
>>>
>>>
>>>
>>>
>>>
>>>
>>> --
>>> Patrick Zandi
>>> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_
>>
>>
>> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_
>
>
>
>
> --
> Patrick Zandi
>



-- 
Patrick Zandi

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Re: clob support frustration at support

[patrick zandi]

yeah, already did that..  found it. .but it was intermittent.. very odd,
like 5 times a min for 4 seconds..  but the ars would not allow the drop..
so I decided to shutdown.. and restart.. the oracle. it cleared up.. and it
allowed the drop of indexes.. but now I cannot create indexes..
It is what BMC had me do with the clob..

On Mon, Apr 9, 2012 at 3:59 PM, Axton  wrote:

> ** You might look into the ar.conf parameter "Read-Only-Tran-Off"
>
> From the docs:
> "Causes AR System not to create database transactions when only
> reading data."
>
> Whether this will help or not depends on where the lock is coming from.
>  You can see what has a lock using this:
> select do.object_name,
> dbms_rowid.rowid_create(1,
> ROW_WAIT_OBJ#,
> ROW_WAIT_FILE#,
> ROW_WAIT_BLOCK#,
> ROW_WAIT_ROW#) row_id,
> 'select * from ' do.object_name ' where rowid = '''
> dbms_rowid.rowid_create(1,
> ROW_WAIT_OBJ#,
> ROW_WAIT_FILE#,
> ROW_WAIT_BLOCK#,
> ROW_WAIT_ROW#)  query
> from v$session s,
>dba_objects do
> where s.sid = 54 and
>  s.ROW_WAIT_OBJ# = do.object_id;
>
> (attributed to 
> http://knol.google.com/k/oracle-locks
> )
>
> This page also has some good queries to get a list of the locks:
> http://www.dba-oracle.com/t_ora_00054_locks.htm
>
> Axton Grams
>
> On Mon, Apr 9, 2012 at 2:16 PM, patrick zandi  wrote:
>
>> ** I am getting a little frustrated..
>> Following the Clob in a row doc to put in a row.. after I ran the job, I
>> get alerts in the oracle alert log about the
>> Index is corrupt,  SO I figure .. fine I will dump all the indexes and I
>> cannot.. I get the
>> ORA-00054: resource busy and acquire with NOWAIT specified or timeout
>> expired,  552,  BMC.CORE:BMC_BaseElement
>> So fine, BMC comes back with
>>
>> From the above error it looks like the table/view -
>> 'BMC.CORE:BMC_BaseElement ' is already locked by some query. Like you have
>> executed "select for update" and has yet not committed/rollback and again
>> fired select query. Kindly have your DBA to unlock the query or rollback
>> before executing your query.
>>
>>
>> They don't tell you how.. just that it needs to be done..  So we figure
>> out that it is locked and then unlocked at about a every 15 seconds, and
>> then not for 10 and then for 15 .. on and off.. constantly..
>>
>> no ryme nor reason.. Fine.. so we shutdown the db.. and start it back up
>> again..
>>
>> Everything seems fine.. dropped all indexes.. Yeah... !!!
>>
>> added 4 indexes.. Wham .. Puke puke puke puke..
>>
>> Failure during SQL operation to the database : ORA-00054: resource busy
>> and acquire with NOWAIT specified or timeout expired (ARERR 552).
>>
>> Failure during SQL operation to the database : 400131300 (ARWARN 552).
>>
>> Failure during SQL operation to the database : 400079600 (ARWARN 552).
>>
>> Failure during SQL operation to the database :
>> 179,1,400079600,400127400,400129200 (ARWARN 552).
>>
>> Index length longer than 255 bytes --
>>
>> may not work on all databases (ARWARN 8037).
>>
>>
>> This clob in a row, is turning into a FIASCO !!! BMC .. come on... my
>> "less than bronze" support is not working..
>>
>>
>>
>>
>>
>>
>> --
>> Patrick Zandi
>> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_
>
>
> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_




-- 
Patrick Zandi

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"

Re: clob support frustration at support

[Axton]

You might look into the ar.conf parameter "Read-Only-Tran-Off"

>From the docs:
"Causes AR System not to create database transactions when only
reading data."

Whether this will help or not depends on where the lock is coming from.
 You can see what has a lock using this:
select do.object_name,
dbms_rowid.rowid_create(1,
ROW_WAIT_OBJ#,
ROW_WAIT_FILE#,
ROW_WAIT_BLOCK#,
ROW_WAIT_ROW#) row_id,
'select * from ' do.object_name ' where rowid = '''
dbms_rowid.rowid_create(1,
ROW_WAIT_OBJ#,
ROW_WAIT_FILE#,
ROW_WAIT_BLOCK#,
ROW_WAIT_ROW#)  query
from v$session s,
   dba_objects do
where s.sid = 54 and
 s.ROW_WAIT_OBJ# = do.object_id;

(attributed to 
http://knol.google.com/k/oracle-locks
)

This page also has some good queries to get a list of the locks:
http://www.dba-oracle.com/t_ora_00054_locks.htm

Axton Grams

On Mon, Apr 9, 2012 at 2:16 PM, patrick zandi  wrote:

> ** I am getting a little frustrated..
> Following the Clob in a row doc to put in a row.. after I ran the job, I
> get alerts in the oracle alert log about the
> Index is corrupt,  SO I figure .. fine I will dump all the indexes and I
> cannot.. I get the
> ORA-00054: resource busy and acquire with NOWAIT specified or timeout
> expired,  552,  BMC.CORE:BMC_BaseElement
> So fine, BMC comes back with
>
> From the above error it looks like the table/view -
> 'BMC.CORE:BMC_BaseElement ' is already locked by some query. Like you have
> executed "select for update" and has yet not committed/rollback and again
> fired select query. Kindly have your DBA to unlock the query or rollback
> before executing your query.
>
>
> They don't tell you how.. just that it needs to be done..  So we figure
> out that it is locked and then unlocked at about a every 15 seconds, and
> then not for 10 and then for 15 .. on and off.. constantly..
>
> no ryme nor reason.. Fine.. so we shutdown the db.. and start it back up
> again..
>
> Everything seems fine.. dropped all indexes.. Yeah... !!!
>
> added 4 indexes.. Wham .. Puke puke puke puke..
>
> Failure during SQL operation to the database : ORA-00054: resource busy
> and acquire with NOWAIT specified or timeout expired (ARERR 552).
>
> Failure during SQL operation to the database : 400131300 (ARWARN 552).
>
> Failure during SQL operation to the database : 400079600 (ARWARN 552).
>
> Failure during SQL operation to the database :
> 179,1,400079600,400127400,400129200 (ARWARN 552).
>
> Index length longer than 255 bytes --
>
> may not work on all databases (ARWARN 8037).
>
>
> This clob in a row, is turning into a FIASCO !!! BMC .. come on... my
> "less than bronze" support is not working..
>
>
>
>
>
>
> --
> Patrick Zandi
> _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"