| Title: | The Replication Option for Rdb |
| Notice: | Product renamed to Replication Option for Rdb |
| Moderator: | BROKE::PROTEAU |
| Created: | Wed Mar 02 1994 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 287 |
| Total number of notes: | 1231 |
Hi,
I just wonder if anyone have come across with the same problem
with Data Distributor RDB$TRANSACTION_TSER table. Here are
the note stream on RDB_6 notesfile #4310. Any comment from Data
Distributor Engineering?
Thanks,
Michael.
<<< nomahs::DISK$NOMAHS1:[NOTES$LIBRARY]RDB_60.NOTE;1 >>>
-< Oracle Rdb - Still a strategic database for DEC on Alpha AXP! >-
================================================================================
Note 4310.0 column RDB$TRANSACTION_TSER %SQL-F-FLDNOTCR. 3 replies
svrav1.au.oracle.com::MCHAN 64 lines 22-JUL-1996 00:59
--------------------------------------------------------------------------------
Rdb V6.1-13
DDD V6
A customer have problem extract the information in the Data Distributor
RDB$CHANGES_MAX_TSER tables getting error message:
%SQL-F-FLDNOTCRS, Column RDB$TRANSACTION_TSER was not
found in the tables in current scope
Customer reckons it worked fine before on Rdb V4.2 .
Is this a known problem?
Thanks,
Michael.
-------------------------------------------------------------------------------
$ SQL
AT 'FI SN_MST_WHO_RGN_DATABASE';
SET TRANS READ ONLY;
SHO TAB RDB$CHANGES_MAX_TSER
Information for table RDB$CHANGES_MAX_TSER
Columns for table RDB$CHANGES_MAX_TSER:
Domain
------
No columns Found
Table constraints for RDB$CHANGES_MAX_TSER:
No constraints found
Constraints referencing table RDB$CHANGES_MAX_TSER:
No constraints found
Indexes on table RDB$CHANGES_MAX_TSER:
No indexes found
Storage Map for table RDB$CHANGES_MAX_TSER:
No Storage Map found
Triggers on table RDB$CHANGES_MAX_TSER:
No triggers found
SEL RDB$RELATION_NAME,RDB$FIELD_NAME FROM RDB$RELATION_FIELDS WHERE
RDB$RELATION_NAME = 'RDB$CHANGES_MAX_TSER';
RDB$RELATION_NAME RDB$FIELD_NAME
RDB$CHANGES_MAX_TSER RDB$TRANSACTION_TSER
1 row selected
SEL RDB$TRANSACTION_TSER FROM RDB$CHANGES_MAX_TSER;
%SQL-F-FLDNOTCRS, Column RDB$TRANSACTION_TSER was not
found in the tables in current scope
sel * from rdb$changes_max_tser;
1 row selected
-------------------------------------------------------------------------------
================================================================================
Note 4310.1 column RDB$TRANSACTION_TSER %SQL-F-FLDNOTCR. 1 of 3
NOVA::SMITHI "Don't understate or underestimate Rdb" 29 lines 22-JUL-1996 09:02
--------------------------------------------------------------------------------
How did they get from V4.2 to V6.1? Did they RMU Convert, Export, etc.
You need to show us more information from the system table:
select *
from rdb$relations
where rdb$relation_name='RDB$CHANGES_MAX_TSER';
select *
from rdb$relation_fields
where rdb$relation_name='RDB$CHANGES_MAX_TSER';
select *
from rdb$field_versions
where rdb$relation_id = (select rdb$relation_id
from rdb$relations
where rdb$relation_name='RDB$CHANGES_MAX_TSER');
select *
from rdb$fields
where rdb$field_name = (select rdb$field_source
from rdb$relation_fields
where rdb$relation_name='RDB$CHANGES_MAX_TSER');
This should help see what is wrong.
thanks,
Ian
================================================================================
Note 4310.2 column RDB$TRANSACTION_TSER %SQL-F-FLDNOTCR. 2 of 3
svrav1.au.oracle.com::MCHAN 95 lines 23-JUL-1996 18:35
-< SQL queries output. >-
--------------------------------------------------------------------------------
Ian,
Customer used RMU/CONVERT to go from 4.2 to 6.1. The output from the
SQL queries follow:
SEL * FROM RDB$RELATIONS
WHERE RDB$RELATION_NAME = 'RDB$CHANGES_MAX_TSER';
RDB$RELATION_NAME RDB$RELATION_ID RDB$STORAGE_ID
RDB$SYSTEM_FLAG RDB$DBKEY_LENGTH RDB$MAX_VERSION
RDB$CARDINALITY
RDB$FLAGS RDB$VIEW_BLR RDB$DESCRIPTION
RDB$VIEW_SOURCE RDB$ACCESS_CONTROL
RDB$EXTENSION_PARAMETERS RDB$CDD_NAME
RDBVMS$SECURITY_AUDIT RDBVMS$SECURITY_ALARM
RDB$SECURITY_CLASS RDBVMS$SECURITY_AUDIT2
RDBVMS$SECURITY_ALARM2
RDB$CHANGES_MAX_TSER 316 706
1 8 1
1
2 NULL NULL
NULL 1:12:59
1:12:57 NULL
0 0
NULL
0
1 row selected
SEL * FROM RDB$RELATION_FIELDS
WHERE RDB$RELATION_NAME = 'RDB$CHANGES_MAX_TSER';
RDB$RELATION_NAME RDB$FIELD_NAME
RDB$FIELD_SOURCE RDB$FIELD_ID RDB$FIELD_POSITION
RDB$QUERY_NAME RDB$UPDATE_FLAG
RDB$QUERY_HEADER
RDB$DESCRIPTION RDB$VIEW_CONTEXT
RDB$BASE_FIELD RDB$DEFAULT_VALUE
RDB$EDIT_STRING
RDB$EXTENSION_PARAMETERS RDB$ACCESS_CONTROL
RDB$DEFAULT_VALUE2 RDBVMS$SECURITY_AUDIT
RDBVMS$SECURITY_ALARM RDB$SECURITY_CLASS
RDB$CHANGES_MAX_TSER RDB$TRANSACTION_TSER
RDB$TRANSACTION_TSER 1 1
NULL 1 NULL
NULL 0
NULL
NULL
>>
>>
>>
>>
NULL NULL
NULL 0
0 NULL
1 row selected
SEL * FROM RDB$FIELD_VERSIONS
WHERE RDB$RELATION_ID = (SELECT RDB$RELATION_ID
FROM RDB$RELATIONS
WHERE RDB$RELATION_NAME = 'RDB$CHANGES_MAX_TSER');
RDB$RELATION_ID RDB$FIELD_ID RDB$FIELD_NAME
RDB$VERSION
RDB$FIELD_TYPE RDB$FIELD_LENGTH RDB$OFFSET RDB$FIELD_SCALE
RDB$FLAGS RDB$VALIDATION_BLR RDB$COMPUTED_BLR
RDB$MISSING_VALUE RDB$SEGMENT_LENGTH
RDBVMS$COLLATION_NAME RDB$ACCESS_CONTROL
RDB$DEFAULT_VALUE2 RDBVMS$SECURITY_AUDIT
RDBVMS$SECURITY_ALARM RDB$FIELD_SUB_TYPE
RDB$SECURITY_CLASS
316 1 RDB$TRANSACTION_TSER
1
8 4 2 0
0 NULL NULL
1:12:58 0
NULL
NULL 0
0 0
NULL
1 row selected
SEL * FROM RDB$FIELDS
WHERE RDB$FIELD_NAME = (SELECT RDB$FIELD_SOURCE
FROM RDB$RELATION_FIELDS
WHERE RDB$RELATION_NAME = 'RDB$CHANGES_MAX_TSER');
0 rows selected
================================================================================
Note 4310.3 column RDB$TRANSACTION_TSER %SQL-F-FLDNOTCR. 3 of 3
NOVA::SMITHI "Don't understate or underestimate Rdb" 15 lines 24-JUL-1996 11:53
--------------------------------------------------------------------------------
Huh? There is no domain called RDB$TRANSACTION_TSER.
SEL * FROM RDB$FIELDS
WHERE RDB$FIELD_NAME = (SELECT RDB$FIELD_SOURCE
FROM RDB$RELATION_FIELDS
WHERE RDB$RELATION_NAME = 'RDB$CHANGES_MAX_TSER');
0 rows selected
This is the problem. It looks like the RMU/CONVERT dropped the domain. Try
creating it my hand.
Also ask in the DATA_DISTRIBUTOR notes conference.
Ian
-------------------------------------------------------------------------------
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 230.1 | I haven't seen this as a problem before now | BROKE::PROTEAU | Jean-Claude Proteau | Thu Jul 25 1996 12:01 | 12 |
I don't recall having heard of this as a problem with other customers.
But then again, I don't know how many have converted from the one
version to the other by skipping versions in between. I assume it's
common enough to do, but I have no first hand knowledge.
It indeed appears that the domain for the tser column has disappeared.
Right now it would seem to be an error in RMU/CONVERT. As Ian
suggested, do some tests yourself to see if the problem can be
corrected by hand before asking the customer to do so.
Claude
| |||||
| 230.2 | RDB$TRANSACTION_TSER column definition? | svrav1.au.oracle.com::MCHAN | Thu Jul 25 1996 22:07 | 9 | |
Hi Claude,
Any idea how to re-define the RDB$TRANSACTION_TSER column?
I'm afraid we dont have the old database anymore.
Thanks,
Michael.
| |||||
| 230.3 | he column/domain definition | BROKE::PROTEAU | Jean-Claude Proteau | Mon Jul 29 1996 12:24 | 7 |
The RDB$TRANSACTION_TSER column and domain are defined as
datatype INTEGER
Comment: Highest TSER value yet defined
Missing Value: -1
| |||||
| 230.4 | create a new database. | svrav1.au.oracle.com::MCHAN | Mon Jul 29 1996 19:25 | 7 | |
As we're not sure what else is missing after RMU/CONVERT of the
database. Customer agreed to create a new transfer database and
its now back to normal.
Cheers,
Michael.
| |||||