Oracle 11g先装64位再装32位后，找不到安装路径下的NETWORK\ADMIN文件夹

Hey there! I’ve run into this exact scenario a few times—installing 64-bit Oracle 11g first, then adding the 32-bit version, and realizing the critical NETWORK\ADMIN folder is nowhere to be found. Let’s walk through how to resolve this step by step:

• First, track down your Oracle Home paths
  By default, your 64-bit installation will live in a path like C:\app\<YourUsername>\product\11.2.0\dbhome_1. The 32-bit version (installed later) will likely be in a similar directory with a different suffix, e.g., dbhome_2. Navigate to each Oracle Home folder to confirm their locations.

• Manually create the NETWORK\ADMIN folder
  Oracle’s installer sometimes skips generating this folder for secondary installations, especially when mixing 32 and 64-bit versions. For both your 64-bit and 32-bit Oracle Home directories:

  1. Inside the main Oracle Home folder, create a new folder named NETWORK.
  2. Inside the NETWORK folder, create a subfolder named ADMIN.

• Set up your TNS configuration files
  If your 64-bit installation already has working tnsnames.ora and listener.ora files, just copy them from the 64-bit ADMIN folder to the 32-bit one. If you don’t have existing files, create a basic tnsnames.ora in the 32-bit ADMIN folder with content like this:

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

  Adjust the HOST, PORT, and SERVICE_NAME to match your actual database setup.

• Configure the TNS_ADMIN environment variable
  To avoid confusion between 32/64-bit setups, set a system environment variable named TNS_ADMIN that points to the ADMIN folder you just created (e.g., C:\app\<YourUsername>\product\11.2.0\dbhome_2\NETWORK\ADMIN). This overrides the default path and ensures both Oracle versions use the correct configuration.

• Test your connection
  Open the 32-bit SQL*Plus (found in your 32-bit Oracle Home’s bin folder) and run a test command like:

  sqlplus your_username/your_password@ORCL
  

  If it connects successfully, you’re good to go!

This issue pops up because the installer doesn’t always handle multi-version (32/64-bit) setups seamlessly, but manual setup fixes it in no time.

内容的提问来源于stack exchange，提问作者NidhinSPradeep