| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3028.1 | Is there a DECEDI_PC.MMF already ? | UTRTSC::SMEETS | Workgroup support | Tue Feb 25 1997 10:01 | 15 |
| Hello Hooi,
Is there in /var/adm/decedi/data a file called DECEDI_PC.MMF ?
If not, perform as root
1. decedi_stop
2. /usr/sbin/decedi_pcc -> this will create an empty DECEDI_PC.MMF
3. decedi_start
After this you should try to build the cache via the CC.
Hope this helps,
Martin
|
| 3028.2 | hostname changed | MSAM03::HOOICHING | SWS Dept Malaysia | Wed Feb 26 1997 15:51 | 14 |
|
Hi Martin,
Thank you for your response.
We could build cache previously. We believe the ORA error could be due to
the server hostname being changed. From CC, we made changes to reflect
the new hostname. However, in the Oracle database (which we query from
Oracle tools) still have entries of the old hostname.
Is there a pre-defined procedure to handle this ?
Regards,
Hooi Ching
|
| 3028.3 | | METSYS::THOMPSON | | Wed Feb 26 1997 18:27 | 20 |
| Hooi,
this is the DEC/EDI Notes conference, it's not a natural place to find
information about how to manage an Oracle 7 Database. There is an Oracle
Notes file, eps::oracle, where you may find some oracle experts lurking.
The primary source should be Oracle Corporation themselves.
All we can advise upon is how DEC/EDI uses the Database.
What exactly was done to this system? Was it just a nodename change of the
system that was already running?
Have you just backed up some disks and moved them to another system?
> SQLERROR (e), SQL error: SQLCODE = -1466 : ORA-01466:
> unable to read data - table definition has changed.
Have there been any upgrades to dec/edi recently?
Mark
|
| 3028.4 | | METSYS::THOMPSON | | Wed Feb 26 1997 18:38 | 37 |
|
From the manual:
ORA-01466 unable to read data - object definition has changed
Cause:
This is a time-based read consistency error for a database object, such
as a table or index. Either of the following may have happened:
o the query was parsed and executed with a snapshot older than the time
the object was changed.
o the creation time-stamp of the object is greater than the current
system time. This can happen if system time is set to a time earlier
than the creation of the object
If the object creation time-stamp is greater than system time, then
export the object's data, drop the object, re-create the object. import
objects data.
-----------
mrt comment.
Call Oracle first.
If nothing else clears this:
1. Export all data from the database
2. re-create the database
3. Import the data you saved earlier.
Call back here before you try this though!
Mark
|
| 3028.5 | | MSAM03::HOOICHING | SWS Dept Malaysia | Thu Feb 27 1997 10:35 | 9 |
|
In the process of trying to locate and fix the problem, we encountered
more problems. We decided to re-install the system and it is OK now.
Thank you all for your input.
Regards,
Hooi Ching
|