My Oracle Support Banner

ORA-4030 Reported When Using RMAN To Startup Force Nomount (Doc ID 1311984.1)

Last updated on FEBRUARY 19, 2019

Applies to:

Oracle Database - Enterprise Edition - Version to [Release 10.2 to 11.1]
Oracle Database Cloud Schema Service - Version N/A and later
Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Information in this document applies to any platform.


When attempting to use RMAN to 'startup force nomount' the following error occurs:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of startup command at 03/11/2011 17:06:45
RMAN-06403: could not obtain a fully authorized session
ORA-00604: error occurred at recursive SQL level 1
ORA-04030: out of process memory when trying to allocate 256 bytes (PCursor,kglob)

The issue can be reproduced at will with the following steps:



New installation of RAC environment, no instances, no parameter files, at node 2.
Can use RMAN to 'startup force nomount', but cannot run the same command in node 1. 



To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.