Tns could not resolve the connect identifier specified как исправить

This is an old question but Oracle’s latest installers are no improvement, so I recently found myself back in this swamp, thrashing around for several days …

My scenario was SQL Server 2016 RTM. 32-bit Oracle 12c Open Client + ODAC was eventually working fine for Visual Studio Report Designer and Integration Services designer, and also SSIS packages run through SQL Server Agent (with 32-bit option). 64-bit was working fine for Report Portal when defining and Testing an Data Source, but running the reports always gave the dreaded “ORA-12154” error.

My final solution was to switch to an EZCONNECT connection string – this avoids the TNSNAMES mess altogether. Here’s a link to a detailed description, but it’s basically just: host:port/sid

http://www.oracledistilled.com/oracle-database/oracle-net/using-easy-connect-ezconnect-naming-method-to-connect-to-oracle-databases/

In case it helps anyone in the future (or I get stuck on this again), here are my Oracle install steps (the full horror):

Install Oracle drivers: Oracle Client 12c (32-bit) plus ODAC.

a. Download and unzip the following files from http://www.oracle.com/technetwork/database/enterprise-edition/downloads/database12c-win64-download-2297732.html and http://www.oracle.com/technetwork/database/windows/downloads/utilsoft-087491.html ):

i. winnt_12102_client32.zip

ii. ODAC112040Xcopy_32bit.zip

b. Run winnt_12102_client32client32setup.exe. For the Installation Type, choose Admin. For the installation location enter C:OracleOracle12. Accept other defaults.

c. Start a Command Prompt “As Administrator” and change directory (cd) to your ODAC112040Xcopy_32bit folder.

d. Enter the command: install.bat all C:OracleOracle12 odac

e. Copy the tnsnames.ora file from another machine to these folders: *

i. C:OracleOracle12networkadmin *

ii. C:OracleOracle12product12.1.0client_1networkadmin *

Install Oracle Client 12c (x64) plus ODAC

a. Download and unzip the following files from http://www.oracle.com/technetwork/database/enterprise-edition/downloads/database12c-win64-download-2297732.html and http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html ):

i. winx64_12102_client.zip

ii. ODAC121024Xcopy_x64.zip

b. Run winx64_12102_clientclientsetup.exe. For the Installation Type, choose Admin. For the installation location enter C:OracleOracle12_x64. Accept other defaults.

c. Start a Command Prompt “As Administrator” and change directory (cd) to the C:SoftwareOracle ClientODAC121024Xcopy_x64 folder.

d. Enter the command: install.bat all C:OracleOracle12_x64 odac

e. Copy the tnsnames.ora file from another machine to these folders: *

i. C:OracleOracle12_x64networkadmin *

ii. C:OracleOracle12_x64product12.1.0client_1networkadmin *

* If you are going with the EZCONNECT method, then these steps are not required.

The ODAC installs are tricky and obscure – thanks to Dan English who gave me the method (detailed above) for that.

automated-testing.info

Загрузка…

  • testomat.io управление авто тестами
  • Python
  • Реклама
  • Работа
  • Консультации
  • Обучение

I am trying to connect to oracle 11g installed on Linux EL 5 and and getting the following error

SQL> connect sys/password@ud06 as sysdba
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor

my listener.ora under network/admin is as follows

LISTENER=
  (DESCRIPTION=
    (ADDRESS_LIST=
      (ADDRESS=(PROTOCOL=tcp)(HOST=ud06)(PORT=1521))
      (ADDRESS=(PROTOCOL=ipc)(KEY=extproc))))

SID_LIST_LISTENER=
  (SID_LIST=
    (SID_DESC=
      (GLOBAL_DBNAME=orcl)
      (ORACLE_HOME=/home/oracle/app/oracle/product/11g)
      (SID_NAME=orcl))
    (SID_DESC=
      (SID_NAME=plsextproc)
      (ORACLE_HOME=/home/oracle/app/oracle/product/11g)
      (PROGRAM=extproc)))

MY tnsnames.ora is as follows

ORCL =
  (DESCRIPTION =
    (ADDRESS = (PROTOCOL = TCP)(HOST = localhost.localdomain)(PORT = 1521))
    (CONNECT_DATA =
      (SERVER = DEDICATED)
      (SERVICE_NAME = orcl)
    )
  )

EXTPROC_CONNECTION_DATA =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC1))
    )
    (CONNECT_DATA =
      (SID = PLSExtProc)
      (PRESENTATION = RO)
    )
  )

UD06=
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = ud06)(PORT = 1521))
    )
    (CONNECT_DATA =
      (SERVICE_NAME = orcl)
    )
  )

MY lsnrctl status shows as follows:

LSNRCTL> status
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ud06.us.server.com)(PORT=1521)))
STATUS of the LISTENER
------------------------
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 11.2.0.1.0 - Production
Start Date                17-FEB-2010 16:23:06
Uptime                    0 days 0 hr. 12 min. 33 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /home/oracle/app/oracle/product/11g/network/admin/listener.ora
Listener Log File         /home/oracle/app/oracle/product/11g/log/diag/tnslsnr/ud06/listener/alert/log.xml
Listening Endpoints Summary...
  (DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=ud06.us.server.com)(PORT=1521)))
  (DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=extproc)))
Services Summary...
Service "orcl" has 1 instance(s).
  Instance "orcl", status UNKNOWN, has 1 handler(s) for this service...
Service "plsextproc" has 1 instance(s).
  Instance "plsextproc", status UNKNOWN, has 1 handler(s) for this service...
The command completed successfully

Issue

How to troubleshoot Oracle Connection errors.

Oracle drivers require very specific connection statements in a unique format, though a TNSNames.ora file may not always be required. For instance, if you have installed only the Tableau-provided Oracle files and do not have a stand-alone Oracle client, the Oracle error messages will still refer to the TNSNames.ora file, making troubleshooting complicated.

    Environment

    • Tableau Desktop
    • Tableau Server
    • Oracle

    Resolution

    Often, correcting route or naming syntax in the Advanced Oracle Connection dialog box or using your full .WORLD database name resolves most Oracle connection issues. If your connection error requires more troubleshooting, refer to the five common connection errors listed below.

    • ORA-03113: end-of-file on communication channel
    • ORA-12154: TNS: could not resolve the connect identifier specified: HOST value incorrect or Global name incorrect or unknown
    • ORA-12514: TNS listener does not currently know of service requested in connect descriptor: SERVICE value incorrect
    • ORA-12541: TNS: no listener: PORT value incorrect
    • ORA-00932: inconsistent data types

      ORA-03113: end-of-file on communication channel

      ORA-03113 is a catch-all type error for any problem interrupting an Oracle session. There can be numerous causes for this error. Please refer to the list below for some troubleshooting guidance.

      • Refer to Oracle documentation specific to this error: My Oracle Support.
        • Refer to Oracle’s B Troubleshooting Common Errors page.
      • Oracle recommends that you check for network problems and review the SQL*Net setup.
      • If you are connecting to Oracle 9.2.0.5, in many cases the primary cause of this error is Oracle bug 3010227. Ask your Oracle database administrator to apply Oracle patch 9.2.0.6 or another patch appropriate for your server.
      • Set the Oracle initialization parameter ‘STAR_TRANSFORMATION_ENABLED’ to FALSE.
      • Test changing the scheduled time of the extract refresh
      • Alternatively, if you would like to test this issue further follow the optional procedure listed below.

      Step 1 

      From the Tableau Desktop start page, select Connect to Data.

      Step 2 

      On the Connect page, click Oracle, then click OK.

      For more information about completing the connection steps, refer to the Oracle Database topic in the Desktop Help.

      Step 3 

      1. In the join area, hover over the Custom SQL table until the edit icon displays, and then click the icon.
      2. Copy the query in the Edit Custom SQL dialog box.

      SELECT "NumericBins", "Key" as "Key",
      "NumericBins", "Measure E-2" AS "Measure E-2",
      "NumericBins", "Measure E-1" AS "Measure E-1",
      "NumericBins", "Measure E+0" AS "Measure E+0",
      "NumericBins", "Measure E+1" AS "Measure E+1",
      "NumericBins", "Measure E+4" AS "Measure E+4",
      "NumericBins", "Measure E+7" AS "Measure E+7"
      FROM "TestV1", "NumericBins" "NumericBins"

       

      Where “TestV1” is the name of your connection in Tableau.

      Step 4 

      In a SQL session connected to this database, paste and run the query. The expected response is error ORA-7445: exception encountered: core dump, which confirms that the problem is ORA-3113, as expected.

      ORA-12154: TNS: could not resolve the connect identifier specified

      ORA-12154 occurs when the transparent network substrate (TNS) cannot resolve the service name. The service name is specified in the TNSNames.ora file, which is located in your %ORACLE_HOME%networkadmin folder. Most often, this error occurs when information in the TNSNames.ora file is incorrect. For example:

      • The .world extension is not included on the database name.
      • The SERVICE_NAME or HOST variable is incorrect.

      To resolve this issue, try one of the three following troubleshooting options, in the order listed below.

      • Option 1: Setting an Oracle Connection to Use TNSNames.ora or LDAP.ora
      • Option 2: Error “ORA-12154” Connecting to Oracle When Not Using TNSNames.ora

      Option 1: Edit TNSNames.ora

       Provide the full database name, including the .world extension in both of the following locations:

      • The TNSNames.ora file.

        And

      • The Server text box of the Connect page.

      Option 2: Ensure that Tableau Server Run As User account has permissions to TNSNames.ora (Tableau Server only)

      If you have Tableau Server installed, complete the procedure below to ensure that the Tableau Server Run As user account has permissions to the location of the TNSNames.ora file. If the Run As user account does not have permissions, Tableau Server is unable to access the Oracle Data source details.

      Step 1 

      Verify the location of the TNSNames.ora file, or the equivalent SQLNET.ora and LDAP.ora files on the machine.

      Note: By default, the TNSNames.ora file is located in <oracle-directory>networkadmin directory. For example, C:Oracle_Clientnetworkadmin.

      Step 2 

      Confirm that the TNS_ADMIN variable points to the location of the file or files described in step 1.

      Note: To check the TNS_ADMIN variable, click the Start button, and select Control Panel > System. Click Advanced system settings, click the Advanced tab, and click Environmental Variables button.
      The system variable file path must be in UNC format.

      Step 3 

      Open TSM in a browser: https://<tsm-computer-name>:8850 For more information, see Sign in to Tableau Services Manager Web UI.

      Step 4 

      Click the Security tab, and then click the Run As Service Account tab.
      Under Server Run As User, copy the information in the Username field.

      Step 5 

      Go to the folder where the TNSNames.ora file is located.

      Step 6 

      Right-click the folder and select Properties. Click the Security tab and click the Edit button.

      Step 7 

      Under Group or user names, click the Add button.

      Step 8 

      In the Enter the object names to select text box, paste the details of the Run As User account you copied in step 6.

      Step 9 

      When finished, click OK.

      Step 10 

      In the Permissions area,ensure that the Full control and Modify check boxes are selected.

      Step 11 

      Click OK to close the dialog boxes.

        Option 3: Verify that all information in TNSNames.ora is correct

         If the above troubleshooting steps do not resolve the issue, continue reading and complete the procedure to verify the other information in the TNSNames.ora file is provided correctly.

        An example of a TNSNames.ora file is shown here:

        QAORCL10.world =

        (DESCRIPTION =

        (ADDRESS_LIST =

        (ADDRESS = (PROTOCOL = TCP)(HOST = MY_HOST_NAME)(PORT = 1521))

        )

        (CONNECT_DATA =

        (SERVICE_NAME = MY_SERVICE_NAME)

        )

        )

        The three variables of interest in the file are HOST, PORT, and SERVICE_NAME. Copy these variables from the TNSNames.ora file and keep them available. These variables are case sensitive.The following steps describe how to provide these variables for your connection.

        Step 1 

        From the Tableau Desktop start page, select Connect to Data.

        Step 2 

        On the Connect page, click Oracle.

        Step 3 

        Provide the following information from the TNSNames.ora file:

        • In the Server name text box, type the HOST name.
        • In the Service text box, type the SERVICE_NAME.
        • In the Port text box, type the PORT number.
        • Specify whether to use Windows Authentication or a specific user name and password, and then click Connect.

        Note: Variables are case sensitive.

        Step 4 

        Select a schema from the Schema drop-down list, drag a table to the join area, and then click Go to Worksheet.

        Step 5 

        Complete the steps in the Setting an Oracle Connection to Use TNSNames.ora or LDAP.ora article.

        Important: 

        • Make sure that you save the TNSNames.ora file you use in ASCII encoding. Any other encoding besides ASCII, for example UTF-8 or Unicode, causes the ORA-12154 error message.
        • These steps are usually required even if the Oracle software is already installed on the machine.

        Step 6

        Download and install the appropriate Oracle drivers from the Tableau Drivers page. Even if an Oracle driver is installed on your computer, it could be incompatible with Tableau and will require the version specified on the Drivers page.

        ORA-12514: TNS listener does not currently know of service requested in connect descriptor

        Typically this error occurs when the SERVICE value is incorrect.

        To resolve this issue, find out what the correct SERVICE value is, open the TNSNames.ora file located in your %ORACLE_HOME%networkadmin folder. Refer to the steps under ORA_12154 if necessary.

        ORA-12541: TNS: no listener

        Typically this error occurs when the PORT value is incorrect.

        To resolve this issue, replace the PORT value with either 1521 or 1526. Try the value that is currently not in use.

        ORA-00932: inconsistent data types

        This error occurs when connecting to Oracle or when creating an extract from an Oracle data source. Typically this error is caused by the installation of incorrect Oracle drivers.

        To resolve this issue, install the correct Oracle drivers from the Drivers page for the version of Tableau you are using.

        In addition to the above common errors, if you are using Tableau Desktop/Server 2020.2 or later and experiencing performance issues e.g. extract refresh taking long time, you can try downloading and installing the Oracle OCI driver. Refer to the article in Related Links. Driver can be downloaded from here.

          Additional Information

          Suggestions

          If you do not have an Oracle Client installed on your machine, be sure to get the necessary files from your database administrator. If the Oracle data connection errors persist, do the following:

          • Check the TNSNames.ora folder path used to create the TNS_ADMIN variable.
          • Restart your machine to ensure that the TNS_ADMIN variable is recognized.
          • Check that the Oracle connection name used in Tableau exactly matches the TNSNames.ora Net Service Name entry. This name is case sensitive.
          • In some cases Windows will need to be restarted before the Oracle driver will pick up the TNS_ADMIN system variable
          • Contact local IT to verify that the TNSNames.ora file is current.
          • If the Oracle connection uses LDAP, make sure to include the SQLNet.ora file as well as the TNSNames.ora file.




          Fix ORA-12154 TNS Could Not Resolve The Connect Identifier Specified Error

          While using Oracle database, you may come across several errors due to some uncertain reasons and one of the error is the ORA-12154 error. If you are the one who has got this error then you don’t have to worry at all. I am saying so because here I am going to show you how to fix ora-12154 error with ease. Yes, you are so lucky that you have visited this webpage because after going through the solutions, you will be definitely able to resolve ora-12154 error in no time.

          But, before we proceed to the solutions let us know something more about this ORA-12154 error that takes place while using Oracle database.

          If you receive ora-12154 error then it means that the Oracle database client has been failed while he/she tries to connect with the listener on the desired server.

          Or, in Oracle language, this error is defined as ‘a connection to the service or the database was requested using a connect identifier, as well as the connect identifier that is specified could not be resolved into a connect descriptor with the use of one of the naming methods configured.’ As for example, if the type of connect identifier used was actually a net service name then the net service name is not found in a naming method repository or the repository is actually be reached or located.

          There are several reasons that are responsible for causing this oracle error and due to the unknown reasons, it has become quite tricky to fix ora-12154 error. However, here I have tried to solve this error based on some reasons that may cause this error to occur.

          What Causes ORA-12154 Error To Occur?

          As I have already mentioned that there are several causes due to which ora-12154 error takes place. Here are some of the major known causes:

          • Missing tnsnames.ora File
          • Searching for Wrong Domain
          • Absent Local Naming Method
          • Missing Parenthesis
          • Connect Identifier Mismatch

          How To Fix ORA-12154: TNS:could not resolve the connect identifier specified?

          ora-12154 error

          Here, you will get to know the best ways to fix ORA-12154: TNS:could not resolve the connect identifier specified error based on the error message you get. All these solutions are very easy and effective that will definitely fix ora-12154 error.

          Error Message #1: ORA-12154 Due to Missing tnsnames.ora File

          When you deliberately deleted tnsnames.ora file for testing the effect, you get the message:

          C:UsersEd>dir /w %TNS_ADMIN%tnsnames.ora
          Volume in drive C has no label.
          Volume Serial Number is C4BB-3A0E

          Directory of C:appclientAdministratorproduct12.2.0client_1networkadmin

          File Not Found

          After getting this message, when you try to connect to the database, you get the below message:

          C:UsersEd>sqlplus /nolog

          SQL*Plus: Release 12.2.0.1.0 Production on Sat Jun 7 19:12:14 2019

          Copyright (c) 1982, 2017, Oracle.  All rights reserved.

          SQL> conn hr/hr@ORCL
          ERROR:
          ORA-12154: TNS:could not resolve the connect identifier specified

          You get these message because of the sqlplus found no file to lookup the connect identifier.

          Solution To Fix This Error:

          In order to fix this error, you can create a new tnsnames.ora or you can also restore the original one.

          C:UsersEd>dir /w %TNS_ADMIN%tnsnames.ora
          Volume in drive C has no label.
          Volume Serial Number is C4BB-3A0E

          Directory of C:appclientAdministratorproduct12.2.0client_1networkadmin

          tnsnames.ora
          1 File(s)            388 bytes
          0 Dir(s)  179,702,697,984 bytes free

          After doing so, you can again try to connect to the Oracle database:

          C:UsersEd>sqlplus /nolog

          SQL*Plus: Release 12.2.0.1.0 Production on Sat Jun 7 19:20:41 2019

          Copyright (c) 1982, 2017, Oracle.  All rights reserved.

          SQL> conn hr/hr@ORCL
          Connected.

          Error Message #2: ORA-12154 Due to Absent Local Naming Method

          When you set TNS_ADMIN environment variable explicitly, you try this:

          C:UsersEd>set TNS_ADMIN=C:appclientAdministratorproduct12.2.0client_1networkadmin

          Check the content of sqlnet.ora. There’s no TNSNAMES naming method.

          C:UsersEd>type %TNS_ADMIN%sqlnet.ora

          SQLNET.AUTHENTICATION_SERVICES= (NTS)
          NAMES.DIRECTORY_PATH= (EZCONNECT)

          After this, you try to connect to the database:

          C:UsersEd>sqlplus /nolog

          SQL*Plus: Release 12.2.0.1.0 Production on Sat Jun 7 19:02:33 2019

          Copyright (c) 1982, 2017, Oracle.  All rights reserved.

          SQL> conn hr/hr@ORCL
          ERROR:
          ORA-12154: TNS:could not resolve the connect identifier specified

          Here, you can get ora-12154 error in sqlplus because there is no TNSNAMES naming method available to support the connection.

          #1: Solution To Fix This Error: Add TNSNAMES Method

          You can fix ora-12154 error here by adding TNSNAMES method back to NAMES.DIRECTORY_PATH.

          C:UsersEd>type %TNS_ADMIN%sqlnet.ora

          SQLNET.AUTHENTICATION_SERVICES= (NTS)
          NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)

          Then we tried to connect to the database again.

          C:UsersEd>sqlplus /nolog

          SQL*Plus: Release 12.2.0.1.0 Production on Sat Jun 7 19:05:24 2019

          Copyright (c) 1982, 2017, Oracle.  All rights reserved.

          SQL> conn hr/hr@ORCL
          Connected.

          Using this way, you will be able to fix this ora-12154 error with ease.

          #2: Solution To Fix This Error: Easy Connect Naming Method

          You can also try connect naming method to fix ora-12154 error and connect to the database. For this, you have to make sure that you have EZCONNECT in the list of NAMES.DIRECTORY_PATH.

          If you don’t have then you will get ora-12154 like this and it will solve your problem soon:

          SQL> conn hr/hr@ora11g.example.com:1521/orcl
          ERROR:
          ORA-12154: TNS:could not resolve the connect identifier specified

          Error Message #3: ORA-12154 Due to Connect Identifier Mismatch

          If you changed the connect identifier while connecting the database using the method below then you can sometime get this error:

          SQL> conn hr/hr@ORCL123
          ERROR:
          ORA-12154: TNS:could not resolve the connect identifier specified

          Solution To Fix This Error

          If you get this error due to connect identifier mismatch then you can try the correct connect identifier so that you can connect to the database easily. To do so, you have to try the below query:

          SQL> conn hr/hr@ORCL
          Connected.

          It is always advisable that you should always use a matched identifier which also exists in tnsnames.ora.

          Error Message #4: ORA-12154 Due to Missing Parenthesis

          Sometimes it happens that you may not notice that there is one parenthesis that is missing from the connect descriptor; generally it is the right side one. You can take an entry in tnsnames.ora, as for example:

          ERPAPP =
          (DESCRIPTION =
          (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.42.21)(PORT = 1521))
          )
          (CONNECT_DATA =
          (SERVICE_NAME = ERPAPP)
          (SERVER = DEDICATED)
          )

          Have you found any error in the above entry? No…..but I have noticed that there is a single parenthesis missing. Even if the connect identifier is correct but its connect descriptor is not correct then it will cause ORA-12154 error in oracle.

          Solution To Fix This Error:

          You can try the below codes to fix ORA-12154 due to missing parenthesis:

           ERPAPP =
          (DESCRIPTION =
          (ADDRESS_LIST =
          (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.42.21)(PORT = 1521))
          )
          (CONNECT_DATA =
          (SERVICE_NAME = ERPAPP)
          (SERVER = DEDICATED)
          )
          )

          Using the above codes, the connect identifier is correct.

          Error Message #5: ORA-12154 Due to Searching for Wrong Domain

          There are some database environments that have been set to the default domain for search which may result ora-12154 error is there is some connect descriptor are configured wrong by these queries:

          C:UsersEd>type %TNS_ADMIN%sqlnet.ora

          SQLNET.AUTHENTICATION_SERVICES= (NTS)
          NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
          NAMES.DEFAULT_DOMAIN = example.com

          Then we tried to connect to the database.

          C:UsersEd>sqlplus /nolog

          SQL*Plus: Release 12.2.0.1.0 Production on Sat Jun 7 19:31:50 2019

          Copyright (c) 1982, 2017, Oracle.  All rights reserved.

          SQL> conn hr/hr@ORCL
          ERROR:
          ORA-12154: TNS:could not resolve the connect identifier specified

          Solution To Fix This Error

          If the ora-12154 error takes place due to wrong domain then you can turn off by connecting out NAMES.DEFAULT_DOMAIN by the following queries:

          C:UsersEd>type %TNS_ADMIN%sqlnet.ora

          SQLNET.AUTHENTICATION_SERVICES= (NTS)
          NAMES.DIRECTORY_PATH= (TNSNAMES, EZCONNECT)
          #NAMES.DEFAULT_DOMAIN = example.com

          After this, you can again try to connect to the database by following these queries:

          C:UsersEd>sqlplus /nolog

          SQL*Plus: Release 12.2.0.1.0 Production on Sat Jun 7 19:33:55 2019

          Copyright (c) 1982, 2017, Oracle.  All rights reserved.

          SQL> conn hr/hr@ORCL
          Connected.

          You will then see that it has been connected.

          Ultimate Solution: Fix ORA-12154 Error Using Oracle File Repair Tool

          Apart from all these fixes, if you are unable to fix ORA-12154: TNS:could not resolve the connect identifier specified you get due to any of the reasons mentioned above then just Oracle File Repair Tool. This tool has the capability to fix any kind of error you get while using Oracle database. Several reasons are there that may cause this error but now you can easily fix it by using this tool. It has great features that allow your oracle database to overcome any kind of error and get back the database easily as it was previously saved before. All you have to do is to download and install Oracle File Repair Tool and use the step by step guide and fix the Oracle database error easily.

          Steps To Fix ORA-12154 Error Using Oracle File Repair Tool

          Step 1: Search the Initial screen of Stellar Phoenix Oracle Recovery with a pop-up window showing options to select or search corrupt Oracle databases on your computer.1

          Step 2: Click Scan File to initiate the scan process after selecting the oracle database. The recoverable database objects get listed in left-side pane.

          2

          Step 3: Click an object to see its preview.

          3

          Step 4: Click Start Repair in the icon bar to start the repair process. A pop-up window is displayed which show the steps needed to perform further. Click next and continue.

          4

          Step 5: Give the user name, password and path of the blank database where you want to save the repaired database objects.

          5

          Step 6: Repairing and restoring various database objects after establishing a connection with blank oracle database.

          6

          Final Words

          If you ever get ORA-12154 error while connecting to the database then stop worrying and just try the solutions mentioned in the above section of this blog. Yes, all these solutions vary and are based on the causes due to which you get ORA-12154: TNS:could not resolve the connect identifier specified. Apart from this, if you find yourself unsuccessful in fixing this error then you can try Oracle File Repair Tool. This tool will help you get rid of ORA-12154 error easily. So, all the best to you….

          Jacob Martin is a technology enthusiast having experience of more than 4 years with great interest in database administration. He is expertise in related subjects like SQL database, Access, Oracle & others. Jacob has Master of Science (M.S) degree from the University of Dallas. He loves to write and provide solutions to people on database repair. Apart from this, he also loves to visit different countries in free time.

          Добавить комментарий