Restricted mode

[girtas]

Labdien !

Uz 10.2 RAC parādījās mistiska problēma.
Uz vienas nodes, vienai instancei bez redzama pamata ieslēdzas
restricted session.

Grid:
Details: The instance is open.
The instance is in a restricted access state.

Failed to connect to database instance: ORA-12526: TNS:listener: all
appropriate instances are in restricted mode (DBD ERROR:
OCIServerAttach).

lsnrctl:

Service "gdisd" has 2 instance(s).
Instance "gdisd1", status READY, has 1 handler(s) for this
service...
Instance "gdisd2", status RESTRICTED, has 2 handler(s) for this
service...

alertlog:

Fri May 8 00:36:20 2009
Stopping background process MMNL
Fri May 8 00:36:21 2009
Stopping background process MMON
Starting background process MMON
Starting background process MMNL
MMON started with pid=16, OS id=11987
Fri May 8 00:36:22 2009
ALTER SYSTEM enable restricted session;
MMNL started with pid=17, OS id=11989
Fri May 8 00:36:22 2009
ALTER SYSTEM SET service_names='gdisd' SCOPE=MEMORY SID='gdisd2';
Fri May 8 00:36:22 2009
Immediate Kill Session#: 297, Serial#: 1953
Immediate Kill Session: sess: 0x15c3c2d08 OS pid: 10076
Fri May 8 00:56:28 2009
MMNL absent for 1219 secs; Foregrounds taking over


Kā atrast kas ieslēdz tādu ALTER SYSTEM enable restricted session un
kādi procesi var tādu režīmu ieslēgt ?
Visus zināmos log-us izraku, nekas gudrs neķeras.

Ģirts.

[Jurijs Velikanovs]

Cau Ģirt,

Via noskaidroji kur probl'ema?
Es pam'e'gin'amtu 2 lietas:
1. LogMiner ar m'er'ki atr'ast sessijas identifik'atorus un tad caur
$OH/rdbms/audit var'etu m'e'gina't atr'ast termin'alu, IP etc
2. Izveidot DB l'ime'na tr'igeri, kur's audit'etu visus ALTER SYSTEM
komandas. Tad ja n'akotne kaut kas tam lidz'igs notiks tu dro'si
zin'asi kur's pie vainas :)

J.

2009/5/8 girtas <girts....@gmail.com>:

--
Jurijs
+371 29268222 (+2 GMT)
============================================
http://otn.oracle.com/ocm/jvelikanovs.html

[girtas]

Paldies !

G.

On 10 maijs, 14:38, Jurijs Velikanovs <j.velikan...@gmail.com> wrote:
> Cau Ģirt,
>
> Via noskaidroji kur probl'ema?
> Es pam'e'gin'amtu 2 lietas:
> 1. LogMiner ar m'er'ki atr'ast sessijas identifik'atorus un tad caur
> $OH/rdbms/audit var'etu m'e'gina't atr'ast termin'alu, IP etc
> 2. Izveidot DB l'ime'na tr'igeri, kur's audit'etu visus ALTER SYSTEM
> komandas. Tad ja n'akotne kaut kas tam lidz'igs notiks tu dro'si
> zin'asi kur's pie vainas :)
>
> J.
>

> 2009/5/8 girtas <girts.api...@gmail.com>:

> ============================================http://otn.oracle.com/ocm/jvelikanovs.html- Paslēpt citēto tekstu -
>
> - Rādīt citēto tekstu -