T.R | Title | User | Personal Name | Date | Lines |
---|
2624.1 | cdd path specification | NOVA::MJOHNSON | Mark Johnson, Oracle Rdb, Nashua, N.H. | Mon May 05 1997 16:33 | 3 |
| what cdd pathname is being specified (/PATHNAME or CDD$DEFAULT logical)
to the ddl/generate command line?
|
2624.2 | looks like a problem... | NOVA::PCHARLAN | ORACLE CODASYL DBMS Engineering | Mon May 05 1997 17:40 | 6 |
| We'll look into this (I can reproduce it), but can you please BUG it?
In the meantime, you can try defining CDD$DEFAULT to be the pathname, then just use the schema name on the command
line (rather than the full pathname). This may work for you, it did for me with the PARTS db.
paul
|
2624.3 | Thank You... | M5::BLITTIN | | Mon May 05 1997 18:18 | 13 |
|
re: .1
Believe we tried both, but I'll verify this...
re: .2
What did you do to reproduce this? I will bug it and try you
suggestion.
Thank You,
Bob
|
2624.4 | Workaround successful... | M5::BLITTIN | | Tue May 06 1997 11:20 | 11 |
|
Tried the workaround, define cdd$default device:[dir]manman.mandb, and
did ddl/generate/default=(subschema) mandb. This worked, to the
customer's delight...
Thank you from the customer...and me!
Bob
I will bug this...
|
2624.5 | Reproducible - Yes | M5::BLITTIN | | Tue May 06 1997 11:29 | 3 |
|
Finally figured out what is happening and was able to reproduce the
behavior. Will bug this.
|
2624.6 | BUGGED: 488723 | M5::BLITTIN | | Tue May 06 1997 12:00 | 2 |
|
BUGGED: 488723
|
2624.7 | BUGDBA problem... | M5::BLITTIN | | Tue May 06 1997 16:22 | 3 |
|
Not sure if this bug got logged correctly. A query in the bugdb
doesn't return anything. I have sent a note to the bugdba folks.
|
2624.8 | BUGDBA Down? | M5::BLITTIN | | Thu May 08 1997 12:31 | 4 |
|
Doesn't appear that the BUGDBA is working. I can't submit a bug via
this process. I have sent mail to BUGDBA and have not heard anything
back from them.
|
2624.9 | BUGGED 497479 | M5::BLITTIN | | Fri May 23 1997 15:19 | 3 |
|
BUGGED 497479
|
2624.10 | ...and fixed | NOVA::PCHARLAN | ORACLE CODASYL DBMS Engineering | Fri May 23 1997 16:26 | 3 |
| This will be fixed in V7.0 and in any future v6.1 release (after v6.1-11).
paul
|