No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>


To have a better experience, please upgrade your IE browser.


Oracle XML Fails to Be Exported and Error Message "ORA-12154: TNS: could not resolve the connect identifier specified" Is Displayed

Publication Date:  2015-07-29 Views:  113 Downloads:  0
Issue Description
The following table lists the information about the product and version, and data related to this case.

When the script is exported by using the Oracle XML, exporting the backup job of the Oracle database fails and the error message the backup failed to back up the requested files, status code 6 is displayed.

The specified configuration file in the script exported by Oracle XML is bporaexp_tables.param. The exported log is stored in the bporaexp_tables.log file.
Handling Process
1.  Change the password of the user backup. Ensure that the new password does not contain @.

2.  Update parameter values of USERID in the bporaexp_tables.param configuration file.

3.  Perform the backup job again.
Root Cause
Possible Causes:

The instance name of Oracle database is incorrect.

Fault Diagnosis:

1.  The instance name of the Oracle database is delivered to the database by USERID in the bporaexp_tables.param configuration file.

USERID is in the format of username/password@sid_name. The parameters are as follows:
  • username in front of / is the user name for backup.
  • The field from / to @ is the password of the user.
  • @sid_name is optional. sid_name is the instance name of Oracle database.
2.  After the bporaexp_tables.log log file is checked, it is found that the record information about USERID is backup/*******@#.

The user name in the configuration file is backup. The field from / to @ is the password. The instance name is #.

3.  The actual instance name of Oracle database is ora11g rather than #. Therefore, the field behind / in USERID of the original configuration file is the password of user backup. The password contains @.

To sum up, the problem occurs because the password of the user backup contains @.
The password of the user name for XML exporting and importing of the Oracle database cannot contain @. Otherwise, use another user name or change the password.