Hello
I have a problem which looks like yours
Before Y2000, I have upgraded obsi to version 2.5 without problem.
I'm working on a desaster recovery plan. After restoring on a test server (Sun
Solaris) all the files saved from the production server, reinstalling and
customizing the SQLBT programs with the CPU ID
I am not able to restore a database. Reason: ADSM message Objet doesn't exist
on server.
After tracing network traffic with command snoop, I see a difference between
production and test server.
Production server ask for an objet /BACKTRACK/xxxxxxxxx/xx.01234567
Test server ask for an objet /BACKTRACK/xxxxxxxxx/xx.01234567oracle
In ADSM API programming manual a backup objet is defined by:
filespace name ex /BACKTRACK
hl name(directory) ex control_files
ll name (filename) ex system.dbf.0123456
owner ex oracle
I have found a workaround to force owner field to blank in the obsi by adding
the line
owner=
in the file oracatalog/poolinfo/POOLS before
end backup_pool
In France SQLBT support doesn't know ADSM.
Hope this help
Alain Ricois
email [EMAIL PROTECTED]
____________________Séparateur de messages____________________
Objet : Re: SQL-Backtrack OBSI Module (via TSM API) for Oracle -vers
Auteur : "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
Date : 12/03/2001 21:49
Hi all
We've been using SQL-Backtrack for Sybase and Oracle for 4+ years. And
recently:
Upgrading the obsi to v2.5 yielded a non functioning system. BMC
personnel, after spending 3 days trying to dial into our system (got warm
fuzzies just with that alone) did manage to get their stuff to work BUT....
They don't seem to be able to support PASSWORDACCESS Generate
They strongly felt they needed to create a new client node to contain the
backtrack info and were unable to use the nodename (hostname) of the
machine from where the databases reside. Further they didn't understand
the impact of a nodename change (we use colocation, and they wouldn't be
able to restore any old SQL backups)
They claim they don't support TSM4.1.2
They could not understand what client option sets were
They want us to change ownership of the generated password file away from
root to they could read it.
Calls to support are indeed frustrating. Where it my choice, I'd move to
another method ASAP.
Al Barth
"Mark A. Adams"
<mark_adams@CSGSY To: [EMAIL PROTECTED]
STEMS.COM> cc:
Sent by: "ADSM: Subject: Re: SQL-Backtrack
OBSI
Module (via TSM API) for Oracle
Dist Stor -versus- TSM TDP for Oracle
Manager"
<[EMAIL PROTECTED]
.EDU>
03/12/01 10:38 AM
Please respond to
"ADSM: Dist Stor
Manager"
We have been using SQL-Backtrack for 3 years now.
We like it very well. Yes, it will do hot backups.
SQL-Backtrack backs up directly to TSM using the API interface.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of
Larry Girardi
Sent: Friday, March 09, 2001 11:30 AM
To: [EMAIL PROTECTED]
Subject: SQL-Backtrack OBSI Module (via TSM API) for Oracle -versus- TSM
TDP for Oracle
People,
I am wondering if anyone has any experience with this stuff.
I am really interested in both Oracle and SQL Server!
1) Does SQL-Backtrack backup directly into TSM without having to use/buy
the
TSM TDP for Oracle/SQL Server ?
2) Can you do a HOT backup of the Oracle/SQL Server database ?
3) Is it slick ... does it work well ?
Thank you, Larry
**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
[EMAIL PROTECTED]
**********************************************************************
Unknown data type
