Connect Internal vs Connect / as sysdba

Hi all,

I know this subject must have been done to death, but I have had two occasions recently where I found myself wishing for the opportunity to connect internal (how often does that happen ?).

I'm on AIX 5L and 9.2.0.3.

An instance recently hit max # of sessions. Any attempt to connect / as sysdba gives the "Max # of sessions exceeded" message - unhelpful. In the end I had to kill the unix processes.

Another instance recently had the archive log area fill. Any attempt to connect / as sysdba gave the message (bizzarely) that the instance was not started. This also seemed to refuse RMAN connections (my RMAN archive backup and delete script just hung. In the end I grew the archive log filesystem, bu7t this may not always be possible.

In both cases I know I would have been able to proeviously connect internal (in earlier versions). And whilst I could have cleanly shut the instance for the first issue (max connections), the second issue (arch log area full) required the RMAN connection to resolve the issue but was unable.

Are these known holes in the functionality of connect / as sysdba ? Metalink can be decidedly unhelpful in situations like these, simply stating "Connect internal is no longer supportd".

Many thanks for any help and answers,

Regards,
neil. Received on Tue Mar 16 2004 - 04:11:45 CST