Stored Procedures Failed to import due to dependancy non-existenc

I had a client who lost two databases (live and archive); The Primary job was to restore their live database and get the users backup and running; and the method their dba employed was to restore from a logical backup (import). However, although all the objects restored okay to that single point in time, many of the Stored Procedires (SP's) failed too.

The reason? Well thats becuase the SP's referenced the archive database via a link. The import log file kindly informs you that the SP failed, but to my way of thinking, really Oracle should load this SP in, but mark as invalid. Is this a "feature" or should someother flag have been used on the import(??!!) to dicate as such?

Remember this, when you create an SP with links to a non-existent database, this SP will fail to compile (as it should) but you can still save it down into the schema.

Cheers, Received on Fri Jan 12 2001 - 08:43:47 CST