Forum Discussion

tetsu_o's avatar
tetsu_o
Level 2
2 years ago

BE 22 Oracle DB backup with remote agent for Windows failed with ORA-12541 TNS:no listener

Hello there,

We have an issue with Oracle DB backup via remote agent.

We recently upgraded Backup Exec server and agent from 14 to 22.
Although we are not sure if this upgrade is causing the issue.

Here is our situation.

1. System overview
[Backup Exec server]
Windows Server 2012 R2
Backup Exec Server 22.1 Rev. 1193

[Backup target server]
Windows Server 2012 R2
Oracle 12c (12.2.0.1.0) *non-CDB database
Backup Exec Remote Agent for Windows 22.0.1193

2. File system backup with RAW works fine.
3. Oracle DB backup with RAW have an error. Backup job error is "ORA-12541 TNS:no listener" in RMAN step.
*#2 and #3 is same target server.

Here is a sample of the backup job log.

---
Recovery Manager: Release 12.2.0.1.0 - Production on Sun Aug 20 13:11:25 2023

Copyright (c) 1982, 2017, Oracle and/or its affiliates. All rights reserved.


RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
ORA-12541: TNS:no listener



# -----------------------------------------------------------------
# RMAN command section
# -----------------------------------------------------------------

RUN {

SET CONTROLFILE AUTOBACKUP FORMAT FOR DEVICE TYPE SBT_TAPE TO 'BE_';
ALLOCATE CHANNEL ch0
TYPE 'SBT_TAPE';
SEND 'BSA_SERVICE_HOST=10.96.66.140,NBBSA_TOTAL_STREAMS=1,NBBSA_JOB_COOKIE={85F33C79-D4EC-4270-8336-EFDAC8A23C85},NBBSA_DB_DEVICE_NAME=Oracle-Win::\\NYKQWORA1.america.sumitomocorp.com\NYKQWORA1';
BACKUP
INCREMENTAL LEVEL=0
FORMAT 'BE_'
DATABASE FORCE PLUS ARCHIVELOG FORCE NOT BACKED UP DELETE INPUT;
BACKUP CURRENT CONTROLFILE
FORMAT 'BE_';

RELEASE CHANNEL ch0;
}
executing command: SET CONTROLFILE AUTOBACKUP FORMAT

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of allocate command at 08/20/2023 13:11:55
RMAN-06171: not connected to target database

EXIT

Recovery Manager complete.
---

4. In the Oracle backup job, Credential test is OK, and backup selection is accessible. I can see the tablespace and archive log files. So, I think communication between BE server and agent is OK.
5. Oracle DB user that defined at "Oracle" tab in the agent has following plivileges.

ALTER ROLLBACK SEGMENT
ALTER SYSTEM
ALTER DATABASE
SELECT ANY TABLE
ALTER TABLESPACE
SYSBACKUP

6. OS user (which is also used as backup job user credential) that defined in the "Database Access" is assigned to the DB server's local groups.
Administrators
ora_dba
ORA_OraDB12Home1_SYSBACKUP

7. DB connection from RMAN and sqlplus with user (Oracle user as above #5 and OS user above #6) works on the Oracle server.
I have no idea why backup job has error "ORA-12541 TNS:no listener", even those connection tests were OK.


Please kindly give me any advise.
Your help much appreciated.

22
Oracle 12c
Windows Server 2012 R2
  • RogRubin's avatar
    RogRubin
    Moderator
    2 years ago

    This error is more likely something on the Oracle or System site then an issue with BE itself.

    You can run the following command to see what the status of the listener is:
    lsnrctl status

    I would assume that is all fine but if not then this is the issue.

    If the status is all fine then it might be related to Environmental variables where the Oracle Home path is not everywhere correctly defined especially in the "path" variables.
    or
    that tnsnames.ora and listener.ora have different information defined.

    IMPORTANT
    Please do not change any values in tnsnames.ora and listener.ora without approval from your DBA.

  • tetsu_o's avatar
    tetsu_o
    Level 2
    2 years ago

    Hello RogRubin,

    Thank you very much for your advice.

    As you expected, listener status is normal.
    DB access is perfectly fine at DB server's OS level.

    Fortunately, we got technical support this morning, and we have learned that we need to create "Oracle DB account" as credential on Backup Exec server and select it as logon credentials in the backup job. That is all.

    According to technical support, this design has changed from version 20.
    We came from version 14, and we were not very careful and unaware about this.
    It seems that in previous BE version’s backup job worked, although it was not quite correct, but the new version required the correct settings.

    Anyway, Oracle backup is now works perfectly.

    Again, thanks for your help.