ORA-07274 spdcr: access error, access to oracle denied

I got ” ORA-07274 spdcr: access error, access to oracle denied ”  error in Oracle database.

 

ORA-07274 spdcr: access error, access to oracle denied

 

Details of error are as follows.

ORA-07274 spdcr: access error, access to oracle denied.

Cause: Unable to access Oracle program. Verify ?/bin/oracle or $ORABCKPRG exist, and are executable.

Action: Check errno returned.

Startup of the database appears to be normal in the alert log up to the point of bringing 
the Undo Segments online.

Then the instance dies with an ORA-07274 error.

Example:

21-MAR-2006 08:22:50.63:
Errors in file DISK2:<TRACE FILE INFORMATION>_PMON.TRC;:
ORA-07274: spdcr: access error, access to oracle denied.
DEC ALPHA VMS Error: 2: no such file or directory
PMON: terminating instance due to error 7274
Instance terminated by PMON, pid = 28c00999

 

 

spdcr: access error, access to oracle denied.

This ORA-07274 is related with the Unable to access Oracle program. Verify ?/bin/oracle or $ORABCKPRG exist, and are executable.

Check errno returned.

 

Reviewing the Oracle provided logical ORA_PARAMS for the init<sid>.ora file:

 

$ show log ora_params

"ORA_PARAMS" = "DISK2:[ORACLE9.dbs]init<SID>.ora" (LNM$JOB_82895EC0)
"ORA_PARAMS" = "DISK2:[DBA.<SID>]INIT.ORA" (LNM$GROUP_000299)

 

 

Note that ORA_PARAMS is defined at both JOB and GROUP level and that the physical file name is not the same.

The Oracle defined ORA_PARAMS logical is not defined as a GROUP logical.

In a normal environment, ORA_PARAMS is defined at PROCESS and JOB level and both definitions pointing to the same physical file.

Using the VMS directory command verify that the files exist.

$ dir DISK2:[ORACLE9.dbs]init<SID>.ora
%DIRECT-W-NOFILES, no files found

$ dir DISK2:[DBA.<SID>]INIT.ORA

INIT.ORA;1


So there are three problems in this case:

1. The OpenVMS logical ORA_PARAMS has not been defined correctly (GROUP table is incorrect).

2. The physical file name pointed to by each logical is not the same.

3. The file pointed at the by the PROCESS level ORA_PARAMS logical does not exist on disk.

 

To implement the solution, please execute the following steps:

1. Deassign the GROUP level definition of ORA_PARAMS. Non-standard definitions are unsupported.

$ deassign/group ora_params

2. Log off the VMS node.

3. Log on the VMS node.

4. Invoke the orauser for the instance @orauser <instance name>

5. Verify that the OpenVMS logical ORA_PARAMS is now defined at PROCESS and JOB level.

6. Verify that both logical definitions point to the same, correct file.

8. Start the instance.

 

 

Second case is as follows.

With job_queue_processes > 0, instance startup fails with ora-7274 error and VMS ERROR: 2.

The alert log shows:

 

8-SEP-2006 13:47:34.28:
Errors in file $1$DGA112:[<DB>.ADMIN.S2.BDUMP]ALPHA4_S2_BG_PMON_002.TRC
;:
ORA-07274: spdcr: access error, access to oracle denied.
DEC ALPHA VMS Error: 2: no such file or directory
PMON: terminating instance due to error 7274
Instance terminated by PMON, pid = 20c062cc

 

The customer added their own group level definition for the OpenVMS logical ORA_COMMON.

 

In release 9.2, Oracle has two unique definitions for the OpenVMS logical ORA_COMMON.

 

$ show log ora_common
"ORA_COMMON" = "DISK$ORACLE:[<DB>.BIN]" (SERVER_2709320413)
"ORA_COMMON" = "DISK$ORACLE:[<DB>.RDBMS]" (LNM$JOB_86DBAB00)

 

 

In this case, an additional group level logical was defined by the customer for ORA_COMMON as follows:

 

 

$ define/group ora_common disk$oracle:[<DB>.rdbms]




$ show log ora_common
"ORA_COMMON" = "DISK$ORACLE:[<DB>.BIN]" (SERVER_2709320413)
"ORA_COMMON" = "DISK$ORACLE:[<DB>.RDBMS]" (LNM$JOB_86DBAB00)
"ORA_COMMON" = "DISK$ORACLE:[<DB>.RDBMS]" (LNM$GROUP_000610)

 

With this group level logical defined, and with job_queue_processes > 0, then an attempt is made to execute ora_common:oracle.exe, which in this case translates to ora_root:[rdbms]oracle.exe. This is the cause of the ORA-7274 error since oracle.exe only resides in ora_root:[bin].  This particular failure only happens with the group logical defined as shown above.

 

Remove the group level definition of the OpenVMS logical ORA_COMMON.

 

$ deassign/group ORA_COMMON

 

 

 

 

 

Do you want to learn Oracle Database for Beginners, then read the following articles.

Oracle Tutorial | Oracle Database Tutorials for Beginners ( Junior Oracle DBA )