ADSM-L

Re: SQL Connect agent errors ...

1998-09-01 04:04:24
Subject: Re: SQL Connect agent errors ...
From: Christo Heuer <christoh AT ABSA.CO DOT ZA>
Date: Tue, 1 Sep 1998 10:04:24 +0200
Hi Del,

Thanks for the quick reply - it turned out to be the
"Wait for Tape Mounts" option that was not set.

Talk about misleading...

Thanks again for the response - my client is very
happy again.

Regards
Christo Heuer


>Christo,
>
>The error message is quite misleading in this case.
>
>It actually has nothing to do with the database format.
>This error is caused by the fact that the ADSM connection
>is failing for some reason.   The DB-LIB message is just
>a "cascaded" error from the ANS0332E rc306 error message
>which indicates a communication problem with the ADSM Server.
>
>- First, make sure you can communicate with the ADSM Server
>  from the SQL Agent by doing a query or simple backup.
>  This will verify that the options file is set up correctly.
>
>- Make sure that you have the "Wait for Tape Mounts" option
>  checked in the SQL Agent Options Editor for the
>  ADSM Server that you are trying to connect to.
>  This is important if the backup is on tape or
>  was migrated to tape from disk.
>
>- Try the restore again.
>
>By the way, there is no need to do an uninstall of the Try and Buy.
>The "Paid" version will only overwrite the needed files
>to upgrade your license to the "Paid" license.
>
>-------------------------
>Del Hoobler
>IBM ADSM Agent Development
>hoobler AT us.ibm DOT com
>
>
>===============================================
>
>>> Hi,
>>>
>>> Has anyone seen the following error with the NT SQL connect agent?
>>>
>>> ANS0332E rc306: no text available for this return code. DB-LIB
>>> message:specified file
>>> \\.\pipe\sqladsm\1998065232\21 is in a obsolete dump database format:
ver1
>>> expected ver7.
>>>
>>> Has anyone seen something like this before - any ideas what could be
causing
>>> this?
>>>
>>> We installed the Try&Buy version at first and after that we tested and
when
>>> the SQL dba
>>> was happy we installed the Full retail version. We did a de-install of
the
>>> try & buy and
>>> installed the new version - the machine has been re-booted since.
>>>
>>> Any ideas welcome - This system will be going live tommorrow... maybe
>>> without Adsm and
>>> the connect agent by the looks of this.
>>>
>>> Thanks
>>> Christo
<Prev in Thread] Current Thread [Next in Thread>
  • Re: SQL Connect agent errors ..., Christo Heuer <=