ADSM-L

PROLE connection error

2005-10-12 10:34:06
Subject: PROLE connection error
From: Thomas Rupp <Thomas.Rupp AT ILLWERKE DOT AT>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Wed, 12 Oct 2005 16:33:28 +0200
Hi TSM-ers,

I installed TDP for mySAP 3.3 on a Windows 2003 machine.
Backups were running fine until I tried to connect to the Administration
Assistant.
I used "prole -update hostname 5126" to update the configuration
accoring to the install docu.
Now I get the following errors even after rebooting the system.

Can anybody give a hint where to start searching? I couldn't find any
errormessages in
the tsm log files or eventlog.

Thanks in advance
Thomas Rupp

BR0002I BRARCHIVE 6.40 (34)
BR0006I Start of offline redo log processing: adrawdcj.cds 2005-10-12
14.18.01
BR0477I Oracle pfile D:\oracle\VT2\920\database\initVT2.ora created from
spfile D:\oracle\VT2\920\database\spfileVT2.ora

BR0280I BRARCHIVE time stamp: 2005-10-12 14.18.04
BR0008I Offline redo log processing for database instance: VT2
BR0009I BRARCHIVE action ID: adrawdcj
BR0010I BRARCHIVE function ID: cds
BR0048I Archive function: copy_delete_save
BR0011I 14 offline redo log files found for processing, total size
634.229 MB
BR0130I Backup device type: util_file
BR0109I Files will be saved by backup utility
BR0126I Unattended mode active - no operator confirmation required

BR0280I BRARCHIVE time stamp: 2005-10-12 14.18.04
BR0229I Calling backup utility with function 'backup'...
BR0278I Command output of 'I:\usr\sap\VT2\SYS\exe\run\backint.exe -u VT2
-f backup -i G:\oracle\VT2\saparch\.adrawdcj.lst -t file -p
D:\oracle\VT2\920\database\initVT2.utl -c':

                  Data Protection for mySAP.com(R) technology

         Interface between SAPDBA Utilities and Tivoli Storage Manager
               - Version 3, Release 3, Modification 10  for WinNT -
                 Build: 219  compiled on Dec  4 2003
        (c) Copyright IBM Corporation, 1996, 2003, All Rights Reserved.

BKI2001E: Socket error while connecting to PROLE at localhost:57321: No
connection could be made because the target machine actively refused it.

<Prev in Thread] Current Thread [Next in Thread>
  • PROLE connection error, Thomas Rupp <=