[{ALLOW view All}]
[{ALLOW edit Authenticated}]
!Data storage quality

|DB12|Datenbank Backups
|DB14|Alle Operationen >  Statusübersicht
|DB20|Update Stats > Anlegen
|DBACOCKPIT|Performance > Additional Functions > SQL Command Editor
|ST05|SQL Anweisung eingeben > Explain

|r.RSORATAD|SEG_NAME = index name, see SE14
|r.RSORAISQ|Index analysis (texts only in English)
|x.DB02 or x.DBACOCKPIT|Overview

see [here|http://www.saptechies.com/faq-index-fragmentation/]

! Check DML table lock
|x.ORA_LOCK|Opens the "Lock Monitor"
Switch to tab "DML Locks. If a job is doing lots of DML statements, the locked table appears here. In a report the table is only released when the report finishes. If you do a "COMMIT WORK" in between, other (parallel) reports are able to pass DML statements in between!

!SAP Client Copy, Mandantenkopie

see [SAP Docu|http://help.sap.com/saphelp_nw04/helpdata/en/69/c24c4e4ba111d189750000e8322d00/frameset.htm] | [Steps|http://www.sap-img.com/bc049.htm] 
|SCC4|Mandantenpflege
|SCC3|Restart Client Copy
|SCCL|Lokale Kopie
|SCC8|Export in Transportaufträge (SAP_ALL)
|SE06|Systemänderbarkeit

Note: RFC user needs authorization according to note [552711|https://service.sap.com/sap/support/notes/552711] and [24853|https://service.sap.com/sap/support/notes/24853] !

!Get table / schema info
{{{
select * from all_tables where table_name = 'PCL2'
}}}

!enq: TX - row lock contention
See [here|http://arjudba.blogspot.com/2008/05/what-is-enq-tx-row-lock-contention.html] 
{{{
For which SQL currently is waiting to:
SQL> select sid, sql_text
from v$session s, v$sql q
where sid in (select sid
from v$session where state in ('WAITING')
and wait_class != 'Idle' and event='enq: TX - row lock contention'
and (
q.sql_id = s.sql_id or
q.sql_id = s.prev_sql_id));

The blocking session is:
SQL> select blocking_session, sid, serial#, wait_class, seconds_in_wait from v$session
where blocking_session is not NULL order by blocking_session;

sessions involved & the objects involved:
SQL> SELECT DECODE(request,0,'Holder: ','Waiter: ')||sid sess, 
id1, id2, lmode, request, type
FROM V$LOCK
WHERE (id1, id2, type) IN
(SELECT id1, id2, type FROM V$LOCK WHERE request>0)
ORDER BY id1, request
}}}

!Enqueue Server / Lock table overflow / Parameter "enque/table_size"

On 18.02.2014 we had an error in PCP0 stating "Überlauf der Sperrtabelle".\\
See [SapDoku|http://help.sap.com/saphelp_nw70/helpdata/de/37/a2e3ab344411d3acb00000e83539c3/content.htm] |
[SapDoku2|http://help.sap.com/saphelp_nw70/helpdata/de/f0/b57338788f4d72e10000009b38f8cf/content.htm]

__Note:__ If remote functions are called, this error may occur also in the remote system, please check there as well, example r.RPCIPE00_OLD.

Check:
*SM12 > Anlisten
*SM12 > Menü > Zusätze > Statistik
*SM12 > Menü > Zusätze > Funktionshinweise (=Help)
*AL11 > DIR_HOME > File "ENQHISOVR"

Where is the Enqueue Server running (general only on central instance)?
* RZ04 > double click > column "Enq"

!SE16N

With SAP Note 1420281 the &SAP_EDIT feature is deactivated (April 2011).\\
You can reactivate it with manipulating two variables in debugging mode: [http://stankowski.it/sap/adm/editse16n.html]\\

In short: Go to SE16N, execute in debugging mode (ie run /H) before executing, and then change the value of two global variables to X.
These variables are GD-EDIT and GD-SAPEDIT. Once changed, click on execute, and voila, you are now able to change the table contents.
(http://scn.sap.com/thread/1708973)

Alternative: fuba.SE16N_INTERFACE