Re: Compiling Error in Imported Procedures

In article <bo.lu.3.04F1FE9E_at_m.cc.utah.edu>, Bo Lu <bo.lu_at_m.cc.utah.edu> wrote:
>Hi, Everyone
>
>We use Export/Import utility to backup user's objects. When we imported user's
>objects back to database, some of stored procedures that have arguments have
>compiling errors. We checked the source code of those imported procedures. It
>looks like that the arguments of the procedures are missing.
>Does anyone meet the same problems. Any suggestion will be appreciated.
>
>Bo Lu
>bo.lu_at_m.cc.utah.edu
>Department of Medical Informatics
>U. of Utah

One of my DBAs brought this up to me just this week. He says it's a known bug in one of the 7.0.xx releases for Novell. When a stored procedure is exported, the source code is somehow corrupted, and the procedure is unusable when imported. Your best option is to upgrade past this version.

Most of my systems are Unix-based, and I have not seen this problem yet (knock on wood). We're at 7.1.3.

Good Luck!

--
============================================================================
Mike Vergara           |   Be good...and you will be lonesome
vergara_at_nosc.mil       |                                       Jimmy Buffett
Opinions expressed are not necessarily those of anyone else but me.  So there.