Re: Oracle 8.1.7 to MySQL: problem with SP and sequences
Posted by: Philip Busch
Date: August 18, 2005 07:13AM

Hi Mike,

unfortunately, I mean exactly NUMBER(100), as displayed by the DESCRIBE command:


SQL> DESCRIBE abrechnung;
Name Null? Type
----------------------------------------- -------- ----------------------------
IDABRECHNUNG NOT NULL NUMBER
VORABZAHLUNG NUMBER(100)
PARAMETER1_TEXT VARCHAR2(80)
PARAMETER2_TEXT VARCHAR2(80)
PARAMETER3_TEXT VARCHAR2(80)


Look at the type of "VORABZAHLUNG": it's NUMBER(100)
Obviously, I wasn't able to manually create a table containing a NUMBER(100).

Then, I wasn't able to produce the corresponding Oracle CREATE TABLE statement either, because the Enterprise Manager 10g installer requests the SYS-password which nobody knows around here (the guy who installed and administered our Oracle database is "currently not available", which probably lasts forever). According to the docs, EM 10g doesn't run with Oracle 8.x anyway... Needless to say, nobody knows where our original Oracle 8.x CDs are right now.

In short, the problem still persists. Furthermore, I cannot even imagine how the NUMBER(100) has been created.

Does it suffice to file a bug report without the corresponding CREATE TABLE statement?
Any other suggestions?

Right now, I am open to just about everything...

Greets and many thanks for your ongoing support,
Philip

PS: just in case anyone is wondering, SELECT dbms_metadata.get_ddl() doesn't work with Oracle versions <9.x



Edited 1 time(s). Last edit at 08/18/2005 07:29AM by Philip Busch.

Options: ReplyQuote


Subject
Written By
Posted
Re: Oracle 8.1.7 to MySQL: problem with SP and sequences
August 18, 2005 07:13AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.