Title: | DEC RdbExpert for OpenVMS |
Notice: | RdbExpert V2.1A is now available - See note 2.4 |
Moderator: | OOTOOL::CRAIG |
Created: | Fri Jul 10 1992 |
Last Modified: | Tue Jun 03 1997 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 755 |
Total number of notes: | 2761 |
Hi, Our customer is getting the error: %RDBX-E-NOOBJEXISTS, the ENTRY was not found on generating a physical schema using Rdb Expert V3.0-1. I read in note 612 about a bug that produce the same error and was fixed in versions after V2.1A. Is the problem described in note 612 fixed in the customer's version (V3.0-1) or I am simply missing something here? thanks, albert. Note: The steps made to reproduce the problem are described below. -------------------------------------------------------------------- $ collect schedule collection rdb_collection_1 rdb_collection_1.dat - /selection=rdb_selection - /beginning=10:30 - /ending=10:45 - /flush_interval=(00:00:02) - /cluster - /collection_files=(protection=(w:rw)) $ collect format /type=rdbvms rdb_collection_1.dat rdb_collection_1.rdb $ rdbexpert / inter=char ORACLEX> ORACLEX> create/open directory mbns ; ORACLEX> create conceptual_design mbns_con ; ORACLEX> create logical_design mbns_con.logdes ; ORACLEX> import logical_schema mbns_con.logdes.logsch from database wizard_data ; or ORACLEX> import logical_schema mbns_con.logdes.logsch from database product rdb 6.1 ; ORACLEX> create physical_design mbns_con.logdes.phydes ; ORACLEX> import workload mbns_con.logdes.phydes from oracle trace rdb_collection_1.rdb ; ORACLEX> import volume mbns_con.logdes.phydes from database wizard_data ; ORACLEX> import environment mbns_con.logdes.phydes from pdl mbns_environment.pdl ; ORACLEX> generate physical_schema mbns_con.logdes.phydes ; %RDBX-E-NOOBJEXISTS, the ENTRY was not found
T.R | Title | User | Personal Name | Date | Lines |
---|---|---|---|---|---|
737.1 | OOTOOL::GUAY | Oracle Expert, 1-2499 | Tue Apr 01 1997 16:37 | 13 | |
Hi Albert, this is a fairly generic error message that occurs when Expert attempts to select an object during rule evaluation and the object isn't found. These tend to be internal problems in the rules. I know of several cases where this was reported and fixed for 3.1. Do you have the latest kit? thanks, todd |