ABS and Oracle

[Jiri Koutnik]

Hi,
my favorite area is to Integrate Oracle to some backup management system, running on OpenVMS.
now its time for ABS.
OpenVMS - version 7.3-2, last patch UPDATE7
Oracle - version 9.2.0.5
ABS and MDSM - version V4.3a(800)

but it still doesnt work, even the sbttest run successfully !!!

error:
those command just hang
any idea whats wrong ?

Jiri

run
{
allocate channel t1 type 'sbt_tape'
parms="SBT_LIBRARY=abs_sbt,
ENV=(MDMS$SBT_ARCHIVE=REG_RMAN_ARCH,
MDMS$SBT_IO_BLOCK_SIZE=65024)";
backup filesperset 4database;
release channel t1;
}

neither this:

run
{
allocate channel t1 type 'sbt_tape'
parms="SBT_LIBRARY=abs_sbt,
ENV=(MDMS$SBT_ARCHIVE=REG_RMAN_ARCH)";
release channel t1;
}

neither this:

run
{
allocate channel t1 type 'sbt_tape' parms="SBT_LIBRARY=abs_sbt";
release channel t1;
}

[Jiri_5]

Hello,
check ora_dump:sbtio.log for errors;

You can set higher trace level - check documentation of ABS


OpenVMS 7.3-2
RDBMS 9207(before 9205, 8174,8173).
SBT-366E7ECA 08/31/06 12:48:08 System Backup to Tape V4.3A (800)

You must define:
$define/sys abs_sbt SYS$SHARE:MDMS$SBTSHR_MA64_9I2.EXE

We always define archive and catalog(I think documentation also allows define this as logical name in the begining of the DCL script, not in rman script) in rman script.

We use "sbt_tape" instead of 'sbt_tape' - may be it's ok, I didn't test it.

If sbttest works - it means archive, catalog and tapes are ok.

We had problem in the past with number and size of files - we got only common error - now we use fileperset 1(or you can use: set limit channel ch1 kbytes=2000000 )
.
Names of catalog and archive are in rman script case sensitive.

[Jiri Koutnik]

Hi,

I just cannot allocate the SBT_LIBRARY !
ora_dump:sbtio.log doesnt exist, probably its created at first (UN}successfull usage of SBT_LIBRARY :-)
abs_sbt is defined correctly.

but Im afraid, it still doesnt work :(
the command (allocate channel...) just hangs
no touch to the SBT_LIBRARY.

any futher guess ?

thanx Jiri

[Jiri Koutnik]

The whole problem was mishmash with Domain names. First I corrected domain in TCPIP, then put the correct domain to the TNSNAME.ora and LISTENER.ora, change lognames MDMS$DATABASE_SERVERS using correct Domain name, restart MDMS and database.
After that all seems to be alright :-)

Jiri