ORA-07274: spdcr: access error, access to oracledenied.

ORA-07274: spdcr: access error, access to oracledenied.

Symptom:

The ORA-12545 error is reported when SQL plus/as sysdba logs into the database, as follows:

[Oracle @ source ~] $ Sqlplus/as sysdba
ORA-12545: Connect failed because targethost or object does not exist

Problem Analysis:

From the error message, this problem should be a simple and common problem, usually because the SID is incorrect, the host points to an incorrect one, and in SQLNET. if the local verification is disabled in ora, the above error will be reported, but the check is normal, as shown below:

Solution 1:

First, we should check the items mentioned above. The results are correct, but they cannot be stored in the dead:

[Oracle @ source ~] $ Cat/etc/hosts

& Nbsp; # Do not remove the following line, orvarious programs
# That require network functionality will fail.

127.0.0.1 localhost. localdomain localhost

192.168.7.20 source
192.168.7.21 target

[Oracle @ source ~] $ Echo $ ORACLE_SID
Woo

[Oracle @ source ~] $ Cat/DBSoft/product/11.2.4/db_1/network/admin/listener. ora
# Listener. ora Network Configuration File:/DBSoft/product/11.2.4/db_1/network/admin/listener. ora
# Generated by Oracle configuration tools.
 
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC) (KEY = EXTPROC1521 ))
(ADDRESS = (PROTOCOL = TCP) (HOST = 192.168.7.20) (PORT = 1521 ))
)
)

ADR_BASE_LISTENER =/DBSoft

[Oracle @ source ~] $ Cat/DBSoft/product/11.2.4/db_1/network/admin/sqlnet. ora
# Sqlnet. ora Network Configuration File:/DBSoft/product/11.2.4/db_1/network/admin/sqlnet. ora
# Generated by Oracle configuration tools.

NAMES. DIRECTORY_PATH = (TNSNAMES, EZCONNECT)
ADR_BASE =/DBSoft

Solution 2:

Check the alert alarm log file and send the following error:

[Oracle @ source ~] $ Tail-50 $ ORACLE_BASE/diag/Woo/woo/alert_woo.log | grep ORA-
ORA-07274: spdcr: access error, access to oracledenied.

Looking at this error message, I am very unfamiliar. Then I went to the Internet to find a solution. I can see that there is a document in askmaclean's blog about this, but the environment is different. If it doesn't work, it's a dead horse, then, the problem is solved:

Solution steps:

From the askmaclean blog, we can see that this problem may occur due to the incorrect oracle File status in the $ ORACLE_HOME/bin directory. The steps for solving this problem are as follows:

1. Check the oracle file in the $ ORACLE_HOME/bin/directory.
[Oracle @ source ~] $ Ll $ ORACLE_HOME/bin/oracle
Ls:/DBSoft/product/11.2.4/db_1/bin/oracle: No such file or directory

2. copy the file from other normal nodes to the directory.
[Oracle @ target ~] $ Scp $ ORACLE_HOME/bin/oracle source: $ ORACLE_HOME/bin/

3. Check the file and related permissions again. It can be seen that they are all correct.
[Oracle @ source ~] $ Ll $ ORACLE_HOME/bin/oracle
-Rwsr-s -- x 1 oracle oinstall 239627073Sep 2/DBSoft/product/11.2.4/db_1/bin/oracle

4. log on to sqlplus again. The problem is solved successfully.
[Oracle @ source ~] $ Sqlplus/as sysdba
SQL * Plus: Release 11.2.0.4.0 Production onWed Sep 3 00:12:54 2014
Copyright (c) 1982,201 3, Oracle. All rights reserved.
Connected:

Oracle Database 11g Enterprise EditionRelease 11.2.0.4.0-64bit Production
With the Partitioning, OLAP, Data Miningand Real Application Testing options
SQL>